Oracle XML PunchOut

Technical explantation of what happens behind-the-scenes through data and requests via Oracle XML Punchout example:

  • Oracle XML login request is made – Similar, though different from cXML, the data within the post often will contain parameters (such as unique identifiers) that may include the user’s email address, business unit ID, DUNS, and others that vary from e-procurement system to system and buyer to buyer that is used by the e-commerce application to properly authenticate the user and reflect the correct offering, pricing, experience, etc. The data from this generally will include the following as examples:
    • fullName: John Doe
    • Manager: Sally Sue
    • title: ceo
    • userEmail: [email protected]
    • companyDUNS: 12345678
    • operatingUnit: 13843
    • companyName: ACME
    • buyercookie: 7555371f46f7a5d057ac3567a2df12c2
    • language: ZH
    • loginURL:…
  • Login URL Response – The vendors e-commerce application returns a URL that redirects the user to to begin their shopping experience directly on the vendors e-commerce application. The response, if successful, will provide a 200 and redirect the browser to the URL from the response, ie.
  • oracleCart Line Data Message – When the user selects to transfer the cart, the data included per line item will generally consist of at least the following parameters that will get posted to “loginURL” referenced in step 1.
    • Description: Some Great Product Name
    • Classification: 80141611 (UNSPSC or sometimes different and will vary from buyer to buyer)
    • PartID: 1234567 (Product SKU)
    • PartAuxiliaryID: 8888/65689 (References the cart data against the session)
    • Quantity: 1
    • Unit Price: 55.68
    • UOM: EA (The Unit of Measure (ie. Each, Case, etc., will also vary from buyer to buyer)
    • Currency: USD