Click or drag to resize

Planned Orders

This Planned Orders Interface is used when Business wants to publish the orders to the Suppliers. The Orders are already created in ERP system and Ultriva acts as a portal for these Orders.

Planned Orders Flat File Field Definition

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

Planned Orders Data File (inbound to Ultriva)

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.

EBJ_ITEMNO

STRING

32

Y

N

Item Number for which this PO has to be accounted for.

ORDERNUM

STRING

128

Y

N

Purchase Order Number.

ORDERLINENUM

INT

N/A

Y

N

Purchase Order Line Number

ORDERRELEASENUM

STRING

32

N

Y

Purchase Order Blanket Release Number if any

ORDERRELEASELINENUM

STRING

32

N

Y

Purchase Order Blanket Release Line Number if any

VENDORCODE

STRING

32

Y

N

Supplier Code

ORDERQTY

NUMBER

N/A

Y

N

Order Quantity

ORDERDATE

DATETIME

N/A

Y

N

Order Date

REQSHIPDATE

DATETIME

N/A

N

N

Required Ship Date if any

REQRECEIVEDATE

DATETIME

N/A

Y

N

Required Receive date

Pre-Processing

This interface uses following fields as uniqueness constraint.

Field Name

Mandatory Field

EBJ_BUSCODE

Yes

EBJ_ITEMNO

Yes

ORDERNUM

Yes

ORDERLINENUM

Yes

ORDERRELEASENUM

No

ORDERRELEASELINENUM

No

  1. If a record already exists with PROCESSED status with the above fields then this RECORD is marked as DUPLICATE.

  2. Given EBJ_BUSCODE must exist in the system.

  3. ORDERQTY must be greater than 0. If it is less than or equal to 0 then the RECORD is marked as ERROR.

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 VendorCode must be an approved vendor for this Item Number. 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 supplier.

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.ITEM_REVISION would set the Revision Number.

Field Name

Data Type

Length

Required

Nullable

Description

EBJ_RTPARAMS.UNITPRICE

NUMBER

N/A

N

N

Unit Price for the line item

EBJ_RTPARAMS.ITEM_REVISION

STRING

N/A

N

Y

Item’s revision number for this purchase order

EBJ_RTPARAMS.PO_REVISION_NUM

STRING

N/A

N

Y

Purchase Order Revision number

EBJ_RTPARAMS.Currency_Code

STRING

N/A

N

Y

Currency Code for this order

Passing Ship To Details

If order contains different Ship To address than default address then the address details can be passed to Ultriva.

There are two ways to pass the details.

  1. Using Drop Off Location Code. The Drop off location must be a valid address code that exists in Ultriva.

    Field Name

    Data Type

    Length

    Required

    Nullable

    Description

    EBJ_RTPARAMS.ShipToAddrCode

    STRING

    N/A

    N

    N

    Ship To Address code

  2. Sending all the address information as separate flex fields.

    Field Name

    Data Type

    Length

    Required

    Nullable

    Description

    EBJ_RTPARAMS.ShipToS1

    STRING

    N/A

    Y

    N

    Address Line 1

    EBJ_RTPARAMS.ShipToS2

    STRING

    N/A

    N

    N

    Address Line 2

    EBJ_RTPARAMS.ShipToS3

    STRING

    N/A

    N

    N

    Address Line 3

    EBJ_RTPARAMS.ShipToC

    STRING

    N/A

    Y

    N

    City

    EBJ_RTPARAMS.ShipToS

    STRING

    N/A

    N

    N

    State

    EBJ_RTPARAMS.ShipToZ

    STRING

    N/A

    N

    N

    Zip code

    EBJ_RTPARAMS.ShipToCtry

    STRING

    N/A

    N

    N

    Country

Error Handling

Planned Orders 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

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 that are allowed to be created in a single attempt setting in the business unit.

Invalid Order Number

Given Order Number is NULL or Empty.

Invalid Order Qty

Given Order Qty is less than 0.

Given Data Row is less than 0

This is an internal error. It should not occur.

Given Data Row is greater than or equal to RowCount

This is an internal error. It should not occur.

Item is disabled

Item is disabled in Ultriva.

Item is not a forecast item

This job releases orders for Items that are categorized as FORECAST. However this given item is not categorized as FORECAST Item.

Given VendorCode <{0}> is not found in the system or not mapped to the Plant

Given supplier is not an approved supplier in Ultriva.

Given Item <{0}> is not found in the system for BusGID <{1}>

Given item code is not found in the given business unit code.

Given VendorCode <{0}> is not mapped to item.

Given vendor is not an approved supplier for this item.

Given VendorCode <{0}> is not found in the system. Tried to locate using VendorCode|VendorSiteCode pattern. Rows returned <{1}>

Given vendor code is not found in the system. The job processor tried to resolve the supplier using combination of Vendor Code and Vendor Site Code which is also failed to resolve to a valid supplier.