Sei sulla pagina 1di 6

FAQ ABOUT POWL - Web Dynpro ABAP

wiki.scn.sap.com/wiki/display/WDABAP/FAQ+ABOUT+POWL

Query '.......' is already open in another session


Are you trying to open same query multiple times with same login user ?, if yes you might
face this problem ending up seeing an error message for second window onwards.

to fix this, you have first find out what is the POWL Component configuration you are
using to your powl application and then put check mark for the attribute 'allow shadowing' --> it
should fix the issue.

Making fields editable in POWL table –> 2 ways


1. you have to directly set 'editable' and 'enabled' property's of the field in the
GET_FIELD_CATALOG method of the feeder class, so the field will be editable always.
2. you have to set 'enabled' property and provide value to the property 'editable_ref' ' of the
field in the GET_FIELD_CATALOG method of the feeder class–> then either in
GET_OBJECTS or HANDL_ACTION method of the feeder class you can set value ' ' to the
editable reference field, so on performing particular action the field will get enabled.
NOTE: if you set value 'X' to the editable reference field,

When you select some value from f4 help of some fields in quick
selection criteria block, the value will not appear in the input field,
but it works for other fields.
it will be due to incorrect assignment of ref_field and datatype of a selection critieria field, it
should be same value for both ref_field and datatype of a selection criteria field.

When you give sort order, and after editing one row–> ENTER, the
lead selection will get reset.
If you want to keep the lead selection to the one which was selected before editing the row,
then you need to provide an index field named SALV_WD_TABLE_INDEX, for more information
,kindly look into this url:

Null and Zero in Field Catalog of POWL

When does the POWL query get refreshed ?


The automatic refresh of the query on initial loading happens for the following different
conditions:
1/6
1.
1. When you have dynamicData flag set in your POWL_UI_COMP component
configuration
2. When you have passed REFRESHA=X or REFRESHQ=X as an application parameter
while firing a plug to POWL or within the application configuration for POWL

For more details about POWL configuration, kindly find the document below:
http://wiki.scn.sap.com/wiki/display/WDABAP/POWL+CONFIGURATIONS

Why in some powl queries, the date fields are not input enabled as
part of selection criteria ?
Enabling the date fields for input on UI follows these rules:

1. When you turn on 'dynamicData' in Configuration and set some rule for your query in the
transaction POWL_QUERY, dynamic dates will be calculated automatically based on that
rule, hence date field will not be available for input

2. If you turn on 'dynamicData' in Configuration and did not set any rule for your query in the
transaction POWL_QUERY, no automatic calculation of dates will be done, thereby date field will
be available for input

3. If you turn off 'dynamicData' in configuration, date field will be available for input

Dump happens only to some users and ST22 trace will be as below:
Category ABAP Programming Error
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED
Except. CX_SY_REF_IS_INITIAL
ABAP Program CL_POWL_UI_HELPER=============CP

Most of the time, it will be due to inconsistent changes of a default query in the transaction
POWL_QUERY, In such cases, you need to run POWL_D01 report for the affected set of users
and delete the all old queries

NOTE: If you remove the result list of POWL_D01 report execution, all the related user queries
will be lost permanently along with user personalizations

How to pass REFRESHQ or REFRESHA to your POWL Application:


IN PORTAL Environment: Go to portal content administration go to your iview properties,
where you are launching your powl application > go to iview properties > mention the
parameter name as REFRESHQ or REFRESHA and pass the value as X. OR If you have used
2/6
POWL Application configuration, you may check 'Refresh All' in your Application configuration
which is nothing but REFRESHA.

IN NWBC Environment: Go to transaction PFCG > edit your role > go to your application > in
the application parameters tab, pass REFRESHQ or REFRESHA with value X. OR If you have used
POWL Application configuration, you may check 'Refresh All' in your Application configuration
which is nothing but REFRESHA.

While changing the query or viewing the results by scrolling down


the results table, you might experience the focus getting shifted to
Top of the page
To fix this, you should have the corrections from the note 1847621 and also, you have to make
sure the the 'powlDefaultFocus' in your component configuration for POWL_UI_COMP WD
component is Unchecked.

When you select a row, it could be possible that some of the buttons
are not enabled on the Results table toolbar or a server roundtrip
does not happen
To fix this, you have to make sure the the 'fireEventForEveryRowSel' in your component
configuration for POWL_UI_COMP WD component is Checked.

When you add some fields to your results table through Settings
button on UI, you might notice that those added fields columns will
appear in the results table with blank values.
To fix this, you have to make sure the 'readVisibleColumns' in your component configuration for
POWL_UI_COMP WD component is Checked for the node 'typeSpecific' under 'confData' and
have assigned your POWL type here.

If the node 'typeSpecific' under 'confData' does not exist, then you have to create 'typeSpecific'
node under 'confData' node and check the 'readVisibleColumns'

Note: 2015291 along with its necessary pre-requisites cotnains the latest fixes in this area

How are admin queries treated after an installation, upgrade or


language import?
Admin query table is classified as 'G' table. This means that existing data records are overwritten
in client 000. In all other clients, new data records are inserted, but existing data records are not
overwritten

3/6
We get the following error on executing a POWL. The ABAP call stack
was: Method: GET_LAYOUT of program
CL_POWL_PERS_ACCESSOR=========CP Method: INITIALIZE of
program CL_POWL_MODEL=================CP
This dump happens when your application ID is not valid. Check whether the application ID of
your POWL exists in the personalization framework table (Tx is FPB_MAINTAIN_HIER)

We get the following dump while starting the POWL. The ABAP call
stack was: Method: INITIALIZE of program
CL_POWL_MODEL=================CP
This happens if the application parameter applid is not provided in the url. Check if a valid
application id is set to parameter APPLID in the URL.

Personalization
Use - This function allows you to tailor your personal worklist (POWL) to exactly suit
your current task or business requirements. In the Personalize view, you can
determine the selection of worklists for your POWL. Additional layout settings
support your personal requirements.
Features - You can click the change icon in the far right hand corner of the POWL
header, to open the Personalize view. You can make the following adjustments in the
Personalize view settings.
Active Queries - This group lists the active queries that are visible as task lists in
your worklist. If a large number of active queries is used, POWL administrators can
create categories (folders) in the cockpit for portal users to file the queries. You can
change the sequence of queries. If you do not want to use a query that you created
or a standard query, remove this query from the list of active queries. You can
rename all queries.
Available Queries - This group lists the inactive queries. You cannot see them in
your worklist. You can also delete an inactive personal query.
Worklist Switch - You can set the default worklist that is displayed when you open
the POWL user interface for the first time within a session. The POWL switching area
contains the POWL category information. You can add a POWL category or change a
POWL category sequence.
Queries with identical descriptions - If there are several queries that have
identical descriptions but are assigned to different categories, a unique query name
appears on the relevant tab page and in the dialog box for personalization. In the
Personalization view, if you move a query with or without category assignment from
the list of active queries to the list of available queries, the selected query shows the
category to which it originally belonged.
4/6
Layout - You determine how your selected worklists are displayed:
Row of tab page
Row of links

POWL, how to display icons


In Method GET_FIELD_CATALOG, the following code:

ls_fieldcat-colid = 'ICON'.
ls_fieldcat-icon_src_ref = 'ICONNAME'.
INSERT ls_fieldcat INTO TABLE me->mt_fieldcatalog.
ls_fieldcat-display_type = 'IM'. "This one is important

e_fieldcat_changed = 'X'.
c_fieldcat = me->mt_fieldcatalog

POWL, how to set sort by reference


In Method GET_FIELD_CATALOG, the following code:

ls_fieldcat-colid = 'SORT_REF'.
ls_fieldcat-sort_order = '02'.
ls_fieldcat-technical_col = ls_fieldcat-allow_sort = 'X'.
INSERT ls_fieldcat INTO TABLE me->mt_fieldcatalog.

CLEAR ls_fieldcat.
ls_fieldcat-colid = 'SORT'.
ls_fieldcat-allow_sort = 'X'.
ls_fieldcat-sort_ref = 'SORT_REF'.
ls_fieldcat-visible = ls_fieldcat-enabled = 'X'.
INSERT ls_fieldcat INTO TABLE me->mt_fieldcatalog.

e_fieldcat_changed = 'X'.
c_fieldcat = me->mt_fieldcatalog

POWL, how to deactivate a query


Go to POWL_QUERYR transaction

Delete that entry for query you donot want

Run POWL_D01 report for application id you want to hide

Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE


5/6
Except. CX_SY_IMPORT_MISMATCH_ERROR
ABAP Program CL_POWL_QUERY_ACCESSOR========CP
Import mismatch of the selection criteria of a query happens when the underlying feeder
changes any of the datatypes associated with various selection parameters. In such a scenario
the POWL cache goes out of sync with the actual data.

Thereby first one has to update the admin query with the recent corrections within the feeder,
this is done via report: POWL_D04. Bear in mind all changes done by the user to the admin
query via query settings or query parameters in the POWL_QUERY transaction will be lost and
will be overwritten with defaults in the feeder, the query id can be found from the variables in
the ST22 dump.

Next all associated user queries need to be deleted via report: POWL_D01 so that new ones are
created afresh using the recently updated admin query

6/6