SAP BWSO_PLANNER_READ Function Module for









BWSO_PLANNER_READ is a standard bwso planner read 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 bwso planner read FM, simply by entering the name BWSO_PLANNER_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: BW03
Program Name: SAPLBW03
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BWSO_PLANNER_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 'BWSO_PLANNER_READ'"
EXPORTING
* DATE_IN = "Field of Type DATS
* FUNCTION = "Not More Closely Defined Area, Possibly Used for Patchlevels

IMPORTING
TITLE = "SAPoffice WWW: Error text
OBJECTS_TITLE = "SAPoffice WWW: Frame key
DATE_FROM = "Field of Type DATS

TABLES
DAYPATTERN = "Days in the Display of Planner
OBJECTS = "Planner Object List
EVENTS = "Planner Event List
.



IMPORTING Parameters details for BWSO_PLANNER_READ

DATE_IN - Field of Type DATS

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

FUNCTION - Not More Closely Defined Area, Possibly Used for Patchlevels

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

EXPORTING Parameters details for BWSO_PLANNER_READ

TITLE - SAPoffice WWW: Error text

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

OBJECTS_TITLE - SAPoffice WWW: Frame key

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

DATE_FROM - Field of Type DATS

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

TABLES Parameters details for BWSO_PLANNER_READ

DAYPATTERN - Days in the Display of Planner

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

OBJECTS - Planner Object List

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

EVENTS - Planner Event List

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

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

DATA:
lv_title  TYPE BW02_KEY, "   
lv_date_in  TYPE DATS, "   
lt_daypattern  TYPE STANDARD TABLE OF BWPLPAT, "   
lt_objects  TYPE STANDARD TABLE OF BWPLOBJ, "   
lv_function  TYPE BW02_TASK, "   
lv_objects_title  TYPE BW02_KEY, "   
lt_events  TYPE STANDARD TABLE OF BWPLEVT, "   
lv_date_from  TYPE DATS. "   

  CALL FUNCTION 'BWSO_PLANNER_READ'  "
    EXPORTING
         DATE_IN = lv_date_in
         FUNCTION = lv_function
    IMPORTING
         TITLE = lv_title
         OBJECTS_TITLE = lv_objects_title
         DATE_FROM = lv_date_from
    TABLES
         DAYPATTERN = lt_daypattern
         OBJECTS = lt_objects
         EVENTS = lt_events
. " BWSO_PLANNER_READ




ABAP code using 7.40 inline data declarations to call FM BWSO_PLANNER_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



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!