OCI and SAP Templates

These fixtures cover generic OCI and SAP-oriented OCI 4/5 field sets. Copy an outbound template into a runtime profile, then compare every target field with the buyer's actual OCI specification.

Inbound reference fixtures

`oci_inbound_core`

Eight rules describe common login values: required FUNCTION and HOOK_URL, plus optional USER, PASSWORD, buyer ID, currency, language and session ID.

`sap_oci_v4_inbound_login`

Seven rules describe the OCI 4 login baseline: required function and hook URL plus optional credentials, buyer, currency and language.

`sap_oci_v5_inbound_login`

Nine rules add ~OkCode and session ID to the OCI 4-oriented set.

These inbound fixtures are synchronized into the catalog, but the core login controller does not execute inbound mapping rules. It parses supported OCI parameters directly. Keep them as implementation references unless custom code explicitly consumes them.

Outbound runtime starters

`oci_outbound_core`

6 rules, all mandatory
Description, quantity, unit, price, currency and vendor material number
Use for a generic OCI cart return after the buyer confirms those field names

`oci_outbound_extended`

3 optional rules
Additional cost, material group and long text
An enrichment set rather than a complete standalone profile; keep required core rules in the final runtime mapping

The module always adds NEW_ITEM-EXT_PRODUCT_ID from the external product ID configured on the buyer profile. This is protected output and is not an editable mapping rule.

NEW_ITEM-LEADTIME and NEW_ITEM-MANUFACTCODE are available as custom mapping targets. Map them only when Magento has a maintained product attribute that matches the buyer's expected value. PunchOut does not invent a lead time or treat a Magento manufacturer label as an SAP manufacturer code.

`sap_oci_v4_outbound_core`

7 rules, 6 mandatory
Core OCI fields plus optional SAP material number

`sap_oci_v5_outbound_core`

8 rules, 6 mandatory
Core fields plus optional material number and external quote ID

`sap_oci_v5_outbound_hierarchy`

8 rules, 6 mandatory
Includes optional parent ID and material group for hierarchy-aware buyer configurations

`sap_oci_v5_outbound_secure`

8 rules, all mandatory
Includes external quote and contract values
Use only when all eight source values are maintained and the buyer rejects incomplete rows

secure means fail-fast required-field behavior in the mapping. It does not enable request signing, encryption or SAP certification.

Selection rule

Start with the smallest outbound set accepted by the buyer. Add optional rules deliberately. Moving from OCI 4 to OCI 5 is a buyer-system decision, not an automatic Magento upgrade.