SAP SAA_GET_ENVIRONMENT Function Module for









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

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



Function SAA_GET_ENVIRONMENT 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 'SAA_GET_ENVIRONMENT'"
EXPORTING
CUSTOMER = "Transport type (SAP/CUSTOMER)

TABLES
ISAAC = "System Administration Assistant: Determining components
.



IMPORTING Parameters details for SAA_GET_ENVIRONMENT

CUSTOMER - Transport type (SAP/CUSTOMER)

Data type: SAACOMP-TRANSTYPE
Optional: No
Call by Reference: Yes

TABLES Parameters details for SAA_GET_ENVIRONMENT

ISAAC - System Administration Assistant: Determining components

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

Copy and paste ABAP code example for SAA_GET_ENVIRONMENT 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_isaac  TYPE STANDARD TABLE OF ISAAC, "   
lv_customer  TYPE SAACOMP-TRANSTYPE. "   

  CALL FUNCTION 'SAA_GET_ENVIRONMENT'  "
    EXPORTING
         CUSTOMER = lv_customer
    TABLES
         ISAAC = lt_isaac
. " SAA_GET_ENVIRONMENT




ABAP code using 7.40 inline data declarations to call FM SAA_GET_ENVIRONMENT

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 TRANSTYPE FROM SAACOMP INTO @DATA(ld_customer).
 


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!