SAP PUT_ANLC_TO_SAPLAIST Function Module for









PUT_ANLC_TO_SAPLAIST is a standard put anlc to saplaist 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 put anlc to saplaist FM, simply by entering the name PUT_ANLC_TO_SAPLAIST into the relevant SAP transaction such as SE37 or SE38.

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



Function PUT_ANLC_TO_SAPLAIST 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 'PUT_ANLC_TO_SAPLAIST'"
EXPORTING
I_ANLN1 = "Main asset number
I_ANLN2 = "Subnumber
I_BUKRS = "Company Code

TABLES
T_ANLC = "

EXCEPTIONS
NOT_FOUND = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLAIST_001 Exchange Number Range
EXIT_SAPLAIST_002 Transfer Data for User Subscreens
EXIT_SAPLAIST_003 Transfer of User-Defined Fields to SAP Master Data Transactions

IMPORTING Parameters details for PUT_ANLC_TO_SAPLAIST

I_ANLN1 - Main asset number

Data type: ANLA-ANLN1
Optional: No
Call by Reference: Yes

I_ANLN2 - Subnumber

Data type: ANLA-ANLN2
Optional: No
Call by Reference: Yes

I_BUKRS - Company Code

Data type: ANLA-BUKRS
Optional: No
Call by Reference: Yes

TABLES Parameters details for PUT_ANLC_TO_SAPLAIST

T_ANLC -

Data type: ANLC
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)

Copy and paste ABAP code example for PUT_ANLC_TO_SAPLAIST 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:
lt_t_anlc  TYPE STANDARD TABLE OF ANLC, "   
lv_i_anln1  TYPE ANLA-ANLN1, "   
lv_not_found  TYPE ANLA, "   
lv_i_anln2  TYPE ANLA-ANLN2, "   
lv_i_bukrs  TYPE ANLA-BUKRS. "   

  CALL FUNCTION 'PUT_ANLC_TO_SAPLAIST'  "
    EXPORTING
         I_ANLN1 = lv_i_anln1
         I_ANLN2 = lv_i_anln2
         I_BUKRS = lv_i_bukrs
    TABLES
         T_ANLC = lt_t_anlc
    EXCEPTIONS
        NOT_FOUND = 1
. " PUT_ANLC_TO_SAPLAIST




ABAP code using 7.40 inline data declarations to call FM PUT_ANLC_TO_SAPLAIST

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.

 
"SELECT single ANLN1 FROM ANLA INTO @DATA(ld_i_anln1).
 
 
"SELECT single ANLN2 FROM ANLA INTO @DATA(ld_i_anln2).
 
"SELECT single BUKRS FROM ANLA INTO @DATA(ld_i_bukrs).
 


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!