SAP CUSTOMER_SEND_MODEL_GET Function Module for NOTRANSL: get customer model for the sender - current system

Search SAP Function Modules

CUSTOMER_SEND_MODEL_GET is a standard customer send model get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: get customer model for the sender - current system 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 customer send model get FM, simply by entering the name CUSTOMER_SEND_MODEL_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function CUSTOMER_SEND_MODEL_GET 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 'CUSTOMER_SEND_MODEL_GET'"NOTRANSL: get customer model for the sender - current system
  EXPORTING
*  REFMESSAGE_TYPE = ' ' "
*  RECEIVING_SYSTEM = ' ' "

TABLES
   MODEL_DATA =  "

EXCEPTIONS
   OWN_SYSTEM_NOT_DEFINED = 1    RCV_SYSTEM_NOT_DEFINED = 2    DISTR_MODEL_ERROR = 3    PARTNER_PROFILE_NOT_DEFINED = 4 

.

IMPORTING Parameters details for CUSTOMER_SEND_MODEL_GET

REFMESSAGE_TYPE -

Data type: TBDME-REFMESTYP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

RECEIVING_SYSTEM -

Data type: TBD03-RCVSYSTEM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CUSTOMER_SEND_MODEL_GET

MODEL_DATA -

Data type: SEND_MODEL
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OWN_SYSTEM_NOT_DEFINED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RCV_SYSTEM_NOT_DEFINED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DISTR_MODEL_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARTNER_PROFILE_NOT_DEFINED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CUSTOMER_SEND_MODEL_GET 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.

ABAP code using 7.40 inline data declarations to call FM CUSTOMER_SEND_MODEL_GET

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