0% found this document useful (1 vote)
298 views3 pages

SAP Note

This SAP note describes an issue where executing certain ABAP development objects causes a dump with the message "SYSTEM_ABAP_ACCESS_DENIED" in SAP S/4HANA on-premise systems. These objects are on a "blocklist" because they are not compatible with or licensed for S/4HANA. The note provides instructions for SAP support to clear specific objects on a case-by-case basis using transaction ABLM_MODIFY_ITEMS to allow them if approved. It also references other notes about particular blocked transactions.

Uploaded by

damar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (1 vote)
298 views3 pages

SAP Note

This SAP note describes an issue where executing certain ABAP development objects causes a dump with the message "SYSTEM_ABAP_ACCESS_DENIED" in SAP S/4HANA on-premise systems. These objects are on a "blocklist" because they are not compatible with or licensed for S/4HANA. The note provides instructions for SAP support to clear specific objects on a case-by-case basis using transaction ABLM_MODIFY_ITEMS to allow them if approved. It also references other notes about particular blocked transactions.

Uploaded by

damar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SAP Note

2249880 - Dump SYSTEM_ABAP_ACCESS_DENIED caused through Blocklist Monitor in SAP S/4HANA on


premise
Component: CA-EPT-TAS (Tools and Services in BS Foundation), Version: 15, Released On: 16.08.2021

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

Executables might be...

Transactions (TRAN => Type 'T'

Function Modules (FUNC) => Type 'C'

Reports (PROG) => Type 'P'

Class Methods (METH) => Type 'M'

Form Routines (FORM) => Type 'F'

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

Reason and Prerequisites


Pre-requisites: Ensure you are using SAP S/4HANA on premise Edition 1511 SP01 and following Support Packages (SPs) or Releases

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.

In such cases, please do the following:

Consult with development support


Raise a ticket on the component of the blocklisted object concerned and inquire with the development support of SAP S/4HANA whether the particular object is
blocklisted and how customer may use it according to the SAP whitelist or dedicated note
Based on the approval of development support via the ticket, you get a clearance to proceed according to the instructions mentioned below

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'

Retry your application which caused the initial dump.

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).

Start transaction SE38 and enter program 'ABLM_MODIFY_ITEMS'


Based on the given information of the former modifcation, select via F4 the corresponding Type (TRAN, FUNC, PROG, METH, FORM)
For TRAN and PROG please enter as 'Name' the executable mentioned as 'Object' in the fromer Dump
For FUNC and METH please enter as 'Name' the executable mentioned as 'Procedure' in the fromer Dump and as 'Main' the executable mentioned as ''Object' in the
former 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 <Modified to be allowed for usage by user...>
Go back (F3) and select the appropriate Radio Button 'Restore once modified entries'
Deselect the checkbox for 'Testmode'
Execute (F8) the report - this might take between 5sec and 180sec
The report shall show the original state of the executable and the general message 'Modification is effective'

Retry your application - this shall now create again a dump.

Manual Activities

Software Components

Software Component And subsequent

S4CORE X

This document refers to


SAP Note/KBA Title

2933993 Enable Report ABLM_MODIFY_ITEMS to reset local modificaitons

2753393 Erroneous entry on S4 blacklist

2476734 Runtime error SYSTEM_ABAP_ACCESS_DENIED

2408693 Override blocklist of Remote Enabled Function Modules

2234168 Blocklist Monitor not started or has to be restarted - message P013(TG)

This document is referenced by


SAP Note/KBA Title

2456442 VA06 giving shortdump SYSTEM_ABAP_ACCESS_DENIED

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

2514366 BAPI order simulation for items with variant configuration

2711702 MCGD transaction is blocklisted* in S/4HANA

2621070 SPRO | SM30 | SYSTEM_ABAP_ACCESS_DENIED

2619000 SAP RU-FI: J3RXMLEXP cannot read data using J_3RFBS_ALL in S/4HANA 1610, 1709

2591412 MSK4: You receive SYSTEM_ABAP_ACCESS_DENIED short dump

2585772 S/4HANA - Function module CONVERSION_EXIT_MATNV_OUTPUT usage

2554785 Upon opening transactions VKM2/VKM3 in an SAP S/4HANA system either a short dump or an error message occurs

2548673 S/4 HANA: SYSTEM_ABAP_ACCESS_DENIED SAPLMGV_SELOPT_INTERFACE

2504510 S/4HANA: MMSC SYSTEM_ABAP_ACCESS_DENIED

3129707 Transactions MCH8 dump with SYSTEM_ABAP_ACCESS_DENIED

2541353 Blocklisted transactions VA05N and VA06

2933993 Enable Report ABLM_MODIFY_ITEMS to reset local modificaitons

2897424 Erroneous entry in blacklist for SAP S/4HANA on premise

2746817 WTY: Dump "SYSTEM_ABAP_ACCESS_DENIED" occurs on executing action A100

2658935 Dump SYSTEM_ABAP_ACCESS_DENIED for transactions VMG1, VMG2, VMG3, VMG4, VMG5

2658391 Blacklisted Transaction need to be released for Customer Usage

2633062 Transaction /SCTM/ZONES_DELETE: Short dump SYSTEM_ABAP_ACCESS_DENIED in S/4HANA 1709

2627247 Search help BUHI_TREE_SEARCH_TERM3 dumps with SYSTEM_ABAP_ACCESS_DENIED


2562808 Runtime error SYSTEM_ABAP_ACCESS_DENIED

2518816 Re-Enabling Tr. MMSC in S/4 HANA 1610 FPS02 release onwards

2502852 Dump SYSTEM_ABAP_ACCESS_DENIED in MM60 transaction in SAP S/4HANA

2482446 Define Number Ranges Customizing Activity Is Not Maintainable on S/4HANA

2442246 Dump SYSTEM_ABAP_ACCESS_DENIED caused by report RV76A001

2421015 Runtime error SYSTEM_ABAP_ACCESS_DENIED

2410678 Transaction MDM_CLNT_EXTR dumps with SYSTEM_ABAP_ACCESS_DENIED

2341343 Adjustment of incompatible RFC Module CIF_DELTA3_GET_MATWERK

2341593 Remove Remote Function Modules from Blocklist

2274307 BDBG dumps as the transaction is blacklisted in SAP S/4HANA, on-premise edition 1511

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy