Get Example source ABAP code based on a different SAP table
Boxed Components Boxed components are structures that are not stored in their superordinate context. Instead, an internal reference that points to the actual structure is stored instead of the structure. A boxed component is therefore always a deep component of its context. It is currently possible to declare substructures of structured data types and structured attributes of classes as
static boxes These boxes support initial value sharing.
Latest notes:
Boxed components are a middle ground between static and dynamic data objects. Their memory requirements are not fixed when the program is started in the ABAP_ISESS , but they can be handled like static data objects with a fixed length.
A nested structure that contains a boxed component as a component is always a deep structure.
Structures of the ABAP Dictionary can also contain boxed components. ABAP Dictionary database tables cannot contain any boxed components since their structures must be flat.
In RTTS classes and objects, boxed components are handled as follows:
The class CL_ABAP_TYPEDESCR contains the constant TYPEKIND_BREF for static boxes. The value of these constants is specified as the type of a static box in the component table COMPONENTS of the class CL_ABAP_STRUCTDESCR or the attribute table ATTRIBUTES of the classes CL_ABAP_CLASSDESCR or CL_ABAP_INTFDESCR.
In the return value of the method GET_COMPONENTS of the class CL_ABAP_STRUCTDESCR or GET_ATTRIBUTE_TYPE of the classes CL_ABAP_CLASSDESCR or CL_ABAP_INTFDESCR, boxed components are listed as type description objects of the class CL_ABAP_REFDESCR, like reference variables. The method GET_REFERENCED_TYPE of this class returns a type description object for the substructure. A type description object of the class CL_ABAP_REFDESCR, which describes a boxed component, cannot be used in the statements CREATE DATA or ASSIGN CASTING . NON_V5_HINTS ABAP_HINT_END
