Professional Documents
Culture Documents
P2P Cycle Complete Technical Flow in Oracle Fusion
P2P Cycle Complete Technical Flow in Oracle Fusion
The Procure to Pay cycle is vital to an organization as in this process the organization buys and
received goods or services from its vendors and makes necessary payments.
The key functionalities for different processes of the Procure-to-Pay cycle are:
In-built intelligence with business transactions--Role based dash boards and work area for buyer,
approver; presenting the statistical report, trend, spend analysis, personalized search capability
Enhanced sourcing capabilities--Supplier analysis, visibility of supplier lead time and popularity
across departments
Supplier self-service-- Single log-on for supplier providing complete visibility to their transactions and
full invoicing capability
Standardized processes -- to facilitate shared services model and centralized procurement function
Smart Receipt capabilities-- Automatic receipt application engine, Over/Under payment rules, scored
recommendations based on customer, transaction or exceptions, centralized approach for receipt
processing, setup rules to match receipt to the specialist for manual intervention and rules to mark the
priority of the receipt based on attributes
Payable dashboard--To collaborate with various participants, visibility of priority items and work
volume, item tagging option for quick retrieval
Invoice Work Area-- Invoice creation from scanned images, exception resolution, Invoice creation in a
format based on real life physical invoice offering easy data entry and audit
Integrated invoice image processing-- Image attached with the invoice throughout invoice life-cycle
Invoice indicators--Out of balance, status and hold, prepayment alert during entry
Personalized view-- Excel like capability to freeze columns, personalized search, full screen view,
export to excel
One of the best characteristics of the Oracle Fusion applications is that these can be fully integrated
with traditional Oracle ERP solutions like PeopleSoft, Oracle EBS. So the existing Oracle customers can
choose to implement module wise and selective Fusion functions too.
With the in-built business intelligence capabilities and business benefits of cloud based applications;
Oracle Fusion financials and procurement definitely equip the finance and purchasing users to play a
bigger role and add value in overall business achievements.
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Click the More Tasks dropdown and select Request Noncatalog Item.
Enter the below requisition details and click on Add to Cart button
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Requisition will create ad it will submit for approval, click on the View PDF button to check the
requisition details
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
SELECT
TO_CHAR (prha.approved_date, 'MM-DD-YYYY HH24:mi:ss') AS
approved_on_date,
prla.quantity_cancelled AS cancelled_line_qty,
TO_CHAR (prla.req_bu_id) AS bu_key,
TO_CHAR (prla.destination_organization_id) AS org_id,
TO_CHAR (prla.po_line_id) AS po_line_id,
NVL (TO_CHAR (prla.deliver_to_cust_id), '0') AS deliver_to_cust_id,
prla.destination_type_code AS destination_type_code,
prla.item_source AS item_source,
NVL (prla.suggested_supplier_item_number, 0) AS
suggested_supplier_item_num,
NVL (prla.suggested_vendor_name, '-') AS suggested_vendor_name,
prla.line_status AS line_status,
(CASE
WHEN prla.matching_basis = 'AMOUNT' THEN prla.amount
ELSE prla.quantity * prla.unit_price
END) AS line_amt,
TO_CHAR (prla.requested_ship_date, 'MM-DD-YYYY HH24:mi:ss') AS
requested_ship_date,
TO_CHAR (prla.last_approval_date, 'MM-DD-YYYY HH24:mi:ss') AS
last_approval_date,
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Click on the tasks and click on the Process Requisitions task from Requisitions
Search with requisition and select the requisition and click on Add to Document Builder button
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
prha.requisition_header_id
||
'~'
||
prla.requisition_line_id
||
'~'
||
pda.distribution_id
AS integration_id
FROM por_requisition_headers_all prha,
por_requisition_lines_all prla,
po_line_locations_all polla,
po_headers_all pha,
po_lines_all pla,
po_distributions_all pdar,
gl_code_combinations glcc,
por_req_distributions_all pda,
per_users fnd,
per_users fnd_c,
poz_suppliers pov
WHERE prla.requisition_header_id = prha.requisition_header_id(+)
AND prla.requisition_line_id(+) = pda.requisition_line_id
AND pla.po_header_id = pha.po_header_id(+)
AND pdar.po_header_id = pha.po_header_id(+)
AND pdar.po_line_id = pla.po_line_id(+)
AND pdar.line_location_id = polla.line_location_id(+)
AND polla.po_line_id(+) = pla.po_line_id
AND polla.po_header_id(+) = pha.po_header_id
AND pda.code_combination_id = glcc.code_combination_id
AND pdar.req_distribution_id(+) = pda.distribution_id
AND TO_CHAR (fnd.user_id(+)) = prla.last_updated_by
AND TO_CHAR (fnd_c.user_id(+)) = prla.created_by
AND pov.vendor_id(+) = prla.vendor_id
ORDER BY pdar.po_distribution_id
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Search with Requisition number or Purchase Order number and select the line and click on Receive
button
SELECT
rcvl.shipment_line_id,
poz.segment1 vendor_num,
DECODE (rcvh.vendor_site_id, NULL, NULL, site.vendor_site_code)
vendor_site,
DECODE (rcvl.po_header_id,NULL, 'Unordered','Ordered') AS receipt_type,
rcvh.receipt_num,
rcvh.creation_date AS receipt_date,
rcvl.ship_to_location_id,
hrl.location_code||'-'|| hrl.description AS ship_to_location,
rcvh.ship_to_org_id,
rcvh.employee_id,
-- ppf.full_name,
rcvh.packing_slip,
rcvh.shipped_date,
rcvh.freight_terms,
rcvl.category_id,
rcvl.quantity_shipped,
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
rcvl.quantity_received,
rcvl.item_description,
poh.segment1 AS po_num,
poh.creation_date AS po_date,
rcvl.po_line_id,
rcvl.po_distribution_id,
rcvl.requisition_line_id,
rcvl.deliver_to_person_id,
rcvh.comments AS header_note,
pol.unit_price,
poh.currency_code,
poll.promised_date,
DECODE (rcvl.routing_header_id, 2, 'Yes','No')
FROM
rcv_shipment_headers rcvh,
rcv_shipment_lines rcvl,
poz_suppliers poz,
poz_supplier_sites_all_m site,
hr_locations_all hrl,
per_all_people_f ppf,
po_headers_all poh,
po_lines_all pol,
po_line_locations_all poll
WHERE rcvh.shipment_header_id = rcvl.shipment_header_id
AND rcvh.vendor_id = poh.vendor_id
AND poh.vendor_id = site.vendor_id
AND rcvh.vendor_site_id = site.vendor_site_id
AND rcvl.ship_to_location_id = hrl.location_id
AND rcvh.employee_id = ppf.person_id(+)
AND rcvl.po_header_id = poh.po_header_id(+)
AND rcvl.po_line_id = pol.po_line_id(+)
AND rcvl.po_line_location_id = poll.line_location_id(+)
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Search with PO number and enter the invoice details and select the Match Invoice Lines and click on
the Go button
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
SELECT
aia.set_of_books_id AS ledger_id,
aia.legal_entity_id AS legal_entity_id,
aia.org_id AS bu_id,
aia.vendor_id AS supplier_id,
aia.vendor_site_id AS supplier_site_id,
TO_NUMBER (TO_CHAR (aia.invoice_date, 'YYYYMMDD')) AS invoice_dt_id,
NVL (aia.accts_pay_code_combination_id, 0) AS glcc_liab_id,
NVL (dist.dist_code_combination_id, 0) AS glcc_expense_id,
aia.payment_method_code,
pm.payment_method_name,
aia.terms_id,
apt.name AS terms_name,
aia.invoice_num,
TO_CHAR (aia.invoice_date, 'MM-DD-YYYY HH24:mi:ss') AS invoice_date,
TO_CHAR (aia.invoice_received_date, 'MM-DD-YYYY HH24:mi:ss') AS
invoice_received_date,
aia.invoice_type_lookup_code,
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
dist.last_updated_by AS dist_last_updated_by,
TO_CHAR (dist.creation_date, 'MM-DD-YYYY HH24:mi:ss') AS
dist_creation_date,
dist.created_by AS dist_created_by,
poh.segment1 AS purch_order_num,
aila.attribute1 AS l_dff_activity_code,
TO_CHAR (aila.attribute_date1, 'MM-DD-YYYY HH24:mi:ss') AS
l_dff_service_start_dt,
TO_CHAR (aila.attribute_date2, 'MM-DD-YYYY HH24:mi:ss') AS
l_dff_service_end_dt,
dist.attribute1 AS dist_dff_activity_code
FROM
ap_invoices_all aia,
iby_payment_methods_tl pm,
ap_terms_tl apt,
ap_invoice_lines_all aila,
ap_batches_all bat,
ap_invoice_distributions_all dist,
ap_lookup_codes alc,
ap_lookup_codes alc1,
ap_lookup_codes alc2,
ap_lookup_codes alc3,
po_distributions_all pda,
po_headers_all poh
WHERE 1=1
AND aia.payment_method_code = pm.payment_method_code(+)
AND NVL (pm.language, 'US') = 'US'
AND aia.terms_id = apt.term_id(+)
AND NVL (apt.language, 'US') = 'US'
AND aia.invoice_id = aila.invoice_id
AND aia.batch_id = bat.batch_id(+)
AND aila.invoice_id = dist.invoice_id(+)
AND aila.line_number = dist.invoice_line_number(+)
AND alc.lookup_type = 'INVOICE TYPE'
AND alc.lookup_code = aia.invoice_type_lookup_code
AND alc1.lookup_type(+) = 'POSTING STATUS'
AND alc1.lookup_code(+) = dist.posted_flag
AND alc2.lookup_type(+) = 'INVOICE DISTRIBUTION TYPE'
AND alc2.lookup_code(+) = dist.line_type_lookup_code
AND alc3.lookup_type(+) = 'INVOICE LINE TYPE'
AND alc3.lookup_code(+) = aila.line_type_lookup_code
AND dist.po_distribution_id = pda.po_distribution_id(+)
AND pda.po_header_id = poh.po_header_id(+)
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Click on the Submit Payment Process Request link from Payments task
Enter the PPR name and select the Payment Method, Supplier, Bank, Payment process profile and
Approver and click on the Submit button
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Once the payment is created it will ask for the approval, click on the Go Actions button to Initiate the
approval
Back to Payments page, Status will changed to approved, Click on the Go actions button
It will complete the process and submit the programs, Click on the View Output on Format Payment
Files job
SELECT
bu.primary_ledger_id AS ledger_id,
ipa.org_id AS bu_id,
ipa.legal_entity_id AS legal_entity_id,
checks.vendor_id AS supplier_id,
checks.vendor_site_id AS supplier_site_id,
COALESCE (TO_NUMBER (TO_CHAR (ipa.payment_date, 'YYYYMMDD')), 0) AS
payment_dt_id,
TO_CHAR (checks.check_date, 'MM-DD-YYYY HH24:mi:ss') AS check_date,
COALESCE (aia.accts_pay_code_combination_id, 0) AS glcc_id,
TO_CHAR (aipa.accounting_date, 'MM-DD-YYYY HH24:mi:ss') AS
accounting_date,
aipa.invoice_id AS invoice_id,
aia.invoice_num AS invoice_num,
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
ipa.int_bank_account_number AS int_bank_account_number,
ipa.bill_payable_flag AS bill_payable_flag,
ipa.payment_reference_number AS payment_reference_number,
checks.check_id AS check_id,
TO_CHAR (aipa.creation_date, 'MM-DD-YYYY HH24:mi:ss') AS
aipa_creation_date,
aipa.created_by AS aipa_created_by,
TO_CHAR (aipa.last_update_date, 'MM-DD-YYYY HH24:mi:ss') AS
aipa_last_update_date,
aipa.last_updated_by AS aipa_last_updated_by,
TO_CHAR (checks.creation_date, 'MM-DD-YYYY HH24:mi:ss') AS
checks_creation_date,
checks.created_by AS checks_created_by,
TO_CHAR (checks.last_update_date, 'MM-DD-YYYY HH24:mi:ss') AS
checks_last_update_date,
checks.last_updated_by AS checks_last_updated_by,
TO_CHAR (ipa.creation_date, 'MM-DD-YYYY HH24:mi:ss') AS
ipa_creation_date,
ipa.created_by AS ipa_created_by,
TO_CHAR (ipa.last_update_date, 'MM-DD-YYYY HH24:mi:ss') AS
ipa_last_update_date,
ipa.last_updated_by AS ipa_last_updated_by,
COALESCE (aipa.invoice_payment_id, 0)
FROM
ap_checks_all checks,
ap_invoice_payments_all aipa,
fun_all_business_units_v bu,
ap_invoices_all aia,
ap_payment_schedules_all ps,
ap_lookup_codes aplc,
ce_payment_documents cpd,
iby_payments_all ipa,
fnd_lookup_values_tl flvt
WHERE 1=1
AND aipa.check_id = checks.check_id
AND ipa.org_id = bu.bu_id
AND aipa.invoice_id = aia.invoice_id
AND aipa.invoice_id = ps.invoice_id
AND aipa.payment_num = ps.payment_num
AND aplc.lookup_type(+) = 'CHECK STATE'
AND aplc.lookup_code(+) = checks.status_lookup_code
AND checks.payment_document_id = cpd.payment_document_id(+)
AND checks.payment_id = ipa.payment_id(+)
AND ipa.payment_function = flvt.lookup_code(+)
AND flvt.lookup_type(+) = 'IBY_PAYMENT_FUNCTIONS'
AND flvt.source_lang(+) = 'US'
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Search with Purchase order number and click on the View Details button
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88
SELECT
COALESCE (l.ledger_id, 0) "LEDGER_ID",
COALESCE (TO_NUMBER (TO_CHAR (l.effective_date, 'YYYYMMDD')), 0)
"JOURNAL_DT_ID",
COALESCE (TO_NUMBER (TO_CHAR (h.posted_date, 'YYYYMMDD')), 0)
"POSTED_DT_ID",
COALESCE (TO_NUMBER (TO_CHAR (gp.end_date, 'YYYYMM')), 0) "PERIOD_ID",
l.status "JOURNAL_LINE_STATUS",
COALESCE (l.code_combination_id, 0) "GLCC_ID",
b.name "JE_BATCH_NAME",
b.status AS "JE_BATCH_STATUS",
b.description AS "JE_BATCH_DESC",
b.approval_status_code AS "JE_BATCH_APPROVAL_STATUS",
b.je_source AS "JE_BATCH_SOURCE",
b.default_period_name AS "JE_BATCH_PERIOD_NAME",
TO_CHAR (b.posted_date, 'MM-DD-YYYY HH24:mi:ss') AS
"JE_BATCH_POSTED_DT",
Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow OracleApps88