SAP HR_GENERATE_WORK_SCHEDULE Function Module for

Search SAP Function Modules

HR_GENERATE_WORK_SCHEDULE is a standard hr generate work schedule SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for hr generate work schedule FM, simply by entering the name HR_GENERATE_WORK_SCHEDULE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PTWS
Program Name: SAPLPTWS
Main Program: SAPLPTWS
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function HR_GENERATE_WORK_SCHEDULE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'HR_GENERATE_WORK_SCHEDULE'"
  EXPORTING
   ZEITY =  "Employee subgroup grouping for work schedules
   MOFID =  "Public holiday calendar ID
   MOSID =  "Personnel subarea grouping for work schedules
   SCHKZ =  "Work schedule rule
   BEGJAHR =  "Start year for work schedule generation
   BEGMONAT =  "Start month for work schedule generation
*  ENDJAHR =  "End year for work schedule generation
*  ENDMONAT =  "End month for work schedule generation

TABLES
   INT552A =  "

EXCEPTIONS
   ERROR_OCCURED = 1 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLPTWS_001 User Exit for Generating Monthly Work Schedule

IMPORTING Parameters details for HR_GENERATE_WORK_SCHEDULE

ZEITY - Employee subgroup grouping for work schedules

Data type: T552A-ZEITY
Optional: No
Call by Reference: No ( called with pass by value option)

MOFID - Public holiday calendar ID

Data type: T552A-MOFID
Optional: No
Call by Reference: No ( called with pass by value option)

MOSID - Personnel subarea grouping for work schedules

Data type: T552A-MOSID
Optional: No
Call by Reference: No ( called with pass by value option)

SCHKZ - Work schedule rule

Data type: T552A-SCHKZ
Optional: No
Call by Reference: No ( called with pass by value option)

BEGJAHR - Start year for work schedule generation

Data type: T552A-KJAHR
Optional: No
Call by Reference: No ( called with pass by value option)

BEGMONAT - Start month for work schedule generation

Data type: T552A-MONAT
Optional: No
Call by Reference: No ( called with pass by value option)

ENDJAHR - End year for work schedule generation

Data type: T552A-KJAHR
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDMONAT - End month for work schedule generation

Data type: T552A-MONAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for HR_GENERATE_WORK_SCHEDULE

INT552A -

Data type: T552A
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_OCCURED - An error has occurred, see long text

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HR_GENERATE_WORK_SCHEDULE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM HR_GENERATE_WORK_SCHEDULE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects