Archive

Archive for the ‘ERP’ Category

Oracle ER/Bug 16306627: WIP IS ISSUING ASSEMBLY PULL COMPONENTS WHEN SCRAP IS ENTERED

April 7, 2013 Leave a comment

The following is entered as an enhancement request at Oracle for their E-Business R12 product.  I have tried to convince Oracle to categorize this as a bug, but have not had any luck.  If you have encountered a similar situation, please log an SR and add yourself to this “ER” and request that it be changed to a bug.

We [Emerson] have an assembly with a BOM where a component is inherited from a phantom assembly into the main assembly as an assembly pull supply type component on operation SEQ 1. The final assembly’s routing begins with operation SEQ 400. When a job is made, the component gets tied to operation SEQ 400. When a WIP move is made to the scrap step of the first operation (400), the assembly pull component is taken out of inventory.

This functionality is described as correct as per WIP User guide.

Oracle® Work in Process User’s Guide Release 12 Part No. B31092-01

When you move assemblies into the Scrap intraoperation step of an operation that has assembly pull components assigned to it, the system backflushes these components and all assembly pull components at prior operations.

This functionality does not seem to be correct. If a component is “assembly pull”, a completion takes it out of inventory at the end of the job. This means the component is acting as assembly pull for a completion, but operation pull for scrap.

If the goal is to take out inventory of assembly pull components when an assembly is completed, than it should not be tied to an operation.

Read more…

Fixed: Adding an Asset Group (Oracle EAM)

December 6, 2012 Leave a comment

I have been testing Oracle Enterprise Asset Management (EAM) at work to check if it can replace one of our legacy systems.  When testing I came across an error that took me days to solve.  I finally found the problem!

Conditions

  • Oracle Enterprise Asset Management (EAM) in Oracle E-Business suite R12
  • Adding a new Asset Group

Symptoms

  • Receive error on save
Insert Procedure Failed with the following error message: 12746302

Problem

  • Oracle was creating a new item based on the @Asset Group template
  • Profile option INV: Default Primary Unit of Measure was set to NULL

Solution

  1. Add a UOM of EA (Each) to the @Asset Group item template
  2. [or] Add EA (Each) as the value for the profile option  INV: Default Primary Unit of Measure

For business reasons, we cannot have a default UOM, so we will likely choose option 1.

BI Publisher Provides Our Organization Extreme Agility

September 25, 2012 Leave a comment

A year and a half ago, our company embarked on a project to run Oracle E-business R12. Part of that process included a manufacturing migration from our legacy systems, and the other part included a migration of financial modules from Oracle 11i.  Included in the 11i financial modules was Accounts Payable, thus our Payment process needed to be migrated to R12.  One of my responsibilities was to create the payment output for the R12 system.  Payments in Oracle R12 are rendered with BI Publisher, an Oracle tool I became very skilled with while working on the AP project.  Although limited, BI Publisher has to be one of the most powerful technologies Oracle provides and has allowed our IT organization to become more agile.

From what I heard, it took the previous business analyst two years to get a check printed in the 11i production system, starting at the beginning of that project.  The R12 Payment processing seemed like a daunting task.  But I was up for the challenge and eager to enhance my skill set.

Within the first day of working on the payment output, I was able to get a check printed out of our test system.  Two weeks later I had a check ready to send to our bank for validation.

Although my manager was impressed, he still had some doubts. I have a feeling he was thinking around the lines of, “this is too good to be true; how can someone get a check ready for approval so fast, when took so long previously?” Whatever his thinking was, the bank validation had the ability to halt my swift progress right in its tracks.

Read more…

Fixed: Oracle BI Publisher Template XLF Translation File Upload Error

July 3, 2012 Leave a comment

I have been working on BI Publisher templates and the XLF Language Translations at work. I found a nice bug where a user uploads a XLF template translation and Oracle gives an Error that does not match the actual problem that caused the error.

Conditions

  • Oracle BI Publisher or XML Publisher module in Oracle E-Business suite R12
  • XLF Template Language Translation files

Symptoms

  • BI Publisher gives error as seen below
  • Unable to upload XLF Translation file
The uploaded translation file is invalid. It should specify a valid target language and territory. Please verify that the file is in the correct format.

Problem

  • Original Oracle Translation file exported specifying UTF-8 encoding
  • Edited translation files actually use ISO-8859-1 encoding

Solution

  • Change XLF Specified Encoding from utf-8 to ISO-8859-1

Refreshing Oracle Self Service Menus and Home Screen

April 6, 2012 Leave a comment

When implementing our RBAC (Role Based Access Control) security model in Oracle, I found it quite irritating when the self service pages would not update to include the newly applied Roles and granted security functions.  Here is the solution I found to refresh the web based pages so they they reflect the user’s newly applied security.

Problem

  • “XXX is not a valid responsibility for the current user” error
  • Not seeing updates from newly assigned or revoked Roles or Responsibilities
  • Changes in self service pages driven by new or changed configurations

Solution

  • Assign yourself the “Functional Administrator” Responsibility.
    • This is a self service responsibility; it must be assigned BEFORE you have the problem which you are trying to solve.
  • Click the Core Services Tab
  • Click the Caching Framework Menu (top)
  • Click the Global Configuration Menu (left)
  • Click the Clear All Cache Button
  • Click the Yes Button

 

Component Backflush with Oracle MTL Transaction Interface Table

September 22, 2011 13 comments

Recently, at work, we noticed the Work Order-less completions inserted into our MTL_TRANSACTIONS_INTERFACE table were not spawning component backflush transactions. It was quite the mystery to us, as they had been working in Oracle 11i (11.5.10).  At some point during our migration to R12 (12.1.3) the backflush transactions had stopped.  We searched Oracle’s documentation, support knowledge base, and all over the internet.  We couldn’t find a solution.

One of my colleagues got in touch with someone she used to work with.  They were able to provide a private API: APPS.wip_flowUtil_priv.  My colleague tried the API call explodeRequirementsToMTI and was able to get the components to backflush.  We thought all was well.

However, upon further testing, I noticed something strange.  The original Assembly was getting stuck in the interface.  And when resubmitted, I saw both the assembly and another round of components getting transacted.  What was going on?

Further testing provided me with the answer: the originally inserted assembly record was getting slightly altered by the material transaction worker before getting marked in error.  Altered to a point which would spawn component backflush transactions if marked for processing and then processed.  I tried inserting a fresh assembly record into the MTL_TRANSACTIONS_INTERFACE table with the updated fields and was able to get the components to backflush, automatically, without any errors.

We now have a functioning R12 Work Order-less completion interface which inserts assembly completion records into the MTL_TRANSACTIONS_INTERFACE table.  Records which are correctly formed and spawn component issue (backflush) transactions when processed by the material transaction manager (Process transaction interface).

These are the two fields that were changed by the transaction manager:

OPERATION_SEQ_NUM from -1 to NULL
TRANSACTION_BATCH_SEQ from NULL to 1

Below is the insert statement we are using, with Oracle 12.1.3 changes noted.

Read more…