Object Structure Element
Integration XML and Schemas 71
The Change, Replace, and AddChange actions differ in the information that they
include in the XML message and the processing that they require of the receiving
system.
An action attribute at the primary object level specifies the overall processing
action that applies to the parent and child records. At the child object level, it
indicates processing that is specific to that record.
Business rules always take precedence over the action attribute. If business rules
prohibit the action that is specified on an inbound XML message, an error occurs.
For example, an inbound transaction that attempts to update a closed PO will
result in an error.
If a single XML document contains multiple instances of an object structure, each
instance of the object structure can specify a different action attribute. In the
following example, the COMPANIES record has multiple child COMPCONTACT
records, each with its own action attribute.
<MXVENDOR>
<COMPANIES action="Change">
<COMPANY>TEST4</COMPANY>
<NAME>test</NAME>
<ADDRESS1>100 Main Str</ADDRESS1>
<COMPCONTACT action="Add">
<NAME>SMITH</NAME>
<TITLE>MANAGER</TITLE>
</COMPCONTACT>
<COMPCONTACT action="Change">
<NAME>JONES</NAME>
<TITLE>ENGINEER</TITLE>
</COMPCONTACT>
</COMPANIES>
</MXVENDOR>
Add action An add action indicates that the corresponding data is added to a database. For
inbound transactions, an error occurs if the data exists. The add action on a
primary object extends to its child objects, so it is not necessary to specify the add
action at the child object level. Outbound transactions contain an add action when
the insert of an object generates the transaction.
Delete action A delete action indicates that the corresponding object and its child objects are
deleted from the database. The delete action on a primary object extends to its
child objects, so it is not necessary to specify the delete action at the child object
level.
An outbound XML message with a delete action on the primary object may not
include the child objects, but the receiving system is responsible for identifying
and deleting them.
When a primary object in an inbound XML message contains the delete action,
the integration framework deletes the child objects that are related to the primary
Null Add records or replace records in the receiving system,
depending on whether the primary record exists in the
database.
Value Description
To Next Page
Loading...