SAP LCA_GET_CLIENTS_WITH_PLANVERS Function Module for









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

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



Function LCA_GET_CLIENTS_WITH_PLANVERS 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 'LCA_GET_CLIENTS_WITH_PLANVERS'"
IMPORTING
ET_CLIENT = "
ET_RC = "

EXCEPTIONS
LC_CONNECT_FAILED = 1 LC_COM_ERROR = 2 LC_APPL_ERROR = 3
.



EXPORTING Parameters details for LCA_GET_CLIENTS_WITH_PLANVERS

ET_CLIENT -

Data type: MAND_TYPE
Optional: No
Call by Reference: Yes

ET_RC -

Data type: LCA_RC_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

LC_CONNECT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

LC_COM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

LC_APPL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LCA_GET_CLIENTS_WITH_PLANVERS 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_et_client  TYPE MAND_TYPE, "   
lv_lc_connect_failed  TYPE MAND_TYPE, "   
lv_et_rc  TYPE LCA_RC_TAB, "   
lv_lc_com_error  TYPE LCA_RC_TAB, "   
lv_lc_appl_error  TYPE LCA_RC_TAB. "   

  CALL FUNCTION 'LCA_GET_CLIENTS_WITH_PLANVERS'  "
    IMPORTING
         ET_CLIENT = lv_et_client
         ET_RC = lv_et_rc
    EXCEPTIONS
        LC_CONNECT_FAILED = 1
        LC_COM_ERROR = 2
        LC_APPL_ERROR = 3
. " LCA_GET_CLIENTS_WITH_PLANVERS




ABAP code using 7.40 inline data declarations to call FM LCA_GET_CLIENTS_WITH_PLANVERS

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!