SAP CRS_OBJCL_MESSAGE_CONVERT Function Module for NOTRANSL: Wandelt die SD-Meldungen in das SFA Message Format um
CRS_OBJCL_MESSAGE_CONVERT is a standard crs objcl message convert 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: Wandelt die SD-Meldungen in das SFA Message Format um 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 crs objcl message convert FM, simply by entering the name CRS_OBJCL_MESSAGE_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM8
Program Name: SAPLCRM8
Main Program: SAPLCRM8
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRS_OBJCL_MESSAGE_CONVERT 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 'CRS_OBJCL_MESSAGE_CONVERT'"NOTRANSL: Wandelt die SD-Meldungen in das SFA Message Format um.
TABLES
IN_SFA_KEYS = "Input Table Structure for SFA Key in Proxy Function Module
T_SDMESSAGES = "Return Parameter
T_CRMMESSAGES = "BAPI Structure: Messages per Data Record
TABLES Parameters details for CRS_OBJCL_MESSAGE_CONVERT
IN_SFA_KEYS - Input Table Structure for SFA Key in Proxy Function Module
Data type: BAPICRMSFKOptional: No
Call by Reference: No ( called with pass by value option)
T_SDMESSAGES - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
T_CRMMESSAGES - BAPI Structure: Messages per Data Record
Data type: BAPICRMMSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRS_OBJCL_MESSAGE_CONVERT 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_in_sfa_keys | TYPE STANDARD TABLE OF BAPICRMSFK, " | |||
| lt_t_sdmessages | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_t_crmmessages | TYPE STANDARD TABLE OF BAPICRMMSG. " |
|   CALL FUNCTION 'CRS_OBJCL_MESSAGE_CONVERT' "NOTRANSL: Wandelt die SD-Meldungen in das SFA Message Format um |
| TABLES | ||
| IN_SFA_KEYS | = lt_in_sfa_keys | |
| T_SDMESSAGES | = lt_t_sdmessages | |
| T_CRMMESSAGES | = lt_t_crmmessages | |
| . " CRS_OBJCL_MESSAGE_CONVERT | ||
ABAP code using 7.40 inline data declarations to call FM CRS_OBJCL_MESSAGE_CONVERT
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