Ansicht
Dokumentation

CNV_OM_PRESEL_REMOTE - Execute Preselection on Remote System

TXBHW - Original Tax Base Amount in Local Currency rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.

Purpose

The purpose of this report is to start a performance test of the preselection in the remote system.

The performance test for the preselection enables you to check your business objects (data models) against performance and data correctness already during the modelling phase. This possibility will help you to optimize your business objects to avoid data inconsistency and performance problems in the later stage of the migration or conversion projects where your business objects will be used. By running the selection test you could see if the links between the tables in your data model are properly defined and deliver the results you expect.

In order to perform this preselection test a temporary workset will be created and the selected business object will be added to this workset.You are able to test the selection of the links inside the data models. The external links during these tests will be ignored.

Integration

Prerequisites

Features

Selection

In order to start the test run of the preselection you would have to fill the following parameters:

RFC Destination: Give the RFC destination to the system where you want to test the selection. In order to ensure better tests results, take care that the RFC destination is to a system where the tables of your data model exist and contain a proper amount of data.

Limit for Header Lines: This parameter controls the max amount of data that will be selected from the head tables of the data models.

Header Blocking Factor: The selection of the data on a child level in the parent-child hierarchy of the data model is done in blocks. This parameter gives the max amount of data(block) taken from a parent table used to find the corresponding entries of the child table. The parameter helps to keep low memory usage during the selection of data on child level.

Edit embeddes specification before selection: If you check this check box, you will jump to the embedded specification of the temporary created workset. You will be able to do changes on the workset, for example, you can set a selection criteria and filters.

Selection Mode:There are two different selection modes possible. FOR ALL ENTRIES and JOIN mode.

FOR ALL ENTRIES is the default mode. In order to get the data from the child level, first a select is done on the parent level, then the data is split into blocks (see Header Blocking Factor), and then each parent data block will be used in the FOR ALL ENTRIES select statement to find the corresponding data on the child level

JOIN mode means that a SQL JOIN statement between the parent and the child level will be used to fetch the relevant data on a children level.

Standard Variants

Output

Results from the preselection test:

Error in SQL Statement: This error can happen in the following scenarios:

Links with field mapping: This error can happen because of a data type mismatch in the FOR ALL ENTRIES statement. Make sure that the field mapping in the links is between fields with compatible data type and the same length.

Link with code mapping. Make sure that the code you have defined for the link has no syntax errors and no security issues.

Duplicate records - wrong cardinality?:This status indicates that there are entries from a child table that have been more than once selected. Means that one entry from the child table can be mapped to one than more entry of the parent table. Check the link definition for the table to its parent! Maybe you can extend the link field mapping with additional fields.

Error in link definition: This status indicates that the link to the parent table is not properly defined. Could be that field mapping is not defined or that no import and export parameters are defined for the link code. Another reason for this error can be that a field name, that does not exist in the DDIC structure of the corresponding table, was used in the link definition(field mapping or code mapping).

Access time is critically low!: The status indicates that the selection from the table takes a long time. Think about if you can use an already defined table index by adding the index fields in the link mapping. Think about of remodeling possibility.

Access time is low, but not critical!: It is only a warning to inform you that the selection from the table is not very performant but also not critically high.

Selects performed, but no records fetched!: The status indicates that the table is not empty and that selection on the table was performed but no relevant records were found. Check if the link to the parent table is correctly defined.

No selects - empty link fields in parent table?: No select was performed on the table. Check if the link to the parent table is correctly defined. It looks that the fields from the parent table, that are used in the link mapping, are empty.

Table is filled but no records fetched!: The status indicates that the table is not empty but no relevant records were found. Check if the selection criteria or the filter is properly defined?

Records fetched, but not all selects successful: The status indicates that not all needed selects from the table are performed.

All selects successful:This is the status that indicates that the preselection was performed successfully and all the relevant data was fetched with good performance.

Table does not exist in DDIC:The table does not exist in the system where the test of the preselection was started. Test the preselection in a system where all the tables of the Business Object exist.

Table is inactive:The table is empty or the parent table has no relevant data.

Activities

Example

Vendor Master (General Section) Addresses (Business Address Services)
This documentation is copyright by SAP AG.

Length: 7050 Date: 20240520 Time: 084729 sap01-206 ( 137 ms )

Ansicht Dokumentation