Sie sind auf Seite 1von 6

1. Order Management / Shipping 2. Cash Management / Treasury 3. Payables 4.

Receivables 5. Purchasing 6. Inventory / Costing 7. Projects 8. Assets 9.


General Ledger
This article explains, steps to be taken in performing period-end processing for Oracle Order Management,
Note: If MOAC is enabled in your EBS Order Management Responsibility, you have to perform the above tasks for each Operating Unit.

1. Complete All Transactions for the Period Being Closed


Ensure that all transactions have been entered for the period being closed

Enter and book all orders

Schedule orders

Enter and book return material authorizations

Run the Generate Pre-billing Acceptance Program for Pre-billing, Implicit Acceptance

Confirm shipments and optionally, the creation of install base entries for shipments

Confirm OM-shipping transaction for the period

Sales order acknowledgments

Cancel backordered included items

Respond to workflow approval notifications

Confirm that invoice interface (OM-> AR interface) has been completed

Optionally, confirm that service contracts for warranties and extended warranties have been created

Close orders
Closing orders that are complete enhances performance, since many programs, windows and report queries retrieve open orders only. Orders marked as closed
are not selected, increasing system speed and efficiency. Closed orders are excluded from many of the standard reports available in Order Management, so
reporting can be limited only to the active orders.
* Close lines and close orders are implemented using workflow. Order Management provides seeded close line and close order workflow sub-processes to close
the

order header

and

line,

respectively.

These

processes,

when

included

in

the

order

header

or

line workflow, close the status of the eligible order or lines. Once an order is closed, no lines can be added or changed.
* The order header close order process checks at the end of every month to see if all the lines associated with it are closed. It closes the order header if it finds
that all the lines are closed.
Close Order Lines
* An order line is eligible to close when it completes all of the line-level activities within the workflow process. Order lines can close independent of each other.
Once an order line is closed, no changes can be made to any fields except the descriptive flexfield, for which you can define processing constraints.
Holds Effect on Eligible Lines
* The close order and close line workflow activities will close order or lines if only generic holds are present .If orders or lines have activity specific holds present,
they will not be closed by workflow activity.
2. Ensure all Interfaces are Completed for the Period (Optional)
Ensure that all interfaces for the current period have been processed: Order Import from External Order Systems.
* If you are using external order processing systems for data entry of orders, use the Order Import to update Order Management from your external systems. If you
are using the Order Management public API to create orders, ensure that the processes calling the public API have completed.
* Use the Order Import Correction window to examine the orders and optionally correct data if it fails the import process. Use the Error Message window to
determine if your data failed to import.
Order Import from Oracle Purchasing for Internal Orders.
If you are using Oracle Purchasing to process Internal Purchase Requisitions, the following processes need to be completed:
a) Enter and approve all internal purchase requisitions in Oracle Purchasing.
b) Run the Create Internal Sales Orders Process in Oracle Purchasing for all requisitions within the current period. Use the Create Internal Sales Orders
process to send requisition information from approved, inventory-sourced requisition lines to the Order Management interface tables. Then, the Order Import
process is run from within Order Management to generate the internal sales orders. The Create Internal Sales Orders and Order Import processes can be
scheduled to run automatically at specified intervals.
c) Run Order Import to create internal sales orders from internal requisitions.
d) Run the Internal Order and Purchasing Requisition Discrepancy Report which displays the differences between the purchasing requisition entered and the
actual items ordered during order entry.

This report includes all open and closed orders, order numbers, order date ranges,order types, requisition numbers, items, ship to information, scheduled dates,
and internal requisition and internal sales order hold discrepancies.
e) Use the Order Import Correction window to examine the orders and optionally correct data if it fails the import process.Use the Error Message window to
determine if your data failed to import.
f) Invoice Interface / AutoInvoice, for external orders. Internal orders do not go through the Invoice interface/ AutoInvoice process. This process will ensure all
shipped sales order information is transferred to Oracle Receivables when it reaches the appropriate point in the order workflow. The AutoInvoice Process updates
Oracle Receivables for invoice and revenue information, as well as credit memos and credits on account created from returns.
3. Review Open Orders and Check the Workflow Status
Use the Sales Orders Workbench to review open orders using the Advanced Tabbed Region to specify controls such as whether to find closed orders/lines and
cancelled orders/lines.
The Sales Orders window displays the order header status in the main tab of the Order Information tabbed region. The order line status is displayed in the main
tab of the Line Items tabbed region.
The Workflow Status option on the Sales Orders window Tools menu launches the Workflow Status page. The window shows in tabular format all the activities an
order header or line has completed and the corresponding results.
From the status page, you can access the Workflow monitor to see the order or line status in a more graphical format. This is available through the View Diagram
button.
4. Review Held Orders
Run the following reports to assist with reviewing sales orders on hold:
a) Orders on Credit Check Hold Report
The Orders on Credit Check Hold Report identifies all of the credit holds currently outstanding for a customer within a date range, or identifies why a particular
order is on hold. Order Management allows you to perform a credit check on customer orders and automatically places orders on hold that violate your credit
checking rules. This report is automatically sorted by customer, currency code, credit check rule, and order number.
All balances are calculated as they are using the online credit check rule, including the factor for shipments and receivables for a certain number of days.
b) Hold Source Activity Report
The Hold Source Activity Report reviews holds placed and removed under a hold source during the time period you specify. This report indicates the date and the
type of activity for each hold transaction.
c) Outstanding Holds Report
The Outstanding Holds Report reviews order holds for the customer or customers you choose. This report displays the order number, order date, ordered items,
and order amount for each order line on hold for each customer you select. It is automatically sorted by customer, order number, order line, and then order line
detail.
5. Review Customer Acceptances (Optional)
In Pre-Billing Customer Acceptance, once the goods are accepted, invoicing is carried out. In Post-Billing Acceptance, the revenue recognition process is
deferred and linked to customers accepting the shipped goods.
6. Review Discounts
It is recommended that you review discounts processed as part of the order process to ensure appropriate discount policies have been followed, and exceptions
are clearly identified and reviewed and/or followed up. Use the following reports:
a) Order Discount Detail Report
The Order Discount Detail Report reviews discounts applied to orders by order line detail. This report provides detailed line pricing information, including price list
price, selling price, and discount information.
b) Order Discount Summary Report
The Order Discount Summary Report reviews discounts applied to orders. This report provides order level pricing information, including agreement,
salesperson and total order discount.
7. Review Backorders
Review backlogs and backorders to ensure that these items are current. If necessary, process cancellations for items/lines which are no longer required.
a) Backorder Detail Report
The Backorder Detail Report reviews all customer orders that have been backordered. This report provides details for each order including customer name, order
number, order type of each order, all backordered items and their appropriate line numbers, total quantity both ordered and backordered, and monetary amounts of
both ordered and backordered quantities.
b) Backorder Summary Report
The Backorder Summary Report lists all unshipped orders. This report includes only open orders in an order cycle that includes pick release. It displays order
information such as order number, customer name and number, order type, purchase order, order date, last shipped date, and the monetary amounts ordered,
shipped and outstanding. This report also includes total amounts for customers and currencies. These amounts involve totals for shippable items only.
8. Review and Correct Order Exceptions
The following reports should be reviewed, and exceptions corrected before completing the Order Management/Receivables period end:
a) Unbooked Orders Report

Use this report to review orders entered but not booked. They may indicate incomplete processing, which needs to be corrected, completed, or deleted
as appropriate.
b) Retry Activities in Error
There are cases when retrying a workflow activity in error will not resolve the problem. When Exception Management encounters this situation, the
workflow activity is set to notified instead of being retried.
c) Sales Order Workflow Status Report
The Sales Order Workflow Status Report enables Order Management users to locate orders that are not progressing through associated workflows as expected.
9. Reconcile to Oracle Inventory
Run the following reports for reconciliation with Oracle Inventory:
a) Backorder Detail Report
b) Review Backorders
c) Returns by Reason Report
The Returns by Reason Report reviews all return material authorizations for various return reasons. Order Management automatically sorts this report by currency,
return reason, and then item.
10. Create Service Contracts (Optional)
Run the Service Contracts Order Processing Concurrent request to create service contracts for extended warranties.
11. Reconcile to Oracle Receivables (Optional)
Run the following reports to assist in reconciliation of orders invoiced in the period:
a) Commercial Invoice (for all ship dates within the current AR period)
The Commercial Invoice Report lists all confirmed shipped items in a delivery. If only a delivery name is specified when defining the parameters of this
report, Shipping Execution prints one commercial invoice per delivery within the trip.
b) Order/Invoice Detail Report
The Order/Invoice Detail Report reviews detailed invoice information for orders that have invoiced. A variety of parameters can be used to print the invoice
information for a specific order or group of orders. If there are no invoices for a particular order that meets the parameter criteria, Order Management prints in the
report that no invoices exist for that order.
12. Run Standard Period End Reports
The following reports should be run each period:
a) Cancelled Orders Report
The Cancelled Orders Report reviews all orders that have been cancelled. This report provides a summary of each cancelled order, including order number,
customer name, line number and item, the date and reason the order or order line was cancelled, the quantity ordered and the quantity cancelled, and who
cancelled the order.
This report can be used to report total amounts cancelled in a specified time-frame, and allows evaluation of the most common cancellation reasons, review
cancellations by salesperson, or review cancellations by customers.
b) Salesperson Order Summary Report
The Salesperson Order Summary Report reviews orders for one or more salespeople.This report displays the order and each order line associated with each
salesperson. Salespeople can use this report to see their current outstanding orders and their status.
This report shows open orders, quantity ordered, shipped, cancelled, and invoiced and their potential commission.
The report displays all open and closed orders for a salesperson, customer or customer number, agreements, order numbers, order date ranges, order types,
line type, and detailed sales credit information for lines in a selected range.
c) Customer Acceptance Report
Generate Pre-billing Acceptance Program for Pre-billing, Implicit Acceptance.

Cash Management
Period End Process In Cash Management R12:
Oracle Cash Management is an enterprise cash management solution that helps you effectively manage and
control the cash cycle. It provides comprehensive bank reconciliation, bank, bank branches & internal bank

accounts setup, intra-bank account transfers, cash pooling and flexible cash forecasting. The Bank
Reconciliation process enables the verification of entries on the Bank Statement by reconciling that
information with system transactions in Oracle Payables, Oracle Receivables and Oracle General Ledger.
During the Bank Reconciliation process miscellaneous transactions can be created for bank-originated
entries, such as bank charges and interest. Cash forecasting is a planning tool that helps anticipate the flow
of cash in and out of the enterprise, allowing the projection of cash needs and evaluation of the company's
liquidity position.
Procedures
The following steps are taken in performing period-end processing for Oracle Cash Management.
1. Complete Daily Cash Management Activities
Complete bank account transfers for the day, validate them, if necessary, and send payment instructions to
the bank.
2. Load Bank Statements
Detailed information from each bank statement, including bank account information, deposits received by
the bank, and checks cleared needs to be entered into Cash Management. Bank statements can be either
manually entered or loaded electronically from information received directly from your bank. For
organizations with high transaction volumes bank statements should be loaded and reconciled on a daily
basis.
3. Generate Sweep Transactions
If you have target balance or zero balance accounts (ZBA) with your banks, you can automatically generate
system transactions to match banking information once the bank posts the sweeps. Once the bank
statements are imported, run the Sweep Transaction Generation concurrent program. The program will scan
the bank statement for sweep lines and, based on the cash pool setup in the system, create sweep
transactions between your internal bank accounts, which can be accounted for and subsequently reconciled.
4. Create Bank Statement Cashflows
If you have recurring items such as bank fees and interest appear on your bank statement, you can use the
Bank Statement Cashflow Creation program to create system transactions (cash flows) to match banking
information . Once the bank statements are imported, run the Bank Statement Creation concurrent program.
This program will scan the bank statement for specific codes, as defined in the Bank Statement Cashflow
Mapping, and create cashflows, which can be accounted for and subsequently reconciled.
5. Reconcile Bank Statements
Once detailed bank statement information has been entered into Cash Management, the information must
be reconciled with the subledger transactions. Cash Management provides two methods to undertake
reconciliations:
a) Automatic
Bank statement details are automatically matched and reconciled with subledger transactions. This method
is ideally suited for bank accounts which have a high volume of transactions.
b) Manual
This method requires a manual match of bank statement details with subledger transactions. This method is
ideally suited to reconciling bank accounts which have a small volume of monthly transactions. The manual
reconciliation method can also be used to reconcile any bank statement details, which could not be
reconciled automatically.
6. Create Miscellaneous Transactions
During the reconciliation process, miscellaneous transactions for bank-originated entries, such as bank
charges and errors can be created. Oracle Payables payments or Oracle Receivables receipts can also be
manually created.
Note: The automatic reconciliation process can be set up to create miscellaneous transactions automatically.
Attention: If you create transactions during the reconciliation process, you will need to re-run the Create

Accounting routine from Oracle Receivables to ensure all information is transferred to the General Ledger.
6a.Complete Bank Transfers
Complete the bank account transfer whether it is manual or automatic and record the validation if required
before completing the transfer.
7. Review Auto-Reconciliation Execution Report
Once the reconciliation process has been completed, reviewing the reconciliation results is recommended.
This report shows import and reconciliation errors that occurred when running the Auto-Reconciliation
program. Cash Management automatically produces this report during the automatic reconciliation process.
You may also request it as needed from the Submit Request window. This report includes either statement
import errors, which prevented the automatic loading of your bank statement, or your reconciliation
exceptions found during the automatic reconciliation process. This report lists the details of any
miscellaneous transactions that were created in Receivables during the automatic reconciliation process.
8. Resolve Exceptions on the Auto-Reconciliation Execution Report
Resolve the exceptions on the Auto-Reconciliation Execution report by either rerunning the import process or
by manually reconciling the exceptions.
9. Run Bank Statement Detail Report
This report shows statement and transaction information for a specific bank account statement, including
bank statement header information, statement line detail, and reconciled transaction detail. This report lists
any un-reconciled transactions separately with their current status, and the statement totals for each type of
transaction, including the amount entered, reconciled, un-reconciled, over-reconciled and under-reconciled,
and gives you the option to select only un-reconciled statement lines.
10. Run Transactions Available for Reconciliation Report
This report shows all transactions available for reconciliation for a specific bank account. It lists detailed
transaction information for your Available Receipts, Available Payment, and Available Journal Entries for
reconciliation. Detailed information includes the Customer, Supplier or Batch Name, Transaction Date,
Payment Method, Transaction Number, Currency, and Amount. This report only lists void payments if the
Show Void Payments option on the Systems Parameters window is checked. It does not list reversed receipts
due to user error nor does it list the associated original receipts that were not reconciled. This
report groups transactions by status so that void or reversed transactions are separate from other
transactions.
11. Resolve Un-reconciled Statement Lines
Resolve the un-reconciled statement lines by manually reconciling the statement lines to the available
transactions.
12. Post to General Ledger
Create journal entries for eligible accounting events generated by Bank Account Transfers and Bank
Statement Cash Flows by submitting "Create Accounting" concurrent program. The program creates and
optionally transfers and posts journal entries to General Ledger. If you do not transfer the journals to General
Ledger immediately, you can later submit the "Transfer Journal Entries to GL" concurrentprogram.
Attention: Final journal entries cannot be further modified in Cash Management. Please make sure you are
satisfied with the draft journal entries before creating final accounting. In addition to creating final
accounting entries, the program can be run in a draft mode, in which case draft journal entries will be
created. Such journals cannot be transferred or posted to General Ledger.
13. Run the GL Reconciliation Report
Use this report to reconcile the General Ledger cash account to a bank statement balance.
This report lists a balance and an adjusted balance for the bank statement. It also lists a separate
adjustment amount for un-reconciled receipts, payments, and journal entries, as well as bank errors.
Warning: To ensure that this report is accurate, you must first perform these tasks:
* Reconcile all statements in Cash Management.

* Transfer journal entry transactions from Oracle Payables and Oracle Receivables to your General Ledger.
* Post journals in General Ledger, if transfer from sub-ledgers was not in FINAL POST mode.
14. Run the Account Analysis Report for the General Ledger Cash Account
Run the Account Analysis Report from General Ledger for the General Ledger Cash Account Flexfield and sort
by Source.
15. Review the Account Analysis Report
Review the Account Analysis Report to ensure that only bank account related transactions have been posted
to the General Ledger Cash Account by checking the Source of the transactions. Valid sources will include
Payables and Receivables. Transactions entered directly via General Ledger will have a Source of Manual or
possibly Spreadsheet if Web Applications Desktop Integrator (Web ADI) is used.
16. Correct any Invalid Entries to the General Ledger Cash Account (Optional)
Reverse or amend any journals incorrectly posted to the General Ledger Cash Account, which were
highlighted during the review of the Account Analysis Report. To prevent invalid journal entries to the General
Ledger Cash Account enable security rules appropriately.