SAP CRM_STATUS_READ_MULTI Function Module for









CRM_STATUS_READ_MULTI is a standard crm status read multi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 crm status read multi FM, simply by entering the name CRM_STATUS_READ_MULTI into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_STATUS_READ_MULTI 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 'CRM_STATUS_READ_MULTI'"
  EXPORTING
*  CLIENT = SY-MANDT "Client
*  ONLY_ACTIVE = ' ' "'Transfer Active Statuses Only' Flag
*  ALL_IN_BUFFER = ' ' "
*  GET_CHANGE_DOCUMENTS = ' ' "
*  NO_BUFFER_FILL = ' ' "

TABLES
*  OBJNR_TAB =  "Table of Object Numbers
   STATUS =  "
*  JSTO_TAB =  "
*  JCDO_TAB =  "
*  JCDS_TAB =  "
.



IMPORTING Parameters details for CRM_STATUS_READ_MULTI

CLIENT - Client

Data type: SY-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

ONLY_ACTIVE - 'Transfer Active Statuses Only' Flag

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

ALL_IN_BUFFER -

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

GET_CHANGE_DOCUMENTS -

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

NO_BUFFER_FILL -

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

TABLES Parameters details for CRM_STATUS_READ_MULTI

OBJNR_TAB - Table of Object Numbers

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

STATUS -

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

JSTO_TAB -

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

JCDO_TAB -

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

JCDS_TAB -

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

Copy and paste ABAP code example for CRM_STATUS_READ_MULTI 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_client  TYPE SY-MANDT, "   SY-MANDT
lt_objnr_tab  TYPE STANDARD TABLE OF CRM_JSTO_PRE, "   
lt_status  TYPE STANDARD TABLE OF CRM_JEST, "   
lv_only_active  TYPE CRM_JEST-INACT, "   SPACE
lt_jsto_tab  TYPE STANDARD TABLE OF CRM_JSTO, "   
lv_all_in_buffer  TYPE SY-DATAR, "   SPACE
lt_jcdo_tab  TYPE STANDARD TABLE OF CRM_JCDO, "   
lv_get_change_documents  TYPE SY-DATAR, "   SPACE
lt_jcds_tab  TYPE STANDARD TABLE OF CRM_JCDS, "   
lv_no_buffer_fill  TYPE SY-DATAR. "   SPACE

  CALL FUNCTION 'CRM_STATUS_READ_MULTI'  "
    EXPORTING
         CLIENT = lv_client
         ONLY_ACTIVE = lv_only_active
         ALL_IN_BUFFER = lv_all_in_buffer
         GET_CHANGE_DOCUMENTS = lv_get_change_documents
         NO_BUFFER_FILL = lv_no_buffer_fill
    TABLES
         OBJNR_TAB = lt_objnr_tab
         STATUS = lt_status
         JSTO_TAB = lt_jsto_tab
         JCDO_TAB = lt_jcdo_tab
         JCDS_TAB = lt_jcds_tab
. " CRM_STATUS_READ_MULTI




ABAP code using 7.40 inline data declarations to call FM CRM_STATUS_READ_MULTI

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 MANDT FROM SY INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
 
 
"SELECT single INACT FROM CRM_JEST INTO @DATA(ld_only_active).
DATA(ld_only_active) = ' '.
 
 
"SELECT single DATAR FROM SY INTO @DATA(ld_all_in_buffer).
DATA(ld_all_in_buffer) = ' '.
 
 
"SELECT single DATAR FROM SY INTO @DATA(ld_get_change_documents).
DATA(ld_get_change_documents) = ' '.
 
 
"SELECT single DATAR FROM SY INTO @DATA(ld_no_buffer_fill).
DATA(ld_no_buffer_fill) = ' '.
 


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!