|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 I
By Suraj Kumar Pabbathi, PI Competency Lead, YASH Technologies
tutorial, we would discuss about CIDX Message eStandards starting from expanding
CIDX. CIDX stands for Chemical Industry Data Exchange.
advent of â€śeBusinessâ€ť, companies in chemical industry adopted certain common
communication principles to reduce the overall cost of XML-Based integration
projects to realize business transactions with partners. These common principles
are based on eStandards known as Chem eStandards which are used by chemical
industries for exchanging data Business-to-Business (B2B) and
more of Chem-eStandards, download the document from http://xml.coverpages.org/Chem-eStandardsV20.pdf
and go through it.
facilitate the use of automated data exchange between chemical companies, CIDX
an organization has transformed its organization to operate as standards
organization. It will support and maintain the Chem eStandards. Its official
website is www.cidx.org.
the messages interoperable across the chemical industries based on XML
standards, chem eStandards leverage the transport, envelope and security aspects
of RNIF version 1.1 as described below diagrammatically:
the explanation of every part of the Chem eStandard Message.
It handles information global to document (version, datestamp)
Preamble of the message is as follows:
Header: It contains
the information about transaction routing and processing information for a given
transaction. The service header contains three separate data objects:
It describes the process to be carried out by the transaction encapsulated in
Service Route: It
describes â€śtoâ€ť and â€śfromâ€ť information.
control: It provides the information how the transaction encapsulated in the
service content is to be processed.
contains the actual message that is considered to be an action message which
needs to be transported to partner.
eStandards is developed with number of conventions for content and structure of
the data models/messages as described below under sections, Message Definition,
Message Responses, Message structure, Message elements.
Definition: They are
defined with two facets of guiding principles.
messages are intended to support only one business function. Eg: OrderCreate is
messages supporting a single business function can modify the nature of
transaction being performed based on data values.
For Eg: OrderCreate message support Standard Order, RushOrder
Responses: There are
two types of Responses. Technical and Transaction Responses.
responses are returned to source system from destination upon deliver of
messages from source to destination. Again there are two types.
ReceiptAcknowledgement is positive Chem eStandard Signal message. When
received, it means that the message is received by partner and the message is
valid chem eStandard Action message.
ReceiveAcknowledgementException: Received by source to state that the
partner has received a message which is invalid in terms of schema validation
General Exception: Received by source system when processing of action
message by partner runs into error.
Response: They are reply or response to requested Action Message. For eg:
Purchase Order Response is sent by partner as a response to the action message
received like Purchase Order.
They are unique and it is not necessary that every
transaction has transaction response.
Action message is the actual message that is sent to partner. Eg: Invoice
message is the response message that is received by source system in response to
the action message received by partner.
Structure: It is XML
document conforming to corresponding DTD (Data type definition). Every message
will start with a root element addressing the message itself and has child
elements as Header and Body.
Elements: An XML
specification describes structure data as explained above. XML document elements
may either contain other data elements or data (or both). These message elements
may contain attributes that describe the data within the message element.
whole transactions can be exchanged between business partners with a sample
explained diagrammatically below:
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