Context COMM_DATA_VISIBLE in component web dynpro HRRCF_C_PERSONL_DATA_UI

Hello,
In e-Recruiting, the service HRRCF_A_CANDIDATE_PROFILE_INT does not display the address information and communication data , the reason for this is the value on the context COMM_DATA_VISIBLE.
Anyone know where the value of the context COMM_DATA_VISIBLE is filled?

Hi Emilio,
this value is set in the component HRRCF_C_PERSONL_DATA_UI -> Windows -> WDW_MAIN -> Tab Inbound-Plugs -> Event Hanlers HANDLEINTERNAL_CANDIDATE/HANDLEEXTERNAL_CANDIDATE.
As this is only a display setting you do not need to modify that. You can display the fields also by using an application configuration you usually have to create anyways. But be aware that there are some points to be taken in account:
- The personal data and communication for internal candidates should not be editable as the HR Core is the leading system (except phone as not distributed)
- Even if you display the address fields you won't see something in there. The ALE distribution for IT 0006 does not assign a channel to the address of the internal candidate so it cannot be mapped to a address type of e-recruiting that's why it is not shown.
If you need detailed information on one of the topics above or plan to allow changes of internal candidate personal data like Email don't hesitat to ask.
Best regards
Roman

Similar Messages

Problem with CrossComponent Context Mapping with PopupWindow (web dynpro ab

The situation:
I have four views (View V1, V2, V2_popup, V3) in three Components C1, C2,C3.
View V1 is embeded in Component C1. View V2 is embeded in C2 with view V2_popup as Popup-Window.
View V3 is embeded in Component-C3. And at last the View of Component C2 and C3 are embeded in View V1.
The Problem is the CrossOver Context Mapping between the view V2 and V3.
My first way is the "direct context mapping":
I define a node in the ComponenteControllen from Component-C2 as interface and use it over the ComponentenController
from Component-C3 in view-V3. Now I bind an attribute of the mapped node to an ui-element (e.g: inputfield),
but the output of the Field is empty.
The second way is, that I define an external Mapping for this situtation.
I define a node in the componente-controllen from Component-C2 (an Component-C3)as interface with the attribute "Input Element (Ext)".
Than I map the two nodes with a node from Component-C1. That's works fine.
BUT, if I execute an action (e.g. action_save)in the popup for view-v2 (V2_popup) the changings from the inputfields don't write (show)in the context of the
popup-view. I check this with the debugger. And if I close the popup and open it again, the changings are visible.
Short: If I define a node with attribute "Input Element (Ext)", I don't can read changings from
the screen in a popup-window.
How I can solve this problem???
Message was edited by:
        Maik Sturm

Hi Maik,
try this:
at first you have to instantiate all! used components in the wddoinit method of the componentcontroller in your main (c1) component.
e.g. instance of c2 Component
lr_usage_c2_comp =   wd_this->wd_cpuse_c2_comp( ).
IF lr_usage_c2_comp->has_active_component( ) IS INITIAL.
    lr_usage_c2_comp->create_component( ).
ENDIF.
and at the end set the reference:
l_ref_interfacecontroller = wd_this->wd_cpifc_c3_comp( ).
l_ref_interfacecontroller->set_usage(
    ir_usage_c2_comp = lr_usage_c2_comp ).
set_usage is a method in the c3 component controller,
METHOD set_usage .
DATA: lr_usage TYPE REF TO if_wd_component_usage.
lr_usage = wd_this->wd_cpuse_c2_comp( ).
lr_usage->enter_referencing_mode( ir_usage_c2_comp ).
After doing this the components are using the same instance and you can simply use direct mapping between the components.
Hope it helps.
regards
Christian

Creating context node dynamically in web dynpro for java

Hi
I am having requirement where user can ask for 3 tables . I have created tables dynamically. But now i want that context node should also be created dynamically.
Thanks and Regards,
Saurabh

Hello Saurabh,
Refer the below link:
http://wiki.sdn.sap.com/wiki/display/WDJava/DynamicUIGeneration.
There is a section Dynamically Building the Context. Please refer to that.
There are lots of things available in SDN for the same.
Regards
Nizamudeen SM

Process Context Web Dynpro

Hello,
Can we have one process context across whole BPM and Web Dynpro? My scenario is: Executing BPM in Web Dynpro through a Web Service. Presently I have set two contexts( one is for web dynpro and another for BPM Web Service/Process Context). Can I use one context instead of two types of contexts. Please let me know if there are any limitations.
Thanks,
Sunita.

HI Sunita,
technically you need different contexts for WebDynpro and BPM. This is due to the fact that these are two independent technologies which manage their context data differently. So, you will need a WebDynpro context as well as a Process context for BPM.
But this does not mean that you cannot share and transfer data from one to another. From the WebDynpro context you might fill the WebService input. This can be simply done through context mapping and model binding. Once the WebService gets called, the input data is automatically mapped and transfered to your Process context. Of course, this has to be modelled first in the Process Composer. From here, you might use the context data to map to activites (human and automated) in your process. From here, you are able to again map it to a WebService in case of an automated activity or a WebDynpro context in case of a human activity.
Hope, this brought some more clarity.
Best regards,
Stefan

In web dynpro i want explanation/definition for the following things

Hi dudes,
I want explanation *** definition for the following
(1) web dynpro
(2) Cardinality
(3) methods
(4) Nodes
(5) Attributes
(6) Interface
(7) Views
(8) Windows
(9) Mapping
(10)Binding
(11)Model
(12)Controller

Hi,
Here are the defintions for the terms you hav requested-
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
Clear separation of business logic and display logic
Uniform metamodel for all types of user interfaces
Execution on a number of client platforms
Extensive platform independence of interfaces
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
A Web Dynpro component is a reusable entity. It summarizes all components that are
required as part of this programming unit for an executable Web Dynpro application.
The Web Dynpro component concept offers a number of advantages:
Structuring of the programming
Creation of easily manageable application blocks
Reusability of whole components
Decoupling of software projects in both time and space
The Web Dynpro component contains any number of windows and views and their
corresponding controllers. Additional Web Dynpro components can also be referenced.
View
A view describes the layout and behavior of a rectangular area of a user interface.
Every Web Dynpro application has at least one view. The layout of a view is made up of
different user interface elements, which can be nested in each other. The positioning of
interface elements in one view is supported by the supplied layout variants.
In addition to the visible part, the layout, a view also contains a controller and a context. The
data to which the elements of the view can be bound are stored and managed in the view
context, enabling them to be represented or used on the screen. The view controller can
contain methods for data retrieval or for processing user input.
Window
A window is used to combine several Views and View Sets (the concept of view sets is only
offered in Web Dynpro for Java). A view can only be displayed by the browser if it has been
embedded in a window. A window always contains one or more views, which are connected
by navigation links. One of these views, or a view set, is specified as the start view and is
displayed the first time the window is called.
Windows have inbound and outbound plugs.
Inbound Plugs and Outbound Plugs
A window has one or several inbound or outbound plugs. Using these plugs, a window can be
included into a navigation chain. The concept of these plugs corresponds to the concept of
the plug for a view. Each plug of a window is visible within the entire window and can be used
for navigating within this window. In addition, one or several plugs can be made accessible to
the component interface so that they are visible even beyond the limits of the component in
question. They thus belong to the interface view of the relevant window.
They are used to navogate from one view to other and pass the data between the views. Which view to be called next from current view - the flow of views is descriebd here using Plugs.
Controller
Controllers are the active parts of a Web Dynpro application. They define how the user can
interact with the Web Dynpro application. The data that a controller can access is defined in
the corresponding context. Different instances of controllers and contexts exist within a Web
Dynpro application.
View Controller
Each view has exactly one view controller, which processes the actions performed by the user in the view.
A view also has exactly one view context, which contains the data required for the view.
Interface Controller
Each Web Dynpro component contains exactly one component controller. This controller is a
global controller that is visible also outside the component. It is thus part of the interface of a
Web Dynpro component.
Context
Definition
The data used in the component or in the view are stored in the context. Read-write access to
this data is available using the controllers as a starting point.
Structure
The data from the contexts is managed in a hierarchical structure. Each context has a root
node, underneath which the individual data fields (attributes) are stored in a tree structure.
You create this tree structure according to the structure of your application.
CONTEXT is generally called as a ROOT Node.
Each context has nodes and attributes also.
Cardinatlity
Each node contains data fields that represent one of the following:
u2022
An individual instance of an object type
u2022
A table of instances.
This property of a node is known as its cardinality. The following table summarizes the
possible cardinalities for a node:
Cardinality Description
1:1 The node contains only one element instance, which is instantiated automatically.
0:1 The node contains only one element instance, which must not be instantiated.
1:n The node can contain multiple element instances, of which at least one must always be
instantiated (and is instantiated automatically).
0:n The node can contain multiple element instances, of which none have to be instantiated.
Further information about this and other properties of context nodes is available in the section
Context-Nodes: Properties.
Recursion Nodes
Dynamic node nesting is possible within a context, creating what is called a recursion node.
The node that is used for recursion is always a predecessor of the new node. The newly
created recursion node is a reference to a predecessor node and therefore cannot be
processed separately. Instead it takes on the structure of the node to be repeated.
Data Binding and Mapping
Within the Web Dynpro architecture, the contexts of the different controllers can be linked in
different ways:
u2022
A UI element of the user interface of the view can be linked with an element of the view
context.
u2022
A mapping can be defined between two global controller contexts, or from a view
context to a global controller context.
The context of a global controller can be linked to a Web Dynpro Model.
Defining Mapping Between Two Contexts
The elements of a view context can be locally defined. In this case (represented in the graphic
below as a "Local Node"), all the contained attributes are only visible within the relevant view.
When the view disappears, the attribute values are deleted.
Event
The component controller allows you to create events.
Events are used to communicate between controllers and enable one controller to trigger
event handlers in a different controller.
Cross-component communication can be implemented using the interface controlleru2019s events.
Events that were created in the component controller are visible within the component only.
Inbound Plugs
Inbound plugs in a view also react like an event. Therefore, when a view is called using an
inbound plug, the event handler that is optionally available for the inbound plug is always
called first. In this case event handling takes place within the current view controller.
UI Element Events
Some UI elements, such as the Button element have special events that are linked with user
actions. These events are predefined and have to be linked with an action at design time.
Actions for UI Element Events
Some UI elements such as the button element can react to a useru2019s interaction: clicking on
the corresponding pushbutton can trigger a handling method to be called within the view
controller. Such UI elements are equipped with one or several general events, which can be
linked with a specific action at design time (switching to a subsequent view, for example). If
such an action is created, an event handler method for this action is created automatically. In
this way, you can equip a UI element event (which has been inserted several times into a
view) with different actions as necessary. The event is then processed by the corresponding
event handler depending on the action that is linked.
Interfaces of Web Dynpro Components
Each component has an interface in order to enable communication between Web Dynpro
components and to enable a component to be called up by a user. This interface consists of
two parts:
Interface View of a Window Contained in a Component
The interface view of a Web Dynpro window is used to link a window with a Web Dynpro
application that can be called by the user.
Reward if helpful.
Best Wishes,
Chandralekha

Problem with Table display in Adobe Form of Web Dynpro ABAP

Hi Team,
I'm trying to display a table in Adobe Print Form (not interactive). The table is bound to the context node in the Web Dynpro ABAP where the cardinality is 0:N. I get a short dump. Don't know what to do here. I'm able to display individual fields from my context successfully. Looks like something is missing when I try to display a table. Any pointers to display a data table in Adobe? Any step by step example you know of where I can find out what I did wrong? Many thanks for your time
We are on support pack SP06 on 2004S release.
DUMP INFORMATION:
Short text
    Access via 'NULL' object reference not possible.
What happened?
    Error in the ABAP Application Program The current ABAP program "CL_WD_ADOBE_SERVICES==========CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in procedure "CREATE_PDF" "(METHOD)", nor was it propagated by a RAISING clause.

Hi Thomas,
We upgraded our system(2004S) to SP10 so that we can use the ADOBE form printing in Web Dynpro ABAP but could not apply note 1034425 because of the validity constraints in SNOTE. All the pre-requisite notes are already in the system apart from one note 1029721 which talks about supporting input helps. We don't want to use input helps in our system and cannot upgrade to SP11 because of problems with Business functionality.
Questions:
1) Is note 1034425 absolutely dependent on 1029721?
2) If NOT, can someone please correct the validity so that we can implement using SNOTE.
3) Would it be OK if we manually apply the changes specified in 1034425 without implementing 1029721?
4) If all of the above is not applicable, is there any other note which fixes the above mentioned short dump.
Your help in this matter will greatly help us in using the ADOBE services provided by SAP WDA.
Thanks much

Passing data from one screen to another(web-dynpro) in SRM sourcing cockpit

HI Experts,
i am facing problem in passing data from one web-dynpro screen and assigning the data it to another web-dynpro screen.
my requirement is that when ever user selects a contract in PROPOSE SOURCES OF SUPPLY screen popup and press only assign only button, the data of the contract should be copied to the shopping cart.
i have already used the BADI BBP_DOC_CHANGE_BADI, but unfortunately it was not working.
so i tried to use the context, element and other web-dynpro fields to pass the data, i am able to pass the data from the popup to the second screen and able to assign it.
but when ever i deselect the shoppping cart which has been assigned with the data of the popup and select another shopping cart the data of the above shopping cart is cgetting changed.
i am unable to figure out the exact reason why this is happeing.i have written code in the ASSIGN ONLY button method to fetch the popup data and in the WDONMODIFYVIEW method of the second screen to assign the popup data to the shopping cart.
i have tried to bind the elements using the BIND_TABLE, BIND_STRUCTURE, BIND_ELEMENT, BIND_ELEMENTS methods, but nothing is working.
can anyone suggest me where i am making mistake and try to solve the issue.
Thanks
Tanveer

Dear Poster
Your thread has had no response since it's creation over
2 weeks ago, therefore, I recommend that you either:
- Rephrase the question.
- Provide additional Information to prompt a response.
- Close the thread if the answer is already known.
Thank you for your compliance in this regard.
Jason Boggans
SAP SRM SDN Moderator

How to run mobile web dynpro application

Hi experts,
I'm using NetWeaver Developer Studio for Mobile SP03.
I create a mobile application for handhelds including 2 components:
- Mobile Application.
- Mobile UI Component (web dynpro component).
I do follow the tutorial for creating the application. I can deploy and run the application on NWDS handheld emulator successfully.
When I deploy it on my SAP Application server to test the web dynpro UI application via a web browser, it throws out a java.lang.ClassNotFoundException: the class <package name>/Internal<Application Name>Comp.class cannot be found by WD framework when I access it. It can be deployed without error and is alive in the web dynpro content admin.
I found that the normal WD component the class Internal<Application Name>Comp is generated during the building process but it is not when developing mobile UI component.
Can anyone tell me there is any difference between the two WD component types? Does my server need to install any extra component for running mobile UI component? Or do I need to configure my NWDS for Mobile to make the application work on SAP server?
Thank you very much,
Steven Linh Nguyen.

Hi,
Mobile webdynpro application for handheld cannot be deployed on SAP AS.
To use the Mobile webdynpro application for handhelds follow the steps:
1. Upload sda files of all DCs to the DOE server (Transaction SDOE_UPLOAD_ARCHIVE) which will be availabe at the location
<workspace.jdi>\LocalDevelopment\DCs\demo.sap.com\<DC>\_comp\gen\default\deploy
2. Install the simulator on laptop or client on PDA
3. Deploy uploaded MCDS(from step1) to the client, after the device registration.
Thanks and Regards,
Suma

Context from Web-Dynpro-Component-Interface & Customer Extention Fields

Hello all,
A main component uses a Web-Dynpro-Component-Interface and defines an external maping to it. Web-Dynpro-Component-Interface has a context and a window. At runtime implementaion of Web-Dynpro-Component-Interface is provided.
All works fine, but how can i create an implementation with view which contains customer extention fields? Unfortunately only fields from context of Web-Dynpro-Component-Interface are visible. I can not even extend the context of Web-Dynpro-Component-Interface via enchancement framework.
I assume, it is possible with dynamic programming, but why is it not possible in declarative way?
thanks
regards
Paul

Hello,
I found this documentation:
Implementation of Interfaces for Customer Developments
Using interfaces in a Web Dynpro component benefits customers by giving them a clean basis for their own further developments. When creating a local development, you can implement a used interface in a separate component and add your own aspects to an application delivered by SAP.
http://help.sap.com/saphelp_nw70/helpdata/en/a9/19eebc1e2943dbb2d443095d017ae9/content.htm.
I think it must be a correct way to extend SAP programms with customer fields. Please reply, issue is very important.
Regards
Paul

No component usage created in enhanced web dynpro component

Hi experts,
I am facing the following problem:
I'd like to enhance a web dynpro component in order to add a popup window. The popup is triggered by the process_event method. So far everything works just fine.
But the popup needs to know some context attributes from the main component, and I cannot create a component usage in order to set the context mapping.
Does anybody know how to solve this issue?
Thanks and regards
Jan Phillip Höft

Hi!
Thanks for your answers first of all.
I need the popup to be a stand alone web dynpro component, so I guess the assistant class doesn't do the trick because I can not access it in the popup component.
The popup is called when the business object is saved. So that the user is asked to notify other users that the document has changed. In this popup the user should fill in the message and click a button to send it and close the popup.
So I tried the OBN approach as well but with two problems :
1. I cannot close the popup component by coding (button click) because it has no direct parent component
2. The save event is not run through properly so the document stays locked by the user. But I didn't look into this yet.
So it would be perfect to have an embedded popup component which is based on a stand alone web dynpro application so it can be closed properly but it need at least access to the guid of the main component.
Anybody got an idea for this?
Thanks and regards
Jan Phillip Höft

Calling session bean's business method through web dynpro component

Hi All,
Can anybody tell me how to call a session bean's methods through a web dynpro WITHOUT java-model or web service model ??
I have following scenario:-
1. Stateless Session bean having two business methods
2. Web Dynpro component
3.Now i want to call business methods without using any model. I have got following piece of code but I dont know how to go about it.
4.Where do i have to set JNDI name for session bean? which interface will be looked for?
5. Do I have to declare public part for EJB DC? If yes, how?
//This is inside web dynpro component
InitialContext context = new InitialContext();
o = context.lookup(JNDIName);
TestSessionbeanHome homeRef = (TestSessionbeanHome) PortableRemoteObject.narrow( o,
TestSessionbeanHome.class);
TestSessionbean beanRef = homeRef.create();
<returnValue> = beanRef.<ejb method name>
Please help to get a step-by-step approach to this case.
Thanks and regards,
Amey Mogare

Hi,
If I comment out the part that is using session bean's business method, DC is building fine.
And if I uncomment, then compiler is unabl eto resolve business method(s).
And i would like to mention that my EJB + J2EE App DC is building properly, but it havent yet deployed properly as I am waiting for data-source-alias name prefix to be configured by ERP team. So will this be a reason why Web Dynpro DC is not able to resolve business methods ??
Because Web Dynpro DC is able to resolved all interfaces of Session bean and entity bean. But when it comes to business method, its not able to resolve.
Any more ideas why it is not happening?
Pls help.
Now i went through some forum posts regarding this and found that we also need to add EJB DC to Java Build Path for WebDynproDC>Properties>Java Build Path.
I did this and now it is able to resolve business methods and DTOs as well. So to summarize I did following:-
1. Added EJB DC (complete DC) as a Used DC to Web Dynpro DC with Buid-n-Deploy-n-Run time dependency
2. Added Sharing reference of J2EE application DC to Web Dynpro DC -->Properties
This reference I constructed as follows:-
<vendorname>/<name of j2ee application as appearing under display name tag in application.xml (replacing '/' with '~')>
So my Sharing Reference becomes:- <vendorname>/reqpstapscreqpstapja_reqid
3. Added EJB DC to Java Build Path in Web Dynpro DC's properties
4. Then I added following piece of code to get object of SessionBean class
InitialContext context = new InitialContext();
Object o = context.lookup("java:comp/env/ejb/SessionRequestIDBean");
SessionRequestIDHome homeRef = (SessionRequestIDHome) PortableRemoteObject.narrow(o, SessionRequestIDHome.class);
SessionRequestID beanRef = homeRef.create();
beanRef.<business method>
But After doing this I am facing another problem :-
The build fails saying it is not able find the package for DTOs. But when I see the Component Controller's code it is not showing any red or yellow marks.
Can anybody pls help me out here?
Thanks and regards,
Amey Mogare

Web service in Web Dynpro development Component

Hi All,
I have created a web service in SAP GUI and I have saved the WSDL file on my local PC.
Now when I create a web service model in a simple web dynpro project it works perfectly.
But when I do the same in a web dynpro development component; as soon as the web service model instance is associated with the activity in the DTR my application get hanged. I have to quit my NWDS. When I reopen NWDS my application shows following errors:
Kind Status Priority Description Resource In Folder Location
Error XMLTokenWriter cannot be resolved (or is not a valid type) for the argument writer of the method serialize Char1.java JD2_ADBESP6_Dtestwebservicesap.com/src/packages/com/adobe/mo_web1/proxies/types line 57
Kind Status Priority Description Resource In Folder Location
Error typeRegistry cannot be resolved or is not a field Z_WS_GETEMPINFO_FULLSoapBindingStub.java JD2_ADBESP6_Dtestwebservicesap.com/src/packages/com/adobe/mo_web1/proxies line 29
Kind Status Priority Description Resource In Folder Location
Error transportBinding cannot be resolved or is not a field Z_WS_GETEMPINFO_FULLSoapBindingStub.java JD2_ADBESP6_Dtestwebservicesap.com/src/packages/com/adobe/mo_web1/proxies line 22
Kind Status Priority Description Resource In Folder Location
Error SOAPSerializationContext cannot be resolved (or is not a valid type) for the argument context of the method serialize Char1.java JD2_ADBESP6_Dtestwebservicesap.com/src/packages/com/adobe/mo_web1/proxies/types line 50
Kind Status Priority Description Resource In Folder Location
Error SOAPDeserializationContext cannot be resolved (or is not a valid type) for the argument context of the method deserialize Char1.java JD2_ADBESP6_Dtestwebservicesap.com/src/packages/com/adobe/mo_web1/proxies/types line 26
Regards
sid

Hi Sidharth,
Which version of NWDS you are using. I was facing the same problem with SP16 sometime back.
I did find a workaround to do that. See, whenever you will create the WS Model in Web Dynpro DC, it will ask you to add some file in DTR..right!!........ do one thing press "Cancel" or "No" there. Then studio will ask one more time to add the files, in different dialog box though. Add the files from the second dialog box rather than the first one.
Regards,
Mausam

The Web Dynpro component cannot be generated due to serious (syntax) errors

Hi everybody,
While I was developing a web dynpro application, I had an error but I couldn't understand this error. Before I took this error message, only I changed bound one context node to another context node in a RadioButtonGroupByKey.Therefore, when I pushed activate button, I took an error message.This error message said "The Web Dynpro component cannot be generated due to serious (syntax) errors". What does it mean ? How can I find out where is the error in the application. Also, I think the reason of this error message is about a BC problem. I am waiting for your comment urgently.

Hi ,
Just delete the context (by using the context binding) and bind the field with the correct node and try to activate .
One more suggestion is that after deleting the binding and before binding to other node check it that whether that binding was properly deleted or not.Some times its not deleting the binding.
Hopely my suggestion may work.
Regards,
Satya

Component Initialisation in web dynpro java

Hi all,
Iam new to web dynpro java.I am using two web dynpro component suppose A and B . Iam declaring the usage of B in A so that i can embedd one of the view in Component B. I want to use the context in Component B in Component A . which component is initialised first when we run the application ...
plz give a procedure to do this task......
Thanks and Regards
prasad

Hi Prasad,
This forum is about Visual Composer. You might want to try the [Web Dynpro|Web Dynpro Java; forum for this question.
Best regards,
Tal.

No component configuration possible for some web dynpros?

Hi experts,
I want to configure buttons for a view. Display of technical information (right click) for UI element
says:
Application: /SAPSRM/WDA_L_FPM_OIF
Web-Dynpro Component: /SAPSRM/WDC_UI_DO_ACC
Window-Info: IV_L_FPC_CA_DETAILS
View-Info: V_DO_ACCOUNTING
Configuration Id: A56B0481584E314F46F1C5E908E8819E
In SE80 no such configuration id (looks like a GUID) is found. What is
the name of the configuration ID? How can I configure this strange WD?
Other views have normal config. id's.
Any ideas?
Thanx.
Joe

Right click on the application name - in context menu chose create\change configuration, and then create application configuration.
While creating your application configuration you will be prompted with a component configuration, click on create and then navigate to component configuration and then you can make settings for visiblity of ur reqd button.
Regards
Manas Dua

Context COMM_DATA_VISIBLE in component web dynpro HRRCF_C_PERSONL_DATA_UI

Similar Messages

Maybe you are looking for