IBM B2B Direct Implementation Guide - Office of the Chief ... · PDF fileLenovo Confidential 1...

Lenovo Confidential 1 of 41

Direct Lenovo B2B Direct Implementation Guide with cXML, OCI/xCBL, Oracle OAG, SAP EBP, SAP XML, and

RosettaNet Appendices

Release 4.0

Latest Version March 2007


Table of Contents Overview ......................................................................................................................... 4 Purchasing Lenovo PC Products .................................................................................... 4

Lenovo B2B Gateway .................................................................................................. 4 Lenovo B2B Technical Support Help Desk.................................................................. 6 General B2B Requirements, Capabilities and Limitations for purchasing PC-based Products ...................................................................................................................... 6 Using the Punchout/Roundtrip Catalog........................................................................ 7 Ordering PC products via XML .................................................................................. 12 Exception Handling for Purchase Orders................................................................... 12

Boarding and Test Plans ............................................................................................... 13 Buyer-Hosted Catalog Test Plan ............................................................................... 14 Results of Buyer-Hosted Catalog Testing.................................................................. 14 Lenovo Punchout/Roundtrip Test Plan ...................................................................... 15 Results of Punchout/Roundtrip Test .......................................................................... 16

OCI/xCBL Appendix ...................................................................................................... 17 PerfectCommerce...................................................................................................... 17 Local Catalog for PC Products .................................................................................. 17 Roundtrip Catalog for PC Products............................................................................ 17 cXBL ship to and bill to RefNum ................................................................................ 18 xCBL Purchase Order Field Length Limits................................................................. 19 xCBL Order Status and Advance Ship Notice ........................................................... 19 Lenovo Customer OCI/xCBL Boarding Plan.............................................................. 19

cXML Appendix ............................................................................................................. 21 Ariba Supplier Network .............................................................................................. 21 Credentials for non-Ariba cXML customers ............................................................... 21 Local Catalog for PC Products .................................................................................. 21 Punchout Catalog for PC Products ............................................................................ 21 Punchout Catalog Filtering using SupplierPartAuxiliaryID ......................................... 22 Punchout Catalog Filtering using an Extrinsic ........................................................... 23 cXML ship to and bill to AddressIDs .......................................................................... 23 cXML OrderRequest Field Length Limits ................................................................... 23 Data from Purchase Order to Invoice ........................................................................ 24 Steps to Access Order Status and Ship Notice for Ariba Buyer customers. .............. 24 cXML Order Status and Advance Ship Notice ........................................................... 24 cXML Order Status Definitions .................................................................................. 24 Lenovo Customer cXML Boarding Plan..................................................................... 25

Oracle OAG Appendix................................................................................................... 27 Model 2 Process for Purchase Orders....................................................................... 27 Oracle PROCESS_PO_007 Field Length Limits ....................................................... 29 Oracle Advance Ship Notice...................................................................................... 29 Lenovo Customer Oracle OAG Boarding Plan .......................................................... 30

SAP Enterprise Buyer Professional (EBP) XML Appendix ............................................ 31 SAP EBP Process for Purchase Orders .................................................................... 31 SAP EBP Purchase Order Field Length Limits .......................................................... 32 SAP EBP Purchase Order Acknowledgements ......................................................... 33 SAP EBP Advance Ship Notice ................................................................................. 33 Lenovo Customer SAP EBP Boarding Plan............................................................... 33

SAP XML (IDOC) Appendix .......................................................................................... 35


Overview.................................................................................................................... 35 SAP XML (IDOC) Process for Purchase Orders........................................................ 35 SAP XML (IDOC) Purchase Order Field Length Limits.............................................. 36 SAP XML (IDOC) Purchase Order Acknowledgements............................................. 37 Lenovo Customer SAP XML Boarding Plan .............................................................. 37

RosettaNet Order/OrderConfirmation Appendix: ........................................................... 39 Overview.................................................................................................................... 39 RosettaNet 3A4 Field Length Limits .......................................................................... 40 Lenovo Customer Boarding Plan............................................................................... 41


Overview This document describes the business and technical processes on implementing a B2B connection with Lenovo using an e-procurement application that supports cXML, OCI and xCBL, and Oracle OAG. It lists our requirements, our capabilities, and our limitations. While this document cannot provide complete coverage of any specific implementation, it will serve as Lenovo’s guideline. We encourage you to share your B2B Implementation Guide with us as well. This Implementation Guide is a dynamic document and is updated as we continue to learn more and enhance our B2B capabilities. Any requirements, capabilities, limitations, and known issues contained in this document are current as of the date listed on the cover page. To be sure you have the latest Lenovo B2B Implementation Guide, please contact your Lenovo B2B Account Manager.

Purchasing Lenovo PC Products In order to purchase PC products directly from Lenovo, you will first need to become a Lenovo Direct customer If you are not already an Lenovo Direct customer, you will need to talk to an Lenovo Direct Account Manager. Lenovo's e-commerce capability offers many features associated with shopping via the Internet. These attributes include allowing users to simply browse products and prices, configure systems, build and save a shopping cart, as well as initiate online transactions. Online payment methods may include both purchase orders and credit card transactions. The product and price information would be tailored specifically to your organization. Your computer commodity personnel will work with your Lenovo PC Specialist to determine the standard PC products you would like to purchase/lease directly from Lenovo. Here we can integrate your approved standards list, entitled price lists, and suggested product configurations to assist your employees in making a purchasing decision. Many of these unique features can also be restricted to a user based on an approved access level. This would protect unauthorized users from performing certain tasks within the site. As another feature of the online commerce enhancements, Lenovo has added the capability to access your order fulfillment information of both web and non-web based orders. The information is updated daily and is accessible through the ‘My Accounts’ link in the masthead of your e-commerce site. Your Lenovo Direct account team will work closely with the web development team to streamline the web fulfillment experience for your organization. Your account team will identify a single point of contact to provide our web team with the correct products and prices that are to appear on your site. Lenovo has committed to provide an accurate and useful web site for all of our direct customers and to further enhancing the performance and functionality of our extranet sites that will ultimately provide your users with a quicker, personalized, and more user-friendly web experience with Lenovo.

Lenovo B2B Gateway Lenovo has built a B2B gateway in order for our catalog and fulfillment systems to communicate directly with an e-procurement application using cXML, or OCI/xCBL. Our


B2B gateway can provide you with a buyer-hosted catalog (local catalog) or a supplier-hosted catalog. Our B2B catalog (buyer-hosted and supplier-hosted) contains the same products and prices that are on your e-site shopping catalog. Local catalogs can be provided in a variety of formats, including CIF 3.0, spreadsheet, delimited text. With a supplier-hosted catalog, we provide an Lenovo website that can communicate directly with an e-procurement application using cXML, OCI or OAG. This process of shopping on a supplier website, by clicking on a button in your procurement application, is also known as punchout, roundtrip, link out. The preferred method of catalog delivery is punchout/roundtrip, as this provides a much more robust environment for product selection as well as minimizes catalog maintenance required by both the buyer and supplier. The B2B punchout/roundtrip site provides simple catalog shopping functionality including a configurator. The punchout/roundtrip site does not contain any external links. After shopping the catalog, our B2B gateway can then receive cXML, xCBL, and OAG orders directly from your e-procurement application or through a commerce network such as Ariba Supplier Network, PerfectCommerce, and Oracle Exchange. We can also receive orders via email, fax, and EDI. Our B2B gateway can also provide order status and advance ship notice for orders that were sent to our gateway successfully via XML. These XML transactions are sent back to the commerce network or to a URL that you specify.


Lenovo B2B Technical Support Help Desk If at any time you experience technical problems with your Lenovo B2B catalog or ordering functionality, please contact the appropriate help desk number as defined below by geography. A trouble ticket will be opened and your B2B Account Manager will be notified. When contacting the helpdesk, please provide as much detailed information as possible, including steps to recreate the problem, screenshots, logs, date and timestamp, etc. Country Phone Canada and United States 1-866-426-BtoB or

1-866-426-2862 or 1-416-383-7502

Austria, Belgium, China, Costa Rica, Denmark, Finland, France, Germany, Hungary, Iceland, Ireland, Israel, Italy, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland, United Kingdom

00-800-4262-2222

Australia 0011-800-4262-2222 Hong Kong 001-800-4262-2222 Japan 010-800-4262-2222 Korea 001-800-4262-2222

002-800-4262-2222 00-800-4262-22222

Macao, Malaysia, New Zealand, Philippines, Taiwan Singapore 001-800-4262-2222 South Africa 09-800-4262-2222 Country Email ALL [email protected]

Please Note: These phone numbers are for Lenovo B2B technical matters only. Order Status information for PC orders will be provided via XML. For other order related information such as order inquiry, please contact your Customer Service Representative directly. For product, solution, or configuration information, contact your Tele-Sales Representative.

General B2B Requirements, Capabilities and Limitations • Our URL and credential information will be provided during the boarding process as

needed. • If you are an Ariba customer, you can use lenovo.com as our punchout URL as the

URL we specify on Ariba Supplier Network will override it. • We provide 6 and 8-digit UNSPSC commodity codes with our products. We can

provide you with a list of UNSPSC codes that is commonly included in a customer catalog. But we cannot provide a complete list all the UNSPSC codes we will have in your catalog until you determine the products that you would like included in your catalog, and your catalog is built.

• Some of our products do not have an 8 digit UNSPSC code, so we use the closest 6 digit code and add “00” as the 7th and 8th digits.

• We do not provide 9th and 10th digit UNSPSC codes. • We provide UNUOM (unit of measure) for all of our products. All these unit of

measures are “EA” as in “each”. • We evaluate custom fields on an individual basis. • We do not provide images or product detail URLs in our buyer-hosted catalogs. • We do not accept orders that include non-catalog items. • We do not accept change orders or cancel orders. • We do not accept orders that have attachments. • We do not provide market price. • We do not accept order with multiple “ship to” addresses or multiple “bill to”

addresses or multiple payment methods per order • We do not provide lease prices in the catalog. • We do not accept lease prices in the purchase order.

Using the Punchout/Roundtrip Catalog The following pictures are designed to show you the navigation and configurator on our punchout/roundtrip site. The welcome page can display your company logo and the text will read “Welcome to [Your Company]’s On-line Store”.

The Search field appears throughout the site and allows you to search your entitled catalog by description or by part number.



The Fast Access field provides you a fast path to add items to your shopping cart if you already know the part numbers of the items you wish to purchase. Part numbers that are not valid in your entitled catalog will not be recognized.

The following is an example of a product category page. This one provides the entry point for ‘Building Your Own Notebook and will include your contracted-notebook products and related pricing.

Clicking on “Add Options” would direct the user to the valid options available for selection in customizing the selected product model. The following page shows an example of this customization capability.


Each option category has a menu with the list of compatible options. Next to each, you will see a “Help Me Decide” button. This button will launch a new window with additional details on upgrade options for your review. Once the user has selected the desired options, a ‘View Summary” page” is displayed, providing ability to ‘Add to Cart’ or continue with further customization.


After clicking on the “Add to Shopping Cart” button, the Shopping Cart page is displayed. Here you can check order contents - verify the products you selected appear in the cart, the quantity ordered is correct, and the total price displayed is correct.


At this point, you may change quantity, empty the cart, update the cart, continue shopping, or checkout. After clicking on “Checkout’ , the shopping cart will be transferred back to your e-procurement application.

Ordering PC products via XML Our B2B gateway receives XML orders for PC products and automatically parses this information directly to our fulfillment systems without human intervention. Once the order is received, our B2B gateway will send back an Order Response message. If the order is valid, an "Acknowledged" response is sent and the order is forwarded onto our fulfillment systems. Orders are posted via HTTPS to a URL to be specified during the boarding process. This automated ordering process reduces errors and provides a reduced fulfillment cycle. Comments and Attachments sent from your e-procurement application (for PC orders) are not mapped to our fulfillment systems and will not be viewed by Lenovo. This is a result of a strategic initiative to implement automated order entry. This applies to catalog orders only. Any ship to override should be done using the proper XML elements and not in the comments section or custom fields.

Exception Handling for Purchase Orders If our Order Response is "Failed", our B2B support organization will be notified to investigate the issue. Common order failures include invalid content, non-catalog order,



order with attachment, change or cancel order, maximum field length limit exceeded, invalid credentials, and application or network problem. If the problem is identified by as a Lenovo problem, appropriate action will be taken to correct the problem. If the order is a valid order, it will be manually entered into our fulfillment systems, with no intervention required by you. If the order is not valid, you will be contacted to resolve the issue. If the order is “Rejected” (for cXML only), Lenovo will take no further action. Common order rejections include invalid content (part number), invalid p-card number, etc.

Boarding and Test Plans Please let us know your dates for testing and go live as soon as they are available. We have a dedicated boarding team and we like to schedule their time for boarding and move-to-production. The following is a list of testing steps that we recommend. Please provide us with any testing steps that you plan to execute. Please take note of any problem that might occur during testing. If during testing you encounter problems that prevent the test from proceeding, please contact Lenovo’s B2B Customer Support Help Desk (refer to earlier section of this document). However, if problems are noted during testing, but the test can continue, please take note of the problem and forward via an email to your Lenovo B2B Account Manager. Please include as much detail as possible including screenshots, logs, and date and time of testing. The results of the end-to-end testing will be documented and approved by both Lenovo and your company before the catalog is approved for ordering.


Buyer-Hosted Catalog Test Plan This test plan involves sending orders to Lenovo by creating a requisition using the items in the buyer-hosted catalog that we have provided to you.

1. Sending an order Purpose: Verify connection using an order with one line item. Actions: Send a purchase order that has one item from the Lenovo catalog. Expected result: HTTPS 200 returned to Customer; Lenovo verifies that Order was received successfully. (Order status is changed to “Acknowledged”.)

2. Sending an order with multiple items

Purpose: Verify an order with more than one item. Actions: Send a purchase order with 10 items from the Lenovo catalog. Expected result: HTTPS 200 returned to Customer; Lenovo verifies that Order was received successfully. (Order status is changed to “Acknowledged”.)

Results of Buyer-Hosted Catalog Testing Please fill out the following table during testing to provide us with detailed documentation of any problems or issues encountered: Step No. Success

(Y/N) Please describe any problems encountered (include order number, date and time, etc)

1. Send an order 2. Send a multi-line item order


Lenovo Punchout/Roundtrip Test Plan The scenarios covered in this test plan include accessing the punchout/roundtrip catalog on our B2B gateway and receiving an approved purchase order from your e-procurement application to our B2B gateway. The following test plan is for end-to-end testing of punchout/roundtrip catalog flow and order processing. The user will access the Lenovo punchout/roundtrip catalog. The user will shop for items, checkout from the punchout/roundtrip site, return to the e-procurement application, and approved orders will be sent back to our B2B gateway. 1. Access to punchout/roundtrip catalog and support page

Purpose: To verify that user gets access to the welcome page after logging in. 1.1 Actions: Verify welcome page displays your company name, text should read “Welcome to [Your Company]’s On-line Store.” This will appear near the bottom of the first page, you may have to scroll to see it. 1.2 Actions: On the welcome page, verify categories of the products. 1.3 Actions: Click on “Customer Support” link in the left navigation bar and verify page contains Customer Support contacts.

2. Shopping cart persistence

Purpose: To verify functionality of shopping cart. 2.1 Actions: Navigate through the categories to a product page, select a product, add options if you choose, and click “Add to shopping cart” button. Expected result: Shopping cart page with the product and quantity “1” displayed total price is correct. 2.2 Actions: Log off from your e-procurement application and log in again, punchout/roundtrip to Lenovo again, click “Shopping Cart” on the punchout/roundtrip site. Expected result: The items you previously added are present in shopping cart.

3. Transferring a shopping cart

Purpose: To test functionality of placing order. 3.1 Actions: In shopping cart page, check order contents and then click on “Proceed to Checkout” button Expected result: Requisition contents are the same as what was in the shopping cart. 3.2 Actions: Access the punchout/roundtrip catalog, click “shopping cart” button. Expected result: The shopping cart should be empty.

4. Order submission (following is dependent on the infrastructure available for testing i.e. backend connectivity)

Purpose: To verify order approval and sending process. 4.1 Actions: Select previously created requisition, approve it and send to Lenovo. Expected result: Order status is changed to “Acknowledged”. (Dependent on backend connection for test ) For cXML orders, order status may change. Besides “Acknowledged”, you may also see “Partially Confirmed”, “Confirmed”, “Shipped”, “Rejected” or “Failed”. 4.2 Actions (optional): Send a purchase order with 20+ line items. - Navigate to a product page and click “Add to shopping cart” button, repeat until 20+ products are in shopping cart. - On shopping cart page click on “Proceed to Checkout” button. - Select previously created requisition, approve it and send to Lenovo. Expected result: Order status is changed to “Acknowledged”. (Dependent on backend connection for test )


Results of Punchout/Roundtrip Test Please fill out the following table during testing to provide us with detailed documentation of any problems or issues encountered: Case No.

Success (Y/N)

Please describe any problem encountered (include page visited, screenshot, order number, date and time, etc)

1. Access to the punchout/roundtrip catalog 1.1 1.2 1.3 2. Shopping cart persistence 2.1 2.2 3. Transferring shopping cart 3.1 3.2 4. Order submission 4.1 4.2


OCI/xCBL Appendix Please be familiar with the documents that can be downloaded from https://connectscout.escout.com/docs/ and http://www.xcbl.org.

PerfectCommerce In order to purchase from Lenovo PC based products using your xCBL application, we need you to add “Lenovo Inc” as a supplier on your PerfectCommerce test account and production account at https://connectscout.escout.com. In the xCBL transactions, we use your trading partner network id (TPID) to identify and authenticate the correct buying organization. For your information, TPID for both our test and production account is (Lenovo = fa285746-7885-1000-9745-3f7428170001).

Local Catalog for PC Products After you work with your Lenovo product specialist to update your e-site with your entitled products you want to purchase, we can then provide a catalog to you. If you request a buyer-hosted catalog, we will upload and publish a catalog to you on PerfectCommerce, where you can download and import into your xCBL application. The SupplierPartNumExt field in the catalog allows a supplier to transmit additional data, such as quote number or contract number. The procurement application passes it back to the supplier in the resulting xCBL purchase order. The contents in this field are invisible to users and are required for the xCBL orders to be fully automated.

Roundtrip Catalog for PC Products If you requested a roundtrip catalog, we require an additional field to be sent in your OCI outbound message to uniquely identify the requistioner that is using our roundtrip site. The default field name is “REQID” and is case-sensitive. This field can be labeled anything, such as “buyerusername” or “userID”, as long as it’s value is unique for each requistioner. If your organization has multiple catalogs (perhaps one for general users and one for IT buyers or a catalog for each country), we require an additional field to be included in the OCI outbound message. The value of the field “view” can be used to display different views of your catalog.

https://connectscout.escout.com/docs/

http://www.xcbl.org/

https://connectscout.escout.com/

Your OCI catalog call structure might look similar to the following picture:

cXBL ship to and bill to RefNum To automate order entry, we require sample orders and a table of your xCBL ship to and bill to RefNum in the following format: RefNum,UniqueName,Address,City,State,PostalCode,Country 100001,Headquarters,123 North Dallas Pkwy.,Dallas,TX,75248,US 100002,Manufacturing Plant 1,45 Executive Drive,Syracuse,NY,11803,US 100003,Manufacturing Plant 2,678 South Street,Detroit,MI,48180,US 100004,Chicago Sales Office,900 Winfield Road,Chicago,IL,60555,US 100005,Miami Sales Office,1234 N.W. 19th Street,Miami,FL,33126,US etc…



xCBL Purchase Order Field Length Limits The following table lists the maximum character limits we accept for the various elements of the PurchaseOrder xCBL message. Field length limits for PurchaseOrder: cXML Field Max char ShipToParty.Party PartyID.NameAddress.Name1 35 ShipToParty.Party PartyID.NameAddress.Address1 ** 35** ShipToParty.Party PartyID.NameAddress.City 35 ShipToParty.Party PartyID.NameAddress.StateOrProvince 9 ShipToParty.Party PartyID.NameAddress.PostalCode 9 ShipToParty.Party PartyID.OrderContact.Contact.Email 80 BillToParty.Party PartyID.NameAddress.Name1 100 BillToParty.Party PartyID.NameAddress.Address1 # 70# BillToParty.Party PartyID.NameAddress.City 70 BillToParty.Party PartyID.NameAddress.StateOrProvince 70 BillToParty.Party PartyID.NameAddress.PostalCode 70 BillToParty.Party PartyID.OrderContact.Contact.Email 80 PurchaseOrder.OrderHeader.GeneralNote Not mapped ** Maximum of 3 “ShipTo Street” elements are accepted, each with a limit of 35 characters. # Maximum of 3 “BillTo Street” elements are accepted, each with a limit of 70 characters.

xCBL Order Status and Advance Ship Notice Our B2B gateway can provide xCBL order status and advance ship notice on orders received successfully via xCBL. After our gateway provides the initial functional acknowledgement, our fulfillment systems will validate the order and provide updated status to a xCBL -enabled URL that you specify. Order confirmations should include an estimated shipment date and estimated delivery date. Advance ship notices will include the shipment date and estimated delivery date and carrier tracking information.

Lenovo Customer OCI/xCBL Boarding Plan Contact Information Lenovo B2B Account Manager: Name, email, phone # E2open: Name, email, phone # Customer Business: Customer Testing (if not the same):

Task Description Owner Target Date 1 Set up Buyer’s e-procurement system 1a Send customer appropriate Lenovo account IDs

eScout Integration MPID: fa285746-7885-1000-9745-3f7428170001

Lenovo

1b Add Lenovo account ID to both test and production environment

Customer

1c Confirm Interoperability is configured E2open / Perfect


Commerce 1d Send customer appropriate Lenovo certificates and

URLs as needed for test and production Lenovo

1e Send Lenovo appropriate customer certificates and URLs as needed for test and production

Customer

2 Set up Supplier’s system 2a Send Lenovo REFNUMs Customer 2b Map REFNUMs to Lenovo MPPs Lenovo 2c Send Lenovo sample order, order response, ship

notice and invoice, include information on how the fields will be populated.

Customer

2d Gap analysis on order, order response, ship notice, and invoice.

Lenovo / E2open

2e Send Lenovo one of your DUNS numbers to be used as the unique identifier (SoldTo PARTNRID) Send Lenovo all MPIDs and TP short names that will be used for sending orders

Customer

2f Send E2open Buyer Network ID (or Unique Identifier) Send E2open all MPIDs and TP Short Names that will be used for sending orders Send E2open the Transaction volume and frequency for the orders. Send E2open “Status” for order response (“Accepted” vs. “Pending”) Send E2open updated part # list, if applicable

Lenovo

2g Notify Lenovo CSR of automation Lenovo 3 OCI Roundtrip Set Up 3a Send customer login information for roundtrip. Lenovo 4 Catalog creation 4a Create catalog Lenovo 4b Post catalog Lenovo 5 Test 5a Provide test plan Lenovo 5b Schedule testing Lenovo /

Customer

6 Move to production Notify Lenovo when first production order is sent as we

track first order through the system to ensure success. Customer


cXML Appendix Please be familiar with the following documents that can be downloaded from your account on http://buyer.ariba.com or http://www.cxml.org.

• Ariba Supplier Network Supplier's Guide • cXML User’s Guide • Ariba cXML Solutions Guide • Ariba PunchOut Implementation Guide • Catalog Format Reference

Ariba Supplier Network In order to purchase from Lenovo PC based products using your Ariba Buyer application, we need you to add “Lenovo Inc” as a supplier on your Ariba Supplier Network test account and production account at http://buyer.ariba.com. You can search for “Lenovo Inc” on your buyer account by searching for our DUNS number, 153345173-T on your test account, 153345173 on your production account. This will give us the required information about your Ariba account (DUNS number, Ariba Network ID, administrator contact information, etc). In the cXML transactions, we use your Ariba Network ID to identify and authenticate the correct buying organization. For your information, our Ariba Network ID for our test account is AN01000500879-T and AN01000500879 for our production account.

Credentials for non-Ariba cXML customers In the cXML transactions, we use the Network ID in the “From” and “Sender” credentials as well as the “shared secret” to identify and authenticate the correct buying organization. We can mutually agree on your NetworkID for the “From” and “Sender” credentials, as well as a shared secret. Our DUNS number will need to be in the “To” credentials (153345173-T for testing, 153345173-T for production) for all cXML transactions.

Local Catalog for PC Products After you work with your Lenovo product specialist to update your e-site with your entitled products you want to purchase, we can then provide a catalog to you. If you request a buyer-hosted catalog, we will upload and publish a catalog to you on Ariba Supplier Network, where you can download and import into Ariba Buyer. In order for us to utilize the SupplierPartAuxID field, we only provide buyer-hosted catalogs in CIF 3.0 format. This field allows a supplier to transmit additional data, such as quote number or contract number. The procurement application passes it back to the supplier in the resulting cXML purchase order. The contents in this field are invisible to users using Ariba Buyer and are required for the cXML orders to be fully automated.

Punchout Catalog for PC Products If you requested a punchout/roundtrip catalog, we require a default extrinsic to be sent in your PunchOutSetupRequest message. The extrinsic “User” (for Ariba Buyer 6.x) or “UniqueName” (for Ariba Buyer 7.x) should have a value that is unique for each user. “User” or “UniqueName” is sent by default by Ariba Buyer. This extrinsic is used to uniquely identify each user to keep shopping carts separate. This extrinsic in the PunchOutSetupRequest cXML message would look like the following for Ariba Buyer 7:

http://buyer.ariba.com/

http://www.cxml.org/

http://buyer.ariba.com/


<Extrinsic name="UniqueName">username</Extrinsic> If your organization has multiple catalogs (perhaps one for general users and one for IT buyers, or a catalog for each country), we require an additional parameter in the PunchOutSetupRequest to determine which catalog to view. This parameter can either be an extra extrinsic or by using the SupplierPartAuxiliaryID.

Punchout Catalog Filtering using SupplierPartAuxiliaryID To filter your punchout catalog using SupplierPartAuxiliaryID, we will supply you with an index.xml file with multiple line (one for each of your punchout catalogs), similar to the following: <IndexItem> <IndexItemPunchout> <ItemID> <SupplierPartID>Catalog1</SupplierPartID> <SupplierPartAuxiliaryID>Catalog1</SupplierPartAuxiliaryID> </ItemID> <PunchoutDetail> <Description xml:lang="en-US">Lenovo Punchout</Description> <URL>https://www.lenovo.com</URL> <Classification domain="SPSC">88888889</Classification> </PunchoutDetail> </IndexItemPunchout> </IndexItem> <IndexItem> <IndexItemPunchout> <ItemID> <SupplierPartID>Catalog2</SupplierPartID> <SupplierPartAuxiliaryID>Catalog2</SupplierPartAuxiliaryID> </ItemID> <PunchoutDetail> <Description xml:lang="en-US">Lenovo Punchout</Description> <URL>https://www.lenovo.com</URL> <Classification domain="SPSC">88888889</Classification> </PunchoutDetail> </IndexItemPunchout> </IndexItem> This will create multiple punchout buttons within Ariba Buyer and will send the SupplierPartAuxiliaryID in the PunchOutSetupRequest. Our B2B Gateway will then direct the punchout user to the appropriate catalog to shop.


Punchout Catalog Filtering using an Extrinsic To filter your punchout catalog by an extrinsic, we will require an extra extrinsic to be included in the PunchOutSetupRequest cXML message. The value of the “CatalogView” extrinsic will be used to display different views of your catalog. This extrinsic in the PunchOutSetupRequest cXML message would look like the following: <Extrinsic name="CatalogView">Catalog1</Extrinsic> In order to send “CatalogView” you will need to add code similar to the following in PunchOutSetupExtrinsics.java in your Ariba “config” directory: if (!Util.nullOrEmptyOrBlankString(duns)) { if (duns.equals("001368083")) { \\ 001368083-T for test extrinsics.put("CatalogView", "Catalog1"); } }

cXML ship to and bill to AddressIDs To automate order entry, we require sample orders and a table of your cXML ship to and bill to address IDs in the following format: AddresseId/RefNum,UniqueName,Address,City,State,PostalCode,Country 100001,Headquarters,123 North Dallas Pkwy.,Dallas,TX,75248,US 100002,Manufacturing Plant 1,45 Executive Drive,Syracuse,NY,11803,US 100003,Manufacturing Plant 2,678 South Street,Detroit,MI,48180,US 100004,Chicago Sales Office,900 Winfield Road,Chicago,IL,60555,US 100005,Miami Sales Office,1234 N.W. 19th Street,Miami,FL,33126,US etc…

cXML OrderRequest Field Length Limits The following table lists the maximum character limits we accept for the various elements of the OrderRequest cXML message. Field length limits for OrderRequest: cXML Field Max char OrderRequest.OrderRequestHeader.ShipTo.Address.Name 35 OrderRequest.OrderRequestHeader.ShipTo.Address.DeliverTo* 35* OrderRequest.OrderRequestHeader.ShipTo.Address.Street** 35** OrderRequest.OrderRequestHeader.ShipTo.Address.City 35 OrderRequest.OrderRequestHeader.ShipTo.Address.State 9 OrderRequest.OrderRequestHeader.ShipTo.Address.PostalCode 9 OrderRequest.OrderRequestHeader.ShipTo.Address.Email 80 OrderRequest.OrderRequestHeader.BillTo.Address.Name 100 OrderRequest.OrderRequestHeader.BillTo.Address.PostalAddress.DeliverTo 70# OrderRequest.OrderRequestHeader.BillTo.Address.PostalAddress.Street 70## OrderRequest.OrderRequestHeader.BillTo.Address.PostalAddress.City 70 OrderRequest.OrderRequestHeader.BillTo.Address.PostalAddress.State 70 OrderRequest.OrderRequestHeader.BillTo.Address.PostalAddress.PostalCode 70 OrderRequest.OrderRequestHeader.BillTo.Address.Email 80 OrderRequest.OrderRequestHeader.Comments Not mapped * Maximum of 2 “ShipTo DeliverTo” elements are accepted, each with a limit of 35 characters.


** Maximum of 3 “ShipTo Street” elements are accepted, each with a limit of 35 characters. # Maximum of 2 “BillTo DeliverTo” elements are accepted, each with a limit of 70 characters. ## Maximum of 3 “BillTo Street” elements are accepted, each with a limit of 70 characters.

Data from Purchase Order to Invoice Our B2B gateway can accommodate the need to include data from a cXML purchase order to an invoice. We can process one extrinsic at the header level and/or one extrinsic at the line level and place the values of these extrinsics on the invoice. From the cXML.dtd, a header level extrinsic is contained in the OrderRequestHeader element, and a line level extrinsic is contained in the ItemDetail element. The name of each extrinsic is not limited, only the value of the extrinsic will be placed on the invoice.

Steps to Access Order Status and Ship Notice for Ariba Buyer customers.

1. User logs in to Ariba Buyer application 2. On "Welcome" screen the user clicks on the "status" button 3. The status page is displayed showing all the PRs and their current status. 4. This page includes a column labeled "status". If the status is set to "ordered" the

user can click on the word "ordered" and it will take them out to the order on the Ariba SN.

5. If the PR has more than 1 order tied to it then the user will be displayed a page that shows all orders and their appropriate status on the Ariba SN.

6. Under the "status" column the user can click on the order they are interested in and they will be shown the status as it appears on the Ariba SN.

7. To return to the Buyer application the user would click on the "Back to Ariba Buyer Requisition Status" link at the top of the window.

cXML Order Status and Advance Ship Notice Our B2B gateway can provide cXML order status and advance ship notice on orders received successfully via cXML. After our gateway provides the initial functional acknowledgement, our fulfillment systems will validate the order and provide updated status to a cXML-enabled URL that you specify. The order status can change to “Partially Confirmed”, “Confirmed”, “Partially Shipped”, “Shipped”, “Rejected” or “Failed”. Order confirmations should include an estimated shipment date and estimated delivery date. Advance ship notices will include the shipment date and estimated delivery date and carrier tracking information.

cXML Order Status Definitions “Partially confirmed” means the order is valid and at least one line item does not have estimated ship/delivery dates. “Confirmed” means the order is valid and all line items in the order have estimated ship/delivery dates. Confirmed with changes means we are providing the estimated ship/delivery dates. If a supplier were to confirm the order with no estimated ship/delivery dates, the status would simply be "Confirmed as is". Since we will always be sending the estimated ship/delivery dates, the status will be "Confirmed with changes" not "Confirmed as is".


“Partially shipped” means at least one product has shipped, but not all products have shipped. Carrier tracking information on shipped items, if available, will be provided in the Advance Ship Notice (ASN) link. “Shipped” means all products in the order have shipped. Carrier tracking information on shipped items, if available, will be provided in the Advance Ship Notice (ASN) link. “Rejected” means the order was invalid or cancelled by Lenovo, could be for a variety of reasons (missing part number/non-catalog items, invalid/denied credit card or p-card, etc). Customer should contact their CSR to determine why the order was rejected in order to resubmit. Lenovo will take no action on a Rejected order, unless there is a problem with our systems that created the Rejected status incorrectly. “Failed” means the order failed to reach Lenovo, could be for a variety of reasons (network issues, invalid credit card number, etc), and if possible, our failed order process will process the order manually, while we investigate the problem. If there is a problem where the order could not be processed manually, the customer will be contacted to help resolve. Estimated ship/delivery dates are estimates, the actual ship/delivery dates can be before or after this date. Backlog items may have initial estimated ship/delivery dates further out in the future, but the estimated ship/delivery dates may be updated to be earlier to accommodate a customer's SLA as best as possible. There is a setting on Ariba Supplier Network (that the customer’s administrator can turn on/off) that will send email to the requisitioner whenever order status is changed by the supplier. These emails are generated by Ariba Supplier Network, not by Lenovo. Theoretically, several emails can be generated, depending a large part on the number of line items on the order and the quantity of each line item. This setting, of whether the requisitioner is notified of order status changes, can be found on buyer.ariba.com under Configuration, Notifications, Order Notification.

Lenovo Customer cXML Boarding Plan Contact Information Lenovo B2B Account Manager: Name, email, phone # E2open: Name, email, phone # Customer Business: Customer Testing (if not the same):

Task Description Owner Target Date 1 Set up Buyer’s e-procurement system 1a Send customer appropriate Lenovo account IDs

Ariba cXML DUNS #: 001368083 001368083-T Ariba email DUNS #: 156945008 156945008-T

Lenovo

1b Add Lenovo account ID to both test and production environment

Customer

1c Send customer appropriate Lenovo certificates and URLs as needed for test and production

Lenovo


1d Send Lenovo appropriate customer certificates and URLs as needed for test and production

Customer

2 Set up Supplier’s system 2a Send Lenovo AddressIDs Customer 2b Map AddressIDs to Lenovo MPPs

Lenovo

2c Send Lenovo sample order, order response, ship notice and invoice, include information on how the fields will be populated.

Customer

2d Gap analysis on order, order response, ship notice, and invoice.

Lenovo / E2open

2e Notify Lenovo CSR of automation Lenovo 3 cXML Punchout Set Up 3a Send customer NetworkID to be used during punchout Not

applicable, if via ASN

4 Catalog creation 4a Create catalog Lenovo 4b Post catalog Lenovo 5 Test 5a Provide test plan Lenovo 5b Schedule testing Lenovo/

Customer

6 Move to production Notify Lenovo when first production order is sent as we

track first order through the system to ensure success. Customer


Oracle OAG Appendix Please be familiar with the documents that can be downloaded from http://exchange.oracle.com and http://www.openapplications.org This appendix describes the Oracle iProcurement capabilities that are supported by Lenovo as a supplier. Lenovo supports Oracle iProcurement Model2 as a supplier. Oracle iProcurement Model 2 describes the process in which Oracle Purchasing 11i documents are exchanged directly between the buyer’s Oracle Applications system and the supplier’s system (with no intermediary hub). The major components of Model 2 are: • The buyer’s Oracle Purchasing 11i system, which includes the Oracle XML

Gateway. Here the Process PO transactions is recorded, and a corresponding XML document is generated and transmitted to the supplier’s system. Here also the advance shipment notice (ASN) is received from the supplier and processed.

• The Lenovo B2B Gateway that receives the XML purchase order documents from the buyer’s system and records the documents into the Lenovo supplier’s system. The Lenovo supplier can also generate XML ASNs in its system and send those to the buyer’s system.

Model 2 Process for Purchase Orders This section describes the process for Model 2 in detail, for purchase orders, including the flow of XML documents from the buyer’s Oracle Applications system to the supplier’s system directly. 1. Oracle Purchasing - Buyer Company When a buyer creates a new approved purchase order (PO) in Oracle Purchasing, a new PO document is recorded in the system. The data contained in these PO documents is used to generate an XML document, “Standard PO” or PROCESS_PO_007. 2. Transport interface Lenovo supports HTTPS as the message transport layer between the buyer system and the Lenovo supplier system. The HTTPS messages are: HTTPS Code Description 200 Document received OK 400 Bad Request (HTTP level error, unsupported document) 401 Unauthorized (Bad SSL credential) 403 Forbidden (Trying to get to an unauthorized URL) 404 Not Found (URL is not found)

3. Header information for the Purchase Order This is an example of the header information for the Purchase Order. The DOCTYPE statement is required for a valid XML message. <?xml version = '1.0' standalone = 'no'?>

http://exchange.oracle.com/

http://www.openapplications.org/

<!DOCTYPE PROCESS_PO_007 SYSTEM "003_process_po_007.dtd"> <PROCESS_PO_007> 4. Ordering PC products via Oracle iProcurement B2B Purchase Orders Lenovo B2B Gateway receives Oracle iProcurement orders for PC products and automatically parses this information directly to our fulfillment systems without human intervention. Once the order is received, Lenovo will process the order. Orders acknowledgements are posted via HTTPS to the Oracle iProcurement system. For each Oracle Purchase Order, the SoldTo Duns number must be the same for all orders from a customer and contained in POORDERHDR.PARTNER.DUNSNUMBER when POORDERHDR.PARTNER.PARTNRID = ‘SoldTo’ To automate order entry, we require sample orders and a table of your BillTo PARTNRID’s in the following format: BillTo.PARTNRID,Name,Address(ADDRLINE),City,STATEPROVN,PostalCode,Country 100001,Headquarters,123 North Dallas Pkwy.,Dallas,TX,75248,US 100002,Manufacturing Plant 1,45 Executive Drive,Syracuse,NY,11803,US 100003,Manufacturing Plant 2,678 South Street,Detroit,MI,48180,US 100004,Chicago Sales Office,900 Winfield Road,Chicago,IL,60555,US 100005,Miami Sales Office,1234 N.W. 19th Street,Miami,FL,33126,US etc… For Oracle, the BillTo.PARTNRID are mandatory for each order and are to be inserted by the Customer in the following Oracle field: POORDERHDR.PARTNER.PARTNRID when POORDERHDR.PARTNER.PARTNRID = ‘BillTo’. In Oracle, there is a ShipTo PartnerID and optionally an address on the first line item in the Purchase Order and it is recommended that the customer provide ShipTo PartnerID’s to Lenovo if their system uses ShipTo PartnerID’s. This could be the case when the customer has a limited number of ShipTo addresses. This will allow for pre-specification of customer ShipTo addresses by Lenovo. In Oracle, the customer can provide an actual ShipTo Address by completing the actual address fields under the is ShipTo PartnerID on the first line item of the Purchase Order. For the Contract number (CONTRACTPONUM), it can be in every order at every line item, or if it is always the same one, Lenovo can preload it.



Oracle PROCESS_PO_007 Field Length Limits The following table lists the maximum character limits we accept for the various elements of the PROCESS_PO_007 message. Field length limits for Oracle Purchase Order :

Oracle Field Max char DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.NAME where DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.PARTNRID.PARTNERTYPE = ShipTo

35

DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.ADDRESS.ADDRLINE index="1" where DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.PARTNRID.PARTNERTYPE = ShipTo

35


35


35

DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.ADDRESS.CITY where POLINESCHD.USERAREA.PARTNER.PARTNRID.PARTNERTYPE = ShipTo

35

DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.ADDRESS.STATEPROVN where POLINESCHD.USERAREA.PARTNER.PARTNRID.PARTNERTYPE = ShipTo

9

DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.ADDRESS.POSTALCODE where DATAAREA.PROCESS_PO.POORDERLIN.POLINESCHD.USERAREA.PARTNER.PARTNERTYPE = ShipTo

9

DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.NAME index="1" where POORDERHDR.PARTNER.PARTNRID.PARTNERTYPE = BillTo

100

DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.ADDRESS.ADDRLINE index="1" where DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.PARTNERTYPE = BillTo

70


70


70

DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.ADDRESS.CITY where DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.PARTNERTYPE = BillTo

70

DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.ADDRESS.STATEPROVN where DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.PARTNERTYPE = BillTo

70

DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.ADDRESS.POSTALCODE where DATAAREA.PROCESS_PO.POORDERHDR.PARTNER.PARTNERTYPE = BillTo

70

Oracle Advance Ship Notice Our B2B Gateway can provide Oracle advance ship notice on orders received successfully. Advance ship notices will include the shipment date and estimated delivery date and shipment identification information.


Lenovo Customer Oracle OAG Boarding Plan Contact Information Lenovo B2B Account Manager: Name, email, phone # E2open (as needed): Name, email, phone # Customer Business: Customer Testing (if not the same):

Task Description Owner Target Date 1 Set up Buyer’s e-procurement system 1a Send customer appropriate Lenovo certificates and

URL for test and production Lenovo

1b Send Lenovo appropriate customer certificates and URL for test and production

Customer

2 Set up Lenovo Supplier’s system 2a Send Lenovo BillTo PARTNRID’s for PCD Orders Customer 2b Map BillTo PARTNRID’s to Lenovo MPPs Lenovo 2c Buyer sends Lenovo sample Oracle orders and

Lenovo sends sample Oracle Ship Notices, include information on how the fields will be populated.

Customer

2d Gap analysis on Oracle Orders and Ship Notices Lenovo/ E2open

2e Send Lenovo one of your DUNS numbers to be used as the unique identifier (SoldTo PARTNRID)

Customer

2f Send E2open the Transaction volume and frequency for the orders. Send E2open updated part # list, if applicable

Lenovo

2g Notify Lenovo CSR of automation Lenovo 3 OAG Punchout Set Up 3a Send customer URL and credentials to be used

during punchout

4 Catalog creation 4a Create catalog Lenovo 4b Post catalog Lenovo 5 Test 5a Provide Test Plan Lenovo 5b Schedule Testing Lenovo/

Customer

6 Move to production Notify Lenovo when first production order is sent as

we track first order through the system to ensure success.

Customer

SAP Enterprise Buyer Professional (EBP) XML Appendix This appendix describes the buyer SAP EBP system capabilities that are supported by Lenovo as a supplier. Lenovo supports SAP EBP XML 3.5 as a supplier. SAP EBP XML 3.5 describes the process in which SAP EBP documents are exchanged directly between the buyer’s SAP EBP system and the supplier’s system. The Lenovo supplier system, which receives the XML purchase order documents from the buyer’s system and records the documents into the Lenovo supplier’s system. The Lenovo supplier will also generate SAP EBP Order Acknowledgments and Confirmations (used for the Advanced Ship Notice) in its system and send those to the buyer’s system.

SAP EBP Process for Purchase Orders This section describes the process for SAP EBP in detail, for purchase orders, including the flow of XML documents from the buyer’s SAP EBP Application System to the supplier’s system. 1. SAP EBP Purchasing - Buyer Company When a buyer creates a new approved purchase order (PO) in SAP EBP, the new PO document is recorded in the system. The data contained in these PO documents is used to generate XML documents. 2. Transport interface Lenovo supports HTTPS as the message transport layer between the buyer system and the Lenovo supplier system. The HTTPS messages are: HTTPS Code Description 200 Document received OK 400 Bad Request (HTTP level error, unsupported document) 401 Unauthorized (Bad SSL credential) 403 Forbidden (Trying to get to an unauthorized URL) 404 Not Found (URL is not found) 3. Header information for the Purchase Order This is an example of the header information for the Purchase Order. The DOCTYPE statement is required for a valid XML message. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE Envelope SYSTEM "EbpXml_PurchaseOrder_main.dtd"> 4. Ordering PC products via SAP EBP B2B Purchase Orders Lenovo B2B Gateway receives SAP EBP orders for PC products and automatically parses this information directly to our fulfillment systems without human intervention. Once the order is



received, Lenovo will process the order. Orders acknowledgements are posted via HTTPS to the SAP EBP system. For each SAP EBP Order, the SoldTo Duns number must be the same for all orders from a customer and contained in PurchaseOrderHeader.TradingPartners.SoldToParty.PartnerID type="DUNS">xxxxxxxxx<. Lenovo asks customer to put the DUNS number in every PO in the SoldTo Partner ID. To automate order entry, we require sample orders and a table of your BillToParty.PartnerID’s in the following format: BillToParty.PartnerID,CompanyName1,House Number Street, City, Region, PostalCode, Country 100001,Headquarters,123 North Dallas Pkwy.,Dallas,TX,75248,US 100002,Manufacturing Plant 1,45 Executive Drive,Syracuse,NY,11803,US 100003,Manufacturing Plant 2,678 South Street,Detroit,MI,48180,US 100004,Chicago Sales Office,900 Winfield Road,Chicago,IL,60555,US 100005,Miami Sales Office,1234 N.W. 19th Street,Miami,FL,33126,US etc… For SAP EBP, the BillToParty.PartnerID is mandatory for each order and is to be inserted by the Customer into one of the following SAP-EBP fields: PurchaseOrderHeader.TradingPartners.BillToParty.PartnerID( type="Buyer" <xxxx> </PartnerID> or PurchaseOrderHeader.TradingPartners.SoldToParty.PartnerID( type="Buyer" <xxxx> </PartnerID> In SAP-EBP, there is a ShipToParty.PartnerID and optionally a ShipToAddress in the Purchase Order header and it is recommended that the customer provide ShipToParty.PartnerID’s to Lenovo if their system uses ShipToParty.PartnerID’s. This could be the case when the customer has a limited number of ShipToParty addresses. This will allow for pre-specification of customer ShipTo addresses by Lenovo. In SAP EBP, the customer can provide an actual ShipToAddress by completing the actual address fields under the ShipToAddress in the Header of the Purchase Order. For the Contract number (LineItem.ContractReference.ContractID), it must be in every order at every line item if the Customer has more than 1 contract number with Lenovo, or if there is only one contract number, Lenovo can preload it.

SAP EBP Purchase Order Field Length Limits The following table lists the maximum character limits we accept for the various elements of the SAP EBP Purchase Order message. Field length limits for SAP EBP Purchase Order : SAP-EBP Field(s) Max char PurchaseOrderHeader.ShipToAddress. CompanyName1 35 All of these fields together with blanks between the fields are limited to the Max char - PurchaseOrderHeader.ShipToAddress.PersonTitle ll First Name ll Last Name ( delimiter of blank)

35

All of these fields together with blanks between the fields are limited to the Max 35


char - PurchaseOrderHeader.ShipToAddress. CompanyName2 ll Dept. II Department ll Bldg. Building ll Room Room Number All of these fields together with blanks between the fields are limited to the Max char - PurchaseOrderHeader.ShipToAddress.House Number ll Street ( delimiter of blank)

35

PurchaseOrderHeader.ShipToAddress.City 35 PurchaseOrderHeader.ShipToAddress.Region 9 PurchaseOrderHeader.ShipToAddress.Postal Code 9 PurchaseOrderHeader.TradingPartners.BillToParty.Address.CompanyName1 100 PurchaseOrderHeader.TradingPartners.BillToParty.Address.PersonTitle ll First Name ll Last Name

70

All of these fields together with blanks between the fields are limited to the Max char - PurchaseOrderHeader.TradingPartners.BillToParty.Address. CompanyName2 ll Dept. II Department ll Bldg. Building ll Room Room

70

All of these fields together with blanks between the fields are limited to the Max char - PurchaseOrderHeader.TradingPartners.BillToParty.Address.House Number ll Street

70

PurchaseOrderHeader.TradingPartners.BillToParty.Address.City 70 PurchaseOrderHeader.TradingPartners.BillToParty.Address.Region 70 PurchaseOrderHeader.TradingPartners.BillToParty.Address.Postal Code 70

SAP EBP Purchase Order Acknowledgements Our B2B Gateway will provide SAP EBP Purchase Order Acknowledgements which will contain the status of the order. Each time the status of the order changes, Lenovo will send an updated Purchase Order Acknowledgement.

SAP EBP Advance Ship Notice Our B2B Gateway can provide SAP EBP Confirmations (used for advance ship notices) on orders received successfully. Advance ship notices will include the shipment date and estimated delivery date and shipment identification information.

Lenovo Customer SAP EBP Boarding Plan Contact Information Lenovo B2B Account Manager: Name, email, phone # E2open (as needed): Name, email, phone # Customer Business: Customer Testing (if not the same):




Customer

2 Set up Lenovo Supplier’s system 2a Send Lenovo BillToParty.PartnerID for PCD

Orders Customer


2b Map BillToParty.PartnerID to Lenovo MPPs Lenovo 2c Buyer sends Lenovo sample SAP EBP orders and

Lenovo sends sample SAP EBP Order Acknowledgements and Confirmations (Ship Notices), include information on how the fields will be populated.

Customer

2d SAP EBP: Gap analysis on SAP-EBP Orders, Order Acknowldegements and Ship Notices

Lenovo/ E2open

2e SAP EBP: Send Lenovo one of your DUNS numbers to be used as the unique identifier (SoldToParty.PartnerID)

Customer

2f SAP EBP Customers: Send E2open the Transaction volume and frequency for the orders. Send E2open updated part # list, if applicable

Lenovo

2g Notify Lenovo CSR of automation Lenovo 3 SAP EBP Punchout Set Up 3a Send customer URL and credentials to be used

during punchout


Customer



Customer

SAP XML (IDOC) Appendix

Overview This appendix describes the buyer SAP XML (IDOC) system capabilities that are supported by Lenovo as a supplier. Lenovo supports SAP XML (IDOC) as a supplier. SAP XML (IDOC) describes the process in which SAP XML (IDOC) documents are exchanged directly between the buyer’s SAP XML (IDOC) system and the supplier’s system. The Lenovo supplier system, which receives the XML purchase order documents from the buyer’s system and records the documents into the Lenovo’s supplier’s system. The Lenovo supplier will also generate SAP XML (IDOC) Order Acknowledgments and Advanced Ship Notices in its system and send those to the buyer’s system.

SAP XML (IDOC) Process for Purchase Orders This section describes the process for SAP XML (IDOC) in detail, for purchase orders, including the flow of XML documents from the buyer’s SAP XML(IDOC) Application System to the supplier’s system. 1. SAP XML (IDOC) Purchasing - Buyer Company When a buyer creates a new approved purchase order (PO) in SAP XML (IDOC), the new PO document is recorded in the system. The data contained in these PO documents is used to generate XML documents. 2. Transport interface Lenovo supports HTTPS as the message transport layer between the buyer system and the Lenovo supplier system. The HTTPS messages are: HTTPS Code Description 200 Document received OK 400 Bad Request (HTTP level error, unsupported document) 401 Unauthorized (Bad SSL credential) 403 Forbidden (Trying to get to an unauthorized URL) 404 Not Found (URL is not found) 3. Header information for the Purchase Order This is an example of the header information for the Purchase Order. The DOCTYPE statement is required for a valid XML message. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ORDERS05 SYSTEM "../dtd/ORDERS05.dtd"> 4. Ordering PC products via SAP XML (IDOC) B2B Purchase Orders Lenovo B2B Gateway receives SAP XML (IDOC) orders for PC products and automatically parses this information directly to our fulfillment systems without human intervention. Once the



order is received, Lenovo will process the order. Orders acknowledgements are posted via HTTPS to the SAP XML (IDOC) system. For each SAP XML (IDOC) Order, the SoldTo Duns number must be the same for all orders from a customer and contained in E1EDK14.ORGID IF E1EDK14.QUALF='011'. Lenovo asks customer to put the SoldTo DUNS number in every PO. To automate order entry, we require sample orders and a table of your BillToParty PartnerID’s in the following format: BillToParty PartnerID,CompanyName1,House Number Street, City, Region, PostalCode, Country 100001,Headquarters,123 North Dallas Pkwy.,Dallas,TX,75248,US 100002,Manufacturing Plant 1,45 Executive Drive,Syracuse,NY,11803,US 100003,Manufacturing Plant 2,678 South Street,Detroit,MI,48180,US 100004,Chicago Sales Office,900 Winfield Road,Chicago,IL,60555,US 100005,Miami Sales Office,1234 N.W. 19th Street,Miami,FL,33126,US etc… For SAP XML (IDOC), the BillToParty PartnerID is mandatory for each order and is to be inserted by the Customer into the following SAP XML (IDOC) fields: E1EDKA1.PARTN IF E1EDKA1.PARVW = RE In SAP XML (IDOC),, there is a ShipToAddress AddressID (E1EDKA1.PARTN IF E1EDKA1.PARVW = WE) and optionally a ShipToAddress in the Purchase Order header and it is recommended that the customer provide ShipToAddress AddressID’s to Lenovo if their system uses ShipToAddress AddressID’s. This could be the case when the customer has a limited number of ShipToAddress addresses. This will allow for pre-specification of customer ShipTo addresses by Lenovo. In SAP XML (IDOC), the customer can provide an actual ShipToAddress by completing the actual address fields under the ShipToAddress (in the E1EDKA1 section) in the Header of the Purchase Order. For the Contract number (E1EDP01.E1EDP02.BELNR if E1EDP01.E1EDP02.QUALF - 005), it must be in every order at every line item if the Customer has more than 1 contract number with Lenovo, or if there is only one contract number, Lenovo can preload it in the Gateway.

SAP XML (IDOC) Purchase Order Field Length Limits The following table lists the maximum character limits we can process for the various elements of the SAP XML (IDOC) Purchase Order message. Field length limits for SAP XML (IDOC) Purchase Order : SAP XML (IDOC) Field(s) Max char E1EDKA1.NAME1 IF E1EDKA1.PARVW = WE 35 E1EDKA1.NAME2 IF E1EDKA1.PARVW = WE 35 E1EDKA1.NAME3 IF E1EDKA1.PARVW = WE 35 E1EDKA1.STRAS IF E1EDKA1.PARVW = WE 35 E1EDKA1.ORT01 IF E1EDKA1.PARVW = WE 35 E1EDKA1.REGIO IF E1EDKA1.PARVW = WE 9


E1EDKA1.PSTLZ IF E1EDKA1.PARVW = WE 9 E1EDKA1.NAME1 IF E1.EDKA1.PARVW = RE 100 E1EDKA1.NAME2 IF E1.EDKA1.PARVW = RE 70 E1EDKA1.NAME3 IF E1.EDKA1.PARVW = RE 70 These two fields together with blanks between the fields E1EDKA1.STRAS IF E1.EDKA1.PARVW = RE and E1EDKA1.STRS2 IF E1.EDKA1.PARVW = RE

70

E1EDKA1.ORT01 IF E1.EDKA1.PARVW = RE 70 E1EDKA1.REGIO IF E1.EDKA1.PARVW = RE 70 E1EDKA1.PSTLZ IF E1.EDKA1.PARVW = RE 70

SAP XML (IDOC) Purchase Order Acknowledgements Our B2B Gateway will provide SAP XML (IDOC) Purchase Order Acknowledgements which will contain the status of the order. Each time the status of the order changes, Lenovo will send an updated Purchase Order Acknowledgement.

Lenovo Customer SAP XML Boarding Plan Contact Information Lenovo B2B Account Manager: Name, email, phone # E2open (as needed): Name, email, phone # Customer Business: Customer Testing (if not the same):




Customer

2 Set up Lenovo Supplier’s system 2a Send Lenovo BillToParty.PartnerID

(E1EDKA1.PARTN IF E1EDKA1.PARVW = RE ) for PCD Orders

Customer

2b Map BillToParty.PartnerID (E1EDKA1.PARTN IF E1EDKA1.PARVW = RE) to Lenovo MPPs

Lenovo

2c Buyer sends Lenovo sample SAP XML (IDOC) orders and Lenovo sends sample SAP XML (IDOC) Order Acknowledgements include information on how the fields will be populated.

Customer

2d SAP XML (IDOC): Gap analysis on SAP XML (IDOC) Orders, and Order Acknowledgements

Lenovo/ E2open

2e SAP XML (IDOC): Send Lenovo one of your DUNS numbers to be used as the unique identifier (E1EDK14.ORGID IF E1EDK14.QUALF='011')

Customer

2f SAP XML (IDOC) Customers: Send E2open the Transaction volume and frequency for the orders.

Lenovo


Send E2open updated part # list, if applicable 2g Notify Lenovo CSR of automation Lenovo 3 SAP Punchout Set Up 3a Send customer URL and credentials to be used

during punchout


Customer



Customer


RosettaNet Order/OrderConfirmation Appendix:

Overview This appendix describes the buyer RosettaNet system capabilities that are supported by Lenovo as a supplier. Lenovo supports RosettaNet PIP 3A4 as a supplier and uses the RNIF 1.1. The major components of the 3A4 PIP are:

• The buyer’s e-procurement system which creates and sends the RosettaNet 3A4 PurchaseOrder and receives the 3A4 Order Confirmation to its RosettaNet enabled gateway.

• The buyer’s RosettaNet enabled B2B gateway which packages and sends the RosettaNet object to the Lenovo gateway and receives, unwraps and validates messages from the Lenovo gateway

• The Lenovo B2B gateway which receives messages from and sends messages to the buyer’s gateway

• The Lenovo RosettaNet supplier system, which receives the 3A4 purchase order from the gateway and records the documents into the Lenovo supplier’s system. The Lenovo supplier will also generate the 3A4 Order Confirmation in its system and send those to the buyer’s system via the Lenovo gateway..

Ordering PC products via RosettaNet 3A4 Purchase Orders For each RosettaNet 3A4 Purchase Order, the SoldTo DUNS number must be the same for all orders from a customer and contained in following: fromRole.PartnerRoleDescription.PartnerDescription.BusinessDescription.GlobalBusinessIdentifier To automate order entry, we require sample orders and a table of your BillTo identifiers in the following format (the BillTo identifiers are in the data element ‘PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. PhysicalAddress.GlobalLocationIdentifier’): BillToidentifiers,businessname,Addressline,City,RegionName,NationalPostalCode,GlobalCountryCode 100001,Headquarters,123 North Dallas Pkwy.,Dallas,TX,75248,US 100002,Manufacturing Plant 1,45 Executive Drive,Syracuse,NY,11803,US 100003,Manufacturing Plant 2,678 South Street,Detroit,MI,48180,US 100004,Chicago Sales Office,900 Winfield Road,Chicago,IL,60555,US 100005,Miami Sales Office,1234 N.W. 19th Street,Miami,FL,33126,US etc… For RosettaNet 3A4, the ‘PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. PhysicalAddress.GlobalLocationIdentifier’ is mandatory for each order and must contain one of the values of the BillTo identifiers that has been given to Lenovo ( see table above). Additional BillTo information may be included but Lenovo will use the information it has associated with the given BillTo identifier as a mailing address.


In RosettaNet 3A4, there is a shipTo.PartnerDescription that includes a shipTo.PartnerDescription.BusinessDescription.GlobalbusinessIdentifer. It is recommended that the customer provide shipTo.PartnerDescription.BusinessDescription.GlobalbusinessIdentifer ‘s to Lenovo if their system uses shipTo.PartnerDescription.BusinessDescription.GlobalbusinessIdentifer. This could be the case when the customer has a limited number of ShipTo addresses. This will allow for pre-specification of customer ShipTo addersses by Lenovo. In RosettaNet 3A4, the customer can provide an actual ShipTo Address by completing the address fields under the shipTo.PartnerDescription.PhysicalAddress. Lenovo will use the shipTo information at the Header level if it exists. Then, at only the first line item, override the header information field by field if it exists at the first line item level. For the Contract number (PurchaseOrder.ProductLineItem.ContractInformation.contractIdentifier.PropietaryDocumentIdentifier), it can be in every order at every line item, or if it is always the same one, Lenovo can use the customer default value and preload it in the Lenovo Gateway.

RosettaNet 3A4 Field Length Limits The following table lists the maximum character limits we can process for the various elements of the RosettaNet 3A4 message. Even though RosettaNet may allow for larger lengths, we would truncate the information to the lengths specified. Field length limits for RosettaNet 3A4 Order : RosettaNet 3A4 Field Max char shipTo.PartnerDescription.BusinessDescription.businessName.FreeFormText. 35 shipTo.PartnerDescription.PhysicalAddress.addressLine1.FreeFormText 35 shipTo.PartnerDescription.PhysicalAddress.addressLine2.FreeFormText 35 shipTo.PartnerDescription.PhysicalAddress.addressLine3.FreeFormText 35 shipTo.PartnerDescription.PhysicalAddress.cityName.FreeFormText 35 shipTo.PartnerDescription.PhysicalAddress.regionName.FreeFormText 9 shipTo.PartnerDescription.PhysicalAddress.NationalPostalCode 9 PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. PartnerDescription.BusinessDescription.businessName.FreeFormText

100

PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. ContactInformation.PhysicalAddress.addressLine1.

70

PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. ContactInformation.PhysicalAddress.addressLine2.FreeFormText

70

PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. ContactInformation.PhysicalAddress.cityName.FreeFormText

70

PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. ContactInformation.PhysicalAddress.regionName.FreeFormText

70

PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. ContactInformation.PhysicalAddress.NationalPostalCode

70

Lenovo Customer Boarding Plan Contact Information Lenovo B2B Account Manager: Name, email, phone # E2open (as needed): Name, email, phone # Customer Business: Customer Testing (if not the same):




Customer

2 Set up Lenovo Supplier’s system 2a Send Lenovo

‘PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. PhysicalAddress.GlobalLocationIdentifier’ for PCD Orders

Customer

2b Map PurchaseOrder.AccountDescription.billTo.PartnerRoleDescription. PhysicalAddress.GlobalLocationIdentifier’ to Lenovo MPPs

Lenovo

2c Buyer sends Lenovo sample RosettaNet Orders and Lenovo sends sample OrderConfirmations, include information on how the fields will be populated.

Customer

2d RosettaNet: Gap analysis on RosettaNet Orders and OrderConfirmations

Lenovo/ E2open

2e Send Lenovo one of your DUNS numbers to be used as the unique identifier (fromRole.PartnerRoleDescription.PartnerDescription.BusinessDescription.GlobalBusinessIdentifier)

Customer

2f RosettaNet Customers: Send E2open the Transaction volume and frequency for the orders. Send E2open updated part # list, if applicable

Lenovo

2g Notify Lenovo CSR of automation Lenovo 3 Test 3a Provide Test Plan Lenovo 3b Schedule Testing Lenovo/

Customer



Customer


IBM B2B Direct Implementation Guide - Office of the Chief ... · PDF fileLenovo Confidential 1...

Documents

Transcript of IBM B2B Direct Implementation Guide - Office of the Chief ... · PDF fileLenovo Confidential 1...