SAP GET_CUSTOMER_EXTENSION Function Module for Get customer extension
GET_CUSTOMER_EXTENSION is a standard get customer extension SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get customer extension 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 get customer extension FM, simply by entering the name GET_CUSTOMER_EXTENSION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SPAU_UI
Program Name: SAPLSPAU_UI
Main Program: SAPLSPAU_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:

Function GET_CUSTOMER_EXTENSION 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 'GET_CUSTOMER_EXTENSION'"Get customer extension.
IMPORTING
E_CLASS_NAME = "Object Type Name
EXCEPTIONS
NO_IMPLEMENTATION = 1
EXPORTING Parameters details for GET_CUSTOMER_EXTENSION
E_CLASS_NAME - Object Type Name
Data type: SEOCLSNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_IMPLEMENTATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_CUSTOMER_EXTENSION 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_e_class_name | TYPE SEOCLSNAME, " | |||
| lv_no_implementation | TYPE SEOCLSNAME. " |
|   CALL FUNCTION 'GET_CUSTOMER_EXTENSION' "Get customer extension |
| IMPORTING | ||
| E_CLASS_NAME | = lv_e_class_name | |
| EXCEPTIONS | ||
| NO_IMPLEMENTATION = 1 | ||
| . " GET_CUSTOMER_EXTENSION | ||
ABAP code using 7.40 inline data declarations to call FM GET_CUSTOMER_EXTENSION
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