punchout overview 28 th of august, 2007 · what is ariba®punchout™? ariba punchout allows...
TRANSCRIPT
Punchout Overview28th of August, 2007
Global Supplier Integration Team
28th August, 2007 2
Punchout Introduction
Roche Punchout Requirements
Technical Overview
Test Scenarios
Documentation Overview
Contact
28th August, 2007 3
What is Ariba® Punchout™?
Ariba Punchout allows procurement applications to use Punchout enabled web shops as a dynamic, supplier hosted catalog.
• Ariba Punchout creates a quote and not an order.
The supplier can’t take any action directly after the punchout session.
• Buyer approval workflow will be triggered.
– The shopping basket will need to be approved in the Roche Ariba application.
– After the approval workflow has been finished in the buying organization the actual
purchase order will be sent to the supplier, who can then start to process / fulfill the
order.
• Ariba Punchout is achieved through a dialog of cXML Messages between:
– Ariba Buyer
– Ariba Supplier Network (ASN)
– Supplier Website
28th August, 2007 4
Punch-Out Message Flow (1)
The initial message flow is transmitted over the ASN in order to securely set up the Website connection.
Ariba BuyerServer
Browser
Supplier
ASN
3. Setup Response
or error 500
4. Punchout Frame Set
https 2. Punchout
Setup Request
Digital certificates or shared
secrets to authenticate cXML
documents
1. Punchout
Setup Request
28th August, 2007 5
Punch-Out Message Flow (2)
The final shopping basket is being transmitted directly from the supplier’s website to Ariba.
Ariba BuyerServer
Browser
ASN
6. PunchoutOrderMessage
5. Checkout HTML-Form (cXML 1.1)
Browser
Form Post
Supplier
28th August, 2007 6
Punchout Introduction
Roche Punchout Requirements
Technical Overview
Test Scenarios
Documentation Overview
Contact
28th August, 2007 7
Ariba Punchout Functionality
A punchout website should be able to handle 3 actions on a shopping basket: Create, Edit and Inspect.
Create a new shopping basket - Mandatory
• The first time the supplier punchout site is selected.
Edit a shopping basket - Preferred
• Edit a: Edit an existing shopping basket
• Edit b: Edit after punch out to the same supplier in one requisition (SelectedItem)
• During editing requisition (if operation was allowed by the supplier)
– Changes are possible
– ItemOut: to reconstruct shopping basket
– SupplierPartAuxiliaryID or SupplierPartID
Inspect existing shopping basket - Preferred
• Changes are not possible
• process after “Add Items” and from status list
• requester and approver
28th August, 2007 8
Ariba Punchout Requirements (1)Following some general requirements which must be fulfilled.
• Supplier provides a dynamic web shop, available 24 hours a day, 5 days a week.
• Supplier gives advance notice of any foreseeable downtime on his side.
• The integration of the punchout takes place on supplier side. Roche simple loads an index
file (CIF or XML) containing the supplier‘s DUNS, name and description of the punchout.
• Connection must be safe, fast and reliable.
• Search engine of the punchout must allow wildcard search and refined search.
• Wildcard search: e.g. search for „*stat*“ will show „Thermostat“ among other results.
• Updates or changes of the catalogue content must be discussed with the responsible
purchasing agent before they will be realized.
28th August, 2007 9
Ariba Punchout Requirements (2)Roche does not have any additional technical requirements above the Ariba specifications. However, some minimal business requirements need to be reached.• Content should be Roche specific
– Roche pricing
– Website should be limited to Roche selected articles / categories.
– Optionally: Have a preferred item page available (i.e. standards list).
• Unit of Measures
– UNUOM codes will need to be provided back in the order request.
– Please provide a list of used UNUOM to your local SE Manager.
• Classification codes
– Roche specific or UNSPSC classification codes should be provided in the PunchoutOrderMessage request.
<Classification domain="roche">30150100</Classification>
Please, provide a list of used UNSPSC codes to your local SE Manager or contact your local SE Manger for a relevant list of Roche codes.
– The index file must contain the Roche specific code (domain “roche”) : “99999999”.
28th August, 2007 10
Ariba Punchout Requirements (3)
The price mentioned in the PunchoutOrderMessage should be calculated in the following manner:
• Roche Specific Unit Price:
– Including the generic discounts according to the contract.
– Quantity Rebates
The unit price for the line item in the shopping basket should be recalculated to reflect the additional quantity rebate.
• Additional Cost (Shipping Cost, Special Charges…)
– Where possible these cost should be included in the Unit Price.
– Or they can also be ignored on the order and just specified on the invoice.
Roche has special tolerances in place for shipping and handling costs. When they are below a specific threshold the invoice will match automatically.
– Specify them as a separate line item:In this case the line item has to be referenced on the invoice.
• Total Order Discounts
– Should only be specified on the invoice.
28th August, 2007 11
Technical Messages Overview
The Roche Ariba messages will contain the standard Ariba information.
Suppliers can use some or all the information provided by Ariba to validate and authenticate the request in their system:
• PunchOutSetupRequest – send to Supplier during punch out
– Buying organization: Network ID – Mandatory to use
– Some optional fields that can be used for certain purposes:
• SelectedItem (optional for Aisle or Item level Punchout)
• ItemOut for Edit and Inspect Punchouts
• User date: UserEmail, UniqueName, Name, CompanyCode
• End user default ShipTo: addressID, City, isoCountryCode
• PunchOutSetupResponse – send from Supplier to Ariba Buyer
– Status, if request was successful and URL to Punchout site
• PunchOutOrderMessage – send from Checkout page to Ariba Buyer
– Item quantity + UnitPrice + UnitOfMeasure
– SupplierPartID + SupplierPartAuxiliaryID
– Description
– Classification (UNSPSC)
– ManufacturerPartID + ManufacturerName (optional)
– Additional inbound extrinsics (optional)
28th August, 2007 12
Punchout Introduction
Roche Punchout Requirements
Technical Overview
Test Scenarios
Documentation Overview
Contact
28th August, 2007 13
PunchOutSetupRequest (1)
How to maintain the PunchOutSetupRequest URL.
URL to receive PunchOutSetupRequest is specified
• on Ariba SN
– Configuration � Electronic Order Routing � Configure cXML Setup �
PunchOutSetupRequest URL
– Advantages:
• Suppliers will be searchable as Punchout enabled
• Suppliers can change the URL whenever they want without updating the
Punchout index files. (The URL on the Ariba SN will always be used when the
ASN sends the received PunchOutSetupRequest to the supplier.)
• or stored in the Punchout index catalog loaded into Ariba Buyer by Roche.
28th August, 2007 14
PunchOutSetupRequest (2)
Supplier site authenticates the transaction by verifying the following:
• <To> credential: DUNS Number of the supplier
And
• The supplier Shared Secret (Maintained on the ASN supplier account under:
Configuration � Electronic Order Routing � Configure cXML Setup �
Authentication Method � Shared Secret
Or
• A digital certificate configured on the ASN supplier account under:
Configuration � Electronic Order Routing � Configure cXML Setup �
Authentication Method � Certificate
28th August, 2007 15
PunchOutSetupRequest (3)
After the authentication of the supplier site:
• ASN identifies the buying organization using the:
<From> credential:
– Optionally further attributes of the requisitioner using the Ship To, Company Code, …
– Be aware of multiple Credential Domains (DUNS, NetworkID), only map the relevant
ones.
• Determines the catalog content and pricing for the requisitioner.
• Creates a unique session id for the requisitioner.
28th August, 2007 16
PunchOutSetupRequest (4)
In the next step, the punchout session will be opened:
• The supplier passes back a redirect URL to ASN, including a unique key to the session id
and / or a means to subsequently identify the Buyer Cookie and BrowserFormPost
Elements.
• The content type is content-type=text/xml.
• ItemOut: Representing the item key/supplier reference (SupplierPartID and –AuxiliaryID) in
Edit or Inspect punchouts.
• PunchOutSetupRequest operation: Either “create”, “edit”, or “inspect”.
28th August, 2007 17
End User Profile (optional)
The punchout site can maintain user profiles by:
• Using UniqueName to create end user profile “on the fly”
– Next time the end users does a punch out his profile will already exist.
• Pre-fill profile with data from SetupRequest like:
– Full Name
– Language settings
– Default ShipTo address
• Profile can be used to offer personal:
– Templates
– Favorites
– Status checks
– Offers
28th August, 2007 18
PunchOutSetupResponse
When the SetupRequest is authenticated and validated, the supplier will send a response message back to the ASN.
• The content type must be content-type=text/xml
• PunchOutSetupRequest status
– Valid request status =200 response
– Invalid request status = 500
• Message will only be visible in the Ariba Buyer log file
28th August, 2007 19
PunchOutOrderMessage
When the user submits his shopping basket, the site must return the basket with the quote to Ariba Buyer.
• Place all credential/domain as you have received them in the Order Message
– The From Credentials should reference your ASN account (see the To credentials in the Setup Request)
– The To Credentials should reference the Roche ASN account (see the From credentials in the Setup Request)
– The Sender Credentials should be the same as your From Credentials
• Use Short Name Tag in description (max. 50 characters)
• Use UNSPSC or roche Classification commodity codes (see “Classification Codes” on slide 9).
• SupplierPartAuxiliaryID can be used for
– Ordering reference (to later fulfill the order)
– Configured / bundled goods reference
– Parameters of configuration
– Restoring shopping baskets
– Specify technical information (Will be passed back to the supplier in any subsequent PunchOutSetupRequest “edit” or “inspect” sessions.)
• Unit of Measure: The UNUOM should be used.
28th August, 2007 20
Punchout Index Item
Supplier will need to provide an catalog index file over the ASN.
• Allowing the end-user to see the punchout catalog
• For Classification Code use:
– Domain “roche”: “99999999”
• Use Long Description to provide search word for the most used products.
• Use Short name to put in your company name and the word “punchout”:
– E.g. Company name - IT Hardware Punchout
• Catalog Name:
– Roche_Country_SupplierName
28th August, 2007 21
Punchout Introduction
Roche Punchout Requirements
Technical Overview
Test Scenarios
Documentation Overview
Contact
28th August, 2007 22
Punchout Test Scenarios
Several tests will need to be performed before a punchout website can be activated.
• As a first step the ASN test accounts need to be linked and the test punchout should be
implemented.
• The supplier‘s test environment should be identical to his productive environment.
• Now, the technical tests can start as described in the following slide. These tests need to
be done to ensure the functionality of the punchout.
• In a next step the purchasing agent will check the assortment, prices and the returning
commodity codes.
• After successful completion of all tests, the punchout can go live.
28th August, 2007 23
Punchout Test Scenarios
Several tests will need to be performed before a punchout website can be activated.
Supplier Test Cases:
• Buying organizations which are not set up must fail
• Wrong supplier shared Secret (password) must fail
Buyer – Supplier Test Cases:
• Request a long list of items and check performance
• Crazy clicking to buttons etc. in the Punchout Site ;-)
• Test edit and inspect functionalities
• Check the available commodity codes / UNUOM
• Process single and multiple line items
• Simultaneous connection / performance test
28th August, 2007 24
Punchout Introduction
Roche Punchout Requirements
Technical Overview
Test Scenarios
Documentation Overview
Contact
28th August, 2007 25
Documentation Overview
All mentioned documentations and more can be found on ASN (see https://service.ariba.com/Supplier.aw/).
• cXML User's Guide
• cXML Solutions Guide
• Catalog Management Guide
• Ariba Catalog Format Reference
All punchout implementations must be based on the above mentioned documents!!!
You will find additional information on the Ariba Supplier Online Portal:
https://knowledge.ariba.com/supplier_login
28th August, 2007 26
Punchout Introduction
Roche Punchout Requirements
Technical Overview
Test Scenarios
Documentation Overview
Contact
28th August, 2007 27
Contact
For punchout support please contact:
About technical issues:
About assortment and prices:
Please contact your responsible purchasing agent.
28th August, 2007 28
We Innovate Healthcare