SAP CRS_SALES_KEY_CONVERT Function Module for NOTRANSL: Konvertierung der Tabelle BAPISDKEY in BAPICRMKEY und BAPICRMR3
CRS_SALES_KEY_CONVERT is a standard crs sales key 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: Konvertierung der Tabelle BAPISDKEY in BAPICRMKEY und BAPICRMR3 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 sales key convert FM, simply by entering the name CRS_SALES_KEY_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRMA
Program Name: SAPLCRMA
Main Program: SAPLCRMA
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRS_SALES_KEY_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_SALES_KEY_CONVERT'"NOTRANSL: Konvertierung der Tabelle BAPISDKEY in BAPICRMKEY und BAPICRMR3.
EXPORTING
* I_REQUEST = ' ' "Single-Character Indicator
I_UPLOAD_ID = "Unique Reference Number
I_UPLOAD_STAT = "Upload Status at Table Level
I_CHANGE_ID = "Change Type (U, I, E, D)
TABLES
RETURN = "Return Parameter
TI_SFA_KEYS = "Input Table Structure for SFA Key in Proxy Function Module
TI_SDKEY = "Key in Sales and Distribution Document
TO_KEYINFO = "BAPI Structure: Key Information
IMPORTING Parameters details for CRS_SALES_KEY_CONVERT
I_REQUEST - Single-Character Indicator
Data type: BAPIFLAG-BAPIFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_UPLOAD_ID - Unique Reference Number
Data type: BAPICRMDH2-REF_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_UPLOAD_STAT - Upload Status at Table Level
Data type: BAPICRMDH2-UPLOADSTATOptional: No
Call by Reference: Yes
I_CHANGE_ID - Change Type (U, I, E, D)
Data type: BAPICRMKEY-CHANGE_IDOptional: No
Call by Reference: Yes
TABLES Parameters details for CRS_SALES_KEY_CONVERT
RETURN - Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TI_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)
TI_SDKEY - Key in Sales and Distribution Document
Data type: BAPISDKEYOptional: No
Call by Reference: No ( called with pass by value option)
TO_KEYINFO - BAPI Structure: Key Information
Data type: BAPICRMKEYOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRS_SALES_KEY_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_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lv_i_request | TYPE BAPIFLAG-BAPIFLAG, " SPACE | |||
lv_i_upload_id | TYPE BAPICRMDH2-REF_ID, " | |||
lt_ti_sfa_keys | TYPE STANDARD TABLE OF BAPICRMSFK, " | |||
lt_ti_sdkey | TYPE STANDARD TABLE OF BAPISDKEY, " | |||
lv_i_upload_stat | TYPE BAPICRMDH2-UPLOADSTAT, " | |||
lt_to_keyinfo | TYPE STANDARD TABLE OF BAPICRMKEY, " | |||
lv_i_change_id | TYPE BAPICRMKEY-CHANGE_ID. " |
  CALL FUNCTION 'CRS_SALES_KEY_CONVERT' "NOTRANSL: Konvertierung der Tabelle BAPISDKEY in BAPICRMKEY und BAPICRMR3 |
EXPORTING | ||
I_REQUEST | = lv_i_request | |
I_UPLOAD_ID | = lv_i_upload_id | |
I_UPLOAD_STAT | = lv_i_upload_stat | |
I_CHANGE_ID | = lv_i_change_id | |
TABLES | ||
RETURN | = lt_return | |
TI_SFA_KEYS | = lt_ti_sfa_keys | |
TI_SDKEY | = lt_ti_sdkey | |
TO_KEYINFO | = lt_to_keyinfo | |
. " CRS_SALES_KEY_CONVERT |
ABAP code using 7.40 inline data declarations to call FM CRS_SALES_KEY_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."SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_request). | ||||
DATA(ld_i_request) | = ' '. | |||
"SELECT single REF_ID FROM BAPICRMDH2 INTO @DATA(ld_i_upload_id). | ||||
"SELECT single UPLOADSTAT FROM BAPICRMDH2 INTO @DATA(ld_i_upload_stat). | ||||
"SELECT single CHANGE_ID FROM BAPICRMKEY INTO @DATA(ld_i_change_id). | ||||
Search for further information about these or an SAP related objects