Sreekanth Reddy Pothula's Oracle ERP Blog

What is Period Close? Closing is the process of accounting for all transactions at the end of each period so all supporting information is transferred to the General Ledger. Sub-ledgers cannot be closed if the required transactions in that period are not processed. Sub-ledgers are E-Business Applications that post (transfer accounting records) to the General Ledger: for example, Payables, Receivables, Inventory, etc. 1. Order Management / Shipping 2. Cash Management / Treasury 3. Payables 4. Receivables 5. Purchasing 6. Inventory / Costing 7. Projects 8. Assets 9. General Ledger —————————————– Payables Complete All Transactions for the Period Being Closed Run the Payables Auto-approval Process for All Invoices / Invoice Batches Review & Resolve Amounts to Post to the General Ledger Reconcile Payments to Bank Statement Activity for the Period Transfer All Approved Invoices Payments, Reconciled Payments to the General Ledger Review the Pay...

R12 Master Generic Data Fix Diagnostic for Purchase Orders and Requisitions Visit Doc ID1474734.1 for the R12 Master Generic Data Fix Diagnostic for Purchase Orders and Requisitions.  Running this one script identifies known data integrity issues within the Purchasing application (for example errors with cancel and close and unit of measure issues) where there are often generic data fixes (GDFs) already available.  The script will produce an HTML output report of all known problems relating to the purchasing transactions created in the specified date range, along with information on notes and/or data-fix patches which are already be available to resolve the data issues. The following data checks are included: Document type records with null ORG ID. Synchronization issues with archive tables. Quantity billed/amount billed mismatch in purchase order shipments and distributions. Purchase orders with a mismatc...

SELECT   aca . employee_id ,         ( SELECT   full_name          FROM     hr_employees   he          WHERE    he . employee_id   =   aca . employee_id )   employee_name ,         icc . ccnumber ,         acca . trx_id ,         acca . transaction_type ,         acca . transaction_type ,         acca . transaction_date ,         acca . transaction_amount ,         acca . billed_amount ,         acca . posted_amount ,         acca . expensed_amount FROM     ap_cards_all   aca ,...

Sometimes the organization's business requirement may not be met by the standard requisition approval workflow. Customizations have to be done to meet these business requirements. Below are some of the scenarios where the approval path will have to be routed differently when compared to the standard path. 1. Requisitions created on certain items. 2. When a base line is set on Approval limit. 3. Information displayed in Notifications. Steps to create the custom workflow: 1. In the workflow builder, copy and paste the standard workflow Requisition (REQAPPRV) (File Name :  $PO_TOP/patch/115/import/US/poxwfrqa.wft) to the DB. It will ask for a new ITEM_TYPE. Provide a name for the custom workflow. 2. Add the required attributes, functions and nodes to the Process. Make necessary changes to the Process. 3. For Notifications, messages need to be provided appropriately. PL/SQL messages may not work properly in 11.5.10 version. For those cases, JRAD notification messages...

Period End Closing Checklist in Oracle in R12 Product family Product Code Step number Step name 1 Order Management (OM): Order Management ONT 1.1 Complete the sales orders Order Management ONT 1.2 Import Sales Order Order Management ONT 1.3 Pre-Billing Acceptance Shipping WSH 1.4 Complete the shipping transactions Order Management ONT 1.5 Prepare the link with AR Order Management ONT 1.5.1 Check run of Workflow background engine Receivables AR 1.5.2 Run the Invoice Interface/Autoinvoice Receivables AR 1.5.3 Verify the Autoinvoice Exceptions 2 Receivables (AR): Receivables AR 2...