2
SAP Note Header Data Symptom Possible errors in the process flow of the time management extractors can only be debugged without restrictions in the test transaction RSA3 in full update mode. Previously, it was not possible to debug the delta upload, in particular if debugging was to be started from BW. Other Terms 0HR_PT_1, 0HR_PT_2, 0HR_PT_3, PTDW, HRMS_BIW_PTDW, HRMS_BIW_TIME_ACTUAL,HRMS_BIW_TIME_ACTUAL_PWS, HRMS_BIW_TIME_ACTUAL_TIMES, HRMS_BIW_TIME_ACTUAL_QUOTA Reason and Prerequisites This function was missing. Solution Debugging traps were incorporated into the source code of time management extractors. If you have not imported the relevant correction Support Package, you can implement the debugging traps with the correction instructions attached to this note. The debugging traps take effect if reporting time types or reporting quota types with a certain name exist. A debugging trap is an endless loop in the program code of an extractor. As soon as the program reaches this character, processing can only continue if the "debug" variable is changed in the debugger. The "debug" variable can have the value "X", blank (empty or initial) or "S". As long as the extractor is in the endless loop, the "debug" variable has the value "X". If the user sets the variable to the blank value, processing can continue. As soon as the extractor requests the next data package, the debugging trap takes effect again. If you want to prevent this, for example, because the debugging session is to be terminated, you can set the "debug" variable to the value "S". If DataSource 0HR_PT_1 is to be checked, create a reporting time type with the name XDEBUG1. If DataSource 0HR_PT_2 is to be checked, create a reporting time type with the name XDEBUG2. If the DataSource 0HR_PT_3 is to be checked, create a reporting quota type with the name XDEBUG3. Validity Correction Instructions Support Packages & Patches 631981 - Debugging trap for time management extractors Version 1 Validity: 06-13-2003 - active Language English Released On 07-24-2003 05:00:05 Release Status Released for Customer Component BW-BCT-PT Personnel Time Management Priority Correction with medium priority Category Program error Software Component From Rel. To Rel. And Subsequent SAP_HR 45B 45B 46B 46B 46C 46C 470 470 Correction Instructions Software Component Valid from Valid to Number SAP_HR 45B 45B 569142 SAP_HR 46B 46B 569141 SAP_HR 46C 46C 569140 SAP_HR 470 470 569139

test

Embed Size (px)

DESCRIPTION

test

Citation preview

  • SAP Note

    Header Data

    Symptom

    Possible errors in the process flow of the time management extractors can only be debugged without restrictions in the test transaction RSA3 in full update mode. Previously, it was not possible to debug the delta upload, in particular if debugging was to be started from BW.

    Other Terms

    0HR_PT_1, 0HR_PT_2, 0HR_PT_3, PTDW, HRMS_BIW_PTDW, HRMS_BIW_TIME_ACTUAL,HRMS_BIW_TIME_ACTUAL_PWS, HRMS_BIW_TIME_ACTUAL_TIMES, HRMS_BIW_TIME_ACTUAL_QUOTA

    Reason and Prerequisites

    This function was missing.

    Solution

    Debugging traps were incorporated into the source code of time management extractors. If you have not imported the relevant correction Support Package, you can implement the debugging traps with the correction instructions attached to this note. The debugging traps take effect if reporting time types or reporting quota types with a certain name exist. A debugging trap is an endless loop in the program code of an extractor. As soon as the program reaches this character, processing can only continue if the "debug" variable is changed in the debugger. The "debug" variable can have the value "X", blank (empty or initial) or "S". As long as the extractor is in the endless loop, the "debug" variable has the value "X". If the user sets the variable to the blank value, processing can continue. As soon as the extractor requests the next data package, the debugging trap takes effect again. If you want to prevent this, for example, because the debugging session is to be terminated, you can set the "debug" variable to the value "S". If DataSource 0HR_PT_1 is to be checked, create a reporting time type with the name XDEBUG1. If DataSource 0HR_PT_2 is to be checked, create a reporting time type with the name XDEBUG2. If the DataSource 0HR_PT_3 is to be checked, create a reporting quota type with the name XDEBUG3.

    Validity

    Correction Instructions

    Support Packages & Patches

    631981 - Debugging trap for time management extractors

    Version 1 Validity: 06-13-2003 - active Language English

    Released On 07-24-2003 05:00:05 Release Status Released for Customer Component BW-BCT-PT Personnel Time Management Priority Correction with medium priority Category Program error

    Software Component From Rel. To Rel. And Subsequent

    SAP_HR 45B 45B

    46B 46B

    46C 46C

    470 470

    Correction Instructions

    Software Component Valid from Valid to Number

    SAP_HR 45B 45B 569142

    SAP_HR 46B 46B 569141

    SAP_HR 46C 46C 569140

    SAP_HR 470 470 569139

  • Support Packages

    Software Component Release Support Package

    SAP_HR 45B SAPKE45BA0

    46B SAPKE46B83

    46C SAPKE46C74

    470 SAPKE47019