Skip to main content


Showing posts from June, 2015

List of AME Tables

select * from AME_ACTIONS select * from AME_ACTIONS_TL select * from AME_ACTION_TYPES select * from AME_ACTION_TYPES_TL select * from AME_ACTION_TYPE_CONFIG select * from AME_ACTION_TYPE_USAGES select * from AME_ACTION_USAGES select * from AME_APPROVALS_HISTORY select * from AME_APPROVAL_GROUPS select * from AME_APPROVAL_GROUPS_TL select * from AME_APPROVAL_GROUP_CONFIG select * from AME_APPROVAL_GROUP_ITEMS select * from AME_APPROVAL_GROUP_MEMBERS select * from AME_APPROVER_TYPES select * from AME_APPROVER_TYPE_USAGES select * from AME_ATTRIBUTES select * from AME_ATTRIBUTES_TL select * from AME_ATTRIBUTE_USAGES select * from AME_CALLING_APPS select * from AME_CALLING_APPS_TL select * from AME_CONDITIONS select * from AME_CONDITION_USAGES select * from AME_CONFIG_VARS select * from AME_CONFIG_VARS_TL select * from AME_EXCEPTIONS_LOG select * from AME_FIELD_HELP select * from AME_HELP select * from AME_ITEM_CLASSES select * from AME_ITEM_CLASSES_TL select * from AME_ITEM_CLASS_USAGES

Query to find the Approval Limits for Requisitions and PO Document Types

Query to find Approval Limits for Requisition SELECT   pj . NAME   job_name ,         g . control_group_name ,         h . object_code ,         h . amount_limit FROM     per_jobs   pj ,         po_position_controls_all   f ,         po_control_groups_all   g ,         po_control_rules   h WHERE    pj . job_id   =   f . job_id         AND   f . control_group_id   =   g . control_group_id         AND   g . control_group_id   =   h . control_group_id         AND   g . org_id   =   22         AND   g . creation_date   >   sysdate   -   90         AND   h . creation_date   >   sysdate   -   90         AND   h . object_code   =   'DOCUMENT_TOTAL'         AND   f . control_function_id   =   8   -- 8 Represents Purchase Requisition Document Type. Query to find Approval Limits for PO SELECT   pj . NAME   job_name ,         g . control_group_name ,         h . object_code ,         h . amount_limit FROM     per_jobs   pj ,         po_position_controls

Receipt Routing in Oracle Purchasing

1.      Direct Receiving:-   It’s a single steps receiving process. Once the Item come in the warehouse, make the receipt and Delivery to sub inventory in one transaction Steps to perform transaction  -           using PO or Requisition Number -           PO is created and sent across to the supplier. -           Search for the Expected Receipt using PO or Requisition Number. You Can Create Receipt from either Purchasing Responsibility or using iProcurement Responsibility using Desktop Receiving Functionality. -           On receiving the receipt information from the supplier the user created the receipt in the system, and at the time of receipt enter the Sub Inventory and Locator and save the transaction 2.     Standard Receiving: - It’s a 2 Step PO receiving 1st we need to make the receipt and then we need to deliver the material into Sub Inventory Steps to perform transaction  -           Requisition Created and approved, auto converted to PO. -

EBS R12 Period Close Advisor: Purchasing

EBS R12 Period Close Advisor: Purchasing [ID 1359462.1]   NOTE:1358356.1 - Recommended Patches for Purchase Order and Requisition Processing NOTE:335.1 - Period Close Advisor: E-Business Suite (EBS) NOTE:1107953.1 - R12 Accrual Balance Mismatch Between Accrual Reconciliation Report and GL - Troubleshooting NOTE:1113712.1 - R12 FAQ: Accrual Accounting - On Line Accruals and Period End Accruals NOTE:1117353.1 - R12: Discrepancies with Accrual Reconciliation Report - Troubleshooting NOTE:1279848.1 - R12: Discrepancies With Period End Accruals - Troubleshooting NOTE:429105.1 - Impact of R12 Design in Procure To Pay Accounting Flow NOTE:467584.1 - R11 What Are The Basic Steps Of The Purchasing Receipt Accrual Period-End Process? NOTE:555547.1 - How To Change The Seeded Default Journal Category from "Receiving" to" Accrual"? NOTE:558421.1 - How To Diagnose Issues With Create Accounting Process For Procure To Pay Cycle In R12 NOTE:563100.1

Good Metalink Notes on Purchasing/Procurement Encumbrance Accounting

Purchasing Encumbrance Accounting 1) PO: Purchasing Encumbrance Accounting Concepts and Process Model (Doc ID 1089107.1) 2) Master Note For Oracle EBS Procurement Suite - Encumbrance And Accrual Accounting (Doc ID 1138043.1) For R12 Encumbrance Accounting process please refer to the following Notes: 1) Note 429105.1 - Impact of R12 Design in PO Accounting 2) Note 558421.1 - How To Diagnose Issues With Create Accounting Process For Procure To Pay Cycle In R12

Mapping Between PO Tables And General Ledger Tables - R12

Table relationships between PO tables and rcv_transactions and rcv_receiving_sub_ledger remain the same as in R11i. The following reference fields are used to capture and keep PO information in RCV_RECEIVING_SUB_LEDGER REFERENCE1 Source (PO or REQ) REFERENCE2 PO Header ID or Requisition Header ID (from po_headers_all.po_header_id or po_requisition_headers_all.requisition_header_id) REFERENCE3 Distribution ID (from po_distributions_all.po_distribution_id or po_req_distributions_all.distribution_id) REFERENCE4 Purchase Order or Requisition number (from po_headers_all.segment1 or po_requistion_headers_all.segment1) REFERENCE5 (Autocreated Purchase Orders only) Backing requisition number (from po_requisition_headers_all.segment1) RCV_TRANSACTION_ID Receiving transaction unique identifier (from rcv_transactions.transactions_id) The receiving package that populates this table is RCV_CreateAccounting_PVT (RCVVACCB.pls) Release 11i Mapping Ref Note.461103.1 - Mapping Between PO Tables

(R12.2+) Changes in Business Rules of PO Cancel Action Functionality

This article provides information about New feature in (R12.2+) related to Cancel Action Functionality and its Business Rules' changes - Oracle Purchasing now provides the following changes in business rules of the Cancel action functionality: When cancelling the PO, Oracle Purchasing will no longer launch the Approval Workflow to make the PO in 'Approved' status after cancellation. Buyers can cancel purchasing documents (at any level: header, line, and shipment) that are at the Requires Reapproval status. When cancelling the Approved PO (at any level), The application creates the document's new revision and maintains archived if archive on is set as 'Approve'. This information is communicated to suppliers. Action history will be recorded with the cancel action (in case of cancel at header level). When a buyer cancels a purchasing document that has changes since its last revision, the application now displays a warning message, which cl