Home

Oracle Exchange Punchout.book

1. Oracle Exchange Setup Steps Setting up your company on Oracle Exchange a On the Oracle Exchange home page click Registration a Select I want to Register a new company as an independent entity Step 1 Accept the Administrator Role whoever registers their company for the first time on Oracle Exchange is the default administrator for the company account Responsibilities include approving new user accounts for company employees and administering the Company s account on the Exchange Step 2 Company Information provide company information including address phone number etc Step 3 Exchange Payment specifies how the company will pay for charges they incur using the Exchange This information will be used to collect any transaction fees that accrue from using the Exchange Step 4 Personal Information the personal information related to the person creating the account This will be used to setup an individual user account for the company administrator in addition to the company account being created Step 5 Legal Agreement accept the Terms and Conditions of use applicable to the Exchange where the registration is occurring These are established by the Oracle Exchange Operator Step 6 Review and Submit review all the information that has been entered during the registration process Once verified submit the registration for approval by the Exchange operator 3 34 Oracle Exchange Punchout Guide Installa
2. lt DTD for element CONTRACT gt lt ELEMENT contract supplierContract buyerContract buyerContractLineNumber catalogType gt lt ATTLIST contract contractNumberIdentifier KNOWN UNKNOWN INFORMATIONAL NONE IMPLIED gt lt ELEMENT supplierContract contractNumber gt lt ELEMENT buyerContract contractNumber gt lt ELEMENT contractNumber PCDATA gt lt ELEMENT buyerContractLineNumber PCDATA gt lt ELEMENT catalogType PCDATA gt lt DTD for element ITEM gt lt ELEMENT item itemNumber itemDescription unitOfMeasure hazardClass gt lt ATTLIST item lineType GOODS SERVICES_AMOUNT SERVICES_QUANTITY IMPLIED gt lt ATTLIST item quantity CDATA 1 gt Oracle iProcurement Punchout DTDs B 5 OrderLinesDataElements did lt ELEMENT itemNumber supplierItemNumber manufacturerlItemNumber buyerItemNumber gt lt ELEMENT supplierItemNumber itemID supplierReferenceNumber gt lt ELEMENT itemID PCDATA gt lt ELEMENT supplierReferenceNumber PCDATA gt lt ELEMENT manufacturerItemNumber itemID manufacturerName gt lt ELEMENT manufacturerName PCDATA gt lt ELEMENT buyerItemNumber itemID buyerItemRevision gt lt ELEMENT buyerItemRevision PCDATA gt lt ELEMENT itemDescription PCDATA gt lt ELEMENT unitOfMeasure buyerUnitOfMeasure supplierUnitOfMeasure gt lt ELEMENT buyerUnitOfMeasure
3. lt userContact Info gt lt userCompany gt lt companyName gt Oracle lt companyName gt lt companyDUNS gt lt contactName gt lt contactPhone gt lt userCompany gt lt userName gt Green Mr Terry lt userName gt lt userInfo gt lt returnURL gt C 10 Oracle Exchange Punchout Guide PunchOutSetupRequest cXML http apl00jvm us oracle com 4634 oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping lt returnURL gt lt loginInfo gt lt body gt lt request gt PunchOutSetupRequest cXML Sample XML lt xml version 1 0 encoding ISO 8859 1 gt lt DOCTYPE cXML SYSTEM http xml cxml org schemas cXML 1 1 007 cXML dtd lt http xml cxml org schemas cXML 1 1 007 cXML dtd gt gt lt cXML version 1 1 007 xml lang en US payloadID Thu Apr 19 10 29 03 GMT 08 00 2001 timestamp Thu Apr 19 10 29 03 GMT 08 00 2001 gt lt Header gt lt From gt lt Credential domain Name gt lt Ident it y gt OEXCHANGE lt Identity gt lt Credential gt lt From gt lt To gt lt Credential domain DUNS gt lt Identity gt 015996366 lt Identity gt lt Credential gt lt To gt lt Sender gt lt Credential domain ap903sun us oracle com gt lt Identity gt 6 2 Dev env lt Identity gt lt SharedSecret gt snow lt SharedSecret gt lt Credential gt lt UserAgent gt 6 2 Dev env lt UserAgent gt lt Sender gt lt Header gt lt Reques
4. lt Credential domain DUNS gt lt Identity gt 654321 lt Identity gt lt Credential gt lt From gt lt To gt 2 12 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site lt Credential domain DUNS gt lt Identity gt 123456 lt Identity gt lt Credential gt lt To gt lt Sender gt lt Credential domain OracleExchangeUserId gt lt Identity gt buyer acme com lt Identity gt lt SharedSecret gt supplier_password lt SharedSecret gt lt Credential gt lt UserAgent gt Exchange_name lt UserAgent gt lt Sender gt lt Header gt lt Request gt lt PunchOutSetupRequest operation create gt lt BuyerCookie gt lt Extrinsic name User gt JSMITH lt Extrinsic gt lt BrowserFormPost gt lt URL gt http iprocurement company com oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping lt URL gt lt BrowserFormPost gt lt Contact gt lt Name xml lang en US gt jsmith lt Name gt lt Email gt buyer acme com lt Email gt lt Contact gt lt PunchOutSetupRequest gt lt Request gt Defining an Oracle Exchange Punchout 2 13 Steps to Perform at Your Web Site lt cXML gt Table 2 4 cXML PunchOutSetupRequest Data Elements Hement Required Type Comment lt From gt lt Credential gt Required Character Identifies the buying organization The domain attribute will be either DUNS If the company has DUNS number on Oracle Exchange the identi
5. gt searchKeywords PCDATA gt cxmlCart SYSTEM cXML dtd gt HoA 3 J H G 0H A A A A A GA O AA GA A A GA HAHAHAAH Oracle iProcurement Punchout DTDs B 3 OEXLoginRequest dtd lt ELEMENT returnURL PCDATA gt Table B 2 OEXLoginRequest did Elements Field Required Comment lt company Name gt Y Company name of iProcurement user e g Big Buyer Inc lt userName gt Y Name of iProcurement user e g Terry Green lt appUserName gt Y Oracle Application user name of iProcurement user e g tgreen lt userPhone gt N Procurement user s phone number lt userEmail gt N Procurement user s email address lt company DUNS gt N DUNS number of iProcurement company lt contactName N Contact Name for iProcurement company lt contactPhone gt N Phone number of company contact lt partySiteId gt N OracleExchange trading partner id Used only if punchout is to supplier via Oracle Exchange lt reqToken gt N Session information sent from iProcurement to Oracle Exchange that will also be sent back to iProcurement by the Exchange lt language gt N Language of the iProcurement user lt searchKeywords gt N Search keywords entered during initial search on iProcurement will be used to re execute search on Oracle Exchange lt returnURL gt Y URL that Oracle Exchange will send the LoginResponse XML document back to lt fullName gt N Full
6. lt xml version 1 0 gt lt request gt lt header version 1 0 gt lt login gt lt password gt welcome lt password gt lt login gt lt action gt SHOPPING Defining an Oracle iProcurement Punchout 3 27 lt action gt lt language gt US lt language gt lt userArea gt lt operatingUnit gt 204 lt operatingUnit gt lt shipTo gt V1 New York City lt shipTo gt lt deliverTo gt V1 New York City lt deliverTo gt lt userArea gt lt header gt lt body gt lt loginInfo gt lt exchangeInfo gt lt exchangeName gt Oracle lt exchangeName gt lt exchangeInfo gt lt userInfo gt lt userContactInfo gt lt userPhone gt lt userEmail gt tgreen vision com lt userEmail gt lt userContact Info gt lt userCompany gt lt companyName gt Oracle lt companyName gt lt companyDUNS gt lt contactName gt lt contactPhone gt lt userCompany gt lt userName gt Green Mr Terry lt userName gt lt userInfo gt lt returnURL gt http iprocurement oracle com oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping 3 28 Oracle Exchange Punchout Guide lt returnURL gt lt loginInfo gt lt body gt lt request gt Note The DTDs are described in detail in the Appendix A of this document Some additional optional user data can also be sent to Oracle Exchange if the punchout was setup in iProcurement to send it The samp
7. request lt ELEMENT request smessage gt gt lt request dtd can instantiate the request element and the response dtd can instantiate the response element gt lt ENTITY response lt ELEMENT response message gt gt lt see request entity gt lt ELEMENT header requestID login action return cookies language userArea gt A 2 Oracle Exchange Punchout Guide POMXMLRR DTD lt an opti a reque login i relavan request gt lt ATTLI lt lt ELE lt ATT lt ELE lt ELE lt ELE lt ELE lt ENTI Ssessi lt ELE E A oO H oA eE A A a eA lt ELEMENT lt ENTIT lt to retu entity header contains onal requestID which is a sequence number to match st and a response in an asynchronous communication an optional login info since a response doesn t have to send back any nfo action indicating what the request is about optional cookies the response can set some info that may not be t to the client agent but must be passed back in the subsequent s This is modeled after the cookies in the http protocol returnStatus return status from the response language the preferred language of the user userArea user specific information ST header version CDATA REQUIRED gt version of the particular dtd being used gt T requestID PCDATA gt requestID to match the response with the corresponding request in case chro
8. url openConnection InputStream urlinstr urlConnection getInputStream dp parseDTD urlinstr rootElementName International Support At this time only American English XML is supported The XML language tag lt language code gt is not used Also only UTF 8 character encoding is supported as in the following example lt xml version 1 0 encoding UTF 8 gt Step 3 Create a URL to accept incoming punchout documents You must create a URL to accept the incoming XML Punchout Request or the cXML PunchOutSetupRequest transaction sent from Exchange The Exchange will establish a server to server communication with this URL and send the request using the HTTP protocol Your URL will need to receive the HTTP Post punchout document parse it against the appropriate dtd to ensure that the document is well formed construct an XML Punchout Response or a cXML PunchOutSetup Response document and post this back to the Exchange via HTTP post 2 8 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site Using a secure connection To provide the necessary security we recommend that you create an HTTPS page to handle this request Digital certificates for the creation of an HTTPS site can be obtained from a certification authority such a Verisign at http www verisign com Note Although you can use an HTTP page for your web catalog portal HTTP does not provide a secure connection Since password infor
9. Punchout Supplier Yes The name of the supplier that will be displayed on the iProcurement home page and in search results during searches performed by iProcurement users example Supplier Web Store Defining an Oracle iProcurement Punchout 3 39 Installation Implementation Steps Table 3 2 Direct Punchout Setup Field Name Required Description Description No Displayed on the external supplier directory page in iProcurement Only visible when a user requests a list of all external suppliers example The Big Business Supplier URL Yes The URL that iProcurement will use to login to the supplier site It should include not only the URL but the program name that will receive and process the login request from iProcurement example http www suppliersite com buyerLogin jsp Image URL No Optional field to specify the web address of the Supplier s logo example http www suppliersite com logo gif Company Name Yes The Company name or user id the supplier will validate during setup of the punchout The supplier you are setting up a punchout with should provide the value Password Yes The password for the company name provided above This will be used as a site level password at the supplier site The supplier you are setting up a punchout with should provide the value Retype Password Yes Retype the password Keywords No Any words entered in this field will be included when an iProcurement us
10. Topics in this chapter include n n Model 2 Punch out from Oracle iProcurement to Oracle Exchange XML Model 3 Punch out from Oracle iProcurement to Supplier via Oracle Exchange XML Model 4 Punch out from Oracle iProcurement to Supplier via Oracle Exchange cXML Model 5 Punch out from Oracle iProcurement directly to Supplier XML Installation Impelmentation Steps Oracle Exchange Setup Steps Oracle iProcurement Setup Steps Oracle eCommerce Gateway Setup Steps Model 2 Punch out from Oracle iProcurement to Oracle Exchange XML An Oracle Exchange is setup as a punchout or external supplier hub in iProcurement and the Oracle Exchange link is displayed on the iProcurement homepage This enables iProcurement users to punch out to Oracle Exchange fill a shopping cart with requisition items and return the cart to iProcurement for approval routing and purchase order creation Defining an Oracle iProcurement Punchout 3 1 Setup iProcurement Buying Organization as Buyer on Oracle Exchange Before an iProcurement adminstrator can setup a punchout to Oracle Exchange they must first register their organization on Oracle Exchange This registration process will provide company and user accounts and a password which are required to setup the punchout process Refer to the Oracle Exchange you want to participate on for details on the registration requirements Setup Supplier on Oracle Exchange The iProcurement buying orga
11. error U unexpected W warning A requires authentication lt operatingUnit gt N Part of the lt userArea gt this is the iProcurement user s operating unit lt shipTo gt N Part of the lt userArea gt this is the iProcurement user s Ship to location lt deliverTo gt N Part of the lt userArea gt this is the iProcurement user s Deliver to location OEXLoginRequest dtd lt gt lt ELE lt ELE lt ELE partys searc lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE lt ELE n Header OEXLoginRequest dtd 115 0 2001 02 03 00 57 04 skaushik noship ENT common SYSTEM pomxmlrr dtd gt ENT body SYSTEM lt ELEMENT body loginRequest gt gt ENT loginRequest companyName userInfo companyInfo userArea iteId reqToken language eywords cxmlCart returnURL gt T companyName PCDATA gt T userInfo userName appUserName userContactInfo gt T userName PCDATA gt T appUserName PCDATA gt T userContactInfo userPhone userEmail gt T userPhone PCDATA gt T userEmail PCDATA gt companyInfo companyDUNS contactName contactPhone gt companyDUNS PCDATA gt contactName PCDATA gt contactPhone PCDATA gt userArea ANY gt partySitelId PCDATA gt reqToken PCDATA gt language PCDATA
12. request gt LoginResponse Sample XML lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt LOGIN_RESPONSE lt action gt lt header gt lt body gt lt loginInfo gt lt loginURL gt http ap904sun us oracle com 6250 orders LinkinCallback jsp sessionId 3fe0a73f6 falc003 164 982359182161 amp action shopping lt loginURL gt lt loginInfo gt lt body gt lt response gt OrderLinesDataElements Sample XML lt xml version 1 0 encoding ISO 8859 1 gt lt response gt lt header gt lt action gt SHOPPING_RESPONSE lt action gt lt header gt Sample Oracle iProcurement XML Documents C 5 OrderLinesDataElements lt body gt lt OrderLinesDataElements gt lt catalogTradingPartner gt OracleExchange lt catalogTradingPartner gt lt orderLine gt lt contract gt lt catalogType gt CONTRACTED lt catalogType gt lt contract gt lt item lineType GOODS quantity 1 0 gt lt itemNumber gt lt supplierItemNumber gt lt itemID gt kb_Item2 lt itemID gt lt supplierItemNumber gt lt itemNumber gt lt itemDescription gt Item 2 kbenjami list TBD b s lt itemDescription gt lt unitOfMeasure gt lt buyerUnitOfMeasure gt lt supplierUnitOfMeasure gt lt supplierUOMType gt Bushel lt supplierUOMType gt C 6 Oracle Exchange Punchout Guide OrderLinesDataElements lt supplierUOMQuantity gt lt supplierUOMQuanti
13. validation process a session should have been created that will be used to identify the user and this session should be incorporated into this URL e g www mysite com s essionID 123 cXML PunchOutSetupResponse document example An example cXML PunchOutSetupResponse file is shown below lt xml version 1 0 gt lt cXML payloadID 2000 08 15 timestamp 2000 08 15 gt lt Response gt lt PunchOut SetupResponse gt lt StartPage gt lt URL gt http www oracle com orders SupplierShopping jsp sessionID 123 lt URL gt lt StartPage gt lt PunchOut SetupResponse gt lt Status code 200 text success gt lt Response gt 2 16 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site lt cXML gt Table 2 7 cXML PunchOutSetupResponse Data Elements Element Required Type Comment lt StartPage gt lt URL gt Required Character This is the URL to which the Exchange user will be directed on your web catalog As part of the validation process a session should have been created that will be used to identify the user and this session should be incorporated into this URL e g www mysite com sessionI D 123 For DTD information on the cXML transaction above see http www cXML org Ideally your portal should create an individual session through which the buyer will access your site This method ensures that the buyers connection is secure because the session will be closed as so
14. 2 1 Oracle Native XML and cXML Transaction Names Oracle Native XML Name cXML Name XML Punchout Request PunchOutSetupRequest XML Punchout Response PunchOutSetupResponse XML Punchout Shopping Cart PunchOutOrderMessage The XML dtd specifications used for validating the Oracle Native XML transactions are included in Appendix B You can download the DTD specifications for the cXML transactions from http www cXML org Defining an Oracle Exchange Punchout 2 7 Steps to Perform at Your Web Site Either way you must ensure the appropriate dtd s are used when parsing the inbound transaction and generating the outbound transactions To create the appropriate dtd files 1 Ifusing the Oracle Native XML protocol create a file for each of the dtd examples described in Appendix B You can create these files using Notepad or another text editor but save the files with an extension of dtd If using the cXML protocol download the specifications for each transaction and create the corresponding dtd The cXML specifications can be downloaded at http www cXML org 2 Place the dtd files in the directory required by your particular XML parser For example if you store the dtd for the inbound XML Punchout Request in the etc templates directory as file punchreq dtd the Java code to parse the incoming request may include the following url new URL file localhost etc templates punchreq dtd urlConnection
15. Define Code Conversion Values Category Here you can choose from a host of values like Item Categories UOM and Currency a All Item Categories must be mapped between the supplier and iProcurement Without mapping the requisition will fail validation See the example below Description Enter the description of the mapping Direction Enter the direction as IN or BOTH Use IN direction if there are more than one supplier code values to map into one value of Oracle Purchasing codes Key 1 Enter OracleExchange if this mapping is for a punchout to Oracle Exchange Enter the supplier name if the punchout is to a supplier Key 2 through Key 5 and External 2 through External 5 are not used Internal Oracle Purchasing codes values External Values Supplier side codes values See the Oracle eCommerce Gateway User s Manual for more details Code conversion examples Table 3 3 Category Direction Key1 Internal Value External 1 ITEM_ IN Catalog Trading Partner Internal category External category CATEGORY code i e code forexample code for example OracleExchange or MISC MISC Bond Paper supplier name if catalog trading partner code does not exist Defining an Oracle iProcurement Punchout 3 43 Installation Implementation Steps Table 3 3 Category Direction Key1 Internal Value External 1 UOM IN Catalog Trading Partner Internal UOM External UOM code code i e OracleExchange or supplier name if cat
16. Elements Field Required Type Comment lt action gt Not currently Character Reserved for future used development Table 2 11 XML Punchout Shopping Cart Body Data Elements Field Required Type Comments lt item quantity gt Optional Number Default 1 Decimals are allowed lt supplierltemNumber Conditionally Character Supplier s internal item optional number 2 22 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site Table 2 11 XML Punchout Shopping Cart Body Data Elements Field Required Type Comments lt itemID gt Optional Character If this item is a configured item you may wish to use this field to provide a unique reference to the configuration that the buyer has selected This will allow you to identify the exact configuration that was originally selected The maximum length of this field is 25 characters lt manufacturerItemNumber gt Optional Character Manufacturer s part number lt manufacturerName Optional Character Manufacturer s name lt itemDescription gt Conditionally Optional Character Description of item If this is a configuration item this field can be optionally used to describe the components of the configuration The maximum length of this description is 240 characters lt supplierUOMType gt Conditionally Operational Character This is the Unit of Measure code that is us
17. Exchange members and Oracle iProcurement users on that exchange can use this punchout definition to access that supplier directly Using the punchout capability provides the following Exchange members have access to a broader range of potential products and services not just products whose information is stored locally on the exchange a Self service requisitioners within a buying organization are able to search on both the exchange and supplier sites for products which meet their requirements while Purchasing Managers can control contract leakage be ensuring that only items from approved suppliers are purchased Suppliers can utilize the large customer base existing within an Oracle Exchange to increase the exposure for their products while reducing their configuration and maintenance effort A supplier can define a punchout once and all members accessing this exchange can use this punchout definition to access the suppliers catalogs Punchout Benefits Products which are configurable or include highly variable or dynamic pricing are difficule to maintain within a static hosted catalog environment These types of items are particularly well suited to a punchout as this allows the supplier to control the configuration and pricing Catalogs which are continually changing are costly and time consuming to maintain in a hosted environment These types of catalogs are more accurately maintained by the supplier to ensure that the latest ca
18. PCDATA gt lt ELEMENT supplierUnitOfMeasure supplierUOMType supplierUOMQuantity gt lt ELEMENT supplierUOMType PCDATA gt lt ELEMENT supplierUOMQuantity PCDATA gt lt ELEMENT hazardClass PCDATA gt lt DTD for element CATEGORY gt lt ELEMENT category categoryCode gt lt ELEMENT categoryCode PCDATA gt lt ATTLIST categoryCode categoryCodeIdentifier SPSC SUPPLIER BUYER IMPLIED gt lt DTD for element PRICE gt lt ELEMENT price currency unitPrice gt lt ELEMENT currency PCDATA gt lt ELEMENT unitPrice PCDATA gt lt DTD for element SUPPLIER gt lt ELEMENT supplier supplierDUNS supplierTradingPartnerCode supplierName contactName contactPhone gt lt ELEMENT supplierDUNS PCDATA gt lt ELEMENT supplierTradingPartnerCode PCDATA gt lt ELEMENT supplierName PCDATA supplierSite gt lt ELEMENT supplierSite PCDATA gt lt ELEMENT contactName PCDATA gt lt ELEMENT contactPhone PCDATA gt lt DTD for element ADDITIONAL ATTRIBUTES gt lt ELEMENT additionalAttributes attributel attribute2 attribute3 attribute4 attribute5 attribute6 attribute7 attribute8 attribute9 attributel0 attributell attributel2 B 6 Oracle Exchange Punchout Guide OrderLinesDataElements ditd attributel3 attributel4 attributel5 gt lt ELEMENT attributel PCDATA gt lt ELEMENT attribute2 PCDATA
19. a disabled Oracle Exchange punchout 2 31 Returning punchout users to Oracle Exchange 2 19 Returning punchout users to Oracle Exchange code example 2 19 Revoking an Oracle Exchange punchout 2 30 U Using a punchout from Oracle Exchange 2 1 X XML Punchout Request document example 2 10 XML Punchout Response for errors document example 2 17 XML Punchout Response document example 2 15 XML Punchout Shopping Cart document example 2 20 Index 2
20. at Your Web Site Table 2 3 XML Punchout Request Body Data Elements Field Required Type Comment lt exchangeName gt Optional Character This is the name of the Exchange from which the punchout was initiated lt userName gt Required Character Buyer s username on the Exchange lt userPhone gt Optional Number Buyer s contact phone number lt userEmail gt Optional Character Buyer s email address lt companyName gt Optional Character Buyer s company name lt company DUNS gt Optional Number Buyer s DUNS number lt contactName gt Optional Character The buyer company administrator name lt contactPhone gt Optional Character The buyer company administrator phone number lt retumURL gt Required Character This is the URL to which your site will pass the shopping cart XML document when the user exits from your web catalog lt searchKeywords gt Optional Character If this user searched for a particular set of keywords prior to this punchout these keywords will be included here cXML PunchOutSetupRequest document example An example cXML PunchOutSetupRequest is shown below lt xml version 1 0 encoding ISO 8859 1 gt lt DOCTYPE cXML SYSTEM http xml cxml org schemas cXML 1 1 007 cXML dtd gt lt cXML version 1 1 007 xml lang en US payloadID Wed Apr 04 12 52 46 GMT 08 00 2001 timestamp Wed Apr 04 12 52 46 GMT 08 00 2001 gt lt Header gt lt From gt
21. computer software and use duplication and disclosure of the Programs including documentation shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement Otherwise Programs delivered subject to the Federal Acquisition Regulations are restricted computer software and use duplication and disclosure of the Programs shall be subject to the restrictions in FAR 52 227 19 Commercial Computer Software Restricted Rights June 1987 Oracle Corporation 500 Oracle Parkway Redwood City CA 94065 The Programs are not intended for use in any nuclear aviation mass transit medical or other inherently dangerous applications It shall be the licensee s responsibility to take all appropriate fail safe backup redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes and Oracle Corporation disclaims liability for any damages caused by such use of the Programs Oracle is a registered trademark and Enabling the Information Age and Oracle Exchange are trademarks or registered trademarks of Oracle Corporation Other names may be trademarks of their respective owners Contents Send US Your Comments 200 0 ccc ccsccscccccssescesessesscsscssesesessessessssssstssesssseesnssessessesesseaees vii POT ACO ro isha attain ETAETA E chat ONE EEA AEE A Manatees ix Uribe SGA LCT Cee coicn a uae oe eas Tap Sees cus daa Be EE A D E T Tadeo coe ix SIA H DE rb
22. does not involve Oracle iProcurement a Model 2 Punch out from Oracle iProcurement to Oracle Exchange XML Defining an Oracle iProcurement Punchout 3 31 Installation Implementation Steps a Model 3 Punch out from Oracle iProcurement to Supplier via Oracle Exchange XML a Model 4 Punch out from Oracle iProcurement to Supplier via Oracle Exchange cXML a Model 5 Punch out directly to Supplier XML In the following section each scenario is described in more detail and includes a list of the setup processes to complete to make it work The setup processes are detailed in the subsequent section Model 2 Punch out from Oracle iProcurement to Oracle Exchange XML When you setup a punchout from iProcurement to Oracle Exchange it allows iProcurement users to search and fill a shopping cart with catalog items hosted on an Oracle Exchange When the authenticated iProcurement user punches out to Oracle Exchange an XML document is sent with the user s company details to Oracle Exchange The company information sent from iProcurement is the same as the company defined in Oracle Exchange A proxy user with a certain profile is attached to this company in Oracle Exchange and the iProcurement user by default inherits the proxy user s job functions on the Exchange This enables the iProcurement administrator to restrict the types of activities an iProcurement user can actually perform on Oracle Exchange In most cases the iProcurement
23. gt lt ELEMENT attribute3 PCDATA gt lt ELEMENT attribute4 PCDATA gt lt ELEMENT attribute5 PCDATA gt lt ELEMENT attribute6 PCDATA gt lt ELEMENT attribute7 PCDATA gt lt ELEMENT attribute8 PCDATA gt lt ELEMENT attribute9 PCDATA gt lt ELEMENT attributel0 PCDATA gt lt ELEMENT attributell PCDATA gt lt ELEMENT attributel2 PCDATA gt lt ELEMENT attributel3 PCDATA gt lt ELEMENT attributel4 PCDATA gt lt ELEMENT attributel5 PCDATA gt Table B 4_ OrderLinesDataElements dtd Elements Field Required Comment lt catalogTradingPartner N The catalog trading partner is used for catalog hosting gt service websites such as TPN or another Exchange It is used to determine which items category mapping should be used within Oracle iProcurement when bringing items into Oracle iProcurement This element should not normally be populated for a punchout to a supplier site lt contract gt N Identifies the beginning of the contract section contains the attribute contractNumberldentifier with possible values KNOWN UNKNOWN INFORMATIONAL or NONE lt contractNumber gt N Supplier or buyer contract number depending on the parent tag lt buyerContractLineNu N Line number of buyer s contract if it exists mber gt lt catalogType gt N Specifies whether or not this is from a contract catalog or non contract catalog lt ite
24. have any other suggestions for improvement please indicate the document title and part number and the chapter section and page number if available You can send comments to us in the fol lowing ways Electronic mail richard sears us oracle com FAX 650 506 7816 Attn Oracle Exchange Postal service Oracle Corporation Oracle Exchange Documentation 300 Oracle Parkway 30P16 Redwood Shores CA 94065 USA If you would like a reply please give your name address telephone number and optionally electronic mail address If you have problems with the software please contact your local Oracle Support Services vii viii Preface This manual describes how to use the punchout capability of Oracle Exchange to provide Exchange members and iProcurement users punchout access to supplier hosted catalogs Intended Audience Structure This manual is intended for suppliers who wish to set up punchout access to their local catalogs and iProcurement managers who wish to enable and control punchout capability from an iProcurement instance This manual describes the following Chapter 1 Using Oracle Exchange Punchouts This chapter explains punchout technology and describes the different punchout models and the benefits of each Chapter 2 Defining an Oracle Exchange Punchout This chapter describes the Oracle Exchange to supplier punchout model and explains the process a supplier uses to implement this type of punc
25. lt operatingUnit gt lt shipTo gt V1 New York City lt shipTo gt lt deliverTo gt V1 New York City lt deliverTo gt lt fullName gt Green Mr Terry lt fullName gt lt title gt MR lt title gt lt manager gt Baker Ms Catherine lt manager gt lt managerEmail gt chaker vision com lt managerEmail gt lt location gt Sample Oracle iProcurement XML Documents C 3 OEXLoginRequest with optional extended data V1 New York City lt location gt lt language gt US lt language gt lt currency gt USD lt currency gt lt dateFormat gt DD MON RRRR lt dateFormat gt lt userArea gt lt header gt lt body gt lt loginRequest gt lt userInfo gt lt userName gt Green Mr Terry lt userName gt lt appUserName gt TGREEN lt appUserName gt lt userContactInfo gt lt userEmail gt tgreen vision com lt userEmail gt lt userContact Info gt lt userInfo gt lt companyInfo gt lt companyName gt IP lt companyName gt lt companyInfo gt lt reqToken gt template tpn _action addToOrder _function addToOrder _reqSessionId 0 _ reqHeaderId 0 _emergencyReq N _itemSourcelId 1001 lt reqToken gt lt returnURL gt http apl00jvm us oracle com 4632 oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping C 4 Oracle Exchange Punchout Guide OrderLinesDataElements lt returnURL gt lt loginRequest gt lt body gt lt
26. lt SupplierPartID gt 5555 lt SupplierPartID gt lt ItemID gt lt ItemDetail gt lt UnitPrice gt lt Money currency USD gt 763 20 lt Money gt lt UnitPrice gt lt Description xml lang Yon gt Leather reclining chair lt Description gt lt UnitOfMeasure gt EA lt UnitOfMeasure gt Defining an Oracle Exchange Punchout 2 25 Steps to Perform at Your Web Site lt Classification domain UNSPSC gt 513333 lt Classification gt lt ItemDetail gt lt ItemIn gt lt PunchOutOrderMessage gt lt Message gt lt cXML gt Table 2 12 cXML PunchOutOrderMessage Data Elements Element Required Type Comment lt SupplierPartID gt Required Character 25 This is a unique item reference number which can be used to identify the item or item configuration lt SupplierPartAuxillaryID gt Not used This element is not used by the Exchange It is therefore necessary to pass a unique reference within the lt SupplierPartID gt element Note For DTD details on the cXML transaction above see http www cXML org Note For configured items such as a laptop PC it is recommended that you return a single line in the shopping card which represents the entire configura tion You must provide enough information to ensure that the correct configu ration will be shipped to the buyer and allow the buyer to identify the item This can be achieved using the information conta
27. name of iProcurement user as stored from iProcurement user record lt title gt N Title of iProcurement user lt manager gt N Name of iProcurement user s manager as stored in iProcurement lt managerEmail gt N iProcurement user s manager s email address lt location gt N Location of iProcurement user from HR information lt currency gt N Currency of iProcurement user lt dateFormat gt N Date format of iProcurement user B 4 Oracle Exchange Punchout Guide OrderLinesDataElements did LoginResponse dtd lt Header LoginResponse dtd 115 0 2001 02 02 01 12 45 mahmad noship gt lt ENTITY common SYSTEM pomxmlrr dtd gt lt ENTITY oracle SYSTEM OrderLinesDataElements dtd gt lt ENTITY body lt ELEMENT body loginInfo gt gt lt ELEMENT loginInfo loginURL gt lt ELEMENT loginURL PCDATA gt Scommon Sresponse Soracle Table B 3 LoginResponse dtd Elements Field Required Comment lt loginURL gt Y URL that the user is re directed to on Oracle Exchange for shopping supplier sync up OrderLinesDataElements dtd lt Header OrderLinesDataElements dtd 115 0 2001 02 02 01 14 01 mahmad noship gt lt OrderLinesDataElements dtd gt lt ELEMENT OrderLinesDataElements catalogTradingPartner orderLine gt lt ELEMENT catalogTradingPartner PCDATA gt lt ELEMENT orderLine contract item category price supplier additionalAttributes gt
28. sent back in the OrderLinesDataElements XML document which is url encoded OrderLinesDataElements sample lt xml version 1 0 encoding ISO 8859 1 gt lt response gt lt header gt lt act ion gt SHOPPING_RESPONSE lt action gt lt header gt lt body gt lt OrderLinesDataElements gt lt catalogTradingPartner gt OracleExchange lt catalogTradingPartner gt lt orderLine gt lt contract gt lt catalogType gt CONTRACTED lt catalogType gt lt contract gt lt item lineType GOODS quantity 1 0 gt lt itemNumber gt lt supplierItemNumber gt lt itemID gt kb_Item2 lt itemID gt lt supplierItemNumber gt lt itemNumber gt lt itemDescription gt Item 2 kbenjami list TBD b s lt itemDescription gt lt unitOfMeasure gt lt buyerUnitOfMeasure gt lt supplierUnitOfMeasure gt lt supplierUOMType gt Bushel lt supplierUOMType gt lt supplierUOMQuantity gt lt supplierUOMQuantity gt lt supplierUnitOfMeasure gt lt unitOfMeasure gt lt item gt lt category gt lt categoryCode categoryCodeldentifier SPSC gt Ball Point Pens lt categoryCode gt lt category gt lt price gt 3 30 Oracle Exchange Punchout Guide Installation Implementation Steps lt currency gt USD lt currency gt lt unitPrice gt 100 0 lt unitPrice gt lt price gt lt supplier gt lt supplierDUNS gt 2820 lt supplierDUNS gt lt supplierName gt Kareem s Corporation lt supplierN
29. to use as a supplier hub must first be setup in Procurement For details on the setup required refer the implementation and installation section later in this document Setup Punchout Suppliers from Oracle Exchange in iProcurement The iProcurement administrator logs on to iProcurement and initiates the process of setting up suppliers they want to enable for punchout Procurement executes PunchOutServlet which first establishes a secure connection with Oracle Exchange Once established PunchOutServlet then generates the OEXLoginRequest XML document and sends it to 3 16 Oracle Exchange Punchout Guide Oracle Exchange After the iProcurement user is authenticated on Oracle Exchange their browser is re directed to Oracle Exchange using the login URL provided in the LoginResponse XML The iProcurement administrator selects the punchout suppliers they want to enable in Procurement Oracle Exchange sends the suppliers setups to iProcurement in the SupplierSyncUpResponse XML document iProcurement then executes PunchOutServlet that creates all the supplier punchout related setups in iProcurement Part of this setup process includes the download of keywords the supplier has associated with their company during their setup on Oracle Exchange The first time a supplier is setup in Procurement these keywords will be downloaded into iProcurement The iProcurement customer can keep these keywords or change them to meet their o
30. was set during configuration of the punchout for this supplier then the user will not be able to make any changes to the item returned from the supplier The requisition then goes through the normal workflow and approval processes configured in iProcurement Note See the Installation and Setup section for details on setting the lock_item_flag and using the EDI setups to create data maps Model 5 Punch out from Oracle Procurement directly to Supplier XML A supplier is setup as a punchout or external supplier in Procurement and the supplier site link is displayed on the iProcurement homepage This allows iProcurement users to punch out to a supplier s web store fill a shopping cart with requisition items and return the cart to iProcurement for approval routing and purchase order creation Defining an Oracle iProcurement Punchout 3 25 This model has been supported in Oracle iProcurement since patch H and has been re architected in patch J The old model however continues to be supported as well The new architecture is described below Setup Supplier as a Punchout external supplier in iProcurement The supplier you want to punch out to must first be setup in Procurement For details on the setup required refer the implementation and installation section later in this document Punchout Process When a user clicks the link to the supplier the PunchOutServlet servlet is executed If required this
31. will first call Oracle SSL APIs to establish a secure connection to the supplier site These APIs request a Certification Authority Certificate from the supplier site and compare that to Certificates stored in iProcurement After a secure connection between iProcurement and the supplier is established PunchOutServlet then generates the SupplierLoginRequest XML document which contains user details and login credentials for the supplier site and a return URL Once generated this is passed to the supplier through the secure connection The supplier can authenticate the iProcurement user Once authenticated the supplier must generate the LoginResponse XML document that is returned to iProcurement After successfully establishing a secure connection and authenticating the iProcurement instance the iProcurement user s browser is re directed to the supplier s site using the login URL provided by the supplier in the LoginResponse XML document The user is then allowed to search and add items to a shopping cart on the supplier site After the user finishes adding items to their shopping cart the supplier must create the OrderLinesDataElements XML document which contains the shopping cart items added from their site This is posted to the return URL on the iProcurement server using the oracleCart parameter iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups
32. 00 text success gt lt Response gt lt cXML gt 4 The PunchOutSetupResponse is returned to the LinkinLogin jsp on Oracle Exchange Oracle Exchange then uses the LinkinMainBean java class to generate the 3 22 Oracle Exchange Punchout Guide LoginResponse XML and sends it back to iProcurement using the return URL The XML document contains the session aware URL which iProcurement user will use to connect to the supplier site LoginResponse XML sample lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt LOGIN_RESPONSE lt action gt lt header gt lt body gt lt loginInfo gt lt loginURL gt http www suppliersite com orders LinkinCallback jsp sessionid 3fe0a73f6falc003 164 982359182161 action shopping lt loginURL gt lt loginInfo gt lt body gt lt response gt 5 Using the session aware login URL provided in the LoginResponse XML iProcurement executes the PunchOutServlet which redirects the iProcurement user s browser to the login URL provided by the supplier The user is allowed to search and add items to their shopping cart on the supplier site 5 When the user finishes adding items to their cart on the supplier site the items in the shopping cart are sent back to iProcurement by posting a form to the return URL received from iProcurement during the initial punchout The parameter for the post should be cxml u
33. 3 lt Classification gt lt ItemDetail gt lt ItemIn gt lt PunchOutOrderMessage gt lt Message gt lt cXML gt 3 24 Oracle Exchange Punchout Guide Note See Appendix A for DTD of the shopping cart sent back from the supplier to iProcurement See Appendix B for a sample XML document shopping cart sent back from the supplier to Procurement 6 The cxml urlencoded parameter used to post the shopping cart lets iProcurement know this is a cXML shopping cart Since iProcurement cannot process the PunchOutOrderMessage cXML document PunchOutServlet receives and re directs the shopping cart to Oracle Exchange The PunchOutServlet establishes a secure and trusted connection with the Exchange then it forwards the cXML shopping cart 7 Oracle Exchange executes PunchoutMainBean and ExportOrder which convert the shopping cart from cXML to XML and also do the code conversions UOM and currency defined on the Oracle Exchange This shopping cart is then returned to iProcurement through the secure connection 8 iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups in Oracle Applications are referenced to do the required data conversion mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement If the lock_item_flag stored in the ICX_ POR_ITEM_SOURCES table
34. CDATA REQUIRED gt lt version of the particular dtd being used gt lt ELEMENT requestID PCDATA gt lt ELEMENT login username password Session gt lt user name and password or the session details gt lt ELEMENT action PCDATA gt lt action required from the request gt lt ELEMENT cookies cookie gt lt cookies set from response see header element for more info gt lt ELEMENT cookie PCDATA gt lt ATTLIST cookie name CDATA REQUIRED gt lt ELEMENT language PCDATA gt lt ELEMENT userArea ANY gt lt ELEMENT username PCDATA gt Oracle iProcurement Punchout DTDs B 1 Common DTD file for all Request Response DTDs pomxmrr dtd lt ELE lt ENT SSeSs lt ELE lt lt ELE lt ENT lt to re entit Sretu lt ATT Sbody ENT password PCDATA gt ITY session lt ELEMENT session sessionID gt gt ion ENT sessionID PCDATA gt any additional user information can be passed in this element gt ENT return returnMessage gt ITY returnMessage lt ELEMENT returnMessage PCDATA gt gt returnMessage is made an entity so that if a specific response desires turn multiple messages or an xml document itself it can override this y gt rnMessage LIST return returnCode S E U W A REQUIRED gt 1 Table B 1 pomxmirr dtd Elelments Field Required Comment lt requestID gt N A
35. Email gt lt userContact Info gt lt userCompany gt lt companyName gt 2 10 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site Buying Corporation lt companyName gt lt companyDUNS gt lt contactName gt JSMITH lt contactName gt lt contact Phone gt 800 123 4567 lt contactPhone gt lt userCompany gt lt userInfo gt lt returnURL gt http ap903sun us oracle com 6290 orders PunchoutCallback jsp app buying lt returnURL gt lt loginInfo gt lt searchKeywords gt paper pens lt searchKeywords gt lt body gt lt request gt Table 2 2 XML Punchout Request Header Data Elements Field Required Type Comment lt username Required but not used Character Not currently used Reserved for Can be empty future development lt password gt Required Character This is the password into your web catalog which your site must validate Note that every user on the Exchange will provide the same password there is no need to register individual accounts on your web site For details on where you register this password see Define your link information to Exchange later in this chapter lt action gt Constant SHOPPING lt language gt Required Character This is the ISO language preference of the user for browsing The XML document itself only supports American English for character sets and number formats Defining an Oracle Exchange Punchout 2 11 Steps to Perform
36. Exchange their browser is re directed to Oracle Exchange using the login URL provided in the LoginResponse XML The iProcurement administrator selects the punchout suppliers they want to enable in iProcurement Oracle Exchange sends the suppliers setups to iProcurement in the SupplierSyncUpResponse XML document iProcurement then executes PunchOutServlet which creates all the supplier punchout related setups in iProcurement Part of this setup process includes the download of keywords the supplier has associated with their company during their setup on Oracle Exchange The first time a supplier is setup in Procurement these keywords will be downloaded into iProcurement The iProcurement customer can keep these keywords or change them to meet their own user s needs This information is not downloaded from Oracle Exchange again Additional setup information maintained by the supplier on Oracle Exchange such as their punchout URL and site level user id and password will remain on the Exchange This is referenced each time a punchout occurs so the iProcurement administrator does not have to maintain any supplier specific login details themselves 3 8 Oracle Exchange Punchout Guide Punchout Process The supplier is automatically setup in Oracle iProcurement as a punchout supplier in the above step and the Supplier s link is displayed on the iProcurement homepage When a user clicks the link to a supplier the PunchOu
37. If the lock_item_flag stored in the ICX_ POR_ITEM_SOURCES table was set during configuration of the punchout for this supplier then the user will not be able to make any changes to the item returned from the supplier The requisition then goes through the normal workflow and approval processes configured in iProcurement Note See the Installation and Setup section for details on setting the lock_item_flag and using the EDI setups to create data maps Model 4 Punch out from Oracle Procurement to Supplier via Oracle Exchange cXML Oracle iProcurement users can also punch out to a cXML supplier through Oracle Exchange Oracle Exchange simplifies the initial setup process as well as the authentication and maintenance of the punchout To punch out to a supplier through the Exchange the iProcurement customer must setup Oracle Exchange as a supplier hub in iProcurement and their suppliers must setup a punchout from Oracle Exchange to their web store Setup Suppliers on Oracle Exchange The suppliers can setup their punchout definitions one time on Oracle Exchange Then an iProcurement administrator can download these definitions which will automatically setup the punchout from iProcurement to that supplier Note See the chapter Defining an Oracle Exchange Punchout for details on setting up a supplier for punchout from an Oracle Exchange Setup Oracle Exchange as a Supplier Hub in iProcurement The Oracle Exchange
38. NAL lt ELEMENT lt ELE lt ELE lt ELE lt ELE ENT ENT lt ELEMEN itemNumber i NONE ENT buyerContract ENT buyerContractLineNumber inesDataElements catalogTradingPartner orderLine gt gTradingPartner PCDATA gt rLine category price supplier additionalAttributes gt ntract supplierContract uyerContractLineNumber catalogType gt contract contractNumberIdentifier KNOWN IMPLIED gt supplierContract contractNumber gt contractNumber gt PCDATA gt PCDATA gt UNKNOWN contractNumber catalogType PCDATA gt item lt ATTLIST i GOODS gt lt ATTLIST i lt ELEMENT buyerItemNumber lt ELEME lt ELE lt ELE lt ELE lt ELE lt ELEME lt ELE lt ELE lt ELE supplierUnitOfMeasure gt lt ELEME lt ELEME supplierUOMQuant lt ELEMENT supplierUOMType lt ELEMENT supplierUOMQuanti lt ELEMENT hazardClass mDescription unitOfMeasure hazardClass gt tem lineType GOODS SERVICES_AMOUNT SERVICES_QUANTITY tem quantity CDATA 1 gt itemNumber supplierItemNumber manufacturerItemNumber gt H supplierItemNumber itemID supplierReferenceNumber gt T itemID PCDATA gt T supplierReferenceNumber PCDATA gt T manufacturerItemNumber itemID manufacturerName gt T manufacturerName PCDATA gt buyerItemNumber itemID buyerItemRevision
39. Oracle Exchange Punchout Guide Release 6 2 September 2001 Part No A92190 01 ORACLE Exchange Release 6 2 Part No A92190 01 Copyright 2001 Oracle Corporation All rights reserved Primary Author Richard Sears Vic Mitchell Contributing Authors Warren Perkinson Sanjay Bhasin Sam Andrus The Programs which include both the software and documentation contain proprietary information of Oracle Corporation they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright patent and other intellectual and industrial property laws Reverse engineering disassembly or decompilation of the Programs is prohibited The information contained in this document is subject to change without notice If you find any problems in the documentation please report them to us in writing Oracle Corporation does not warrant that this document is error free Except as may be expressly permitted in your license agreement for these Programs no part of these Programs may be reproduced or transmitted in any form or by any means electronic or mechanical for any purpose without the express written permission of Oracle Corporation If the Programs are delivered to the U S Government or anyone licensing or using the programs on behalf of the U S Government the following notice is applicable Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are commercial
40. Step 3 Define Your Search Keywords Defining appropriate search keywords for items in your web catalog is important to ensure that buyers browsing the Exchange are presented with the link to your catalog If a buyer s 2 28 Oracle Exchange Punchout Guide Steps to Configure Your Punchout Definition search criteria includes at least one of the keywords you define your web catalog will be displayed in the list of suppliers presented to the buyer Keywords define the items that you have available on your web catalog and you can enter up to 2000 characters of information for each language for which you require keywords For example if you sell paper products to both English and French speaking customers you may want to include the following keywords in American English ream paper photocopy Xerox A5 A4 A3 A2 Al Letter and the following keywords in French rame papier enveloppe photocopie A5 A4 A3 A2 Al If a buyer searches on the Exchange in a foreign language for which you have defined no keywords no link to your catalog will be displayed In the example above if the buyer searches for papel in Spanish a link to your catalog is not returned because you defined no keywords for Spanish 1 To create search keywords you must sign on to Exchange as a user with Catalog Authoring authority 2 On the Configure Catalog Punchout page click the Click here to define keywords for your punchout link The Trading Partner Keywords p
41. XML lt Identity gt 888 lt Identity gt lt Credential gt lt To gt lt Sender gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt lt Credential gt lt UserAgent gt Workchairs cXML lt UserAgent gt lt Sender gt lt Header gt lt Message gt lt PunchOutOrderMessage gt lt BuyerCookie gt ICX lt BuyerCookie gt lt PunchOutOrderMessageHeader operationAllowed edit gt lt Total gt lt Money currency USD gt 112 4 lt Money gt lt Total gt lt PunchOutOrderMessageHeader gt lt ItemIn quantity 3 gt lt ItemID gt lt SupplierPartID gt 5555 lt SupplierPartID gt lt ItemID gt lt ItemDetail gt lt UnitPrice gt lt Money currency USD gt 763 20 lt Money gt lt UnitPrice gt lt Description xml lang en gt Leather reclining chair lt Description gt lt UnitOfMeasure gt EA lt UnitOfMeasure gt lt Classification domain UNSPSC gt 513333 lt Classification gt lt ItemDetail gt lt ItemIn gt lt PunchOutOrderMessage gt lt Message gt lt cXML gt Sample Oracle iProcurement XML Documents C 13 PunchOutOrderMessage cXML C 14 Oracle Exchange Punchout Guide Index A Additional documentation 1 6 Apache Xerces XML parser URL for downloading 2 7 B Benefits of using punchouts 1 2 Buyer steps to control Oracle Exchange punchout access 2 30 C Catalog hosting options differences 1 3 Comparison of punchout m
42. XML PunchOutOrderMessage document a identifying a method for redirecting the buyer and passing the XML Punchout Shopping Cart or cCXML PunchOutOrderMessage document back to Exchange Step 4A Process the incoming XML Punchout Request or cXML PunchOutSetupRequest transaction The XML Punchout Request c XML PunchOutSetupRequest transaction is created on Exchange when a buyer clicks the link to your catalog This transaction contains information about the user and the user s company You should use this information to validate the proper level of user access The Exchange will establish a server to server communication with your site and return either the XML Punchout Request or cKML PunchOutSetupRequest document using the HTTP protocol XML Punchout Request document example An example XML Punchout Request xml document is shown below lt xml version 1 0 encoding ISO 8859 1 gt lt request gt lt header version 1 0 gt lt act ion gt SHOPPING lt action gt lt login gt lt username gt lt username gt lt password gt supplier_password lt password gt lt login gt lt language gt EN lt language gt lt header gt lt body gt lt loginInfo gt lt exchangeInfo gt lt exchangeName gt Exchange Name lt exchangeName gt lt exchangeInfo gt lt userInfo gt lt userName gt Joe Smith lt userName gt lt userContactInfo gt lt userPhone gt 800 123 4568 lt userPhone gt lt userEmail gt jsmith mail com lt user
43. age appears 3 Select the language for which you wish to define keywords from the Language drop down menu 4 Enter all appropriate keywords in the text area 5 When you have completed defining your keywords click the Apply Changes button 6 Repeat steps 3 5 for any additional languages your web catalog supports Step 4 Control Punchout Availability Your punchout definition is not initially available to users Only the punchout author can access your punchout for testing purposes You must publish your punchout definition before any buyers can use it 1 From the Configure Catalog Punchout page click the Click here to set the availability of your punchout link The Control Punchout Availability page appears 2 Click the radio button next to Yes publish my punchout to buying companies on the Exchange 3 Click the Apply Changes button Defining an Oracle Exchange Punchout 2 29 Steps to Configure Your Punchout Definition 4 Your punchout is now available Revoking a punchout used by an Exchange member You can revoke your punchout definition at any time This prevents the punchout from being seen and used by buyers The definition itself remains on Exchange If a buyer has created an order which includes an item from the punchout it is possible for the buyer to reorder the order at a later stage If you revoke or unpublish a punchout which was been previously used to create an order a buyer w
44. alog trading partner code does not exist code for example BOX for example BX VENDOR _ IN NAME Internal supplier name for example Staples External supplier name for example Staples Corp VENDOR _ IN SITE Internal supplier site name i e HQ External supplier name i e Staples Corp 3 44 Oracle Exchange Punchout Guide A Oracle Exchange Punchout DTDs This Appendix contains the XML DTD specifications that govern the format and content of the XML transactions used to pass information between Exchange and your host site Punchout Request Pomlognr dtd Punchout Response Pomlogns dtd Punchout Shopping Cart pomcarts dtd Pomxmlrr dtd Shoppingcart dtd You can find information on the cXML DTD specifications at http xml cXML org schemas cXML 1 1 007 cXML dtd XML Punchout Request pomlognr dtd See also pomxmlrr dtd for common DTD elements lt E lt E lt E lt E lt E lt E lt E lt E lt E lt E lt E lt E lt E LE LE LE LE LE LE LE LE LE LE LE TITY TITY E E E A G G a eee common SYSTEM pomxmlrr dtd gt body lt ELEMENT body loginInfo searchKeywords gt gt loginInfo exchangeInfo userInfo returnURL gt exchangeInfo exchangeName gt exchangeName PCDATA gt userInfo userName userContact Info userCompany gt userName PCDATA gt userContactInfo userPhone userEmail gt
45. ame gt lt supplier gt lt orderLine gt lt OrderLinesDataElements gt lt body gt lt response gt Note See Appendix A for DTD of the shopping cart sent back from the supplier to iProcurement See Appendix B for a sample XML document shopping cart sent back from the supplier to iProcurement 5 iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups in Oracle Applications are referenced to do the required data conversion mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement If the lock_item_flag stored in the ICX_ POR_ITEM_SOURCES table was set during configuration of the punchout for this supplier then the user will not be able to make any changes to the item returned from the supplier site The requisition then goes through the normal workflow and approval processes configured in iProcurement Note See the Installation and Setup section for details on setting the lock_item_flag and using the EDI setups to create data maps Installation Implementation Steps For each of the punchout methods discussed in the previous section there is setup required in iProcurement and either Oracle Exchange or on the Supplier s web store site This section addresses the setup that needs to occur for each type of punchout model Model 1 punchout from Oracle Exchange to supplier
46. an java class to generate the LoginResponse XML document that is returned to iProcurement Upon receipt of this LoginResponse XML document by iProcurement the iProcurement user s browser is re directed to the login URL provided by the supplier The Oracle Exchange involvement in this process is transparent to the iProcurement user The user can shop the supplier s site and add items to a shopping cart on the supplier site When the user finishes adding items to their shopping cart the supplier executes a program which takes the items in the shopping cart and creates an OrderLinesDataElements XML document with the shopping cart item details This document is returned to iProcurement based on the return URL iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups in Oracle Applications are referenced to do the required data conversion mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement If the lock_item_flag was not set during configuration of the punchout for this Exchange then the user will be able to make any changes to the Defining an Oracle iProcurement Punchout 3 9 item returned from Oracle Exchange The requisition then goes through the normal workflow and approval processes configured in Procurement Supplier Hosted Catabg i 1 The iProcurement user starts on their homepage which
47. ay optionally validate that the connection password included is the same as the password you defined when you set up the punchout to your catalog Your portal may also choose to validate other information for example you may wish to check the username and or company name if you are hosting buyer specific content or price breaks Step 4B Provide an appropriate XML Punchout Response or cXML PunchOutSetupResponse Provided that the password is correct your portal should then respond back to Exchange with either an XML Punchout Response or cXML PunchOutSetupResponse document XML Punchout Response document example An example XML Punchout Response document is shown below lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt LOGIN_RESPONSE lt action gt lt header gt lt body gt lt loginInfo gt lt loginURL gt http 130 35 117 113 6290 orders testscripts SupplierCallback jsp Defining an Oracle Exchange Punchout 2 15 Steps to Perform at Your Web Site sessionId 123 lt loginURL gt lt loginInfo gt lt body gt lt response gt Table 2 5 XML Punchout Response Header Data Elements Field Required Type Comment lt action gt Constant LOGIN_RESPONSE Table 2 6 XML Punchout Response Body Data Elements Field Required Type Comment lt loginURL gt Required Character This is the URL to which the Exchange user will be directed on your web catalog As part of the
48. ce of the punchout To punch out to a supplier through the Exchange the iProcurement customer must setup Oracle Exchange as a supplier hub in iProcurement and their suppliers must setup a punchout from Oracle Exchange to their web store Defining an Oracle iProcurement Punchout 3 7 Setup Suppliers on Oracle Exchange The suppliers can setup their punchout definitions one time on Oracle Exchange Then any iProcurement administrator can download these definitions which will automatically setup the punchout from iProcurement to that supplier Note See the chapter Defining an Oracle Exchange Punchout for details on setting up a supplier for punchout from an Oracle Exchange Setup Oracle Exchange as a Supplier Hub in iProcurement The Oracle Exchange you want to use as a supplier hub must first be setup in iProcurement For details on the setup required refer the implementation and installation section later in this document Setup Punchout Suppliers from Oracle Exchange in iProcurement The iProcurement administrator logs on to the iProcurement eContent Manager and initiates the process of setting up punchout suppliers they want to enable iProcurement executes PunchOutServlet which first establishes a secure connection with Oracle Exchange Once established PunchOutServlet then generates the OEXLoginRequest XML document and sends it to Oracle Exchange After the iProcurement user is authenticated on Oracle
49. communicated to all buyer organizations Available using XML format only Oracle iProcurement for Release 11i Installation Guide Oracle iProcurement for Release 11i Implementation Guide Oracle Exchange Implementation and Setup Guide Software Requirements Oracle Exchange 6 1 Patchset C or above Oracle iProcurement Release 11i Patchset J or above 1 6 Oracle Exchange Punchout Guide 2 Defining an Oracle Exchange Punchout This chapter explains how to implement a punchout from Oracle Exchange to a supplier Topics in this chapter include a Introduction to Oracle Exchange punchout a Functional overview of Oracle Exchange punchouts a Steps to perform on Oracle Exchange Steps to perform on your web site a Steps to configure your punchout definition a Oracle Exchange punchout setup checklist Introduction Suppliers using Oracle Exchange typically choose to host their catalogs of goods and services physically on Exchange This relieves them of many of the catalog management tasks If you wish however to still host your own web catalog and yet allow that catalog to be accessible to customers browsing Exchange you can set up a punchout from the Exchange to your supplier hosted catalogs While buyers are browsing the Exchange they enter keywords to search for particular products and services The Exchange search engine will present a list of items which match the keywords entered by the buyer If items from y
50. curement user punches out to Oracle Exchange and is validated during the setup of the punchout session Defining an Oracle iProcurement Punchout 3 37 Installation Implementation Steps Table 3 1 Supplier Hub Setup Field Name Required Description Password Yes The password for the proxy user account created on Oracle Exchange This is used in combination with the Username to establish the punchout session Retype Password Yes Retype the password Keywords No Any words entered in this field will be included when an iProcurement user searches for items on iProcurement If any words match the search criteria entered by the iProcurement user the link to this supplier hub will be displayed along with the other search results Always display this No If checked this Supplier Hub will be displayed in the search hub with search results for any search performed in iProcurement results Items added to No If checked the iProcurement user will be allowed to modify shopping cart from shopping cart items returned from any external site before the external punchout cart is submitted If you do not want the iProcurement user to sites can be modified modify price quantity etc of the items added from external in iProcurement sites leave this box unchecked This is the lock_item_flag earlier referenced in the document Send optional user No If checked the login request XML will include additional user and company
51. d to this hosted catalog model for example books where the catalog changes frequently Yet Exchange suppliers and procurement system content providers know that their users still want the ability to purchase such items The problem is how to allow access to all the items but without the high cost overhead of having to maintain catalogs locally The solution is punchout technology Topics covered in this chapter include a Overview of Oracle Exchange Punchouts a Punchout models Benefits comparison of the punchout models a References a Software requirements Overview of Oracle Exchange Punchouts Punchout enables buyers to connect to the supplier s catalog and search for items directly on the supplier s site When an item or items are identified the item information is returned to the buyer s system to be added to any additional items being purchased Punchout benefits both the supplier and the buyer by allowing suppliers to maintain and host their own catalog information while buyers can search for items from within their own ERP system procurement software or online exchange purchasing operation Using Oracle Exchange Punchouts_ 1 1 Additionally a supplier can utilize the large customer base existing within an Oracle Exchange to increase the exposure that their products receive while reducing the configuration effort required on the part of the supplier A supplier can define a punchout on an Oracle Exchange once and all
52. data when it is sent to the supplier hub or supplier web store information when See details of additional information in Appendix B Sample connecting to the hub XML Documents site Once all the data is entered click the Create button to finish the setup Now your iProcurement users will see a link to this supplier hub on the iProcurement home page or in the external supplier s directory Downloading punchout enabled suppliers from hub If you have suppliers that have already enabled a punchout from Oracle Exchange to their web store you can use this setup to download that setup information into iProcurement Once you complete this setup you can punch out from iProcurement to a supplier s web store and add items to your shopping cart from their site and then return the shopping cart to iProcurement to go through the approval process 3 38 Oracle Exchange Punchout Guide Installation Implementation Steps Note that this functionality will only work with Oracle Exchanges version 6 1c and higher that have an Oracle Exchange setup as a supplier hub and with punchout suppliers enabled on the Exchange a Login to Procurement and navigate to the eContent Manager Home Page and then select Download Punchout Enabled Suppliers from the Hub a Select Supplier Hub Name to view a list of suppliers available on that Oracle Exchange a You will be presented with a list of Suppliers that have a punchout setup with the O
53. displays a link to a supplier site When the user clicks the link the browser connects to the iProcurement server and the PunchOutServlet is executed This servlet first calls Oracle SSL APIs to establish a secure connection with Oracle Exchange The APIs request the Certification Authority CA digital certificate public key from Oracle Exchange This is compared to certificate authorities stored in the ca bundle crt file in Procurement After the secure connection is established the PunchOutServlet generates the OEXLoginRequest XML document that includes a base set of user details and the return URL for the iProcurement instance This XML document is passed to the Oracle Exchange site OEXLoginRequest sample lt xml version 1 0 gt lt request gt lt header version 1 0 gt lt login gt lt username gt buyerl lt username gt lt password gt WELCOME lt password gt lt login gt lt action gt shopping lt action gt lt language gt US lt language gt lt userArea gt lt operat ingUnit gt 204 lt operatingUnit gt lt shipTo gt V1 New York City lt shipTo gt Defining an Oracle iProcurement Punchout 3 19 lt deliverTo gt V1 New York City lt deliverTo gt lt userArea gt lt header gt lt body gt lt loginRequest gt lt userInfo gt lt userName gt Green Mr Terry lt userName gt lt appUserName gt TGREEN lt appUserName gt lt userContactInfo gt lt userEmail gt tgreen v
54. displays a link to a supplier site When the user clicks the link the browser connects to the iProcurement server and the PunchOutServlet is executed This servlet first calls Oracle SSL APIs to establish a secure connection with Oracle Exchange The APIs request the Certification Authority CA digital certificate public key from Oracle Exchange This is compared to certificate authorities stored in the ca bundle crt file in iProcurement After the secure connection is established the PunchOutServlet generates the OEXLoginRequest XML document which includes a base set of user details and the return URL for the iProcurement instance This XML document is passed to the Oracle Exchange site OEXLoginRequest sample lt xml version 1 0 gt lt request gt lt header version 1 0 gt lt login gt lt username gt buyerl lt username gt lt password gt WELCOME lt password gt lt login gt lt action gt shopping lt action gt lt language gt US lt language gt lt userArea gt 3 10 Oracle Exchange Punchout Guide lt operatingUnit gt 204 lt operatingUnit gt lt shipTo gt V1 New York City lt shipTo gt lt deliverTo gt V1 New York City lt deliverTo gt lt userArea gt lt header gt lt body gt lt loginRequest gt lt userInfo gt lt userName gt Green Mr Terry lt userName gt lt appUserName gt TGREEN lt appUserName gt lt userContactInfo gt lt userEmail gt tgreen vision com l
55. e you can setup the Exchange as an external supplier which will be available to users from the iProcurement home page or as part of the search results Note iProcurement users that punch out from iProcurement to Oracle Exchange must be associated with an Oracle ERP employee Setting up profile options 3 new system level profile values in the iProcurement setup section a POR Proxy Server Name Proxy server name if the customer has a proxy setup a POR Proxy Server Port Proxy server port if the customer has a proxy setup a POR CA Certificate File Name Absolute file path of ca bundle crt where all the certificates names are stored Maintaining supplier hubs To setup an Oracle Exchange as a punchout supplier navigate to the eContent Manager in iProcurement From the home page of the eContent Manager select the link for Maintain Supplier Hubs a Click Create New button to setup a new supplier hub 3 36 Oracle Exchange Punchout Guide Installation Implementation Steps a Enter information in the fields on this page to complete the setup Table 3 1 Supplier Hub Setup Field Name Required Description Supplier Hub Name Yes The name that will be displayed on the iProcurement home page and in search results during searches performed by iProcurement users Hub Description No Displayed on the external supplier directory page in iProcurement Only visible when a user re
56. e must be able to process this XML or cXML document validate that the password is correct create an HTTP session to handle the request and respond with a document specifying a destination URL and session information The session information is important for two reasons m If required it will allow you to provide buyer specific information such as unique or pre selected configurations buyer specific pricing or products or buyer specific advertising or links a It will allow your site to recognize buyers as having linked to your site from Exchange and to return the buyers back to the Exchange along with the contents of their shopping carts once they have completed selecting their items For examples of this document in both XML and cXML see Provide an appropriate Punchout Request Response PunchOutSetupResponse transaction later in this chapter The Exchange will redirect the buyer s browser to the URL passed to it from the your site to allow the buyer to continue to shop on your web catalog When the buyer finishes shopping and is ready to return to the Exchange your site must post an XML or cXML document containing all the selected items in the shopping cart back to the URL the Exchange passed in the initial call to your site For examples of this document in both XML and cXML see Return the XML Shopping Cart PunchOutOrderMessage information later in this chapter Defining an Oracle Exchange Punchout 2 3 Steps to Pe
57. ecessary punch out information 1 Click the Click here to configure your punchout link on the Configure Catalog Punchout page The Configure Punchout Definition page appears Enter values in the Punchout URL and Punchout Password fields The Punchout URL is the address of your web catalog s portal page This is the URL you created in a prior step and is the address Exchange will contact when processing a punchout request The punchout password is the value Exchange will pass to your web catalog for access validation Select the communication protocol you will use to pass information to Exchange Exchange supports both XML and cXML Defining an Oracle Exchange Punchout 2 27 Steps to Configure Your Punchout Definition 4 When you have entered the URL password and protocol values scroll to the bottom of the page 5 You may optionally enter the following additional information using the User Interface Identification section of the Configure Punchout Definition page This information appears when your company is displayed as a punchout enabled supplier You can provide an alternate company name in the Display Name field This name will be used in place of your company s registered name You can supply the location of a company logo image in the Logo URL field This image must be in gif format and no larger than 125 pixels wide and 25 pixels high This URL address must be outside your firewall so Exchange can acce
58. ed in your web catalog and ERP applications lt hazardClass gt Do not use Character This tag is required but should not contain any data lt categoryCode gt Required Number Type of product being purchased Defining an Oracle Exchange Punchout 2 23 Steps to Perform at Your Web Site Table 2 11 XML Punchout Shopping Cart Body Data Elements Field Required Type Comments lt currency gt Conditionally Number This is the currency code Optional which you defined within the Data Mapping on the Exchange lt unitPrice gt Conditionally Number Price per unit of this item Optional lt supplier DUNS gt Conditionally Number Supplier DUNS number Required Either lt supplierDUNS gt or lt supplierTradingPartner Code gt is required lt supplierTradingPartnerCode gt Conditionally Character Code for this trading Required partner Either lt supplierDUNS gt or lt supplierTradingPartner Code gt is required Note In the chart above all elements noted as conditionally optional are only optional if there are no items in the shopping cart Note For configured items such as a laptop PC we recommend that you return a single line in the shopping card which represents the entire configura tion You must provide enough information to ensure that the correct configu ration will be shipped to the buyer and allow the buyer to identify the item This can be achieved throu
59. edential gt lt To gt lt Sender gt lt Credential domain OracleExchangeUserId gt lt Identity gt buyer acme com lt Identity gt lt SharedSecret gt supplier_password lt SharedSecret gt Defining an Oracle iProcurement Punchout 3 21 lt Credential gt lt UserAgent gt Exchange_name lt UserAgent gt lt Sender gt lt Header gt lt Request gt lt PunchOutSetupRequest operation create gt lt BuyerCookie gt lt Extrinsic name User gt JSMITH lt Extrinsic gt lt BrowserFormPost gt lt URL gt http iprocurement company com oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping lt URL gt lt BrowserFormPost gt lt Contact gt lt Name xml lang en US gt jsmith lt Name gt lt Email gt buyer acme com lt Email gt lt Contact gt lt PunchOutSetupRequest gt lt Request gt lt cXML gt 3 The supplier site generates a response in the form of a PunchOutSetupResponse cXML document which contains the login URL with session information for the supplier s site PunchOutSetupResponse cXML sample lt xml version 1 0 gt lt cXML payloadID 2000 08 15 timestamp 2000 08 15 gt lt Response gt lt PunchOut SetupResponse gt lt StartPage gt lt URL gt http www suppliersite com orders LinkinCallback jsp sessionId 3fe0a73f6falc003 164 982359182161l amp action shopping lt URL gt lt StartPage gt lt PunchOut SetupResponse gt lt Status code 2
60. ees 2 27 Step 1 Configure Punchout Definition ce ceeeee cece ceeeeeeeceseseseseneneneeseneneneneseees 2 27 Step 2 Test Punchout Definition ccc paa ai aa aE ii aaar aaas 2 28 Step 3 Define Your Search Keywords isississnssnrsnsnsi ansie 2 28 Step 4 Control Punchout Availability 0 00 cee cece ceeseeeecenenseeseneneseseneneneseneneee 2 29 Oracle Exchange Punchout Setup Checklist 0 0 cccccccecssssesesesessseesesescseseesesescssseseeseseees 2 31 Defining an Oracle iProcurement Punchout Model 2 Punch out from Oracle iProcurement to Oracle Exchange XML ou 3 1 Model 3 Punch out from Oracle iProcurement to Supplier via Oracle Exchange XML 3 7 Model 4 Punch out from Oracle iProcurement to Supplier via Oracle Exchange cXML 3 16 Model 5 Punch out from Oracle iProcurement directly to Supplier XML uu 3 25 Installation Implementation Steps cccccceeseesssesssssssesesenssssesesssesesesesesseseeeseneseseseees 3 31 Oracle Exchange Settip Steps sissscisisissscctisabiessisshsibecscsns coc athonies deena E E sees 3 34 Oracle iProcurement Setup Steps cccccccc cece ce ceesseeesesseenesesessseeeseeesseeneseeeeeeeees 3 36 Oracle eCommerce Gateway Setup Steps cccccceccseccneneeseseneieensnseesesnensesescecessassnansneneees 3 42 Oracle Exchange Punchout DTDs XML Punchout Request pomlognrdtd 00 0 0 ccc ccc cceee cscs eeeseecececessnseececesesseseesscssssenesecenes A 1 XML Punchout Response pomlogns d
61. egister their company on Oracle Exchange Once authenticated LinkinMainBean java class generates the LoginResponse XML and sends it back to the Oracle iProcurement LoginResponse sample lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt LOGIN_RESPONSE lt action gt lt nheader gt lt body gt lt loginInfo gt lt loginURL gt http www oracleexchange com orders LinkinCallback jsp sessioniId 3fe0a73f6falc003 164 982359182161 action shopping lt loginURL gt lt loginInfo gt lt body gt lt response gt Now that a secure and trusted connection is established and the user has been assigned a session their browser is re directed to the loginURL on Oracle Exchange and they are allowed to search and add items to their shopping cart on Oracle Exchange The Exchange functionality available to the user is based on the job functions assigned to the Oracle Exchange user that was used during the initial authentication of the punch out The iProcurement administrator on Oracle Exchange controls the job functions Defining an Oracle iProcurement Punchout 3 5 4 When the user finishes adding items to their cart on Oracle Exchange the items in the shopping cart sspcart jsp are posted in a form to iProcurement using the parameter oracleCart This is controlled by the ReqTransaction java class using the callback URL received from iProcurement during the initial punc
62. ency gt USD lt currency gt lt unitPrice gt 50 99 lt unitPrice gt lt price gt lt supplier gt lt supplierDUNS gt 12345 lt supplierDUNS gt lt supplierName gt supplier_name lt supplierName gt lt supplier gt lt orderLine gt lt orderLine gt lt item quantity 10 gt lt itemNumber gt lt supplierItemNumber gt lt itemID gt C1324 lt itemID gt lt supplierItemNumber gt lt manufacturerItemNumber gt lt itemID gt X456 lt itemID gt lt manufacturerName gt Acme Office Supplies lt manufacturerName gt lt manufacturerItemNumber gt lt itemNumber gt lt itemDescription gt Red Whiteboard Markers Chisel Tip lt itemDescription gt lt unitOfMeasure gt lt supplierUnitOfMeasure gt lt supplierUOMType gt Defining an Oracle Exchange Punchout 2 21 Steps to Perform at Your Web Site Each lt supplierUOMType gt lt supplierUnitOfMeasure gt lt unitOfMeasure gt lt hazardClass gt ABC123 lt hazardClass gt lt item gt lt category gt lt categoryCode gt MAB 7836 lt categoryCode gt lt category gt lt price gt lt currency gt USD lt currency gt lt unitPrice gt 5 99 lt unitPrice gt lt price gt lt supplier gt lt supplierDUNS gt 12345 lt supplierDUNS gt lt supplierName gt supplier_name lt supplierName gt lt supplier gt lt orderLine gt lt OrderLinesDataElements gt lt body gt lt response gt Table 2 10 XML Punchout Shopping Cart Header Data
63. er searches for items on iProcurement If any words match the search criteria entered by the iProcurement user the link to this supplier site will be displayed along with the other search results Always display this No If checked this Supplier will be displayed in the search supplier with search results regardless of the search criteria entered by the results iProcurement user Items added to No If checked the iProcurement user will be allowed to modify shopping cart from shopping cart items returned from the supplier site before the external punchout sites cart is submitted If you do not want the iProcurement user can be modified in to modify price quantity etc of the items added from the iProcurement supplier site leave this box unchecked This is the lock_item_flag earlier referenced in the document Send optional user and No If checked the login request XML will include additional company information when connecting to the supplier site user data when it is sent to the supplier site See details of additional information in Appendix B Sample XML Documents 3 40 Oracle Exchange Punchout Guide Installation Implementation Steps Maintaining punchout suppliers This page allows the Procurement administrator to maintain any of the setup information for a punchout supplier setup previously This encompasses both direct punchout suppliers and suppliers downloaded from Oracle Exchange n n n Navigate to the
64. erry lt userName gt lt appUserName gt TGREEN lt appUserName gt lt userContactInfo gt lt userEmail gt tgreen vision com lt userEmail gt lt userContact Info gt lt userInfo gt lt companyInfo gt lt companyName gt IP lt companyName gt lt companyInfo gt lt reqToken gt template tpn _action addToOrder _function addToOrder _reqSessionId 0 _reqHeaderId 0 _emergencyReq N _itemSourcelId 1001 lt regToken gt lt returnURL gt http iprocurement company com oa_servlets oracle apps icx por punchout PunchOutServlet callBack shopping lt returnURL gt lt loginRequest gt lt body gt lt request gt 3 4 Oracle Exchange Punchout Guide Note The DTDs are described in detail in the Appendix A of this document Some additional optional user data can also be sent to Oracle Exchange if the punchout was setup in iProcurement to send it The sample XML document for a login request with additional optional user data is attached in Appendix B of this document For details on how to include the additional information see the Installation and Implementation section Oracle Exchange receives the OEXLoginRequest with the LinkinLogin jsp and executes the LinkinAuthBean java class to authenticate the iProcurement user The user id and password used to authenticate the Procurement user are the same user id and password that is created by the iProcurement administrator when they r
65. gh a combination of information contained in the lt itemID gt and lt itemDescription gt fields It is recommended that the lt itemID gt field contain a code which uniquely identifies the specific configuration selected by the buyer and the lt itemDescription gt field contain a user under standable description of the configured item 2 24 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site lt xml version lt cXML version cXML PunchOutOrderMessage document example An example cXML PunchOutOrderMessage file is shown below 1 1 007 xml lang payloadID 99999 timestamp lt Header gt lt From gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt lt Credential gt lt From gt lt To gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt lt Credential gt lt To gt lt Sender gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt lt Credential gt 1 0 encoding UTF 8 gt en US 2000 08 15 gt lt UserAgent gt Workchairs cXML lt UserAgent gt lt Sender gt lt Header gt lt Message gt lt PunchOutOrderMessage gt lt BuyerCookie gt ICX lt BuyerCookie gt lt PunchOut OrderMessageHeader operationAllowed edit gt lt Total gt lt Money currency USD gt 112 4 lt Money gt lt Total gt lt PunchOutOrderMessageHeader gt lt ItemIn quantity 3 gt lt ItemID gt
66. gt T buyerItemRevision PCDATA gt T itemDescription PCDATA gt T unitOfMeasure buyerUnitOfMeasure G G G A G a w T buyerUnitOfMeasure T supplierUnitOfMeasure ity gt PCDATA gt supplierUOMType PCDATA gt ty PCDATA gt PCDATA gt lt ELEMENT category categoryCode gt lt ELEMENT categoryCode PCDATA gt A 4 Oracle Exchange Punchout Guide SHOPPINGCART DTD lt ATTLIST categoryCode categoryCodeIdentifier SPSC SUPPLIER BUYER IMPLIED gt lt ELEMENT price currency unitPrice gt lt ELEMENT currency PCDATA gt lt ELEMENT unitPrice P lt ELEMENT supplier contactName lt ELEMENT lt ELEMENT lt ELEMENT lt ELEMENT CDATA gt supplierDUNS supplierTradingPartnerCode supplierName contactPhone gt lt ELEMENT supplierDUNS lt ELEMENT supplierTradingPartnerCode PCDATA gt supplierName supplierSite PCDATA gt contactName contactPhone PCDATA gt PCDATA supplierSite gt PCDATA gt PCDATA gt lt ELEMENT additionalAttributes attributel attribute2 attribute3 attribute5 at attribute4 attributel0 attributel5 lt E lt E lt E lt E lt E lt E XKE lt E lt E lt E lt E lt E lt E lt E lt E LE LE LE LE LE LE LE LE LE LE LE LE LE LE LE E E E E E E E E E E E E E E E attribu
67. guageSpecificInfo gt lt supplierLanguageSpecificInfo gt lt language gt Pa lt language gt lt supplierName gt TestCo lt supplierName gt lt supplierDescription gt Yahoo Life Nothing Pen lt supplierDescription gt lt supplierKeywords gt lt supplierLanguageSpecificInfo gt lt supplierLanguageSpecificInfo gt lt language gt US lt language gt lt supplierName gt TestCo lt supplierName gt lt supplierDescription gt Yahoo Life Nothing Pen lt supplierDescription gt lt supplierKeywords gt Monkey Donkey lt supplierKeywords gt lt supplierLanguageSpecificInfo gt lt supplier gt lt body gt lt response gt SupplierLoginRequest Sample XML lt xml version 1 0 gt lt request gt lt header version 1 0 gt lt login gt lt password gt welcome lt password gt lt login gt Sample Oracle iProcurement XML Documents C 9 SupplierLoginRequest lt action gt SHOPPING lt action gt lt language gt US lt language gt lt userArea gt lt operatingUnit gt 204 lt operatingUnit gt lt shipTo gt V1 New York City lt shipTo gt lt deliverTo gt V1 New York City lt deliverTo gt lt userArea gt lt header gt lt body gt lt loginInfo gt lt exchangeInfo gt lt exchangeName gt Oracle lt exchangeName gt lt exchangeInfo gt lt userInfo gt lt userContactInfo gt lt userPhone gt lt userEmail gt tgreen vision com lt userEmail gt
68. h out see step 1 of this section The data is sent back in the OrderLinesDataElements XML document generated by ExportOrder java which is URL encoded OrderLinesDataElements sample lt xml version 1 0 encoding ISO 8859 1 gt lt response gt lt header gt lt act ion gt SHOPPING_RESPONSE lt action gt lt header gt lt body gt lt OrderLinesDataElements gt lt catalogTradingPartner gt OracleExchange lt catalogTradingPartner gt lt orderLine gt lt contract gt lt catalogType gt CONTRACTED lt catalogType gt lt contract gt lt item lineType GOODS quantity 1 0 gt lt itemNumber gt lt supplierItemNumber gt lt itemID gt kb_Item2 lt itemID gt lt supplierItemNumber gt lt itemNumber gt lt itemDescription gt Item 2 kbenjami list TBD b s lt itemDescription gt lt unitOfMeasure gt lt buyerUnitOfMeasure gt lt supplierUnitOfMeasure gt lt supplierUOMType gt Bushel lt supplierUOMType gt lt supplierUOMQuantity gt lt supplierUOMQuantity gt lt supplierUnitOfMeasure gt lt unitOfMeasure gt lt item gt lt category gt lt categoryCode categoryCodeIdentifier SPSC gt Ball Point Pens lt categoryCode gt lt category gt lt price gt lt currency gt USD lt currency gt 3 6 Oracle Exchange Punchout Guide lt unitPrice gt 100 0 lt unitPrice gt lt price gt lt supplier gt lt supplierDUNS gt 2820 lt supplierDUNS gt lt supplierName g
69. he appropriate method for redirecting buyers back to the Exchange and create the code necessary to accomplish this 2 6 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site Prerequisites You have decided how you want to validate user access You have decided how you want to redirect users to Exchange Step 1 Install an XML Parser Step 2 Create Communication between Exchange and web catalogs makes extensive use of XML processing You must have an XML parser tool installed to decode the XML documents passed to you You can use Oracle XML Parser for Java Apache AML Xerces Java Parser or another commercially available parser To download either the Oracle or Apache XML parsers contact one of the sites below Use the instructions on the site s web page when downloading and installing the parser To download the Oracle XML Parser software and documentation and installation instructions see http technet oracle com tech sml parser_java2 To download the Apache XML Parser for Java documentation and software see http xml apache org dtd files for use with your XML Parser XML parsers can use definitions contained in dtd files to test the validity and completeness of data contained in an xml file There are three XML transactions that are used when communicating between a web catalog site and Exchange The name of the transaction depends on the protocol you are using either XML or cXML Table
70. he code shown in the second column enter the code you use in the third column For example your company may use US as the code for US dollars while Exchange uses USD for US dollars In this case you would enter US in the third column s datafield to define the correct mapping After you have specified all your code mappings click the Apply Changes button Map unit of measurement codes In addition to mapping your currency codes you must also map the unit of measurement codes You must map all unit of measurement codes that will be passed between your company and Exchange The process to map unit of measurement codes is similar to that of mapping currency codes 1 Sign on to Exchange using a signon with Company Admin authority 2 From the Marketplace homepage click the Company Admin link Click the Application Setup tab The Application Setup page appears 3 Click the Data Mapping link The Data Mapping page appears 4 Click the Unit of Measurement radio button and click the Edit Mapping button The Edit Mapping Unit of Measurement page appears Defining an Oracle Exchange Punchout 2 5 Steps to Perform at Your Web Site 5 If you do not see the unit of measurement code you wish to map enter the code in the Unit of Measurement Search datafield and click the Go button or click the letter link that corresponds to the first letter of the code The resulting display shows all unit
71. her inbound and outbound XML documents passed between Exchange and your company You must be signed on to Exchange as a Company Administrator to define these mappings Map currency codes 1 Sign on to Exchange using a signon with Company Admin authority If you just registered your company in the previous step the signon you used will have Company Admin authority 2 From the Marketplace homepage click the Company Admin link then click the Application Setup tab The Application Setup page appears 2 4 Oracle Exchange Punchout Guide Steps to Perform on Exchange 3 Click the Data Mapping link The Data Mapping page appears 4 Click the Currency Code radio button and then click the Edit Mapping button The Edit Mapping Currency Code page appears 5 Display the currency code you wish to map by entering the code in the Currency Code Search datafield and clicking the Go button or by clicking the letter link that corresponds to the first letter of the code The resulting display shows all currency codes that matched your search criteria My Company to Exchange to My Description Exchange Value Exchange Value Company Text description of The value used The value you will pass to The value Exchange will the currency code internally by Exchange forward to you if sending a Exchange to transaction from the represent this Exchange not used for currency Punchout If your company does not use t
72. hese words and if a match is found during the search a link to the supplier site will be included on the search results page For Oracle Exchange suppliers this is automatically downloaded during the setup process but can be subsequently change by the iProcurement administrator For direct suppliers the iProcurement administrator enters this during the setup process See step 3 under the Create Direct Punchout Suppliers section for descriptions of the remaining options Once you have completed your changes click the Update button to make your changes Defining an Oracle iProcurement Punchout 3 41 Installation Implementation Steps Re Sequencing the punchout display This page controls the order in which all punchout suppliers including Oracle Exchange are listed in iProcurement The first few suppliers in the list appear on the iProcurement home page Once the list is too long to display all suppliers on the home page a more link is displayed after the first few suppliers Clicking this link provides a list of all punchout suppliers enabled in iProcurement This page will let you control the order these suppliers are listed a Navigate to the iProcurement eContent Manager home page Choose the link to Re sequence Punchout Display a A list of all punchout suppliers enabled in iProcurement is displayed a Enter the sequence number in the left column according to how you want the list of suppliers ordered
73. hout Chapter 3 Defining an Oracle iProcurement Punchout This chapter explains the different punchout models supported by Oracle iProcurement and how to implement each Appendix A Oracle Exchange Punchout DTDs This appendix contains examples of the DTDs used when executing Oracle Native XML punchout transactions from Oracle Exchange Appendix B Oracle iProcurement Punchout DTDs This appendix contains examples of the DTDs used when implementing an XML punchout from Oracle iProcurement Appendix C Sample Oracle iProcurement XML Documents This appendix conatins example XML documents used during a punchout from Oracle iProcurement sample XML documents used for native XML punchout from Oracle Exchange are contained in Chapter 2 Related Documents For additional information on installing and implementing Oracle Exchange and Oracle iProcurement see the following manuals a Oracle iProcurement for Release 11i Installation Guide a Oracle iProcurement for Release 11i Implementation Guide a Oracle Exchange Installation Guide 1 Using Oracle Exchange Punchouts While procurement systems and online exchanges typically offer the ability to store information about their suppliers items or services locally the task of defining and maintaining these local catalogs is both time consuming and in the case of some products that are continually changing extremely difficult Additionally some items and services are not well suite
74. i N ZEAE IEA ASNE E A ACEEA TEE E TAE AEN ES ix Related DOCUIMEN tS srren eee fie BIA sche eed tee a a ote sada at de Mace ius as Ss RN se aa Ca aes x Using Oracle Exchange Punchouts Overview of Oracle Exchange Punchouts 0 0 0 ce cceeeececesseseesssesseesesssssseeseseseseeeees 1 1 Benefits Comparison of Punchout Models cccccceceeeeee ce cessseeeeesssssesseesesesesseesesssesesesees 1 6 References aise eG ise tds ee ns avn seen ie 1 6 Software REGUIFETEIISS ientra p e ei a a toons 1 6 Defining an Oracle Exchange Punchout Introductions neie etene e a e a ved Bee ee aaea e a a E Ea a Ea a eee 2 1 Functional Qyetvie Wese nein e a aa Sines ete a Atel Eee 2 2 Steps to Perform on Exchange siinsesse ae 2 4 Step 1 Register your company on Exchange cccccceseeesee ce csesssesessessssseeesesssssseesesssesesesens 2 4 Step 2 Create cod Mappings issssiens ii uasna airin ana EE E e i a SE 2 4 Steps to Perform at Your Web Site n ssesnesneeseesesseestestesessesntertesessssnrentesnesssnrenresetssenenrennessesses 2 6 Step Install an XM Parsets sian ceisits se aecitr etude sinters svn EEEN ditee ss 2 7 Step 2 Create dtd files for use with your XML Parser ccc ee cesses ceeseseeeeseeeeeens 2 7 Step 3 Create a URL to accept incoming punchout documents cceceeseteeeeesestetetenees 2 8 Step 4 Create the XML processing Code sssusa anisi 2 9 Steps to Configure Your Punchout Definition cece cesses neceeseneseeseeteen
75. iProcurement eContent Manager home page Select the link to Maintain Punchout Suppliers The iProcurement is presented with a list of all punchout suppliers enabled in iProcurement n Supplier column downloaded from Oracle Exchange or entered in the punchout supplier field during a direct punchout supplier setup Description downloaded from Oracle Exchange or entered in the description field during a direct punchout supplier setup Source identifies where the supplier setup information originated If the supplier was downloaded from an Oracle Exchange this column will contain the supplier hub name entered during set up of the hub If the supplier was setup as a direct punchout supplier in Procurement the value in this column is Internal Click the supplier name to edit the supplier specific details n Punchout supplier the name that is displayed to Procurement users For Oracle Exchange suppliers this is automatically downloaded during the setup process For direct suppliers the iProcurement administrator enters this during the setup process Description used when this supplier is displayed in the complete list of external suppliers For Oracle Exchange suppliers this is automatically downloaded during the setup process For direct suppliers the Procurement administrator enters this during the setup process Keywords used when an Procurement user is searching for catalog items The search engine will include t
76. iately be unavailable for use by any buyer It will continue to appear on the Select Supplier Punchouts page although it will be identified as having been disabled by the supplier 2 30 Oracle Exchange Punchout Guide Oracle Exchange Punchout Setup Checklist Once the Purchasing Manager deselects the disabled punchout links and commits the change the links are not available for reselection until the supplier re enables the punchout Reordering from a Punchout Disabled by the Purchasing Manager A situation can arise when a Purchasing Manager enables access to a supplier s punchout a buyer then creates an order from this punchout and the Purchasing Manager subsequently disallows this punchout If after the Purchasing Manager has disallowed this punchout the buyer then clicks the Reorder button to reorder these items the buyer will get an error message and be prompted to view those items which could not be copied onto the new order If the buyer then clicks the link a list with all the items which could not be copied onto a new purchase order displays For those items created from a punchout which has subsequently been disallowed by the Purchasing Manager the following message displays The item was selected from an external site which has since been disabled by your Purchasing Manager Please select another item Oracle Exchange Punchout Setup Checklist The following is a checklist of the tasks you must complete to integrate yo
77. ich requests the Certification Authority CA digital certificate public key from the supplier site The Oracle Exchange operator compares this to certificate authorities setup If validated a secure connection is opened between Oracle Exchange and the supplier site The PunchOutLoginBean java class then generates the LinkRequest XML document It includes the site level user name and password that the supplier requires accessing their web store Note The site level user name is stored and maintained on Oracle Exchange by the supplier There is no need for the iProcurement sysadmin to store this information The LinkRequest also includes user and company details from the iProcurement user that were included in the initial OEXLoginRequest from iProcurement to Oracle Exchange LinkRequest XML sample lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt login gt lt username gt lt password gt supplier_password lt password gt lt login gt lt action gt lt header gt lt body gt lt loginInfo gt lt exchangeInfo gt lt exchangeName gt Oracle Exchange lt exchangeName gt lt exchangeInfo gt 3 12 Oracle Exchange Punchout Guide lt userInfo gt lt userName gt Joe Smith lt userName gt lt userContactInfo gt lt userPhone gt 6505062000 lt userPhone gt lt userEmail gt jsmith hotmail com lt userEmail gt lt userContactInfo gt lt u
78. ich they would normally proceed with the checkout process they will see instead a Return to Exchange button The following sample Java code will conditionally display a button if the value of the variable sessionID is set to 123 lt if request getParameter sessionID equals 123 gt lt form name form_name gt lt input type submit name sSubmit_button value Return to Exchange gt lt Put other appropriate HTML form commands here gt lt form gt lt 5 gt If your web catalog will only be accessed from Exchange no such conditional processing is necessary Step4D Return the XML Punchout Shopping Cart or cXML PunchOutOrderMessage information Once the user clicks the Return to Exchange button your site must send a transaction to the Exchange containing details of all the items the buyer selected from your web catalog Defining an Oracle Exchange Punchout 2 19 Steps to Perform at Your Web Site For Oracle Native XML transactions the URL to which this XML transaction should be sent is the URL identified by the lt returnURL gt tag in the original XML Punchout Request transaction It is important that the document is url encoded and the parameter name for the HTTP Post is oracleCart For cXML transactions the URL to which this transaction should be sent is identified by the lt BrowserFormPost gt tag in the original cXML PunchOutSetup Request It is important that
79. ii cite sisiteessinetsinninstemnnntescnninsoxaitetri titre anteatiiseenes C 1 OEXLoginRequest with optional extended data ccccccccesssesesteteseseeteeeteseeceenesesnsneneseneees C 3 LOginR esponse sns ie etn a Ma eh casas Bu ett Mero Birstall ace ate C 5 OrderLinesDataEleme nt wisi 3es 0sie esessisaevettesiisvvavisstssvesianids ssia ais tee asaina C 5 Link Reg test poao Ress peptidases e ots alannah a AA eed peat ra A E E these bas C 8 LinkRespons stinde S5s 62 eas N Veins Sin aie eoeti de abies ts C 8 SupplierSyncUpResponse isicseceeseececcesssidenssasesedenssvsssoersesvtnssserssensentinssetvnvnsedsetsniesnasessebeotatuce C 8 S pplerLoginReg st iira e n nE EN E E E R E E ES EN C 9 PunchOutSetupRequest CXML ccccsesccsssscsssesesescsesesesesescscsesesesescsesesesescsesessseseesscsssnsneseeeees C 11 PunchOutSetupResponse CCXML nriran ana na aaaea aai aa C 12 PunchOutOrderMessage CXML innnan haana arst C 12 Index vi Send Us Your Comments Oracle Exchange Punchout Guide Release 6 2 Part No A92190 01 Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this document Your input is an important part of the information used for revision Did you find any errors Is the information clearly presented Do you need more information If so where Are the examples correct Do you need more examples What features did you like most If you find any errors or
80. ill be prevented from reordering any of the items on this order Buyer Steps to Control Punchout Access Purchasing managers need to be able to specify which suppliers punchouts can be used by buyers within their company They can do this by enabling punchouts only from approved suppliers When a new company registers with Exchange no punchouts are available until they are enabled and any new supplier punchouts that are defined are not visible to buyers until specifically enabled by the Purchasing Manager Purchasing Manages can remove or add punchout definitions at any time You must have the Control Punchout Access Exchange task to identify the punchouts available to buyers within your company Note also that Company Administrators can control access to punchouts by granting or revoking the Punchout to Supplier Site Exchange task to individual users 1 In the Marketplace Buyer application click the Purchases tab 2 Under Catalogs click the Control Punchout Access link The Control Punchout Access page appears This page lists all punchouts defined for Exchange 3 Click the Select checkbox next to the punchouts you wish to enable for buyers in your company 4 Once you have selected all the punchouts your company will use click the Review and Submit button 5 A confirmation page appears Your users can now access the punchouts Effect of a Supplier Disabling a Punchout If a supplier disables a punchout it will immed
81. in Oracle Applications are referenced to do the required data conversion mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement And if the lock_item_flag was not set during configuration of the punchout for this supplier then the user will be able to make changes to the item returned from the supplier site The requisition then goes through the normal workflow and approval processes configured in iProcurement 3 26 Oracle Exchange Punchout Guide Supplier N Orade Procurement Sener Supplier Porta a Supplier Hosted Catabg The Procurement user starts on their homepage which displays a link to an external supplier When the user clicks the supplier link the browser connects to the iProcurement server and the PunchOutServlet is executed This servlet first calls Oracle SSL APIs to establish a secure connection with the supplier site if required The APIs request the Certification Authority CA digital certificate public key from the supplier site This is compared to certificate authorities stored in the ca bundle crt file in iProcurement After the secure connection is established the PunchOutServlet generates the SupplierLoginRequest XML document which includes a base set of user details and the return URL for the Procurement instance This XML document is passed to the supplier site SupplierLoginRequest sample
82. ined in the lt SupplierPartID gt element It is recommended that the lt SupplierPartID gt element contain a code which uniquely identifies the specific configuration selected by the buyer and that the lt Description gt element contain a user understandable description of the configured item 2 26 Oracle Exchange Punchout Guide Steps to Configure Your Punchout Definition Steps to Configure Your Punchout Definition The final set of steps is necessary to make Exchange aware of your web catalog s punchout capability and to control accessibility These setup steps are documented below 1 gt N Configure Punchout Definition Test Punchout Definition Assign Search Keywords Control Availability Prerequisites You have a signon with Catalog Authoring authority and the Catalog Authoring job function includes the Configure Catalog Linkout job task You also have the Create Add to Cart Order job function The Configuration steps listed about are performed from the Configure Catalog Punchout page 1 2 In the Markeplace Selling application click the Catalogs tab From the Catalogs page click the Configure Catalog Punchout or the Setting up a catalog punchout link The Configure Catalog Punchout page appears The four steps to configuring your punchout are accessible from this page Step 1 Configure Punchout Definition For users to punch out directly to your catalog you must provide the n
83. ision com lt userEmail gt lt userContact Info gt lt userInfo gt lt companyInfo gt lt companyName gt IP lt companyName gt lt companyInfo gt lt partySitelId gt 2963 lt partySiteld gt lt reqToken gt template tpn _action addToOrder _function addToOrder _regqSessionId 0 _reqHeaderId 0 _emergencyRegq N _itemSourceld 1001 lt regToken gt lt returnURL gt http iprocurement company com oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping lt returnURL gt lt loginRequest gt lt body gt lt request gt Note The DTDs are described in detail in the Appendix A of this document Some additional optional user data can also be sent to Oracle Exchange if the punchout was setup in iProcurement to send it The sample XML document for a login request with additional optional user data is attached in Appendix B of this document For details on how to include the additional information see the Installation and Implementation section Oracle Exchange receives the OEXLoginRequest with the LinkinLogin jsp and executes the LinkinAuthBean java class to authenticate the iProcurement user 3 20 Oracle Exchange Punchout Guide After the Procurement user is authenticated on Oracle Exchange the Exchange executes the PunchOutLoginBean java class To establish a secure connection to the supplier site it calls Oracle SSL APIs if required based on
84. kinMainBean java class to generate the LoginResponse XML document that is returned to iProcurement through the secure connection After the login response is received by the iProcurement instance the user s browser is re directed to the login URL provided by the Exchange in the LoginResponse XML document Now the user can search and add items to a shopping cart on Oracle Exchange The Exchange functionality available to the user is based on a profile previously setup in Oracle Exchange 3 2 Oracle Exchange Punchout Guide After the user finishes adding items to their shopping cart the ReqTransaction java class in Oracle Exchange calls the ExportOrder java class which creates the OrderLinesDataElements XML document that contains the shopping cart items added from Oracle Exchange This is sent back to iProcurement based on the return URL iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups in Oracle Applications are referenced to do the required data conversion mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement If the lock_item_flag was not set during configuration of the punchout for this Exchange then the user will be able to make any changes to the item returned from Oracle Exchange The requisition then goes through the normal workflow and approval processes configured in iProcurement before bei
85. le XML document for a login request with additional optional user data is attached in Appendix B of this document For details on how to include the additional information see the Installation and Implementation section The supplier receives the SupplierLoginRequest and authenticates the iProcurement user Once authenticated the supplier must generate the LoginResponse XML and send it back to the Oracle iProcurement LoginResponse sample lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt LOGIN_RESPONSE lt action gt lt header gt lt body gt lt loginInfo gt lt loginURL gt http www suppliersite com orders LinkinCallback jsp sessionid 3fe0a73f6falc003 164 982359182161 action shopping lt loginURL gt lt loginInfo gt lt body gt lt response gt Now that a secure and trusted connection is established the iProcurement user s browser is re directed to the session aware login URL provided by the supplier Now the user is allowed to search and add items to their shopping cart on the supplier site Defining an Oracle iProcurement Punchout 3 29 4 When the user finishes adding items to their cart on the supplier s site the items in the shopping cart are posted to the iProcurement server with the oracleCart parameter using the return URL received from iProcurement during the initial punch out see step 1 of this section The data must be
86. lier on Oracle Exchange lt supplierKeywords gt Y Keywords provided by the supplier on Oracle Exchange lt supplierPartyId gt Y The supplier s party ID on Oracle Exchange lt supplierImageUrl gt Y The URL pointing to the supplier s logo SupplierLoginRequest dtd lt Header SupplierLoginRequest dtd 115 0 2001 02 03 00 57 54 skau noship gt lt ENTITY lt ENTITY lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME lt ELEME Scommon Srequest 2 6 2 common SYSTEM pomxmlrr dtd gt body lt ELEMENT body loginInfo searchKeywords gt gt loginInfo exchangeInfo userInfo returnURL gt exchangeInfo exchangeName gt exchangeName PCDATA gt userinfo userName userName userContact Info userCompany gt PCDATA gt userContactInfo userPhone userEmail gt userCompany companyName companyDUNS contactName contactPhone gt userPhone userEmail PCDATA gt PCDATA gt companyName PCDATA gt companyDUNS PCDATA gt contactName PCDATA gt contactPhone PCDATA gt returnURL B 10 Oracle Exchange Punchout Guide PCDATA gt PunchOutOrderMessage dtd Table B 6 SupplierLoginRequest did Elements Field Required Comment lt exchangeName gt Y The iProcurement company name that is t
87. m lineType Y Identifies the beginning of the item section contains the GOODS quantity following attributes 1 0 gt LineType Possible values GOODS SERVICES_ AMOUNT SERVICES_QUANTITY with GOODS as default with nothing is specified Quantity The number of items ordered lt itemID gt Y Supplier buyer or manufacturer item number depending on parent tag Oracle iProcurement Punchout DTDs B 7 OrderLinesDataElements did Table B 4_ OrderLinesDataElements dtd Elements Field Required Comment lt supplierReferenceNu N Reference number provided by the supplier for this item or mber gt order is stored by iProcurement in the supplier reference number field lt manufacturerName gt N The name of the manufacturer for this item will populate the Manufacturer Name in iProcurement lt buyerltemRevision gt N If provided by the supplier populates the item revision field in iProcurement lt itemDescription gt Y The supplier s description of this product it will populate the item description in the iProcurement shopping cart lt buyerUnitOfMeasure gt Y Identifies the buyer s unit of measure lt supplierUOMType gt Y Specifies the supplier s unit of measure type i e each dozen bushel etc lt supplierUOMQuantity N Specifies the suppliers quantity in the specified unit of gt measure lt hazardClass gt N Hazard class name for the item if provided b
88. m2 lt itemID gt lt supplierItemNumber gt lt itemNumber gt lt itemDescription gt Item 2 kbenjami list TBD b s lt itemDescription gt lt unitOfMeasure gt lt buyerUnitOfMeasure gt lt supplierUnitOfMeasure gt lt supplierUOMType gt Bushel lt supplierUOMType gt lt supplierUOMQuantity gt lt supplierUOMQuantity gt lt supplierUnitOfMeasure gt lt unitOfMeasure gt lt item gt lt category gt lt categoryCode categoryCodeldentifier SPSC gt Ball Point Pens lt categoryCode gt lt category gt lt price gt lt currency gt USD lt currency gt lt unitPrice gt 100 0 lt unitPrice gt lt price gt lt supplier gt lt supplierDUNS gt 2820 lt supplierDUNS gt lt supplierName gt Kareem s Corporation lt supplierName gt lt supplier gt lt orderLine gt lt OrderLinesDataElements gt lt body gt lt response gt Note See Appendix A for DTD of the shopping cart sent back from the supplier to iProcurement See Appendix B for a sample XML document shopping cart sent back from the supplier to iProcurement iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups in Oracle Applications are referenced to do the required data conversion Defining an Oracle iProcurement Punchout 3 15 mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement
89. mation is passed between Exchange and your portal using an unsecure connection may allow the transmission to be intercepted and compromise the security of your site If your site accepts HTTPS requests when the Exchange initiates communication with your site your server will return your digital certificate identification number which Exchange will compare to a list of trusted certificates contained in the file pomdigcrt txt on the Exchange Note This is the default certificate file name The name can be changed by the Exchange Operator If this digital certificate is recognized the certificate will be used to generate a unique session key to be used only for the duration of this connection between your site and the Exchange and the Exchange will transmit this session key back to your site encrypted using your server s public key All subsequent communication between the Exchange and your site will be encrypted Step 4 Create the XML processing code You will need to create code to perform the XML processing required to communicate with Exchange This processing includes interpreting the XML Punchout Request or cXML PunchOutSetupRequest document passed to you from Exchange creating the XML Punchout Response or cXML PunchOutSetupResponse document and passing it back to Exchange Defining an Oracle Exchange Punchout 2 9 Steps to Perform at Your Web Site creating the XML Punchout Shopping Cart or c
90. nfo gt lt loginURL gt http www suppliersite com orders SupplierShopping jsp sessionID 123 lt loginURL gt lt loginInfo gt lt body gt lt response gt 5 Using the session aware login URL provided in the LoginResponse XML iProcurement executes the PunchOutServlet that re directs the Procurement user s browser to the supplier site using the supplier s login URL The user is allowed to search and add items to their shopping cart on the supplier site 6 When the user finishes adding items to their cart on the supplier site the items in the shopping cart must be sent back to iProcurement by posting a form to the return URL received from iProcurement during the initial punchout The parameter for the post should be oracleCart The data is sent back in the OrderLinesDataElements XML document which is url encoded OrderLinesDataElements XML sample lt xml version 1 0 encoding ISO 8859 1 gt lt response gt lt header gt lt act ion gt SHOPPING_RESPONSE lt action gt lt header gt lt body gt lt OrderLinesDataElements gt lt catalogTradingPartner gt lt suppier name gt lt catalogTradingPartner gt lt orderLine gt lt contract gt lt catalogType gt CONTRACTED lt catalogType gt lt contract gt lt item lineType GOODS quantity 1 0 gt 3 14 Oracle Exchange Punchout Guide lt itemNumber gt lt supplierItemNumber gt lt itemID gt kb_Ite
91. ng turned into a purchase order 1 The iProcurement user starts on their homepage which displays a link to an Oracle Exchange When the user clicks the Oracle Exchange link the browser connects to the iProcurement server and the PunchOutServlet is executed This servlet first calls Oracle SSL APIs to establish a secure connection with Oracle Exchange The APIs request the Certification Authority CA digital certificate public key from Oracle Exchange This is compared to certificate authorities stored in the ca bundle crt file in iProcurement After the secure connection is established the PunchOutServlet generates the OEXLoginRequest XML document which includes a base set of user details and the Defining an Oracle iProcurement Punchout 3 3 return URL for the iProcurement instance This XML document is passed to the Oracle Exchange site OEXLoginRequest sample lt xml version 1 0 gt lt request gt lt header version 1 0 gt lt login gt lt username gt buyerl lt username gt lt password gt WELCOME lt password gt lt login gt lt action gt shopping lt action gt lt language gt US lt language gt lt userArea gt lt operatingUnit gt 204 lt operatingUnit gt lt shipTo gt V1 New York City lt shipTo gt lt deliverTo gt V1 New York City lt deliverTo gt lt userArea gt lt header gt lt body gt lt loginRequest gt lt userInfo gt lt userName gt Green Mr T
92. nization must also have their suppliers register and load catalogs on the Oracle Exchange they will punch out to The supplier catalog can include buyer specific pricing for the iProcurement customer and is loaded on Oracle Exchange using either a tab delimited text file spreadsheet or XML file Refer to the Exchange you want to register on for details on loading a catalog Setup Oracle Exchange as a Punchout external Supplier in iProcurement The Oracle Exchange you want to punch out to must first be setup in iProcurement For details on the setup required refer the implementation and installation section later in this document Punchout Process When a user clicks the link to Oracle Exchange the PunchOutServlet servlet is executed First this calls Oracle SSL APIs to establish secure connection to Oracle Exchange These APIs request a Certification Authority Certificate from the Oracle Exchange site and compare that to Certificates stored in iProcurement After a secure connection between iProcurement and Oracle Exchange is established PunchOutServlet then generates the OEXLoginRequest XML document that contains user details and login credentials for Oracle Exchange as well as a return URL Once generated this is passed to Oracle Exchange LinkinLogin jsp through the secure connection Oracle Exchange uses the LinkinAuthBean java class to authenticate the iProcurement user Once authenticated Oracle Exchange uses the Lin
93. nous communication gt T login username password session gt user name and password or the session details gt T action PCDATA gt action required from the request gt cookies cookie gt cookies set from response see header element for more info gt T cookie PCDATA gt ST cookie name CDATA REQUIRED gt T language PCDATA gt userArea ANY gt T username PCDATA gt T password PCDATA gt session lt ELEMENT session sessionID gt gt aB K T sessionID PCDATA gt return returnMessage gt Y returnMessage lt ELEMENT returnMessage PCDATA gt gt returnMessage is made an entity so that if a specific response desires rn multiple messages or an xml document itself it can override this gt SreturnMessage lt ATTLI lt Warning require ST return returnCode S E U W A REQUIRED gt return code for the request S Success E Error U Unexpected W and A means require authentication Authentication returncode is d in case the session is expired and the user has to use username password info instead of the session info gt Oracle Exchange Punchout DTDs A 3 SHOPPINGCART DTD Sbody lt body ent ity has to be customized by each request response dtd gt SHOPPINGCART DTD lt ELEMENT OrderL lt ELEMENT catalo lt ELEMENT orde contract item lt ELEMENT co buyerContract b lt ATTLIST INFORMATIO
94. ode 401 text Invalid Shared Secret gt lt Response gt lt cXML gt For detailed information about the elements in the cXML example above see the cXML 1 1 User s Guide available at http www cXML org If you deny access to your web catalog as in the example above the buyer will be shown an error message and will be unable to access your web catalog 2 18 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site Step 4C Determine the redirect method Once buyers have completed browsing your site they must return to the Exchange to complete the purchase process for the items they added to their shopping cart from your web catalog Depending on the structure of your web catalog you may need to determine whether a buyer navigated to your site from the Exchange or from another site If you site accepts buyers from both the Exchange and other sites your checkout process will be different than if you only accept buyers from the Exchange If you accept buyers from both Exchange and alternate sites your Exchange buyers should see a Return to Exchange button instead of a generic Proceed to Checkout button You could achieve this as follows 1 When the user initially establishes a connection with your web catalog they could have a session ID defined for their connection refer to Create a URL to accept incoming punchout documents earlier in this chapter 2 When the user reaches the point at wh
95. odels 1 6 cXML Punchout Response for errors document example 2 18 cXML PunchoutOutOrderMessage document example 2 25 cXML PunchOutSetupRequest document example 2 12 cXML PunchOutSetupResponse document example 2 16 O Oracle Exchange Punchout Exchange Setup Steps Creating code mappings 2 4 Registering your company 2 4 Punchout Configuration Configuring the punchout definition 2 27 Controlling punchout availability 2 29 Defining keywords 2 28 Testing the punchout definition 2 28 Web Site Setup Steps 2 6 Creating a URL to accept incoming documents 2 8 Creating dtd files 2 7 2 27 Creating XML processing code 2 9 Installing an XML parser 2 7 Oracle Exchange Punchout Setup Checklist 2 31 Oracle Exchange Punchout international support and character encoding 2 8 Oracle Exchange punchout using secure connections with 2 9 Oracle Exchange to supplier punchout model 1 3 Oracle iProcurement to Oracle Exchange punchout model 1 4 3 1 installation implementation maintaining punchout suppliers 3 41 maintaining supplier hubs 3 36 overview 3 32 resequencing the punchout display 3 42 setting up a site level user on Oracle Exchange 3 35 setting up profile options 3 36 setting up your code conversions 3 43 setting up your company on Oracle Exchange 3 34 setting up your trading partner 3 42 Punchout process 3 2 Oracle iProcurement to supplier punchout model 1 5 3 25 installation implementation crea
96. of measurement codes that match your search criteria My Company to Exchange to My Description Exchange Value Exchange Value Company Text description The value used The value you will pass to The value Exchange will of the unit of internally by Exchange forward to you if sending a measurement Exchange to transaction from the code represent that unit of Exchange not used for measurement Punchout If your company does not use the code shown in the second column enter the code you use in the third column For example your company may use CSE as the code for case while Exchange uses CS for case In this case you would enter CSE in the third column s datafield to define the correct mapping After you have specified all your code mappings click the Apply Changes button Steps to Perform at Your Web Site Exchange uses XML and cXML based transactions when communicating with host sites so you will need to modify your site to support this processing This includes installing an XML parser if one is not already in place and storing the DTD specifications for the transactions involved The complete set of steps includes 1 Install an XML parser 2 Create and store the necessary DTD specifications for the transactions to be used 3 Create a new URL to handle the incoming punchout request 4 Create the code necessary to process and generate the necessary XML or cXML documents to communicate with Exchange 5 Determine t
97. omparison of Punchout Models References Model Buyer Benefits Supplier Benefits Comments 1 Oracle Exchange punchout to Buyer members automatically have access to centralized Suppliers define punchouts once to Exchange and are then visible to potentially all Exchange Suppliers can control access to their punchouts supplier hosted collection of punchouts members Purchasing catalogs simply by registering Managers and with Exchange Company Admins can control buyer access 2 iProcurement As soon as a supplier defines a iProcurement requisitioners have catalog to Exchange iProcurement punchout to Oracle Exchange hosted catalogs access to all supplier catalogs defined on Exchange users have access to it Catalogs are also available to registered Exchange users 3 4 iProcurement punchout to supplier hosted catalogs via Oracle Exchange iProcurement users have access to centralized collection of punchouts Suppliers only have to define their punchouts on the Exchange once An individual configuration within each iProcurement instance is not required Punchout can be via Oracle native XML or cXML 5 iProcurement punchout directly to supplier hosted catalogs eContent managers can control their users access to punchouts from within iProcurement Supplier can control access by determining who obtains the punchout information Any punchout changes must be
98. on as the buyer returns to the Exchange and will also be used to identify the buyer as having navigated to your site from the Exchange In the above example the session is identified with a session ID If an error is discovered for example the password is invalid an XML Punchout Response similar to the example below should be returned to Exchange lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt return returnCode A gt lt return gt lt header gt lt body gt lt loginInfo gt lt loginURL gt lt lLoginURL gt lt loginInfo gt lt body gt Defining an Oracle Exchange Punchout 2 17 Steps to Perform at Your Web Site lt response gt Table 2 8 XML Punchout Response Header Data Elements Field Required Type Comment lt return gt Not currently used Character Provision for a failure message in the future Not used currently lt return returnCode gt Required Attribute Character Valid Values S Success E Error W Warning A Requires Approval Table 2 9 XML Punchout Response Body Data Elements Field Required Type Comment lt loginURL gt Optional Character Ignored The cXML equivalent would be lt xml version 1 0 gt lt cXML payloadID 99999 timestamp 2000 08 15 gt lt Response gt lt Punchout SetupResponse gt lt StartPage gt lt URL gt lt URL gt lt StartPage gt lt PunchOut SetupResponse gt lt Status c
99. our supplier hosted web catalogs match the search criteria the buyer is presented with a link from the Exchange catalog to navigate to your supplier hosted catalog When the buyer completes selecting items to purchase your supplier hosted site returns the shopping cart contents to the Exchange to complete the buyer s transaction Defining an Oracle Exchange Punchout 2 1 Introduction Oracle Exchange uses XML transactions to pass information between Exchange and your supplier hosted site Exchange supports both XML and cXML protocols for exchanging information Functional Overview Exchange Supplier Website ORACLE Exchange Catalog Search ORACLE Exchange Return URL Supplier Web Store ORACLE Exchange Checkout Firewall 2 2 Oracle Exchange Punchout Guide Introduction When the keywords you defined when you defined your punchout on the Exchange meet the search criteria of a buyer shopping on Exchange a link to your site is displayed When the buyer clicks the link to your site the Exchange will post an XML or cXML document to the URL address that you specified for your web catalog This document will include among other things a connection password the buyer s Exchange username the buyer s company name and a return URL For examples of this document in both XML and cXML see Process the incoming Punchout Request PunchOutSetupRequest transaction later in this chapter Your sit
100. pplier avoids managing a complex web site and web content Oracle Exchange supports various punchout models allowing both suppliers and buyers to provide and obtain goods and services most efficiently Model 1 Oracle Exchange punchout to Supplier hosted catalogs Oracle i Exchange waas Up plier com Supplier Hosted Catslogs Buyer Bp eolo view Eu vor Bp enlin Prioing Contaots Using Oracle Exchange Punchouts 1 3 Model 2 Punchout from Oracle iProcurement to Oracle Exchange in XML format iit Spies Oracle Exchange Punchout AML Model 3 Punchout from Oracle iProcurement to a Supplier hosted catalog via Oracle Exchange using XML format waas up plier com Supplier Hosted Catalogs Sippler Buyer Bp polta view Buyer Bpeolto Prioing Paachort Cantants Deth thors 1 4 Oracle Exchange Punchout Guide Model 4 Punchout from Oracle iProcurement to a Supplier hosted catalog via Oracle Exchange using cXML format Catalogs se I 1 1 Oracle Supplier Hosted Exchange Punchout sappier Paachort Deth thors EuyorB Ito View cXML Buyer appalto Pricing Cantaots Model 5 Punchout from Oracle iProcurement directly to a Supplier hosted catalog using XML wasup plier com Punchout Supplier Hosted AML Catalogs Buyer Bp polta view Eu yor Bpeolto Pricing Contaots Using Oracle Exchange Punchouts 1 5 Benefits C
101. quests a list of all external suppliers example The Exchange for Big Business Small Business All Business URL Yes The URL that iProcurement will use to login to Oracle Exchange For any Oracle Exchange it should be the following http www lt exchangename gt com orders LinkinLogin jsp Example http exchange oracle com orders LinkinLogin jsp Image URL Optional field to specify the web address of the Exchange s logo For Oracle Exchange s the URL will be http www lt exchangename gt com brands lt xx gt marketing lt yy gt logo gif Where lt xx gt represents the database of the exchange instance Ask the Exchange operator you are creating a link to for this information Where lt yy gt represents the language code e g US for American English D for German F for French JA for Japanese etc There may be a different logo for each language the Exchange supports example https exchange oracle com brands ox marketing US logo gif Company Name Yes The Company name of the proxy user established on Oracle Exchange This must be entered exactly the same as it was entered during the registration process on Oracle Exchange If you are unsure of the registered company name it can be found in the Trading Partner Directory on the Oracle Exchange link from the Exchange home page Username Yes The username of the proxy user created on Oracle Exchange This will be used each time an iPro
102. racle Exchange you selected a Select the suppliers you want to download setup information for into iProcurement Each of the suppliers you select at this point will be made available to your iProcurement users as an external supplier a Select Sync Suppliers button This will return you to iProcurement and display a confirmation message letting you know the setup information for the suppliers you selected was successfully saved Creating direct punchout suppliers When you have a supplier you would like to setup a direct punchout to you can setup their punchout information in this section This option requires additional development efforts by the supplier on their web site If you are going to do a direct punchout to a supplier site they must be able to receive the login request detailed in the solution section of this document They must also be able to generate a login response in the format iProcurement expects as well as be able to generate and send a shopping cart in the format supported by iProcurement Once a supplier has met these criteria on their site use this functionality to setup the parameters and enable them as an external punchout supplier in Procurement a Navigate to the iProcurement eContent Manger home page a Select the link to Create Direct Punchout Suppliers a Enter information in the following fields to complete the setup Table 3 2 Direct Punchout Setup Field Name Required Description
103. rform on Exchange 6 Once the buyer has returned to the Exchange additional purchases can be made or the buyer can proceed to checkout Steps to Perform on Exchange Step 1 Register your company on Exchange To enable buyers on Exchange to access your site you must exist as a registered company on the Exchange if you are already registered with Exchange no additional or special type of registration is necessary To register with Exchange 1 Navigate to the URL of the Exchange with which you wish to participate 2 From the Marketplace home page click the Sign me up link 3 On the Exchange Registration page click the appropriate radio button selection and then click Proceed to Registeration 4 Use the online help pages available by clicking the Help icon at the top of the page to guide you through the remainder of the registration process Step 2 Create code mappings If you plan to integrate the Exchange with your ERP system and web catalog it is necessary to map the codes which are used within Exchange to the codes that are used for items in your catalog This allows Exchange to recognize codes that are passed to it by your site when users have finished selecting the items they wish to purchase You need to create mappings for currency codes and unit of measurement codes Note that Currency Code and Unit of Measurement are only two of the codes which can be mapped Mapping values you specify are also used for ot
104. rlencoded The data is sent back in the PunchOutOrderMessage XML document which is url encoded PunchOutOrderMessage XML sample lt xml version 1 0 encoding UTF 8 gt lt cXML version 1 1 007 xml lang en US payloadID 99999 timestamp 2000 08 15 gt lt Header gt lt From gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt lt Credential gt lt From gt lt To gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt Defining an Oracle iProcurement Punchout 3 23 lt Credential gt lt To gt lt Sender gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt lt Credential gt lt UserAgent gt Workchairs cXML lt UserAgent gt lt Sender gt lt Header gt lt Message gt lt PunchOutOrderMessage gt lt BuyerCookie gt ICX lt BuyerCookie gt lt PunchOut OrderMessageHeader operationAllowed edit gt lt Total gt lt Money currency USD gt 112 4 lt Money gt lt Total gt lt PunchOutOrderMessageHeader gt lt ItemIn quantity 3 gt lt ItemID gt lt SupplierPartID gt 5555 lt SupplierPartID gt lt ItemID gt lt ItemDetail gt lt UnitPrice gt lt Money currency USD gt 763 20 lt Money gt lt UnitPrice gt lt Description xml lang en gt Leather reclining chair lt Description gt lt UnitOfMeasure gt EA lt UnitOfMeasure gt lt Classification domain UNSPSC gt 51333
105. rying to login into the supplier site lt userName gt Y The name of the iProcurement user e g Terry Green lt userPhone gt N The iProcurement user s phone number lt userEmail gt N The iProcurement user s email address lt companyName gt N The iProcurement user s company s name lt companyDUNS gt N The company s DUNS number lt contactName gt N Name of Procurement company s contact lt contactPhone gt N The company s contact s phone number lt returnUrl gt Y The URL where iProcurement expects to receive the login response document PunchOutSetupRequest dtd http xml cXML org schemas cXML 1 1 007 cXML dtd PunchOutSetupResponse dtd http xml cXML org schemas cXML 1 1 007 cXML dtd PunchOutOrderMessage dtd http xml cXML org schemas cXML 1 1 007 cXML dtd Oracle iProcurement Punchout DTDs B 11 PunchOutOrderMessage dtd B 12 Oracle Exchange Punchout Guide C Sample Oracle iProcurement XML Documents OEXLoginRequest This document is also used as the Supplier Sync up Login the only difference being that the action is suppSync instead of shopping Sample XML lt xml version 1 0 gt lt request gt lt header version 1 0 gt lt login gt lt username gt buyerl lt username gt lt password gt WELCOME lt password gt lt login gt lt action gt shopping lt action gt lt language gt US lt language gt lt userArea gt lt operatingUnit g
106. sequence number to match a request and response in an asynchronous communication Not currently used lt action gt Y For the OEXLoginRequest either shopping or suppSync Shopping if the request is to add items to a shopping cart suppSync if the iProcurement administrator is downloading new punchout suppliers from Oracle Exchange to iProcurement For the LoginResponse the value should be LOGIN_ RESPONSE This is the response returned to iProcurement from either Oracle Exchange or the supplier site For the OrderLinesDataElements shopping cart this is SHOPPING_RESPONSE Included in the XML that returns the shopping cart to iProcurement For the supplierSyncUpResponse this is SYNC_ RESPONSE Included in the XML that is returned to iProcurement from Oracle Exchange during the initial setup of Exchange punchout suppliers lt cookie gt N Required attribute is the cookie name lt language gt Y Language code for the site level user lt userName gt Y The site level user name on Oracle Exchange Created when the proxy user is created on Oracle Exchange lt password gt Y Password associated with the site level username above lt SessionID gt N Oracle Exchange session ID if the session is already established B 2 Oracle Exchange P unchout Guide OEXLoginRequest dtd Table B 1 pomxmirr dtd Elelments Field Required Comment lt returnMessage gt N Valid return codes are S success E
107. serCompany gt lt companyName gt ABC Incorporated lt companyName gt lt companyDUNS gt 12345 lt companyDUNS gt lt userCompany gt lt userInfo gt lt returnURL gt http iProcurment company com oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping lt returnURL gt lt loginInfo gt lt body gt lt response gt The supplier site generates a response in the form of a LinkResponse XML document that contains the login URL with session information for the supplier s site LinkResponse XML sample lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt lt header gt lt body gt lt loginInfo gt lt loginURL gt http www suppliersite com orders SupplierShopping jsp sessionID 123 lt lLoginURL gt lt loginInfo gt lt body gt lt response gt The LinkResponse is returned to the PunchoutCallback jsp Oracle Exchange then uses the LinkinMainBean java class to generate the LoginResponse XML and sends Defining an Oracle iProcurement Punchout 3 13 it back to iProcurement using the return URL The XML document contains the session aware URL which the iProcurement user will use to connect to the supplier site LoginResponse XML sample lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt LOGIN_RESPONSE lt action gt lt header gt lt body gt lt loginI
108. ss the image You can add a brief description of your catalog and the items you sell in the Company Description field When you have enter the required information click the Apply Changes button On the Confirmation page click Return to Configure Catalog Punchout Step 2 Test Punchout Definition After you have configured your punchout definition you should test it You can test your definition while still within the configuration process This allows you to test your definition before opening the punchout to users To test your punchout you must have the Create Add to Cart Order authorization 1 From the Configure Catalog Punchout page click the Click here to test your punchout link The Test Catalog Punchout page appears 2 Click the Begin Punchout Test Now button If your definition has been correctly defined you will be able to punchout to your site and select items from your catalog Once you have selected several items return to Oracle Exchange by clicking the Return to Oracle Exchange button or whatever name you used when creating your redirect earlier Verify your shopping cart contents have been successfully added to an Oracle Exchange shopping cart Once you have done this you should empty the cart so you don t create a purchase order accidentally If you receive an error message at any point in the punchout process described above make a note of the message to assist in resolving the problem
109. supplier site The user will be presented with the supplier s web site and allowed to fill and return a shopping cart to iProcurement To set this up complete the following Oracle Exchange Setups a Setup Company on Oracle Exchange a Setup Site Level User for iProcurement on Oracle Exchange iProcurement Setups a Setup Profile Options Maintain Supplier Hubs a Download Punchout Enabled Suppliers from Hub a Resequence punchout display optional a Maintain punchout suppliers ongoing Oracle eCommerce Gateway Setups a Setup Trading Partner a Setup Conversion Code Note The setup processes listed above are detailed in the subsequent section Model 5 Punch out directly to Supplier XML In this case the Procurement user clicks a link to a supplier site from the Procurement home page and is taken directly to the suppliers site Once there they can add items to a shopping cart and return the cart to iProcurement to complete the requisitioning process To set this up complete the following iProcurement Setups Defining an Oracle iProcurement Punchout 3 33 Installation Implementation Steps n n n n Setup Profile Options Create Direct Punchout Suppliers Resequence punchout display optional Maintain punchout suppliers ongoing Oracle eCommerce Gateway Setups n n Setup Trading Partner Setup Conversion Code Note The setup processes listed above are detailed in the subsequent section
110. t 204 lt operatingUnit gt lt shipTo gt V1 New York City Sample Oracle iProcurement XML Documents C 1 OEXLoginRequest lt shipTo gt lt deliverTo gt V1 New York City lt deliverTo gt lt userArea gt lt header gt lt body gt lt loginRequest gt lt userInfo gt lt userName gt Green Mr Terry lt userName gt lt appUserName gt TGREEN lt appUserName gt lt userContactInfo gt lt userEmail gt tgreen vision com lt userEmail gt lt userContact Info gt lt userInfo gt lt companyInfo gt lt companyName gt IP lt companyName gt lt companyInfo gt lt reqToken gt template tpn _action addToOrder _function addToOrder _reqSessionId 0 _ reqHeaderId 0 _emergencyReq N _itemSourceId 1001 lt reqToken gt lt returnURL gt http apl00jvm us oracle com 4632 oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping lt returnURL gt lt loginRequest gt lt body gt lt request gt C 2 Oracle Exchange Punchout Guide OEXLoginRequest with optional extended data OEXLoginRequest with optional extended data Sample XML lt xml version 1 0 gt lt request gt lt header version 1 0 gt lt login gt lt username gt buyerl lt username gt lt password gt WELCOME lt password gt lt login gt lt action gt shopping lt action gt lt language gt US lt language gt lt userArea gt lt operatingUnit gt 204
111. t userEmail gt lt userContact Info gt lt userInfo gt lt companyInfo gt lt companyName gt IP lt companyName gt lt companyInfo gt lt partySitelId gt 2963 lt partySiteld gt lt reqToken gt template tpn _action addToOrder _function addToOrder _reqSessionId 0 _reqHeaderId 0 _emergencyReq N _itemSourcelId 1001 lt regToken gt lt returnURL gt http iprocurement company com oa_ servlets oracle apps icx por punchout PunchOut Servlet callBack shopping lt returnURL gt lt loginRequest gt lt body gt lt request gt Note The DTDs are described in detail in the Appendix A of this document Some additional optional user data can also be sent to Oracle Exchange if the punchout was setup in iProcurement to send it The sample XML document for a login request with additional optional user data is attached in Appendix B of this document For details on how to include the additional information see the Installation and Implementation section Defining an Oracle iProcurement Punchout 3 11 Oracle Exchange receives the OEXLoginRequest with the LinkinLogin jsp and executes the LinkinAuthBean java class to authenticate the iProcurement user 2 After the Procurement user is authenticated on Oracle Exchange the Exchange uses LinkinLogin jsp to establish a secure connection to the supplier site It calls Oracle SSL APIs if required based on the supplier s setup wh
112. t Kareem s Corporation lt supplierName gt lt supplier gt lt orderLine gt lt OrderLinesDataElements gt lt body gt lt response gt Note See Appendix A for the DTD of the shopping cart sent back from Oracle Exchange to iProcurement See Appendix B for a sample XML document shopping cart sent back from Oracle Exchange to iProcurement 5 iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups in Oracle Applications are referenced to do the required data conversion mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement And if the lock_item_flag stored in the ICX_POR_ITEM_SOURCES table was set during configuration of the punchout for this Exchange then the user will not be able to make any changes to the items returned from Oracle Exchange The requisition then goes through the normal workflow and approval processes configured in iProcurement Note See the Installation and Setup section of this chapter for details on setting the lock_item_flag and using the EDI setups to create data maps Model 3 Punch out from Oracle Procurement to Supplier via Oracle Exchange XML Oracle iProcurement users can also punch out to an XML supplier through Oracle Exchange Using Oracle Exchange for the punchout simplifies the initial setup process and as the authentication and maintenan
113. t N Up to 15 additional attributes can be included with each item e15 gt in the shopping cart LinkRequest dtd See the Ddining an OracleExchangePunchout chapter for details on this XML document LinkResponse dtd See the Ddining an OracleExchangePunchout chapter for details on this XML document SupplierSyncUpResponse dtd lt Header SupplierSyncUpResponse dtd 115 0 2001 02 02 01 15 09 mahmad noship gt lt ENTITY common SYSTEM pomxmlrr dtd gt lt ENTITY body lt ELEMENT body supplier gt gt lt ELEMENT supplier supplierPartylId supplierImageUr1l supplierLanguageSpecificInfo gt lt ELEMENT supplierLanguageSpecificInfo language supplierName supplierDescription supplierKeywords gt lt ELEMENT supplierName PCDATA gt lt ELEMENT supplierDescription PCDATA gt lt ELEMENT supplierKeywords PCDATA gt lt ELEMENT supplierPartyId PCDATA gt ENT supplierImageUrl PCDATA gt n Oracle iProcurement Punchout DTDs B 9 SupplierLoginRequest dtd Sresponse Table B 5 SupplierSyncUpResponse dtd Elements Field Required Comment lt language gt Y Language of the information being retrieved lt supplierName gt Y The supplier s company name in the specified language the Oracle Exchange registered name of the company lt supplierDescription gt Y The supplier s description in the specified language entered by the supp
114. t gt lt PunchOutSetupRequest operation create gt lt BuyerCookie gt 12345678 lt BuyerCookie gt lt Extrinsic name User gt KBENJAMI lt Extrinsic gt lt BrowserFormPost gt lt URL gt http ap903sun us oracle com 6290 orders PunchoutCallback jsp app buying lt URL gt lt BrowserFormPost gt lt Contact gt Sample Oracle iProcurement XML Documents C 11 PunchOutSetupResponse cXML lt Name xml lang en US gt KareemAndreBen jami lt Name gt lt Email gt dumas4 yahoo com lt Email gt lt Contact gt lt PunchOut SetupRequest gt lt Request gt lt cXML gt PunchOutSetupResponse cXML Sample XML lt xml version 1 0 gt lt cXML payloadID 2000 08 15 timestamp 2000 08 15 gt lt Response gt lt PunchOut SetupResponse gt lt StartPage gt lt URL gt http www oracle com orders SupplierShopping jsp sessionID 123 lt URL gt lt StartPage gt lt PunchOut SetupResponse gt lt Status code 200 text success gt lt Response gt lt cXML gt PunchOutOrderMessage cXML Sample XML lt xml version 1 0 encoding UTF 8 gt lt cXML version 1 1 007 xml lang en US payloadID 99999 timestamp 2000 08 15 gt lt Header gt lt From gt lt Credential domain DUNS gt lt Identity gt 888 lt Identity gt lt Credential gt lt From gt lt To gt lt Credential domain DUNS gt C 12 Oracle Exchange Punchout Guide PunchOutOrderMessage c
115. tServlet servlet is executed First this calls Oracle SSL APIs to establish secure connection to Oracle Exchange These APIs request a Certification Authority Certificate from the Oracle Exchange site and compare that to Certificates stored in the iProcurement After a secure connection between the iProcurement server and Oracle Exchange is established PunchOutServlet then generates the OEXLoginRequest XML document which contains user details and login credentials for Oracle Exchange as well as a return URL Once generated this is passed to Oracle Exchange LinkinLogin jsp through the secure connection Oracle Exchange uses the LinkInAuthBean java class to authenticate the iProcurement user Once authenticated Oracle Exchange uses the PunchOutLoginBean java class to initiate a connection with the supplier site If required based on the setup of the supplier Oracle Exchange will request a Certification Authority Certificate from the supplier site and compare that to Certificates stored in Oracle Exchange Once a secure connection is established the PunchOutLoginBean java class will generate and deliver the LinkRequest XML document to the supplier site which contains the iProcurement return URL The supplier site generates a response in the form of a LinkResponse XML document which contains the login URL and session information for the supplier s site Oracle Exchange uses the LinkinMainBe
116. talog content and pricing are available Obtaining information directly from a supplier using a punchout ensures that the product information is accurate and up to date which eliminates downstream inefficiencies due to incorrect product or pricing information The burden of maintaining the hosted catalog is removed from the buying organization which reduces both catalog maintenance and data storage costs Products which previously had been difficult to maintain within a locally hosted catalog can now be purchased from within the buyer s ERP system procurement software or directly from the exchange Punchout does not suit every product or supplier however By allowing the supplier to host catalog information locally the buyer or buying organization must work closely with the supplier to control the content and pricing of products 1 2 Oracle Exchange Punchout Guide Table 1 1 Supplier Hosted versus Locally Hosted Catalogs Supplier Hosted Catalogs Best suited for products requiring a high degree of configuration such as computer hardware specialized services or products with fluctuating prices Locally Hosted Catalogs Best suited for commodity type items such as office supplies products with pre negotiated or stable prices MRO items or products built to a predetermined specification such as mass produced mechanical parts Supplier closely manages the content presented to buyers Punchout Models Su
117. td cccccccccceccsesescsceeeseececsceeseseececesseseseececssensneseeenes A 2 Shopping Cart DTD pom carts dtd snpiisii nasisa A 2 POMXMERR DTD cid ili Bio seca ES ete oe lSS ts fag asap es Donates OO EO A 2 SHOPPING CARY DI D cic OEE EEA ARAA EELE ORNE EN E A 4 Oracle iProcurement Punchout DTDs Common DTD file for all Request Response DTDs pomxmlrr dtd 0 0 0 0 cece B 1 OEXLoginRequ st dtd ec nisou i ar cots ee ea e sibel eee EAE E iE S E lesa danir tia deo Eia B 3 EosinR sp ns dtd s rana aaee sate lenge inten St e aa AEE aooaa EER SRR OEE EEEo ESTE ES B 5 OrderLinesDataEleme ts dtd rinasa ia ea a ai aiei ans B 5 LinkRequ st dtd vrsi eck nea seas ie ad adi Gee Wotan E a las B 9 Tink Response dtd srren E aeae Nene ane en E Ee Caters utids ovens e Nts coat EERE EOR ANE ae EEE AER o B 9 SupplierSyncUpResponse dtd ccccccccsssssesesesesssssesesessssssesesessssesesesesesssesesesesssesesesssesesesees B 9 SupplierLoginRequest dtd cccccsesesessscssesesescsesssesesescscsesesesescscsssesescscscssseseecscsssnsseseseees B 10 PunchOutSetupRequest dtd o cccccccccssesesessscsesesesescscsssesesescscsssesesescscsssesescscsessseseecscsssnsseseeeees B 11 PunichOutSetiipResponse dtd i ccc irinin ena a A a a a Mutts B 11 PunchOutOrderMessage dtd v vicsiccccccsissneeesessievueasesssssveavasinesoneeaticscesevebinnsvcetebvensnvevssnenscrsnsteene coves B 11 C Sample Oracle iProcurement XML Documents OEXLogin Request v
118. te11 eae fe moe TA ice sat eau nak eae hese a oe de eae ees T tribute1 tribute2 tribute3 tribute4 tribute5 tribute6 tribute7 tributes tribute9 tributel0d tributell tributel2 tributel3 tributel4 tributel5 tribute6 attribute7 attribute8 attribute9 attributel2 attributel3 attributel4 PCDATA PCDATA PCDATA PCDATA PCDATA PCDATA PCDATA PCDATA PCDATA Oracle Exchange Punchout DTDs A 5 SHOPPINGCART DTD A 6 Oracle Exchange Punchout Guide B Oracle iProcurement Punchout DTDs Common DTD file for all Request Response DTDs pomxmirr dtd lt Header pomxmlrr dtd 115 0 2001 02 02 01 16 04 mahmad noship gt lt common dtd file for all the request response dtds gt lt ENTITY message header body gt gl both response and request are modeled similarly with a header and a body lt ENTITY body lt ELEMENT body ANY gt gt any request can override this body element gt lt ENTITY request lt ELEMENT request message gt gt lt I gt request dtd can instantiate the request element and the response dtd can instantiate the response element gt lt ENTITY response lt ELEMENT response message gt gt lt see request entity gt lt ELEMENT header requestID login action return cookies language userArea gt lt ATTLIST header version
119. ter The cxml urlencoded parameter used during the return of the shopping cart lets iProcurement know this is a cXML shopping cart Since iProcurement cannot process the PunchOutOrderMessage cXML document PunchOutServlet receives and re directs the shopping cart to Oracle Exchange First the PunchOutServlet establishes a secure and trusted connection with the Exchange and then it forwards the cXML shopping cart On Oracle Exchange PunchoutMainBean and ExportOrder are executed to convert the shopping cart from cXML to XML and also do the code conversions UOM and currency defined on the Oracle Exchange This shopping cart is then returned to iProcurement through the secure connection iProcurement executes the AppsManager java class to add the items to the requisition The EDI setups in Oracle Applications are referenced to do the required data conversion mapping between the external code values coming from the supplier and the internal code values setup in Oracle iProcurement If the lock_item_flag was not set during configuration of the punchout for this Exchange then the user will be able to make any changes to the item returned from Oracle Exchange The requisition then goes through the normal workflow and approval processes configured in iProcurement 3 18 Oracle Exchange Punchout Guide Supplier Porta Procurement Sener The Procurement user starts on their homepage which
120. the document is either url encoded or Base 64 encoded and that the parameter name for the HTTP Post is either cxml urlencoded or cxml base64 respectively Once the transaction is returned to the Exchange the selected items will then be added to the shopping cart and the buyer can complete the purchase process XML Punchout Shopping Cart document example An example XML Punchout Shopping Cart transaction file is shown below lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt lt action gt lt header gt lt body gt lt OrderLinesDataElements gt lt orderLine gt lt item quantity 1 gt lt itemNumber gt lt supplierItemNumber gt lt itemID gt B1324 lt itemID gt lt supplierItemNumber gt lt manufacturerItemNumber gt lt itemID gt X456 lt itemID gt lt manufacturerName gt Bob s Office Supplies Factory lt manufacturerName gt lt manufacturerItemNumber gt lt itemNumber gt lt itemDescription gt Whiteboard 6 x 4 lt itemDescription gt 2 20 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site lt unitOfMeasure gt lt supplierUnitOfMeasure gt lt supplierUOMType gt Each lt supplierUOMType gt lt supplierUnitOfMeasure gt lt unitOfMeasure gt lt hazardClass gt UVW456 lt hazardClass gt lt item gt lt category gt lt categoryCode gt MAS 736 lt categoryCode gt lt category gt lt price gt lt curr
121. the supplier s setup which requests the Certification Authority CA digital certificate public key from the supplier site This is compared to certificate authorities setup by the Oracle Exchange operator Once certified a secure connection is opened between Oracle Exchange and the supplier site The PunchOutLoginBean java class then generates the PunchOutSetupRequest cXML document It includes the site level user name and password that the supplier requires to access their web store Note The site level user name is stored and maintained on Oracle Exchange by the supplier There is no need for the iProcurement sysadmin to store this information The PunchOutSetupRequest includes the iProcurement return URL as well as user and company details from the iProcurement user that were included in the initial OEXLoginRequest from iProcurement to Oracle Exchange PunchOutSetupRequest cXML sample lt xml version 1 0 encoding ISO 8859 1 gt lt DOCTYPE cXML SYSTEM http xml cxml org schemas cXML 1 1 007 cXML dtd gt lt cXML version 1 1 007 xml lang en US payloadID Wed Apr 04 12 52 46 GMT 08 00 2001 timestamp Wed Apr 04 12 52 46 GMT 08 00 2001 gt lt Header gt lt From gt lt Credential domain DUNS gt lt Identity gt 654321 lt Identity gt lt Credential gt lt From gt lt To gt lt Credential domain DUNS gt lt Identity gt 123456 lt Identity gt lt Cr
122. ting direct punchout suppliers 3 39 maintaining punchout suppliers 3 41 overview 3 33 resequencing the punchout display 3 42 setting up profile options 3 36 setting up your code conversions 3 43 setting up your trading partner 3 42 punchout process 3 26 Oracle iProcurement to supplier via Oracle Exchange cXML punchout model 1 5 3 16 installation implementation downloading punchout enabled suppliers from hub 3 38 maintaining punchout suppliers 3 41 maintaining supplier hubs 3 36 overview 3 33 resequencing the punchout display 3 42 setting up a site level user on Oracle Index 1 Exchange 3 35 setting up profile options 3 36 setting up your code conversions 3 43 setting up your company on Oracle Exchange 3 34 setting up your trading partner 3 42 punchout process 3 17 Oracle iProcurement to supplier via Oracle Exchange XML punchout model 1 4 3 7 installation implementation downloading punchout enabled suppliers from hub 3 38 maintaining punchout suppliers 3 41 maintaining supplier hubs 3 36 overview 3 33 resequencing the punchout display 3 42 setting up a site level user on Oracle Exchange 3 35 setting up your code conversions 3 43 setting up your company on Oracle Exchange 3 34 setting up your trading partner 3 42 punchout process 3 9 Oracle XML Parser URL for downloading 2 7 P Punchout definition 1 1 Punchout models 1 3 Punchout software requirements 1 6 R Reordering using
123. tion Implementation Steps After the registration information is submitted the approval of the company account is not automatic Each Oracle Exchange operator can decide whether or not to approve or reject a company s registration The time for approval of an account on the Exchange will vary by operator Setting up a site level user for iProcurement on Oracle Exchange When the company account is approved on Oracle Exchange then a proxy user must be setup in Oracle Exchange for the company created in the above step a On the Oracle Exchange home page click Registration a Select I think my company is already registered and I want to register myself as a new user a Step 1 Find Your Company you are registering as a user of the company account created in the step above On this screen search for and select the company name you previously created a Step 2 Personal Information enter the personal information for this user account You may want to specify the name as IP User or Proxy User or some variation a Step 3 Legal Agreement this agreement should have been reviewed and accepted on behalf of the company during the registration of the company account It is provided during the user registration for informational purposes a Step 4 Review and Submit teview all the information that has been entered during the registration process Once verified submit the registration for approval by the company adminis
124. tion with the supplier site If required based on the setup of the supplier Oracle Exchange will request a Certification Authority Certificate from the supplier site and compare that to Certificates stored in Oracle Exchange Once a secure connection is established the PunchOutLoginBean java class will generate and deliver the LinkRequest XML document to the supplier site which contains the iProcurement return URL The supplier site generates a response in the form of a Defining an Oracle iProcurement Punchout 3 17 LinkResponse XML document which contains the login URL and session information for the supplier s site Oracle Exchange uses the LinkinMainBean java class to generate the LoginResponse XML document that is returned to iProcurement Upon receipt of this LoginResponse XML document by iProcurement the iProcurement user s browser is re directed to the login URL provided by the supplier The Oracle Exchange involvement in this process is transparent to the iProcurement user The user can shop the supplier s site and add items to a shopping cart on the supplier site When the user finishes adding items to their shopping cart the supplier executes a program which takes the items in the shopping cart and creates a PunchOutOrderMessage cXML document with the shopping cart item details This url encoded document is posted to the Procurement return URL with the cxml urlencoded parame
125. trator The company administrator usually the person that registered the company in the previous step must approve this user on Oracle Exchange To approve this user so the proxy account is active on the exchange the company administrator should Login to the Oracle Exchange where the company s account was created a Navigate to the Admin or Company Account tab Under the Users heading click Approve Users a Select the user and click Approve button a Select the user again and click the Assign Job Functions button a Under the Job Functions heading choose Select and add existing job functions a At this point the administrator is presented with a list of possible job functions to be assigned to the Procurement proxy user If you want your company employees to be able to shop on Oracle Exchange but only from those catalogs that have buyer specific Defining an Oracle iProcurement Punchout 3 35 Installation Implementation Steps pricing available for your company select the following job functions Buyer with Restricted Pricing View At this point you have completed all the setup necessary on Oracle Exchange Note Any job functions assigned to this user on Oracle Exchange will be available to all Procurement users that punch out from iProcurement to Oracle Exchange Oracle iProcurement Setup Steps Now that you have created company and user accounts on Oracle Exchang
126. ty element will have the DUNS number NAME If there is no DUNS number the identity element will have the name of the company on Oracle Exchange lt To gt lt Credential gt Required Character Identifies the supplier organization The rules determining the identity attribute are the same as above lt Sender gt lt Credential gt Required Character Identifies the Exchange The domain attribute identifies the Exchange domain value e g OracleExchange com The Shared Secret attribute is the password set by the supplier for this exchange lt Sender gt lt UserAgent gt Required Character Specifies the name of the Exchange e g OracleExchange com lt BrowserFormPost gt Required Character This is the URL to which lt URL gt your site will pass the shopping cart XML document when the user exits from your web catalog lt Extrinsic Required Character This is the username of the name User gt user on the Exchange 2 14 Oracle Exchange Punchout Guide Steps to Perform at Your Web Site Table 2 4 cXML PunchOutSetupRequest Data Elements Hement Required Type Comment lt Contact gt Optional This Name and Email elements within the contact element are passed to the Supplier Note The table above is not a complete list of all elements included in the cXML PunchOutSetupRequest document For DTD details on the cXML transaction above see http www cXML org Your site m
127. ty gt lt supplierUnitOfMeasure gt lt unitOfMeasure gt lt item gt lt category gt lt categoryCode categoryCodeldentifier SPSC gt Ball Point Pens lt categoryCode gt lt category gt lt price gt lt currency gt USD lt currency gt lt unitPrice gt 100 0 lt unitPrice gt lt price gt lt supplier gt lt supplier DUNS gt 2820 lt supplierDUNS gt lt supplierName gt Kareem s Corporation lt supplierName gt lt supplier gt lt orderLine gt Sample Oracle iProcurement XML Documents C 7 LinkRequest lt OrderLinesDataElements gt lt body gt lt response gt LinkRequest See PunchoutRequest DTD in Appendix A for details on this XML document LinkResponse See Punchout Response DTD in Appendix A for details on this XML document SupplierSyncUpResponse Sample XML lt xml version 1 0 gt lt response gt lt header version 1 0 gt lt action gt SYNC_RESPONSE lt action gt lt header gt lt body gt lt supplier gt lt supplierPartylId gt 2817 lt supplierPartyId gt lt supplierImageUr1 gt http www yahoo com lt supplierImageUr1 gt lt supplierLanguageSpecificInfo gt lt language gt F lt language gt lt supplierName gt TestCo lt supplierName gt lt supplierDescription gt Yahoo Life Nothing Pen lt supplierDescription gt C 8 Oracle Exchange Punchout Guide SupplierLoginRequest lt supplierKeywords gt lt supplierLan
128. ur web catalog with Exchange 1 Register your company with Exchange if necessary Map your currency codes if necessary Map your unit of measurement codes if necessary Obtain and install an XML Parser fo FY KN Create necessary dtds see Appendix B for details if using Oracle Native XML see http www cXML org if using cXML 6 Determine how you are going to validate user access using the information passed to you 7 Determine any additional processing you may want to perform using the information passed to you 8 Determine what method to use when returning buyers to Exchange 9 Create the URL to process transaction validation 10 Create code to process Defining an Oracle Exchange Punchout 2 31 Oracle Exchange Punchout Setup Checklist 11 12 13 14 XML Punchout Request PunchOutSetupRequest XML Punchout Response PunchOutSetupResponse XML Punchout Shopping Cart PunchOutOrderMessage Define the punchout information for your web store on Exchange Test your punchout Define your search keywords for every language your site supports Enable your punchout definition 2 32 Oracle Exchange Punchout Guide 3 Defining an Oracle iProcurement Punchout This chapter explains the punchout process used by Oracle iProcurement for each of the punchout models described in the Overview chapter This chapter includes both an architectural overview of the model and the steps to implement each model
129. user is restricted to only being able to view items with the iProcurement company s pre negotiated pricing Typically they would not access Oracle Exchange functionality that allows them to shop open market catalogs create or bid in auctions use Supply Chain Collaboration tools or Product Design collaboration tools To set this up complete the following Oracle Exchange Setups Setup Company on Oracle Exchange a Setup Site Level User for iProcurement on Oracle Exchange iProcurement Setups a Setup Profile Options Maintain Supplier Hubs a Resequence punchout display optional Maintain punchout suppliers ongoing Oracle eCommerce Gateway Setups a Setup Trading Partner Setup Conversion Code 3 32 Oracle Exchange Punchout Guide Installation Implementation Steps Note The setup processes listed above are detailed in the subsequent section Model 3 amp 4 Punch out from Oracle Procurement to Supplier via Oracle Exchange XML or cXML When you setup a punchout from iProcurement to a supplier s web store it allows iProcurement users to search and add items to a shopping cart on the suppliers web site and then bring those details back to iProcurement to complete the requisition process and have a purchase order created The iProcurement user clicks a link to the supplier site on their iProcurement home page iProcurement will then authenticate to Oracle Exchange and Oracle Exchange will authenticate to the
130. userCompany companyName companyDUNS contactName contactPhone gt userPhone PCDATA gt userEmail PCDATA gt companyName PCDATA gt companyDUNS PCDATA gt Oracle Exchange Punchout DTDs A 1 XML Punchout Response pomlogns dtd lt ELEMENT contactName PCDATA gt lt ELEMENT contactPhone PCDATA gt lt ELEMENT returnURL PCDATA gt Scommon Srequest XML Punchout Response pomlogns dtd See also pomxmlrr dtd for common DTD elements lt ENTITY common SYSTEM pomxmlrr dtd gt lt ENTITY body lt ELEMENT body loginInfo gt gt lt ELEMENT loginInfo loginURL gt lt ELEMENT loginURL PCDATA gt Scommon 2 2 Sresponse Shopping Cart DTD pom carts dtd See also pomxmlrr dtd and shoppingcart dtd for common and included elements lt ENTITY common SYSTEM pomxmlrr dtd gt lt ENTITY shoppingcart SYSTEM shoppingcart dtd gt sshoppingcart lt ENTITY body lt ELEMENT body OrderLinesDataElements gt gt Scommon Sresponse POMXMLRR DTD lt Header pomxmlrr dtd 115 2 2001 02 05 18 42 11 mangupta noship gt lt common dtd file for all the request response dtds gt lt ENTITY message header body gt lt both response and request are modeled similarly with a header and a body gt lt ENTITY body lt ELEMENT body ANY gt gt lt any request can override this body element gt lt ENTITY
131. when it is displayed to iProcurement users a Click the Update button to re order the list Note After supplier setup the documents exchanged between iProcurement and the supplier can be seen in the debug log file and jvm error log file The location of debug log file is determined in ssp_init txt Oracle eCommerce Gateway Setup Steps a Setup Trading Partner a Setup Conversion Code Setting up your trading partner Navigate to eCommerce Gateway gt Setup gt Trading Partner Trading Partner Enter the Supplier name here The trading partner supplier first needs to be defined in Oracle Purchasing Supplier details will then default here These are the suppliers of the items selected from Oracle Exchange 3 42 Oracle Exchange Punchout Guide Installation Implementation Steps Important The site for this supplier must have the EDI Location set to either the DUNS number for this trading partner if they have a DUNS number and that DUNS number is associated with this trading partner on the Exchange or the Oracle Trading Partner id from the exchange if this is a punchout to the Exchange or an agreed unique reference that the supplier will return within the lt SupplierDUNS gt tag if this is a punchout to a supplier Setting up your code conversions This setup maps the Supplier side codes to Oracle iProcurement n n n Navigate to eCommerce Gateway gt Setup gt Code Conversion gt
132. wn user s needs This information is not downloaded from Oracle Exchange again Additional setup information maintained by the supplier on Oracle Exchange such as their punchout URL site level userid and password will remain on the Exchange This is referenced each time a punchout occurs so the iProcurement administrator does not have to maintain any supplier specific login details themselves Punchout Process The supplier is automatically setup in Oracle iProcurement as a punchout supplier in the above step and the Supplier s link is displayed on the iProcurement homepage When a user clicks the link to a supplier the PunchOutServlet servlet is executed First this calls Oracle SSL APIs to establish secure connection to Oracle Exchange These APIs request a Certification Authority Certificate from the Oracle Exchange site and compare that to Certificates stored in iProcurement After a secure connection between the iProcurement server and Oracle Exchange is established PunchOutServlet then generates the OEXLoginRequest XML document which contains user details and login credentials for Oracle Exchange and a return URL Once generated this is passed to Oracle Exchange LinkinLogin jsp through the secure connection Oracle Exchange uses the LinkInAuthBean java class to authenticate the iProcurement user Once authenticated Oracle Exchange uses the PunchOutLoginBean java class to initiate a connec
133. y the supplier lt category Y Specifies the category used to classify this item Valid categoryCodeldentifier attributes are SPSC SUPPLIER or BUYER If code is not SPSC gt specified SPSC is assumed lt categoryCode gt Y Category code value lt currency gt N The currency the price is specified in lt unitPrice gt Y The price per unit of the item lt supplierDUNS gt Y The supplier s DUNS number Used to get supplier name lt supplierTradingPartne and supplier site information in iProcurement rCode gt Either lt supplierDUNS gt or lt supplierTradingPartnerCode gt must be provided in the DTD lt supplierTradingPartnerCode gt is used if the supplier does not have a DUNS number and this element should be populated with a unique alphanumeric code which the buyer will use to identify the internal supplier code in their ERP system lt supplierName gt Y The supplier s company name This is validated against vendors defined in iProcurement lt supplierSite gt N Supplier s site as defined in iProcurement lt supplierNumber gt N Supplier number as defined in iProcurement B 8 Oracle Exchange Punchout Guide SupplierSyncUpResponse dtd Table B 4_ OrderLinesDataElements dtd Elements Field Required Comment lt supplierTradingPartne N Not currently used r gt lt contactName gt N Contact name for supplier lt contactPhone gt N Supplier contact s phone number lt attributel gt lt attribu

Oracle Exchange Punchout.book

Contents

Download Pdf Manuals

Related Search

Related Contents