sap mm release strategy deletion
DESCRIPTION
SAP MM Release Strategy DeletionTRANSCRIPT
SAP MM Release strategy deletion
SAP MM Release strategy deletion
INDIA\SAP\[email protected] a Purchase Requisition (PR) using t-code ME51 is created and saved, a release strategy to the PR is assigned..
When the release strategy assigned to the PR for releasing is checked, a wrong release code in the release-to-date is found, which is not related to the release strategy.Observation and AnalysisThe configuration of the release strategy 24 had been checked and the wrong release code (15) had not been found.
The table - T16FS - Release Strategies had been checked and there were no wrong release codes found.
But in table - T16FV - Release Pre-requisites, the wrong release code (15) was found and the release strategy was deleted directly without following the sequence; hence an inconsistency has been created in table T16FV.It was deleted as the release strategy earlier was customized at Header level and later was changed to Item level. When it was directly corrected in customizing, it did not update the tables properly. Hence in tables T16FK, T16FV, T16FS, T16FC and T16FG, there will be entries from previous customizing settings (for example, old release groups) that were indeed deleted from the customizing settings, but not deleted from the tables. This creates an inconsistency.
Solution:
Temporary solution:
1. The correct solution may be deleting these release strategies and transporting to the production client, checking all tables for clearing the data, recreating and then transporting to the production system. This is a long but perfect method.
2. If there are very few inconsistencies and we have clearly identified these, table level correction can be done. This is a short but not a much recommended method. This should be done strictly in SAP's control.Permanent solution:
To avoid inconsistency during Release strategy deletion, SAP has recommended a procedure to follow:1. Delete the release strategies2. Delete the release indicators3. Delete the release codes4. Delete the release group5. Delete the class (Transaction CL02), provided a new one has been created for the new release strategies.
Further use Transaction SE16 to check if the entries in the tables mentioned above were deleted. Execute the report in Customizing (Transaction OMGQCK or OMGSCK) and ensure that the system does not display any red traffic lights.SAP MM Release Strategy Deletion
07/03/2008
Tata Consultancy servicesInternal use Page 2 of 3