SAP Note
SAP Note
Symptom
A callable ABAP development was tried to be executed, which is registered as a so called Blocklist Item.
Blocklist items are executable development objects like Transactions, Function Modules, Reports, Class Methods or Form Routines. They have been registered inside the ABAP
kernel to perform a dump because
they are not (or not yet) adjusted to the prerequisites of changed data models in S/4HANA and may create disruptive data
they are not part of the Feature Scope Description and by that not licensed for use by customer
they are not decoupled from the S/4HANA Code base and will be deleted at a later point in time
They are also part of the Simplification List and Simplification Database where you'll find further information about the reason of the deactivation of the executable.
Other Terms
Simplification List, Simplification Database
Also, please note that the blocklisted objects belong to SAP and SAP has blocklisted them (either temporarily or permanently) in SAP S/4HANA releases due to reasons mentioned
above, and one among them is the fact that the functionality is not compatible with SAP S/4HANA architecture or other reasons, the functionality is no longer required and/or
supported in the related application/product under SAP S/4HANA.
In case an object is not set forth in the SAP S/4HANA Feature Scope Description, the customer has no license right to use the object.
SAP may allow or whitelist a temporarily blocklisted objects and SAP may allow its general usage by removing them from the blocklist in any future support package or – prior to the
provisioning of an support package - through a dedicated note where compatibility or enablement has been downported.
Solution
After clearence through SAP, please proceed as follows:
This is to be done for each system (based on System-Id SID) in one client of your choice through a system user which has the authorization S_ADMI_FCD (System Authorizations).
Ensure that the programm 'ABLM_MODIFY_ITEMS' is on latest state as mentioned in note 2933993
Start transaction SE38 and enter program 'ABLM_MODIFY_ITEMS'
Based on the given information of the Dump, select via F4 the corresponding Type (TRAN, FUNC, PROG, METH, FORM)
For TRAN and PROG enter as 'Name' the executable mentioned as 'Object' in the Dump
For FUNC and METH enter as 'Name' the executable mentioned as 'Procedure' in the Dump and as 'Main' the executable mentioned as ''Object' in the Dump
Execute (F8) the report first in 'Testmode' - this is the default and keep the Radio Button on 'No Action | Check Entry'
Check whether the Blocklist Entry has been found and the current status is <Blocked for internal usage>
Go back (F3) and select the appropriate Radio Button 'Allow Entry for Internal Usage'
Deselect the checkbox for 'Testmode'
Execute (F8) the report - this might take between 5sec and 180sec
The report shall show the correct state of the executable and the general message 'Modification is effective'
Procedure to restore the original blocking of executables after a former clearance through SAP and its Modification:
This is to be done for each system (based on System-Id SID) in one client of your choice through a system user which has the authorization S_ADMI_FCD (System Authorizations).
Manual Activities
Software Components
S4CORE X
3266325 Error or dump with transaction OVFI when maintaining payment guarantee schema
2840842 After running task list SAP_FIORI_CONTENT_ACTIVATION more (hundred) system dumps are written per day
2619000 SAP RU-FI: J3RXMLEXP cannot read data using J_3RFBS_ALL in S/4HANA 1610, 1709
2554785 Upon opening transactions VKM2/VKM3 in an SAP S/4HANA system either a short dump or an error message occurs
2658935 Dump SYSTEM_ABAP_ACCESS_DENIED for transactions VMG1, VMG2, VMG3, VMG4, VMG5
2518816 Re-Enabling Tr. MMSC in S/4 HANA 1610 FPS02 release onwards
2274307 BDBG dumps as the transaction is blacklisted in SAP S/4HANA, on-premise edition 1511