Symptom
- Release of transport request is blocked due to the MAPPING XXX.
- Release of BCP prevented by external check.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open App "Manage Your Solution".
- Click the button "Proceed to deploy".
Cause
Release of the change project is blocked due to external checks - G/L account renumbering application has items which are not in released or rejected status.
Resolution
- Open App "Manage Your Solution".
- Navigate to "Configure your solution" tile.
- Click configure icon on the SSCUI 150000.
- Please make sure that all the mapping is in "Released" or "Rejected" status. Options are described below.
a. Reject Mapping: This option should be selected if you DO NOT want to convert the G/L Accounts in your system now, and proceed with BCP release in Q-system.
b. Start Conversion: This option should be selected, if you want to convert the G/L Accounts in your system and release your G/L Account changes as well with current BCP project. If you are selecting this option, then your system would be unavailable for around 2-4 hours, where no business users will be allowed for login and once your system is back up and running after completion of conversion then you should release the BCP project.
To take and perform the actions accordingly you need to go to FIORI app "Convert renumbered G/L Accounts" which should be available for the users having business catalog-SAP_CA_BC_CNV1_PC assigned. This catalog is delivered as standard business role template SAP_BR_ADMINISTRATOR.
See Also
Keywords
S4_PC, S4HC, SV-CLD-FRM-INF, proceed to deploy, release, blocked, mapping, change project, external check, convert G/L, renumbering , KBA , SV-CLD-FRM-INF , Implementation Framework Infrastructure , Problem