Introduction
The activity “Update TDMS Header Tables with Business Process Data” in Time-based reduction  and Company Code based reduction for SAP ERP starts the activities to fill the TDMS header tables CNVTDMS_05_& in the sender system. As soon as one header table has been filled completely, the selection of the related migration objects will start automatically.The activity “Start Data Selection for Header Tables” lets you access the sub-activity information of the data selection for migration objects containing TDMS header tables.
Note: Re-execute the activity “Start Data Selection for Header Tables” in case the selection process for these conversion objects stops before it has been finished completely.
Objectives
The objective of this document is to keep you informed about all the required and useful SAP TDMS header parameters used for SAP ERP for Time-Based reduction and Company Code based reduction.
Parameter Description

  • Parameter P_TECHNQ
P_TECHNQ determines whether to use DROP technique or DELETE technique for data deletion. It is by default set to AUTO, where SAP TDMS determines which technique to use depending on the table content. Recommended value is DROP if the sender system is new and does not have data pertaining to       historical packages.
The value can be any of the following:
AUTO: Drops a table only if the table contains entries exclusive to the current package. If the table contains entries relevant to multiple packages, deletes the entries relevant to the selected package.
DROP: Uses the drop-insert technique for all TDMS header tables.
DELETE: Uses the array-delete technique for all TDMS header tables.

  • Parameter P_SELECT:
P_SELECT determines whether to use Full Table Scan for Deletion or to Select Relevant Entries to Delete. Recommended value is Full Table Scan (F) and by default this is maintained.
The value can be any of the following:
R: Selects only the relevant entries
F: Carries out a full table scan by removing non-relevant entries

  • Parameter P_CLU:
For larger database systems, set the parameter P_CLU = Y to optimize the runtime.
         
Note: if this is not consistently set to Y for all three VBUK TDMS (TD05X_FILL_VBUK, TD05X_FILL_VBUK_1 and TD05X_FILL_VBUK_2) header activity then it will lead to data inconsistency in the receiver system.

  • Parameter P_PARA:
P_PARA is used when P_CLU is set to ‘Y’. P_PARA determines how many parallel processes to use when the Cluster technique is activated. By default this is set to 4.
The value can be any of the following,
A: Locates free dialog processes automatically. If the number of located processes is sufficient (at least two), cluster processing is possible.
Y: Enables cluster processing regardless of the number of available processes.
N: The default setting. Cluster processing is not possible.

  • Parameter P_POWR:
While executing the TDMS Header Activity, if the program terminates with a time out error because of the time out in the sender system due to reasons like network connectivity, reduce the value of P_POWR for the TDMS Header Activity. Default value of P_POWR is ‘1000’.
  • Parameter P_FULL:
In case it is required to do a full transfer of related tables. Set the parameter P_FULL = X for all the TDMS header activities.
  • Parameter P_ROLL:
In case if there are any ROLL memory issues with the TDMS header activity set the parameter P_ROLL = X.
(Refer to SAP note 1054584 (Only instructions).

  • Parameter P_ROLL_W:
This is only applicable for the activities “Identification of Conditions Data”  (TD05X_FILL_KONV) and “Identification of Texts for SAP Application Objects” (TD05X_FILL_STXH). During the execution of the TDMS header program, if it terminates with a ROLL Memory issue on the table WPRP, then set the parameter  P_ROLL_W to ‘X’ and re-execute the program.

  • Parameter P_OP:
This parameter is applicable only for the activity “Identification of Accounting Documents” (TD05X_FILL_BKPF). By default, TDMS does not transfer open items when it comes to Accounting. If it is necessary to transfer the Open items as well then set the parameter P_OP = ‘X’. By default this is set to blank. Please note that setting this parameter will increase the transfer load significantly.
  • Parameter P_POPR:
While executing the TDMS Header Activity, if the program terminates with a Time Out Error in the Sender System, reduce the value of P_POPR for the TDMS Header Activity. Default value of P_POPR is ‘10000’.

  • Parameter P_PORE:
The Parameter P_PORE determines the package size of selecting data with the Cluster Technique using Cluster Technique (P_CLU = ‘Y’). If memory issue occurs reduce this value. By default the value is ‘1000000’.

  • Parameter P_SEL:
P_SEL is used for Parallel Data Selection. To activate Parallel Data Selection for objects using the TDMS header for BKPF, the parameter P_SEL has to be set to ‘X’.
For example: if you need to start the data selection of object X_JEST with multiple jobs, set P_SEL = “X” for the activity “TDMS header for JEST table”.

  • Parameter P_DONE:
This parameter signifies that major processing for TDMS header is done so that we can save extra runtime in case customer re-executes the TDMS header program again. There is no need to set this parameter explicitly. System will automatically take care of the same.

  • Parameter P_PLAN:
The parameter P_PLAN is applicable only for the activity “Identification of Controlling Documents” (TD05X_FILL_COTAB). This parameter controls the reduction logic for tables COSS, COSP, COST, COSL, and COEPR. By default, the TDMS header activity reduces these tables based on the entries in tables COEP or COBK. If you want to reduce the tables COSS, COSP, COST, COSL, and COEPR without reference to tables COEP and COBK, you can use this parameter. To proceed, set the value of this parameter to X.

  • Parameter P_DIS:
In TDO5X_FILL_COTAB, P_DIS parameter is used to choose how many fields of the table COEP is to be selected. In-case the contents of the table is big you choose just two fields by setting P_DIS = ‘TWO’. By setting P_DIS = ‘ALL’ or P_DIS = ‘ ‘, we will be selecting all the relevant fields, this may take time to execute depending on the table contents.
In TD05X_FILL_BKPF: P_DIS parameter is used to specify the technic used to select the data RFBLG table. If we set the parameter value P_DIS = ‘X’, FOR ALL ENTRIES method will be used to choose the data (the data is chosen from RFBLG based on the contents in BKPFC table). If we set P_DIS = ‘ ‘ we will be selecting using SELECT inside LOOP method.
In TD05X_FILL_AUFPL: While selecting the entries from the table AUFPL, we can choose either to select all the records and then delete the duplicates from it or to select only the distinct AUFPL records. This is done using the parameter P_DIS. If P_DIS is set to ‘ALL’ then all the records are selected and then the duplicates are deleted and if it is set to ‘  ‘ then only distinct records will be selected. This can be chosen depending on the number of entries in the table AUFPL.
  • Parameter P_EQUI_R:
If we set the parameter P_FULL in EQUI TDMS header program to ‘X’, then the content of the EQUI TDMS Header Table will be high and when it is queried in the JEST TDMS header program it may consume a lot of time to execute. In this scenario we set P_EQUI_R = ‘X’ so that the EQUI TDMS Header table is queried using CURSOR Technique.

  • Parameter P_RESB_R:
If we set the parameter P_FULL in RESB TDMS header program to ‘X’, then the content of the RESB TDMS Header Table will be high and when it is queried in the JEST TDMS header program it may consume a lot of time to execute. In this scenario we set P_RESB_R = ‘X’ so that the RESB TDMS Header table is queried using CURSOR Technique.

  • Parameter P_ROLL_W:
During the execution of this TDMS header program, if the program terminates with a ROLL Memory issue on the table WPRP, then we set the parameter P_ROLL_W to ‘X’ and re-execute the program.

The following parameters are set to specific objects for the respective TDMS headers:
Activity: Identification of Status Data for Objects (TD05X_FILL_JEST_REST):
  • Parameter P_IE:
P_IE is set to transfer all application objects starting with the prefix ‘IE’. By default this is set to the recommended value ‘X’.
  • Parameter P_OF:
P_OF is set to transfer all application objects starting with the prefix ‘OF’. By default this is set to the recommended value ‘X’.
  • Parameter P_OK:
P_OK is set to transfer all application objects starting with the prefix ‘OK’. By default this is set to the recommended value ‘X’.
  • Parameter P_OR:
P_OR is set to transfer all application objects starting with the prefix ‘OR’. By default this is set to the recommended value ‘X’.
  • Parameter P_OS:
P_OS is set to transfer all application objects starting with the prefix ‘OS’. By default this is set to the recommended value ‘X’.
  • Parameter P_OV:
P_OV is set to transfer all application objects starting with the prefix ‘OV’. By default this is set to the recommended value ‘X’.
  • Parameter P_VB:
P_VB is set to transfer all application objects starting with the prefix ‘VB’. By default this is set to the recommended value ‘X’.

NOTE: By default, SAP TDMS sets the parameter value to X and transfers the application-specific status objects from the JEST table.

Activity: Identification of Controlling Documents (TD05X_FILL_COTAB):
  • Parameter P_CC_BU: By default, this parameter enables the selection of data from the table COEP based on the controlling unit KOKRS. The value of this parameter is set to space. To enable the selection of data from the table COEP based on the organizational unit BUKRS, set the value of the parameter to X.

Activity: Identification of Additional Sales Orders (TD05X_FILL_VBUK_1):
  • Parameter P_CLU:
Described above
  • Parameter P_RECUR:
To improve the consistency in the receiver system and to enable the correct representation of the document flow in sales, the selection on the document flow table is repeated a number of times so that all the predecessor and successor documents can be found and selected. By-default the program runs five times. You can change the number of times a program run by changing the value of parameter P_RECUR. Please note that change in the value of this parameter will result in change in run time and volume of data to be transferred. If required, change the value of parameter P_RECUR accordingly.
  • Parameter P_1555:
In very rare cases program may terminate with error ORA-01555 in case of Oracle data base. If this happens then set the parameter P_1555 by entering ‘X’ in the field for this parameter. Note that, if this parameter is set then run time for this activity will also increase.

Activity:  Identification of Relevant Sales History Documents (TD05X_FILL_VBUK_2):
  • Parameter P_RECUR:
To improve the consistency in the receiver system and to enable the correct representation of the document flow in sales, the selection on the document flow table is repeated a number of times so that all the predecessor and successor documents can be found and selected. By-default the program runs five times. You can change the number of times a program run by changing the value of parameter P_RECUR. Please note that change in the value of this parameter will result in change in run time and volume of data to be transferred. If required, change the value of parameter P_RECUR accordingly.
  • Parameter P_CE2:
If this parameter is set then entries from CE3* tables are also selected. By-default this parameter is set.
  • Parameter P_1555:
Described above
  • Parameter P_MOD:
This parameter is used to improve the performance of activity. By-default it is set to ‘X’ and if it is set to ‘X’ then for huge amount of data a different check routine will be called for writing into database.
  • Parameter P_AKTBO:
To transfer the contents of the Profitability Segments (CE4XXXX_ACCT tables, where the XXXX is the Operating Concern in the system) set the parameter to ‘X’. By default it is set to Blank.

Activity:  Identification of Billing Plan Numbers (TD05X_FILL_FPLA):
  • Parameter P_INV:
This parameter enables the transfer of invoicing plan numbers from table EKPO based on the purchasing document numbers present in header table CNVTDMS_05_EKKO. To enable the transfer, the value of this parameter is set to X.
  • Parameters P_HINT and P_HNT_VL:
P_HINT_1: To activate Parallelization at DB level (only in Oracle) set the parameter P_HINT_1 to ‘X’.
P_HNT_VL: If the parameter P_HINT is to ‘X’ then use the parameter P_HNT_VL to set the value of the number of parallel process at DB level. Recommended value is ‘4’.
Note: The hint syntax changes depending on the database.
Activity:  Identification of Object Numbers with Status (TD05X_FILL_JEST):
  • Parameter P_IE:
Described above
  • Parameter P_OF:
Described above
  • Parameter P_OK:
Described above
  • Parameter P_OR:
Described above
  • Parameter P_OS:
Described above
  • Parameter P_OV:
Described above
  • Parameter P_VB:
Described above

Activity:  Identification of Conditions Data (TD05X_FILL_KONV):
  • Parameters P_HINT_1 and P_HNT_VL:

Described above

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply