P2P Technical, Functional and GL Flow

P2P Technical Flow(Complete Query)
/* Formatted on 6/23/2014 5:26:24 PM (QP5 v5.115.810.9015) */

SELECT prh.segment1 "PO Requisition Number",
pha.segment1 "PO Number",
aps.segment1 "Supplier Number",
aps.vendor_name,
apss.vendor_site_code,
apsc.first_name,
apsc.last_name,
pla.item_id,
plla.ship_to_organization_id,
plla.ship_to_location_id,
rt.transaction_type,
rt.destination_type_code,
rsh.receipt_num "PO Receipt Number",
aia.invoice_num,
aida.dist_code_combination_id,
aca.check_number,
gjh.ledger_id,
gjh.name
FROM po_requisition_headers_all prh,
po_requisition_lines_all prl,
po_req_distributions_all prd,
po_headers_all pha,
po_lines_all pla,
po_distributions_all pda,
po_line_locations_all plla,
ap_suppliers aps,
ap_supplier_sites_all apss,
ap_supplier_contacts apsc,
rcv_transactions rt,
rcv_shipment_headers rsh,
rcv_shipment_lines rsl,
ap_invoices_all aia,
ap_invoice_lines_all aila,
ap_invoice_distributions_all aida,
ap_invoice_payments_all aipa,
ap_checks_all aca,
xla.xla_transaction_entities xte,
xla_events xe,
xla_ae_headers xah,
xla_ae_lines xal,
xla_distribution_links xdl,
gl_import_references gir,
gl_je_batches gjb,
gl_je_headers gjh,
gl_je_lines gjl
WHERE prh.segment1 = :requitionnumber --Right click :RequitionNumber from Toad Enable
Prompt For Substitution Variables
AND aps.vendor_id = pha.vendor_id
AND apss.vendor_id = aps.vendor_id
AND apss.vendor_site_id(+) = pha.vendor_site_id
AND apss.vendor_site_id = aca.vendor_site_id
AND apsc.vendor_site_id = apss.vendor_site_id
AND apsc.vendor_contact_id = pha.vendor_contact_id
AND prl.requisition_header_id = prh.requisition_header_id
AND prd.requisition_line_id = prl.requisition_line_id
AND pda.req_distribution_id = prd.distribution_id
AND pla.po_header_id = pda.po_header_id
AND pla.po_line_id = pda.po_line_id
AND pha.po_header_id = pla.po_header_id
AND pha.org_id = 204
AND plla.po_header_id = pla.po_header_id
AND plla.po_line_id = pla.po_line_id
AND rt.transaction_type = 'DELIVER'
AND rt.po_header_id = pha.po_header_id
AND rt.po_line_id = pla.po_line_id
AND rsh.shipment_header_id = rt.shipment_header_id
AND rsl.shipment_header_id = rsh.shipment_header_id
AND rsl.shipment_line_id = rt.shipment_line_id
AND aila.po_header_id = pha.po_header_id
AND aila.po_line_id = pla.po_line_id
AND aia.invoice_id = aila.invoice_id
AND aida.invoice_id = aila.invoice_id
AND aida.invoice_line_number = aila.line_number
AND aipa.invoice_id = aia.invoice_id
AND aca.check_id = aipa.check_id
AND xte.entity_code = 'AP_PAYMENTS'
AND xte.transaction_number = aca.check_number
AND xte.source_id_int_1 = aipa.check_id
AND xte.security_id_int_1 = aia.org_id
AND xe.entity_id = xte.entity_id
AND xah.event_id = xe.event_id
AND xal.ae_header_id = xah.ae_header_id
AND xal.ae_line_num = aida.invoice_line_number
AND xdl.ae_header_id = xah.ae_header_id
AND xdl.ae_line_num = xal.ae_line_num
AND xdl.applied_to_dist_id_num_1 = aida.invoice_distribution_id
AND gir.reference_5 = xte.entity_id
-- Entity Id
AND gir.reference_6 = TO_CHAR (xe.event_id)
--Event Id
AND gir.reference_7 = TO_CHAR (xah.ae_header_id)
-- AE Header Id
AND gir.gl_sl_link_id = xal.gl_sl_link_id
--and gir.created_by = 1318

AND gjb.je_batch_id = gir.je_batch_id
AND gjh.je_batch_id = gjb.je_batch_id
AND gjh.je_header_id = gir.je_header_id
AND gjl.je_header_id = gjh.je_header_id
AND gjl.je_line_num = gir.je_line_num
Posted by Elangovan Ragavan at 17:27 1 comment:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: P2P Cycle, PO
Friday, 6 June 2014
11i vs. R12 Procure to Pay (P2P) Cycle different in oracle apps
1) Create Requisition:
Requisition is nothing but a formal request to buy something (like Inventory material, office
supplies etc.) needed for the enterprise. Only an employee can create one.
There are two types of requisitions:
Internal Requisition: Internal requisitions provide the mechanism for requesting and
transferring material from one inventory to other inventory.
Purchase requisition: Unlike Internal requisitions, Purchase requisitions are used for
requesting material from suppliers.
Navigation:
Purchasing Vision Operations (USA) > Requisitions > Requisitions.
1. Choose the requisition type and enter the Item, quantity, Price details in the Lines tab.
2. In Source Details tab, specify the Buyer name.
3. Click the Distributions button. Enter the Charge Account.
4. Save the work. The status of the requisition will now be Incomplete. And now the
Approve button is highlighted.
The requisition needs to be approved first before proceeding further by the concerned authority.
Submit this requisition for Approval by clicking on the Approve button. The status will now be
updated to In Process .The workflow then will send an Approval notification to the concerned
person (derived based on hierarchy used Position or Supervisor hierarchy) using which he can
Approve or Reject the requisition.
At any time the status of requisition can be checked using the Requisition summary
window. Navigation (Requisitions > Requisition Summary). Here enter requisition
number and click on the find button.
We can also check the Action History of requisition (it will show details about who has
submitted, approved and cancelled the requisitions). Navigation (Tools menu > Action
History).
Underlying Tables:
o
PO_REQUISITION_HEADERS_ALL
PO_REQUISITION_LINES_ALL
PO_REQ_DISTRIBUTIONS_ALL
Without changing Responsibility and without closing windows buyers will now be able to view
consolidated requisition demand spanning multiple operating units. The operating units that
buyers can transact on behalf of will be controlled by the security profile associated with their
responsibilities.
Operating Unit extra field in the R12 forms due to MOAC.
Base tables are same as 11i but more than 15 extra columns in R12 for the table
PO_REQUISTION_HEADERS_ALL, PO_REQUISTION_LINES_ALL
and PO_REQ_DISTRIBUTIONS_ALL for tax etc.
Many changes were happened in supplier details in R12.
Note: Suppliers into TCA Architecture in R12:

Prior to R12 the suppliers information is stored in PO_VENDORS. From R12 onwards
suppliers have been moved in to the TCA Data Model.
HZ_PARTIES: This is the master table for suppliers.
HZ_PARTY_USG_ASSIGNMENTS: This table stores the Party Usages, for example,
for the suppliers it captures the fact that the given party_id is of type SUPPLIER.
HZ_ORGANIZATION_PROFILES: This table captures additional Supplier

information, for example, credit scoring details of Supplier or the Number of Employees
working in Supplier Organization.
IBY_EXTERNAL_PAYEES_ALL: It captures payment related details of the supplier.

Like how should the suppliers remittance advice must be sent, default Payment method
Code for this supplier, who bears the bank charges when lets say SWIFT payment is
made?
AP_SUPPLIERS: This is another master table that replaces the PO_VENDORS table. It
stores the supplier specific attributes.
POS_SUPPLIER_MAPPINGS: This table holds the mapping between the

AP_SUPPLIERS.VENDOR_ID and HZ_PARTIES.PARTY_ID. This is useful in cases
whereby two vendors effectively belong the same HZ_Party Record.
ZX_PARTY_TAX_PROFILE: The taxation related details like Tax Codes, and Tax
Accounts etc. have been moved from AP into ZX. ZX is the name of a new Application
E-Business Tax.
PO_VENDORS: PO_VENDORS is a view in R12, which joins AP_SUPPLIERS &

HZ_PARTIES.
Similarly, PO_VENDOR_SITES and PO_VENDOR_SITES_ALL are also views based

upon AP_SUPPLIER_SITES_ALL.
2) Create Purchase Order:
There are 4 types of Purchase Orders:

1. Standard PO: A Standard PO is created for onetime purchase of various items.
2. Planned PO: A Planned PO is a long-term agreement committing to buy items or services
from a single source. You must specify tentative delivery schedules and all details for goods or
services that you want to buy, including charge account, quantities, and estimated cost.
3. Blanket agreement: A Blanket PO is created when you know the detail of the goods or
services you plan to buy from a specific supplier in a period, but you do not know the detail of
your delivery schedules.
4. Contract agreement: Contract purchase agreements are created with your suppliers to agree
on specific terms and conditions without indicating the goods and services that you will be
purchasing
Navigation for creating a standard PO:
1. Purchase Orders > Purchase Orders
2. Choose type as Standard Purchase Order. Enter the Supplier, Buyer. In the Lines tab,
specify the line number, line type, Item, quantity, price etc.
3. Click Terms to enter terms, conditions, and control information for purchase orders.
4. Click Currency button to enter and change currency information for purchase orders,
RFQs, and quotations.
5. Click Shipments button to enter multiple shipments for standard and planned purchase
order lines Purchase order shipment specifies the quantity, ship-to organization and
location, date you want your supplier to deliver the items on a purchase order line, and
country of origin for the items. When you save, Purchasing creates distributions
depending on the default information available.
6. To enter more shipment information, select the More tab.
7. Enter the Receipt Close Tolerance percent, Invoice Close Tolerance percent to set the
receiving and invoice close point.
8. Select one of the following options for Match Approval Level:
TwoWay: Purchase order and invoice quantities must match within tolerance before the
corresponding invoice can be paid.
ThreeWay: Purchase order, receipt, and invoice quantities must match within tolerance
before the corresponding invoice can be paid.
FourWay: Purchase order, receipt, accepted, and invoice quantities must match within
tolerance before the corresponding invoice can be paid.
1. Select an Invoice Match Option
Purchase Order: Payables must match the invoice to the purchase order.
Receipt: Payables must match the invoice to the receipt.
1. Save the work.

2. Click the Receiving Controls button to enter receiving control information for purchase
orders.
3. Enter the maximum acceptable number of Days Early and Days Late for receipts.
4. Enter the Action for receipt date control.
5. Enter the maximum acceptable over-receipt Tolerance percent (receipts that exceed the
quantity received tolerance).
6. Enter the Action for Over-receipt Quantity.
7. Select Allow Substitute Receipts to indicate that receivers can receive substitute items in
place of ordered items.
8. Enter the default Receipt Routing that you assign goods: Direct Delivery, Inspection
Required, or Standard Receipt.
9. Enter the Enforce Ship To location option to determine whether the receiving location
must be the same as the ship-to location.
10. Save the work.
11. Click Distributions button to enter distributions for the shipments.
12. Select more tab to enter more details and the requisition number (optional).
13. Save the work.
14. Click on the Approve button to initiate the Approval process.
Underlying Tables:
PO_HEADERS_ALL
PO_LINES_ALL
PO_DISTRIBUTIONS_ALL (REQ_HEADER_REFERENCE_NUM in Distributions

table is the Requisition number for this PO)
PO_LINE_LOCATIONS_ALL
For creating a Purchase order, let us use the Autocreate Documents Form. Follow the below
Navigation and Query for the Requisition.
1. Click on Automatic to create a Purchase Order.
2. Click on Create button to create a Purchase order.
3. View the shipment screen to change the Match Approval Level to 2-Way.
4. Click the Receiving Controls to make sure that the Routing is made as Direct
Routing
5. Click Save and submit for Approval.
Note:
1. In Release 11i10 generation of purchasing documents in Adobe PDF format required
organizations to create layout templates in the form of XSL-FO style sheets. With
Release 12.0 organizations can also use RTF or PDF layout templates which require little
training to configure and maintain.
2. Base tables are same as 11i but few extra columns.
3. Release 12.0 allows finer control of how blanket agreements are enabled for automatic
document sourcing. Buyers can now choose to enable them only in specific inventory
organizations.
3) Create Receipt:
Create a receipt to receive the items in the Purchase Order.

Navigation:
1. ReceivingReceipts.
2. Enter the PO Number and select find button.
3. Go to Lines; check the lines you want to receive in the PO.
4. Click on Header button and save which creates the receipt.
5. Now you can check the Inventory in the same subinventory for the items on-hand
quantity.
Receipt Tables are:
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES (Lines Table has PO_HEADER_ID)
Navigate to RECEIVING>RECEIPTS
Query with the Purchase order created in the above stage.
Check the check box near to the lines that are received and click save.
Click the Header Button to view the Receipt Number.
Note:
Base tables are same as in 11i but few extra columns.
4) Create Invoice in Payable:
Once the goods are received, its time to pay the vendor for the goods purchased and hence the
invoices are created.
1. Navigation: Payables, Vision Operations (USA) > Invoices Entry> Invoices
2. Enter type Standard, supplier information and amount.
3. Click the Match button to match to either Purchase Order or Receipt (depending on the
Invoice Match option specified on the PO) and avoid manually entering the invoice.
4. Enter the PO Number you want match to and click Find.
5. Select the lines required and click on Match button.
6. Click on Distribute button to navigate to the Match to Purchase Order Distributions
window.
7. This creates the invoice and you can see the status of the invoice as Never Validated. It
has to be Validated and Accounted before you can pay it.
8. Validating the Invoice: Click on Actions Button and Select Validate. Click on OK button.
9. Now you can see the status of the invoice as Validated, if there are no issues during
validation.
10. Create Accounting Entries: Click on Actions Button and Select Create Accounting. Click
on OK button.
11. You can see the Accounting Entries here: Tools View Accounting.
12. Now we can see the Accounted status as Yes.
Invoice Tables:
AP_INVOICES_ALL
AP_INVOICE_DISTRIBUTIONS_ALL
Accounting Entries Tables:
AP_ACCOUNTING_EVENTS_ALL
AP_AE_HEADERS_ALL
AP_AE_LINES_ALL
Creating invoices, debit memo, credit memo and do payments for the suppliers. The information
regarding these invoices are stored into ap_invoices_all and also in in to ap_invoice_lines_all.
AP_INVOICE_LINES_ALL holds invoice lines records entered manually, generated
automatically or imported from the Open Interface tables. An invoice can have one or more
invoice lines and an invoice line can have one or more invoice distributions. An invoice line
represents goods (direct or indirect materials), service(s), and/or associated
tax/freight/miscellaneous charges invoiced from a supplier.
Till 11i version, we have seen invoices:
Had only distributions line.
Allocation of freight and special charges are captured at the distribution level only.
Tax and payment and Project accounting Payment was captured through global
Descriptive Flexfields.
But in R12:
Invoice Lines as a new additional line accommodated in Invoice data model.
Allocate freight and special charges are captured to the lines on the invoice.
Invoice distributions created at the maximum level of detail similar to 11i.
Because of introduction of invoice lines there is significant improvement of data flow with other
oracle modules
Fixed Asset Asset Tracking
Business Tax Tax line
Payment Payment
SubLedger Accounting Accounting
5) Making a Payment:
1. Go to the Invoice window and query the invoice you want to pay. You would see Amount
paid as 0.00 before you make a payment.
2. Click Actions button. Select Pay in full and click OK.
3. Select the bank account and Document. Save the Work.
4. Now that the payment is made, when you query for the invoice in Invoice window, you
will find the Amount Paid.
5. Create Accounting entries for payment. Click Actions and select Create Accounting.
6. Select the void checkbox to cancel the payment.
7. View Accounting Entries: In the Payments window, query for the payment. Tools>
menu>View Accounting.
8. You can also pay the invoices using Payment Batch screen.
Payment Tables:
AP_INVOICE_PAYMENTS_ALL
AP_PAYMENT_SCHEDULES_ALL
AP_CHECKS_ALL
AP_CHECK_FORMATS
AP_BANK_ACCOUNTS_ALL
AP_BANK_BRANCHES
AP_TERMS
Once invoice got approved, click actions so that we can Create Accounting and Create
Payments via Action Button in the Invoice Form as we validated the invoice.
Suppliers Bank Accounts:
In 11i, Banks and Branches are defined in AP. Due to this, Bank accounts often replicated
in multiple OUs.
In R12, Suppliers, Banks and Branches are defined as Parties in TCA. Supplier (partys)
payment information and all payment instruments (Bank Accounts, Credit Cards) moved
into Oracle Payments.
6) Transfer to General Ledger:
Navigation:
Payables Responsibility > View Requests
Run the concurrent program Payables Transfer to General Ledger with the required parameters.
Journal Import: To transfer the data from General Ledger Interface table to General Ledger, run
the Journal Import program from Oracle General Ledger.
1. Navigation: General Ledger > Journal> Import> Run
2. Select the appropriate Source.
3. Enter one of the following Selection Criteria:
No Group ID: To import all data for that source that has no group ID. Use this option if
you specified a NULL group ID for this source.
All Group IDs: To import all data for that source that has a group ID. Use this option to
import multiple journal batches for the same source with varying group IDs.
Specific Group ID: To import data for a specific source/group ID combination. Choose a
specific group ID from the List of Values for the Specific Value field.
1. If you do not specify a Group ID, General Ledger imports all data from the specified
journal entry source, where the Group_ID is null.
2. Define the Journal Import Run Options (optional).
3. Choose Post Errors to Suspense if you have suspense posting enabled for your set of
books to post the difference resulting from any unbalanced journals to your suspense
account.
4. Choose Create Summary Journals to have journal import create the following:
One journal line for all transactions that share the same account, period, and currency and
that has a debit balance.
One journal line for all transactions that share the same account, period, and currency and
that has a credit balance.
1. Enter a Date Range to have General Ledger import only journals with accounting dates in
that range. If you do not specify a date range, General Ledger imports all journals data.
2. Choose whether to Import Descriptive Flexfields, and whether to import them with
validation.
3. Click on Import button.
Posting:
We have to Post journal batches that we have imported previously to update the account balances
in General Ledger.
1. Navigation: General Ledger> Journals > Enter
2. Query for the unposted journals for a specific period.
3. If you know the batch name to be posted you can directly post using the Post window.
Navigation: General Ledger> Journals> Post
Navigation:
Payables Responsibility > View >Requests
Run the concurrent program create accounting with the required parameters.
Mode= Final
Post in GL = yes.etc
The Create Accounting process has similar options, you can create accounting in Final or Draft
mode and if Final mode is selected, the Transfer to GL parameter can be used to automatically
transfer the accounting created by the corresponding run. When the Create Accounting process
transfers the journal entries to GL it only transfers the accounting created by the process that
calls it. If there is accounting created by the online option = Final or a previous Create
Accounting program that was not transferred, that accounting will not be transferred. The
Transfer Journal Entries to GL program needs to be run separately to transfer any accounting
created online or created by a previous Create Accounting process that did not transfer the
entries.
Note:
1. In R12 the adjustment in GL is automated. No manual journal is required. The create
accounting program and Transfer to GL program will transfer the write off journals
automatically to General Ledger.
2. In Release 11i you reconciled your transactions and distributions to General Ledger
through transactional reports. In the accounting reports in Release 11i youd see the
balances but not the transactional information. In Release 12 there is no reason to
reconcile distributions on transactions to General Ledger. You can still reconcile
transaction reports to accounting reports. The new accounting reports in Release 12 now
also contain more comprehensive information not just on balances but also on suppliers,
customers and transactions. The point to note is that when you do account balance
reconciliation you should ignore distributions in Release 12, especially if you have
altered your subledger accounting rules.
Posted by Elangovan Ragavan at 08:46 2 comments:
Labels: P2P Cycle
Sunday, 18 May 2014
Pay on Receipt(s) in Oracle Apps R12
Pay on Receipt(s) in Oracle Apps R12
POR (Pay on Receipt) is a feature in P2P cycle. Its helping to generate the invoice automatically
when you receive the goods.
Pre-Requisites
1. Supplier site should be enabled the following flags. (PAY and PURCHASING)
2. "Pay on" field should have a value "Receipt". The invoice summary level should also have the
value of "Receipt".
3. In Purchase Order; Terms window "Pay On" field value should be "Receipt".
1. Supplier Creation
Navigation (Purchasing Super User > Supply Base > Suppliers > Create Supplier)
Name : SUPPLIER_1
Type : Standard
Country : United States
2. Supplier Site Creation (Address Book)
Enter valid address and check the PURCHASING & PAYMENT flags.
3. Purchase Order Creations

** For an example, I am creating the Blanket PO. (for an easy process/testing purpose, we can
create multiple requisitions against this PO.)
(Approval Notification)
4. Just ensure the Approved Supplier list. (Supplier, Site and Item) If the combination is not
present please create the same.
5. Define the Sourcing Rule and assign the same into "Assignment Set"
6. Create the PO Requisitions for the item as we mentioned in PO. (Complete the approval and
Release process.)
Inventory Responsibility >> Receipts
Purchasing Responsibility >> Requests >> Submit Request ("Pay On Receipt Autoinvoice")
It's automatically submits the "Payables Open Interface Import". Verify the invoice details ...

Labels: AP_Module, FUNCTIONAL, P2P Cycle
Tuesday, 24 December 2013

Purchase module sub-query in oracle apps
SELECT segment1
FROM po_headers_all
WHERE po_header_id IN (SELECT po_header_id
FROM po_lines_all
WHERE po_header_id = 756464)
SELECT segment1
FROM po_headers_all
WHERE po_header_id IN
(SELECT po_header_id
FROM po_lines_all
WHERE po_header_id IN (SELECT po_header_id
FROM po_distributions_all
WHERE po_header_id = 756464))
SELECT segment1
FROM po_headers_all
FROM po_lines_all
WHERE PO_DISTRIBUTION_ID IN
(SELECT PO_DISTRIBUTION_ID
FROM rcv_transactions
WHERE PO_DISTRIBUTION_ID =
53129)))

SELECT segment1
FROM po_headers_all
FROM po_lines_all
WHERE SHIPMENT_LINE_ID IN
(SELECT SHIPMENT_LINE_ID
FROM RCV_SHIPMENT_LINES
WHERE SHIPMENT_LINE_ID =
3011))))
SELECT segment1
FROM po_headers_all
FROM po_lines_all
FROM RCV_SHIPMENT_HEADERS
WHERE SHIPMENT_LINE_ID =
3005)))))
Friday, 29 November 2013
PO TO GL LINK IN R12
PO TO GL LINK IN R12( THROUGH XLA) or ( WITH XLA )
SELECT prh.segment1 "PO Requisition Number",
pha.segment1 "PO Number",
aps.SEGMENT1 "Supplier Number",
aps.vendor_name,
apss.vendor_site_code,
apsc.first_name,
apsc.last_name,
pla.item_id,
plla.ship_to_organization_id,
plla.ship_to_location_id,
rt.transaction_type,
rt.destination_type_code,
rsh.receipt_num "PO Receipt Number",
aia.invoice_num,
aida.dist_code_combination_id,
aca.check_number,
gjh.ledger_id,
gjh.name
FROM po_requisition_headers_all prh,
po_headers_all pha,
po_lines_all pla,
po_distributions_all pda,
po_line_locations_all plla,
ap_suppliers aps,
ap_supplier_sites_all apss,
ap_supplier_contacts apsc,
rcv_transactions rt,
rcv_shipment_headers rsh,
rcv_shipment_lines rsl,
ap_invoices_all aia,
ap_invoice_lines_all aila,
ap_invoice_distributions_all aida,
ap_invoice_payments_all aipa,
ap_checks_all aca,
xla.xla_transaction_entities xte,
xla_events xe,
xla_ae_headers xah,
xla_ae_lines xal,
xla_distribution_links xdl,
gl_import_references gir,
gl_je_batches gjb,
gl_je_headers gjh,
gl_je_lines gjl
WHERE
prh.segment1 = :RequitionNumber--Right click :RequitionNumber from Toad
Enable Prompt For Substitution Variables
AND aps.vendor_id = pha.vendor_id
AND apss.vendor_id = aps.vendor_id
AND apss.vendor_site_id(+) = pha.vendor_site_id

AND apss.vendor_site_id = aca.vendor_site_id
AND apsc.vendor_site_id = apss.vendor_site_id
AND apsc.vendor_contact_id = pha.vendor_contact_id
AND prl.requisition_header_id = prh.requisition_header_id
AND prd.requisition_line_id = prl.requisition_line_id
AND pda.req_distribution_id = prd.distribution_id
AND pla.po_header_id = pda.po_header_id
AND pla.po_line_id = pda.po_line_id
AND pha.po_header_id = pla.po_header_id
AND pha.org_id = 204
AND plla.po_header_id = pla.po_header_id
AND plla.po_line_id = pla.po_line_id
AND rt.transaction_type = 'DELIVER'
AND rt.po_header_id = pha.po_header_id
AND rt.po_line_id = pla.po_line_id
AND rsh.shipment_header_id = rt.shipment_header_id
AND rsl.shipment_header_id = rsh.shipment_header_id
AND rsl.shipment_line_id = rt.shipment_line_id
AND aila.po_header_id = pha.po_header_id
AND aila.po_line_id = pla.po_line_id
AND aia.invoice_id = aila.invoice_id
AND aida.invoice_id = aila.invoice_id
AND aida.invoice_line_number = aila.line_number
AND aipa.invoice_id = aia.invoice_id
AND aca.check_id = aipa.check_id
AND xte.entity_code = 'AP_PAYMENTS'
AND xte.transaction_number = aca.check_number
AND xte.source_id_int_1 = aipa.check_id
AND xte.security_id_int_1 = aia.org_id
AND xe.entity_id = xte.entity_id
AND xah.event_id = xe.event_id
AND xal.ae_header_id = xah.ae_header_id
AND xal.ae_line_num = aida.invoice_line_number
AND xdl.ae_header_id = xah.ae_header_id
AND xdl.ae_line_num = xal.ae_line_num
AND xdl.applied_to_dist_id_num_1 = aida.invoice_distribution_id
AND gir.reference_5 = xte.entity_id
-- Entity Id
AND gir.reference_6 = TO_CHAR (xe.event_id)
--Event Id
AND gir.reference_7 = TO_CHAR (xah.ae_header_id)
-- AE Header Id
AND gir.gl_sl_link_id = xal.gl_sl_link_id
--and gir.created_by = 1318
AND gjb.je_batch_id = gir.je_batch_id
AND gjh.je_batch_id = gjb.je_batch_id
AND gjh.je_header_id = gir.je_header_id
AND gjl.je_header_id = gjh.je_header_id

AND gjl.je_line_num = gir.je_line_num
Monday, 21 January 2013
P2P FAQ
1.
2.
In which table is Purchase order number stored?

Ans: po_headers_all
How many types of purchasing matching option are there?
Ans: 3
3.
Types of purchasing matching options?

Ans: 2 way, 3 way, 4 way
4.
4. How many types of purchase orders are present in Oracle?

Ans: 4
5.
5. The purchase order which consists of Supplier, Item and Cost but doesnt know the delivery
schedules
Ans: Blanket purchase Agreement
6.
Which purchase order is a long-term agreement committing to buy items or services from a
single source having tentative delivery schedules and all details for goods or services that you
want to buy, including charge account, quantities, and estimated cost.
Ans: Planned purchase order
7.
How many types of Approval Hierarchies are used in purchasing?

Ans: 2
8.
What are the types of Approval Hierarchies used in purchasing?

Ans: Employee-Supervisor Hierarchy and Position Hierarchy
9.
Purchasing performs matching to verify that purchase order and invoice information Match
within tolerance this is called as
Ans: 2 way
10. Purchasing performs matching to verify the purchase order, receipt, and invoice information
match within tolerance this is called as
Ans: 3 way
11. Purchasing performs matching to verify the purchase order, receipt, inspection, and invoice
information match within tolerance this is called as
Ans: 4 way
12. A statement of the price, terms, and conditions of sale a supplier offers you for and item or items
is called as
Ans: Quotation
13. A document you use to solicit supplier quotations for goods or services you need is called as
Ans: Request for quotation (RFQ)
Labels: P2P Cycle
P2P TABLES
Usual Oracle Applications PO Tables
PO_HEADERS_ALL: Purchase Order information with Supplier, Site and status
PO_LINES_ALL: PO Lines with Item Information and quantity
PO_LINE_LOCATIONS_ALL: PO Information on Shipments Destination
PO_DISTRIBUTIONS_ALL: PO Distribution where the accounts are
PO_LINE_LOCATIONS_ARCHIVE_ALL: table updated for history on Shipment/Destination
Location Information
PO_LINE_TYPES_B: PO Types used in the PO_LINES_ALL

PO_LINES_TYPES_TL: PO Line Types used in MLS
PO_RELEASES_ALL: Stores revision number for the PO
PO_HEADERS_ARCHIVE_ALL: table updated for the history on the status and PO Header
changes, Lines, Location and PO Accounts Distribution
PO_LINES_ARCHIVE_ALL: table updated for the history on the lines
PO_DISTRIBUTIONS_ARCHIVE_ALL: table updated for the history on the account
distribution
PO_AGENTS_ALL_V: Buyer
PO_VENDORS: Supplier Table - R - ap_suppliers
PO_VENDOR_SITES: Supplier Sites
PO_VENDOR_CONTACTS: Supplier Contacts
PO_HAZARD_CLASSES: contains code and description for hazardous items which gets
automatically printed into purchase order, RFQ and Receipt Travelers
PO_REQUISITION_LINES_ALL: Requisition Lines
PO_REQUISITION_HEADERS_ALL: Requisition Headers
PO_REQ_DISTRIBUTIONS_ALL: Distribution Lines of Requisition where accounts are
PO_APPROVED_SUPPLIER_LIST: Supplier List for Auto-Sourcing
PO_ASL_DOCUMENTS: Advanced Shipment Documents
PO_APPROVAL_LIST_HEADERS: PO Approval Path
PO_APPROVAL_LIST_LINES: PO Approval Path
Labels: P2P Cycle
Friday, 3 August 2012
PO MATCH IN ORACLE APPS
How many ways for matchingThey are mainly 3 ways:

2-ways
3-ways
4-ways
How to explain
2-way matching
This verifies verifies that Purchase order and invoice information match within your tolerances
as follows:
Invoice price <= Purchase order price
Quantity billed <= Quantity Ordered
3-way matching
This verifies that the receipt and invoice information match with the quantity tolerances defined:
Quantity billed <= Quantity received
4-way matching
This verifies that acceptance documents and invoice information match within the quantity
tolerances defined:
Quantity billed <= Quantity received
Quantity billed <= Quantity accepted
How to relate between PO and invoice tables:
Here are the entity relationship diagram, explaining 2 way and 3 way matching condition.
In summary
PO, Receiving and XLA Queries

=>Provide PO Number to the following query.
SELECT PO_HEADER_ID
FROM PO_HEADERS_ALL
WHERE SEGMENT1 ='&PO_NUMBER';
Take the PO_HEADER_ID from the above output and provide it the following queries
Data from PO Tables:
1.
SELECT *
FROM PO_HEADERS_ALL
WHERE PO_HEADER_ID = &PO_HEADER_ID;
2.
SELECT *
FROM PO_LINES_ALL
3.
SELECT *
FROM PO_LINE_LOCATIONS_ALL
4.
SELECT *
FROM PO_DISTRIBUTIONS_ALL
5.
SELECT *
FROM PO_RELEASES_ALL
Data from Receiving Tables & Inventory Tables:

6.
SELECT *
FROM RCV_SHIPMENT_HEADERS
WHERE SHIPMENT_HEADER_ID IN
(SELECT SHIPMENT_HEADER_ID
WHERE PO_HEADER_ID = &PO_HEADER_ID);
7.
SELECT *
8.
SELECT *
FROM RCV_TRANSACTIONS
9.
SELECT *
FROM RCV_ACCOUNTING_EVENTS
10.
SELECT *
FROM RCV_RECEIVING_SUB_LEDGER
WHERE REFERENCE3 IN
(SELECT TO_CHAR(PO_DISTRIBUTION_ID)
11.
SELECT *
FROM RCV_SUB_LEDGER_DETAILS
WHERE RCV_TRANSACTION_ID IN
(SELECT TRANSACTION_ID
FROM RCV_TRANSACTIONS
12.
SELECT *
FROM AP_INVOICE_DISTRIBUTIONS_ALL
13.
SELECT *
FROM AP_INVOICES_ALL
WHERE INVOICE_ID IN
(SELECT INVOICE_ID
FROM AP_INVOICE_DISTRIBUTIONS_ALL
( SELECT PO_DISTRIBUTION_ID
WHERE PO_HEADER_ID = &PO_HEADER_ID));
XLA Queries
14.
SELECT *
FROM XLA_DISTRIBUTION_LINKS XDL
WHERE XDL.SOURCE_DISTRIBUTION_ID_NUM_1 IN
(SELECT TO_CHAR(RRSL.RCV_SUB_LEDGER_ID)
FROM RCV_RECEIVING_SUB_LEDGER RRSL
WHERE RRSL.REFERENCE3 IN
(SELECT TO_CHAR(PO_DISTRIBUTION_ID)
WHERE PO_HEADER_ID = &PO_HEADER_ID)
)
AND SOURCE_DISTRIBUTION_TYPE = 'RCV_RECEIVING_SUB_LEDGER'
AND APPLICATION_ID
= 707;
15.
SELECT *
FROM XLA_DISTRIBUTION_LINKS XDL
WHERE XDL.SOURCE_DISTRIBUTION_ID_NUM_1 IN
( SELECT aida.invoice_distribution_id
FROM AP_INVOICE_DISTRIBUTIONS_ALL aida
WHERE aida.PO_DISTRIBUTION_ID IN
(SELECT pod.PO_DISTRIBUTION_ID
FROM PO_DISTRIBUTIONS_ALL pod
WHERE pod.PO_HEADER_ID = &PO_HEADER_ID)
)
AND APPLICATION_ID = 200;
=> Get AE_HEADER_ID from above query and prvide as input to following queries
16.
SELECT XAH.GL_TRANSFER_STATUS_CODE, XAH.*
FROM XLA_AE_HEADERS XAH
WHERE XAH.APPLICATION_ID =200

AND AE_HEADER_ID
= &AE_HEADER_ID ;
17.
SELECT *
FROM XLA_AE_LINES XAL
WHERE XAL.APPLICATION_ID = 200
AND AE_HEADER_ID
= &AE_HEADER_ID;
Posted by Elangovan Ragavan at 20:33 No comments:
Labels: P2P Cycle
Thursday, 14 June 2012
P2P Queries
REQUISITION
select prh.segment1 Req_num,
pdt.document_type_code,prh.TYPE_LOOKUP_CODE Type, prh.AUTHORIZATION_STATUS
status,ppf.FULL_NAME Preparer,
PRL.LINE_NUM ,msi.SEGMENT1 item_num,PLT.LINE_TYPE,msi.DESCRIPTION
Item_des,ppf.FULL_NAME Requester
from po_requisition_headers prh,
per_people_f ppf,
po_requisition_lines prl,
PO_LINE_TYPES PLT,
po_document_types pdt,
Mtl_system_items msi
where prh.REQUISITION_HEADER_ID=prl.REQUISITION_HEADER_ID
and prh.preparer_id = ppf.person_id
and plt.line_type_id = prl.line_type_id
AND msi.inventory_item_id= prl.item_id
-- and msi.ORGANIZATION_ID=prl.ORG_ID
AND pdt.document_subtype = prh.type_lookup_code
AND pdt.document_type_code = 'REQUISITION'
AND pdt.org_id=prh.org_id
AND prh.segment1='5633'
PURCHASE ORDER QUERY
select pv.VENDOR_NAME,pv.VENDOR_ID,pv.SEGMENT1 vend_num,pp.FULL_NAME
buyer_name, pp.LAST_NAME,pdt.type_name po_type,ph.STATUS_LOOKUP_CODE STATUS
,msi.SEGMENT1 item_num,msi.DESCRIPTION Item_des,pl.QUANTITY,pl.UNIT_PRICE

FROM po_vendors pv,
po_headers ph,
po_lines pl,
po_document_types pdt,
per_people_f pp,
mtl_system_items msi
where ph.po_header_id=pl.PO_HEADER_ID
AND pv.VENDOR_ID=ph.VENDOR_ID
and msi.ORGANIZATION_ID=ph.ORG_ID
AND (( pdt.document_type_code IN ('PO', 'PA')
AND pdt.document_subtype = ph.type_lookup_code
))
AND msi.inventory_item_id = pl.item_id
AND ph.agent_id = pp.person_id
AND ph.SEGMENT1=4419
P2P Cycle
select prh.segment1 reqno,ph.SEGMENT1 po_num ,prh.TYPE_LOOKUP_CODE
po_Type,prh.TYPE_LOOKUP_CODE req_type ,prl.LINE_NUM,ph.ORG_ID
,pd.PO_DISTRIBUTION_ID,ai.INVOICE_TYPE_LOOKUP_CODE
,ai.INVOICE_AMOUNT,ai.AMOUNT_PAID,ai.INVOICE_DATE
from po_requisition_headers_all prh,
po_headers ph
,po_lines pl
,ap_invoices_all ai
,po_distributions_all pd
,RCV_SHIPMENT_HEADERS RSH
,RCV_SHIPMENT_LINES RSL
,ap_invoice_distributions_all aid
and prd.REQUISITION_LINE_ID=prl.REQUISITION_LINE_ID
and pd.REQ_DISTRIBUTION_ID =prd.DISTRIBUTION_ID
and RSH.SHIPMENT_HEADER_ID=RSL.SHIPMENT_HEADER_ID
and ph.PO_HEADER_ID=rsl.PO_HEADER_ID
and pl.PO_LINE_ID=pd.PO_LINE_ID
and pl.PO_HEADER_ID=ph.PO_HEADER_ID
and aid.INVOICE_ID=ai.INVOICE_ID
and pd.PO_DISTRIBUTION_ID=aid.PO_DISTRIBUTION_ID
and prh.segment1='5659'
REQUSITION & PO QUERY FOR IDS

select prh.SEGMENT1 reqno,ph.SEGMENT1 ponum,
prh.REQUISITION_HEADER_ID,ppf.FULL_NAME preparer,ppf.FULL_NAME requester,
podt.DOCUMENT_TYPE_CODE,plt.LINE_TYPE,ms.SEGMENT1
Item,mo.ORGANIZATION_NAME,
pv.VENDOR_NAME supplier,hl.LOCATION_CODE "ship to location",mo.CITY "bill to
location",ppf.FULL_NAME buyer
from
po_requisition_headers_all prh
,po_requisition_lines_all prl
,po_document_types podt
,po_headers ph
,po_lines pl
,po_vendors pv
,po_line_types plt
,po_req_distributions_all prd
,per_people_f ppf
,mtl_system_items ms
,mtl_organizations mo
,hr_locations_all_tl hl
and ph.PO_HEADER_ID=pl.PO_HEADER_ID
and ph.VENDOR_ID=pv.VENDOR_ID
and prl.REQUISITION_LINE_ID =prd.REQUISITION_LINE_ID
and prd.DISTRIBUTION_ID=pd.REQ_DISTRIBUTION_ID
and pl.PO_LINE_ID=pd.PO_LINE_ID
and prh.TYPE_LOOKUP_CODE=podt.DOCUMENT_SUBTYPE
and prl.LINE_TYPE_ID=plt.LINE_TYPE_ID
and prh.PREPARER_ID=ppf.PERSON_ID
and prl.ITEM_ID=ms.INVENTORY_ITEM_ID
and prh.ORG_ID=mo.ORGANIZATION_ID
and prh.ORG_ID=ms.ORGANIZATION_ID
and ph.SHIP_TO_LOCATION_ID=hl.LOCATION_ID
and prh.SEGMENT1='5710'
ABOVE QUERY TO GET THE DETAILS FOR REQUSITION WITHOUT PO
select prh.SEGMENT1 reqno,ph.SEGMENT1 ponum,
prh.REQUISITION_HEADER_ID,ppf.FULL_NAME preparer,ppf.FULL_NAME requester,
podt.DOCUMENT_TYPE_CODE,plt.LINE_TYPE,ms.SEGMENT1
Item,mo.ORGANIZATION_NAME,
pv.VENDOR_NAME supplier,hl.LOCATION_CODE "ship to location",mo.CITY "bill to
location",ppf.FULL_NAME buyer
from
po_requisition_headers_all prh
,po_requisition_lines_all prl
,po_document_types podt
,po_headers ph
,po_lines pl
,po_vendors pv
, po_line_types plt
,po_req_distributions_all prd
,per_people_f ppf
,mtl_system_items ms
,mtl_organizations mo
,hr_locations_all_tl hl
and ph.PO_HEADER_ID(+)=pl.PO_HEADER_ID
and ph.VENDOR_ID=pv.VENDOR_ID(+)
and prl.REQUISITION_LINE_ID =prd.REQUISITION_LINE_ID
and prd.DISTRIBUTION_ID=pd.REQ_DISTRIBUTION_ID(+)
and pl.PO_LINE_ID(+)=pd.PO_LINE_ID
and prh.TYPE_LOOKUP_CODE=podt.DOCUMENT_SUBTYPE
and prl.LINE_TYPE_ID=plt.LINE_TYPE_ID
and prh.PREPARER_ID=ppf.PERSON_ID
and prl.ITEM_ID=ms.INVENTORY_ITEM_ID
and prh.ORG_ID=mo.ORGANIZATION_ID
and prh.ORG_ID=ms.ORGANIZATION_ID
and ph.SHIP_TO_LOCATION_ID=hl.LOCATION_ID(+)
and prh.SEGMENT1='5711'
Labels: P2P Cycle
Tuesday, 27 March 2012
Base Tables for Procure To Pay Cycle
Requisition
po_requisition_headers_all
po_requisition_lines_all ( segment1 ========== requisition number)

po_req_distributions_all
Note: requisition_header_id is the link between po_requisition_headers_all and
po_requisition_lines_all
requisition_line_id is the link between po_requisition_lines_all and po_req_distributions_all
Purchase order
po_headers_all
po_lines_all
po_distributions_all
po_line_locations_all
Note: po_header_id is the link between all these tables
Receipt
rcv_shipment_headers
rcv_shipment_lines
rcv_transactions
quality result stored in qa_results table
Note: shipment_header_id is the link between rcv_shipment_headers and rcv_shipment_lines
po_header_id is the link between rcv_shipment_headers and rcv_transaction
Invoices
ap_invoices_all
ap_invoice_distributions_all
Note: invoice_id is the link between ap_invoices_all and ap_invoice_distributions_all
Payments
ap_checks_all
ap_invoice_payments_all
ap_payment_schedules_all
Payment Reconcillation
ap_banks
ap_bank_branches
GL Transfer
gl_periods
gl_period_status
gl_set_of_books
glfv_charts_of_accounts
Labels: P2P Cycle
P2P - SCREEN
Here in this post, I tried to explain the steps involved in Procure to Pay Cycle. This is a
pure functional Stuff and helps you to understand the navigation steps.
I tried to keep as simple as Possible for clear understanding. The screenshots given below
are taken from R12.1.1 apps instance.
Stage 1: Choosing an Item
Let us choose an item to be procured in our example.

Go to Purchasing Responsibility and follow the below navigation to check for the suitable
item.
The item picked for our example should be purchasable item as above. Click on tools and
choose Categories to view the below screen.
Stage 2: Creation of Requisition
Follow the below Navigation to reach Requisition Form.
Create a new Requisition for the item viewed in Stage 1.
Click on Distributions to View the charge Account.
Save and Submit for Approval
Now note down the Requisition number and open the Requisition Summary Form to
view the status of it. For our Example, Requisition number is: 14855
Stage 3 : Checking the Status of Requisition
Query for the Requisition Number and click Find.
Here for our example purpose, I kept the submitted and approved person has same and
hence it shows the status as approved.
To see the approval status, please follow the below navigation.
Stage 4 : Creation of Purchase Order
For creating a Purchase order, let us use the Autocreate Documents Form. Follow
the below Navigation
Query for the Requisition
Click on Automatic as shown in the above figure to create a Purchase Order
Click on Create button to create a Purchase order
View the shipment screen to change the Match Approval Level to 2-Way.
Click the Receiving Controls to make sure that the Routing is made as Direct
Routing
Click Save and submit for Approval.
Note down the PO Number.
Stage 5: Creation of Receipts
Query with the Purchase order created in the above stage.
Check the check box near to the lines that are received and click save.
Click the Header Button to view the Receipt Number.
Stage 6: Checking the On Hand
Go to any Inventory Responsibility and follow the below Navigation
Query for our Receipt and make sure the Organization is the same as we received.
Below screen will show that our inventory has been increased by 5 quantities.
Stage 7: Check the Material Transactions
Follow the below Navigation to reach Material Transactions Form
Query for the item and date as below
Below screen shows the source and transaction Type
Below screen shows you the Serial Numbers of the items received.
Stage 8: Creation of Invoice
Navigate to any Purchasing Responsibility and view Requests

Submit the below requests by providing the Receipt number as Parameter to create an
invoice.
Check the status of the program.
Stage 9: Checking the Invoice
Change to any Payables Responsibility and open the invoices Form.
Query for the Purchase order as below,
Click Actions Button then tick the Validate Check Box and press Ok to validate the
invoice
Below screenshot will give you the status of the invoice
Stage 10: Creation of Accounting and Payment
Once invoice got approved, we can Create Accounting and Create Payments via
Action Button in the Invoice Form as we validated the invoice.
Thus the brief description of P2P cycle came to end.

P2P - CYCLE DOCUMENT
Overview of Procure to Pay Cycle in Oracle Apps
Procure to Pay Lifecycle is one of the important Process in Oracle Applications. Procure to Pay
meansProcuring Raw Materials required to manufacture the final or finished Goods from a
Supplier to Paying the Supplier from whom the material was purchased. But this process is not
just two steps. It involves many steps. Lets see the steps and Oracle Application involved in
performing those steps.
1.Creation Of Purchase Requisition

Requisition is nothing but a formal request to buy something. Requisitions represent the demand
for any goods or services that an organization needs.
Requisitions for goods and services:

Are generated by applications including Inventory, Work in Process (WIP), Material
Requirements Planning (MRP) and Order Management.
May be entered manually through Purchasing windows.
May be entered using iProcurement.
May be imported from external systems.

There are two types of Requisitions
1] Internal Requisition Basically used when there is a Requirement from One Inventory
Organization to the Other Inventory Organization (Inter- Organization Transfer)
2] Purchase Requisition Basically used when there is a Requirement to be fulfilled by
External Sources i.e. Suppliers, Requirement from MRP, Requirement from WIP, Requirement
from Sales Order etc.
With Oracle Purchasing module, you can create, edit, and review requisition information online. Then the Requisitions went for approvals from proper authorities.
2. Creation of Purchase Order
Based on the Purchase Requisition and its approval next we have to create a Purchase order to
buy the item.
Purchasing supports four types of purchase orders:

1] Standard: Create standard purchase orders for one-time purchases of various items. You
create standard purchase orders when you know the details of the goods or services you require,
estimated costs, quantities, delivery schedules, and accounting distributions.
2] Blanket: Create blanket purchase agreements when you know the detail of the goods or
services you plan to buy from a specific supplier in a period, but you do not yet know the detail
of your delivery schedules.
3] Contract: Create contract purchase agreements with your suppliers to agree on specific terms
and conditions without indicating the goods and services that you will be purchasing.
4] Planned: A planned purchase order is a long-term agreement committing to buy items or
services from a single source. You must specify tentative delivery schedules and all details for
goods or services that you want to buy, including charge account, quantities, and estimated cost.
Once purchase orders are created, they may be submitted for approval. The approval process
checks to see if the submitter has sufficient authority to approve the purchase order. Once the
document is approved, it may be sent to your supplier using a variety of methods including:
printed document, EDI, fax, e-mail, iSupplier Portal and XML. Once the purchase order or
release is sent to your supplier, they are authorized to ship goods at the times and to the locations
that have been agreed upon.
3. Receipt of Material
After receiving the PO, the supplier will send the items.
Purchasing lets you control the items you order through receiving, inspection, transfer, and
internal delivery. You can use these features to control the quantity, quality, and internal delivery
of the items you receive.
4. Creation of Payables Invoice
Once youve received goods or service from your supplier, youll also receive an invoice.
Using Payables you can record invoices in a number of different ways.
With Payables you can:

Import/Enter invoices manually, either individually or in batches.
Use Quick Invoices for rapid, high-volume entry of standard invoices and credit memos
that are not complex and do not require extensive online validation.
Automate invoice creation for periodic invoices using the Recurring Invoice
functionality.
Use iExpenses to enter employee expense reports using a web browser.
Import EDI invoices processed with the e-Commerce Gateway.
Import XML invoices.
Match invoices to purchase orders or receipts to ensure you only pay what youre
supposed to be paying for.
5. Payment to Supplier
Once invoices are validated, they can be paid. Payables integrates with Oracle Payments, the EBusiness Suite payment engine, to handle every form of payment, including checks, manual
payments, wire transfers, EDI payments, bank drafts, and electronic funds transfers. Payables
also integrates with Oracle Cash Management to support automatic or manual reconciliation of
your payments with bank statements sent by the bank.
This is how the P2P Cycle occurs in Oracle Apps.
Labels: P2P Cycle
Tuesday, 30 August 2011
Puchasing and Payables Module: Technical Details
PO_VENDORS
This table stores information about your suppliers. Oracle Purchasing uses this information to
determine active suppliers. The primary key is VENDOR_ID.
PO_VENDOR_SITES_ALL
This table stores information about supplier sites. Oracle Purchasing uses this information to
store supplier address information. The primary key is VENDOR_SITE_ID.
PO_VENDOR_CONTACTS
This table stores information about supplier site contacts. The primary key is
VENDOR_CONTACT_ID.
PO_REQUISITION_HEADERS_ALL
PO_REQUISITION_HEADERS_ALL stores information about requisition headers. Each row
contains the requisition number, preparer status, and description. It is one of three tables that
stores requisition information. The primary key is REQUISITION_HEADER_ID.
PO_REQUISITION_LINES_ALL
This table stores information about requisition lines. Each row contains the line number, item
number, item category, item description, need-by date, deliver-to location, item quantities, units,
prices, requestor, notes, and suggested supplier information for the requisition line. This table is
one of three tables that stores requisition information. The primary key is
REQUISITION_LINE_ID.
PO_REQ_DISTRIBUTIONS_ALL
PO_REQ_DISTRIBUTIONS_ALL stores information about the accounting distributions
associated with each requisition line. Each requisition line must have at least one accounting
distribution. Each row includes the Accounting Flex field ID and requisition line quantity. This
table is one of three tables that stores requisition information. The primary key is
DISTRIBUTION_ID.
PO_HEADERS_ALL
PO_HEADERS_ALL contains information for your purchasing documents. Each row contains
buyer information, supplier information, notes, foreign currency information, terms and
conditions information, and the document status. Oracle Purchasing uses this information to
record information related to a complete document. The primary key is PO-HEADER_ID.
PO_LINES_ALL
PO_LINES_ALL stores current information about each purchase order line. You need one row
for each line you attach to a document. Each row includes the line number, item number and
category unit, price, tax information, and quantity ordered for the line. Oracle Purchasing uses
this information to record and update item and price information for purchase orders, quotations,
and RFQs. The primary key is PO_LINE_ID.
PO_LINE_LOCATIONS_ALL
This table contains information about purchase order shipment schedules and blanket agreement
price breaks. You must have one row for each schedule or price break you attach to a document
line. Each row contains the location, quantity, and dates for each shipment schedule. Oracle
Purchasing uses this information to record delivery schedule information for purchase orders and
price break information for blanket purchase orders, quotations, and RFQs. The primary key is
LINE_LOCATION_ID.
PO_DISTRIBUTIONS_ALL
PO_DISTRIBUTIONS_ALL contains accounting information for a purchase order shipment
line. Oracle Purchasing uses this information to record accounting and requisition information
for purchase orders and releases. It is one of five tables that stores purchase orders and releases.
The primary key is PO_DISTRIBUTION_ID.
RCV_SHIPMENT_HEADERS
This table stores common information about the source of your receipts or expected receipts. You
group your receipts by the source type and the source of the receipt. Oracle Purchasing does not
allow you to group receipts from different sources under one receipt header. The primary key is
SHIPMENT_HEADER_ID.
RCV_SHIPMENT_LINES
This table stores information about items that have been shipped or received from a specific
receipt source. This table also stores information about the default destination for in-transit
shipments. The primary key is SHIPMENT_LINE_ID.
RCV_TRANSACTIONS
This table stores historical information about receiving transactions that you have performed.
When you enter a receiving transaction and the receiving transaction processor processes your
transaction, the transaction is recorded in this table.
Once a row has been inserted into this table, it will never be updated. When you correct a
transaction, the net transaction quantity is maintained in RCV_SUPPLY. The original transaction
does not get updated. You can only delete rows from this table using the Purge feature of Oracle
Purchasing. The primary key is TRANSACTION_ID.
PO_RELEASES_ALL
This table contains information about blanket and planned purchase order releases. You need one
row for each release you issue for a blanket or planned purchase order. Each row includes the
buyer, date, release status, and release number. Each release must have at least one purchase
order shipment (PO_LINE_LOCATIONS_ALL). The primary key is PO_RELEASE_ID.
AP_INVOICES_ALL
This table contains records for supplier invoices and has one row for each invoice.
To pass Invoice Validation, the INVOICE_AMOUNT in the AP_INVOICES_ALL table must
equal the sum of the AMOUNT columns in the AP_DISTRIBUTIONS_ALL table. The primary
key is INVOICE_ID.
AP_INVOICE_DISTRIBUTIONS_ALL
This table holds the distribution line information.
There is a row for each invoice distribution. If matching is used, distribution information is
copied from PO_DISTRIBUTIONS_ALL during the matching process.
AP_PAYMENT_SCHEDULES_ALL
This table contains information about scheduled payments for an invoice.
Oracle Payables uses this information to determine when to make payments on an invoice and
how much to pay in an automatic payment batch.
AP_HOLDS_ALL
This table contains a record for each hold placed on an invoice.
An invoice might have multiple records in this table.
An invoice cannot be paid until all holds placed on it have been released.
AP_CHECKS_ALL
This table stores information about payments issued to suppliers.
Each row includes the supplier name, address, and bank account name for auditing purposes, in
case any of them change after you make the payment.
If the payment is electronic, the supplier bank account information is stored in the payment
record.
AP_INVOICE_PAYMENTS_ALL
This table provides the link between a payment (CHECK_ID) and the invoice(s) paid by that
payment.
This table contains records of invoice payments that you make to suppliers. Oracle Payables
updates this table when you confirm an automatic payment batch, enter a manual payment, or
process a Quick Payment. This table contains one row for each payment made for each invoice.
Void payments are also entered into this table as a negative record of the original payment line.
AP_BANK_ACCOUNTS_ALL
This table stores information about your bank accounts and your suppliers and customers bank
accounts. This table contains one row for every bank account, whether it is an internal (supplier)
or external (customer) account.
AP_BANK_BRANCHES
This table stores information about the bank branches and details about the branches.
ORACLE GENERAL LEDGER PROCESS
Contents
Manual Journal Entry

Journal Approval Process
Daily Rates Entry
Calendar Definition Year-wise
Auto Copy JE
Auto Reversal of JE
Posting Process
STAT Journal Entry
Account Inquiry
Budget Inquiry
Account Maintenance
Revaluation JE
Translation JE
Consolidation JE
Period-Close
Manual Journal Entry

Navigation: General Ledger Super User Responsibility>>Journals>>Enter
To enter a journal:
1. Navigate to the Enter Journals window.

2. Enter or query the batch for which you are entering journals. To enter a journal without
entering batch information, choose New Journal and proceed to Step 4.
To enter journals for a new batch, choose New Batch and enter the batch
information.
To add journals to an existing batch, query the batch and choose Review Batch.
Note: The Status region on the Batch window will display the current statuses for Posting, Funds
reservation, and journal Approval.
3. Choose New Journal.
4. Enter a unique Journal name for the entry. If you do not enter a journal name, General Ledger
automatically assigns a name using the following format: Source Journal ID Date.
If you did not enter a batch name before entering journals, General Ledger uses the name of the
first journal in the batch to create a default batch name.
5. Enter the Period for the journal entry. If you entered a period at the batch level, you must use
the same period for each journal entry in the batch. If you did not enter a period at the batch
level, choose any Open or Future Enterable period for your journal entry. Note that you can only
post journals in Open periods.
Additional Information: Balance Type is a display-only field. It displays Actual when you are
entering actual journals and Budget when you are entering budget journals.
6. Accept or change the default Effective Date for the journal entry.
7. Enter a Category to describe the purpose of your journal entry, such as accrual, payments or
receipts. All lines in a journal entry share the same journal category.
General Ledger defaults the journal category if you defined the profile option Journals:Default
Category.
8. If you use automatic tax on journal entries, enter Required in the Tax field to indicate that you
want to enter additional tax information. Otherwise, enter Not Required. This field only appears
if you have automatic tax enabled for your Ledger.
10. Enter an optional Description for the journal entry. General Ledger uses this as the default
description for each journal entry line. You can change the journal entry description as necessary.
11. Enter a Control Total if you want to verify the total debits for the journal lines against the
journal control total.
12. Accept the default Currency (the functional currency for your Ledger), or change the journal
currency to enter a foreign currency or statistical journal.
13. Choose Other Information tab to enter optional reference information about the journal entry.
Enter a Reference description to further identify the journal entry on general ledger and
journal entry reports.
Switch Dr/Cr: General Ledger creates your reversing journal by switching the debit and credit
amounts of the original journal entry. This method is often used when reversing accruals.
Change Sign: General Ledger creates your reversing journal by changing the sign of your
original journal amounts from positive to negative. This reversal method is often used when
reversing journals to correct data entry mistakes.
14. Enter the journal lines.
15. Save your work.
Journal Approval Process
Description: General Ledger's Journal Approval feature is used to ensure that journal entries and
batches are approved by appropriate management personnel before the journals can be posted to
account balances
Pre-requisites:
Before setting the approval limit we need to do the pre-requisite set ups for this functionality.
These setups are as given below
Setting of journal approval in primary ledger

Setting of journal approval in journal sources
Setting of journal authorization limits for the employees
Navigation: Setup > Financials > Accounting setup manager > Accounting setups>Ledger
Options
Setting of journal approval in primary ledger: Click on the Enable Journal Approval checkbox.
Click Finish
Navigation: Setup > Journals > Journal Source

Setting of journal approval in journal sources: Query the respective source (eg: Manual) and
Click on the Require Journal Approval checkbox
Navigation: Setup > Employees > Limits

Setting of journal authorization limits for the employees
Enter Journal in Journal Window:
Refer the status of the Approval in Other Information Tab
Manager/Supervisor can either query the journal name on the General Ledger Responsibility and
Click Approve button
Journal.
on the Journal Entry window to approve the
Alternatively approval can be provided using the Workflow notification.
A popup window will be displayed post approval.
Daily Rates Entry
Description: Enter the rates for the foreign currency on the Daily Rates Window to
automatically calculate the currency conversion rates on the sub ledger level foreign currency
transactions as well as foreign currency journal entries in GL whenever entered.
Navigation: Setup > Currencies > Rates > Daily
Enter the From Currency and To Currency

Enter the Date
Enter the Type as Corporate
Enter the rates
Save the changes.
Calendar Definition Year-wise

Description: For every accounting year you are required to add the From and To Dates on the
Accounting Calendar Window inorder to enter and post transactions on any given period. Note
that this should be completed at the beginning of each year.
Navigation: Setup > Financials > Calendars > Accounting

Steps to enter the Periods:
Enter the name of the month on the Prefix column. Do maintain consistency on the
entering the name i.e. refer previous accounting year definition to find out how the period
names are entered and use the same name for the current year as well. For Example if the
name for the period January is mentioned as JAN you are required to copy the same
format and naming convention when defining the current year period and also for
subsequent years.
Choose the Type as Month from the list of values (LOV).
Enter the Current Year.
Enter the quarter on which the month or period falls. For example - Jan, Feb and Mar
falls on the Quarter 1 so enter the Quarter as 1 for Jan, Feb and Mar period and so on.
Enter From and To dates for each period. Since the Period type is Month you are required
to enter the starting date and ending date of the month. It is important to enter the dates
without any gap on the dates. If there is any gap on the period the calendar validation will
fail and have serious consequences on the accounting and transaction posting which is
irreversible.
The Name of the period will be displayed by the system automatically by combining the
Prefix and Year.
Note: After saving your changes, system will run the calendar validation program to validate any
discrepancies or gap on the calendar periods being entered. It is mandatory to check the
concurrent program and ensure that validation is successful.
Auto Copy JE
Description: You can copy entire journal batches with any status by using the AutoCopy button
which is strategically placed on the Journals Workbench, Journal Batches and Journal forms.
When copying Journals, you are prompted to create a batch name, select a period and/or
the effective date.
Go to Journals>>Enter
Query the journal by providing the search parameters on the search window (eg: Period as
Jun14)
From the results shown click the particular line of journal and click AutoCopy
button.
Enter the Batch Name, Period and Effective Date for the new Journal.
Click OK
Clicking OK will then submit a concurrent request called Autocopy Journals. Once this is
complete, you can modify and update the batch, journal and lines in the normal way.
Go to View>>Requests>>Find to view the status of the Concurrent Program
You can then view and post the journal which was created automatically by the system.
Auto Reversal of JE
Description: If you routinely generate and post large numbers of journal reversals as part of
your
month end closing and opening procedures, you can save time and reduce entry errors by using
Automatic Journal Reversal to automatically generate and post your journal reversals.
Note: Automatic Journal Reversal reverses posted journals of the balance type Actual. You
cannot use this feature to automate budget or encumbrance journal reversals
General Ledger generates and posts reversals for journals that satisfy the following conditions:
The journal balance type is Actual.
The journal category is enabled to be Autoreversed.
The journal is posted but not yet reversed.
The journal reversal period is open or future enterable.
Setup Journal Reversal Criteria Set:
Navigation: Setup>>Journal>>AutoReverse
Enter the Name for Criteria Set

Enter the Description
Choose the Journal Category from the Category Field (eg: Accrual)
Choose the Reversal Period from the dropdown (eg: Next Period)
Choose the Reversal Date (eg: First Day)
Choose the Method as Switch Dr/Cr
Enable the checkboxes AutoReverse and AutoPost Reversal.
Click Save
Attach the created Criteria Set to the Ledger.

Navigation: Setup>Accounting Setup Manager>Accounting Setups
Go to Journal Processing section and choose the journal criteria set from the LOV.
Posting Process
AutoPost Process:
Description: You can automatically post journal batches that meet specific criteria that you
defined
in an AutoPost criteria set. You can define multiple criteria sets that include a range of
Journal effective dates and multiple AutoPost priorities. AutoPost priorities include combinations
of ledger or ledger set, journal source, journal category, balance type, and period
Once you define an AutoPost criteria set, run the AutoPost program to select and post
any journal batches that meet the criteria defined by the criteria set. You can also
schedule the AutoPost program to run at specific times and submission intervals. You
can submit the AutoPost program or schedule AutoPost runs directly from the
AutoPost Criteria Sets window. Alternatively, you can use the Submit Request window.
Navigation: Setup>>Journal>>AutoPost
Enter the Criteria Set Name

Enter the Description
Ensure that Enabled box is checked.
Click Submit All Priorities in Order
If you want you can enter the From and To Date
Enter the Priority, Ledger, Source, Category, Source Type and Period.
Click Save
Submit All Priorities in Order: Select this option to submit the batches for all of your
AutoPost priorities in the same AutoPost run. Note that priorities are processed in
order, based on the Priority number.
Submit Only Priorities with Batches in Order: Select this option to submit batches
only from the specified Number of Priorities in the same AutoPost run. If a priority
results in no selected batches it is not included in the count of the number of priorities
whose batches are processed. For example, if the number of priorities is 2 and your first
priority has no selected batches, AutoPost will process priorities 2 and 3. If you submit
AutoPost again, it will process priorities 4 and 5, and so on for each priority that has
selected batches.
Note: Use this option when you need to balance the load on your
concurrent manager. This may be necessary since a single AutoPost
request that contains multiple priorities can result in numerous
instances of the Posting program running concurrently. The load on the
concurrent manager is increased further if a large number of journal
batches are selected by your AutoPost priorities
To schedule an AutoPost run:
1. Navigate to the AutoPost

Criteria Set window.
2. Query the AutoPost criteria set for which you want to schedule the AutoPost program.
.
3. Choose the Schedule AutoPost button. The Submit Request window displays.
You can schedule any AutoPost criteria set that is not secured using Definition
Access Sets or for which you have been granted Use privilege.
Note: Optionally, you can submit the AutoPost program from the
Submit Request window. Enter the AutoPost criteria set name in
the Parameters window.
.
Posting from Journal Window:
Navigation: Journals>>Enter
Query the particular journal from the Journal window.
Click Post button
A Concurrent program will be run by the system as soon as Post button is clicked.
View>>Requests
Requery the Journal and navigate to the Other Information tab on the Journal window
Status should be changed as Posted.
Posting Journals via Post function:

Navigation: Journal>>Post
Query the Batch by entering the batch name or search the journals by entering the period name.
Click Find button.
From the list of unposted batches choose all the batches or a particular batch by clicking the
checkbox on the left side on the screen.
Click Post button
A concurrent will be submitted by the system.
View>>Requests
STAT Journal Entry

Description: General Ledger provides two ways to enter statistical journals. You can enter
journals with only statistical debit and credit amounts. If your user profile permits, you can also
combine monetary and statistical amounts in the same journal line.
Note: Statistical journal entries do not require balanced debits and credits.
Navigation: Journal>>Enter
1. Enter optional batch information.
2. Enter your journal information, specifying STAT for the journal Currency.
3. Enter your journal lines, using statistical debit and credit amounts. The debits do not need to
equal credits for a statistical journal.
4. Save your work.
Account Inquiry
Description: Using Account Inquiry feature you can
Review specific account balances and compute variances from a secondary balance type.
Review information about specific journal batches and journal entries
Navigation: Inquiry> Account

Enter the following fields for the results:
Choose the Name of Ledger from the LOV (eg: AUS USD Ledger)
Accounting Periods From and To date.
Currency as Entered, Total or Statistical
Primary Balance Type as Actual
Factor as Units
Enter the Accounts on the Accounts Section. You can either enter the whole account code
combination or the natural account segment alone (eg: Liability account)
Click Show Balances button to show the PTD and YTD balances against the account.
After performing an online query, you can drill down to see additional details.
Summary to Detail: after querying a summary account, drill down to the detail balances
that comprise the summary account balance for a ledger. For budgets, drill down from
master budgets to detail budgets.
Detail Balances to Journals: from any detail account balance you can drill down to
the journals that contribute to the balance. If you drill down to summary journals,
you can drill down further to detail journals.
Journals to Subledger Detail: from detail journals you can drill down further to see the
Oracle subledger transactions that comprise the journal. You can also view subledger
transactions as balanced journal entries or in the form of T-accounts.
Budget Inquiry
Description: You can perform online inquiries about your master and detail budgets. General
Ledger
compares summary balances between your master and detail budgets, and checks for
budget variances and violations. In addition, you can drill down from summary balances to detail
account balances, and then to budget journal details
Navigation: Inquiry>>Budget
Navigate to the Budget Inquiry window.

Enter the Ledger and Budget you want to review. You can enter a master budget,
detail budget, or a budget not associated with a master-detail relationship.

However, you must enter a budget which has at least one open budget year.
Enter the Currency of the budget balances you want to review. You only see budget
amounts entered in the specified currency.

Enter the range of accounting periods to include in your inquiry. The accounting
period range must be within an open budget year
Choose the Inquiry Type you want to perform. Your Inquiry Type choices depend on
whether you are performing the inquiry on a master or detail budget
For a detail budget, you can only choose Drilldown this Budget to see detail
budget balances with a drilldown to detail accounts
Select the Factor as Units
Query a Summary Account
Choose the Show Balances button to review summary balances based on your inquiry
criteria.
Account Maintenance
Description: Use Mass Maintenance to move balances by period from one account to another or
merge balances by period from multiple accounts into a single account. The moved/merged
balances
are added to the existing balances in your target accounts. If you change your mind about a
move/merge, you can reverse it and restore your account balances to their previous amounts
During a move/merge operation the financial integrity between General Ledger and its
sub ledgers is maintained, so you can still drill down to your subledger details after the
move/merge is complete.
Note: To drill down, perform an account inquiry from the move/merge target account. From
there, you can drill down to the move/merge source account, then to the subledger detail.
A move operation transfers balances from one or more source accounts to one or more
target accounts. In the Mass Maintenance Workbench window, you use one account specification
each to define the source accounts and the target accounts.
A merge operation transfers balances from multiple source accounts into one or more target
accounts.
In the Mass Maintenance Workbench window, multiple account specifications are used to define
the source accounts while the same account specification is used to define the target accounts.
To Perform the Move/Merge:
Navigate to the Mass Maintenance Workbench

Enter the Request Name
Choose the Ledger
Enter the Source and Target accounts at Line level. (For example if you want to move the
balances from one cost center to another cost center enter the source cost center and the
target cost center along with the balancing segment value).
Click Submit button
Business Rules:
You cannot move/merge across ledgers.
If you submit a move/merge request for a ledger set, a parent request will be automatically
submitted along with multiple child requests, one for each ledger in the ledger set.
You cannot move/merge across balancing segment values. For example, if your balancing
segment is company, you cannot move balances from one company to another.
You cannot move/merge across financial statement categories. For example, you cannot move a
balance sheet account balance to an income statement account. You can move/merge within
categories, except for equity accounts. For example, you can move/merge an asset balance to a
liability account.
You cannot move/merge budget or encumbrance balances.
What Move/Merge Does:
If no errors are encountered, a move/merge will perform the following steps before it finishes
processing:
Validate accounts
Create target accounts that don't already exist
Calculate balances to be moved or merged
Calculate amounts to adjust quarter-to-date, year-to-date, project-to-date, Period-averageto-date, quarter-average-to-date, and year-average-to-date balances
Move/merge the calculated balances
Create move/merge audit journals
Produce the Mass Maintenance Execution Report
Translated Balances:
After a successful move/merge operation, translated balances will be out of date. You must run
General Ledger's Translation program for each balance level reporting currency to update your
translated balances.
Revaluation JE
Description: Revaluation is a process that adjusts account balances denominated in a foreign
currency using a one time, daily, or period-end exchange rate. Revaluation amounts, based on
changes in conversion rates between the date of the journal entry and the revaluation date, are
posted to the
underlying account with the offset posted to an unrealized gain or loss account. All debit
revaluation adjustments are offset against the unrealized gain account and all credit adjustments
are offset against the unrealized loss account. If the same account is specified in the gain and loss
fields, the net of the revaluation adjustments is derived
Navigation: Currency>>Revaluation
Query the existing Revaluation Template (eg: AUS Primary Ledger Revaluation)
Click Revalue Button
General Ledger launches a concurrent process to revalue your account balances. Use the
Revaluation Execution Report to review the status of your revaluation. General Ledger
automatically generates this report when you run Revaluation.
Post the revaluation journal batch if you do not have AutoPost enabled
Alternatively, you can run or schedule the Program - Revalue Balances to run the revaluation for
the period.
View>>Requests>>Submi t a New Request
Run the Program called Program Revalue Balances
Choose the following Parameters
Ledger or Ledger set

Revaluation Template name
Period
Effective dates.
Click Submit
Review the report output generated by the system.
Navigate to the Journal Window and query the batch.

Note: The Journal will be created under Journal Category Revaluation.
Translation JE
You can translate your actual and budget account balances from your functional currency to
another currency..
Run translation after you have completed all journal activity for an accounting period. If you post
additional journal entries or change your translation rates after running translation for a period,
you must retranslate. Additionally, if you change the account type for an account segment value
and want to retranslate your actual account balances, you may need to purge past translations,
change the account type assignment, and then run translation.
Navigation: Setup>>Financials>>Accounting Setup Manager>>Accounting Setups
Navigate to the Ledger options

Enter the Period End Rate Type, Period Average Rate Type
Enter the cumulative translation adjustment account.
When you translate your actual balances into another currency, General Ledger automatically
adjusts the balance of the Cumulative Translation Adjustment account to the net difference
needed to balance your translated chart of accounts. General Ledger does not make adjustments
to this account when you translate budget balance
Run Translation:
Navigation: Currency>>Translation
Enter Target Currency

Enter Balance Type (Actual)
Enter the GL Period
Click Translate Button
Translation program will be submitted by the system.
View>>Requests>>Find
Run the Trial Balance Translation program
Consolidation JE
Consolidation is period-end process of combining financial results of separate subsidiaries with
parent company to form a single, combined statement of financial results. Consolidation System
provides flexibility to help manage consolidation needs regardless of company structure
To consolidate multiple Ledgers that have different functional currencies, accounting calendars,
or charts of accounts, you must first map your subsidiaries' charts of accounts to your parent's
chart of accounts.
A consolidation mapping is a set of instructions for mapping accounts or entire account segments
from a subsidiary Primary Ledger to the parent Primary Ledger. When you subsequently transfer
amounts from a subsidiary to your parent, General Ledger creates an unposted consolidation
journal batch in your parent Primary Ledger based on the subsidiary's mapping information.
Navigation: Consolidation>>Define
Enter the Consolidation Name

Enter Description
Choose the Parent Ledger
Choose the Subsidiary Ledger
Choose the Method as either Balances or Transactions
Choose the Currency
Click Mapping button
Balances: Consolidate actual, average, translated, budget, or statistical balances. This method
does not include journal entry detail
Transactions: Consolidate actual journal entry detail from a subsidiary Primary Ledger. Use this
method only if both books have same functional currency. You cannot use this method for
budgets
Segment rules: map subsidiary account segments to parent account segments. For example, you
can map your subsidiary's Department segment to your parent's Cost Center segment.
Enter the name for Mapping

Enter Description
Choose the Target COA structure
Choose the Source COA structure
Click Segment Rules
Start mapping your COA segments one by one

Copy Value From: Copy all values in your subsidiary segment to the same values in
your parent segment. The segments do not have to use the same value set, but must use
the same segment values.
Assign Single Value: Assign one specific value that will be used for the parent segment.
You must enter the value that the parent chart of accounts will use.
Use Rollup Rules From: Map values from your subsidiary segments to your parent
segments using the rule specified in the Rollup Rules region.
If you chose the Use Rollup Rules From action in the previous step, enter the
mapping rules in the Rollup Rules region.
Additional Information: Once you save your work, you cannot modify your rollup rules, except
to change the parent and subsidiary segment detail values. To change a rollup rule, delete it then
create a new one.
Click Save and back to Consolidation Definition Window
Run Journal Import: Checking this option launches Journal Import after your
subsidiary data has been transferred. This creates an unposted consolidation batch in your
parent Primary Ledger automatically.
If you choose not to run Journal Import, the transfer process populates the
GL_INTERFACE table so that you can run Journal Import later.
Audit Mode: Check this option to keep a record of how accounts from your subsidiary
Primary Ledger map to accounts in your parent Primary Ledger. You can then run the
Consolidation Audit Report, the Disabled Parent Accounts Report, and the Unmapped
Subsidiary Accounts Report to see consolidation audit information. After your subsidiary
data has been transferred and you have requested the audit reports, purge your
consolidation audit data using the Purge Consolidation Audit Data window.
Create Summary Journals: Check this option to summarize all journal lines that affect
the same account code combination into one line in the parent Primary Ledger. Since this
is a summary action, General Ledger creates one journal entry line showing debits and
credits for each account code combination.
AutoPost: Check this option to automatically post your consolidation journals in the
parent Primary Ledger
Click Consolidation Set button to Create a mapping set to transfer consolidation data for
multiple subsidiaries simultaneously
Press Transfer and system will create a unposted journal in parent Primary Ledger
Choose the Period for Subsidiary and Parent Ledgers.
Click Transfer button.
System will submit a concurrent request for the transfer instruction.
View>>Requests>>Find
Check the Journal Import output:
Find Consolidation Journal in Parent Ledger
Period-Close
You need to be sure to complete the following period-end tasks:
Finish entering all regular and adjusting journals for the period in your ledger.
Post all unposted journals in your ledger if not already done in the previous step.
Post all unposted journals in your reporting currencies if not already done in the
previous step.
Run Revaluation in both your ledger and reporting currencies. Post the resulting
revaluation batches in each ledger.
As needed, translate balances in your ledger.
Generate needed reports from both your ledger and reporting currencies.
Close your accounting period in both your ledger and reporting currencies

P2P Technical, Functional and GL Flow

Uploaded by

Copyright:

Available Formats

P2P Technical, Functional and GL Flow

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

P2P Technical, Functional and GL Flow

Uploaded by

Copyright:

Available Formats

P2P Technical Flow(Complete Query)

/* Formatted on 6/23/2014 5:26:24 PM (QP5 v5.115.810.9015) */

--and gir.created_by = 1318

Many changes were happened in supplier details in R12.

Note: Suppliers into TCA Architecture in R12:

HZ_ORGANIZATION_PROFILES: This table captures additional Supplier

IBY_EXTERNAL_PAYEES_ALL: It captures payment related details of the supplier.

POS_SUPPLIER_MAPPINGS: This table holds the mapping between the

PO_VENDORS: PO_VENDORS is a view in R12, which joins AP_SUPPLIERS &

Similarly, PO_VENDOR_SITES and PO_VENDOR_SITES_ALL are also views based

There are 4 types of Purchase Orders:

1. Select an Invoice Match Option

Receipt: Payables must match the invoice to the receipt.

1. Save the work.

PO_DISTRIBUTIONS_ALL (REQ_HEADER_REFERENCE_NUM in Distributions

Create a receipt to receive the items in the Purchase Order.

Query with the Purchase order created in the above stage.

Click the Header Button to view the Receipt Number.

Invoice distributions created at the maximum level of detail similar to 11i.

SubLedger Accounting Accounting

Country : United States

2. Supplier Site Creation (Address Book)

3. Purchase Order Creations

Inventory Responsibility >> Receipts

Posted by Elangovan Ragavan at 11:56 1 comment:

Tuesday, 24 December 2013

/* Formatted on 12/24/2013 6:46:27 PM (QP5 v5.114.809.3010) */

AND apss.vendor_site_id(+) = pha.vendor_site_id

AND gjl.je_header_id = gjh.je_header_id

In which table is Purchase order number stored?

Types of purchasing matching options?

4. How many types of purchase orders are present in Oracle?

How many types of Approval Hierarchies are used in purchasing?

What are the types of Approval Hierarchies used in purchasing?

PO_LINE_TYPES_B: PO Types used in the PO_LINES_ALL

How many ways for matchingThey are mainly 3 ways:

PO, Receiving and XLA Queries

Data from Receiving Tables & Inventory Tables:

WHERE XAH.APPLICATION_ID =200

,msi.SEGMENT1 item_num,msi.DESCRIPTION Item_des,pl.QUANTITY,pl.UNIT_PRICE

REQUSITION & PO QUERY FOR IDS

po_requisition_lines_all ( segment1 ========== requisition number)

Stage 1: Choosing an Item

Let us choose an item to be procured in our example.

Stage 2: Creation of Requisition

Follow the below Navigation to reach Requisition Form.

Create a new Requisition for the item viewed in Stage 1.

Click on Distributions to View the charge Account.

Save and Submit for Approval

Stage 3 : Checking the Status of Requisition

Query for the Requisition Number and click Find.

To see the approval status, please follow the below navigation.

Stage 4 : Creation of Purchase Order

Query for the Requisition

Click on Automatic as shown in the above figure to create a Purchase Order

Click on Create button to create a Purchase order

Click Save and submit for Approval.

Note down the PO Number.