Ansicht
Dokumentation

ABAPMODIFY_ENTITY_ENTITIES - MODIFY ENTITY ENTITIES

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

MODIFY ENTITY, ENTITIES

MODIFY ENTITY, Short Form

1. MODIFY ENTITY $[IN LOCAL MODE$|PRIVILEGED$] bdef operations $[response_param$].

MODIFY ENTITIES, Long Form

2. MODIFY ENTITIES OF bdef $[IN LOCAL MODE$|PRIVILEGED$]
           ENTITY bdef1 operations
          $[ENTITY bdef2 operations$]
          $[...$]
          $[response_param$].

MODIFY ENTITIES OPERATIONS, Dynamic Form

3. MODIFY ENTITIES $[IN LOCAL MODE$| PRIVILEGED$] OPERATIONS op_tab $[response_param$].

Effect

Used to perform RAP modify operations on RAP BO instances. This includes standard operations (CREATE, CREATE BY, UPDATE, DELETE) and nonstandard operations (actions) using the keyword EXECUTE.

The following variants of the MODIFY statement can be used to modify RAP BO entities:

• MODIFY ENTITY, Short Form

The short form of the MODIFY statement allows modifying instances of a single entity.

• MODIFY ENTITIES, Long Form

The long form of the MODIFY statement allows modifying instances of multiple entities.

• MODIFY ENTITIES OPERATIONS, Dynamic Form

The dynamic form of the MODIFY statement allows collecting multiple instances to be modified in multiple entities in one MODIFY statement.

Notes

• RAP modify standard operations do not return result parameters, whereas non-standard operations do so. The changed data can be read via a subsequent READ statement.

• RAP BO instances can only be modified if several conditions are met. For example, a modification can be prevented depending on certain specifications in the BDEF, among them control characteristics like (global or instance) authorization and feature control, locking, ETag or prechecks. See more detailed information on the mentioned topics in the Development guide for the ABAP RESTful Application Programming Model, section Business Object.

• If ABAP EML modify statements are used outside of behavior pools, for example, in ABAP programs, a COMMIT ENTITIES statement is necessary to persist data to the database. If the statement is not provided, there would not be any effect on the database because the modify operations are only performed on the transactional buffer. Hence, a manual triggering of the save sequence is required. This is valid for all modify operations. Note that RAP supports the established SAP LUW concept that incorporates COMMIT WORK. In RAP, COMMIT ENTITIES basically includes COMMIT WORK and provides additional information.

• When executing independent modify requests, there is no dedicated processing sequence. However, the processing sequence is relevant if the modify requests are dependent, for example, when using %cid or %cid_ref or in case of create-by-association operations that can be dependent on a previous operation. To ensure the processing sequence when executing independent modify requests, it is recommended that separate EML statements are used. In the interest of a better performance, requests should preferably be executed in a bundled way.
  
  

• The example - MODIFY, Variants demonstrates the different variants with a simple managed RAP BO.

• For more examples, see Examples for ABAP EML MODIFY.

• The example Example for RAP Handler Methods demonstrates various RAP handler methods within a RAP handler class using a simple unmanaged RAP BO that is draft-enabled. It includes ABAP EML requests with MODIFY in a RAP consumer and provider.

General Data in Customer Master   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 7301 Date: 20240419 Time: 153225     sap01-206 ( 82 ms )