Defining a field-level mapping for each integration point includes providing data types, field lengths, applicable values, and validation logic for each field. This mapping helps you identify the mapping requirements between the system so that you can address any data type, field length, and restrictions. The following table shows customer integration between Finance and Operations and an e-commerce application:
|
Finance and Operations Field name |
Data type |
Requirement |
Default value |
E-commerce field |
Description |
|
CustTable.AccountNum |
NVARCHAR(20) |
Mandatory |
Number sequence |
Account.Id |
Unique identifier for the customer record |
|
CustTable.CustGroup |
NVARCHAR(10) |
Mandatory |
Web |
NA |
Defines customer group |
|
DirPartyPostalAddress.PostalAddress |
NVARCHAR(250) |
Optional |
|
Account. PostalAddress |
Stores the customer's address |