|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Chem XML Message eStandards and CIDX Scenario - Part II
By Suraj Kumar Pabbathi, PI Competency Lead, YASH Technologies
I, we have discussed about CIDX Message eStandards. Now let us discuss how
to configure and design the objects to support the communication based on CIDX
standards in XI.
achieved by designing the Message types in Integration Repository and
configuring collaboration profiles using CIDX adapter in Integration Repository.
Adapter: CIDX Adapter supports the chem eStandards described in PartI and
facilitates to send the messages between Integration Server and Partner System
by transforming the message format in XML to message format compliant to chem
eStandard Business transaction (chem XML Message) and vice-versa.
supports Single-Action Asynchronous business transaction, in the sense, at a
time it can send only single action message (for e.g.: Invoice) to partner
system in asynchronous mode.
variety of chem eStandard business transactions described in the chem eStandard
that can be exchanged with partner participating in different roles such as
buyer, seller and so on.
some of the transactions supporting Logistics execution are listed below; where
in third column indicates Global Process Indicator code of chem XML
Sample Transaction Code List
messages when sent by Integration Engine to Adapter Engine, in Adapter Engine,
the messages are enveloped as RNIF Action and Signal messages as specified in
RNIF 1.1 specification.
the step by step procedure to design and configure the scenario to send a sample
(Invoice) message to Partner system.
time activities in Integration Repository:
based on chem. eStandards, must be compliant with message interface content in
repository. This means that the DTDs/Schemas need to be downloaded from www.cidx.org
and uploaded into Integration Repository through External Definitions as
illustrated in the screenshot below:
that Software component CIDX has Software component version 1.0, which in turn
has different namespaces created under them.
namespaces and Schemas should be supporting chem. eStandards, as CIDX Adapter
determines/constructs the namespace and interface name of an incoming CIDX
Action Message as follows:
Specify the selected version of the message chosen from the schemas available
Message> := /ServiceHeader/â€¦/ActionControl/ActionIdentity/GlobalBusinessActionCode
Message: A big list of messages are provided which would suit the business
transactions performed between chemical companies. They support many scenarios
like Customer, Logistics Execution, Catalog and RFQ, Purchase Order, Financials,
ForeCasting, Exchange Interactions.
time activities in Integration Directory:
plan for a scenario where in our XI system acts as receiver of the message and
partner system sends an Invoice message. That is Partner is starting a message
exchange with XI.
a Sender CIDX adapter needs to be configured which is considered to be Single
Create two parties, one representing Buyer (initiator) and
other Seller (Responder), EDI_XML_Buyer and EDI_XML_Seller respectively.
Service Name should be as CIDX<TransactionCode>_Version_PartnerRole.
<Transaction Code>:= /ServiceHeader/ProcessControl/ProcessIdentity/GlobalProcessIndicatorCode
Transaction Code: For every business transaction, CIDX
standards have defined unique Code to identify the transaction and process it
accordingly. A sample code list is provided earlier in this document.
<Partner Role>:= /ServiceHeader/ProcessControl/TransactionControl/PartnerRoleRoute/fromRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode
<Current Role>:= /ServiceHeader/ProcessControl/TransactionControl/PartnerRoleRoute/toRole.PartnerRoleDescription/GlobalPartnerRoleClassificationCode
Buyer service should be named as CIDXE81_40_Buyer
Seller service should be named as CIDXE81_40_Seller
Find below the sample message containing the information as
As partner is initiating the message select the adapter type
For understanding more about the parameters of CIDX adapter
while configuring them, go through http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
XI and RNIF protocols support message level security by
digital signature and encryption. Message-level
security processing is done in Java part of SAP WAS.
CA (Certificate Authority) certificates to be used need to be
entered into Key Store of J2EE Engine that executes the security handling at
During configuration these certificates are referred while
defining the communication channels when certificate logon is used.
Otherwise, UserName/Password authenticity can be used
There are three sections to achieve the security of
transmission of the messages between chemical companies
Non-Repudiation of the message when selected for inbound messages means
that partner cannot deny of sending the messages and stores the inbound message
in the security archive.
Non-Repudiation of the message when selected for Outbound messages means
that partner cannot deny or receiving the messages and stores the outbound
message in the security archive.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards