Ansicht
Dokumentation
DTINF_DEFINE_PARAM - Define Parameters
BAL Application Log Documentation rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
In this Customizing activity, you can maintain optional parameters that influence the creation of the IRF data model as well as the data collection process. For more information about the different parameters that can be maintained, refer to the Activities section.
To use this Customizing activity, the following prerequisites must be fulfilled:
- You have activated the business function Information Retrieval Framework (CA_DTINF_FW) in transaction SFW5.
- You have enabled the current system to work with the IRF. You can configure this in Customizing activity Maintain System Status.
Follow below steps to create a new entry in table DTINF_PARAMETERS:
- Call up the Customizing activity and choose Display -> Changefrom the application toolbar.
- Click on New Entries.
You can maintain the following parameters:
- Parameter SAP_MODEL_BADIS
- When creating the data model required by the IRF, you can use this parameter to define if you want to accept or ignore SAP-delivered implementations of BAdI: Tables Used by an ILM Object.
- For certain applications, SAP provides BadI implementations of BAdI: Tables Used by an ILM Object(BADI_DTINF_ILM_OBJ_TABLES). These BAdI implementations are meant to simplify your data modeling process by adding/ removing tables relevant for an ILM object as well as by adjusting the relationships and field-to-field links between these tables. For more information about the availability of these implementations, refer to SAP Note 2743548.
- However, if any IRF data models already exist in your system, these might be changed when using SAP delivered BAdI implementations. If you set parameter SAP_MODEL_BADIS, you can decide whether you want to accept or ignore SAP-delivered BAdI implementations. The general behavior of the parameter is as follows:
- If this parameter is not set in table DTINF_PARAMETERS (i.e. it is not present in field Parameter Name 1), the BAdI implementations delivered by SAP will be ignored.
- If the parameter name is set in table DTINF_PARAMETERS(i.e it is present in field Parameter Name 1), you can maintain its value as described in the table below.
| Field | Field Value |
|---|---|
| Parameter Name 1 | SAP_MODEL_BADIS[mandatory value] |
| Parameter Value 1 | If there is no value maintained for this field, the BAdI implementations delivered by SAP will be ignored by the IRF. This is the default value for this parameter. |
| If you want to use the BAdI implementations delivered by SAP, set the field value to "X". |
- It is also possible to use both your own BAdI implementations (with BADI_DTINF_ILM_OBJ_TABLES_C) as well as the ones delivered by SAP (with BADI_DTINF_ILM_OBJ_TABLES). In these cases, please note that the methods of the SAP implementations will be called first when generating a data model for the relevant ILM object.
- Parameter DISPLAY_ACROSS_ILM
- You can use this parameter to collect data across data models.
- By default, data will only be collected per data model. If you set this parameter, the collection will run across the logically related links defined between tables of several data models. Maintain the parameter as follows:
| Field | Field Value |
|---|---|
| Parameter Name 1 | DISPLAY_ACROSS_ILM |
| Parameter Value 1 | Set value to "X" to perform cross-model collection. |
- Parameter SEARCH
- You can use this parameter to define an application-specific starting table for the data collection process.
- The data collection can only be triggered using a business partner number, customer number, account number of supplier, user name or personnel number. This means that a master data table must be the starting point for the data collection. However, several applications storing personal data might not have a connection to any of these master data tables. In these cases, it is possible to define an application-specific table as the starting point for the data collection. Maintain the following values of parameter SEARCH to define an application-specific starting table:
| Field | Field Value | ||
|---|---|---|---|
| Parameter Name 1 | SEARCH [mandatory value] | ||
| Parameter Name 2 | Enter a unique search type (max. 10 characters), e.g. BP for business partner number | ||
| Parameter Value 1 | Short description of the starting table you define in Parameter Value 2The value maintained here will be displayed in the Start Data Collection and Process Data Collection Results report as the Data Subject ID Type. The field is case-sensitive. | ||
| Parameter Value 2 | Technical name of the starting table | ||
| Parameter Value 3 | Technical name of the starting field within the starting table | ||
- Parameter COLL_BATCH_SIZE
- You can use this parameter to define a batch size for the data collection, i.e. you determine how many data records are inserted at once into the result tables during a data collection run (the default value is 5000 entries). If you want to increase or decrease the batch size, maintain this parameter as follows:
| Field | Field Value |
|---|---|
| Parameter Name 1 | COLL_BATCH_SIZE[mandatory value] |
| Parameter Value 1 | Enter a numeric value for the batch size. |
- Parameter PARALLEL_COLL
- You can use this parameter to enable or disable parallel data collections. If you enable parallel processing, the following additional settings can be made:
- Define the maximum number of purposes for which parallel processing can be performed. By default, the search runs for a maximum of 5 purposes at the same time.
- Determine the percentage of free work processes that are made available for parallel processing. By default, 50 percent of free work processes are allocated for parallel processing.
- If you want to disable parallel processing, maintain this parameter as follows:
| Field | Field Value |
|---|---|
| Parameter Name 1 | PARALLEL_COLL[mandatory value] |
| Parameter Name 2 | DISABLE |
| Parameter Value 1 | Set value to "X" to disable parallel processing. |
- If parallel processing is enabled and you want to maintain a maximum number of purposes that can be processed in parallel, maintain this parameter as follows:
| Field | Field Value |
|---|---|
| Parameter Name 1 | PARALLEL_COLL[mandatory value] |
| Parameter Name 2 | MAX_PROCESS |
| Parameter Value 1 | Set a numeric value to define the maximum number of purposes to be processed in parallel. |
- If parallel processing is enabled and you want to define the percentage of free work processes that should be made available for parallel processing, maintain this parameter as follows:
| Field | Field Value |
|---|---|
| Parameter Name 1 | PARALLEL_COLL[mandatory value] |
| Parameter Name 2 | WP_USAGE_PERCENTAGE |
| Parameter Value 1 | Set a numeric value to define the percentage of free work processes that should be made available for parallel processing. |
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 11839 Date: 20240523 Time: 172356 sap01-206 ( 145 ms )
