IBM Support

Customer Master Data Template File Description

Question & Answer


Question

Customer Master Data Template File Description

Answer

Customer Master Data Template File Description

The fields in the customer_template.csv fileand the conditions to be maintained when updating this file are describedin the following table:

Header FieldDescription
CUSTOMERIndicates the title of the entity type. Do notmodify this row and its contents.
RECORDID (ACTRID)Indicates the identifier of the record for actionto be performed. Do not modify the order of this field in the masterdata file. When adding a new row you must copy the value in thiscolumn to the new row. Any row that does not contain the RECORDIDvalue will be considered as an invalid record and this record willnot be processed.
ACTIONIndicates the action to be performed on thisrecord. The valid values are Manage Create Modify and Delete. Thedefault value is Manage.
RECORDID (CSTRID1)Indicates the identifier of the record for customerdetails. Do not modify the order of this field in the master datafile. When adding a new row you must copy the value in this columnto the new row. Any row that does not contain the RECORDID value willbe considered as an invalid record and this record will not be processed.
CUSTOMERIDIndicates the name of the customer. Ensure thatthe name of the customer does not exceed 16 characters. This is amandatory field. The master data upload will fail if you do not providea value in this field.
COMPANYIndicates the name of the customer.
CUSTOMERTYPEIndicates the type of the customer. The validvalues are CONSUMER and BUSINESS.
RELATIONSHIPTYPEIndicates the relationship of this customerwith your organization for example Buyer Seller and so on.
VERTICALIndicates the customer's vertical marketor line of business for example Education Government and so on.
DUNSNUMBERIndicates the Data Universal Numbering System(DUNS) number of the customer organization.
ISTAXEXEMPTIndicates whether the customer contact is exemptedfrom tax. The valid values are Y and N.
RECORDID (CSTRID2)Indicates the identifier of the record for customercontact details. Do not modify the order of this field in the masterdata file. When adding a new row you must copy the value in thiscolumn to the new row. Any row that does not contain the RECORDIDvalue will be considered as an invalid record and this record willnot be processed.

You can add multiple additional attributes tothe CSTRID2 record in the master data file. You can provide theserecurring values in the master data file by copying the recurringfields group (CSTRID2 and its corresponding fields) one after theother in the master data file.

The CSTRID2 recurring group includesFIRSTNAME MIDDLENAME LASTNAME JOBTITLE EMAILID and DAYPHONE fields.

FIRSTNAMEIndicates the first name of the customer contact.
MIDDLENAMEIndicates the middle name of the customer contact.
LASTNAMEIndicates the last name of the customer contact.
JOBTITLEIndicates the functional designation of thecustomer contact.
EMAILIDIndicates the email address of the customercontact.
DAYPHONEIndicates the telephone number of the customercontact.
RECORDID (CSTRID3)Indicates the identifier of the record for additionalcustomer contact details. You can use this recurring group to addadditional addresses to the customer contact. Do not modify the orderof this field in the master data file. When adding a new row youmust copy the value in this column to the new row. Any row that doesnot contain the RECORDID value will be considered as an invalid recordand this record will not be processed.

You can add multiple additionalattributes to the CSTRID3 record in the master data file. You canprovide these recurring values in the master data file by copyingthe recurring fields group (CSTRID3 and its corresponding fields)one after the other in the master data file.

The CSTRID3 recurringgroup includes FIRSTNAME MIDDLENAME LASTNAME EMAILID DAYPHONEADDRESSLINE1 ADDRESSLINE2 CITY STATE COUNTRY ZIPCODE ISCOMMERCIALADDRESSDEFAULTSHIPTO DEFAULTBILLTO AND DEFAULTSOLDTO fields.

FIRSTNAMEIndicates the first name of the customer contact.
MIDDLENAMEIndicates the middle name of the customer contact.
LASTNAMEIndicates the last name of the customer contact.
EMAILIDIndicates the email address of the customercontact.
DAYPHONEIndicates the telephone number of the customercontact.
ADDRESSLINE1Indicates the address of the customer contact.
ADDRESSLINE2Indicates the address of the customer contact.
CITYIndicates the location of the customer contact.
STATEIndicates the state where the customer contactis located.
COUNTRYIndicates the country of the customer contact.
ZIPCODEIndicates the ZIP code of the customer contact'slocation.
ISCOMMERCIALADDRESSIndicates whether the address of the customercontact is commercial or residential. The valid values are Y and N.
DEFAULTSHIPTOIndicates whether the address specified is thedefault address of the customer contact for shipping the order. Thevalid values are Y and N.
DEFAULTBILLTOIndicates whether the address specified is thedefault address of the customer contact for billing. The valid valuesare Y and N.
DEFAULTSOLDTOIndicates whether the address specified is thedefault address of the customer contact. The valid values are Y andN.
Notes:
  • New customers can be created using the master data upload functionality.The Organization Code for a new customer is constructed by concatenatingthe value of the CustomerID (provided in the master data file) andthe partial value of the Parent Organization Code. For example ifthe value of CustomerID is TESTCUSTID001 and the value of the ParentOrganization Code is ODCO00130789 the Organization Code of the newcustomer is created by removing ?ODCO? and appending the remaining8 characters to the CustomerID. Therefore the constructed OrganizationCode is TESTCUSTID00100130789.
  • If you have deleted an existing business customer from the systemusing the Delete option in the Action attributein the customer_template.csv file ensure that youdo not reuse the value of the CustomerID of the deleted business customer.This is because the organization associated with the deleted businesscustomer is retained in the database. If you attempt to upload theCustomer master data template file with the value of the CustomerIDof the deleted business customer the master data upload fails witha ?Record already exists in the database? error message. Howeverthis restriction in the reuse of the CustomerID value is not applicablewhen uploading the Customer master data template file for a consumercustomer.
  • The maximum size of the master data file that you can upload ata time is 4 MB. If you need to upload a master data file whose filesize is greater than 4 MB modify the master data file or create additionalmaster data files in conformity with the maximum file size limit.
  • Do not reuse the values of the RECORDID provided in the templatefile such as ACTRID CSTRID1 and so on in the other fields such asCUSTOMERID COMPANY and so on. The master data upload will fail ifyou provide the same values as that of the RECORDID
  • Do not add multiple values for a non-recurring group against asingle record. This will cause the record to fail as the record willbe considered as an invalid record.
  • Ensure that none of the fields contain blank values. If you donot want to use a field in the master data file you must enter anasterisk as the value in that field such that the unused field isdisregarded during the master data file upload.
  • The third and fourth rows of the master data template file containsample data.
  • Do not add a line break in a field.
  • Do not localize the master data file.

"

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SS73G6","label":"Sterling Total Payments for Financial Services"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 December 2018

UID

ibm10762749