When does Batch Close Variance Occur?

Batch Close Variances can occur in the following situations when using Actual Costing,

• If the batch was released in one cost period and the debit to WIP is valued at one cost, but the batch was completed in a later cost period when the credit to WIP for the same quantities is valued at a different cost.
  This results in a left over balance WIP due to the cost change and must be cleared out.

• Batch is released in one period and closed in the next period and has ingredient issues after last product yield and no product yield in next period.

• When the Ingredient consumptions and product yields are recorded in a period, and in the next period the ingredient, resource, or byproduct consumptions for these batches are updated without any further product yields.

• Ingredient issued in one period and returned back in next period with cost changes for ingredient across periods.
  - Essentially Ingredient/By-product transactions should be posted prior to product transactions in general, and certainly at least prior to last of product transaction so that such transactions do not contribute to batch close variance.

• Cost Allocation factors on the Formula are not same as Cost Allocation Factors on the Batch Material details which could happen when using Dynamic Cost Allocation factors (profile option - GMF: Cost Allocation Factor Calculation - set to "Dynamic")
  Any cost allocation factor change made after a Batch is released ( as it happens in case of dynamic cost allocation factors) would require re-layering.
  Re-layering these Batches followed by running the Actual Cost Process, Cost Update and OPM-Preprocessor will eliminate the Batch Close Variances for these Batches.

• The profile option - 'GMF: Batch Actual Cost Calculation Basis' is set to 'Use Virtual Incremental Backflush Quantities' for a situation where on a Batch all the Ingredients and Resources are not issued out Upfront.
  Virtual Incremental Backflush is essentially designed to address a common situation in process industries where most or all ingredients are issued upfront and there are multiple product yields. 
  Without using the Virtual Incremental Backflush, the first yield would be posted at very high cost and subsequent yields would be posted at zero cost.
  With Virtual Incremental Back flush, costs are apportioned based on the Formula setup even before transactions occur.
  Thus if those transactions do not actually occur prior to batch close, Batch Close Variances would result.

• Use of Virtual Incremental Backflush with consumption activity and cost changes for ingredients across periods.
  
  
  

  ---X---

  
  

  
  

JAI_OPM_GMD_ARIUD_T1

If you get this error message while doing material correction in a batch in OSP (Outside Processing) Organization, don’t worry this is a standard bug in Oracle R12.

nexpected ORA-20001: APP—20110: You can not reduce the

Actual Quantity

ORA-06512: at “APPS.APP_EXCEPTION”, LINE 72

ORA-06512: at “APPS.JAI_OPM_GMD_ARIUD_T1”, line 206

ORA-04088: error during execut

Cause:

APPS.JAI_OPM_GMD_ARIUD_T1 trigger is restricting from doing corrections in the batch.

With the help of following query, we can check the status of the trigger.

select status from all_triggers where trigger_name = ‘APPS.JAI_OPM_GMD_ARIUD_T1’

If the status of the trigger is active, disable it with the following query.

alter trigger APPS.JAI_OPM_GMD_ARIUD_T1 disable;

After doing the corrections in the batch enable the trigger.

alter trigger APPS.JAI_OPM_GMD_ARIUD_T1 enable;

Note:

This bug was there in 11i also. Oracle hasn’t provided the full functionality of OSP concept in Process manufacturing as they did for discrete manufacturing.

I have faced this issue many a times and have risen SR’s regarding this issue to oracle, for which the oracle suggests to disable the trigger and complete the batch. Since for process manufacturing (OPM) module, oracle is not supporting OSP concept (no 57F4 challan) there is no harm in disabling the trigger.

---X---

JAI_OPM_GBH_ARIUD_T1

If you get this error message while trying to revert the status of a batch in OSP (Outside processing) organization, disable the trigger and change the status of the batch.

ORA-20001: APP—20110: Encountered the error in trigger

JAI_OPM_GBH_ARIUD_T1ORA-00001: unique constraint

(JA.JAI_OPM_TXN_EXTN_HDRS_U1) violated

ORA-06512: at “APPS.APP_EXCEPTION”, line 256

In Package GME_BATCH_HEADER_DBL Procedure UPDATE_ROW

Solution:

Check the status of the trigger.

select status from user_triggers where trigger_name = 'JAI_OPM_GBH_ARIUD_T1'

If the status of the trigger is enabled, disable it with the following query.

alter trigger JAI_OPM_GBH_ARIUD_T1 disable;

After changing the status of the batch, enable the trigger.

alter trigger JAI_OPM_GBH_ARIUD_T1 enable;

Note:

This bug was there in 11i also. Oracle hasn’t provided the full functionality of OSP concept in Process manufacturing as they did for discrete manufacturing.

I have faced this issue many a times and have risen SR’s regarding this issue to oracle, for which the oracle suggests to disable the trigger and complete the batch. Since for process manufacturing (OPM) module, oracle is not supporting OSP concept (no 57F4 challan) there is no harm in disabling the trigger.

---X---

Subledger Accounting Balances Update

In this post we will see what Subledger accounting balances update concurrent is & what it does?

The Subledger Accounting Balances Update is a standalone concurrent program which calculates the control balances and analytical balances (supporting reference balances) for any newly accounted transactions.

Normally, Create Accounting and online accounting will automatically call the Subledger Accounting Balances Update program to calculate the control/analytical balances. However, there have been situations where multiple online accounting programs are called simultaneously, and if all of them have accounts which belong to either control accounts or analytical accounts then only one of the simultaneous online accounting programs will be successful in updating the balances.

To ensure that balances are up to date, it is recommended that you manually run the Subledger Accounting Balances Update program for the ledger at least once before you run the Third Party Balances report or before viewing Supporting Reference Balances. This is to ensure that all balances are updated completely.

---X---

Process Execution Parameters are not defined for the selected organization. Please define in Parameters form

When you got this error message while accessing “Production Supervisor” responsibility, it means valid “Process Execution Parameters” are not defined for the particular organization.

 

Navigation:

Production Supervisor – Setup – Parameters   

Totally there are five tabs to enter the information’s as below. Define the parameters as per your need.

Note:

The above screen shots are for indicative purpose only. Set the parameters as per the requirement. 

---X---

OPM Cost Allocation Process

In this post we will see what exactly OPM Cost Allocation Process concurrent does and how to run it.

OPM Cost Allocation process concurrent takes care of spreading the costs down to the products as defined in Allocation definitions form.

 

Parameters:

Legal Entity – Enter your LE

Cost Calendar – Enter the name of your calendar

Period – Enter the period for which the cost has to be allocated.

Cost Type – Enter the costing method which you use.

Fiscal year – Fiscal year

Period – This refers to GL Period

Allocation From - Enter the from allocation code   

Allocation To - Enter the to allocation code

Refresh Interface – Yes / No

---X---

COGS Recognition and Concurrent Processes

The matching and synchronization of the earned and deferred components of sales order revenue and COGS is accomplished by running the following COGS recognition concurrent processes.

• Record Order Management Transactions
• Collect Revenue Recognition Information
• Generate COGS Recognition Events
  
  

Record Order Management Transactions

The Record Order Management Transactions concurrent process picks up and costs all uncosted sales order issue and RMA return transactions and creates a record for each new order line in the costing COGS recognition matching table.

This process is not mandatory.

If you don’t run this process, then the cost processor will select and cost the uncosted sales order issues and insert them in the COGS matching table. This process can be used if you need to process the COGS recognition transactions at shorter intervals than the cost processor.

Collect Revenue Recognition Information

The Collect Revenue Recognition Information concurrent process calls an Oracle Receivables API to retrieve the latest revenue recognition percentage of all invoiced sales order lines in Oracle receivables for a specific ledger and with activity dates within a user-specified date range.

This process must be run before the Generate COGS recognition Event concurrent process.

Generate COGS Recognition Events

The Generate COGS Recognition Events concurrent request compares the COGS recognition percentage for each sales order line and accounting period combination to the current earned revenue percentage.

When the compared percentages are different, the process raises a COGS recognition event and creates a COGS recognition transaction in Oracle Inventory that adjusts the ratio of earned and deferred COGS to match that of earned and deferred revenue.

You must run this process after completion of the Collect Revenue Recognition Information concurrent process.

---X--- 

You cannot reverse frozen subledger journal sources

When reversing a posted Journal or batch if you get this error message, it means the journal source for the subledger journal is frozen.

This is an intended functionality in R12.

To reverse the journal you need to unfreeze the subledger journal source.

 

Navigation:

General Ledger – Setup – Journal – Sources

Query for the source of your journal

 

Select the pretended option from the ‘Freeze Journals’ list of values.

• Yes: Journals from this source cannot be changed in the Enter Journals form nor the Journal Correction form. In addition, you cannot reverse journals with Subledger Accounting journal sources that are frozen.
   

• No: Journals from this source can be changed in both the Enter Journals form and the Journal Correction form. In addition, you can reverse journals with unfrozen Subledger Accounting journal sources.
  

• Journal Entry Page Only: Journals from this source cannot be changed in the Enter Journals form but can be changed in the Journal Correction form. In addition, you cannot reverse journals with Subledger Accounting journal sources that have this option.

Change the value to ‘No’ & save. Now the system will allow you to reverse the journal.

 

Note:

After reversing the journal, freeze the subledger source (i.e.) change the value to ‘Yes’. If not frozen this will allow users to reverse subledger sourced journals at will, causing reconciliation problems between general ledger and the subledgers.

---X---

Order Import does not spawn child request

Even after running “Create Internal Orders” and doing “Order Import Request”, if the internal sales order (ISO) is not generated check whether Order Import concurrent has triggered the child concurrent.

 

If the child concurrent is not triggered, follow the below procedure to resolve the issue.

Why the child concurrent is not triggered?

This issue is caused because there was a value for Request Id column in OE_Headers_Iface_All table when the Order Import is submitted.

Order Import program would not pick up records for processing if the Request Id is already populated in the Interface table OE_Headers_Iface_All, and hence no child request would be spawned.

When Order Import sees a value for Request Id already populated, this is interpreted as an already processed record and is not picked up again.

Navigation:

Order Management – Orders, Returns – Import Orders – Corrections

Enter corresponding Order source & Order reference and click find.

 

This will put out the data from the Interface table. Clear out the Request Id and uncheck the Error_Flag, which is present in the status tab of the Corrections screen.

Now re-submit Order Import, now the child concurrent will be triggered & ISO will be generated.