HOW TO STOP/BLOCK WORK FLOW MAILER SEND MAIL FROM THE CLONED INSTANCE

HOW TO STOP/BLOCK WORK FLOW 

MAILER SEND MAIL FROM THE 

CLONED INSTANCE

YOur Work Flow mailer is triggering Mail often when you clone your Instance and you are unable to test the New 
stuff using work Flow Mailer 

Here is the solution for the Work flow mailer to stop sending older mails in the Test Instance 

UPDATE WF_NOTIFICATIONS

SET STATUS = ‘CLOSED’

where status =’OPEN’;

UPDATE WF_NOTIFICATIONS

SET MAIL_STATUS = ‘SENT’

where status =’OPEN’;

commit; 

Simple , but very Effective steps to Control your work flow mailer , sending old mails

Check this Steps:

Application Manager — > Application Dashboard ->

Application System– > Dev–> service Components –> Component Details

Set override Address : Dev: Work Flow Notification Mailer

Enter the Over Ride Address : *******. Mail .Com

Update the scripts:

update fnd_svc_comp_param_vals fscpv
set fscpv.PARAMETER_VALUE = ‘<override email address>’
where fscpv.parameter_id in (select fscpt.parameter_id
from fnd_svc_comp_params_tl fscpt
where fscpt.display_name = ‘Test Address’);

If this is Entered he/She will receive all the notification mails which has been triggered in the DEV 
or UAT 

Step 1Login to “Workflow Administrator Web Applications”

Step 2
Ensure that Notification Mailer is running, and then click on icon as below

Step 3
Click on “View Details”

Step 4.
Click on “Set Override Address”

Step 5.
Finally you can change the email address here. Please read the instructions in red carefully.

WHAT IS BATCH CLOSE VARIANCE 

IN OPM?

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.

WHAT ARE ALL ORACLE ASCP PLAN 

TYPES?

In R12, you can launch three type of plans:

1. Production Plan
2. Manufacturing Plan
3. Master Plan

For MPS Planning item level, you should run Production Plan

And for MRP Planning Item, you should run Manufacturing plan.

Please see the explanation from Dev in similar question from other customers in Oracle Technical 
forum:

“The below are the 3 plan types :
1. MPP (Master Plan)
2. MPS (Production Plan)
3. MRP (Manufacturing Plan)

A. In 11.5.9, we had three plan types: DRP (Distribution Plan), MPS (Production Plan) and MRP 
(Manufacturing Plan)

B. In 11.5.10, we had three plan types: MPP, MPS and MRP. We changed the DRP name to MPP.
Why? Because in R12, we introduced a new Distribution Planning engine and having the term DRP 
used for the old plan type would have caused more confusion than MPP.”