Click or drag to resize

Customer Orders

This option allows connector to send Customer Order Information to a business unit in Ultriva. The fields marked as bold are required. Required fields must always have non-empty data.

Customer Order Flat Field Definition

The following table defines the fields in Customer Orders 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

EBJ_BUSCODE

STRING

32

Y

N

Business Unit Code. This must match with the code in Ultriva.

CUSTOMERCODE

STRING

32

Y

N

Customer Code. This must be a valid customer code in Ultriva customer master.

EBJ_ITEMNO

STRING

32

Y

N

Plant Item Number for which this order is created for.

ITEMNO

STRING

32

N

Y

Customer Item Number if known.

ORDERDATE

DATETIME

N/A

Y

N

Timestamp of the order when it is created.

ORDERQTY

NUMBER

N/A

Y

N

Order Qty must be valid positive number.

REQSHIPDATE

DATETIME

N/A

N

N

Date time when the order has to be shipped. This is an optional field. If not given then Ultriva calculates this field from given Required Receive Date.

REQRECEIVEDATE

DATETIME

N/A

Y

N

Valid Time stamp for order to be received by the customer.

PONUM

STRING

N/A

Y

N

Purchase Order Number

POLINENUM

INTEGER

N/A

Y

N

Purchase Order Line Number

POReleaseNum

STRING

N/A

N

Y

Blanket Release Number if any.

POReleaseLineNum

STRING

N/A

N

Y

Blanket Release Line Number if any.

UnitPrice

NUMBER

N/A

N

Y

Purchasing Unit Price

UOM

STRING

N/A

N

Y

Optional Unit of Measure

Pre-Processing

This interface uses following fields as uniqueness constraint.

Field Name

Mandatory Field

EBJ_BUSCODE

Yes

EBJ_ItemNo

Yes

CustomerCode

Yes

OrderNum

Yes

OrderLineNum

Yes

OrderReleaseNum

No. Conditionally mandatory.

OrderReleaseLineNum

No. Conditionally mandatory.

SalesOrderNum

No. Conditionally mandatory.

SalesOrderLineNum

No. Conditionally mandatory.

  1. If there are duplicate records for this combination then other records for this combination will be marked as DUPLICATE.

Validation

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

  1. Given EBJ_ITEMNO must exist in the given Business Unit context.

  2. Given Customer Code must be mapped to the Business Unit. If not the record is marked as ERROR.

Processing Logic

The Batch Job Processor creates a non-replenishment card for given order details and releases the card to the plant.

Error Handling

Customer Order 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

Unable to find the given customer code <{0}> in business unit {1}

Given Customer Code is not found in the Customer master for the supplying plant or workcenter business unit.

Unable to find the given item number in this business unit

Given Item Number is not found in the item master.

Invalid Order Qty

Given Order Qty is less than 0

Customer Code {0} could not be resolved

Unable to resolve the customer code to internal customer GID.

Invalid Order Number

Order Number is empty

Item is disabled

Given item is disabled

JobErpPlannedOrder.ReleaseForecastOrder OrderQty: {0} LotSize: {1} NoOfCards/Lots to be released: {2} which is above the maximum limit {3}

Calculated Number of cards to be created is exceeding number of cards are allowed to create in a single attempt setting in the business unit.