SAP SO_OBJECT_READ_FLAG_CHANGE Function Module for

Search SAP Function Modules

SO_OBJECT_READ_FLAG_CHANGE is a standard so object read flag change 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 so object read flag change FM, simply by entering the name SO_OBJECT_READ_FLAG_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function SO_OBJECT_READ_FLAG_CHANGE 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 'SO_OBJECT_READ_FLAG_CHANGE'"
  EXPORTING
   FORWARDER =  "Object: Forwarder
   OBJECT_ID =  "Object: ID
   OWNER =  "Object: Owner of folders (recipient)
   READ_FLAGS =  "Flags which should be read

EXCEPTIONS
   COMMUNICATION_FAILURE = 1    FORWARDER_NOT_EXIST = 2    OBJECT_NOT_EXIST = 3    PARAMETER_ERROR = 4    OWNER_NOT_EXIST = 5    SYSTEM_FAILURE = 6    X_ERROR = 7    ENQUEUE_ERROR = 8 

.

IMPORTING Parameters details for SO_OBJECT_READ_FLAG_CHANGE

FORWARDER - Object: Forwarder

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

OBJECT_ID - Object: ID

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

OWNER - Object: Owner of folders (recipient)

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

READ_FLAGS - Flags which should be read

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

EXCEPTIONS details

COMMUNICATION_FAILURE -

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

FORWARDER_NOT_EXIST - Forwarder does not exist

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

OBJECT_NOT_EXIST - Object does not exist

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

PARAMETER_ERROR - Incorrect entry of data

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

OWNER_NOT_EXIST - The owner/recipient does not exist

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

SYSTEM_FAILURE -

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

X_ERROR - Other error

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

ENQUEUE_ERROR - Object still blocked (SOFM/SOOD/SOOS)

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

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

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