Problem with Edit Text Entered on Steps on Recipe Details
(Doc ID 1951921.1)
Last updated on MARCH 08, 2017
Oracle Process Manufacturing Product Development - Version 12.1.3 and later Information in this document applies to any platform.
On : 12.1.3 version, Product Development Recipes
ACTUAL BEHAVIOR --------------- There is a problem with trying to enter Edit Text for recipe step data (gmd_recipe_routing_steps). The Steps section of the Recipe form pulls data from fm_rout_dtl unless you make a change, and then the change is stored in gmd_recipe_routing_steps. So if you enter text on a step on a recipe that has not previously had a change made, you see the paragraphs set up for fm_fout_dtl, and the text you enter is stored in fm_rout_dtl, not gmd_recipe_routing_steps. But now that you have made a change (entering text), this causes a row to be created in gmd_recipe_routing_steps, so when you try to retrieve the text, you are now presented with the paragraphs for gmd_recipe_routing_steps, and so you cannot retrieve the data initially entered (and not only that, but since the text is stored in fm_rout_dtl, text that you initially entered or edited from the recipe actually shows up afterwards on the routing, which is wrong - you should not be able to change the master routing text from the recipe).
The customer has a business need to enter text for steps, and this text is different for the same routing step in different recipes, so it cannot be entered for the routing in fm_rout_dtl, it needs to be entered for the recipe in gmd_recipe_routing_steps. But that cannot be done without first making some kind of change to the recipe step data, such as changing the step qty on the recipe step (and then changing it back since they do not want to change step qty) or entering bogus text first that will go into fm_rout_dtl text (and then show up on the routing itself). The customer has thousands of recipes, so it is not practical to make a bogus change on every recipe step just so that they can then add text to gmd_recipe_routing_steps.
EXPECTED BEHAVIOR ----------------------- The code should realize that if you are entering text for a step on a recipe, that it should be stored in gmd_recipe_routing_steps, not fm_rout_dtl. The code already creates a row in gmd_recipe_routing_steps when you edit text, but that is after it has put the text in fm_rout_dtl. Therefore, when entering text on a recipe step the user should be presented with the paragraphs set up for gmd_recipe_routing_steps, not fm_rout_dtl, and the text should be stored in gmd_recipe_routing_steps.
STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Create a recipe with a routing 2. Click on a step on the Step Quantity tab. 3. Go to Actions > Edit Text. You see the paragraphs set up for fm_rout_dtl. 4. Enter and save text. 5. Retrieve the recipe again and click on the same step. 6. Go to Actions > Edit Text and you now see the paragraphs set up for gmd_recipe_routing_steps.
BUSINESS IMPACT ----------------------- The issue has the following business impact: Due to this issue, users cannot enter text for recipe steps without having to first make a bogus change to the recipe step to create a row in gmd_recipe_routing_steps, and then revert the change.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!