SAP HRFPM_FTE_RESTRICTION_CREATE Function Module for

Search SAP Function Modules

HRFPM_FTE_RESTRICTION_CREATE is a standard hrfpm fte restriction create 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 hrfpm fte restriction create FM, simply by entering the name HRFPM_FTE_RESTRICTION_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRFPM_FTE_ANNOT_MAINT
Program Name: SAPLHRFPM_FTE_ANNOT_MAINT
Main Program: SAPLHRFPM_FTE_ANNOT_MAINT
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRFPM_FTE_RESTRICTION_CREATE 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 'HRFPM_FTE_RESTRICTION_CREATE'"
  EXPORTING
   PLVAR =  "Plan Variant
*  OTYPE = 'BU' "Object Type
   OBJID =  "Object ID
*  SUBTY =  "Subtype
*  BEGDA = '19000101' "Start Date
*  ENDDA = '99991231' "End Date
*  ISTAT = '1' "Planning Status
*  VTASK = 'B' "
*  I_AMNT_SUGGEST =  "Number

EXCEPTIONS
   OTYPE_NOT_VALID = 1    NO_ACTIVE_PLVAR = 2    ERROR_IN_ENQUEUE = 3    OBJECT_NOT_FOUND = 4    INVALID_BUDGET_TYPE = 5    CANCEL = 6 

.

IMPORTING Parameters details for HRFPM_FTE_RESTRICTION_CREATE

PLVAR - Plan Variant

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

OTYPE - Object Type

Data type: P1509-OTYPE
Default: 'BU'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJID - Object ID

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

SUBTY - Subtype

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

BEGDA - Start Date

Data type: P1509-BEGDA
Default: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA - End Date

Data type: P1509-ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ISTAT - Planning Status

Data type: P1509-ISTAT
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VTASK -

Data type: HRRHAP-VTASK
Default: 'B'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_AMNT_SUGGEST - Number

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

EXCEPTIONS details

OTYPE_NOT_VALID -

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

NO_ACTIVE_PLVAR -

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

ERROR_IN_ENQUEUE -

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

OBJECT_NOT_FOUND -

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

INVALID_BUDGET_TYPE -

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

CANCEL -

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

Copy and paste ABAP code example for HRFPM_FTE_RESTRICTION_CREATE 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 HRFPM_FTE_RESTRICTION_CREATE

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