| CONDITION | OBSERVATION |
| SCENARIO-1 | | |
| Release Procedure configured with document type. | Configure release strategy for the document type, Create PO with the same document type and save. Remove the configuration made for Release strategy and view the PO which had the Release strategy. | The release strategy tab was not found in the header detail of PO. When tried to release the PO with ME29N t-code, system gives the message as purchasing document cannot be released. During MIGO for the same Purchase order the system shows a message as purchase document not yet released. Again went to edit mode of Purchase order no and without making changes the PO was saved, the system gave a message as no data was changed. Once again went to MIGO and tried to do GR with the PO number, the system again gave the same message as Purchase document not yet released. Tried to change the PO quantity and created GR against the same PO, Still the system shows the same message as Purchasing document not yet released. |
| De-activating and activating Release Procedure | With the continuation of the previous step activate Release procedure once again | in the previous step we have configured the release strategy and created PO with release strategy tab, But when the release strategy was made inactive, The same PO didn’t had the release strategy tab. Once again the release strategy was made active and it was observed that the release strategy appeared again. In the Previous step GR for the PO was not able to possible, the system was giving error message as Purchasing document not yet released. But after activating the Release strategy the system was able to recognize the PO and it was posted with the following material document. |
| Creation of PO before customizing Release Strategy | PO is created in the system without Release Strategy, Release strategy is configured later on and the PO status is checked | The PO was Created in the system without Release strategy, The Release Strategy was configured later on and the PO was taken with using T-code ME23N, The PO didn’t had the Release Strategy Tab, GR was possible against the PO. The PO was taken in the edit mode and the quantity for the same PO was changed, after selecting the check option in PO it was found that the Release Strategy tab came automatically. For the same PO without releasing, it was not possible to do GR. |
| CONCLUSION | All PO should be released before removing Release Strategy from the system, Because once Release Strategy has been removed, The Release Strategy Tab gets deactivated in the PO header Tab and the system will not allow the PO to do GR without releasing it. | |
| SCENARIO-2 | | |
| Three Release Codes are maintained for a Release Strategy in which One release code is removed and saved-Release Strategy activated on the Document type | Release Strategy is configured in the System and PO's are created with release strategy. Three codes are maintained in the release strategy of which one Code is deleted, The behavior of PO's are observed | The PO's which were having three codes earlier have now two codes in the release strategy tab of the header detail. The Po can be released with the T-code ME29N and GR can be done against the PO. |
| SCENARIO-3 | | |
| In the Classification of Release Strategy Characteristics value is made Blank | Release Strategy is configured in the system and PO's are created with release Strategy in the header tab of PO. Classification of Release Strategy Characteristics value are made blank. | The PO's created previously will not have not have any changes in their release strategy tab of their header detail. The PO's are able to release using T-code ME29N and GR is also possible for the released PO's, if in the change mode of the respective PO's any changes are made then the PO will not have the release Strategy Tab in their Header detail. |
| SCENARIO-4 | | |
| Another Characteristics is created and is assigned it to the Class | Another Characteristics with table name WERKS with referring Plant has been created and is assigned it to the class, Release Groups and release codes are created. | Previous Po created with only one characteristics release strategy will not have any effect. The previous PO's can be released and GR can be made against those PO's. The newly customized release strategy will trigger on PO which satisfies the combination. If the Previous PO are taken in the Edit mode and changes are made on it, then it will take the new Release strategy into consideration and the newly created release codes will be applied on it. |
| SCENARIO-5 | | |
| The old characteristics which was assigned to the class is deleted. | The old characteristics will be deleted from the class and the release strategy is assigned with the new characteristics. | There wont be any effect on the previous PO's. The Po's can be released and GR can be done on the PO's. If changes are made on the PO it will trigger the Current Release Strategy. |
| | |
| NOTE:- | When ever we configure Release Strategy it is always suggested to create a multiple combination, so that it wont affect the contract, RFQ and Scheduling agreement. | |
| CONCLUSION | Problem occurred during Setting Release Indicator % values. Tried different scenarios with settings different Release Indicators. All Conditions worked fine but % values with the indicator i.e. the tolerance didn’t work out. | |
