Click or drag to resize

Supplier Sync

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

Supplier Sync Flat File Field Definition

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

Supplier Master Data File (inbound to Ultriva)

Field Name

Data Type

Length

Required

Nullable

Description

PlantCode

STRING

32

Y

N

Plant Code where this new supplier or association should be made

SupplierCode

STRING

32

Y

N

Unique SupplierCode Code to identify this supplier.

SupplierName

STRING

256

Y

N

Supplier Name for this supplier.

Address1

STRING

64

Y

N

Address Line 1 for the supplier address

Address2

STRING

64

N

N

Address Line 2 for the supplier address

Address3

STRING

64

N

N

Address Line 3 for the supplier address

City

STRING

32

Y

N

City of this Supplier

State

STRING

32

Y

N

State

Zip

STRING

32

Y

N

Zip Code

Country

STRING

32

Y

N

Country

Pre-Processing

This interface uses following fields as uniqueness constraint.

Field Name

Mandatory Field

EBJ_BUSCODE

Yes

VENDORCODE

Yes

  1. If there are duplicate records for this combination then only one record with latest timestamp is considered (other records for this item will be marked as DUPLICATE).

Processing Logic

The Batch Job Processor uses following logic to identify the supplier business unit

  1. It looks up the approved suppliers list for a given Business Unit Code and Vendor Code. If it finds a record then it updates the Supplier properties.

  2. If it does not find the record by the above lookup then it looks up by the Vendor Code in the Global Supplier List. If it finds a record then uses the supplier record and creates a new supplier association to the given Plant/EBJ_BUSCODE.

  3. If both the methods failed to resolve the supplier then it looks up by the name in the Global Supplier List. If the supplier is found then it checks if the given address is same as the resolved supplier. If they are same then the same supplier is used to create a new association.

  4. If all the three methods failed to resolve a supplier then processor creates a new supplier in the global supplier list and creates a new supplier association with the given business unit code.

Optional Fields

Additional to the fields mentioned above ERP could send some optional fields.

Field Name

Data Type

Length

Required

Nullable

Description

IsAutoAccept

INT

N/A

N

Y

If 1 then auto accept is enabled. Default is 0.

IsAutoReceive

INT

N/A

N

Y

If 1 then auto receipt is enabled. Default is 0.

Holidays

STRING

64

N

Y

Series of holiday weekday numbers. For e.g. 17 will make Sunday and Saturday as holidays. If it is empty then Processor defaults to 17.

1 is for Sunday and 7 is for Saturday.

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

STRING

N/A

N

Y

Telephone number for this supplier business unit

EBJ_RTPARAMS.FAXNO

STRING

N/A

N

Y

Fax number of the supplier

EBJ_RTPARAMS.LOCATION

STRING

N/A

N

Y

Supplier Business Unit Location. Processor defaults City as Location. However if the input is given for this field then processor uses this input for the location.

Error Handling

Supplier Sync 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

Vendor Name already exists for different Vendor Code

Given Vendor Name already exists with different vendor code.