SAP TB_LIMITS_SPLIT Function Module for Split Limits

Search SAP Function Modules

TB_LIMITS_SPLIT is a standard tb limits split SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Split Limits processing and below is the pattern details for this FM, 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 tb limits split FM, simply by entering the name TB_LIMITS_SPLIT into the relevant SAP transaction such as SE37 or SE38.

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

Function TB_LIMITS_SPLIT 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 'TB_LIMITS_SPLIT'"Split Limits
  EXPORTING
   I_VTBLV0 =  "Limit for Splitting
   I_DATE =  "Data on Which Split Is Set
   I_TABIX =  "Internal Tables, Current Line Index

 IMPORTING
   E_VTBLV0_ONE =  "New Limit Until Split Date
   E_VTBLV0_TWO =  "New Limit From Split Date

CHANGING
   C_VTBLVIL =  "Interim Limits for Limit

EXCEPTIONS
   WRONG_DATE = 1    LIMIT_NOT_RELEASED = 2    IL_NOT_RELEASED = 3    NO_RELEVANT_IL = 4    FUTURE_INTERIMS = 5 

.

IMPORTING Parameters details for TB_LIMITS_SPLIT

I_VTBLV0 - Limit for Splitting

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

I_DATE - Data on Which Split Is Set

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

I_TABIX - Internal Tables, Current Line Index

Data type: SY-TABIX
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for TB_LIMITS_SPLIT

E_VTBLV0_ONE - New Limit Until Split Date

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

E_VTBLV0_TWO - New Limit From Split Date

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

CHANGING Parameters details for TB_LIMITS_SPLIT

C_VTBLVIL - Interim Limits for Limit

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

EXCEPTIONS details

WRONG_DATE - Split on this Date Not Possible

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

LIMIT_NOT_RELEASED - Limit Not Completely Released

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

IL_NOT_RELEASED - Interim Limits Not Completely Released

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

NO_RELEVANT_IL - There Is No Interem Limit for Date

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

FUTURE_INTERIMS - There Are Interim Limits After Split Date

Data type:
Optional: No
Call by Reference: Yes

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

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