Underneath is to give an overview of
the integration of various modules of an Oracle e-Business Suite from a PO
point of view. It determines dependencies that how the different
modules communicate data between each others.
è Account Payable
- Matching need PO number to match Invoices
- PO Distribution Details Default to Invoice Lines
- Projects and Assets Information default to Invoice Line
Distribution depending on PO Match
- AP Invoice Holds depend on PO Tolerance limits and Paid
When Holds are released and Tolerance level met
è Inventory
- Items Setup in Inventory are Used in a PO
- Item Attributes Assigned define behavior of Items on a
PO
- Categories Defined and assigned to Items are defaulted
to Items Ordered in a PO
è Projects
- Projects setup in Project Accounting can be selected at
the PO Distribution level
- Type of Project Determines the Project default
- Accounting derived based on Defaults for Projects
- Project status affects the use of specific project on a
PO
è Fixed Assets
- Items classified with Asset Category used on a PO
derive the classification of Item on a PO line
- PO Defaults are interfaced to Assets via APModule
- Asset Category & Asset Clearing Account is
interfaced to Assets from PO
- Important to select Appropriate Account on PO, before
the PO Line can interface to Assets via Mass Additions
- Supplier information defaults to Assets from PO
- Employee and Manufacturer information interfaced from
PO to Assets
è General Ledger
- All Account details defined on Items, Projects or Item
Categories determine the account on a PO Shipment’s Distribution
- Employee Default account information determines the
account on a PO Distribution for Expense related PO/Requisition
- Default account selected on a Requisition derives the
account on a PO Distribution
- SLA Definition derives the account upon GL Transfer
è Order Management
- Items defined as Outside Processing (OSP) are defaulted
on an Internal Sales Order, which then converts it into an Internal
Requisition and a PO
- Drop-shipment functionality affects PO Item behavior
è HRMS
The purchasing module uses the HR
employee database for the following purposes:
- Designate employees as buyers.
- To assign documents (purchase orders, requisitions,
etc.) against them when these documents are created.
The module can use either the
supervisory or the position hierarchy for routing approvals
