100% found this document useful (2 votes)
2K views25 pages

Oracle Process Manufacturing Period End Closing Process

This document provides an overview of the key processes involved in period-end close for Oracle Process Manufacturing (OPM). It discusses the GMF Period Close process, Actual Cost process, Cost Rollup process, Lot Cost process, OPM Cost Update process, OPM Accounting Pre-processor, and Create Accounting process. It provides guidance on best practices for running each process, including order, settings, and handling errors. The document aims to help customers successfully execute period-end close in OPM.

Uploaded by

tenalis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (2 votes)
2K views25 pages

Oracle Process Manufacturing Period End Closing Process

This document provides an overview of the key processes involved in period-end close for Oracle Process Manufacturing (OPM). It discusses the GMF Period Close process, Actual Cost process, Cost Rollup process, Lot Cost process, OPM Cost Update process, OPM Accounting Pre-processor, and Create Accounting process. It provides guidance on best practices for running each process, including order, settings, and handling errors. The document aims to help customers successfully execute period-end close in OPM.

Uploaded by

tenalis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 25

<Insert Picture Here>

OPM Period End Process Best Practices


Venkat Chukkapalli, Director (OPM Development) Parag Kanetkar, Senior Principal Engineer (OPM Development)

Agenda

OPM Period Close Process Introduction Costing and Accounting processes Q&A

OPM Period Close Process - Introduction


Processes Involved in Period Close Activity:
Running GMF Period Close Process to compute period end Inventory Balances. Running one or more of the Cost engines. Actual Cost Process Cost Roll up Lot Cost Process Cost update

OPM Accounting Pre-Processor


Create Accounting

Introduction

continue...

GMF Inventory Period Close Process

GMF Inventory Period Close Process

continue...

Concurrent process records Period End Inventory Balances and Closes Inventory Periods of process organizations.

Run after all transactions are recorded.


Process can be run in Preliminary and Final Mode. Process can be run multiple times in Preliminary Mode.

Use this concurrent process to close inventory periods of process organizations


This R12 Concurrent Process replaces 11i Period Close in OPM Inventory. Data generated is used by Actual Cost Process, OPM Accounting Pre-Processor and Inventory Valuation Report.

Actual Cost Period-End Processing Flow

OPM Actual Cost process

OPM Actual Cost process


Run after all transactions are recorded. Process can be run multiple times. As far as possible avoid creating circular references in batches by creating flat batches. This can be done when there are no common intermediates for multiple products. Avoid creating circular references in batches that can cause diverging items costs in the actual cost process. Optimal settings for profiles (GMF: Costing Tolerence Percent and GMF: Actual Costing Maximum Iteration Limit for Circular Reference ) when circular references can not be avoided. Performance Vs Accuracy trade-off. Refer to notes: 1319329.1 and 417820.1. Whenever using cost adjustments to fine tune the item cost, use appropriate actual cost adjustments (Unit Cost adjustment, Value Cost adjustment, Average Cost adjustment).

Re-layer batches whenever cost allocation factors are updated or dynamic cost allocation factors are used.
Run on regular intervals and resolve transactional and costing errors
9

Standard Cost Period-End Processing Flow

10

OPM Cost Rollup process

11

OPM Cost Rollup process

Continue

Run any time after Ingredient costs for the period are recorded / updated. Process can be run multiple times. Process does not have to be run if costs are not changed. In such situation older costs can be copied instead. It is better to freeze the cost as early in the period as possible. This allows Accounting processes to be run on regular intervals(daily, weekly) in high transaction volume environments. This will also reduce the time during period close activities at period end.

12

Lot Cost Period-End Processing Flow

13

OPM Lot Cost process


Generally similar to Perpetual Costing in Discrete Costing, but at item, org and lot level. Process can be run anytime after all prior transactions are correctly recorded. It can be run multiple times in Preliminary mode. Accurate recording of transaction date. This would avoid inaccuracies and errors in lot costing. Avoid back-dating of the transactions as much as possible.

Set profile GMF: Maximum Number of Iterations for Lot costing to 2 or 3 if you are observing large number of uncosted lot transactions messages in the process.
Data generated is used by OPM Accounting Pre-Processor if customer is using Lot costing.

14

OPM Cost Update process


Copies cost data generated by costing engines for use by OPM Accounting preprocessor to Generate distributions. Process can be run multiple times. Process is required to be run after costs are rolled up or costs are copied. Additionally freezes Formula, Routings if run in final mode. This process is not a required process for Lot Costing customers if all items are lot controlled and lot costed. Data generated is used by OPM Accounting Pre-Processor.

15

OPM Accounting Pre-processor

16

OPM Accounting pre-processor


Run OPM accounting preprocessor on regular intervals(daily, weekly) in high transaction volume environments. Review and resolve errors without waiting for period close. If the preprocessor is taking long time to complete due to large transactional volume, then consider running process separately for each source, running process for smaller DATE range. Review Detailed Subledger Report even before running create accounting. This will have most of the information, except for the accounts which would not typically change after going live. Set profile GMF: Commit Count in Accounting Pre-Processor to appropriate value (5,000 to 10,000) based on the transactional volume. Pre-processor wrapper program for Order Management enables to run parallel runs within the period

17

Detailed Subledger Report

18

Review the accounting entries

19

SLA Setup and Create Accounting process


Avoid defining multiple Priorities in an ADR. Where ever possible try if the same thing can be achieved using Mapping Sets in SLA instead of creating more and more individual priorities in an ADR. Maintain minimal number of cost components for item cost. More number of components would lead to more number of journal lines to be processed and hence could lead to performance issue . Accounting for secondary ledgers (SLA Vs OPM) Use parallel workers for improved performance Run the process in DRAFT mode on regular intervals (daily, weekly) in high transaction volume environments. Review and resolve errors without waiting for period close. Set profile GMF: Check If Costs Are Frozen When Create Accounting Run In Final Mode to Yes if additional check is needed while running create accounting in final mode. Upgrading from 11i to R12 Re-implementing Vs Migrating 11i MAC Accounting rules
20

Create accounting

On Submitting program, the following requests will be invoked:


Create Accounting Accounting Program Journal Import and Subledger Accounting

Balances Update

21

Custom Sources
Example1
Extend the list of sources available to application accounting definitions Used to derive accounts based on non-standard sources PL/SQL function used to derive the source Return value can be a string, an accounting flexfield or a value set

22

General Recommendations

Analyze the database schema statistics at regular intervals. If the transaction volume is expected to be very high, then it is recommended to maintain multiple legal entities. Because, all OPM costing / accounting processes are run at the Legal entity level. Keep cost structure as simple as possible by having fewer Cost component class, Analysis code combinations for Item Costs. This can be done by Optimally defining Material Cost component class setup for the items, cost component classes for resources and in set up for Material cost components in Freight & Special charges (OR) LCM setups. Check health of the transactions and costs on regular intervals. Pending / stuck / unposted transactions Uncosted items/lots and Abnormal variations in items costs Upgrade considerations (11i to R12) Warehouse to subinventory / organization OPM Company to Legal Entity / organization Global items Vs organization items
23

[email protected] [email protected]
24

25

Common questions

Powered by AI

The Lot Cost Process in OPM functions similarly to Perpetual Costing in discrete costing systems, but operates at the item, organization, and lot level. It supports accurate cost recordings by ensuring that transaction dates are correctly logged to avoid inaccuracies and errors. This process allows adjustments to be made if there are issues with cost allocations and can be run multiple times in Preliminary mode. Compared to discrete costing, the lot cost process provides more granularity, which can be beneficial in environments where lot traceability and specific cost identification are critical .

In high transaction volume environments, running the OPM Accounting Pre-Processor is crucial as it processes cost data into accounting distributions and ensures that accounting entries are prepared accurately and efficiently. By running this process regularly (daily or weekly), organizations can review and resolve potential errors before the period close, reducing the likelihood of last-minute disruptions. The process should be adjusted for large transactional volumes by setting an appropriate 'GMF: Commit Count in Accounting Pre-Processor' value, and if it takes too long, considering splitting runs by source or date range to improve efficiency .

Maintaining a simple cost structure in OPM is essential to ensuring system performance and accuracy. By defining fewer cost component classes and analysis code combinations, organizations can reduce the complexity of calculations and processing costs, which in turn minimizes the number of journal lines to process, thus reducing potential performance bottlenecks. A simpler structure also enhances the accuracy of cost data since it decreases the likelihood of errors that can occur in more complex configurations. This simplification can streamline the setup of material cost components and helps in maintaining efficient transactional and accounting processes .

When upgrading from Oracle 11i to R12 in the context of OPM accounting rules, organizations should carefully consider whether to re-implement or migrate existing 11i MAC accounting rules. Factors such as potential performance improvements, alignment with current business processes, and readiness of data to adapt to new structural changes in R12 should be evaluated. This might involve redesigning the warehouse to subinventory or organization mappings and changing from OPM company setups to legal entity configurations. Other considerations include managing global versus organizational items and ensuring seamless integration with existing systems .

Potential issues in cost and transaction data management in OPM include pending, stuck, or unposted transactions and uncosted items or lots leading to abnormal cost variations. To mitigate these issues, regular analysis of database schema statistics is recommended. Strategies include ensuring accurate transaction date recordings to prevent errors and adjusting the 'GMF: Maximum Number of Iterations for Lot costing' if there are large numbers of uncosted lot transaction messages. Furthermore, running routine checks to ensure no discrepancies in cost or transaction data can prevent these issues .

The Oracle Process Manufacturing system handles circular references in cost batches by recommending creating flat batches, which means avoiding intermediates that are common to multiple products to prevent diverging item costs. When circular references cannot be avoided, optimal settings should be used for GMF: Costing Tolerance Percent and GMF: Actual Costing Maximum Iteration Limit to balance between performance and accuracy. These measures help prevent inaccuracies in cost calculations that might arise from the iteration limits in handling circular references, ensuring that cost data remains reliable while maintaining acceptable performance .

To minimize performance issues in the Create Accounting process within the OPM system, it is suggested to avoid defining multiple priorities within an Accounting Derivation Rule (ADR) and instead use Mapping Sets within Subledger Accounting (SLA). Maintaining a minimal number of cost components for item cost to reduce the number of journal lines processed can also prevent performance bottlenecks. Implementing parallel processing techniques, such as using parallel workers, is recommended for better performance. Additionally, running the process in DRAFT mode at regular intervals allows for the identification and resolution of errors before the final accounting run .

Freezing costs early in the period within the OPM system's Cost Rollup process allows for accounting processes to run regularly, such as daily or weekly, in environments with high transaction volumes. This timing can reduce workload and time pressure at the end of the period close activities, streamlining operations and improving accuracy in accounting entries. However, the risk lies in premature cost freezes that may not account for late-arriving cost adjustments or unforeseen price changes which might require retroactive adjustments and could affect the accuracy of financial reports .

The GMF Period Close Process plays a critical role in OPM inventory management by recording period-end inventory balances and closing inventory periods for process organizations. It adapts from the older version, 11i, by replacing the period close function with a new R12 Concurrent Process. This new process can run in both Preliminary and Final modes, allowing for multiple runs in Preliminary mode to refine data before final closure. This adaptation aims at improving accuracy in inventory records and enhancing the efficiency of subsequent costing and accounting processes .

The main processes involved in closing an inventory period within the OPM system are: running the GMF Period Close Process, using cost engines such as the Actual Cost Process, Cost Roll up, and Lot Cost Process, performing cost updates, and executing the OPM Accounting Pre-Processor followed by creating accounting entries. These processes ensure accurate computation of period-end inventory balances, updating and maintaining cost data, and generating accounting distributions to reflect accurate financial statements. The GMF Period Close Process specifically records the period end inventory balances and allows closure of inventory periods for process organizations, while the cost engines adjust costs accurately to avoid discrepancies. The accounting pre-processor and subsequent create accounting processes ensure that all financial transactions are captured and reported correctly .

You might also like