Template Selection Guide
Choose the template from the cart document the buyer expects, not from the procurement brand alone.
1. Choose protocol
- Use OCI when the buyer opens the shop with OCI parameters and expects indexed
NEW_ITEM-*form fields back. - Use cXML when the buyer sends a
PunchOutSetupRequestand expects aPunchOutOrderMessageback.
2. Choose an outbound starting point
| Buyer contract | Start with | Add or change when |
|---|---|---|
| Generic OCI | oci_outbound_core |
Copy selected rules from oci_outbound_extended for extra fields. |
| SAP OCI 4 | sap_oci_v4_outbound_core |
The buyer explicitly accepts a different field/version set. |
| SAP OCI 5 | sap_oci_v5_outbound_core |
Use hierarchy fields only when requested. |
| Generic cXML | cxml_outbound_core |
Add selected level-2 enrichment rules when requested. |
| SAP Ariba-oriented cXML | ariba_cxml_outbound_core |
Move to level 2 for buyer-required manufacturer/extrinsic data. |
| Coupa-oriented cXML | coupa_cxml_outbound_poom_1_2_023 |
Change versions or fields to match the buyer's current specification. |
| Oracle-oriented cXML | oracle_cxml_outbound_1b_core |
Add or remove extrinsics according to the tenant contract. |
Do not assign an inbound template to a buyer. Inbound fixtures are catalog/reference records in the current core and are not executed by the setup controllers.
3. Decide whether strict is appropriate
A strict template marks every supplied rule mandatory. It is useful only when the buyer rejects incomplete rows and Magento reliably contains every value.
Strict mapping does not mean stricter authentication. Request signing, IP restrictions and transport authentication are configured separately.
4. Validate the copied profile
- Copy the template into a new outbound profile.
- Remove fields the buyer does not accept.
- Map required fields to maintained Magento data.
- Test products with missing optional attributes, decimal quantities and buyer-specific prices.
- Inspect the generated payload and have the procurement system accept it.
- Keep the runtime copy stable; do not edit the synchronized template for project-specific behavior.
See the Templates Overview for the current template catalog.