Oracle Projects Account generators
PAAPINVW — Project Supplier Invoice Account Generation
PAAPWEBX — Project Expense Report Account Generator
POWFPOAG — PO Account Generator
POWFRQAG – PO Requisition Account Generator
Project Supplier Invoice Account Generator
Project Supplier Invoice by default: The default process “Generate default account” contains nothing more than a dummy
procedure (PA_ACC_GEN_WF_PKG.AP_INV_ACC_UNDEFINED_RULES) which generates
the following message and aborts:
“The default workflow for the Oracle Payables account function Project Supplier Invoice charge Account has not been
customised.Please replace the dummy function in the default process for account generation by your own account generation method”.
Expense Report Account Generator
The default Expense Report Account Generator works as follows:
The vendor on an expense report must be associated with an employee. Employees can be assigned a default expense account in the employee setup in
Oracle Human Resources:
People->Enter and Maintain->Assignment->Purchase Order Information The account generator will use this default expense account. If it is not
defined you will get an error when you try to save your expense report.
PO/Requisition Account Generator
The PO and Requisition account generators actually generate a series of Accounts. Each has procedures to generate the charge/expense account,
the accrual account, the budget account and the variance account. Within the default account generator there is a separate process to generate each of these
accounts for project related purchase orders and requisitions.
PO Project-Related?
The default PO and Requisition Account Generator processes contain a procedure to determine if the PO or requisition is project-related or not.
This procedure (PO_WF_PO_CHARGE_ACC.IS_PO_PROJECT_RELATED) as defined is a dummy procedure that always returns false.
In order to generate specific accounts for project-related purchase orders and requisitions, this process must be modified, or the activity replaced with
another that accurately determines whether the object is projects-related.
A common technique to accomplish this is to replace the function activity with a Compare Number” function (available in the list of standard functions).
This function allows you to compare the value of the “Test value” (which you set to be the item attribute “Project id”) and the “Reference value” (which you set
to be the constant 0). The results of this function are “Greater Than”, “Less Than”, “Equal” or “Null”. It will return null if the test value is null.
Therefore branching off of this comparison you will have two transitions. One linked to the “Null” return value which leads to the non project-related
process, and one which is the <Default> encompassing all the other return values which leads to the project-related process. In this way, if the
project_id is not null, it will branch to the project related process.
Build Expense Project Accounts
There are four subprocesses of the default workflow which are called if the above process determines that the item is project related. They are all named
“Build Expense Project XXXX Account”, where XXXX could be Budget, Accrual, Variance or Charge. Like the Supplier Invoice process, there is no
default logic associated with any of these processes, and if there is a business need to enter project information and to generate different accounts based on that, they must be customized.
*********************************************************************
Process Flow from PO to PA
1. Create PO - No Accounting Entry
2. Receipts - Receiving > Receipts
Receiving Transaction Processor
Receipt:
Receiving Inventory Dr. (Receipt)
Accrued Expenses CR.(Receipt)
3.Receiving Transactions- Receiving >Receiving Transactions
Deliver:
Job Expense Dr. (Deliver) - as per Project AAR
Receiving Inventory Cr.(Deliver)
4. Create Payable Invoice
Navigation : Invoices > Entry > Invoices
AP Accrual Dr. (Accrued Expenses)
Liability Cr. (Accounts Payable)
5. Transfer Cost to PA.
Raw Cost Dr.
PROCURE TO PAY CYCLE
Oracle Purchasing: You enter Suppliers of different materials and products you want to purchase to manufacture a finished good that your organization plans to sell.
Oracle Purchasing: You prepare a Request for Quotation (RFQ) and send it to different suppliers to get the best and/or economical price for the product.Oracle Purchasing: Suppliers sends their quotations and you upload those quotations in Oracle Purchasing to get the best three quotes and further to get the one best quote. Oracle Purchasing: You prepare a Purchase Order(PO) against the best RFQ to buy the goods from the supplier who quoted the suitable price and sends the PO to that supplier Oracle Purchasing: The supplier receives the confirmation of purchase from PO and ships the ordered goods. You receive the goods enter aGoods Received Note (GRN) in Oracle Purchasing. Oracle Inventory / Oracle Assets: It’s up to you whether you want to receive the goods at your head office or you Inventory directly. In either case you move the received goods to your different Raw Material Inventory from Oracle Purchasing to Oracle Inventory and the Item Count increases. If the item is Asset Type then it will move to Oracle Assets at the time of Invoice creation in Oracle Payables. Oracle General Ledger: Once you move the goods to Oracle Inventory, it sends the Material Accounting to Oracle General Ledger. Oracle Payables: After this the supplier sends you the invoice for the purchased goods and you Enter or Match the invoice against the PO from Oracle Purchasing in Oracle Payables. As said before, if the item is Asset in nature then it will move to Oracle Asset. Oracle General Ledger: When you enter the invoice it means that you have created a Liability against that supplier and also you have recorded the expense incurred or asset purchased. Oracle Payables sends the invoice accounting to Oracle General Ledger. Oracle Payables: You pay the invoice and settle the Liability. Oracle General Ledger: The liability is settled and your cash movement account is updated. Oracle Cash Management: As you pay the invoice Oracle Payables sends the payment information to Oracle Cash Management for Bank Reconciliation. Once reconciled, Oracle Cash Management sends the updated Bank/Cash accounting entry to Oracle General Ledger. Oracle General Ledger: Your cash at bank is updated with actual balance. Oracle Process Manufacturing(OPM) / Oracle Discrete Manufacturing(ODM): You start the manufacturing of your final product. Both OPM or ODM requests the different raw materials from your inventory organizations and manufactures a finished good. Oracle Inventory: As the raw materials are issued to OPM and ODM the inventory sends the issuing material accounting to General Ledger and decreases the Item Count from the Raw Material Store. As the finished good is prepared, Oracle Inventory receives the finished good in Finished Good Store and increase the Item Count. Now the final product is ready to be sold in the market.
PAAPINVW — Project Supplier Invoice Account Generation
PAAPWEBX — Project Expense Report Account Generator
POWFPOAG — PO Account Generator
POWFRQAG – PO Requisition Account Generator
Project Supplier Invoice Account Generator
Project Supplier Invoice by default: The default process “Generate default account” contains nothing more than a dummy
procedure (PA_ACC_GEN_WF_PKG.AP_INV_ACC_UNDEFINED_RULES) which generates
the following message and aborts:
“The default workflow for the Oracle Payables account function Project Supplier Invoice charge Account has not been
customised.Please replace the dummy function in the default process for account generation by your own account generation method”.
Expense Report Account Generator
The default Expense Report Account Generator works as follows:
The vendor on an expense report must be associated with an employee. Employees can be assigned a default expense account in the employee setup in
Oracle Human Resources:
People->Enter and Maintain->Assignment->Purchase Order Information The account generator will use this default expense account. If it is not
defined you will get an error when you try to save your expense report.
PO/Requisition Account Generator
The PO and Requisition account generators actually generate a series of Accounts. Each has procedures to generate the charge/expense account,
the accrual account, the budget account and the variance account. Within the default account generator there is a separate process to generate each of these
accounts for project related purchase orders and requisitions.
PO Project-Related?
The default PO and Requisition Account Generator processes contain a procedure to determine if the PO or requisition is project-related or not.
This procedure (PO_WF_PO_CHARGE_ACC.IS_PO_PROJECT_RELATED) as defined is a dummy procedure that always returns false.
In order to generate specific accounts for project-related purchase orders and requisitions, this process must be modified, or the activity replaced with
another that accurately determines whether the object is projects-related.
A common technique to accomplish this is to replace the function activity with a Compare Number” function (available in the list of standard functions).
This function allows you to compare the value of the “Test value” (which you set to be the item attribute “Project id”) and the “Reference value” (which you set
to be the constant 0). The results of this function are “Greater Than”, “Less Than”, “Equal” or “Null”. It will return null if the test value is null.
Therefore branching off of this comparison you will have two transitions. One linked to the “Null” return value which leads to the non project-related
process, and one which is the <Default> encompassing all the other return values which leads to the project-related process. In this way, if the
project_id is not null, it will branch to the project related process.
Build Expense Project Accounts
There are four subprocesses of the default workflow which are called if the above process determines that the item is project related. They are all named
“Build Expense Project XXXX Account”, where XXXX could be Budget, Accrual, Variance or Charge. Like the Supplier Invoice process, there is no
default logic associated with any of these processes, and if there is a business need to enter project information and to generate different accounts based on that, they must be customized.
*********************************************************************
Process Flow from PO to PA
1. Create PO - No Accounting Entry
2. Receipts - Receiving > Receipts
Receiving Transaction Processor
Receipt:
Receiving Inventory Dr. (Receipt)
Accrued Expenses CR.(Receipt)
3.Receiving Transactions- Receiving >Receiving Transactions
Deliver:
Job Expense Dr. (Deliver) - as per Project AAR
Receiving Inventory Cr.(Deliver)
4. Create Payable Invoice
Navigation : Invoices > Entry > Invoices
AP Accrual Dr. (Accrued Expenses)
Liability Cr. (Accounts Payable)
5. Transfer Cost to PA.
Raw Cost Dr.
PROCURE TO PAY CYCLE
Oracle Purchasing: You enter Suppliers of different materials and products you want to purchase to manufacture a finished good that your organization plans to sell.
Oracle Purchasing: You prepare a Request for Quotation (RFQ) and send it to different suppliers to get the best and/or economical price for the product.