Customer Shipment Data |
This option allows the ERP to send the Cards to Ultriva so that those can be Shipped in Ultriva. The fields marked as bold are required. Required fields must always have non-empty data.
The following table defines the fields in ERPCustomerShip Data file. The fields marked as bold are required. Required fields must always have non-empty data.
Field Name | Data Type | Length | Required | Nullable | Description |
---|---|---|---|---|---|
ReleaseID | STRING | 32 | Y | N | Kanban Card Barcode ID from Ultriva - unique for a cycle. If not available Send $ and send CardGID and Cycle No. |
PlantCode | STRING | 32 | Y | N | The Plant Code the Card Belongs to |
Item_Num | STRING | 32 | Y | N | Part number. |
CustomerCode | STRING | 32 | Y | N | The Customer Code of the card |
ShipTime | DATETIME | N/A | Y | N | Card Ship Time |
ShipQty | INTEGER | N/A | Y | N | Ship Qty |
CardGID | STRING | 32 | Y | Y | Card GID. This has to be sent if ReleaseID is sent as $ |
CycleNo | INTEGER | N/A | Y | Y | Card Cycle No. This has to be sent if ReleaseID is sent as $ |
TrackingNumber | STRING | 32 | N | Y | Tracking No. if any |
CarrierCode | STRING | 32 | N | Y | Carrier Code if any |
ChargeNo | STRING | 32 | N | Y | Charge No. if any |