Product master data

1. Endpoints

All read-only (GET). Row counts are what this host currently serves.

Single-entity reads use OData v2 key syntax: A_Product('SKU') and A_ProductPlant(Product='SKU',Plant='KOK2').

2. Query options

3. Will my pipeline config work here?

Filters taken verbatim from real inbound-pipeline configs, with the rows this host returns for each. A non-zero, non-total count means the filter is genuinely being applied.

4. A_Product

One row per material. Carries the commodity classification (ProductGroup) and the base unit.

{
  "d": {
    "results": [
      {
        "Product": "CW-APC-5L",
        "ProductType": "ZDIE",
        "BaseUnit": "PCE",
        "ProductGroup": "A030102",
        "ProductDescription": "All-purpose cleaner 5L",
        "CatalogueProductId": "cleanworks:APC-5L"
      }
    ]
  }
}

5. A_ProductPlant

One row per material and plant (SAP MARC) — the material is extended to that plant. It carries no storage location: that is one grain further down, in A_ProductStorageLocation. Note also that a plant extension alone does not mean the material is stocked — service and non-stock material types carry plant views too, so pair it with a ProductType whitelist.

{
  "d": {
    "results": [
      {
        "Product": "CW-APC-5L",
        "Plant": "HBN1",
        "ProfileCode": "",
        "ProfileValidityStartDate": null,
        "PurchasingGroup": "001",
        "CountryOfOrigin": "",
        "Region": "",
        "ProductionInvtryManagedLoc": "",
        "IsBatchManagementRequired": false,
        "SerialNumberProfile": "",
        "IsMarkedForDeletion": false,
        "MRPType": "PD",
        "MRPResponsible": "",
        "MRPGroup": "",
        "ReorderThresholdQuantity": "0",
        "PlanningTimeFence": "0",
        "LotSizingProcedure": "EX",
        "MinimumLotSizeQuantity": "0",
        "MaximumLotSizeQuantity": "0",
        "FixedLotSizeQuantity": "0",
        "RoundingProfile": "",
        "GoodsReceiptDuration": "0",
        "PlannedDeliveryDurationInDays": "0",
        "SafetyStock": "0"
      }
    ]
  }
}

6. A_ProductStorageLocation

One row per material, plant and storage location (SAP MARD). The row's existence is the “has a storage-location view” signal; quantities are not here — those live in a separate material-stock API.

• IsMarkedForDeletion is how de-stocking is signalled. Flagged rows stay in the collection — 13 of 49 here — so a consumer never has to infer removal from a row's absence. Do not filter them out of the query, or you lose exactly that signal.
• There is no change timestamp on this entity or on A_ProductPlant — only CreationDate. A delta load keyed on “last changed” is not possible; these sources full-reload. Scope them by plant to keep that affordable.

{
  "d": {
    "results": [
      {
        "Product": "CW-APC-5L",
        "Plant": "HBN1",
        "StorageLocation": "7000",
        "WarehouseStorageBin": "BIN-7000",
        "MaintenanceStatus": "DL",
        "PhysicalInventoryBlockInd": "",
        "CreationDate": "/Date(1639008000000)/",
        "IsMarkedForDeletion": false,
        "DateOfLastPostedCntUnRstrcdStk": null,
        "InventoryCorrectionFactor": "0",
        "InvtryRestrictedUseStockInd": "",
        "InvtryCurrentYearStockInd": "",
        "InvtryQualInspCurrentYrStkInd": "",
        "InventoryBlockStockInd": "",
        "InvtryRestStockPrevPeriodInd": "",
        "InventoryStockPrevPeriod": "",
        "InvtryStockQltyInspPrevPeriod": "",
        "HasInvtryBlockStockPrevPeriod": "",
        "FiscalYearCurrentPeriod": "2021",
        "FiscalMonthCurrentPeriod": "12",
        "FiscalYearCurrentInvtryPeriod": "2021",
        "LeanWrhsManagementPickingArea": ""
      }
    ]
  }
}