RCG Customers Process API - Implementation Template
Data mappings
This document provides information generated from the DataWeave scripts included in the project, such as function definitions, variable definitions, and data mapping tables.
customer-date-sync-response
Customer Sync Success Response
Source:
./src/main/resources/dwl/customer-date-sync-response.dwl
customer-sync-retrieve-by-last-modified-date
Source:
./src/main/resources/dwl/customer-sync-retrieve-by-last-modified-date.dwl
get-customer-orders
Get Orders of a Customer Mapping
Source:
./src/main/resources/dwl/get-customer-orders.dwl
Mapping Tables
Maps Orders of a Customer from OMS System API as in CIM format.
OMS | Customer | Description |
---|---|---|
orderId | id | The Order Id for an Order as in OMS |
orderNumber | orderNumber | Order Number for an Order |
filedDate | filedDate | Filed Date of the the Order |
promiseDate | promiseFulfillmentDate | Fulfillment Date for the Order |
orderStartDate | orderStartDate | Start Date for the Order |
orderEndDate | orderEndDate | End Date for the Order |
customerId | soldToCustomer | Customer associated with the Order |
originalOrderId | originalOrder | OriginalId of the Order |
orderType | salesOrderType.name | Order Type of the Order |
orderStatus | salesOrderStatus.name | Status of the order |
get-list-of-customers-response
Source:
./src/main/resources/dwl/get-list-of-customers-response.dwl
map-b2c-customer-update-request
Customer Update Mapping for B2C Commerce
Source:
./src/main/resources/dwl/map-b2c-customer-update-request.dwl
Mapping Tables
Maps customer profiles of SourceSystems (SAP or Salesforce) to MDM in CIM format which is further used for creation of Customer in B2C Commerce. The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId to be stored in B2C Commerce to uniquely identify the customer.
MDM | B2C Commerce | Description |
---|---|---|
id | id | The id will be GlobalPartyRoleId for updating an existing customer |
partyRoleType | partyRoleType | The type of party role - default as Customer |
party.id | null | The id of the Party |
party.partyType | Individual | The type of Party |
party.personName | firstName lastName | The full name of the Party |
party.firstName | firstName | The first name of the Party |
party.lastName | lastName | The last name of the Party |
party.externalIds | externalIds | The GlobalPartyId of Customer as in MDM.This will not be stored in B2C Commerce |
customerNumber | customerNumber | The Customer Number to be stored in B2C Commerce |
customerStatus | customerStatus | The Status of Customer to be updated in B2C Commerce |
externalIds | externalIds | The GlobalPartyRoleId of Customer as in MDM that will need to be stored in B2C Commerce |
map-customer-contact-points
Source:
./src/main/resources/dwl/map-customer-contact-points.dwl
map-customer-create-request
Customer Create Mapping for a System (B2C,Salesforce,SAP,HANA,OFBiz)
Source:
./src/main/resources/dwl/map-customer-create-request.dwl
Mapping Tables
Maps customer profiles of SourceSystem to MDM in CIM format which is further used for creation of Customer in other systems (B2C,Salesforce,SAP,HANA,OFBiz).The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId with ExternalIdType as MDM. This Id will be stored in SAP ECC to uniquely identify the customer.
MDM | System | Description |
---|---|---|
id | id | The id will be null for creating a new Customer in a System |
partyRoleType | partyRoleType | The type of party role - usually Customer |
party | party | The Party |
externalIds | externalIds | The GlobalPartyRoleId of Customer as in MDM that will need to be stored in SAP ECC |
customerNumber | customerNumber | The Customer Number to be stored in a System |
customerStatus | customerStatus | The Status of Customer to be updated in a System |
map-erp-prc-request
Customer Mapping for ERP Systems (SAP ECC, HANA)
Source:
./src/main/resources/dwl/map-erp-prc-request.dwl
Mapping Tables
Maps customer profiles of SourceSystems (B2C,Salesforce,ERP Systems -SAP ECC, HANA) to MDM in CIM format which is further used for creation of Customer in B2C Commerce. The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId to be stored in ERP Systems(SAPECC,HANA) to uniquely identify the customer.
MDM | ERP Systems | Description |
---|---|---|
id | id | The id will be GlobalPartyRoleId for updating an existing customer |
partyRoleType | partyRoleType | The type of party role - default as Customer |
party.id | null | The id of the Party |
party.partyType | Party | The type of party |
party.personName | firstName lastName | The full name of the Party |
party.firstName | firstName | The first name of the Party |
party.lastName | lastName | The last name of the Party |
party.externalIds | externalIds | The GlobalPartyId of Customer as in MDM.This will not be stored in ERP Systems |
customerNumber | customerNumber | The Customer Number to be stored in ERP Systems |
customerStatus | customerStatus | The Status of Customer to be updated in ERP Systems |
externalIds | externalIds | The GlobalPartyRoleId of Customer as in MDM that will need to be stored in ERP Systems |
map-new-contact-points
Source:
./src/main/resources/dwl/map-new-contact-points.dwl
map-ofbiz-customer-create-request
Customer Create Mapping for OFBiz
Source:
./src/main/resources/dwl/map-ofbiz-customer-create-request.dwl
Mapping Tables
Maps customer profiles of SourceSystem (SAP or B2C Commerce) to MDM in CIM format which is further used for creation of Customer in OFBiz.The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId with ExternalIdType as MDM. This Id will be stored in OFBiz to uniquely identify the customer.
MDM | OFBiz | Description |
---|---|---|
id | id | The id will be null for creating a new Customer in OFBiz |
partyRoleType | partyRoleType | The type of party role - usually Customer |
party | party | The Party |
externalIds | externalIds | The GlobalPartyRoleId of Customer as in MDM that will need to be stored in OFBiz |
customerNumber | customerNumber | The Customer Number to be stored in OFBiz |
customerStatus | customerStatus | The Status of Customer to be updated in OFBiz |
map-ofbiz-customer-update-request
Customer Update Mapping for OFBiz
Source:
./src/main/resources/dwl/map-ofbiz-customer-update-request.dwl
Mapping Tables
Maps customer profiles of SourceSystem (SAP or B2C Commerce) to MDM in CIM format which is further used for creation of Customer in OFBiz. The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId with ExternalIdType as MDM. This Id will be stored in OFBiz to uniquely identify the customer.
MDM | OFBiz | Description |
---|---|---|
id | id | The id will be GlobalPartyRoleId to update an existing Customer in OFBiz |
partyRoleType | partyRoleType | The type of party role - usually Customer |
party.id | null | The id of the Party |
party.partyType | Party | The type of Party |
party.personName | firstName lastName | The full name of the Party |
party.firstName | firstName | The first name of the Party |
party.lastName | lastName | The last name of the Party |
party.externalIds | externalIds | The GlobalPartyId of Customer as in MDM.This will not be stored in OFBiz |
externalIds | externalIds | The GlobalPartyRoleId of Customer as in MDM that will need to be stored in OFBiz |
customerNumber | customerNumber | The Customer Number to be stored in OFBiz |
customerStatus | customerStatus | The Status of Customer to be updated in OFBiz |
map-salesforce-customer-create-request
Customer Create Mapping for Salesforce
Source:
./src/main/resources/dwl/map-salesforce-customer-create-request.dwl
Mapping Tables
Maps customer profiles of SourceSystem (SAP or B2C Commerce) to MDM in CIM format which is further used for creation of Customer in Salesforce.The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId with ExternalIdType as MDM. This Id will be stored in Salesforce to uniquely identify the customer.
MDM | Salesforce | Description |
---|---|---|
id | id | The id will be null for creating a new Customer in Salesforce |
partyRoleType | partyRoleType | The type of party role - usually Customer |
party | party | The Party |
externalIds | externalIds | The GlobalPartyRoleId of Customer as in MDM that will need to be stored in Salesforce |
customerNumber | customerNumber | The Customer Number to be stored in Salesforce |
customerStatus | customerStatus | The Status of Customer to be updated in Salesforce |
map-salesforce-customer-update-request
Customer Update Mapping for Salesforce
Source:
./src/main/resources/dwl/map-salesforce-customer-update-request.dwl
Mapping Tables
Maps customer profiles of SourceSystem (SAP or B2C Commerce) to MDM in CIM format which is further used for creation of Customer in Salesforce. The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId with ExternalIdType as MDM. This Id will be stored in Salesforce to uniquely identify the customer.
MDM | Salesforce | Description |
---|---|---|
id | id | The id will be GlobalPartyRoleId to update an existing Customer in Salesforce |
partyRoleType | partyRoleType | The type of party role - usually Customer |
party.id | null | The id of the Party |
party.partyType | Party | The type of Party |
party.personName | firstName lastName | The full name of the Party |
party.firstName | firstName | The first name of the Party |
party.lastName | lastName | The last name of the Party |
party.externalIds | externalIds | The GlobalPartyId of Customer as in MDM.This will not be stored in Salesforce |
externalIds | externalIds | The GlobalPartyRoleId of Customer as in MDM that will need to be stored in Salesforce |
customerNumber | customerNumber | The Customer Number to be stored in Salesforce |
customerStatus | customerStatus | The Status of Customer to be updated in Salesforce |
map-salesforce-individual-create-request
Contacts Create Mapping for Salesforce
Source:
./src/main/resources/dwl/map-salesforce-individual-create-request.dwl
map-salesforce-individual-update-request
Contacts Update Mapping for Salesforce
Source:
./src/main/resources/dwl/map-salesforce-individual-update-request.dwl
map-subscriber-contact-points
Source:
./src/main/resources/dwl/map-subscriber-contact-points.dwl
map-subscriber-create-request
Individual/Subscriber Creation Mapping for Salesforce Marketing
Source:
./src/main/resources/dwl/map-subscriber-create-request.dwl
Mapping Tables
Maps Individual associated with Customer Profile of SourceSystem (SAP or B2C Commerce) to MDM in CIM format which is further used for creation of Subscriber in Salesforce Marketing.The object structure is same with only exception of GlobalPartyRoleId being sent as an ExternalId with ExternalIdType as MDM. This Id will be stored in Salesforce Marketing to uniquely identify an Individual.
MDM | Salesforce Marketing | Description |
---|---|---|
id | id | The id will be null for creating a new Subscriber in Salesforce Marketing |
partyType | Individual | The type of party - default as Individual |
personName | firstName lastName | The full name of the individual |
firstName | firstName | The first name of the individual |
lastName | lastName | The last name of the individual |
externalIds | externalIds | The GlobalPartyId of an Individual as in MDM.This will not be stored in Salesforce Marketing |
contactPoints | contactPoints | The ContactPoints of an Individual used for creating a Subscriber in Salesforce Marketing Cloud. ContactPointEmailAddress is only used by Salesforce Marketing Cloud |
map-subscriber-update-request
Individual/Subscriber Update Mapping for Salesforce Marketing
Source:
./src/main/resources/dwl/map-subscriber-update-request.dwl
Mapping Tables
Maps Individual associated with Customer Profile of SourceSystem (SAP or B2C Commerce) to MDM in CIM format which is further used for creation of Subscriber in Salesforce Marketing. The object structure is same with only exception of GlobalPartyId being sent as an ExternalId to be stored in Salesforce Marketing to uniquely identify an Individual.
MDM | Salesforce Marketing | Description |
---|---|---|
id | id | The id will be GlobalPartyId for updating an existing Subscriber in Salesforce Marketing |
partyType | Individual | The type of party - default as Individual |
personName | firstName lastName | The full name of the individual |
firstName | firstName | The first name of the individual |
lastName | lastName | The last name of the individual |
externalIds | externalIds | The GlobalPartyId of an Individual as in MDM.This will not be stored in Salesforce Marketing |
contactPoints | contactPoints | The ContactPoints of an Individual used for creating a Subscriber in Salesforce Marketing Cloud. ContactPointEmailAddress is only used by Salesforce Marketing Cloud |
map-updated-contact-points
Source:
./src/main/resources/dwl/map-updated-contact-points.dwl
ping-check-dependency-sys-api-response
Ping Status Response of the backend System API's
Source:
./src/main/resources/dwl/ping-check-dependency-sys-api-response.dwl
ping-response-payload
Ping Status Response of the API
Source:
./src/main/resources/dwl/ping-response-payload.dwl
retrieve-customers-queryParams-request-mapping
Source:
./src/main/resources/dwl/retrieve-customers-queryParams-request-mapping.dwl
update-external-id-object
update external Id using update operator
Source:
./src/main/resources/dwl/update-external-id-object.dwl
Mapping Tables
using update operator we can modify particular field in an payload. To update particular key in an object we can use this syntax field("keyNametoupdate") with "ValueToKey" To update particular key in an Array we can use this syntax ["ArrayKeyName","keyNametoUpdate"] with "ValueToKey".
CIM - Customer | AnypointMQ | Description |
---|---|---|
id | externalIds.Id | The Master Id of that MDM |
externalIds.Id | CustomerNumber | The SAPECC customer number |
externalIds.externalIdType | SAP_ECC | Hardcoded to SAP_ECC |