Click or drag to resize

Accept Data

This option allows the ERP to send the Cards to Ultriva so that those can be Accepted in Ultriva. The fields marked as bold are required. Required fields must always have non-empty data.

ERP Accept Flat File Field Definition

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

ERPAccept 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

Accept_Time

DATETIME

N/A

Y

N

Card Accept Time

Pre-Processing

This interface uses following fields as uniqueness constraint.

Field Name

Mandatory Field

EBJ_BUSCODE

Yes

VendorCode

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. CardID should be in the right state

  2. CardID must belong to the supplier and plant

  3. CardID should belong to the item from the record

Processing Logic

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.

Optional Fields

Additional to the fields mentioned above ERP could send some optional fields.

Field Name

Data Type

Length

Required

Nullable

Description

OrderNum

STRING

64

No

Yes

Purchase order number

OrderLineNum

INTEGER

NA

No

Yes

Purchase order line number

OrderReleaseNum

STRING

32

No

Yes

Purchase order release number

OrderReleaseLineNum

STRING

32

Yes

No

The Release Line No if any, Send 0 if Empty.

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