SAP TB_LIMIT_READ_PARTNER Function Module for Read Business Partner
TB_LIMIT_READ_PARTNER is a standard tb limit read partner SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Business Partner 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 limit read partner FM, simply by entering the name TB_LIMIT_READ_PARTNER 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_LIMIT_READ_PARTNER 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_LIMIT_READ_PARTNER'"Read Business Partner.
EXPORTING
IT_ATLAT = "
CHANGING
CT_VTBLSP = "
EXCEPTIONS
PARTNER_NOT_FOUND = 1
IMPORTING Parameters details for TB_LIMIT_READ_PARTNER
IT_ATLAT -
Data type: TRLM_T_LATOptional: No
Call by Reference: Yes
CHANGING Parameters details for TB_LIMIT_READ_PARTNER
CT_VTBLSP -
Data type: TRLM_T_VTBLSPOptional: No
Call by Reference: Yes
EXCEPTIONS details
PARTNER_NOT_FOUND - Partner Not Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TB_LIMIT_READ_PARTNER 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.| DATA: | ||||
| lv_it_atlat | TYPE TRLM_T_LAT, " | |||
| lv_ct_vtblsp | TYPE TRLM_T_VTBLSP, " | |||
| lv_partner_not_found | TYPE TRLM_T_VTBLSP. " |
|   CALL FUNCTION 'TB_LIMIT_READ_PARTNER' "Read Business Partner |
| EXPORTING | ||
| IT_ATLAT | = lv_it_atlat | |
| CHANGING | ||
| CT_VTBLSP | = lv_ct_vtblsp | |
| EXCEPTIONS | ||
| PARTNER_NOT_FOUND = 1 | ||
| . " TB_LIMIT_READ_PARTNER | ||
ABAP code using 7.40 inline data declarations to call FM TB_LIMIT_READ_PARTNER
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