Explit 'ENTER' in POV

Hi Experts,
Is it possible to explit 'ENTER' command in POV, so that PBO will be triggerred and my problem will be solved.
Any inputs are appreciated.
Regards
Sravan

Keshav.T wrote:
> Read [SUPPRESS DIALOG|http://help.sap.com/abapdocu_70/en/ABAPSUPPRESS.htm]
@Keshav: The OP wants to trigger PBO from the POV module. How does SUPPRESS DIALOG help? I don't get it
@Sravana: If you give more details about your problem, may be we can provide you with the solution.
BR,
Suhas

Similar Messages

Smartview webf run time prompts upon submit are not picking up from the POV

Hi ,
I am in Planning 11.1.2.1 and using Smartview 11.1.2.1.103. After connecting to Planning Webform from Smartview, i am saving a composite form which should launch a Business Rule with run time prompts attached to the webform upon submit. The business rules are running with default run time prompts and it is not picking up the members from the POV ... is there a way to make it pick up the members from POV into the run time prompts upon saving it ? so far the workaround is to initiate the business rule from the planning tab in smartview .. any thoughts on this ? cheers

I found a known issue for smart view in 11.1.2.1 read me doc
11075506
When you open a data form in Smart View, if a business rule is directly attached to a composite data form that is set to Use Members on Data Form and Hide Prompt, the runtime prompt values are not picked up. Instead, the Runtime Prompt dialog box is displayed, and the user is prompted to enter a value.
Good Luck

Problems with entering data

Hi all,
I have prepared several data forms and grids, but I'm not able to enter data. All cells are red colored with cell status "INVALID".
Does anybody know why is that?
Thanks,
Vlado

The red color in cells indicate that you have chosen a Point Of View (POV) which is invalid for the accounts viewed on the form.
Example 1: Suppose you have selected several accounts some of them having intercompany analysis and then select an ICP member, accounts not supporting intercompany analysis will be displayed as red, while accounts supporting ICP analysis, will display as yellow (provided you have selected base members for all other POV dimensions)
Example 2: Suppose you use Custom 3 to hold both Channel and Grade analysis with different hierarchy subtrees (example drawn from COMMA sample app). Note that the [None] member belongs only in the Grades hierarchy. When you choose to view the OperatingIncome account which uses TotalChannels as Custom3TopMember (the hierarchy which does not contain the [None] member) with Custom 3 = [None], again you will see the invalid cells.
Kostas

Hiding the locked Grid POV's in HFR

Hello Experts,
I have a HFR report wherein we have two grids and each one is being displayed based on the input for a User point of view provided by the User. e.g. When the user enters "Y" for "Flag" Dimension Grid 1 is being displayed and Grid 2 when the user enters "N". There are many Grid POVs and all the Grid POV's except for one has been locked for both the grids. The unlocked POV's for both the grids are different. e.g. The active Grid POV for Grid 1 is "X" and for Grid 2 is "Y.
How do i hide the locked Grid POV's when i run and view the report in Workspace?
It would be really gr8 if anyone helps me out on this.
Thanks in advance
Ravi B

Hi Ravi,
The dimensions which one dont specify in the grid row/column/pages, are displayed either as Grid POV or User POV.
So instead of locking that dimesion selection in the grid POV, place that dimension in the grid and then hide the corresponding row/column.
Regards,
Rahul

SmartView POV Manager in Power Point

Hi All,
I'm trying to past and copy data from a SmartView report developed in Excel to a Power Point slide.
The data are correctly copied and dispayed but every time I past a figure SmartView generates a new Query displayed in the Power Point POV Manager.
Even if I cancel the pasted figure the Query remains in the POV Manager , this means that I have a lot of these query that I don't use anymore.
How can I delete old query that are no longer used?
Thank you in advance
Giacomo

Hi,
What version are you connecting to V11, 9.3.x ?
What source are you connecting to Planning, Essbase ?
An example in V11 would you enter adhoc analysis mode and this will return the default POV, you should also get a floating toolbar with POV on it, you can select one of the dimensions and then select .... and it will open the member selection window where you can choose a member.
In 11 to use the POV manager, right click the application you are connected to and choose add to favourites, then go to the POV manager, there should be Active in the right hand window, double click it and a connection should appear, double click the connection and a POV window should be displayed, now you can click on a dimension and click the member selector and you will be able to select a member.
It should be around the same sort of process of other versions, not exactly the same I know.
Cheers
John
http://john-goodwin.blogspot.com/

Capital asset global assumption can not enter data

Hi,
I created a generic dimension for currency and add it to Oracle CAPEX. Then the global assumption form in Oracle can't be entered data any more. Please help.

First of all, adding dimensions is a big change in any application. I hope you are trying to setup a new app and need a dimension based on requirements... But if you were doing this and I was client, I might be running towards a train..You should never add a dimension without completely understanding the impact on current application including webforms, calculations and reports.
The default global assumption form in CAPEX in based only on the dimensions that are created by default in CAPEX application. Now, if you add a dimension, you will need to go to all forms and add member/s from your new dimension to one of either row/column/page/POV in the webform. Go to webform and you will find selection for your new dimension in POV where you need to add a member. Along with these, there are lot of formulas in CAPEX that depend on default members in dimension (No Entity, etc) which you will need to change to include the newly added dimension to make your calculations work correctly.
Just an opinion.... you either need someone to guide you or have someone with experience set this up for you.
HTH

Alias names couldn't be shown on Prompt window or POV

hi All.
We have some financial reports , display this reports on workspace. But we want to change dimension member from prompt option window or POV. Pop up window shows us only members “Name”s, we can not see member alias.
hyperion Financial Reporting 9 , version 9.3.1.354
hyperion planning 9.3.1.1.10.4
thanks

Hi ,
Follow below procedure will help you to display member alias in POV.
1) In workspace File > Preferences > Financial Reporting.
2) From User Point of View, click General tab , select Setup Members. The Setup User POV dialog is displayed.
3) Select data sources from Database Connection.
4) If prompted enter your log on credentials, click OK
5) Select the member label you prefer from Display Member Label. If you wish to see Alias name in POV window then select *'Default'*
6) Click OK to save your current changes and return to the repository screen.

Problem with USER POV

Hello All
Whenever I change the User Point of View for 1 report , all the other reports for that user get the same User Point of view.
I am using Hyperion 11 EPMA fusion edition FR.
Does any1 has solution to this ?
Thanks and Happy new year to all :-)
Pooja

Sorry for the delay. This will be somewhat of a lengthy reply.
You will need to build a "trigger" into the report - allowing the conditional suppression to display the correct columns.
1. You will want to enter 1 column, use CurrentPOV for "Year" and "Period". Mark this column as "Hide Always". For this column, enter conditional suppression that will look like the following:
- (Advanced Options) Suppress column if "Member Name" for "Period" ("Period" being the dimension that includes the quarter members) "equals" "Quarter1".
2. I will make the assumption that the column just entered is Column "A".
3. Now enter 1 more column - column "B". This will be the first column to show on the report, and will be CurrentPOV for "Year" and "Period".
4. Finally enter 2 more columns.
- For the first column - column "C", Make the "Year" dimension the same as that in the POV, and for the "Period" dimension use the RelativeMember function and "Offset" = -1.
- For the second column - column "D", Force the "Year" dimension to use the RelativeMember function and "Offset"= -1, and do the same for "Period", "Offset" = -1.
5. Now you will need to enter the conditional suppression for the 2 columns just entered.
- For Column "C", use conditional suppression to do the following:
(Advanced Options) Suppress column if "Data Values in column" "A" "equals" "Suppressed".
- For Column "D", use conditional suppression to do the following:
(Advanced Options) NOT Suppress column if "Data Values in column" "C" "equals" "Suppressed". The key here being the Not, be sure to check that box.
Basically, this will look at what the user selects for "Period".
- If they select Quarter 1, it shows the column for Quarter 4 and prior year.
- If they select Quarters 2-4, then the report will show the column for prior quarter, and current year.
Let me know if you run into issues with this.

Cursor positiong at POV

Hi,
my customer's requirement is to move a cursor at the end of PROCESS ON VALUE REQUEST on one subscreen field to another field.
Details: during sales order item creation (VA01) the cursor is positioned automatically at the field for Material (program SAPMV45A, subscreen 4900). After a matchcode is triggered the program goes through POV on the screen (module RV45A_MABNR_VALUES) and displays it afterwards - without going through PBO or PAI. The request is to move the cursor automatically to the "Quantity" field after material is selected (that means at the end of POV on material field). The reason: a call center agent has to be able to enter many sales order items as quickly as possible u2013 from their point of view the reduction of manual cursor positioning would be very helpful.
I've already tried to add following modifications at the end of module RV45A_MABNR_VALUES:
-     SET CURSOR u2013 it doesn't work, since it's not PBO
-     SET SCREEN u2026/ LEAVE TO SCREEN u2026 - it's not allowed since 4900 is a subscreen
-     SUPPRESS DIALOG - it doesn't work neither
Even if they worked, I wouldn't be happy with these solutions, since they trigger PBO / PAI again, which could be time consuming.
My idea has been to find something similar to the function module DYNP_VALUES_UPDATE (screen fields update w/o PBO) which would enable cursor positioning too, but I couldnt' find it.
Any ideas?
Edited by: Tomislav Sesnic on Apr 27, 2009 11:42 AM

Hi,
i used the same to get F4 help for table control fields according to cursotr position.
*F4 Help
PROCESS ON VALUE-REQUEST.
FIELD wa_zcxref_classes-atwrt MODULE f4_choose_batch_values.
MODULE f4_choose_batch_values INPUT.
* getting the cursor line in Table Control
GET CURSOR FIELD selfield LINE selline.
selindex = tc_batch-top_line + selline - 1.
* Fetching the Characteristic Name in the cursor Position
READ TABLE t_zcxref_classes INTO wa_zcxref_classes
                            INDEX selindex.
* Movinig the characteristic name to FM to fetch the possible enteries
w_char_old-atnam = wa_zcxref_classes-characteristic.
CALL FUNCTION 'CHAR_VALUE_POSSIBLE_ENTRIES'
    EXPORTING
      char_imp            = w_char_old
      flg_display_imp     = ' '
    IMPORTING
      char_val_exp        = wa_zcxref_classes-atwrt
      flg_val_changed_exp = w_flg_val_changed_exp
    EXCEPTIONS
      not_found           = 1
      close_error         = 2
      set_error           = 3
      no_authority        = 4
      failed              = 5
      OTHERS              = 6.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDMODULE.                 " F4_CHOOSE_BATCH_VALUES INPUT
Regards,
Prabhudas

POV Manager

How do you save a POV once entered for using Ad Hoc reporting?

There are two ways that an alias table can be set in Smart View today: at the connection and at the session.
The connection alias table is set using the connection manager. This also acts as the starting session alias table for any new session for this connection.
The session alias table is set using the menu or ribbon.
The POV Manager currently uses the connection alias table as it's point of reference.
The POV toolbar uses the session alias table as it's point of reference.
With that said, there is a bug that alias members do not persist in the POV Manager.

Screen value in POV

Hi All,
There is a selection screen in which i am entreing matnr and based on the matnr i have to provide F4 help.I am using a function module to show F4 help.I need the matnr entered on the screen as input the function module.The FM is in Process-on-value request module.How to get the matnr entered in the selection screen in POV module?
Thanks,
Rakesh.

Hi,
Hi,
At POV event of module-pool place :-
Field <fieldname for F4 help> module <module name for Coding>.
At SE38:-
This is above module created at SE38 by double clicking on it.
Module <module name for Coding>_input.
data: begin of help_item occurs 0,
posnr type vbap-posnr,
matnr type vbap-matnr,
arktx type vbap-arktx,
end of help_item.
data: dynfields type table of dynpread with header line.
dynfields-fieldname = '<Screenfieldname ie p_matnr>'.
append dynfields.
call function 'DYNP_VALUES_READ'
exporting
dyname = sy-cprog
dynumb = sy-dynnr
translate_to_upper = 'X'
tables
dynpfields = dynfields.
read table dynfields with key fieldname = '<Screenfieldname ie p_matnr'>.
p_vbeln = dynfields-fieldvalue.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
exporting
input = '<Screenfieldname ie matnr>'
importing
output = '<Screenfieldname ie matnr'>.
select matnr maktx into table help_item
from makt where matnr = 'Screenfieldname ie matnr'.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
exporting
retfield = '<Databasefieldname ie maktx>'
dynprofield = '<Screenfieldname ie p_matnr>'
dynpprog = sy-cprog
dynpnr = sy-dynnr
value_org = 'S'
tables
value_tab = help_item.
Regards,
Vijay Mekala

Profile values for specifically if enter section name and product name

I have tried to get Profile values with the following query,
SELECT *
FROM fnd_profile_options_vl po,
fnd_profile_option_values pov,
fnd_user usr,
fnd_application app,
fnd_responsibility rsp,
fnd_nodes svr,
hr_operating_units org
WHERE 1 = 1
AND pov.application_id = po.application_id
AND pov.profile_option_id = po.profile_option_id
AND usr.user_id(+) = pov.level_value
AND rsp.application_id(+) = pov.level_value_application_id
AND rsp.responsibility_id(+) = pov.level_value
AND app.application_id(+) = pov.level_value
AND svr.node_id(+) = pov.level_value
AND org.organization_id(+) = pov.level_value
Suppose I need to populate the profile values for specifically if I enter section name and product name.
How can I do that ???

Hussein Sawwan wrote:
Thanks, I have gone through the documentation,I can get all profile values.But how can I get the profile values and names that is related to/affects a particular product.
Is there any connection between products/items with profile option.No. However, you may run the same queries using the follows:
For example ..
For GL --> PROFILE_OPTION_NAME like '%GL%'
For AR --> PROFILE_OPTION_NAME like '%AR%'
And so on.
Please note that the above will not return all profile options that affect (or related to) specific module.
You can also get the list of profile option which are set at the Application/Responsibility level.
Thanks,
Hussein
>
Thanks, I have gone through the documentation,I can get all profile values.But how can I get the profile values and names that is related to/affects a particular product.
Is there any connection between products/items with profile option.No. However, you may run the same queries using the follows:
For example ..
For GL --> PROFILE_OPTION_NAME like '%GL%'
For AR --> PROFILE_OPTION_NAME like '%AR%'
And so on.
Please note that the above will not return all profile options that affect (or related to) specific module.
You can also get the list of profile option which are set at the Application/Responsibility level.
Thanks,
Hussein
Hussein ,
Can I use following query to retrieve the profile values for an item with m.msite_id =10218 AND s.section_id =10591 and i.organization_id = 204 and i.inventory_item_id =66567
select distinct *
FROM fnd_profile_options_vl po,
fnd_profile_option_values pov,
fnd_user usr,
fnd_application app,
fnd_responsibility rsp,
fnd_nodes svr,
hr_operating_units org,
ibe_msites_tl m,
ibe_dsp_sections_tl s,
mtl_system_items_b i
where
pov.application_id = po.application_id
AND pov.profile_option_id = po.profile_option_id
AND usr.user_id(+) = pov.level_value
AND rsp.application_id(+) = pov.level_value_application_id
AND rsp.responsibility_id(+) = pov.level_value
AND app.application_id(+) = pov.level_value
AND svr.node_id(+) = pov.level_value
AND org.organization_id(+) = pov.level_value
and m.msite_id =10218
AND s.section_id =10591
and i.organization_id = 204
and i.inventory_item_id =66567
Anything wrong here???
Thanks

Want help in creating pov and poh in module pool

i want to create process on help and process on value request.
which function modules to use and how use them
then i want put icon symbols over push buttons.
can u please send me this information also.
i am new to screen programming .

krishna,
For POV
Input Help in Dialog Modules
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These all have the prefix F4IF_. The most important are:
F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT DEMO_DYNPRO_F4_HELP_MODULE.
TYPES: BEGIN OF VALUES,
         CARRID TYPE SPFLI-CARRID,
         CONNID TYPE SPFLI-CONNID,
       END OF VALUES.
DATA: CARRIER(3) TYPE C,
      CONNECTION(4) TYPE C.
DATA: PROGNAME LIKE SY-REPID,
      DYNNUM   LIKE SY-DYNNR,
      DYNPRO_VALUES TYPE TABLE OF DYNPREAD,
      FIELD_VALUE LIKE LINE OF DYNPRO_VALUES,
      VALUES_TAB TYPE TABLE OF VALUES.
CALL SCREEN 100.
MODULE INIT OUTPUT.
PROGNAME = SY-REPID.
DYNNUM   = SY-DYNNR.
CLEAR: FIELD_VALUE, DYNPRO_VALUES.
FIELD_VALUE-FIELDNAME = 'CARRIER'.
APPEND FIELD_VALUE TO DYNPRO_VALUES.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE VALUE_CARRIER INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
       EXPORTING
            TABNAME           = 'DEMOF4HELP'
            FIELDNAME         = 'CARRIER1'
            DYNPPROG          = PROGNAME
            DYNPNR            = DYNNUM
            DYNPROFIELD       = 'CARRIER'.
ENDMODULE.
MODULE VALUE_CONNECTION INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
       EXPORTING
            DYNAME                   = PROGNAME
            DYNUMB                   = DYNNUM
            TRANSLATE_TO_UPPER       = 'X'
       TABLES
            DYNPFIELDS               = DYNPRO_VALUES.
READ TABLE DYNPRO_VALUES INDEX 1 INTO FIELD_VALUE.
SELECT CARRID CONNID
    FROM SPFLI
    INTO CORRESPONDING FIELDS OF TABLE VALUES_TAB
    WHERE CARRID = FIELD_VALUE-FIELDVALUE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
       EXPORTING
            RETFIELD         = 'CONNID'
            DYNPPROG         = PROGNAME
            DYNPNR           = DYNNUM
            DYNPROFIELD      = 'CONNECTION'
            VALUE_ORG        = 'S'
       TABLES
            VALUE_TAB        = VALUES_TAB.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The input fields have been adopted from the program fields CARRIER and CONNECTION. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
MODULE INIT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON VALUE-REQUEST.
FIELD CARRIER MODULE VALUE_CARRIER.
FIELD CONNECTION MODULE VALUE_CONNECTION.
When the user chooses input help for the individual fields, the following is displayed:
For the Airline field, the POV module VALUE_CARRIER is called. The function module F4IF_FIELD_VALUE_REQUEST displays the input help for the component CARRIER1 of the structure DEMOF4HELP from the ABAP Dictionary, namely the search help DEMOF4DE. The users selection is returned to the screen field CARRIER.
For the Flight number field, the POV module VALUE_CONNECTION is called. The function module DYNP_VALUE_READ transports the value of the screen field CARRIER into the program. The program then reads the corresponding values from the database table SPFLI into the internal table VALUES_TAB using a SELECT statement, and passes the internal table to F4IF_INT_TABLE_VALUE_REQUEST. This displays the internal table as input help, and places the users selection into the screen field CONNECTION.
For POH
Field Help
There are three ways of displaying field help for screen elements:
Data Element Documentation
If you place a field on the screen in the Screen Painter by copying a ABAP Dictionary field, the corresponding data element documentation from the ABAP Dictionary is automatically displayed when the user chooses field help (as long as the help has not been overridden in the screen flow logic).
For further information about creating data element documentation, refer to data elements.
Data Element Supplement Documentation
If the data element documentation is insufficient, you can expand it by writing a data element supplement
Data element supplement documentation contains the heading Definition, as well as the following others:
Use
Procedure
Examples
Dependencies
To create data element supplement documentation for a screen, choose Goto ® Documentation ® DE supplement doc. from the element list of the screen. A dialog box appears in which the system proposes a number as the identified for the data element supplement. You can then enter help texts for the above headings using the SAPscript editor.
Data element supplement documentation created in this way is program- and screen-specific. Any data element supplement documentation created in the ABAP Dictionary with the same number is overridden by the screen-specific documentation. You can link existing data element supplement documentation created in the ABAP Dictionary with a screen field by using the table THLPF. To do this, crate a new row in THLPF containing the following data: Program name, screen name, field name, and number of the data element supplement documentation.
To display data element supplement documentation, you must code the following screen flow logic in the POH event:
PROCESS ON HELP-REQUEST.
FIELD is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
       VAR(4),
       INT TYPE I,
       LINKS TYPE TABLE OF TLINE,
       FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
    WHEN 1.
    VAR = '0100'.
    WHEN 2.
    VAR = '0200'.
    INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
       EXPORTING
            DOKLANGU                      = SY-LANGU
            DOKTITLE                      = TEXT-002
            CALLED_FOR_TAB                = 'DEMOF1HELP'
            CALLED_FOR_FIELD              = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
       EXPORTING
            DOKCLASS                      = 'TX'
            DOKLANGU                      = SY-LANGU
            DOKNAME                       = 'DEMO_FOR_F1_HELP'
            DOKTITLE                      = TEXT-003
       TABLES
            LINKS                         = LINKS.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:
The screen fields DEMOf1HELP-FIELD1 and DEMOF1HELP-FIELD2 from the ABAP Dictionary and the program fields FIELD3 and FIELD4 are assigned to the input fields. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON HELP-REQUEST.
FIELD DEMOF1HELP-FIELD2 MODULE F1_HELP_FIELD2 WITH VAR.
FIELD FIELD3 MODULE F1_HELP_FIELD3.
FIELD FIELD4 MODULE F1_HELP_FIELD4.
The components FIELD1 and FIELD2 of structure DEMOF1HELP both refer to the data element DEMOF1TYPE. This data element is documented, and also has two supplements with numbers 0100 and 0200.
The following field help is displayed:
When the user chooses F1 on the input field for DEMOF1HELP-FIELD1, the data element documentation for DEMOF1TYPE is displayed, since the field does not occur in the PROCESS ON HELP-REQUEST event.
If the user chooses F1 repeatedly for the input field DEMOF1HELP-FIELD2, the data element documentation is displayed, along with the supplement documentation for either 0100 or 0200 alternately. The variable VAR is filled in the dialog module F1_HELP_FIELD2.
When the user chooses F1 on the input field for FIELD3, the data element documentation for DEMOF1TYPE is displayed, since this is called in the dialog module F1_HELP_FIELD3 by the function module HELP_OBJECT_SHOW_FOR_FIELD.
When the user chooses F1 on the input field for FIELD4, the SAPscript documentation DEMO_FOR_F1_HELP is displayed, since this is called in the dialog module F1_HELP_FIELD4 by the function module HELP_OBJECT.
Don't forget to reward if useful...

Screen input into POV event?

Hi....Friends....
In one of my module pool screen....
Iam having two screen fields....
VKORG
VBELN
And one display button in that screen.
Now If i enter 1000 as input for VKORG and click on DISPLAY button..... what happens??
In run time VKORG = 1000. Is n't it?
Not only DISPLAY, we can press ENTER, SAVE or any other push button if our screen.
What ever it may be All the coding part of this buttons can contains PAI module. So no issues.
Then what is the matter of POV event?
How can get the value as 1000 in POV event??
Here my requirement is....
Iam having search help for VBELN...i.e. with following code.
process before output.
module status_1000.
process after input.
module user_command_1000.
process on value-request.
field VBELN module f4_vbeln. <------This wl triggers when clicks on serch help, and it contains select query with where condition of 5 VKORGs
So my search help fetching records for 5 sales organizations.
Now I want to fetch for one sales organization, Which i enters in first field VKORG.
Yes we can chage where conditon as...
> where vkorg = VKORG.
But how can i get value into VKORG, As iam not doing any action with screen which is related to PAI event???
Once again...my task is...
1. Enter into screen.
2. Enter the VKORG as 1000
3. Press the search help of VBELN to give input for VBELN.
...here this search help should be fetch the data of VKORG 1000 only!
Thanks,
Naveen.I

Hi....Narin...
Thanks.
My problem solved with that function module.
DYNP_VALUES_READ
I called this in my POV event.
And that was very good documentaion on this function module.
Thanks,
Naveen.I

Only one User is not able to see POV for reports

Hi gurus,
Entity POV is not seen to the user in the prompt button for a FR in DEV where as the same user is able see the POV in PROD.
What might the reason for this as POV to be seen in one environment and not seen in the orther?
Any help would be appreciated on this issue.
Thanks in advance.

Hi,
thanks for the updates.I have gone through the document but i got an error msg while executing the ManageUserPov.cmd, here is the error msg
D:\Hyperion\products\biplus\bin>ManageUserPov.cmd Delete ManageUserPov.properties
log4j:WARN No appenders could be found for logger (com.hyperion.reporting.config.GlobalResourceBundle).
log4j:WARN Please initialize the log4j system properly.
*[INFO] RegistryLogger - REGISTRY LOG INITIALIZED*
*[INFO] RegistryLogger - REGISTRY LOG INITIALIZED*
Please enter AdminUser : admin
Please enter AdminPassword :
Exception in thread "main" java.lang.NullPointerException
at com.hyperion.reporting.hrfoundation.ManageUserPovImpl.main(Unknown Source)
Any help would be appreciated,
Thanks in advance

Explit 'ENTER' in POV

Similar Messages

Maybe you are looking for