Get Example source ABAP code based on a different SAP table
• %control ABAP_BDEF_DER_TYP_COMP
%control>
ABAP_USE %control> is a component group> in BDEF derived types>. It is a structure that contains all key and data fields of a RAP BO instance> as components indicating flags. It is used to get information on which fields are provided (e. g. in the context of CREATE>> or UPDATE>> operations) or set a flag for which fields are requested (e. g. in the context of READ>> operations) by RAP BO providers> or RAP BO consumers> respectively during the current transaction. In many cases, the control structure is filled implicitly and automatically, for example, in the context of RAP MODIFY> operations using the ABAP word SET FIELDS WITH>>. However, depending on the context, the explicit specification of %control > is mandatory. For example, in the context of a RAP MODIFY> operation using the ABAP word FROM> (e. g. ... CREATE FROM ... > or ... UPDATE FROM ...>), %control> must be specified. For specifying the values of the fields, the structured constant mk > of interface IF_ABAP_BEHV>> can be used: if_abap_behv=>mk-on> and if_abap_behv=>mk-off>. For example, if fields are set with the value if_abap_behv=>mk-on > in a CREATE> operation, they are respected by the operation. If they are set with if_abap_behv=>mk-off>, the fields are not respected. Note that the technical type is x length 1>, hence, a simple flag like 'X'> does not work. In READ> operations, the keys must always be used and returned. Hence, unmarking the keys in %control> in the context of managed scenarios are ignored. Type> The components of the %control> structure have the following type: ABP_BEHV_FLAG>>