Period Close Checklist In Oracle Account Receivables

Complete manual payments and adjustments for the period (including cleanup of ‘Out of Balance’ batches)

Check and Complete final Receivables Interface from Order Management

Complete manual invoices, DEBIT Memos and credit memos

Run your final Auto Invoice process

Correct ALL Auto Invoice rejects and re-run

Clear all receipts from Cash Management

Apply receipts against Invoices and Debit Memos

Review the Unapplied Receipts Register

Reconcile receipts

Apply Credit memo to Debit Memo and Invoices

Approve or reject ALL Pending Adjustments

Complete or delete ALL ‘Incomplete’ invoices

Complete or delete ALL ‘Incomplete’ credit memos

Correct and post ALL open Lockbox batches (If Lock Box Implemented)

Print Dunning (Reminder) Letters (Optional)

Run Journal Entries Reports

Review Journal Entries reports for ‘unusual’ accounts and correct as needed

Run Period End Reports

Balance to the Aged Trial Balance

Post to the General Ledger using the period start date through the period end date – verify that ALL steps completed successfully.

Close the period – verify that there are no items in error

Open the next period and the next Future period

Post Journal Entries (In General Ledger)

Balance to the General Ledger (for the key accounts)

Reference

Why Don’t My AR and GL Numbers MATCH BY Cathy Cakebread

Metalink

Oracle Account Receivable user Guide

e business Suite Diagnostics Period / Year End Close Note:402237.1

Price List Bulk Loader Example Scripts

Please apply Patch#4900462 and find the following example scripts under QP_TOP/patch/11.5/sql directory.

QPBLKEX1.sql – Script populates interface tables to insert price list header and price list line.

QPBLKEX2.sql – Script populates interface tables to insert price list header and price list line and pricing attributes.

QPBLKEX3.sql – Script populates interface tables to insert price list header and price break line.

QPBLKEX4.sql – Script populates interface tables to update price list header with qualifiers.

QPBLKEX5.sql – Script populates interface tables to attach secondary price lists to the primary price list.

Serial number is not available when doing a inventory transaction but shows in on hand quantity

serial-number-is-not-available-when-doing-a-inventory-transaction-but-shows-in-on-hand-quantity

Oracle Purchasing Hierarchies used for Approval routing.

There are two types of Hierarchies used for approval routing.

a. Position Hierarchies

b. Supervisor Hierarchies

Position Hierarchies

========================

Position Hierarchies are hierarchies that have a JOB/POSITION relationship.

For example, you could have a JOB called BUYER and within BUYER you could have various grades or POSITIONS of BUYER – Junior, Senior and Chief

Each POSITION has an approval limit, so when a purchase order exceeds the limits of the POSITION, the purchase order is forwarded onto the next POSITION in the Hierarchy.

The hierarchy for this JOB/POSITION type of hierarchy is defined on the Position Hierarchy form. When this is complete or is changed, the Fill Employee Hierarchy concurrent process must be run for the new hierarchy to come into effect.

The Position Hierarchy form can be found at PO Navigator – Setup – Personnel – Position Hierarchy

Supervisor Hierarchies

==========================

Supervisor Hierarchies are hierarchies that have an Employee/Supervisor relationship

The supervisor of an employee is defined on the Assignment zone of the Employee form

This type of hierarchy does not use the Position Hierarchy form, but is defined by the employee / supervisor relationship

If the purchase order raised by the employee exceeds the approval limits, the purchase order is forwarded onto the employees’ supervisor, as defined on the Employee form.

Reference

Oracle Metalink and Oracle White Papers

Formula to Calculate Available to Reserve at Different levels

The formula is  

Actual Available to Reserve = Minimum (Available to Reserve at Particular node/Sub Inventory level, Available to Reserve at higher nodes/ Inventory Organization Level)Explanation

——————————–
1. Organization level (highest level):

On Hand Quantity for item A = 345 – 30 = 315

(Here Consider 30 is stuck quantity in MMTT, Mean unprocessed pending transactions in MMTT)

So Available to Reserve at Organization level = 315
——————————–
2. Sub Inv level:On Hand Quantity for item A = 345
Available to Reserve at Sub Inventory level= 315
Actual Available to Reserve = Minimum (Available to Reserve at Sub Inventory level, Available to Reserve at Organization level)

Insert value in a table column c

Select Min(c) from dual

Result will be 315 Available to Reserve is 315

If anyone have any observation / reservation then let me know