SAP CRM_STATUS_READ Function Module for Read Object Status (JSTO and JEST)

Search SAP Function Modules

CRM_STATUS_READ is a standard crm status read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Object Status (JSTO and JEST) 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 crm status read FM, simply by entering the name CRM_STATUS_READ 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 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'"Read Object Status (JSTO and JEST)
  EXPORTING
*  CLIENT = SY-MANDT "Client
   OBJNR =  "Object Number
*  ONLY_ACTIVE = ' ' "'Transfer Active Statuses Only' Flag

 IMPORTING
   OBTYP =  "Object type
   STSMA =  "Status Profile
   STONR =  "Status number
   ET_JEST_BUF =  "Status Table in Accordance with CRMBSVA Status Management

TABLES
*  STATUS =  "Table of Individual Statuses for the Object

EXCEPTIONS
   OBJECT_NOT_FOUND = 1 

.

IMPORTING Parameters details for CRM_STATUS_READ

CLIENT - Client

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

OBJNR - Object Number

Data type: CRM_JSTO-OBJNR
Optional: No
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)

EXPORTING Parameters details for CRM_STATUS_READ

OBTYP - Object type

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

STSMA - Status Profile

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

STONR - Status number

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

ET_JEST_BUF - Status Table in Accordance with CRMBSVA Status Management

Data type: CRMT_JEST_BUF_TAB
Optional: No
Call by Reference: Yes

TABLES Parameters details for CRM_STATUS_READ

STATUS - Table of Individual Statuses for the Object

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

EXCEPTIONS details

OBJECT_NOT_FOUND - Status Object Not Found

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

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

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