- SAP Managed Tags
I am happy to announce that we have extended our envelope support to the cXML Type System. Our B2B Library of predefined content now includes the envelope structures for cXML as well. As a result, you can now combine cXML Envelope and cXML Message parts into one Message Implementation Guideline (MIG). Doing so, you can use the envelope fields at other places like in Mapping Guidelines (MAGs). In this blog post I want to give you an overview of the new offering.
cXML Envelopes in Type System Content
The Type System Content in Integration Advisor was extended to contain the cXML Envelopes as well (starting from version 1.2.044). In Message Overview you can simply search for Envelope to find the according structures.
cXML defines three different envelope structures: the EnvelopeForRequests, the EnvelopeForResponses plus the EnvelopeForMessages. Note as a cXML specialty that the choice of the Envelope depends on the Message Type:
- Use EnvelopeForRequests for so called cXML Request messages like OrderRequest or InvoiceRequest.
- Use EnvelopeForResponses for so called cXML Response messages like DataResponse or OrderStatusSetupResponse.
- Use EnvelopeForMessages for so called cXML Message messages like SupplierChangeMessage or ProductActivityMessage.
By the way, if you navigate to the Message placeholder node within the envelope structures, you will find the fitting message types (shown as allowed code values).
Refer above screenshot for a cXML EnvelopeForRequests structure. Please note that the envelope structure is independent from the specific message(s) used and only shows a placeholder for the message level.
Message Implementation Guidelines with Envelopes
For your Message Implementation Guideline (MIG) you have now the new option to combine Envelope and Message parts into one merged structure.
When creating a new MIG for the cXML Type System, you will find the step Envelopes as part of the Creation Wizard. Here you can decide if you want to use an envelope or not and select the specific envelope structure you want to use.
As a result, your MIG starts with the root node cXML and has the envelope parts (see blue box above) plus the specific message parts (see green box above) according to the Message Type you have selected for your MIG. Refer above screenshot for an exemplary cXML OrderRequest MIG which includes the EnvelopeForRequests (with nodes Header and Request).
Envelope Usage in Cloud Integration
Previously, your Integration Flow in Cloud Integration needed an additional flow step to remove the envelope parts from the cXML payload. You don’t need this flow step anymore if you use an envelope inside your cXML MIG.
Additionally, we implemented another small improvement: If your MIG does not include an Envelope, then the Integration Advisor preprocessing (preproc.xslt) automatically removes the envelope part from the payload. This applies to all Type Systems that offer envelopes. In this way, you can even skip this additional flow step for MIGs without envelope.
Further cXML Content Improvements in Integration Advisor
As we have updated our cXML content, we used the chance to add a few more improvements to it (in accordance with the cXML Reference Guide):
- All date/time fields (based on Simple Type datetime.tz) and all time fields (based on Simple Type time.tz) refer to a new special Date Time Format required by cXML. In both cases, this is the standard ISO 8601 format, but with mandatory time zone offset and Z not being allowed (like 2026-04-01T11:11:11+02:00 for Date/Time or 11:11:11+02:00 for Time).
- The common xml:lang attribute is now used in its standard form inside your MIG.
- All fields based on Simple Type UnitOfMeasure come now with a reference to the codelist Rec 20 from UN/CEFACT.
Conclusion
With this extension we support envelope structures for the cXML Type System in Integration Advisor. You can now include envelope nodes into your Message Implementation Guideline (MIG) definition and as result use these nodes inside your Mapping Guidelines (MAGs).
Further reading
Bluesky| User | Count |
|---|---|
| 34 | |
| 9 | |
| 9 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
