Case Study: Purchase Order Extract

Outbound

Author: Chandan A Kumar

Creation Date: Mar 13, 2009
Last Updated: Mar 13, 2009

Approvals:

Copy Number _____

 Mar 13, 2009

Document Control

Change Record
3

Date Author Version Change Reference

Reviewers

Name Position

Distribution

Copy No. Name Location

1
Library Master Project Library
2 Project Manager
3
4

Note To Holders:

If you receive an electronic copy of this document and print it out, please write
your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front
cover, for document control purposes.

Case Study: Purchase Order Extract Outbound

Introduction
File Ref: 402348185.doc
 Mar 13, 2009

Contents

Document Control..............................................................................................ii

Introduction........................................................................................................1
Purpose.........................................................................................................1
Background..................................................................................................1
Scope and Application..................................................................................1
Audience.......................................................................................................2
Source system..............................................................................................2
Assumptions.................................................................................................2
Pre-Requisites..............................................................................................3
Business Rules...........................................................................................3
Approach......................................................................................................4
Module List........................................................................................................5

Registering Concurrent Program........................................................................8

Downloading Concurrent Program Script........................................................14

Deployment......................................................................................................15

Extract File Layout...........................................................................................16

Calling Extract Custom Concurrent Program..................................................17

Open and Closed Issues for this Deliverable....................................................18

Open Issues................................................................................................18
Closed Issues..............................................................................................18

Case Study: Purchase Order Extract Outbound

Introduction
File Ref: 402348185.doc
Introduction
A purchase order (PO) is a commercial document issued by a buyer to
a supplier, indicating the type, quantities and agreed prices for products or
services the seller will provide to the buyer. It will specify payment terms,
delivery dates, item identification, quantities, shipping terms and all other
obligations and conditions.

Purchase orders are generally preprinted, numbered documents generated by

the retailer's financial management system, which shows that purchase details
have been recorded and payment will be made.

Use the Purchase Order window to enter the standard purchase order, blanket
purchase order, planed purchase order, purchase requisitions etc. You can also
query and update purchase order in this window.

To enter or query a Purchase Order from front end navigate to Purchasing

Responsibility, Select Purchase Orders -> Purchase Orders.

This document demonstrates the extract of purchase order data, which is

approved and received.

Purpose

This document describes the:

This case study is intended to demonstrate the extraction of data from
Oracle Applications Purchase Order for legacy system.
File layout to be used for interface.
Approach and technical design for extractions.

Background

This case study document is designed to demonstrate a practical scenario that

occurs during implementation of oracle Purchase Orders.

Scope and Application

The following boundaries are specific to the extractions of Purchase Order
data using PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL,
RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES standards table

 All standard purchase orders are available in Oracle Applications

1. The ‘XX<EMPID>: Purchase Orders Extract Program’
create a file which will contain Purchase Order data which
are approved and received.

Introduction
File Ref: 402348185.doc
 2. The ‘XX<EMPID>: Purchase Orders Extract Program’
have two parameters.
 Data File Path: Enter the path of Oracle
Applications Server, where this custom
concurrent program will create the file for
outbound.
 Data File Name: Enter the file name, which will
be used for naming the file while extracting the
data from Oracle Applications.

Audience

This document is intended for the following individuals:

This document should be used for demonstration purposes only.

Source system

The implementation team studies the source system and understands the data
required to be migrated from Oracle Applications to legacy system. This data is
then extracted and cleansed from the Oracle Applications (this is done by IT
team of source system) in the format as agreed by the client, source system IT
team and the implementation team.

Assumptions

This case study document is based on the following assumptions:

 Users have access to Oracle Applications for the following responsibility.

 Purchasing Super User

 System Administrator

 Users have access to Oracle Applications server access with write

privilege.

 Users have access to Oracle Applications database (apps schema)

 All the functional setups and master data (as listed in pre-requisites) are
already completed in Oracle Applications.

 The extract-file layout must be in the format as specified in the extract

file layout section

Introduction
File Ref: 402348185.doc
Pre-Requisites

Approved and Received Purchase order records should be available in

Oracle Applications

Business Rules

Following business rules are applicable for the Purchase Order extract process.
 Extract all the purchase order records which are approved and
received
 Please refer Extract file layout for the columns to be extract for
the purchase order.

PL/SQL UTL_F ILE Registercu stom

O racle
Package Utility concu rrentprogram
Applications

Approach

Call custom
Legacy DataFileIntroduction
File Ref: 402348185.doc System
FTPUtility concurrentp rogram
 The Approach for extracting Purchase Order data from Oracle Applications to
a data file is
1. Login to the Oracle Applications
2. Using PL/SQL write a package
3. Use UTL_FILE utility in PL/SQL package to create the data file
4. Data file would be created by custom concurrent program
5. Use any FTP utility to transfer the extract data file into legacy system.

Introduction
File Ref: 402348185.doc
Module List

Concurrent Programs
‘XX<EMPID>: Purchase Order Extract Program’

The ‘XX<EMPID>: Purchase Order Extract Program’ concurrent

program is based on the stored procedure
XXPO_PURCHASE_OUTBOUND_PKG.main that is registered as a
PL/SQL executable.

 The above program calls stored procedures to create the data file
(Data file name and path passed as parameter values)

NOTE:

1. Change the <EMPID> with your Employee ID,

2. Follow the steps for registering concurrent program from Registering

Concurrent Program section.

Stored Procedures
XXPO_PURCHASE_OUTBOUND_PKG package consist the following
stored procedures:

XXPO_PURCHASE_OUTBOUND_PKG.main

This is the main procedure that calls the create_headers and create_lines
procedures.

XXPO_PURCHASE_OUTBOUND_PKG.create_headers

This procedure is used to create the header for the extract file.

XXPO_PURCHASE_OUTBOUND_PKG.create_lines

This procedure is used to create the lines for the extract file.

NOTE: Please refer the attached documents for Package Specifications and
Package body. Kindly open the attached script in notepad.

XXPO_PURCHASE_O
UTBOUND_PKG.pks
1. Package Specification:

Introduction
File Ref: 402348185.doc
 XXPO_PURCHASE_O
UTBOUND_PKG.pkb
2. Package Body:

Grant Script
If package is created in custom schema then grant the package to APPS
schema

NOTE: Please refer the attached script for table and package granting. Kindly
open the attached script in notepad.

XXPO_PURCHASE_O
UTBOUND_PKG.grt
1. Package Grant Script:

Synonym Script
If table and package are created in custom schema then grant the package and
create synonym for table and package in APPS schema

NOTE: Please refer the attached script for table and package synonym. Kindly
open the attached script in notepad.

XXPO_PURCHASE_O
UTBOUND_PKG.syn
1. Package synonym script:

Install Script
Install script contains UNIX Shell Script and will be used to deploy the objects
attached to this document on Oracle Applications Server.

Following are the object to be deployed on server.

1. Package Specification Script
2. Package Body Script
NOTE: Please refer the attached Install script for deployment of Purchase
Order object on Oracle Applications Server. Kindly open the attached script in
notepad.

XXPO_PURCHASE_O
UTBOUND.install
1. Install Script:

Introduction
File Ref: 402348185.doc
 Note: Please prefix your employee ID for each object you create and deploy in
Application Server and Database.
A.) Package Name
B.) Table Name
C.) Synonym Name
D.) Concurrent Program Executable.
E.) Concurrent Program Name.

Introduction
File Ref: 402348185.doc
Registering Concurrent Program
Registering Extract Concurrent Program
To register a concurrent program for ‘XX<EMPID>: Purchase Order Extract
Program’ in Oracle Applications Navigate to System Administrator
Responsibility

1. Select Concurrent -> Program -> Executable

Introduction
File Ref: 402348185.doc
 2 Enter The Following in the Concurrent Program Executable Form
a. Executable Name: Enter unique name for executable.
b. Short Name: Enter unique short name and this short name later
will be use for defining Concurrent Program.
c. Application: Enter the Application Name from List of Values
(LOV), as we are developing an interface program for Purchase
Order so the Application Name should be Custom Application.
d. Description: Enter the description of Executable
e. Execution Method: Execution method should be PL/SQL Stored
Procedure.
f. Execution File Name: Here we would be passing the package
name with one public procedure. As discussed in Module List the
package name would be XXPO_PURCHASE_OUTBOUND_PKG
and the public procedure define in this package is main.

Concurrent Program Executable Form

Introduction
File Ref: 402348185.doc
 2. Select Concurrent -> Program -> Define

4. Enter The Following in the Concurrent Program Form

a. Program Name: Enter “XX<EMPID>: Purchase Order Extract
Program”
b. Short Name: Enter a unique concurrent program short name, for
example: XXPOOUTBOUNDMAIN
c. Application: Select the value from LOV, as we would be executing
this concurrent program from Payables Applications so select
Custom Development and add this concurrent program in Purchase
Order Request Group.
d. Description: Enter the description of this concurrent program.
e. Executable Name: Select the executable name from LOV, as we
have already registered an executable for loader program so select
XXPOOUTBOUNDMAIN from LOV.
f. Executable Method: Executable method will be populated
automatically.
g. Parameters if any: Select the Parameter Button to specify the
parameter list. In our case there should be two parameters we
would be passing. A) Data File Path B) Data File Name

Introduction
File Ref: 402348185.doc
 Concurrent Program Form

Concurrent Program Parameters Form

Introduction
File Ref: 402348185.doc
 Registering Interface Concurrent Program in Request Group
To register a concurrent program ‘XX<EMPID>: Purchase Order Extract
Program’ in Request Group, Navigate to System Administrator
Responsibility

1. Select Security -> Responsibility-> Request

Introduction
File Ref: 402348185.doc
 2. Query the Request Group – All Reports and Applications – Purchasing

Request Group Form

3. Add an entry for Concurrent Program in the Request Group and save the
work.

Request Group Form

Introduction
File Ref: 402348185.doc
Downloading Concurrent Program Script
After completion of Registering Concurrent program in System Administrator
responsibility, we can download the script for concurrent program and further
it can be used to install in another Application Server.

Before downloading the script of Concurrent Program, connect your local

system to Applications Server

Run the Following Command to download the script

FNDLOAD <Apps User/Apps Pwd> 0 Y DOWNLOAD

$FND_TOP/patch/115/import/afcpprog.lct <File_Name.ldt> PROGRAM
CONCURRENT_PROGRAM_NAME=<Concurrent_Program_Short_Name>

For Example:

 To Download the “XX<EMPID>: Purchase Order Extract

Program” script please enter the below command at unix/linux
prompt.

FNDLOAD apps/apps 0 Y DOWNLOAD

$FND_TOP/patch/115/import/afcpprog.lct
XXPURCHASEORDERLOAD.ldt PROGRAM
CONCURRENT_PROGRAM_NAME = XXPOOUTBOUNDMAIN

Introduction
File Ref: 402348185.doc
Deployment
 To deploy the attached zip file which contains package, table scripts, grant
script, synonym script, concurrent program script and install script, please
follow the below steps

XXPOOUTBOUND.tar
.gz

1. Save the attached zip file in local system

2. Transfer the zip to the Oracle Applications Server

3. Create a Staging Directory [E.g. XXPOOUTBOUND] in temporary

area on Oracle Application Server.

4. mkdir -p XXPOOUTBOUND

5. Change the Permissions on the temp directory.

6. chmod 755 XXPOOUTBOUND

7. FTP the XXPOOUTBOUND.tar.gz file in BINARY mode to

directory XXPOOUTBOUND

8. Change directory to XXPOOUTBOUND as given below

9. cd XXPOOUTBOUND

10. Uncompress XXPOOUTBOUND.tar.gz as given below

11. gunzip XXPOOUTBOUND .tar.gz

12. Untar the file XXPOOUTBOUND.tar using

13. tar -xvf XXPOOUTBOUND.tar.gz

14. Grant the execute permission on the install script using

15. chmod 755 XXPO_PURCHASE_OUTBOUND.install

16. Run XXPO_PURCHASE_OUTBOUND.install

17. sh XXPO_PURCHASE_OUTBOUND.install

18. Enter the apps schema user name password (apps/

<apps_pwd>), when asked for.

Introduction
File Ref: 402348185.doc
Extract File Layout
Data File Columns Datatype Size Table Name
PO_NUMBER VARCHAR2 30 PO_HEADERS_ALL
PO_TYPE VARCHAR2 25 PO_HEADERS_ALL
AGENT_NAME VARCHAR2 240 PER_ALL_PEOPLE_F
VENDOR_NAME VARCHAR2 240 AP_SUPPLIERS
VENDOR_SITE VARCHAR2 15 AP_SUPPLIER_SITES_ALL
PAYMENT_TERM VARCHAR2 30 AP_TERMS_TL
CURR_CODE VARCHAR2 30 PO_HEADERS_ALL
AUTH_STATUS VARCHAR2 25 PO_HEADERS_ALL
LINE_NUM NUMBER 1 PO_LINES_ALL
INVENTORY_ITEM VARCHAR2 30 MTL_SYSTEM_ITEMS
ITEM_DESCRIPTION VARCHAR2 250 MTL_SYSTEM_ITEMS
UOM VARCHAR2 25 MTL_SYSTEM_ITEMS
UNIT_PRICE NUMBER PO_LINES_ALL
LINE_QUANTITY NUMBER PO_LINES_ALL
RECEIPT_NUM VARCHAR2 30 RCV_SHIPMENT_HEADERS
QUANTITY_RECEIVED NUMBER RCV_SHIPMENT_LINES

Please find the attached extract file for Purchase Order, which has been
extracted, from Oracle Applications.

PO_EXTRACT_FILE.x
ls

Introduction
File Ref: 402348185.doc
Calling Extract Custom Concurrent Program
After installation of all the script attached with this document run the
concurrent program “XX<EMPID>: Purchase Order Extract Program”. To run
the concurrent program navigate to Purchasing Responsibility.

Use the below query to find out the path to create the extract file and use one
of the path from value to pass as parameter value for Data File path.
SELECT VALUE 

FROM V$PARAMETER 

WHERE NAME LIKE '%utl_file_dir%';

Select View Menu -> Request, Submit a new request, and click on single
request and than click OK Button.

SRS Form

1. Select the Concurrent Program name from LOV

2. Enter the parameter value for Data File Path and Data File Name.
3. Click on Submit Button to run the request.

Introduction
File Ref: 402348185.doc
Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Introduction
File Ref: 402348185.doc