| Element | Parent | Required | Data Type | Description | Valid Values |
|---|---|---|---|---|---|
| TransactionHeader | Yes | ||||
| TransactionType | TransactionHeader | Yes | VARCHAR(20) | This is the type of transaction that is being integrated | Adjustment |
| TransactionClassID | TransactionHeader | No | VARCHAR(50) | This is the ID of the inventory transaction class the transaction belongs to. The default transaction class is used, if the value is not provided. | |
| TransactionID | TransactionHeader | No | VARCHAR(50) | This is the transaction number. If a transaction number is passed and this transaction exists we will add the items to the transaction. If the transaction does not exist we will create it. If this is empty we will use the next number. | |
| TransactionStatusName | TransactionHeader | No | VARCHAR(25) | This is the status that the transaction should be integrated as. If no status is passed, "New" will be used. | |
| SiteID | TransactionHeader | Yes | VARCHAR(20) | This is the site ID that the transaction is being completed in. | |
| TransactionDate | TransactionHeader | Yes | DATETIME | This is the date the transaction affects inventory. | |
| ReasonCode | TransactionHeader | No | VARCHAR(50) | This is the reason code for the adjustment. Must be a valid NorthScope reason code. | |
| UserID | TransactionHeader | No | VARCHAR(110) | This is the user who is completing the transaction. Does not have to be a valid NS user. | |
| CompanyID | TransactionHeader | Yes | VARCHAR(15) | This is the ID of the company that you are sending data for. The value must match an entry in ERPx_MFDataEntityCompany for the Company ID column. | |
| TransactionDetail | TransactionHeader | Yes | |||
| ItemSort | TransactionDetail | No | Integer | This is the sequence of the items on the transaction. If not passed we will sequence them. If a sequence conflict comes up we will override with the new information. | |
| ItemID | TransactionDetail | Yes | VARCHAR(50) | This is the item ID for the inventory item being adjusted. This must be a valid Sales/Inventory item type. | |
| TransactionUnits | TransactionDetail | No | NUMERIC(18,5) | This is the number of units for this line on the transaction. If an item is managed by units only or units and weight this value must be passed. | |
| UnitsUOMID | TransactionDetail | No | VARCHAR(10) | This is the unit of measure for the units on the transaction. It is required if TransactionUnits is being used. | |
| TransactionWeight | TransactionDetail | No | NUMERIC(18,5) | This is the weight value for this line on the transaction. If an item is managed by weight only or units and weight this value must be passed. | |
| WeightUOMID | TransactionDetail | No | VARCHAR(10) | This is the unit of measure for the weight on the transaction. It is required if TransactionWeight is being used. | |
| Lot | TransactionDetail | No | VARCHAR(50) | This is the production batch (or "lot") number for this line of the transaction if batches/lots are being managed. |
Example:
<TransactionHeader>
<TransactionType>Adjustment</TransactionType>
<TransactionClassID>Default</TransactionClassID>
<TransactionID>A123456</TransactionID>
<TransactionStatusName>Ready To Post</TransactionStatusName>
<SiteID>ABC</SiteID>
<TransactionDate>2017-12-19</TransactionDate>
<ReasonCode />
<UserID>Integrated</UserID>
<CompanyID>XYZ</CompanyID>
<TransactionDetail>
<ItemSort />
<ItemID>1234321</ItemID>
<TransactionUnits>5.00000</TransactionUnits>
<UnitsUOMID>CASE</UnitsUOMID>
<TransactionWeight>150.5500</TransactionWeight>
<WeightUOMID>LB</WeightUOMID>
<Lot>18001</Lot>
</TransactionDetail>
</TransactionHeader>