SAP AM_P_GET_INSTANCE Function Module for









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

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



Function AM_P_GET_INSTANCE 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 'AM_P_GET_INSTANCE'"
EXPORTING
INSTANCE_SELF = "

CHANGING
INSTANCE_WA = "
TAB_KBLINKS = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for AM_P_GET_INSTANCE

INSTANCE_SELF -

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

CHANGING Parameters details for AM_P_GET_INSTANCE

INSTANCE_WA -

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

TAB_KBLINKS -

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

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 AM_P_GET_INSTANCE 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_not_found  TYPE STRING, "   
lv_instance_wa  TYPE CFGAM_INSTANCE, "   
lv_instance_self  TYPE CFGAM_OBJECT_INSTANCE, "   
lv_tab_kblinks  TYPE CFGAM_KBLINKS. "   

  CALL FUNCTION 'AM_P_GET_INSTANCE'  "
    EXPORTING
         INSTANCE_SELF = lv_instance_self
    CHANGING
         INSTANCE_WA = lv_instance_wa
         TAB_KBLINKS = lv_tab_kblinks
    EXCEPTIONS
        NOT_FOUND = 1
. " AM_P_GET_INSTANCE




ABAP code using 7.40 inline data declarations to call FM AM_P_GET_INSTANCE

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!