Template Selection Guide
Use this page to choose the right template quickly.
Step 1: Choose Protocol and Direction
- OCI outbound: cart transfer in OCI field format.
- cXML outbound: PunchOutOrderMessage transfer.
- cXML inbound: setup/request normalization scenarios.
Step 2: Choose Platform Pack
| Platform | Recommended Start | When to switch |
|---|---|---|
| Generic OCI | oci_outbound_core |
use oci_outbound_extended if extra OCI fields are required |
| SAP OCI 4 | sap_oci_v4_outbound_core |
move to SAP OCI 5 templates when the buyer supports v5 fields |
| SAP OCI 5 | sap_oci_v5_outbound_core |
use sap_oci_v5_outbound_hierarchy for parent-child data, or sap_oci_v5_outbound_secure for strict enforcement |
| Generic cXML | cxml_outbound_core |
add optional enrichments with cxml_outbound_level2 |
| SAP Ariba | ariba_cxml_outbound_core |
use ariba_cxml_outbound_level2 or strict variant if level-2 fields are mandatory |
| Coupa | coupa_cxml_outbound_poom_1_2_023 |
use strict variant for mandatory complete payloads |
| Oracle Procurement | oracle_cxml_outbound_1b_core |
use strict variant when all mapped fields must be enforced |
Step 3: Pick Core vs Strict
core: safer for initial onboarding and partial source data quality.strict: best for mature integrations where every mapped field is required.
Step 4: Validate with Simulator and Trace
Before production:
- execute simulator request for target protocol
- verify mapped payload fields in trace
- confirm procurement-side acceptance