Get Example source ABAP code based on a different SAP table
• FROM MODIFY ENTITY • FROM MODIFY ENTITIES • FIELDS, WITH MODIFY ENTITY • FIELDS, WITH MODIFY ENTITIES • SET FIELDS WITH MODIFY ENTITY • SET FIELDS WITH MODIFY ENTITIES • AUTO FILL CID MODIFY ENTITY • AUTO FILL CID MODIFY ENTITIES
MODIFY ENTITY, ENTITIES, field_spec
ABAP_SYNTAX ... ${ FROM fields_tab $} $| ${ AUTO FILL CID WITH fields_tab $} $| ${ $[AUTO FILL CID$] FIELDS ( comp1 comp2 ... ) WITH fields_tab $} $| ${ $[AUTO FILL CID$] SET FIELDS WITH fields_tab $} ...
ABAP_VARIANTS: 1 ... FROM fields_tab 2 ... AUTO FILL CID WITH fields_tab 3 ... $[AUTO FILL CID$] FIELDS ( comp1 comp2 ... ) WITH fields_tab 4 ... $[AUTO FILL CID$] SET FIELDS WITH fields_tab
ABAP Addition ... AUTO FILL CID
What does it do? The field specification expressions are used to specify input parameters on whose basis modify operations can be performed on entity instances. The variants FIELDS (...) WITH and SET FIELDS WITH can be used for the operations CREATE, CREATE BY and UPDATE. The variant FROM is the only option for DELETE and EXECUTE in most cases. The variants with AUTO FILL CID can be used for the operations CREATE and CREATE BY. The parameters that are respected for modify operations must be specified in an internal table ( fields_tab ). It is essential that the internal table is typed with the required BDEF derived type. Depending on the operation and the variant, the parameters of the internal table comprise special components . The following table provides an overview of the operations, which field specification expressions are possible for the operations, and which type and components of the required internal table are relevant. Depending on the context, the components listed in the Components column might cover more than mentioned. For example, the draft indicator %is_draft is available in case of draft scenarios only. %pid is only available in late numbering scenarios. OperationField Specification ExpressionType of Internal Table fields_tabComponents of Internal Table CREATE FROM lbr AUTO FILL CID WITH lbr FIELDS (...) WITH lbr SET FIELDS WITHTABLE FOR CREATE bdef %cid lbr %control lbr %data lbr %key lbr lbr ABAP_NOTE In case of FROM and AUTO FILL CID WITH, %control must be filled explicitly. CREATE BY _assoc FROM lbr AUTO FILL CID WITH lbr FIELDS (...) WITH lbr SET FIELDS WITH TABLE FOR CREATE bdef _assoc %cid_ref lbr %key lbr %pky lbr %target lbr %tky lbr lbr ABAP_NOTE In case of FROM and AUTO FILL CID WITH, %control must be filled explicitly within %target. UPDATE FROM lbr FIELDS (...) WITH lbr SET FIELDS WITHTABLE FOR UPDATE bdef %cid_ref lbr %control lbr %data lbr %key lbr %pky lbr %tky lbr lbr ABAP_NOTE In case of FROM, %control must be filled explicitly. DELETE FROM TABLE FOR DELETE bdef %cid_ref lbr %key lbr %pky lbr %tky EXECUTE FROM TABLE FOR ACTION IMPORT bdef~action %cid_ref lbr %key lbr %param lbr %pky lbr %tky bdef is the root entity name, _assoc the name of the association defined in the underlying CDS view of the root entity, and action the name of an action specified in the BDEF. See the details on the components in the documentation for Components of BDEF Derived Types.
Latest notes:
In case of operations for which %cid_ref can be specified in the internal table, the mandatory specification of the keys in the internal table can be omitted if a clear reference to the instance that is to be modified is given using %cid_ref.
In case of create and create-by-association operations, %cid should be specified even if the RAP BO consumer is not interested in %cid.
The additions FIELDS ( ... ) WITH and SET FIELDS WITH are only possible for modify operations executing actions (using EXECUTE ) if the action is defined with ABAP Alternative 2@2@>deep $[table$] parameter and without a selective parameter in the BDEF. NON_V5_HINTS ABAP_HINT_END
ABAP_VARIANT_1 ... FROM fields_tab
What does it do? The modify operation respects input parameters specified in an internal table (fields_tab). It can be used for all operations (CREATE, CREATE BY, UPDATE, DELETE, EXECUTE) and it is the only option for DELETE and EXECUTE. The %control structure must be filled explicitly in the internal table fields_tab for CREATE, CREATE BY and UPDATE. ABAP_NOTE
Due to the explicit filling of the %control structure, more lines of code are necessary compared with the variants FIELDS (...) WITH and SET FIELDS WITH.
A syntax check on static read-only fields is not possible with this variant (in contrast to FIELDS (...) WITH).
Fields can be set to initial values.
ABAP_EXAMPLE_VX5 The following source code section taken from CL_DEMO_RAP_EML_MODIFY_OPRTNS demonstrates the keyword FROM within a MODIFY statement. ABEXA 01525 ABAP_EXAMPLE_END
ABAP_VARIANT_2 ... AUTO FILL CID WITH fields_tab
What does it do? It is basically the variant ... FROM fields_tab using the addition AUTO FILL CID. In this case, the keyword WITH must be used before fields_tab instead of FROM. The %control structure must be filled explicitly in the internal table fields_tab. The variant can be used for CREATE and CREATE BY. See the details on AUTO FILL CID further down.
ABAP_EXAMPLE_VX5 The following source code section taken from CL_DEMO_RAP_EML_AUTO_FILL_CID demonstrates the use of AUTO FILL CID WITH with a create operation as part of an ABAP_EML MODIFY statement. ABEXA 01558 ABAP_EXAMPLE_END
ABAP_VARIANT_3 ... FIELDS ( comp1 comp2 ... ) WITH fields_tab
What does it do? Using this variant, you specify the fields that should be respected by a RAP BO operation in a field list in parentheses after the keyword FIELDS. For example, you specify the fields of RAP BO instances that should be updated. The input parameters are specified in an internal table ( fields_tab). The fields ( comp1, comp2, etc.) can be any of the entity's fields. At least one field must be specified in the field list. The fields are not separated by a comma. The order of the fields provided in this list is irrelevant. The variant is a convenience variant and a shortcut for FROM. It cannot be used for DELETE and EXECUTE. %control is filled implicitly in fields_tab. If a field is specified within the brackets of FIELDS (...) WITH, it is set to the hexadecimal value 01 in the %control structure. Otherwise, it is set to the hexadecimal value 00. ABAP_NOTE
A syntax check on static read-only fields is possible with this variant when specifying the fields within the parentheses of FIELDS (...) WITH .
Fields can be set to initial values.
If the key is not specified within the parentheses, the initial value for the key is used for the operation (even if a concrete value for the key is specified in the BDEF derived type). The initial value for the key is also used if the key is specified within the parentheses but a concrete value is not specified in the BDEF derived type.
ABAP_EXAMPLE_VX5 The following source code demonstrates the implicit setting of the %control structure component values using FIELDS (...) WITH within MODIFY statements. First, an internal table typed with a BDEF derived type is created and filled. This table is used to create a RAP BO instance in the context of a RAP create operation. All data fields are specified within the parentheses of the FIELDS (...) WITH addition as part of an ABAP_EML MODIFY statement. As a next step, the internal table is filled with other values followed by another ABAP_EML MODIFY statement. Here, the fields specified within the parentheses of FIELDS (...) WITH purposely do not include all fields. The outcome shows the effect of the field specification and the implicit setting of the %control structure. Before the ABAP_EML modify request, all hexadecimal values of the input table are 00. For the first ABAP_EML modify request in which all fields are specified, all values in the %control structure are set to 01 . For the second ABAP_EML modify request, only those components in the %control structure are set to the hexadecimal value 01 that are specified within the parentheses of the FIELDS (...) WITH addition. Consequently, despite specifying values in the input table, these fields have their initial value in the created instance. ABEXA 01668 ABAP_EXAMPLE_END
ABAP_EXAMPLE_VX5 The following source code section taken from CL_DEMO_RAP_EML_MODIFY_OPRTNS demonstrates the keywords FIELDS (...) WITH within a MODIFY statement. ABEXA 01526 ABAP_EXAMPLE_END
