|
Limitations, Restrictions or Patch Requirements
Patch:
1) When attempting to use the recipe API for recipe creation/updates, there are issues with the owner value. The API is inserting the user_id of the person executing the API instead of the value assigned for the owner. (Doc ID 2622010.1).
Please install the patch suggested in the above Doc ID.
(Note: If you have EBS Version 12.2 then you may require to contact Oracle Support in order to obtain the patch. The patch link provided in the above doc for 12.2 may not work and Oracle should give you the working link of the 12.2 patch to download. The 12.1 patch link seems to work correctly).
2) Some customer has noticed that after uploading the Recipe using the loader, if they open the same Recipe on the Standard Oracle EBS Form then without changing any values, the form asks to save changes. That is because of The column RECIPE_YIELD.
Our loader does not utilize the "recipe_yield" field because the field is not visible on standard recipe form, its only in the database table. After investigation, we found that the Oracle Recipe Public API does not retain the existing recipe_yield field value i.e. the API clears the recipe_yield field value.
EBS 12.1: GMD_RECIPES_B table imported recipe_tield column in 12.1. instances via patch #22644544. So EBS 12.1 customers will required to install this patch and the form will stop erroring about the save changes dialog.
EBS 12.2: For 12.2 instances, the patch number is difficult to determine. Please contact More4apps for more info on this. (Note: It is seen that the file: GMDRCP.odf version 120.12.12020000.7 brings the “RECIPE_YIELD” column to the table: GMD_RECIPES_B. There are a lot of patches containing this file.)
Limitations:
1) Due to Oracle API Limitations, some sections are limited to certain transaction types. Such as the Step Quantities can only be updated. Furthermore, Step/Material Association can only be created.
2) The way the Oracle API is structured, only the header level status is printed as Accepted or Error status. There is no possible way to have statuses appear for the lower level sections.
3) Oracle Recipe Public API does not retain the existing “recipe_yield” field value i.e. the API clears the “recipe_yield” field value. If the “recipe_yield” field value is desired, an Oracle SR may need to be filed. For assistance, please feel free to contact More4app.
4) The API allows changing Recipe Status to any of the available status but it restricts updating the status to "Frozen". So, the Recipe Status cannot be changed to "Frozen" via the loader.
5) Users cannot set the Throughput details while creating a new Recipe.
Users first must create a recipe and then download the successfully created recipe in the loader.
This is because the routing step, operations etc. details are not attached to the Recipe until the Recipe is created. Once the recipe is created, all required information for the Organization Details would be downloaded with the recipe download.
6) The API allows changing the Recipe Status to "On Hold" or "Obsolete/Archived", this is able to be passed down to the Validity Rules Status if the current Validity Rules Status is anything other than "New".
i.e. if the Validity Rules Status is "New" then changing the Recipe Status to "On Hold" via the loader does not change the Validity Rules Status "On Hold". The API fails with the error message: "The target status On Hold is invalid for the current status."
Restrictions:
1) To access the Organization Throughput, at least one Plant/Laboratory record is required associated with the Recipe and a routing must be present in the Recipe.
2) The Recipe status must be “New”, “Approved for Laboratory Use” or “Approved for General Use” to edit/change the Organization Throughput section fields. Otherwise, those fields are not updatable.
