The Procure to Pay Process - P2P

Based on organizational practice and the requirement in question, procurement leaders choose to complete the most relevant stages of a procure-to-pay process. Here are nine logical steps of an ideal procure-to-pay process.

procure to pay processLogical steps of an ideal procure-to-pay process. 

This post explains the Procure-To-Pay process in layman’s terms.

Lets take the following scenario – A person wants to buy a car.

The tasks associated with this can be listed out as below :

1. Identify the car
2. Identify the vendor
3. Check for discounts available
4. Place the order
5. Receive the car
6. Make payment

The above are the major tasks that the person would have to do for getting the product at his place of choice. So, for understanding’s perspective, tasks 1 through 5 are grouped under Procurement or Purchasing while task 6 is a part of Payment or Payables.

Extending the understanding to an organizations’s perspective, we have the following :

Requester - The person who raises the request for an item. This could be anyone within the organization, authorized to raise purchasing requests.

Buyer – Generally a person from the Purchasing department. This person is tasked with collating all the items requested by various Requestors and placing purchasing orders to the vendors.

Vendor / Supplier – The person or an organization tasked with supplying the requested item.

Receiver – A person who receives the requested item.

Invoice – A document provided by the vendor to the buying organization having details of the item like item description, quantity, amount, tax and total amount payable.

So, going back to our earlier scenario :

Requestor is the person looking to buy a car. Buyer is the person who will identify the vendor, check for discounts and place the order. Vendor (or supplier or dealer in this example) will ship the car that will be received by the Receiver. Vendor will also send an invoice that will be paid by the buying organization.

This is how a typical Procure-To-Pay process works in an organization. Of course, in reality it is not so simple and has other functionalities / processes within each of the major tasks that we just saw.

A more detailed examination of this P2P process will be discussed in my subsequent posts. That will focus more on PeopleSoft terminologies and processes.

PeopleSoft Procure to Pay links Purchasing and Payables modules to provide control and visibility over the entire life-cycle of a transaction – right from the way an item is ordered to the way that the final invoice is processed.

If you are starting out as a Procure to Pay consultant, this list of tables will be a quick reference for you. The main application tables used in the Procure to Pay cycle are listed here.

Master data tables

ModuleTable NameDescription
APVENDORVendor Header
PO, INITEMItems
GLGL_ACCOUNT_TBLAccounts
GLDEPT_TBLDepartments
GLPRODUCT_TBLProducts
GLPROJECT_FSProjects
GLOPER_UNIT_TBLOperating Units
POMASTER_ITEM_TBLItem Master Header
PO, ININV_ITEMSInventory Item master
INSTOR_LOC_INVStorage Location Definition


Transaction tables

ModuleTable NameDescription
APVOUCHERAP Voucher Header
APDISTRIB_LINEVoucher Distribution Lines
APPAYMENT_TBLAP Disbursements
APPYMNT_ADVICEAP payment Advice Information
APVENDORVendor Header
APBUS_UNIT_TBL_APAP Business Unit table
AMASSETAsset general Information
AMASSET_ACQ_DETAsset Acquisition Detail
AMDEPRECIATIONDepreciation transactions
AMCOSTAsset Cost Transactions
POREQ_HDRRequisition header
POREQ_LNRequisition line
POPO_HDRPurchase order header
POPO_LINEPurchase order line
ARITEMCustomer Items
GLJRNL_HEADERJournal Headers
GLJRNL_LNJournal Line Data
INCM_ONHAND_VWOn hand quantity
INCM_INTRANSITInventory in transit
INTRANSACTION_INVInventory Transactions
ININ_DEMANDOrder Request
INPHYSICAL_INVPhysical Inventory


Accounting tables

ModuleTable NameDescription
APVCHR_ACCTG_LINEAP Accounting entries
AMDIST_LNAM Accounting entries
GLLEDGERLedger Data
ARITEM_DSTAR Accounting entries
POPO_LINE_DISTRIBPOline accounting entries
INCM_ACCTG_LINEINV Accounting Distribution


Entity Relationship Diagrams for PS Products

PeopleSoft ERD shows all the tables in the PeopleSoft database and the relationships between them. This information can be useful in identifying the relationships and dependencies between various components of the PS Application system and can help you understand the PS Application(HRMS/FSCM/CRM etc.) better.

For more information about ERDs, search for the document entitled “What is an ERD” on PeopleSoft Customer Connection

You can find the Data Models/ERDs at "1051533.1 - PeopleSoft Entity Relationship Diagrams" on oracle support (provided you have an account on Oracle Support)

At present following ERDs are available :

CS:      9.0/8.9 Note: 1053084.1
CRM:   9.1 Note: 986733.1, 9.0 Note: 978853.1, 8.9 Note: 981780.1
SCM/SRM:   9.2 Note: 1547384.1, 9.1  Note: 1074949.1, 9.0 Note: 975752.1,
                   8.9 Note: 981711.1, 8.8 Note: 989690.1
EPM:   9.1/9.0/8.9 Note: 985535.1
Portal: 9.1 Note:1061022.1, 8.9 Note: 988728.1


PeopleSoft offers ERDs for other products such as ELM, FMS, FSCM, CRM etc in direct PDF/web format which are easy to download & analyse.


HCM ERDs :
PeopleSoft provides ERDs for HCM as a change package/project which needs be to loaded into Database and then can be seen from Portal menu(PIA).

INSTALLATION : It takes between 45-60 mins.

Example : HCM 8.8 ERD installation

1. Use the Copy Project from Files function in PeopleSoft Application Designer
    to load the downloaded PRJ149571 project into your DEMO database.
    Specify the import directory path (example: C:\TEMP) that contains your update project.
[Local Directory]\UPD149571\PRJ149571
[Project]: PRJ149571

Built the record HC_TLS_ATTACH to create table PS_HC_TLS_ATTACH

2. run supplied dms to import UPD149571.DAT data

3. Perform below Steps in App Designer

Follow the instructions below to grant access to the component HC_TLS_ERD_VIEW

 a. File, Open, Component HC_TLS_ERD_VIEW in the Application Designer
     Tools, Register Component…
     On the “Registration Wizard Start” dialog:
     Check “Add this component to a menu”
     Uncheck “Add this component to a portal registry”
     Check “Add this component to a permission list”
     Click on the “Next” button

 b. On the “Registration Wizard – Add to Menu and Bar” dialog:
     Click on Select and select SETUP_HRMS menu
     Select SYSTEM from the dropdown list for Bar Name
     Click on the “Next” button

 c. On the “Registration Wizard – Add to Permission List” dialog:
     Click on Select and select HCCPHR9100 Permission List
     Check the checkboxes for “Add”, “Update/Display”, “Update/Display All” and “Correction” actions
     In the “Open” URI Base, replace the word “localhost” with your webserver name.
     Click on the “Next” button

 d. On the “Registration Wizard – Finish” dialog:
     Ensure that “Menu” and “Permission list” are the only ones checked on,
     in the “Add to Project” group. “Registry entry” must be unchecked.
     Click Finish

4.  Shutdown appserver, delete appserver and browser cache, startup appserver.

Note : To be able to see ERDs under "Data models" you need to be either PSADMIN/Super User or
need to have any one of these roles assigned to you

HR System Administrator
HR Technical/Admin

View ERDs under new menu "Data Models" at root level on PeopleSoft Portal (PIA).

The ERDs are static Read-Only format delivered in the form of PDF files. They are built based on the baseline version of the release, and are never updated until the next Service Pack or the next release. Hence they are based on Delivered data always.

Excel to Component Interface Utility

  To use the Excel to Component Interface utility, you must grant access to the iScript WEBLIB_SOAPTOCI in the permission list of the user w...