SAP CRS_SALES_EXTRACT_DIMA Function Module for NOTRANSL: Accelerated Extractor for Sales Documents - DIMa Header Compare









CRS_SALES_EXTRACT_DIMA is a standard crs sales extract dima 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: Accelerated Extractor for Sales Documents - DIMa Header Compare 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 extract dima FM, simply by entering the name CRS_SALES_EXTRACT_DIMA into the relevant SAP transaction such as SE37 or SE38.

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



Function CRS_SALES_EXTRACT_DIMA 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_EXTRACT_DIMA'"NOTRANSL: Accelerated Extractor for Sales Documents - DIMa Header Compare
  EXPORTING
   I_BAPICRMDH1 =  "
*  I_DO_NOT_SEND_DATA =  "Checkbox
*  I_OBJ_NAME =  "Object name for download
*  I_CALL_MODE =  "Synchronous or Asynchronous Call of Save BAPIs
*  I_RECEIVE_MODULE =  "Name of Function Module

 IMPORTING
   E_STATUS =  "Extractor Processing Status

TABLES
*  TI_TABLES =  "
*  TI_RANGE =  "
*  TI_RELATION =  "
*  TO_VBAK =  "
.



IMPORTING Parameters details for CRS_SALES_EXTRACT_DIMA

I_BAPICRMDH1 -

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

I_DO_NOT_SEND_DATA - Checkbox

Data type: ORDER_VIEW-HEADER
Optional: Yes
Call by Reference: Yes

I_OBJ_NAME - Object name for download

Data type: BAPICRMOBJ-OBJ_NAME
Optional: Yes
Call by Reference: Yes

I_CALL_MODE - Synchronous or Asynchronous Call of Save BAPIs

Data type: CRM_PARA-CALL_MODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_RECEIVE_MODULE - Name of Function Module

Data type: TFDIR-FUNCNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CRS_SALES_EXTRACT_DIMA

E_STATUS - Extractor Processing Status

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

TABLES Parameters details for CRS_SALES_EXTRACT_DIMA

TI_TABLES -

Data type: CRMTABLES
Optional: Yes
Call by Reference: Yes

TI_RANGE -

Data type: CRMSELSTR
Optional: Yes
Call by Reference: Yes

TI_RELATION -

Data type: CRMRELA
Optional: Yes
Call by Reference: Yes

TO_VBAK -

Data type: VBAK
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for CRS_SALES_EXTRACT_DIMA 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_status  TYPE BAPICRMEXP-STATUS_EXT, "   
lt_ti_tables  TYPE STANDARD TABLE OF CRMTABLES, "   
lv_i_bapicrmdh1  TYPE BAPICRMDH1, "   
lt_ti_range  TYPE STANDARD TABLE OF CRMSELSTR, "   
lv_i_do_not_send_data  TYPE ORDER_VIEW-HEADER, "   
lv_i_obj_name  TYPE BAPICRMOBJ-OBJ_NAME, "   
lt_ti_relation  TYPE STANDARD TABLE OF CRMRELA, "   
lt_to_vbak  TYPE STANDARD TABLE OF VBAK, "   
lv_i_call_mode  TYPE CRM_PARA-CALL_MODE, "   
lv_i_receive_module  TYPE TFDIR-FUNCNAME. "   

  CALL FUNCTION 'CRS_SALES_EXTRACT_DIMA'  "NOTRANSL: Accelerated Extractor for Sales Documents - DIMa Header Compare
    EXPORTING
         I_BAPICRMDH1 = lv_i_bapicrmdh1
         I_DO_NOT_SEND_DATA = lv_i_do_not_send_data
         I_OBJ_NAME = lv_i_obj_name
         I_CALL_MODE = lv_i_call_mode
         I_RECEIVE_MODULE = lv_i_receive_module
    IMPORTING
         E_STATUS = lv_e_status
    TABLES
         TI_TABLES = lt_ti_tables
         TI_RANGE = lt_ti_range
         TI_RELATION = lt_ti_relation
         TO_VBAK = lt_to_vbak
. " CRS_SALES_EXTRACT_DIMA




ABAP code using 7.40 inline data declarations to call FM CRS_SALES_EXTRACT_DIMA

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 STATUS_EXT FROM BAPICRMEXP INTO @DATA(ld_e_status).
 
 
 
 
"SELECT single HEADER FROM ORDER_VIEW INTO @DATA(ld_i_do_not_send_data).
 
"SELECT single OBJ_NAME FROM BAPICRMOBJ INTO @DATA(ld_i_obj_name).
 
 
 
"SELECT single CALL_MODE FROM CRM_PARA INTO @DATA(ld_i_call_mode).
 
"SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_i_receive_module).
 


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!