Get Example source ABAP code based on a different SAP table
• IN LOCAL MODE READ ENTITY • IN LOCAL MODE READ ENTITIES • IN LOCAL MODE READ ENTITIES OPERATIONS • IN LOCAL MODE MODIFY ENTITIES OPERATIONS • IN LOCAL MODE MODIFY ENTITY • IN LOCAL MODE MODIFY ENTITIES
ABAP_EML - IN LOCAL MODE
ABAP_SYNTAX ... IN LOCAL MODE ...
What does it do? The addition is used to exclude feature controls and authorization checks. It can be added to the following EML statements:
READ ENTITY, ENTITIES
MODIFY ENTITY, ENTITIES It can currently only be used in RAP BO implementations for the particular RAP BO itself, i. e. not for other RAP BOs. That means IN LOCAL MODE can only be used for this RAP BO's implementation classes in the behavior pool or other classes that are called from those implementation classes (for example, legacy code or other reused logic contained elsewhere). The reused logic contained elsewhere cannot be referred to by RAP statically. In that case, a warning is displayed in ADT. Yet, at runtime, there will not be an issue if this logic is called via the implementation classes of this RAP BO. If the reused logic is not called from the implementation classes of this RAP BO or it is called indirectly, a short dump is the consequence. For example, if the logic is called from a report (the implementation class of the RAP BO is not called at all) or if, at runtime, another RAP BO is meanwhile involved. Example use case: A field to display the booking status of a trip on an SAP Fiori UI is specified as readonly in a BDEF. Hence, it cannot be modified by a user on the UI directly. For example, the status of a trip is set to and displayed as not booked. A button on the UI triggers an action to book the trip. With clicking the button, the status gets changed and booked is displayed. To enable this, the underlying modify operation with the action to be executed in the ABP has the addition IN LOCAL MODE that ignores the feature control.
