Skip to main content

CMD and RKTS Integration

In existing on-prem system rkts07-integration application will convert the SC300S XML message into RKTS tag based message format and push into MQ and from there RKTS application will consume the data.

In modernization, CMD will publish the messages into EMP topic on cloud and from there messages will be replicated to ground by EMP. The messages from ground topic will be consumed and converted to RKTS tag based message format.

The below diagram shows the how the RKTSPush solution needs to be implemented in modern platform without impacting the RKTS application.

Below table shows field mapping and transformation logic from CMD to RKST. This is not fully completed, needs to be mapped all fields.

CMD EMP FieldsTransformation LogicRKTS FieldsDefault Value
MESSAGE_IDSCVFE001
VERSION1
Current DatetimesendTimeNow
Get Previous time from config filesendTimePrevious
TAG_IDTAG001
externalSystemReferenceexternalSystemName=SCVcustomerNumber
tradingNamecustomerName
tradingNamecustomerAbbrName
apartmentOrFloor,streetNamecustomerAddress1
streetNumber,subArea,district,cityNamecustomerAddress2
regionCode,postalCode,isoCountryCodecustomerAddress3
customerAddress4
zipCode
regionCodestate
linkPhoneNumber
LINK_EXPORT_FAX
telefax
concernCode
vipNonRollvipClass
EDI_SYSTEM
MSL_EXPORT_SALES_CODE
FORWARDERS_BROKER
FORWARDERS_COMMUNICATION
ORG_BROKERAGE
orgFmcCode
EMPLOYEE_CODE
BUREAU_OF_CONSENSUS_AUTHORIZED
EXCLUDE_FORWARDER
EXCLUDE_BROKER
LOCAL_MARK
identifierValueidentifierType=TAX, identifierCodetaxReference
PREPAID_PAY_AT_PORT
COLLECT_PAY_AT_PORT
PREPAID_PAYER
COLLECT_PAYER
LINK_IMPORT_FAX
MSL_IMPORT_SALES_CODE
SCL_EXPORT_SALES_CODE
SCL_IMPORT_SALES_CODE
locAddressName
locPoBoxNumber
locStreetName
locStreetNumber
locAddressLine2
locCityCode
locAddressLine3
ACTION1
Was this page helpful?