* **** D WGTYP?
* **** **** ADDWT *
* **** 6900 ADDWT * ELIMI * ADDWT /301
* **** 6910 ADDWT * ELIMI * ADDWT /302
* **** 6920 ADDWT * ELIMI * SETIN 1=01ADDWT /4PEADDWT /4PR
2009년 12월 29일 화요일
RPUTRBK0 - Transfer old payroll results: Update Payroll Status (Infotype 0003)
Program....: RPUTRBK0
Description: Utility to update Payroll Status (Infotype 0003).
Logic......: A list of screen fields to be updated is provided
as select-options in the selection-screen. The program
assumes that all data entered are correct, and no
validation, other than check for valid personnel
numbers, are performed. Due to the nature of the
Payroll Status (Infotype 0003), direct database update
will be performed. This program is developed based on
a similar SAP delivered program, namely, RPUCRR00.
Description: Utility to update Payroll Status (Infotype 0003).
Logic......: A list of screen fields to be updated is provided
as select-options in the selection-screen. The program
assumes that all data entered are correct, and no
validation, other than check for valid personnel
numbers, are performed. Due to the nature of the
Payroll Status (Infotype 0003), direct database update
will be performed. This program is developed based on
a similar SAP delivered program, namely, RPUCRR00.
2009년 12월 28일 월요일
BUS7023.InsertLegacy
Your must transfer the payroll results from your legacy system before the first payroll run.
You transfer the data using the BUS7023.InsertLegacy method in the Data Transfer Workbench. For general information on using the Workbench, refer to Application help from the Data Transfer Workbench. Choose Data Transfer Objects in Applications -> HR - Human Resource Management -> Data Transfer: Payroll Account. This also gives detailed information on the transfer of payroll results.
If you complete the interface tables T558B, T558D and T558E with your own report, you do not have to use the Data Transfer Workbench.
Subsequently, you start the payroll driver with the data transfer schema xLK0 (x stands for the country code), to format the data from the interface tables as payroll results and to store it in the database table PCL2. This ensures that all payroll periods are transferred from table T558B.
function bapi_extpayroll_insert_legacy.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(EMPLOYEENUMBER) LIKE BAPI_BUS7023-PERNR
*" EXPORTING
*" VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2
*" TABLES
*" PERIODS STRUCTURE BAPI7023_PAYPERIODS
*" WAGETYPES STRUCTURE BAPI7023_WAGETYPES
*"----------------------------------------------------------------------
You transfer the data using the BUS7023.InsertLegacy method in the Data Transfer Workbench. For general information on using the Workbench, refer to Application help from the Data Transfer Workbench. Choose Data Transfer Objects in Applications -> HR - Human Resource Management -> Data Transfer: Payroll Account. This also gives detailed information on the transfer of payroll results.
If you complete the interface tables T558B, T558D and T558E with your own report, you do not have to use the Data Transfer Workbench.
Subsequently, you start the payroll driver with the data transfer schema xLK0 (x stands for the country code), to format the data from the interface tables as payroll results and to store it in the database table PCL2. This ensures that all payroll periods are transferred from table T558B.
function bapi_extpayroll_insert_legacy.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(EMPLOYEENUMBER) LIKE BAPI_BUS7023-PERNR
*" EXPORTING
*" VALUE(RETURN) LIKE BAPIRET2 STRUCTURE BAPIRET2
*" TABLES
*" PERIODS STRUCTURE BAPI7023_PAYPERIODS
*" WAGETYPES STRUCTURE BAPI7023_WAGETYPES
*"----------------------------------------------------------------------
2009년 12월 21일 월요일
Payroll Rule: PRT ZLOZ NOAB *Store user wage types - LOAN
[양수]
* ****
* /LEP D VAKEYLNTYP
* /LEP **** ADDWTE5000
* /LEP 9000 ADDWTE5000NEXTR A INTEREST
* /LEP 9000 A
* /LEP 9001 ADDWTE5020NEXTR A INTEREST
* /LEP 9001 A
* /LEP 9100 ADDWTE5040NEXTR A INTEREST
* /LEP 9100 A
* /LEP 9200 ADDWTE5070NEXTR A INTEREST
* /LEP 9200 A
* /LID D VAKEYLNTYP
* /LID **** ADDWTE5000
* /LID 9000 ADDWTE5010NEXTR A INTEREST
* /LID 9000 A
* /LID 9001 ADDWTE5030NEXTR A INTEREST
* /LID 9001 A
* /LID 9100 ADDWTE5060NEXTR A INTEREST
* /LID 9100 A
* /LOP D VAKEYLNTYP
* /LOP **** ADDWTE5000
* /LOP 9000 ADDWTE5000NEXTR A INTEREST
* /LOP 9000 A
* /LOP 9001 ADDWTE5020NEXTR A INTEREST
* /LOP 9001 A
* /LOP 9100 ADDWTE5040NEXTR A INTEREST
* /LOP 9100 A
* /LOP 9200 ADDWTE5070NEXTR A INTEREST
* /LOP 9200 A
* /LRP D VAKEYLNTYP
* /LRP **** ADDWTE5000
* /LRP 9000 ADDWTE5000NEXTR A INTEREST
* /LRP 9000 A
* /LRP 9001 ADDWTE5020NEXTR A INTEREST
* /LRP 9001 A
* /LRP 9100 ADDWTE5040NEXTR A INTEREST
* /LRP 9100 A
* /LRP 9200 ADDWTE5070NEXTR A INTEREST
* /LRP 9200 A
[음수]
* ****
* /LEP D VAKEYLNTYP
* /LEP **** ADDWTE5000
* /LEP 9000 AMT*-1 ADDWTE5000NEXTR A INTEREST
* /LEP 9000 A
* /LEP 9001 AMT*-1 ADDWTE5020NEXTR A INTEREST
* /LEP 9001 A
* /LEP 9100 AMT*-1 ADDWTE5040NEXTR A INTEREST
* /LEP 9100 A
* /LEP 9200 AMT*-1 ADDWTE5070NEXTR A INTEREST
* /LEP 9200 A
* /LID D VAKEYLNTYP
* /LID **** ADDWTE5000
* /LID 9000 AMT*-1 ADDWTE5010NEXTR A INTEREST
* /LID 9000 A
* /LID 9001 AMT*-1 ADDWTE5030NEXTR A
* /LID 9001 A
* /LID 9100 AMT*-1 ADDWTE5060NEXTR A INTEREST
* /LID 9100 A
* /LOP D VAKEYLNTYP
* /LOP **** ADDWTE5000
* /LOP 9000 AMT*-1 ADDWTE5000NEXTR A INTEREST
* /LOP 9000 A
* /LOP 9001 AMT*-1 ADDWTE5020NEXTR A INTEREST
* /LOP 9001 A
* /LOP 9100 AMT*-1 ADDWTE5040NEXTR A INTEREST
* /LOP 9100 A
* /LOP 9200 AMT*-1 ADDWTE5070NEXTR A INTEREST
* /LOP 9200 A
* /LRP D VAKEYLNTYP
* /LRP **** ADDWTE5000
* /LRP 9000 AMT*-1 ADDWTE5000NEXTR A INTEREST
* /LRP 9000 A
* /LRP 9001 AMT*-1 ADDWTE5020NEXTR A INTEREST
* /LRP 9001 A
* /LRP 9100 AMT*-1 ADDWTE5040NEXTR A INTEREST
* /LRP 9100 A
* /LRP 9200 AMT*-1 ADDWTE5070NEXTR A INTEREST
* /LRP 9200 A
* ****
* /LEP D VAKEYLNTYP
* /LEP **** ADDWTE5000
* /LEP 9000 ADDWTE5000NEXTR A INTEREST
* /LEP 9000 A
* /LEP 9001 ADDWTE5020NEXTR A INTEREST
* /LEP 9001 A
* /LEP 9100 ADDWTE5040NEXTR A INTEREST
* /LEP 9100 A
* /LEP 9200 ADDWTE5070NEXTR A INTEREST
* /LEP 9200 A
* /LID D VAKEYLNTYP
* /LID **** ADDWTE5000
* /LID 9000 ADDWTE5010NEXTR A INTEREST
* /LID 9000 A
* /LID 9001 ADDWTE5030NEXTR A INTEREST
* /LID 9001 A
* /LID 9100 ADDWTE5060NEXTR A INTEREST
* /LID 9100 A
* /LOP D VAKEYLNTYP
* /LOP **** ADDWTE5000
* /LOP 9000 ADDWTE5000NEXTR A INTEREST
* /LOP 9000 A
* /LOP 9001 ADDWTE5020NEXTR A INTEREST
* /LOP 9001 A
* /LOP 9100 ADDWTE5040NEXTR A INTEREST
* /LOP 9100 A
* /LOP 9200 ADDWTE5070NEXTR A INTEREST
* /LOP 9200 A
* /LRP D VAKEYLNTYP
* /LRP **** ADDWTE5000
* /LRP 9000 ADDWTE5000NEXTR A INTEREST
* /LRP 9000 A
* /LRP 9001 ADDWTE5020NEXTR A INTEREST
* /LRP 9001 A
* /LRP 9100 ADDWTE5040NEXTR A INTEREST
* /LRP 9100 A
* /LRP 9200 ADDWTE5070NEXTR A INTEREST
* /LRP 9200 A
[음수]
* ****
* /LEP D VAKEYLNTYP
* /LEP **** ADDWTE5000
* /LEP 9000 AMT*-1 ADDWTE5000NEXTR A INTEREST
* /LEP 9000 A
* /LEP 9001 AMT*-1 ADDWTE5020NEXTR A INTEREST
* /LEP 9001 A
* /LEP 9100 AMT*-1 ADDWTE5040NEXTR A INTEREST
* /LEP 9100 A
* /LEP 9200 AMT*-1 ADDWTE5070NEXTR A INTEREST
* /LEP 9200 A
* /LID D VAKEYLNTYP
* /LID **** ADDWTE5000
* /LID 9000 AMT*-1 ADDWTE5010NEXTR A INTEREST
* /LID 9000 A
* /LID 9001 AMT*-1 ADDWTE5030NEXTR A
* /LID 9001 A
* /LID 9100 AMT*-1 ADDWTE5060NEXTR A INTEREST
* /LID 9100 A
* /LOP D VAKEYLNTYP
* /LOP **** ADDWTE5000
* /LOP 9000 AMT*-1 ADDWTE5000NEXTR A INTEREST
* /LOP 9000 A
* /LOP 9001 AMT*-1 ADDWTE5020NEXTR A INTEREST
* /LOP 9001 A
* /LOP 9100 AMT*-1 ADDWTE5040NEXTR A INTEREST
* /LOP 9100 A
* /LOP 9200 AMT*-1 ADDWTE5070NEXTR A INTEREST
* /LOP 9200 A
* /LRP D VAKEYLNTYP
* /LRP **** ADDWTE5000
* /LRP 9000 AMT*-1 ADDWTE5000NEXTR A INTEREST
* /LRP 9000 A
* /LRP 9001 AMT*-1 ADDWTE5020NEXTR A INTEREST
* /LRP 9001 A
* /LRP 9100 AMT*-1 ADDWTE5040NEXTR A INTEREST
* /LRP 9100 A
* /LRP 9200 AMT*-1 ADDWTE5070NEXTR A INTEREST
* /LRP 9200 A
Payroll rule: PIT ZSIP GEN NOAB *고용보험 10원미만 절사
000010 D WGTYP?
000020 **** ADDWT *
000030 /4UE AMT= /4UEROUND -010ADDWT *
000040 /4UR AMT= /4UEROUND -010ADDWT *
000050 /YFE AMT= /4UEROUND -010ADDWT *
000060 /YFR AMT= /4UEROUND -010ADDWT *
000070 /YUE AMT= /4UEROUND -010ADDWT *
000080 /YUR AMT= /4UEROUND -010ADDWT *
000020 **** ADDWT *
000030 /4UE AMT= /4UEROUND -010ADDWT *
000040 /4UR AMT= /4UEROUND -010ADDWT *
000050 /YFE AMT= /4UEROUND -010ADDWT *
000060 /YFR AMT= /4UEROUND -010ADDWT *
000070 /YUE AMT= /4UEROUND -010ADDWT *
000080 /YUR AMT= /4UEROUND -010ADDWT *
Payroll rule: P0014 ZR11 GEN NOAB *Import recurring payments/deductions수정
1. without the WPBP split
000010 AMT= BETRGNUM= ANZHLNEXTR
000020 1 D VAKEYZEINH
000030 *** D VWTCL 47
000040 *** * D AMT?0
000050 *** * * KRSNRS ADDWT *
000060 *** * > OPIND ADDWT *
000070 *** Q ELIMI * ADDWTE* ADDWT&MY10 FORCE BANK TRANSFER
000080 010 D VWTCL 47
000090 010 * OPIND ADDWT *
000100 012 D VWTCL 47
000110 012 * OPIND ADDWT *
2. with the WPBP split
000010 AMT= BETRGNUM= ANZHLNEXTR
000020 1 D VAKEYZEINH
000030 *** D VWTCL 47
000040 *** * D AMT?0
000050 *** * * KRSNRS ADDWT *
000060 *** * > OPIND ELIMI A WPBPC ADDWT *
000080 *** Q ELIMI * ADDWTE* ADDWT&MY10 FORCE BANK TRANSFER
000090 010 D VWTCL 47
000100 010 * OPIND ADDWT *
000110 012 D VWTCL 47
000120 012 * OPIND ADDWT *
2009년 12월 17일 목요일
Note 412261 - Enhancement of Time Management infotypes
Note 412261
Summary
Symptom
According to the documentation for the enhancement of infotypes, the infotypes of Time Management are excluded from the enhancement concept (customer-specific fields). That is, you cannot include new fields in these infotypes. Incorrectly, however, the documentation only states infotypes with numbers 2nnn here. However, also the following Time Management infotypes cannot be enhanced that is, you also cannot add new fields to these infotypes:
Infotype 0005 ('Leave Entitlement');
Infotype 0080 ('Maternity Protection/Parental Leave')
Infotype 0081 ('Military Service')
Infotype 0083 ('Leave Entitlement Compensation')
Infotype 0416 ('Time Quota Compensation')
If you add fields to these infotypes, no stable and secure processing of the infotype records can be guaranteed. Under these conditions, inconsistent data may occur.
Additional key words
CI-INCLUDE, PM01.
Cause and prerequisites
For business reasons, the specified infotypes have a complex screen control and flow logic which overrides the general infotype screen control concept. For example, the screen control is influenced by the processing mode (infotype 5: creation and change of the record, use of other screens) or the initial screens are views of several infotype records.However, a basic prerequisite for the secure functioning of the enhancement concept is that the general infotype screen control concept is adhered to and that the flow logic does not differ from the infotype standard concept.
Solution
Do not use the option of the enhancement concept for the above infotypes.
The following solution may be interesting for you as a workaround: Add the relevant customer-specific fields to a new customer-specific infotype or to a related master data infotype which supports the enhancement concept. If required, use the option of the infotype header to display these new fields in the context of the time infotype as well.
Some customers report that they made quite good experiences with the use of customer-specific fields in the above time infotypes in particular if these infotypes are supplied by batch input so that the user interactions can be foreseen.Here it should be mentioned that in specific customer situations, a correct processing is actually possible, however, this correct functioning cannot be guaranteed in the general case as described above. In particular changes of the processing logic (or error corrections as in Note 313887) may lead to the situation that a 'correct' processing is suddenly no longer possible.Thus it has to be made clear that the use of customer-specific fields in the above time infotypes always occurs at your own risk. In the extreme case, you have to change to the above workaround and migrate the stored data to the new infotype if problems occur.
Header Data
Release Status:
Released for Customer
Released on:
25.06.2001 22:00:00
Master Language:
German
Priority:
Correction with low priority
Category:
Consulting
Primary Component:
PT-RC Time Data Recording and Management
Summary
Symptom
According to the documentation for the enhancement of infotypes, the infotypes of Time Management are excluded from the enhancement concept (customer-specific fields). That is, you cannot include new fields in these infotypes. Incorrectly, however, the documentation only states infotypes with numbers 2nnn here. However, also the following Time Management infotypes cannot be enhanced that is, you also cannot add new fields to these infotypes:
Infotype 0005 ('Leave Entitlement');
Infotype 0080 ('Maternity Protection/Parental Leave')
Infotype 0081 ('Military Service')
Infotype 0083 ('Leave Entitlement Compensation')
Infotype 0416 ('Time Quota Compensation')
If you add fields to these infotypes, no stable and secure processing of the infotype records can be guaranteed. Under these conditions, inconsistent data may occur.
Additional key words
CI-INCLUDE, PM01.
Cause and prerequisites
For business reasons, the specified infotypes have a complex screen control and flow logic which overrides the general infotype screen control concept. For example, the screen control is influenced by the processing mode (infotype 5: creation and change of the record, use of other screens) or the initial screens are views of several infotype records.However, a basic prerequisite for the secure functioning of the enhancement concept is that the general infotype screen control concept is adhered to and that the flow logic does not differ from the infotype standard concept.
Solution
Do not use the option of the enhancement concept for the above infotypes.
The following solution may be interesting for you as a workaround: Add the relevant customer-specific fields to a new customer-specific infotype or to a related master data infotype which supports the enhancement concept. If required, use the option of the infotype header to display these new fields in the context of the time infotype as well.
Some customers report that they made quite good experiences with the use of customer-specific fields in the above time infotypes in particular if these infotypes are supplied by batch input so that the user interactions can be foreseen.Here it should be mentioned that in specific customer situations, a correct processing is actually possible, however, this correct functioning cannot be guaranteed in the general case as described above. In particular changes of the processing logic (or error corrections as in Note 313887) may lead to the situation that a 'correct' processing is suddenly no longer possible.Thus it has to be made clear that the use of customer-specific fields in the above time infotypes always occurs at your own risk. In the extreme case, you have to change to the above workaround and migrate the stored data to the new infotype if problems occur.
Header Data
Release Status:
Released for Customer
Released on:
25.06.2001 22:00:00
Master Language:
German
Priority:
Correction with low priority
Category:
Consulting
Primary Component:
PT-RC Time Data Recording and Management
2009년 12월 16일 수요일
2009년 12월 7일 월요일
Function: RH_DIR_ORG_STRUC_GET
If you like to get a cost center of a organization unit, use the function 'RH_DIR_ORG_STRUC_GET'.
others: RH_READ_COSTCENTER_OF_OBJECT, RH_COSTCENTER_OF_OBJECT_GET
others: RH_READ_COSTCENTER_OF_OBJECT, RH_COSTCENTER_OF_OBJECT_GET
피드 구독하기:
글 (Atom)