Click or drag to resize

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.

ERP Ship Flat File Field Definition

The following table defines the fields in ERPShip Data file. The fields marked as bold are required. Required fields must always have non-empty data.

ERPShip Data File (inbound to Ultriva)

Field Name

Data Type

Length

Required

Nullable

Description

ReleaseID

STRING

32

Y

N

Kanban Card Barcode ID from Ultriva - unique for a cycle

PlantCode

STRING

32

Y

N

The Plant Code the Card Belongs to

Item_Num

STRING

32

Y

N

Part number.

Vendor_Code

STRING

32

Y

N

The Vendor Code of the card

ShipTime

DATETIME

N/A

Y

N

Card Ship Time

ShipQty

INTEGER

N/A

Y

N

Ship Qty

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

MasterLabelID

STRING

32

N

Y

Auto Generated Master Label ID from the allocated range, if any

PackingSlipNo

STRING

256

N

Y

Shipment Bill of Lading/ Packing Slip Number

SiteID

STRING

12

N

Y

Ultriva Site ID

Pre-Processing

This interface uses following fields as uniqueness constraint.

Field Name

Mandatory Field

EBJ_BUSCODE

Yes

Order Parameters

Yes

ReleaseId

Yes

  1. If ReleaseId is empty then it looks up by item, plant, supplier, order number, order line number, order release number, order release line number. This must return only one record.

Validation

Batch Job Processor validates each record with following validation before it starts processing the record.

  1. Master Label ID, Ultriva allocates a specific range of numbers for Master Labels within which the supplier has to generate for each shipment

  2. CardID should be in the right state

  3. CardID must belong to the supplier and plant

  4. CardID should belong to the item from the record

  5. Shipment Qty must be greater than 0

Processing Logic

If Master Label Id is not given then the system will generate one if supplier has enabled for master label.

If ReleaseID is given then it returns a CardID. Using the CardID, a card is found. If the card is in a valid state then the card is sent to supplier.

If ReleaseID is empty, then it looks up by item, plant, supplier, order number, orderline number, orderrelease number, orderreleaseline number. This must return only one record. This record is used to find the card. If the card is in a valid state then the card is sent to supplier.

Job file Params

Settings for processing logic

Key Name

values

Default

Comments

novendorcode

true/false

false

true - The input file does not have EBJ_BUSCODE false - The input file must have EBJ_BUSCODE

Additional Flex Fields

Additional to the fields mentioned above ERP could send some advanced fields in the Flex field format. The Field name should start with EBJ_RTPARAMS and then a dot then a field name. For e.g. EBJ_RTPARAMS.TELNO would set the Telephone number.

Field Name

Data Type

Length

Required

Nullable

Description

EBJ_RTPARAMS.LOTNO

STRING

32

N

Y

Vendor Lot Number/ Serial number

EBJ_RTPARAMS.LOTNOTES

STRING

64

N

Y

Any additional information regarding the lot

EBJ_RTPARAMS.LOTQTY

Double

N/A

N

Y

Quantity for the Lot

Error Handling

Accept Data Processor may mark incoming records with specific error messages during interface processing.

The following table shows the error messages and their meaning:

Note Note

In the following table the placeholders are encoded with curly braces.

Error Message

Meaning

CardID does not belong to plant

CardID does not match plant code given in the file

CardID does not belong to item

CardID does not belong to the item referenced by Item Number

Plant code is missing

Empty plant code in the record

Item number is missing

Empty item number in the record

Invalid Order Number

When release id is empty, then the order lookup failed

More than one card found for order number

When release id is empty, order lookup resulted in more than one card

CardID does not belong to plant item

CardID does not belong to supplier item

CardID does not belong to item number

CardID does not belong to item passed in the file