SAP GET_LIMIT Function Module for

Search SAP Function Modules

GET_LIMIT is a standard get limit 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 get limit FM, simply by entering the name GET_LIMIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: FITP_INTEGRATION
Program Name: SAPLFITP_INTEGRATION
Main Program: SAPLFITP_INTEGRATION
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_LIMIT 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 'GET_LIMIT'"
  EXPORTING
   MOREI =  "Trip Provision Variant
   CATEGORY =  "Travel Service Category
   PAYED_BY_COMPANY =  "Paid by Company
   BEGDA =  "Validity Start Date
   ENDDA =  "End of Validity Period
   COUNTRY =  "Trip Country
   PLAN_ACTIVITY =  "

 IMPORTING
   LIMIT_TYP =  "
   LIMIT =  "
   CURRENCY =  "Currency
   MESSAGE_ID =  "Message Class
   MESSAGE_NUMBER =  "Message Number

TABLES
   ITEMS =  "Request Items

EXCEPTIONS
   NOT_FOUND = 1    NO_LIMIT = 2 

.

IMPORTING Parameters details for GET_LIMIT

MOREI - Trip Provision Variant

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

CATEGORY - Travel Service Category

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

PAYED_BY_COMPANY - Paid by Company

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

BEGDA - Validity Start Date

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

ENDDA - End of Validity Period

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

COUNTRY - Trip Country

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

PLAN_ACTIVITY -

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

EXPORTING Parameters details for GET_LIMIT

LIMIT_TYP -

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

LIMIT -

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

CURRENCY - Currency

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

MESSAGE_ID - Message Class

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

MESSAGE_NUMBER - Message Number

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

TABLES Parameters details for GET_LIMIT

ITEMS - Request Items

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

EXCEPTIONS details

NOT_FOUND -

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

NO_LIMIT -

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

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

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