Click or drag to resize

Item Sync

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

Note Note

Please use File based approach for the Item Sync because the SQL based approach is deprecated

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

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

Ultriva Item Sync manages following:

  1. Item Properties:

    • Updates an existing Item if the given Item Number is found in the Business Unit context

    • If given item is not found then process Creates a new Item in the given business unit context

  2. Item to Supplier Relationship Properties:

    • If Item2Supplier details are given then the process also updates the Item2Supplier properties. (For instance a file may contain suppliercode and leadtime details then Ultriva Item sync updates or adds the Item2Supplier relationship data. Please note that for an existing item this process does not create new supplier relationship.)

Item Sync SQL Table Field Definition

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

Item Master Data SQL Table (inbound to Ultriva) ERP2UEKItemData

Field Name

Data Type

Length

Required

Nullable

Description

Destination Table

GID

STRING

32

Y

N

Unique Identifier.

--

ItemNo

STRING

64

Y

N

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

Item

ItemDesc

STRING

255

Y

N

Item Description

Item

PlantCode

STRING

32

Y

N

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

Item

Buyercode

STRING

32

Y

N

Buyer or Item co-ordinator user Code. This field may contain Ultriva user name here or User's buyer code field value.

Item

UOM

STRING

64

N

Y

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

Item

DrawingRefNo

STRING

64

N

Y

Drawing Number for this item if any

Item

RevisionNo

STRING

64

N

Y

Item Revision No. if any

Item

DailyDemand

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.

Item

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.

Item

CardQty

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

Item

FamilyCode

STRING

32

N

Y

Opitonal Product Line code. If not given then Unknown is assumed.

Item

LeadTime

NUMBER

N/A

Y

N

Lead Time in Business Days

Item2Supplier

TransitTime

NUMBER

N/A

Y

N

Transit Time in Business Days

Item2Supplier

OrderCycle

NUMBER

N/A

Y

N

Handling Time in Business Days

Item

VendorCode

STRING

32

Y

N

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

Item2Supplier

SupplierItemNo

STRING

64

N

Y

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

Item2Supplier

SupplierItemDesc

STRING

255

N

Y

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

Item2Supplier

MinOrderQty

INTEGER

N/A

N

Y

Minimum Number of orders. Used for Runline

Item2Supplier

Consolidate

INTEGER

N/A

N

Y

This flag tells if the Supplier uses Consolidated Shipments 1 or 0

Item

InspectionRequired

INTEGER

N/A

N

Y

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

Item

IntegrationRequired

INTEGER

N/A

N

Y

This flag tells if we need Po Release/Po Receipt integration point. 1 or 0.

Item

SupplierPoNum

STRING

32

N

Y

Blanket Supplier PO Number if any

Item2Supplier

SupplierPoLineNum

INTEGER

N/A

N

Y

Blanket Supplier PO Line Number if any

Item2Supplier

LocationCode

STRING

32

N

Y

Item Location code if any

Item

ERPSTATUS

STRING

32

Y

N

Should be Set to Created.

--

ERPSTATUSMSG

STRING

1024

Y

N

Any Status Message. Can be Empty

--

ERPLASTUPDATE

DATETIME

N/A

Y

N

Record Updated Time

--

UEKSTATUS

STRING

32

N

Y

Populated by Ultriva. Indicates the Staus of the Transaction. Valid Values(created,fail,processed))

--

UEKSTATUSMSG

STRING

1024

N

Y

Populated By Ultriva. If Error Error message will be sent.

--

UEKLASTUPDATE

DATETIME

N/A

N

Y

Populated By ultriva. Record Update Time

--

CRDATE

DATETIME

N/A

Y

N

Record Created Time

--

ActionDate

DATETIME

N/A

N

Y

Populated By ultriva.

--

Category

STRING

32

N

Y

One of the following values: Kanban, Virtual, Forecast. Default is Kanban

Item

ResponseGID

STRING

32

N

Y

Ultriva Internal Field

--

ClassificationCode

STRING

32

N

Y

Opitonal Commodity Code. If not given then Unknown is assumed.

Item

InventoryUnitCost

NUMBER

N/A

Y

N

Unit Price of this item

Item

SUBINVENTORY

STRING

32

N

Y

Subinventory for this item

Item

Processing Logic

An Import Process imports the Date from the SQL Table. 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 item number exists for given plant code. If it is not found then it will create an item. If it is found then it will update that item record

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

  3. If given product line or commodity code does not exist then the process creates those master entries.