SAP ABAP Data Element ST04N_PARAMETERSTRING (Parameter string for report)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-CCM-MON-ORA (Application Component) Oracle Database Monitors
     ⤷ S_DBMON_ORA_COCKPIT (Package) Database Monitor for Oracle in Cockpit Framework
Basic Data
Data Element ST04N_PARAMETERSTRING
Short Description Parameter string for report  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CHAR255    
Data Type CHAR   Character String 
Length 255    
Decimal Places 0    
Output Length 255    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Parameters 
Medium 15 Parameters 
Long 20 Parameter String 
Heading 16 Parameter String 
Documentation

Definition

String can be used optionally to define fix parameters for the report that has to be called.

Use

For a submonitor of type report define the parameters by the following syntax:

<parametername1> <kind1> <sign1> <option1> "<low-value1>" "<highvalue1>"; <parametername2> <kind2> <sign2> <option2> '<low-value2>' '<highvalue2>';

  • parametername is the name of the parameter or select-option
  • kind is: P for parameter, S for select-options
  • sign is: I for inclusive, E for exclusive (only relevant for select-options, ignored for parameters)
  • option is the operation know for range tabs, eg.: EQ, BT, NE, ...
  • the low- and high value have to be specified between quotes . The high value is only relevant for select-options and will be ignored for parameters

When more than 1 parameters have to be specified, you have to separate them by a ';'

For a submonitor of type "integrated submonitor" define the parameters by the following syntax:

<start subscreen>; <init function module name>; <OK-Code function module name>; <free resource function module name>

Example:

0100; ZZORAEX2_INIT; ZZORAEX2_OKCODE_HANDLER; ZZORAEX2_FREE

  • start subscreen is the number of the first subscreen that has to be processed within your submonitor
  • init function module: This function module is intended to initialize global data (within the function group / module pool) of the submonitor, set a PF Status for the first dynpro, read initial data from oracle views
  • OK Code function module: This function module is needed to handle the OK-Codes within the submonitor because OK-Codes are passed by SAP standard logic to the main dynpro (not to the submonitors subscreen). The main monitor passes all OK-Codes (indirectly) to your OK-Code function module. Parameters
    • OK-Code (Import) - The OK-Code that was initiated by user interaction
    • Next subscreen (Export) - The next aubmonitor subscreen, that has to be processed
    • Flag "OK-Code handled by submonitor" (Export) - This flag indicates to the main monitor that the OK-Code was handled by the submonitor
  • "free resource function module" is optional. - This function module is intented to free all control related resources of the submonitor (used e.g. when submonitor is terminated or another submonitor is called)

Dependencies

Example

  • SO_XYZ S I BT 'fromvalue' 'tovalue'
  • PAHI_UPD P I EQ ' ' ' '; IPARTYPE P I EQ 'D' ' '

History
Last changed by/on SAP  20070813 
SAP Release Created in 700