Creating Purchase Order and back-table in Oracle Fusion
Notes written in the session
==========================
Topic: Creating Purchase Order
P2P Cycle
Sai Serservice -Maruthi Dealer
30 Yrs
Creating Requisition
Ertiga 101 100 Qty
Alto 101 10 qty
Create PO AutoCreate Requision --Supplier
Create PO --Supplier
A2CF need 100 Laptops
venkat raised request to buy 100 laps with 1 tb HD 2 gb ram
may 10 th 2026 to llcation 101 Blor KR Puram A2CF Office
Request for Quotations from suppliers
HP -- Madhu is supplier
Del -- Dell outlet -- Dell is supplier
Compaq --
IBM
WIPRO
Quotations -Quote Analysis
AutoCreate PO with Madhu
101 Blor KR Puram --Employee receiving role
Ramki - Receive good
Create Receipt --Goods Receiving Receipt
Invoice --
Validate
payment
Create Acccounting
Post to ledger
EGP_ -- Item Master PDH module
INV_ -- Inventory
POR_ PO Module
PO_ PO Module
PON_ PO Module
Rcv_ PO Module
AP_ AP Module
XLA_AE_ Subledger Module
GL_ GL Module
US165299 PO number
PO_Headers_all
PO_Lines_ALL
PO_Line_locations_all --Schedule
po_Distributions_all
============
Detailed Explanation:
Module
Purpose
Table Prefix
Product Development Hub (PDH)
Item Master data
`EGP_`
Inventory (INV)
On-hand quantities and inventory transactions
`INV_`
Purchasing (PO)
Requisitions and Purchase Orders
(Requisitions) / (Orders)
Sourcing (PON)
Negotiations, RFQs, and Quotations
`PON_`
Receiving (RCV)
Goods receiving receipts and shipment lines
`RCV_`
Accounts Payable (AP)
Invoices, lines, and distributions
`AP_`
Subledger Accounting (XLA)
Subledger accounting entries and entities
`XLA_`
General Ledger (GL)
General ledger and posting
`GL_`
EGP_ is the prefix for back-end tables belonging to the Product Development Hub (PDH) module, primarily used for storing Item Master data. These tables can be found in the link:
(This table stores translatable attributes of item)
INVENTORY_ITEM_ID
ORGANIZATION_ID
LANGUAGE
SOURCE_LANG
LAST_UPDATE_DATE
LAST_UPDATED_BY
CREATION_DATE
CREATED_BY
EGP_ITEM_REVISIONS_B
Stores revision levels for an inventory item
12 Inventory Management
INV_ORG_PARAMETERS: Maintains configuration parameters for each inventory organization, including GL accounts, locator control, lot/serial control, and cost method.
PO_HEADERS_ALL (PO): Stores the header information for Purchase Orders, Blanket Purchase Agreements (BPAs), and Contracts (Supplier, Status, Header ID).
PO_LINES_ALL (PO): Stores the line item details for POs (Item, Unit Price, UOM, Line ID).
PO_LINE_LOCATIONS_ALL (PO): Stores shipment schedules, quantity to be shipped, delivery dates, and Price Breaks for BPAs.
PO_DISTRIBUTIONS_ALL (PO): Stores the accounting distribution (Charge Account, Budget info) for each PO shipment.
PO_RELEASES_ALL (PO): Stores releases created against Blanket Purchase Agreements.
PO_ACTION_HISTORY (PO): Tracks the approval workflow history (who approved, when, action taken).
Self_Procurement Service
POR - Purchase Requisition Tables
PO_REQUISITION_HEADERS_ALL (POR/PO): Stores header information for internal purchase requisitions (Requisition Number, Requestor).
PO_REQUISITION_LINES_ALL (POR/PO): Stores line-level information for requisitions (Item details, Quantity, Supplier suggestion).
POR_REQUISITION_LINES_ALL (POR - Fusion specific): In Oracle Fusion, this is a key table storing requisition line information, often referred alongside POR_REQUISITION_HEADERS_ALL.
PO_REQ_DISTRIBUTIONS_ALL (POR/PO): Stores the accounting distribution for requisition lines.
XLA_AE_ Subledger Module
Core Subledger Accounting (XLA) Tables
XLA_EVENTS: Records all accounting events (e.g., invoice validation, payment creation) that require accounting. It is the primary table for event management.
XLA_TRANSACTION_ENTITIES: Stores information about subledger documents or transactions (e.g., which AP invoice or AR transaction is being accounted).
XLA_AE_HEADERS: Stores the subledger journal entry headers, acting as the primary container for a subledger journal entry.
XLA_AE_LINES: Stores the subledger journal entry lines, containing debit and credit amounts, code combinations (CCIDs), and descriptions.
XLA_DISTRIBUTION_LINKS: Connects transaction distribution lines (e.g., from AP_INVOICE_DISTRIBUTIONS) to the corresponding XLA_AE_LINES. This table is crucial for auditing from GL back to the subledger transaction.
XLA_ACCOUNTING_ERRORS: Stores error messages encountered during the "Create Accounting" process.
Setup and Configuration Tables
XLA_SUBLEDGERS: Contains information about subledger applications (e.g., Payables, Receivables) registered in the Accounting Hub.
XLA_ACCTG_METHODS_B: Stores Subledger Accounting Methods (SLAM).
XLA_SOURCES_B: Stores the sources used for creating accounting rules and conditions.
Typical Join Query Strategy
To create reports, these tables are often joined in this order:
Transaction Table (e.g., AP_INVOICES_ALL)
XLA_TRANSACTION_ENTITIES (Links transaction to SLA)
XLA_EVENTS (Links entity to events)
XLA_AE_HEADERS (Links event to journal)
XLA_AE_LINES (Links header to lines)
XLA_DISTRIBUTION_LINKS (Links lines to transaction distributions)
GL Module
Core Transaction & Balance Tables
GL_BALANCES: The most critical table for reporting, storing actual, budget, and encumbrance balances for each account, currency, and period.
GL_JE_HEADERS: Stores header-level information for journal entries (e.g., journal name, source, category, ledger, status).
GL_JE_LINES: Contains the detailed debit and credit lines for journal entries, connected to the header via JE_HEADER_ID.
GL_JE_BATCHES: Stores information about journal entry batches.
Oracle Help Center
Oracle Help Center
Setup & Configuration Tables
GL_CODE_COMBINATIONS: Stores valid account combinations (Accounting Flexfield segments) used in journals and balances.
GL_LEDGERS: Contains the ledger definitions, including ledger currency, calendar, and chart of accounts.
GL_PERIOD_STATUSES: Stores the open/closed status of accounting periods.
Interface & Reference Tables
GL_INTERFACE: The primary staging table used to import journal entries from external systems or subledgers into the GL.
GL_DAILY_RATES: Stores currency conversion rates used for foreign currency transactions.
GL_IMPORT_REFERENCES: Links journals to their source transactions (subledger entries), often used for drill-down.
Key Relationships
GL_JE_LINES links to GL_JE_HEADERS via JE_HEADER_ID.
GL_JE_LINES links to GL_CODE_COMBINATIONS via CODE_COMBINATION_ID.
GL_BALANCES links to GL_CODE_COMBINATIONS and GL_LEDGERS.
===================================
Core concepts of the Procure-to-Pay (P2P) cycle as demonstrated in the video, ranging from initial business processes to technical back-end structures.1. Procurement Business Processes
Purchase Requisitions: Understand how a requisition is the starting point for internal requests, which can include multiple items and quantities for specific locations.1
Purchase Orders (PO): Learn the two primary ways to create a PO:
From an Approved Requisition: Converting an existing, internally approved request into a PO.2
Direct Creation: Creating a PO directly against a supplier without a prior requisition when business terms are already established.3
The Request for Quotation (RFQ) Cycle: Study how businesses handle negotiations by getting quotes from multiple suppliers, performing quote analysis, and then auto-creating a PO for the best quote.4
2. The P2P Lifecycle Steps
Study the hierarchical flow of the Procure-to-Pay cycle:5
Approval: Internal supervisor or departmental approval of requisitions and POs
Goods Receiving: The role of the storekeeper in logging into the application to create a "goods receiving receipt" upon delivery.7
Invoicing and Payment: The progression from creating an invoice to validation, payment, and finally posting to the general ledger.8
3. Oracle Fusion Technical Architecture
For those in technofunctional roles, focus on the naming conventions and structure of the back-end database objects:9
Module Prefixes:
PO Module: Requisitions (PR_), Purchase Orders (PO_), and Negotiations (PON_).10
Receiving: Receiving transactions (RCV_).11
Inventory & Items: Item master (EGP_) and Inventory (INV_).12
Financials: Invoices (AP_), Subledger Accounting (XLA_), and General Ledger (GL_).13
PO Table Hierarchy: Understand the primary-foreign key relationships between these four levels:14
PO_HEADERS_ALL: General information (PO number, BU, Supplier).15
PO_LINES_ALL: Specific item and quantity details.16
PO_LINE_LOCATIONS_ALL (Schedules): Delivery dates and quantities.17
PO_DISTRIBUTIONS_ALL: Accounting and distribution data for each schedule.18
4. Hands-on Application Navigation
Procurement Dashboard: Navigating to "Purchase Requisitions" and "Purchase Orders".19
Document Builder: Using the "Add to Document Builder" feature to consolidate requisition lines into a new PO.20
Order Management: Managing existing orders and querying them for modifications or approval.
No comments:
Post a Comment