On this page
  1. cxml_inbound_posr_core
  2. cxml_outbound_core
  3. cxml_outbound_level2

cXML Core Templates

Use these fixtures when the buyer needs standard cXML-style fields without a platform-specific starter pack.

cxml_inbound_posr_core

This inbound reference contains eight PunchOutSetupRequest rules. Operation, sender domain, sender identity, buyer cookie and browser form-post URL are mandatory in the fixture; shared secret and selected-item IDs are optional.

The current setup controller parses these fields directly from cXML. It does not execute this inbound profile. Use the fixture as a field reference or as a base for custom inbound normalization code.

cxml_outbound_core

  • 6 rules, 5 mandatory
  • Quantity, supplier part ID, unit price, description and unit of measure are required
  • Classification is optional

This is the normal starting point for a generic PunchOutOrderMessage runtime profile. Independently of the mapping, every emitted ItemIn carries a sequential lineNumber; a procurement platform can echo it as ItemOut@lineNumber in the later OrderRequest for exact returned-cart line matching.

cxml_outbound_level2

  • 5 optional enrichment rules
  • Supplier auxiliary ID, manufacturer name/part ID, classification domain and image URL extrinsic

This fixture is not complete by itself because every rule is optional. Add its relevant rules to a profile that also contains the required core cart fields.

Before go-live, confirm the buyer's DTD expectations, units, classification domain, currency and extrinsic names. The module generates cXML, but acceptance remains buyer-specific.

Display preferences

Adjust how this website is displayed. Changes apply immediately.

Text size
Text spacing
Reading aids

Follows the pointer. Move it with Alt + Up/Down outside input fields. Hidden while a dialog is open.

Uses the voices provided by your browser, which may use an online service. Reading starts only when you press Read aloud.

Your choices are saved in this browser for this website.