You use table type EFG_TAB_GENDATA to flexibly transfer data between different application forms involved in the printing process and the superordinate collection.
The related data type EFG_STR_GENDATA has the following structure:
Field Name |
Data Type |
Description |
TYPE |
EFG_DTE_GENDATA_TYPE |
Type ID for data |
KEY |
EFG_DTE_GENDATA_KEY |
Key for data ID |
ATTR |
EFG_DTE_GENDATA_ATTR |
Additional attribute |
REF_TO_DATA |
EFG_DTE_REF_TO_DATA |
Reference to data |
XSTRING |
EFG_DTE_GENDATA_XSTRING |
RAWSTRING for XML data |
The fields TYPE, KEY, and ATTR identify/attribute the data record. You can
assign these fields as you require. The field TYPE identifies a component or
application. For example, PWB_DATA identifies the data selected in an
application form. The field KEY identifies an object below the information in
TYPE (for example, the name of the application form). In the field ATTR, you
can define additional attributes or information. The fields REF_TO_DATA and
XSTRING contain the data previously determined:
· REF_TO_DATA is an ABAP data reference that you have to remove before accessing the data. For detailed information, see the documentation for the ABAP Editor (transaction ABAPHELP) ® ABAP Programming Language ® Reference. You can determine the ABAP/DDIC type dynamically using ABAP methods or using the information in TYPE and KEY. In the case of PWB_DATA, the referenced data type is the highest complex DDIC type in the form class.
· The field XSTRING transports XML data. If TYPE = PWB_DATA, this means that you configure the data of the highest complex data type of the form class and all global variables that are defined in the user top include of the application form here. To do this, use the ABAP command CALL TRANSFORMATION. Before further processing, you can also use this command to reconvert this data into ABAP variables.