Click or drag to resize

PO Change Data

This option is used to Send the ERP Date Changes to Ultriva so that those can be updated. The fields marked as bold are required. Required fields must always have non-empty data.

ERP POChange Flat File Field Definition

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

POChange 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

EBJ_BUSCODE

STRING

32

Y

N

The Plant Code the Card Belongs to

EBJ_ITEMNO

STRING

32

Y

N

Part number.

ReqReceiveDate

DATETIME

N/A

Y

N

New Required Receive Date

OrderNum

STRING

32

Y

N

Purchase Order Number from ERP

OrderLineNum

INTEGER

N/A

Y

N

Purchase Order Line No from ERP Send 0 if Empty

OrderReleaseNum

STRING

32

Y

N

The P.O. Release No if any

OrderReleaseLineNum

STRING

32

Y

N

The Release Line No if any

Pre-Processing

This interface uses following fields as uniqueness constraint.

Field Name

Mandatory Field

EBJ_BUSCODE

Yes

EBJ_ITEMNO

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. If quantity and price are not given, then date is changed, therefore at least date must be given

  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

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 updated.

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

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.QTY

Double

N/A

N

Y

New Order Quantity

EBJ_RTPARAMS.UNITPRICE

Double

N/A

N

Y

New Unit Price

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