Translate

Saturday, July 26, 2014

Invalid Object MSC_EXA_UTIL

Step if the package MSC_EXA_UTIL is invalid

Error statement in Package body(Line 23)

FUNCTION check_exa_nodes return number IS
vCount number;
BEGIN
 select count(*) into vCount from v$cell;
 if ( vCount > 0) then

SOLUTION

This is due to a missing grant.

To allow the package to be valid run the command below ss sys user,


SQL> GRANT SELECT ON V_$CELL TO APPS;

Wednesday, July 16, 2014

hub-and-spoke planning single plan ASCP

Oracle® Advanced Supply Chain Planning enables you to run holistic plans that span long term aggregate planning to short term detailed schedules, multiple manufacturing processes (lot based, process, discrete, configure-to-order, and project based), and all organizations across a virtual supply chain. 

As a single solution for distribution, supply chain, and manufacturing planning, it is based on one supply chain model, one planning engine, and one setup. 

Its flexible configuration, however, enables you to define different models that can co-exist (hub-and-spoke planning; single plan) and evolve as your organization grows without requiring re-implementation. 

Extensive defaulting logic, paired with a productivity enhancing UI and strong exception management, enables planners to quickly use the tool to make their planning decisions.

PS Does not snap shot Alternate Resource For Firmed Batches

On : 12.1.3.8 version, Anything not covered by other codes

ACTUAL BEHAVIOR
---------------
Find that the alternate resource is not present in Production Scheduling (PS) for firmed OPM Batches

EXPECTED BEHAVIOR
-----------------------
Expect to see the alternate resources present in PS

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1- Define Alternate Resource for a certain Resource- Item
2- Create Firmed Batch on that Item
3- N/A
4- Run Data Collection
5- Run Production Scheduling Schedule (Without ASCP Plan Reference)

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot manually assign alternate resources in PS for OPM firmed batches


CAUSE

The alternate resource for batches that are Firmed at the header are not collected into ASCP and hence this data is not available to PS. This is the correct functionality as it is a positive user action to firm the batch header, without this action the alternate resource is collected into ASCP and is available in PS
 l


SOLUTION

To implement the solution, please execute the following steps:

1. Go into the responsibility: Production Supervisor

2. Navigate to Batches

3. Do not set the batch header as firmed or create the batches from ASCP/PS and firm the resources without firming the header 

Getting error message "gme_gmf_wip_acct_issue" when cancelling batch

When attempting to cancel a batch the following error occurs.

GME_GMF_WIP_ACCT_ISSUE_CONT


STEPS:
1. Production Supervisor > Batches >Cancel batch

CAUSE

Batches having no transaction should not give any warning / error when canceling such batch.

In GMF_BATCH_VALIDATIONS.check_cancel_batch cursor Min_max_trans_date would always get a row due to use of min and max function even when transactions do not exist. Thus cursor not found check needs to be replaced by if min and max dates are null. This would be the case when there are no transactions.

Solution :

Apply Patch

To implement the solution, please execute the following steps:

1. Download and review the read me and pre-requisites for R12.0.x Patch 14627037

                                                                            R12.1.x Patch 16777853
2. Ensure that you have taken a backup of your system before applying the recommended patch.
3. Apply the patch in a test environment.
4. Confirm the following file versions:
     R12.0.x      GMFBCHVB.pls 120.0.12000000.5

     R12.1.x      GMFBCHVB.pls 120.2.12010000.4
You can use the commands like the following:

strings -a $GMF_TOP/patch/115/sql/GMFBCHVB.pls |grep '$Header'
5. Retest the issue.
6. Migrate the solution as appropriate to other environments.

Retrieving Previously Saved Production Batch Error FRM-40735: POST-QUERY trigger raised unhandled exception

Cannot retrieve a previously saved batch.  Entering Material Details or Line Allocations on the batch errors:

FRM-40735: POST-QUERY trigger raised unhandled exception ORA-04062
ORA-04062: signature of package 'APPS.GMIVDBL' has been changed
ORA-01403: no data found

The Navigation Path is:
Production Supervisor>Create Document
Production Supervisor>Batches
(B)Material Details>(B)Line Allocations

CHANGES

Applied OPM 11i Family Pack I (2216258)

CAUSE

An attempt to execute a stored procedure to serve an RPC stub was made, which specifies a timestamp/signature that is different from the current timestamp/signature of the procedure.

SOLUTION

Recompile forms, PLLs and objects in APPS schema using adadmin utility to pick up the new timestamp/signature.

Monday, July 7, 2014

Find Invalid Objects in Oracle DBA

An Simple Sql Script can help you to Find all the Invalid Objects

select count(*) from dba_objects where status = 'INVALID';


If the count is large, proceed with step 5.
Otherwise, proceed with step 9

 Compile Invalid Packages
adadmin
Compile/Reload Applications Database Entities menu
Compile APPS schema

Re-create Missing Grants/Synonyms
adadmin
Maintain Applications Database Entities
Re-create grants and synonyms for APPS schema

Validate APPS Schema
adadmin
Maintain Applications Database Entities
Validate APPS schema

Check the output of Validate APPS schema (in APPS.lst)
Make sure there are no invalid objects and no missing grants/synonyms
If there are you can repeat the above steps

Check for the number of invalid objects (should be minimal)


Sunday, June 22, 2014

Discrete Job Statuses - ORACLE R12

Job and Repetitive Schedule Status Changes

Statuses describe the various stages in the life cycle of a job or repetitive schedule. Statuses are either user or processing controlled. Processing controlled statuses are updated based on the progress and outcome of concurrent processes. User controlled statuses can be updated by the user or are changed based on events such as job or schedule completion.
Some status changes are allowed while others are not. Some status changes are conditional. For example, you cannot change jobs and schedules from Released to Unreleased if there are net issue, move, resource, completion, or scrap charges associated with them. You also cannot unclose a job that is linked to a sales order or that was closed in a now closed accounting period.

Change To USER status From USER StatusUnreleasedReleasedCompleteComplete-No ChargesOn HoldCancelledClosed
UnreleasedN/AYesYesNoYesYesYes
ReleasedCondN/AYesNoYesYesYes
CompleteCondYesN/AYesYesYesYes
Complete - No Charges (DIS)NoNoYesN/ANoNoYes
Complete - No charges (REP)NoNoNoN/ANoNoN/A
On Hold (DIS)CondYesYesNoN/AYesYes
On Hold (REP)CondYesYesNoN/AYesYes
Cancelled (REP)NoNoNoNoNoN/AN/A
Cancelled (DIS)CondYesYesYesYesN/AYes
Pending - Mass Loaded (REP)YesYesYesNoYesYesN/A
Pending Bill Load (DIS)NoNoNoNoNoNoNo
Failed Bill Load (DIS)YesYesNoNoYesNoYes
Pending Routing Load (DIS)NoNoNoNoNoNoNo
Failed Routing Load (DIS)YesYesNoNoYesNoYes
Pending Close (DIS)CondYesYesYesYesYesYes
Failed Close (DIS)YesYesYesNoYesYesYes
Closed (DIS)YesYesYesNoNoNoN/A