2009년 12월 16일 수요일
2009년 12월 7일 월요일
2009년 11월 19일 목요일
2009년 8월 31일 월요일
2009년 8월 24일 월요일
Checking P0655 settings in HRFORMS payslip using badi HRFORM_HRF02
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/15086
by Carlos Martinez Escribano
Hi Guys,
I'd like to share with the HCM community some hints on how to customize the HRFORMS payslip so that the settings in Infotype P0655 are taken into account. In the case of PE51 based forms, this is not necessary as the standard deals with infotype P0655. Users can record at infotype P0655 whether the employee uses ESS remuneration statement, therefore the payslip must not be printed when the remuneration statement program is run at the backend.
by Carlos Martinez Escribano
Hi Guys,
I'd like to share with the HCM community some hints on how to customize the HRFORMS payslip so that the settings in Infotype P0655 are taken into account. In the case of PE51 based forms, this is not necessary as the standard deals with infotype P0655. Users can record at infotype P0655 whether the employee uses ESS remuneration statement, therefore the payslip must not be printed when the remuneration statement program is run at the backend.
Scrum is an iterative incremental framework - Wiki
http://en.wikipedia.org/wiki/Scrum_%28development%29
Scrum is an iterative incremental framework for managing complex work (such as new product development) commonly used with agile software development. Though not an acronym, some companies implementing the process have been known to adhere to an all capital letter expression of the word, i.e., SCRUM. This may be due to one of Ken Schwaber's early papers capitalizing SCRUM in the title.[1]
Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach.
Scrum is an iterative incremental framework for managing complex work (such as new product development) commonly used with agile software development. Though not an acronym, some companies implementing the process have been known to adhere to an all capital letter expression of the word, i.e., SCRUM. This may be due to one of Ken Schwaber's early papers capitalizing SCRUM in the title.[1]
Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach.
피드 구독하기:
글 (Atom)