Ansicht
Dokumentation
FKK_STRUCTURE_READ - Internal: FI-CA Strucure Read Module
ROGBILLS - Synchronize billing plans BAL_S_LOG - Application Log: Log header dataThis documentation is copyright by SAP AG.
Functionality
Function module FKK_STRUCTURE_READ reads, based on records of a database table (or view) transferred, or the key of these records in a defined navigation path, related records of other associated (by foreign key) tables.
The data exchange with the calling program takes place via internal tables, that have the same structure as the corresponding databases or views. You can transfer several output table records to the structure reader and thus carry out the navigation for several records simultaneously. The output table records can belong to different tables or views.
The navigation path is transferred in the internal table XT_PATH. Every line in this table defines a navigation step. This means that records are read from a table for each line. The structure reader processes table XT_PATH sequentially in the order of the lines. The resulting navigation path does not have to be connected. You can use a table/view more than once during the navigation, and can repeat individual navigation steps.
To select the data, the structure reader uses function modules that perform ARRAY-selects. It is therefore very efficient.
The data selection is carried out for all historically managed tables/views for the period specified in the parameters X_AB and X_BIS. You cannot specify other periods for individual tables or records.
As standard, all of the table records transferred to the structure reader are read from the database and completed before the actual navigation phase. It therefore suffices to specify the keys (with the exception of the from date that the structure reader sets). If you set the parameter X_IS_COMPLETE, this function no longer takes place. The structure reader assumes that all records transferred from all tables are complete, correct, and up-to-date.
On request, a structure table is created that records which table records are connected with which other table records. In table YT_STRUC, more connections may be returned than expected. Possible reasons are:
- A connection between two historical records is displayed, even thought the validity periods of both categories are not connected.
- There are connections of a specific category between table records that, based on the selection sequence, were not selected in the corresponding selection step but independently of one another later in different steps.
Example
For the devices with keys 4711 and 4712, the device locations,the connection objects in which they are located, and the premise that belong to this connection object are to be found.
Parameters transferred:
- Blank internal tables T_xxxx with the structures of database tables EGPL, EHAU, and EVBS.
- Internal table T_EGER of structure V_EGER with two records where only keys 4711 and 4712 are filled
- Internal table X_PATH with the records:
EGER - EGPL - space
EGPL - EHAU - space
EHAU - EVBS - space
- Parameter X_STRUC = 'X'
Result of call:
- Internal tables T_xxxx filled with the appropriated records
- Internal table yt_path that describes a connection between two connected records of internal tables T_xxxx for each record.
Notes
All internal tables that are accessed during navigation are returned sorted by primary key. This particularly applies to tables that are only output of navigation steps. Therefore, indexes for lines generally do not point to the same table records as before the call.
Further information
The tables and views supported and the possible navigation paths are displayed in the documentation of the function group EFSR.
Parameters
T_FKKVKPXT_PATH
X_AB
X_ACTUAL
X_BIS
X_IS_COMPLETE
X_PROGRESS_DISPLAY
X_STRUCTURE
YT_STRUC
Exceptions
DATE_INVALIDPATH_INVALID
Function Group
FKSTABAP Short Reference General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 4619 Date: 20240523 Time: 073145 sap01-206 ( 89 ms )
