원본: http://www.enm-consulting.co.kr/xe/890
===================================================
테스트 결과
1. 퇴직발령 없이 소득정산(0008) 실행할 때 급여 Function KRSIP 에서
에러 발생 -> 퇴직일을 읽어 오는 Function에서 퇴직일 결과가 '000000'으로 됨
2. 소득정산 후 이후 회사에서 급여 계산시 CRT가 초기화한 다음 누적되어야 하는데,
계속 누적 됨.
3. 근로소득 원천징수 영수증 출력시 이전 소득정산(0008) 실행한 것을 출력해도
근무지 정보가 현재 소속회사로 출력됨.
처리방법
1. 입사일 퇴사일 BADI 수정회사 그룹사 이동 발령전일을 퇴사일에 추가
IMG : Personal Management->Personnel Administration->Evaluation basis
-> BADI Determine Entry/Leaving Dates
2. 급여 Function SETCU를 복사 수정해서 이전 급여가 중도정산(0007,0008)
이면 CRT Refresh
3. 중도정산 (0007,0008) 실행될때 그룹사 이동발령인 경우 종(전)근무지 인포타입 3542생성하여
중도정산 결과 저장 (연말정산 실행시 전근무지 정보로 읽어 옴)
4. 중도정산이 있는 사원의 연말정산 실행시 급여 Function KRTAX의 Tax Period의 시작일을
중도정산 익일로 변경
5. 원천징수 영수증 출력등 프로그램에서 사원의 소속근무지를 읽어오는 기준일자 수정
2010년 10월 28일 목요일
대량의 데이타를 저장 시 Buffer Clear - 펌
원본: http://www.enm-consulting.co.kr/xe/641
================================================
BDC나 또는 다른 방법으로 대량의 데이타를 Infotype에 처리 시
HR_INFOTYPE_OPERATION 을 사용하는데 이 함수의 큰 단점이
대량의 데이타 처리 시 시간이 지날수록 한건의 데이타 처리 시간이
기하급수적으로 증가하여 때로는 시스템이 죽은 것처럼 보일 정도로
한건의 데이타처리 시간이 엄청나게 오래 걸리는 경우가 종종 발생합니다.
이를 방지하기 위해 메모를 비워주는 함수를 사용하면 그 시간이 굉장히
단축됩니다. (LOOP문의 맨처음 정의)
Function : HR_INITIALIZE_BUFFER
HR_PSBUFFER_INITIALIZE
[ 사용예 ]
LOOP AT it_record.
* BUFFER 초기화
CALL FUNCTION 'HR_INITIALIZE_BUFFER'.
CALL FUNCTION 'HR_PSBUFFER_INITIALIZE'.
...
...
ENDLOOP.
================================================
BDC나 또는 다른 방법으로 대량의 데이타를 Infotype에 처리 시
HR_INFOTYPE_OPERATION 을 사용하는데 이 함수의 큰 단점이
대량의 데이타 처리 시 시간이 지날수록 한건의 데이타 처리 시간이
기하급수적으로 증가하여 때로는 시스템이 죽은 것처럼 보일 정도로
한건의 데이타처리 시간이 엄청나게 오래 걸리는 경우가 종종 발생합니다.
이를 방지하기 위해 메모를 비워주는 함수를 사용하면 그 시간이 굉장히
단축됩니다. (LOOP문의 맨처음 정의)
Function : HR_INITIALIZE_BUFFER
HR_PSBUFFER_INITIALIZE
[ 사용예 ]
LOOP AT it_record.
* BUFFER 초기화
CALL FUNCTION 'HR_INITIALIZE_BUFFER'.
CALL FUNCTION 'HR_PSBUFFER_INITIALIZE'.
...
...
ENDLOOP.
휴무쿼터 관련 Function Module - 펌
원본: http://www.enm-consulting.co.kr/xe/632
============================================================
대게 Infotype에 데이타를 저장 시 HR_INFOTYPE_OPERATION을 사용하는데
휴무쿼터에 대한 데이타 반영시 HR_INFOTYPE_OPERATION을 사용하면
쿼터 반영에 오류가 있다고 합니다.
휴무관련 데이타(특히 2001번) 반영 시 아래에 명기되어 있는 Function 그룹의
Function을 사용해야 제대로 데이타가 처리되니 참고하시기 바랍니다.
Function Group : HRTIM00BAPIABSATT
Function Module : BAPI_PTMGRATTABS_MNGCHANGE - Change Attendances/Absences
BAPI_PTMGRATTABS_MNGCREATION BAPI - Creates Attendances/Absences
BAPI_PTMGRATTABS_MNGDELETE - Delete Attendances/Absences
BAPI_PTMGRATTABS_MNGFROMWF - Create/Change/Delete Attendances/Absences from Workflow
============================================================
대게 Infotype에 데이타를 저장 시 HR_INFOTYPE_OPERATION을 사용하는데
휴무쿼터에 대한 데이타 반영시 HR_INFOTYPE_OPERATION을 사용하면
쿼터 반영에 오류가 있다고 합니다.
휴무관련 데이타(특히 2001번) 반영 시 아래에 명기되어 있는 Function 그룹의
Function을 사용해야 제대로 데이타가 처리되니 참고하시기 바랍니다.
Function Group : HRTIM00BAPIABSATT
Function Module : BAPI_PTMGRATTABS_MNGCHANGE - Change Attendances/Absences
BAPI_PTMGRATTABS_MNGCREATION BAPI - Creates Attendances/Absences
BAPI_PTMGRATTABS_MNGDELETE - Delete Attendances/Absences
BAPI_PTMGRATTABS_MNGFROMWF - Create/Change/Delete Attendances/Absences from Workflow
2010년 9월 16일 목요일
Note 317722 - Upgrade information for table T77S0
Note 317722 - Upgrade information for table T77S0
Summary
Symptom
A number of entries in table T77S0 delivered in the standard 4.6B system are incorrect. These include:
PLOGI ORGA
TRSP CORR
PLOGI EVENB
...
After upgrade, it is possible that the system response changed in many instances in HR. For example, after the upgrade the automatic transport connection is always active.For example, the automatic transport link is always active after the upgrade.
Other terms
Upgrade
Reason and Prerequisites
The error occurs during an upgrade from a release <= 4.6B to a Release >= 4.6B.In addition, the error occurs during each upgrade to an R3 Enterprise system.
Solution
On SAPSERV3, in the directory ~ftp/general/R3server/abap/note.0317722 you will find subdirectories containing the required programs RH77S0BU and RH77S0RE.
If the legacy system has status 3.0 or 3.1, choose the ~/s0_3 subdirectory.If the legacy system has a status >= 4.0, choose the ~/s0_4 subdirectory.
Start the report RH77S0BU before the upgrade.This report saves the T77SO entries in all clients in table INDX.
Copy report RH77S0RE to your customer name range so that you still have the report after the upgrade.It is important that you also copy the status of the report. After the upgrade you can run the copied report per client.The report provides a list of entries that are different and can restore the old status where necessary.The problem only concerns entries that were changed by the customer in a former release. No new flags should be deleted.
Header Data
Release Status: Released for Customer
Released on: 21.02.2003 14:08:35
Master Language: German
Priority: Correction with high priority
Category: Upgrade information
Primary Component: PA-BC Basis
Affected Releases
Release-Independent
Related Notes
748338 - Upgrade LSO (Table LSO_CUSTOMIZE_C)
505820 - Backup of Table entries in T77S0 for CM Upgrade
373038 - Organizational Management: data missing after upgrade
353861 - HR: Upgrade to 4.6C (or higher)
==============
참고용. old버전 자료임
Summary
Symptom
A number of entries in table T77S0 delivered in the standard 4.6B system are incorrect. These include:
PLOGI ORGA
TRSP CORR
PLOGI EVENB
...
After upgrade, it is possible that the system response changed in many instances in HR. For example, after the upgrade the automatic transport connection is always active.For example, the automatic transport link is always active after the upgrade.
Other terms
Upgrade
Reason and Prerequisites
The error occurs during an upgrade from a release <= 4.6B to a Release >= 4.6B.In addition, the error occurs during each upgrade to an R3 Enterprise system.
Solution
On SAPSERV3, in the directory ~ftp/general/R3server/abap/note.0317722 you will find subdirectories containing the required programs RH77S0BU and RH77S0RE.
If the legacy system has status 3.0 or 3.1, choose the ~/s0_3 subdirectory.If the legacy system has a status >= 4.0, choose the ~/s0_4 subdirectory.
Start the report RH77S0BU before the upgrade.This report saves the T77SO entries in all clients in table INDX.
Copy report RH77S0RE to your customer name range so that you still have the report after the upgrade.It is important that you also copy the status of the report. After the upgrade you can run the copied report per client.The report provides a list of entries that are different and can restore the old status where necessary.The problem only concerns entries that were changed by the customer in a former release. No new flags should be deleted.
Header Data
Release Status: Released for Customer
Released on: 21.02.2003 14:08:35
Master Language: German
Priority: Correction with high priority
Category: Upgrade information
Primary Component: PA-BC Basis
Affected Releases
Release-Independent
Related Notes
748338 - Upgrade LSO (Table LSO_CUSTOMIZE_C)
505820 - Backup of Table entries in T77S0 for CM Upgrade
373038 - Organizational Management: data missing after upgrade
353861 - HR: Upgrade to 4.6C (or higher)
==============
참고용. old버전 자료임
Backing Up Table T512W (Wage Types)
https://websmp105.sap-ag.de/~sapidb/011000358700008832642001E
acking Up Table T512W (Wage Types)
Use
We generally recommend backing up wage types table T512W before upgrading. However, in the following cases, you must back up table T512W:
You have modified 'technical' wage types, that is wage types beginning with '/' (adjustment of processing class, evaluation class, and so on).
You are using SAP model wage types, that is wage types beginning with a letter, and you have modified these.
You have defined wage types that are not within the customer name range. To find out if this applies, check table TRESC by entering T512W as the table name and TABU as the object.
Procedure
Note
Read SAP note 447984 and implement SAP note 605878 before the upgrade.
Before the upgrade, back up table T512W or selected areas of this table. To do this, use report RPU12W0S. The documentation on the report includes instructions on how to proceed.
Note
Table T512W is client-specific. Make sure you back up the data in the correct client.
You can restore your backup copy after the upgrade. To do this, you can use the following reports:
RPU12W0C restores selected parts of table T512W. This method is particularly suitable if you have exact documentation about the wage types you have modified.
RPU12W0S restores the entire backup or a generically selected area of the table.
acking Up Table T512W (Wage Types)
Use
We generally recommend backing up wage types table T512W before upgrading. However, in the following cases, you must back up table T512W:
You have modified 'technical' wage types, that is wage types beginning with '/' (adjustment of processing class, evaluation class, and so on).
You are using SAP model wage types, that is wage types beginning with a letter, and you have modified these.
You have defined wage types that are not within the customer name range. To find out if this applies, check table TRESC by entering T512W as the table name and TABU as the object.
Procedure
Note
Read SAP note 447984 and implement SAP note 605878 before the upgrade.
Before the upgrade, back up table T512W or selected areas of this table. To do this, use report RPU12W0S. The documentation on the report includes instructions on how to proceed.
Note
Table T512W is client-specific. Make sure you back up the data in the correct client.
You can restore your backup copy after the upgrade. To do this, you can use the following reports:
RPU12W0C restores selected parts of table T512W. This method is particularly suitable if you have exact documentation about the wage types you have modified.
RPU12W0S restores the entire backup or a generically selected area of the table.
2010년 9월 10일 금요일
Wagetype copy: table to table
(1)T511
(2)T512T
(3)T512W
(4)T512Z
(5)T52D7
(6)T52DZ
(7)T539A
(8)T539J
(9)T591B
(10)T51P6
(11)T510S
(12)T52EK
(13)T52EKT
(14)T52EL
(15)T52EZ
========================
sample sql
T511
WHERE MOLGA = '41' AND LGART BETWEEN '1A00' AND '9ZZZ'
T512T
WHERE SPRSL = '3' AND MOLGA = '41' AND LGART BETWEEN '1A00' AND '9ZZZ'
T512W
WHERE MOLGA = '41' AND LGART BETWEEN '1A00' AND '9ZZZ'
T512Z
WHERE MOLGA = '41'
T52D7
WHERE MOLGA = '41'
T52DZ
WHERE MOLGA = '41'
T52EL
WHERE MOLGA = '41'
T52EZ
WHERE MOLGA = '41'
T539J
WHERE MOLGA = '41' AND BWLGA BETWEEN '1A00' AND '9ZZZ'
T591B
WHERE MOLGA = '41'
(2)T512T
(3)T512W
(4)T512Z
(5)T52D7
(6)T52DZ
(7)T539A
(8)T539J
(9)T591B
(10)T51P6
(11)T510S
(12)T52EK
(13)T52EKT
(14)T52EL
(15)T52EZ
========================
sample sql
T511
WHERE MOLGA = '41' AND LGART BETWEEN '1A00' AND '9ZZZ'
T512T
WHERE SPRSL = '3' AND MOLGA = '41' AND LGART BETWEEN '1A00' AND '9ZZZ'
T512W
WHERE MOLGA = '41' AND LGART BETWEEN '1A00' AND '9ZZZ'
T512Z
WHERE MOLGA = '41'
T52D7
WHERE MOLGA = '41'
T52DZ
WHERE MOLGA = '41'
T52EL
WHERE MOLGA = '41'
T52EZ
WHERE MOLGA = '41'
T539J
WHERE MOLGA = '41' AND BWLGA BETWEEN '1A00' AND '9ZZZ'
T591B
WHERE MOLGA = '41'
2010년 9월 1일 수요일
Function: SE16N_INTERFACE (Display table as full screen)
SE16N_INTERFACE
I_TAB = Table name
I_EDIT = 'X'
FUNCTION SE16N_INTERFACE.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_TAB) TYPE SE16N_TAB
*" VALUE(I_EDIT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_SAPEDIT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_NO_TXT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_MAX_LINES) TYPE SYTABIX DEFAULT 500
*" VALUE(I_LINE_DET) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_DISPLAY) TYPE CHAR1 DEFAULT 'X'
*" VALUE(I_CLNT_SPEZ) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_CLNT_DEP) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_VARIANT) TYPE SLIS_VARI DEFAULT ' '
*" VALUE(I_OLD_ALV) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_CHECKKEY) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_TECH_NAMES) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_CWIDTH_OPT_OFF) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_SCROLL) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_NO_CONVEXIT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_LAYOUT_GET) TYPE CHAR1 DEFAULT ' '
*" EXPORTING
*" VALUE(E_LINE_NR) TYPE SYTABIX
*" VALUE(E_DREF)
*" TABLES
*" IT_SELFIELDS STRUCTURE SE16N_SELTAB OPTIONAL
*" IT_OUTPUT_FIELDS STRUCTURE SE16N_OUTPUT OPTIONAL
*" IT_OR_SELFIELDS TYPE SE16N_OR_T OPTIONAL
*" IT_CALLBACK_EVENTS TYPE SE16N_EVENTS OPTIONAL
*" EXCEPTIONS
*" NO_VALUES
*"----------------------------------------------------------------------
I_TAB = Table name
I_EDIT = 'X'
FUNCTION SE16N_INTERFACE.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_TAB) TYPE SE16N_TAB
*" VALUE(I_EDIT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_SAPEDIT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_NO_TXT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_MAX_LINES) TYPE SYTABIX DEFAULT 500
*" VALUE(I_LINE_DET) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_DISPLAY) TYPE CHAR1 DEFAULT 'X'
*" VALUE(I_CLNT_SPEZ) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_CLNT_DEP) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_VARIANT) TYPE SLIS_VARI DEFAULT ' '
*" VALUE(I_OLD_ALV) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_CHECKKEY) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_TECH_NAMES) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_CWIDTH_OPT_OFF) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_SCROLL) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_NO_CONVEXIT) TYPE CHAR1 DEFAULT ' '
*" VALUE(I_LAYOUT_GET) TYPE CHAR1 DEFAULT ' '
*" EXPORTING
*" VALUE(E_LINE_NR) TYPE SYTABIX
*" VALUE(E_DREF)
*" TABLES
*" IT_SELFIELDS STRUCTURE SE16N_SELTAB OPTIONAL
*" IT_OUTPUT_FIELDS STRUCTURE SE16N_OUTPUT OPTIONAL
*" IT_OR_SELFIELDS TYPE SE16N_OR_T OPTIONAL
*" IT_CALLBACK_EVENTS TYPE SE16N_EVENTS OPTIONAL
*" EXCEPTIONS
*" NO_VALUES
*"----------------------------------------------------------------------
피드 구독하기:
글 (Atom)