Oracle Procurement (Procurement)

This chapter covers the following topics:

• Cancel Purchase Order using Open Interface and PLSQL
• Update of Purchase Order using Open Interface and PLSQL
• Create Standard Purchase Order using Web Services
• Update Price and Quantity of Standard Purchase Order using Web Services
• Procure to Pay End to End Flow using Open Interface, API and Web Services
• Creating and Updating the Supplier and Supplier Site

Cancel Purchase Order using Open Interface and PLSQL

Buyer logs and creates standard purchase order using the open interface having multiple lines, multiple shipments and multiple distributions. Buyer can create multiple PO's using Open Interface and then import the standard purchase orders into the application using the concurrent program “Import Standard Purchase Orders”.

Buyer then cancels the above approved standard purchase orders using API.

Flow Type

OI and PLSQL-Hybrid flow

Technical Name

Cancel_PO_PLSQL

Prerequisites

Not Applicable

Profile Options

Not Applicable

Predefined Data

Not Applicable

Setup Data

The following data must be set up:

Window/User Name	Field Name	Field Value
Operating Unit	Vision Operations	Vision Operations
Responsibility	Responsibility	Purchasing, Vision Operations (USA)
Users	User	Operations
Document Style	Style Name	Standard Purchase Order

Description of the Scenarios in the Flow (Procurement)

Following are the details of the scenarios in the flow:

Scenario	Objective	Artifact/Method	Component Set	Main Component
Create_PO	This scenario creates a purchase order using the open interface	Import_Standard_Purchase_Orders_POXPOPDOI	Import_Standard_Purchase_Orders_POXPOPDOI	Import_Standard_Purchase_Orders_POXPOPDOI
Retrieving_PO_Number				SELECT Get_PO_Number_Interface
Verification_PO				UI Component: Search_POSummary_Common Verify_PO_POHeader
Cancel_PO	This scenario is used to cancel the created purchase order from the above scenario	Cancel_PO_PLSQL	-	PO_DOCUMNET_CONTROL_PUB_CONTROL_DOCMENT_Main

Update of Purchase Order using Open Interface and PLSQL

Buyer logs and creates standard purchase order using the open interface having Multiple Lines and then imports the standard purchase orders into the application using the concurrent program “Import Standard Purchase Orders”.

Buyer then updates the line information such as quantity, price, and need-by date and promised date of the above approved standard purchase order using API.

Flow Type

OI and PLSQL-Hybrid flow

Technical Name

Update_PO_PLSQL

Prerequisites

Not Applicable

Profile Options

Not Applicable

Predefined Data

Not Applicable

Setup Data

The following data must be set up:

Window/User Name	Field Name	Field Value
Operating Unit	Vision Operations	Vision Operations
Responsibility	Responsibility	Purchasing, Vision Operations (USA)
Users	User	Operations
Document Style	Style Name	Standard Purchase Order

Description of the Scenarios in the Flow (Procurement)

Following are the details of the scenarios in the flow:

Scenario	Objective	Artifact/Method	Component Set	Main Component
Create_PO	This scenario creates a purchase order using the open interface	Import_Standard_Purchase_Orders_POXPOPDOI	Import_Standard_Purchase_Orders_POXPOPDOI	Import_Standard_Purchase_Orders_POXPOPDOI
Get_PO_Number				SELECT
Update_PO	This scenario is used to update the created purchase order line information from the above scenario	Update_PO_PLSQL	-	PO_Change_APIA_S_UPDATE_PO_Main

Create Standard Purchase Order using Web Services

Buyer creates multiple standard purchase orders using the web services and approves the SPO.

Buyer needs to login to purchasing responsibility and verify the above created standard purchase order in the application.

Flow Type

Web services

Technical Name

Create_Purchase_Order_WS

Prerequisites

• Web Services for purchasing must be deployed and configured.

• SOAP UI must be installed and WSDL mapping must be defined.

Profile Options

Not Applicable

Predefined Data

Not Applicable

Setup Data

The following data must be set up:

Window/User Name	Field Name	Field Value
Operating Unit	Vision Operations	Vision Operations
Responsibility	Responsibility	Purchasing, Vision Operations (USA)
Users	User	Operations
Document Style	Style Name	Standard Purchase Order

Description of the Scenarios in the Flow (Procurement)

Following are the details of the scenarios in the flow:

Scenario	Objective	Artifact/Method	Component Set	Main Component
Create_PO	This scenario creates a purchase order using the Web services	CreatePO_WS	POS_CPO	POS_CPO_Main
Get_PO_Number	This scenario fetches the PO number	-	-	Get_PO_Number_Interface

Update Price and Quantity of Standard Purchase Order using Web Services

Buyer updates the standard purchase order using the web services and approves.

Buyer needs to login to purchasing responsibility and verify the above updated standard purchase order in the application.

Flow Type

Web Services

Technical Name

Update_SPO_WS

Prerequisites

• Web Services for purchasing must be deployed and configured.

• SOAP UI must be installed and WSDL mapping must be defined.

Profile Options

Not Applicable

Predefined Data

Not Applicable

Setup Data

The following data must be set up:

Window/User Name	Field Name	Field Value
Operating Unit	Vision Operations	Vision Operations
Responsibility	Responsibility	Purchasing, Vision Operations (USA)
Users	User	Operations
Document Style	Style Name	Standard Purchase Order

Description of the Scenarios in the Flow (Procurement)

Following are the details of the scenarios in the flow:

Scenario	Objective	Artifact/Method	Component Set	Main Component
Create_PO	This scenario creates a purchase order using the open interface	Import_Standard_Purchase_Orders_POXPOPDOI	Import_Standard_Purchase_Orders_POXPOPDOI	Import_Standard_Purchase_Orders_POXPOPDOI
Get_PONumber	-	-	-	SELECT
Update_PO	This scenario is used to update the created purchase order line information from the above scenario	Purchase Order Service	POS_UPO	POS_UPO_Main

Procure to Pay End to End Flow using Open Interface, API and Web Services

Requester logs in with the iProcurement Responsibility and creates a requisition for Goods Line type for an item and approves it using Open Interface. Requester then imports the “Requisition Import Program” using concurrent request.

Buyer creates standard purchase order using the web services by giving the above requisition number as reference in the SPO and approves it.

Buyer updates the approved standard purchase order using the API and approves.

Purchase Order is received using concurrent program “Receiving Transaction Processor” which is an Open Interface.

Flow Type

Open Interface, PLSQL and Web services - Hybrid flow

Technical Name

End_to_End_PO_API

Prerequisites

• Web Services for purchasing must be deployed and configured.

• SOAP UI must be installed and WSDL mapping must be defined.

Profile Options

Not Applicable

Predefined Data

Not Applicable

Setup Data

The following data must be set up:

Window/User Name	Field Name	Field Value
Operating Unit	Vision Operations	Vision Operations
Change Org	Inventory Org	V1(Used for Receiving)
Responsibility	Responsibility	Purchasing, Vision Operations (USA)
Users	User	Operations
Document Style	Style Name	Standard Purchase Order

Description of the Scenarios in the Flow (Procurement)

Following are the details of the scenarios in the flow:

Scenario	Objective	Artifact/Method	Component Set	Main Component
Create_Req	This scenario creates a purchase requisition using the open interface	Requisition_Import_REQIMPORT	Requisition_Import_REQIMPORT	Requisition_Import_REQIMPORT
Create_PO	This scenario creates a purchase order using the Web services	Create_ PO	POS_CPO	SELECT
Retrive_PO			-	Get_PO_Number_Interface
Update_PO	This scenario is used to update the created purchase order line information from the above scenario	Update_PO	-	PO_Change_APIA_S_UPDATE_PO_Main
Receive_PO	This scenario is to receive the goods against the purchase orders created	Receiving_Transaction_Processor_RVCTP	Receiving_Transaction_Processor_RVCTP	Receiving_Transaction_Processor_RVCTP
Create_Recept_PO			Receiving_Transaction_Processor_RVCTP	Receiving_Transaction_Processor_RVCTP

Creating and Updating the Supplier and Supplier Site

Buyer logs in with Supplier Management Administrator responsibility and creates supplier and Supplier Site. Later updates the above created Supplier and Supplier Site details.

Flow Type

Open Interface

Technical Name

Create_Update_Vendor_PLSQL

Prerequisites

Not Applicable

Profile Options

Not Applicable

Predefined Data

Not Applicable

Setup Data

The following data must be set up:

Window/User Name	Field Name	Field Value
Operating Unit	Vision Operations	Vision Operations
Responsibility	Responsibility	Supplier Management Administrator
Users	User	Operations

Description of the Scenarios in the Flow (Procurement)

Following are the details of the scenarios in the flow:

Scenario	Objective	Artifact/Method	Component Set	Main Component
Create_Vendor	This scenario creates a supplier using the open interface	Supplier_Open_Interface_Import_APXSUIMP	Supplier_Open_Interface_Import_APXSUIMP	Supplier_Open_Interface_Import_APXSUIMP
Create_Vendor_Site	This scenario is used to create the supplier/vendor site details	Supplier_Sites_Open_Interface_Import_APXSSIMP	Supplier_Sites_Open_Interface_Import_APXSSIMP	Supplier_Sites_Open_Interface_Import_APXSSIMP
Update_Vendor	This Scenario is used to update the above created supplier/vendor details	Supplier_Open_Interface_Import_APXSUIMP	Supplier_Open_Interface_Import_APXSUIMP	Supplier_Open_Interface_Import_APXSUIMP
Update_Vendor_Site	This Scenario is used to update the above created supplier/vendor site details	Supplier_Sites_Open_Interface_Import_APXSSIMP	Supplier_Sites_Open_Interface_Import_APXSSIMP	Supplier_Sites_Open_Interface_Import_APXSSIMP