Get Example source ABAP code based on a different SAP table
• %cid ABAP_BDEF_DER_TYP_COMP
%cid>
ABAP_USE %cid> is a component of BDEF derived types>. It is a string to define a content ID that should be filled for ABAP_EML requests. In case of strict(2)>> mode, the use of %cid> is enforced. Content IDs are used as a unique and preliminary identifier for RAP BO> instances, especially as long as no primary key exists for the particular instance. %cid> is used in RAP create operations to create RAP BO instances and for performing further, referencing modifications on those instances using %cid_ref>>. %cid_ref> - which has the same value as %cid> - is then used, for example, in RAP operations using CREATE BY >>, UPDATE>> and DELETE>>, as well as actions > with EXECUTE>> in a single ABAP_EML MODIFY>> request. %cid> must be unique within one ABAP_EML request and can be specified manually or automatically. The specified content ID is only valid within one ABAP_EML request. The specification of %cid> should be done even if there are no further operations referring to it. Especially in the context of early numbering >> and late numbering>> scenarios, %cid> must be specified to avoid issues. In ABAP_EML MODIFY> statements, the addition AUTO FILL CID> > can be used to create %cid> automatically to ensure that %cid> is filled. However, if %cid_ref> is to be used, %cid> must be specified manually since %cid_ref > cannot refer to an automatically created value. Type> The component has the following type: ABP_BEHV_CID>>.