Click or drag to resize

Customer Item Sync

This option allows the Ultriva Customer Item master data to be in synch with the ERP Customer Item master data. The fields marked as Required Yes are mandatory fields. Required fields must always have non-empty data.

Note Note

If an item already exists in the Ultriva master, this process updates the item

During the update process one could pass -1 for NUMBER fields and empty string for string fields for not updating the field value.

Note Note

To reset a string field value you may pass $$reset

Note Note

An item file may contain same item number multiple times if an item is supplied by multiple vendors.

Item Sync Flat File Field Definition

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

Customer Item Master Data File (inbound to Ultriva)

Field Name

Data Type

Length

Required

Nullable

Description

ItemNo

STRING

64

Y

N

This must be unique part number with in given Business Unit Code

ItemDesc

STRING

255

Y

N

Item Description

PlantCode

STRING

32

Y

N

Plant Code. A single file may contain data for a business unit and it's workcenters.

CustomerCode

STRING

32

Y

N

Customer Business Unit Code. If given Customer business unit code is not found then this record will be errored out

ActionCode

STRING

1

Y

N

ActionCode A-Add, C-Change, D-Disable

CustomerItemNo

STRING

64

N

Y

Customer Item Code. This is an optional field. If not given Plant Item No is used.

CustomerItemDesc

STRING

255

N

Y

Customer Item Description. This is an optional field. If not given plant Item description is used.

UOM

STRING

64

N

Y

UnitDescription - This filed is Unit of Measure. For Eg Ea-(Each), Pcs(Pieces).

FamilyCode

STRING

32

Y

N

Product Line (Must already be setup in Ultriva). Send '$' if no family association required

ClassificationCode

STRING

32

Y

N

Commodity Code (Must already be setup Ultriva). Send '$' if no Commodity code association required

UsagePerDay

NUMBER

N/A

Y

N

It is the average daily demand or average usage per day for the Part Number. This value is used in the Kanban Card Calculation.

SafetyTime

NUMBER

N/A

Y

N

Represents the Safety Stock you wish to carry for that part. For e.g. for a 2 day safety stock you enter a value of 2.

QtyOnCard

NUMBER

N/A

Y

N

It is the standard lot size used by the supplier for replenishment (box or palette or container size). This is used as the Quantity per Kanban Card

LeadTime

NUMBER

N/A

Y

N

Lead Time in Business Days

TransitTime

NUMBER

N/A

Y

N

Transit Time in Business Days

HandlingTime

NUMBER

N/A

Y

N

Handling Time in Business Days

MinOrderCards

Integer

N/A

N

Y

Minimum Number of orders. Used for Runline

CustomerPoNum

STRING

32

N

Y

Blanket Customer PO Number if any

CustpmerPoLineNum

Integer

N/A

N

Y

Blanket Customer PO Line Number if any

PricePerUOM

NUMBER

N/A

Y

N

Unit Price of this item

Consolidate

Integer

N/A

N

Y

Consolidate the shipping. If yes,1 else 0. (Activates Ship Hub State)

Inspection

Integer

N/A

N

Y

Is this item needs inspection after Receipt? 1 or 0. 1 means Inspection Required

Integration

Integer

N/A

N

Y

If ERP integration required for PORelease and POReceipt then 1 else 0.

Additional Flex Fields in Item Master File (inbound to Ultriva)

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.RevisionNo would set the Revision Number in the item master.

Note Note
Please note that the Flat file's field names can be mapped to Ultriva Field names through configuration. For e.g. an incoming file may contain a field called Drawing_Number and this field can be mapped to Ultriva field name EBJ_RTPARAMS.DrawingNo.

Field Name

Data Type

Length

Required

Nullable

Description

EBJ_RTPARAMS.DrawingNo

STRING

32

N

Y

Drawing Number for this item

EBJ_RTPARAMS.SUBINVENTORY

STRING

32

N

Y

Subinventory for this item

EBJ_RTPARAMS.RevisionNo

STRING

32

N

Y

Revision Number for this item

EBJ_RTPARAMS.SW

STRING

32

N

Y

Shipping Weight for this item

EBJ_RTPARAMS.ABCCode

STRING

32

N

Y

ABCCode for this item

Processing Logic

An Import Process imports the file. During the import if it finds missing values or wrong data then it marks those records as errors. Remaining records are imported into Batch Table for further processing.

After successful importing of the data, a batch job processes each set of item records.

  1. The process checks if the given vendor code is already associated to the busienss unit if not it checks the parent business unit for supplier association, if the association is found then it creates a new association to this business unit.