The document describes two key business cycles - procure to pay (P2P) and order to cash (O2C). The P2P cycle involves requisition, purchase order, goods receipt, invoice creation, payment, and general ledger transfer. The O2C cycle involves order creation, order booking, pick/ship confirmation, invoice generation via a workflow process, and receipt entry against invoices. For each major step, the document lists the backend database tables impacted, such as PO_HEADERS_ALL, RCV_SHIPMENT_HEADERS, AP_INVOICES_ALL, and OE_ORDER_HEADERS_ALL. It also provides example SQL queries to retrieve records from these tables.

1. CYCLES
2 Types Of Cycles
1 p2p [procure to pay]- POINVAPGL
2 o2c[order to cash]- OMINVARGL
P2P CYCLE:
Inventor
Requisition
RFQ
Quotation  supplier
Quotation analysis
Purchase ordersupplier
invoicegoodssupplier
validate
Payment
invoice created by payables
transfer to gl
unposted journal will be created
Posted

2. O2C CYCLE
Ordering
Scheduling
Shipping
Auto invoice to AR
Invoicing
Receipts and collections
Cash management
Transfer to GL

3. P2P CYCLE
1.0 Creation of Requisitions

5. SELECT * FROM PO_REQUISITION_HEADERS_ALL WHERE SEGMENT1=5671
SELECT * FROM PO_REQUISITION_LINES_ALL
WHERE REQUISITION_HEADER_ID = (SELECT REQUISITION_HEADER_ID FROM
PO_REQUISITION_HEADERS_ALL WHERE SEGMENT1='5671')
 After saving the REQUISITION initially Status at the header
level is incomplete and press APPROVE tab for the approval.
 This is sent for the approval and if it has been approved then
the STATUS is converted APPROVED.

7. 2.0 Creating Purchase Order against the Requisition:
 Either you can create manually or using auto create a PURCHASE ORDER.
 In this opting to choose Autocreate.

8. >Click the Auto create option

9.  Click Automatic

10.  Click Create to automatically create the purchase order
 If you want to define shipment schedules then define by pressing
Shipments tab

11.  save the record and submit for APPROVAL. Now the STATUS
becomes approved after approving by corresponding Approver.

12. At back end they are stored in:
> All Header level information is stored in
SELECT * FROM PO_HEADERS_ALL WHERE SEGMENT1=4500
 All line level information is stored in:
SELECT * FROM PO_LINES_ALL
WHERE PO_HEADER_ID= (SELECT PO_HEADER_ID FROM
PO_HEADERS_ALL WHERE SEGMENT1=4500)
 All shipment schedules details are stored:
SELECT * FROM PO_LINE_LOCATIONS_ALL
WHERE PO_HEADER_ID=(SELECT PO_HEADER_ID FROM
PO_HEADERS_ALL WHERE SEGMENT1=4500)
> All the Distribution information stored in
SELECT * FROM PO_DISTRIBUTIONS_ALL
WHERE PO_HEADER_ID=(SELECT PO_HEADER_ID FROM PO_HEADERS_ALL WHERE
SEGMENT1=4500).
3.0 Receiving against the Purchase Order

13.  Change the receiving Organization before you create a receipt
to which org you supposed to ship the goods.
 If it is a ordered Receipt then enter the Purchase Order Number
against which you have to receive

14. >Click Find
 Receive the goods against that Purchase Order
At back end they are stored in

15. SELECT * FROM RCV_SHIPMENT_HEADERS
WHERE RECEIPT_NUM =9621
SELECT * FROM RCV_SHIPMENT_LINES
WHERE SHIPMENT_HEADER_ID IN (SELECT SHIPMENT_HEADER_ID
FROM RCV_SHIPMENT_HEADERS
WHERE RECEIPT_NUM =9621 AND
SHIPMENT_HEADER_ID=69428)
> The more Tables that are affected are
Select * from RCV_TRANSACTIONS
Where PO_HEADER_ID IN (SELECT PO_HEADER_ID
FROM PO_HEADERS_ALL
WHERE SEGMENT1=4500)
SELECT *
FROM mtl_material_transactions
WHERE RCV_TRANSACTION_ID IN (select TRANSACTION_ID
From RCV_TRANSACTIONS
Where PO_HEADER_ID IN (SELECT PO_HEADER_ID
FROM
PO_HEADERS_ALL WHERE
SEGMENT1=4500))

16. 4.0 Creation of Invoice
 Switch responsibility to Payables
Manager( AP module)

17.  Match it with either a purchase Order or Receipt.
Initially Invoice status will be Not Validated
Approval Status will be Required Approval
 Then go for Actions Tab
Actions -> Validate check and press Ok.
 See for Holds if any and Release the holds
Actions -> Release Holds
> Then check the ‘Force Approval’ Press OK.
> Then check ‘Create Accounting’ Press Ok.
> For Payment
>Press actions

19. At back end they are stored in:
The tables that are going to be impacted are
1. AP_INVOICES_ALL
2. AP_INVOICE_DISTRIBUTIONS_ALL
SELECT *
FROM AP_INVOICES_ALL
WHERE INVOICE_NUM=4579
SELECT *
FROM AP_INVOICE_DISTRIBUTIONS_ALL
WHERE INVOICE_ID IN (SELECT INVOICE_ID
FROM AP_INVOICES_ALL
WHERE INVOICE_NUM='4579')

20. Payments are made in & it depends on the payment terms
At back end they are stored in:

21. Tables affected are:
SELECT *
FROM AP_PAYMENT_SCHEDULES_ALL
WHERE INVOICE_ID IN (SELECT INVOICE_ID FROM
AP_INVOICES_ALL
WHERE INVOICE_NUM='4579')
SELECT *
FROM AP_INVOICE_PAYMENTS_ALL
WHERE INVOICE_ID IN (SELECT INVOICE_ID FROM AP_INVOICES_ALL --63568
WHERE INVOICE_NUM='4579')
SELECT *
FROM AP_PAYMENT_DISTRIBUTIONS_ALL
WHERE INVOICE_PAYMENT_ID IN (SELECT INVOICE_PAYMENT_ID
FROM AP_INVOICE_PAYMENTS_ALL
WHERE INVOICE_ID IN (SELECT INVOICE_ID FROM AP_INVOICES_ALL --63568
WHERE INVOICE_NUM='4579'))
SELECT *
FROM AP_CHECKS_ALL
WHERE CHECK_ID=28698  Corresponding vendor_id and
bank_account is related to that particular vendor

22. 6.0 Reconciling Bank Accounts in Cash Management Module

24. At back end they are stored in:
SELECT STATEMENT_HEADER_ID FROM CE_STATEMENT_HEADERS_ALL
WHERE STATEMENT_HEADER_ID =75826
SELECT * FROM CE_STATEMENT_LINES
WHERE STATEMENT_HEADER_ID IN (SELECT STATEMENT_HEADER_ID
FROM CE_STATEMENT_HEADERS_ALL
WHERE STATEMENT_HEADER_ID =75826)
 After these Invoice’s are transferred to GL by
running
Payables Transfer to General Ledger PROGRAM
The tables affected are
GL_JE_BATCHES
GL_JE_HEADERS
GL_JE_LINES

25. Order to cash management
1.0 Creating an Order...............................................................................................26
3.0 Pick Release a Sales Order.................................................................................32
4.0 Pick Confirm a Sales Order................................................................................41
5.0 Ship Confirm a Sales Order................................................................................46
6.0 Running Workflow Background Process...........................................................54
7.0 Entering Receipts against Invoice......................................................................56

26. 1.0 Creating an Order

29. At back end they are stored in:
Major Tables Impacted:
oe_order_headers_all
oe_order_lines_all
Queries:
SELECT * FROM oe_order_headers_all WHERE order_number = 57803
SELECT * FROM oe_order_lines_all WHERE header_id = (SELECT header_id FROM
oe_order_headers_all WHERE order_number = 57803)

30. 2.0 Booking an Order
At back end they are stored in:
Major Tables Impacted:

31. wsh_delivery_details
Queries:
SELECT * FROM wsh_delivery_details WHERE source_header_id = (SELECT header_id FROM
oe_order_headers_all WHERE order_number = 57803)

32. 3.0 Pick Release a Sales Order

37. At back end they are stored in:
Major Tables Impacted:
wsh_delivery_assignments
wsh_new_deliveries
(more tables continued for Pick Release in the following pages)
Queries:
SELECT delivery_id FROM wsh_delivery_assignments WHERE delivery_detail_id =
(SELECT delivery_detail_id FROM wsh_delivery_details WHERE source_header_id = (SELECT
header_id FROM oe_order_headers_all WHERE order_number = 57803))
SELECT * FROM wsh_new_deliveries WHERE delivery_id = 211904
(more queries continued for Pick Release in the following pages)

40. At back end they are stored in:
Tables Impacted:
mtl_txn_request_headers
mtl_txn_request_lines
Queries:
SELECT header_id FROM mtl_txn_request_headers WHERE request_number = '187252'
SELECT * FROM mtl_txn_request_lines WHERE header_id = 209289

41. 4.0 Pick Confirm a Sales Order

44. At back end they are stored in:
Tables Impacted:
mtl_material_transactions_temp
mtl_material_transactions
Queries:
SELECT * FROM mtl_material_transactions WHERE transaction_id IN (11262482, 11262483)

46. 5.0 Ship Confirm a Sales Order

49. At back end they are stored in:
Major Tables Impacted:
wsh_delivery_legs
(more tables to be continued for Ship Confirm)
Queries:
SELECT * FROM wsh_delivery_legs WHERE delivery_id = 211904
(more queries to be continued for Ship Confirm)

51. At back end they are stored in:
Major Tables Impacted:
wsh_trip_stops
(more tables to be continued for Ship Confirm)
Queries:
SELECT * FROM wsh_trip_stops WHERE stop_id IN (216963, 216964)
(more queries to be continued for Ship Confirm)

53. At back end they are stored in:
Major Tables Impacted:
wsh_trips
(more tables to be continued for Ship Confirm)
Queries:
SELECT * FROM wsh_trips WHERE trip_id = 179789
(more queries to be continued for Ship Confirm)
Inventory Interface- SRS updates inventory with the ship confirmation information. Inventory balances
are decremented and reservations relieved. This program always spawns the Order Management
Interface - SRS program. It is very important in the process flow that the Inventory Interface complete
before the Order Management Interface to ensure the integrity of the reservation information.
Inventory Interface picks records from MTI (MTL_TRANSACTIONS_INTERFACE) and inserts them
into MMTT (MTL_MATERIAL_TRANSACTIONS_TEMP). The Inventory Manager then processes
rows and inserts them in to MTL_MATERIAL_TRANSACTIONS.
Order Management Interface runs to update Order Management with the ship confirmation
information. Order line shipped quantities will be updated.
At the end of ship confirm, invoice lines are created in Ra_interface_lines_all table.
Tables Impacted:
Ra_interface_lines_all
Queries:
SELECT * FROM ra_interface_lines_all where interface_line_attribute1 = <order_number>

54. 6.0 Running Workflow Background Process

55. At back end they are stored in:
Tables Impacted:
Ra_customer_trx_lines_all
Ra_customer_trx_all
Queries:
SELECT * FROM Ra_customer_trx_lines_all where interface_line_attribute1 = <order_number>
SELECT * FROM Ra_customer_trx_all where trx_header_id = <trx_header_id> (trx_header_id
fetched from Ra_customer_trx_lines_all)

56. 7.0 Entering Receipts against Invoice

59. MAJOR TABLES IMPACTED:
ar_cash_receipts_all
ar_receivable_applications

60. MAJOR TABLES IMPACTED:
ar_cash_receipts_all
ar_receivable_applications