Message type: E = Error
Message class: ME_RELCHK - Check Customizing for Release Strategy
Message number: 018
Message text: Initial status of release strategy &1 not "blocked"
A <DS:GLOS.352AC0A188E65CD5E10000009B38F974>release indicator</>
"Blocked" must be assigned to the initial status of each
<DS:GLOS.3526BFF3AFAB52B9E10000009B38F974>release strategy</>.
This indicator is missing from release strategy &V1& of release group
&V2&.
As a rule, a purchasing document must first be released before it can
be processed further. When you create a purchasing document, a release
indicator which blocks the latter from further processing must
therefore initially be assigned to the document.
If necessary, define a release indicator for the status of this release
strategy.
Error message extract from SAP system. Copyright SAP SE.
ME_RELCHK018
- Initial status of release strategy &1 not "blocked" ?The SAP error message ME_RELCHK018 indicates that the initial status of the release strategy for a purchase requisition or purchase order is not set to "blocked." This error typically occurs during the release (approval) process of a purchase requisition or order when the system checks the release strategy conditions.
Cause: The error is caused by the release strategy configuration in the SAP system. Specifically, it means that the release strategy defined for the document does not have a status that allows it to be processed further. The initial status should be set to "blocked" for the release strategy to work correctly.
Solution: To resolve this error, you can take the following steps: Check Release Strategy Configuration: Go to the transaction code SPRO (SAP Reference IMG). Navigate to Materials Management > Purchasing > Purchase Requisition > Release Procedure > Define Release Procedure for Purchase Requisitions. Check the release strategy settings for the relevant document type. Ensure that the initial
Get instant SAP help. Sign up for our Free Essentials Plan.
ME_RELCHK017
Release indicators missing for statuses of release strategy &1
What causes this issue? You have not maintained <DS:GLOS.352AC0A188E65CD5E10000009B38F974>release indicators</> for all release statuses....
ME_RELCHK016
No release codes assigned to release strategy &1
What causes this issue? You have not assigned any <DS:GLOS.3526BFF1AFAB52B9E10000009B38F974>release codes</> tp <DS:GLOS.3526BFF3AFAB5...
ME_RELCHK019
Final status of strategy &1 not "Released"
What causes this issue? A <DS:GLOS.352AC0A188E65CD5E10000009B38F974>release indicator</> "Released" must be assigned to the fin...
ME_RELCHK020
Assignment of release codes to strategy &1 faulty
What causes this issue? When you assign <DS:GLOS.3526BFF1AFAB52B9E10000009B38F974>release codes </> to your <DS:GLOS.3526BFF3AFAB52B9E...
Click on this link to search all SAP messages.