Skip to end of metadata
Go to start of metadata

Symptom

While running RPTEXTPT (CAT6) to transfer CATS data to infotypes you experience Performance Problems.

Solution

There are a couple of reason on why you can have such performance issues which will be covered on this article.

There are problems with running this program during the day. For example, if you run the program in the background please note that infotypes are also updated in the background. Infotypes will not be updated until a user has left the application, which can create long waiting periods for the user. In these cases, it would be best to run the program at night when there are not a lot of programs trying to compete for the same limited resources. This page describes some hints and best practices to avoid such kind of issue.

Ten Commandments for a good performance with RPTEXTPT

  1. Run a transfer every night by a batch job;
  2. Run the transfer report more frequently;
  3. Split employees in subgroups and run different groups on different application servers;
  4. Don't run the transfer report at times a lot of users enter data, because this will slow down the process. Schedule it, so the process can run with a high priority;
  5. Check if there are any other background processes running. If so, reschedule them;
  6. Reorganize time sheet interface tables (report RCATSRIF - tcode CATR) more frequently, but only for the entries that will no more be changed by users, e.g. previous financial year;
  7. In general, decreasing the 'lower limit' on the time settings in the data entry profile is good for performance. A setting of 2 is optimal;
  8. If you are using SAP enhancements (user exits), performance problems often results in these exits. You may consider deactivating these until your performance problems are resolved;
  9. Make sure to switch off the infotype log;
  10. If applicable, think about the immediate transfer to HR. In this case, every entry would use 1-2 seconds;

Improving performance in time tables

First please review the note 326120 regarding index creation on the interface table PTEX2000 which should have a positive effect on performance. The index should be created on the fields MANDT, PERNR and and BEGDA. Please also make sure, that the option 'Index on all database systems' or 'For selected database systems' is active for this index.

Furthermore we recommend to run report RCATSRIF frequently (e.g. as a batch run) to reorganize time sheet interface tables (PTEX2000 and PTEX2010 for HR). This report deletes records that have already been transferred to the target components from their respective interface tables.

Please also refer to the notes 350113, 363286, 153887 and 153560 which contain useful information in this context and are also valid for your release (even if the validity in the note administration refers to earlier releases).

More info about RPTEXTPT report

Please have a look at the documentation to the new transferring report RPTEXTPT (used in CATA as well as in transaction CAT6): "You can use the report "Transfer External Time Data ->Human Resources" (RPEXTTHR) to transfer data from the interface tables PTEX20XX to the relevant infotypes (20xx) in Human Resources (HR). The transfer of external time wage types from the interface table PTEX2000 to the Absences (2001) and Attendances (2002) infotypes and to the interface table PTEX2010 in the Employee Remuneration Info. infotype (2010) is supported. The transfer report is based on the data from the interface tables PTEX2010 and PTEX2000. You can use insert BAPIs for the business objects PTManagerExtAttAbs & PTMgrExtRemunSpec Information to fill the interface tables. These BAPIs receive data with a predefined external format and convert the fields into the SAP internal format of structure PTEX2000 or PTEX2010.

Please be also aware, that if your profile is customized with "direct transfer to HR" there could be some situations, when the data can´t be transferred and the system doesn`t give any error-messages. For example, if the personnel number is locked in HR (PA30).
So if you find out that there are some records not transferred to HR, you could start the report RPTEXTPT (CAT6 or CATA) in mode "repeat transfer" one more time."

Nevertheless, in regards to performance you may parallel RPTEXTPT as follows:

  • Count the number of CPUs on all the customer's application servers;
  • Split the customer's personnel numbers in ranges, one range for each CPU;
  • Start an appropriate number of SAP work processes on these application servers (BATCH);
  • On each application server, set up batch jobs with report RPTEXTPT for each CPU with the corresponding range of personnel numbers as data selection parameter;
  • Plan to start all these batch jobs simultaneously as soon as the intermediate tables are filled with the external time data.

The result is a speed-up of the transfer by the total number of CPUs.

Usually the transfer process is only done for a considerable short time interval, as the report has not been designed to transfer a large data 'package' with one run. Therefore we can only suggest to split up the data into smaller parts (potentially using job scheduling) and running report RPTEXTPT without log.

  • No labels