Ansicht
Dokumentation
CNV_10020_CREATE_COLLECTOR - Collection of LOR data for collector paths
Fill RESBD Structure from EBP Component Structure CL_GUI_FRONTEND_SERVICES - Frontend ServicesThis documentation is copyright by SAP AG.
Description
This program reads the relationship data for all alternative paths belonging to a multiple path flagged as a collector path from the related LOR table for a given package, and stores them under the object type of the multiple path in the same LOR table. In the process, the path status is updated automatically so that from now on the relationship data for the multiple path can be read directly from the LOR table.
The purpose of this collection of the LOR data is to avoid multiple determination steps at runtime. When a program accesses the multiple paths, the alternative paths are not processed any longer. Instead, the target determination values can be read directly from the object table for the object type of the multiple path.
The term "LOR data" as mentioned below may refer not only to the transparent object tables, but also to data that is saved in the cluster table.
Requirements
- The relationship data for all alternative paths must already be available in a LOR table. If these relations are not elementary, you need to create shortcuts beforehand. Interval data from ROR tables is not supported, because overlaps are likely to occur during the collection process, and it would be virtually impossible to resolve these overlaps at reasonable cost.
- Set the path parameters for the multiple paths in accordance with your requirements. If you write data by packages, for example, you may want to set the indicator for accepting duplicate entries.
Example
The line item data for a document may be stored in more than one table and belong to different company
codes. The way to find out the company code to which a given document header belongs is for the system
to read the corresponding line items and find the company codes. To avoid multiple access to the object tables at runtime, the program collects the relationship data in an object type called 'BL'.
In the example below, the collected LOR data for the following sample records from multiple path BLPOS_BUKRS (consisting of the elementary relationships BLPOS_BUKRS1 and BLPOS_BUKRS2) is listed:
- Document line items for table 1
-
BELNR POS BUKRS
0000000001 001 1000
0000000001 002 1000
0000000001 003 3000
0000000001 005 1000
0000000001 008 3000
- Document line items for table 2
-
BELNR POS BUKRS
0000000001 004 1000
0000000001 006 2000
0000000001 007 2000
- Elementary relationship BLPOS_BUKRS1 for table 1
-
OBART_S DTVAL_S DTVAL_T
01 0000000001 1000
01 0000000001 3000
- Elementary relationship BLPOS_BUKRS2 for table 2
-
OBART_S DTVAL_S DTVAL_T
02 0000000001 1000
02 0000000001 2000
- Collector path BLPOS_BUKRS
-
OBART_S DTVAL_S DTVAL_T
BL 0000000001 1000
BL 0000000001 2000
BL 0000000001 3000
Selection screen
On the selection screen, you define the package and the multiple path for which you want to collect the relationship data.
If the indicator Delete LOR data is set, the relationship data for the alternative paths is automatically deleted from the object tables after the collection (unless it is needed for other purposes).
If the indicator Test run is set, the relationship data is collected internally, but not stored in the database in this form. The number of read and created LOR records, the respective required storage space and the resulting compression rate are output.
If the indicator List output of collector data is set, the collected relationship data is listed. This is done exclusively for testing purposes. This indicator should only be set if the relevant data volume is very small, because otherwise the output would become much too unwieldy.
If the indicator Execute in background is set, the program runs in the background with the current settings as specified on the selection screen.
rdisp/max_wprun_time - Maximum work process run time General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 4705 Date: 20240531 Time: 144639 sap01-206 ( 86 ms )
