Location inventory data-loading
This service adds the inventory for the previously created items and locations in the warehouse. It calls the adjustLocationInventory() API.
Attribute | Description | Sequence | Data Type | Size |
---|---|---|---|---|
ALOCINVN | The inventory header identifier | 1 | String | 8 |
EnterpriseCode | The Inventory Organization Code. This indicates the Enterprise whose product information is being stored. | 2 | String | 24 |
Node | The Business key or unique identifier for a ship node. | 3 | String | 24 |
CaseId | The identifier for a case. This gives the LPN information for adjustment. | 4 | String | 40 |
LocationId | The identifier for a location. This forms unique key of this table in conjunction with NODE_KEY. Indicates the location from where the inventory is being adjusted. LocationId becomes mandatory, if CaseId/PalletId is not passed. | 5 | String | 40 |
PalletId | The identifier for a pallet. This gives the LPN information for adjustment. | 6 | String | 40 |
InventoryStatus | The inventory status gives the status of the inventory. Only one level InventoryStatus transitions happen for the inventory for positive adjustments. Negative adjustments do not take care of InventoryStatus transitions. If not passed, the status is taken as blank. | 7 | String | 10 |
SegmentType | The segment type for particular enterprise or organization. SegmentType becomes mandatory if Segment is passed. | 8 | String | 40 |
Segment | The segment for particular enterprise or organization. Segment becomes mandatory if SegmentType is passed. | 9 | String | 40 |
Quantity | This gives the adjustment quantity for the inventory. The negative quantity specifies negative adjustment and positive quantity denotes positive adjustment. Quantity becomes mandatory if SerialDetail does not provide quantity for adjustment. | 10 | Decimal | 14 |
ItemID | The item identity for the inventory | 11 | String | 40 |
UnitOfMeasure | The unit of measure for the item | 12 | String | 40 |
ProductClass | The product class for the item | 13 | String | 40 |
LotNumber | The lot number for the inventory | 14 | String | 40 |
LotAttribute1 | The lot attribute for the inventory | 15 | String | 40 |
LotAttribute2 | The lot attribute for the inventory | 16 | String | 40 |
ShipByDate | The date by which the inventory has to be shipped | 17 | Date | 10 |
SerialNo | The unique identifier for each serial | 18 | String | 40 |
ReasonCode | The reason code for the inventory transaction. The business significance of this reason code is that inventory bins are tied to this reason code, which is used to adjust inventory (for global inventory visibility purposes) on host systems. This is mandatory if inventory is getting updated. Some Sterling Order Management System Software APIs doing inventory adjustments expect some adjustment reason codes to be configured in the system. These are RECEIPT used by Receiving, PACK used by Packing functions and SHIP used by Shipment. PACK should have a bin associated while RECEIPT and SHIP should not have bin location associations. | 19 | String | 40 |
Schema files used
The schema files used by each component of the service and the API called by the service are as follows:
- Service Name: Inventory
- Service Group: InitialDataLoad
- Text Translator: AdjustLocationInventorySchema
- XSL Translator: AdjustLocationInventory
- API: adjustLocationInventory
- Server Name: InventoryLoader