Owner: ebis guide Revision Number: 29 Last Revision Date: November 20, 2015 Table of Contents Preface 9
Download 1.42 Mb.
|
- Navigate this page:
- 2.Purchase Order Request: Process
- 10.Message Guideline (PIP 3A4
Known LimitationsConfig Express functionality, a Service Provider feature is not yet available in the new system. 1.IntroductionCisco has prepared this document for implementing the Purchase Order message of RosettaNet PIP 3A4 V02.00.00. RosettaNet is a globally supported standards organization that provides a common language for e-business transactions and the foundation for integrating critical processes among partners within the global supply chain. RosettaNet Partner Interface Process (PIP) is a specialized system to system XML based dialog that defines business processes between trading partners. This implementation guide describes the details of various PIP elements and how those elements should be used in an integration with Cisco. The RosettaNet PIP 3A4 specifies the purchase order management process between trading partners. The process includes the creation, change, acceptance, and cancellation of a purchase order. a.OverviewThe interactions between the partner systems and Cisco are done by a request and response XML interchange mechanism. After Cisco’s systems receive a PIP3A4 Purchase Order Request, the request is validated as per business rules. If all validations pass, Cisco accepts the purchase order. If there are any errors, the purchase order is rejected, with appropriate error messaging. In the general sales process flow, partners submit purchase orders following preparing a configuration and/or a quote. Partner creates and manages a configuration. A Quote may be created and approved. A Purchase Order Request is submitted to Cisco. Partner’s order moves to Fulfillment and Service phase. Figure : High-Level General Sales Process Flow The solution ensures data security by using digital certificate authentication, and guarantees document delivery with the RosettaNet standard. In addition to this document, the reader should also consult the following documents: PurchaseOrderMessageGuideline of RosettaNet PIP 3A4 PurchaseOrderMessage DTD of RosettaNet PIP 3A4 Note: The above-mentioned documents can be accessed at http://www.rosettanet.org. b.AudienceThe intended audience for this document is business analysts, IT engineers, and technical architects who are involved in the integration project. Other stakeholders who wish to understand business and/or technical aspects of integration may also use the document as a reference. c.ScopeThe scope of this implementation guide is limited to the Purchase Order Request and Response message. This guide is derived from the original specification (PIP 3A4 V02.00.00) as published by the RosettaNet standards body. This guide also retains all the elements of the DTD as published in the original document from RosettaNet. d.PrerequisitesIt is assumed that the reader has some familiarity with Cisco’s CCW platform through either formal or informal training and/or demonstration. The credentials to access CCW and Cisco’s Submit Purchase Order infrastructure must have been previously established. Please contact your Partner Solutions representative for assistance if they are yet to be established. Any firewall / security settings in the partner system have been configured to allow Cisco’s CCW platform to post XML messages to the designated partner system.
Upon the submission of a Purchase Order Request to Cisco, the order is validated against business logic, such as configuration validity. If errors are found, the order is rejected. The response message from Cisco will include error messaging to help the partner address the problem. Error severity management represents the success or failure to meet a business rule validation. An order can be rejected, which results in an error. An order can be accepted, but include a warning of tasks associated with the order. Lastly, an order can be accepted and have no further action required of the partner. For examples of the request and response messages, see the Message Guideline section. The process of sending and receiving an order in the form of PIP 3A4 is as follows:
3.The partner submits the PO Request to Cisco via their XML gateway. 4.The Cisco XML gateway receives and acknowledges the PO Request. 5.The partner receives the PO Request via their XML gateway. 6.Cisco validates and processes the PO Request. 7.Cisco sends a PIP 3A4 PO Confirmation to the partner via Cisco XML gateway. 8.The partner receives the PO Confirmation via their XML gateway. 9.The partner processes the PO Confirmation.
Figure : Service for Purchase Order Request Process 10.Message Guideline (PIP 3A4 V02.00.00)The request and response messages that partners send to and receive from Cisco include all of the data elements and structure to facilitate the PO Submit process. This section describes in detail, the correct way to structure a 3A4 PO Request document to ensure the order is processed correctly by Cisco. a.Guideline AnnotationsThe following guideline annotations apply when creating a request or interpreting a response: Cardinality values indicate if a message element is required or optional, and specify its valid instance count. Color coding advises a partner if the code is used. Table : Cardinality Values and Color Codes
Directory: web web -> The Truth about the Rwandan Genocide web -> T/R 8: 00am-9: 15am Office Hours: Mon through Thurs. 11: 00am 2: 00pm web -> M/W 8: 00am-9: 15am Office Hours: Mon through Thurs. 11: 00am 2: 00pm web -> Chapter 13 Exercises web -> Freshly squeezed script tues 17/04/07 web -> For Official Use Only Proforma and Time Frame for Submitting web -> The "Metaphysicals": English Baroque Literature in Context web -> Terry L. Root web -> Contests, Competitions, and Activities humanities Download 1.42 Mb. Share with your friends:
|
