Hiding fields in Review button in ESS iviews

Hi All,
In ESS iviews, say Communication Address under Personal Information, have hid some fields (ctrl+rt click) which were not needed it goes fine till i click Review button.
After i click Review button to come under Review and Save roadmap, all the fields are again visible in disable mode.
Can you please help me in resolving this issue.
I need to hide some fields which are not needed permanently from the iview.
Thanks and Regards
Piyush

Hi
In content administration go to that iview, preview it and click CTR+Right click it open's personalization editor from there you can hide the tab's and can change the text in that iview. this works for only ESS iviews
Regards
Mahesh

Similar Messages

Exit button on ESS iViews

Hi,
We have ESS deployed on EP7.0, so we are using the WebDynpro version of ESS. Now we want to redirect the navigation to our own customized iView when click "Exit" button on any of the ESS iView, for example , address iView. I guess this should be controlled in the pcui_gp xssutil component, am I right? Can anyone give me some hints on where I can make this modification? Thanks a lot

Hi Chris,
thanks for your reply.
If you mean to hide the button using the iView/WD Personalisation by rightclick on the iView in PCD and then Review, well yes i know this and i have tried this already before and we were able to hide some not required input fields in the Webdynpro, but we were not able to find and to hide the "EXIT" Button using the personalisation..!!?? you know why?
Why to hide the Exit button, i will tell you why, in the iView for maintainig the ESS Personal Information -> e.g. Adresse --> Edit Adresse View (Roadmap view No. 2) --> when User click on the Exit Button --> This will open new browser Window with ESS... ---> This second Browser Window (Pop up) would confuse the User, since he already have an opened window, so the Customer mean why open new window, since the user can simply click the Button Back and so his data are also saved..
How can we manage to control the behaviour of the Button, so the iView is closed safety without that new Pop-up windows are opened...
Many Thanks,
Nazih

ESS US Addresses - Hide Review Button

Hello Experts,
I'm currently working on an ESS DC for BP 1.0 (ERP 2005), specifically the US Addresses webdynpro application (essusaaddr) and my requirement is to show the Edit Screen differently, according to the different Infotype 0006 subtypes available in the Bizcard overview screen.
I got this done by verifying which is the active subtype and depending on this, I change fields atributes accordingly (e.g. Read Only, Invisible).
Problem is that for one specific subtype I need to hide the Review and Save button, because this subtype is all read-only. And I cannot find the application's buttons anywhere, so I don't know how to act upon them...
Bottom line is: where can I find the buttons for the Bizcard view and Edit view for the ESS US Addresses application? Anyone?
Thanks a lot in advance,
Antonio Caldas

Hi Guys,
Thanks for your replies.
I'm sorry but I think I wasn't clear enough. The question is not hiding a button or label using the FPM personalization features. The question is that for the US Addr application, only one Edit view is provided, ao all subtypes existing in the Overview Screen point to it. The result is that if I hide the "Review" button in the Edit view, this will apply for all subtypes. And my requirement was only to hide the Review button for 2 specific subtypes.
So the only way I managed to solve this by modifying the standard us~addr webdynpro application, using code logic.
Thanks again for your replies,
Antonio

Adding Validations at ESS Review button

Hello,
I am on EP7.0 ERP05 and NW04s and trying to add validations on the Review event of the Banks Detail screen like making a checkbox as mandatory which I added on the screen .... and restricting the Dollar Amount field on the screen not to be less than 10.....I wonder how can I acieve this when the Review button is a part of the FPM(Floor Plan Manager) in the ess~per application ....I have also deployed the Self- Service Administrator Role on the portal for this ........but don;t know how to useit ...
Any help would be highly appreciated.

Hello
Thanks for the reply. But actually I am adding my own checkbox on the screen and want to make it mandatory rather than making the fields as mandatory ...
Looking forward to your reply.

I need to filter the field Compensation Review :iview Compensation Planning

hello
I need to filter the field Compensation Review (iview Compensation Planning), this value come from table : T71ADM08 Compensation Reviews
i have many values, but i need show a range o one set the of values, any ideas ??
I can show only one filtering parameter from the parameter value of the iView, but it only one value, I need a filter a range
please any ideas, ???

Hello,
having had this very same issue in the past - the option we went with was to enhance the RFC FM that returned the list of the reviews with some removed depending on the employee type.
(I'm assuming that the list of avaliable reviews is dependent on the employee and that's why you want to filter).
Chris

How to rename 'Review' or 'Save' buttons in ESS/MSS applications?

Hi,
We are on EP7 SP9 and ESS 6.0
How to rename the 'Review' or 'Save' buttons in ESS/MSS?
I know these BPs are implementation of FPM.
I would like to know in which DC I need to do changes ?
Points will be awarded.
regards,
Raj.

Hi,
In each webdynpro application (irrespective of ESS or MSS) have Vc Components. All UI elements define here.
If you want to change text of any UI element in any standard DC (addr, bank, fam, cat, lea... ), you have to go to particular Vc Component under DC, change the text of UI Element.
FcEmployeeServicesComponent and FcNavigationComponent are commonly used DC's in all DC's.
FcEmployeeServicesComponent is used to get Employee number, molga....
FcNavigationComponent is used to navigate to AreaGroupPage, AreaPage, RestartService and Exit from current Application.
Thanks & Regards
Vasundhara

Call BADI on click of a submit button in ESS

Hi All,
I am trying to call a function module ( i.e through BADI ) in a different browser by clicking on a submit button in Travel & Expenses Iview in ESS ( EP 6.0 ) but i didn't see any new window/ browser opened when i clicked on submit button.
The BADI is activated and its working fine because the same functionality is working good when i tested this through trans. code PR_WEB_1200. When i clicked on a submit button, a new browser was opened and the form was displayed the way we want in a different browser.
But when i tested the same in ESS, i couldn't see any new browser or window opened. If the BADI was called when i clicked on the submit button atleast a new browser has to open with a blank page.
Please guide me, If anybody knows, how to call a function module in a new browser by clicking on a button in ESS - Portal.
Thanks.
Anil

Hi Jayesh,
You can use the BADI BBP_CUF_BADI_2 to change the display from customer-defined fields to the SAP standard screen. This BAdI enables you to control whether the fields can be edited, and how they are displayed.
MODIFY_SCREEN method will Show/hide field display and restrict edit options.
For more information on BADI please go to SPRO -> BADI.
OR View the information on BADI's.
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
Hope above proves helpful to you.
Regards,
Rajeshree.

Hiding fields in a form

hiding fields in a Form is called what? How do I go about hiding fields in a form than having a button the user can click on to make the fields visible to fill out? Thanks Nick

The "presence" property controls the visibility of form elements.
This eseminar explains the details:
http://adobechats.adobe.acrobat.com/p87746471/
Thom Parker
The source for PDF Scripting Info
pdfscripting.com
The Acrobat JavaScript Reference, Use it Early and Often
http://www.adobe.com/devnet/acrobat/javascript.html
Then most important JavaScript Development tool in Acrobat
The Console Window (Video tutorial)
The Console Window(article)

Code for save event in review screen of ess

Hi All,
I was unable to find the code for trigger of the save event when user clicks save button on ess application lastscreen in the VcPerAddressRevieww component, its not in view or controller of the component.When user hits save in the last screen after review where is programming code which is triggering the save event in any ESS application.
Thanks.

nithya,Thanks for your answer but my question is on out of box ess source code for example in the review and save screen of ess application , when the user clicks save button there should be somewhere a call to fc component that calls the rfc to update the backend.I am looking for that call in the code, i didnot found it in VcperAddressReview Component controller or in the view.Is it a part of CC component or where can i find the call on save button hit.
Thanks,
sameer

Problem with Hiding fields of selection screen which is called as subscreen

Hello All,
I have problem while hiding the selection screen which is called as subscreen.
Flow of my logic:
Selection-screen with one field and three buttons CREATE,DISPLAY and CHANGE in application toolbar.
user enter some value in field and either he press change or dispaly
When change i need to call selection screen when it is in dispaly i need to stop calling this selection screen.
Upto my knowledge we can't stop calling selection screen in display mode so there is only one possibility is hiding the fields when it is in display mode.
How can i hide the fields and where i need to hide fields?
Please post some codes.
Regards,
Lisa

you can refer the sample code which i mentioned in your previous post. that will solve the problem.

ITS 620 Patch 19 - ESS iviews (PZ13 etc) show initial WebGui screen

Hi,
We have EP6 SP12 with the ESS Business Package. All the ESS iviews were working until I upgraded the ITS 6.20 to patch 19 (I think this is when the problems began). Now, any ESS iview that does not have an IAC service in the R/3 system (for example PZ13 - Personal Data, PZ02 - Addresses), the iview shows the WebGui start screen (the one with the "Start SAP Easy Access" button) rather than the IAC screen.
If I access the IAC through ITS directly (i.e. using the http://itsserver:port/scripts/wgate/pz13/! URL) I can access the transaction, but the IAC iviews do not work.
Any help greatly appreciated!
Regards,
Jane

Jane,
Did you restart the ITS Instance? The setting i mentioned is correct, it worked for us. Here is the SAP note number, Sorry i don't have the note number,just saved the text.
Symptom
After installing ITS 6.20 patch level 19, some enterprise portal iviews of type WebGui are connected successfully to the backend system, but show SAP easy access menu, instead of an appropriate start transaction screen.
Reason and Prerequisites
A defined ITS start transaction (~transaction) is not processed when using SSO ticket to logon to a backend system.
Other logon methods like User/Password, do not show this behavior.
Solution
Problem is fixed with ITS 6.20 patch level 20.
To curcumvent the problem in ITS 6.20 patch level 19, please set
~popupsduringlogon 0
in the ITS global servcie file and restart the system

Disable or Remove some field from User Profile in Personalize iView

Hi All,
I have a requirement to Disable one field and Remove one field from User Profile in Personalize iView.
i want to disable Activate Accessibility Feature field and Remove Language field.
How to archive this.
Thanks and Regards
Trilochan

Hi,
You can use [Personalization|http://help.sap.com/saphelp_nw70/helpdata/en/42/ed3ce7f8593eebe10000000a1553f7/frameset.htm] to do this :
1. logon as an admin and navigate to Portal Content > Portal Users > Standard Portal Users and open Every User Core Role
2. right click on User Profile and select edit
3. click on the Preview button then right click + CTRL on the iView and personalize the User Profile iView
That's it.
Regards,
Pierre

Error while trying to use ESS iViews

Hi All Experts,
We are upgrading our portal to EP 7.0
I am working with ESS iViews and when I try to open any ESS iView say, Benefits and Payment, I get the following error.
Service cannot be reached
What has happened?
URL https://srams.dev-sap.grainger.com:44306/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea call was terminated because the corresponding service is not available.
Note
The termination occurred in system SRA with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-https-c:000-u:SAPSYS-l:E-i:devsun10_SRA_06-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
Please help.
Thanks
Preet

Hi,
Do you still have you problem ?
Regards

Hiding fields in HCM forms

Hi Experts,
I have following requirement for hiding fields in my form.
I have two screens MANAGER and HR screen.
now i have some input fields which has to be visible in MANAGER screen and
and should be hidden in HR screen.
please let me know how can i achieve this using form calc or java script.
any code will be helpful.
Thanks,
Santosh

Hi sushmita,
Thanks for ur reply.
The solution which you have given i have already tried but not working.
my requirement is like MGR or HR can initiate the process.
if only MGR intiates the process the solution which u have given will work.
but here i have a diff scenario.i have created separate process for HR also but im not able
to see that process on the process list.
so i have to use only one process and resolve this.whatever im writing validation is working
only when MGR initiates the process but fails when HR initiates.
Hope u got my point.any suggestions will be helpful.
Thanks,
santosh

Hiding fields in phtmlb:formLayout (new thread)

Original Thread:
hiding fields in a bsp...
What Kevin is talking about, is some special development we did for HR eRecruitement. Well, let us turn it around. They helped us, and we returned the favour. And yes, this is actually some of the more interesting bits and pieces of BSP. (Fresh meat to discuss:).
Effectively, the <phtmlb:formLayout> has two functionalities. The first is a very easy way to layout a form. The second is a way via customization to dynamically have customers overwrite the visibility/required property of each field. So the SAP puts the maximum number of fields into the formlayout, and the customer can then via customization remove some, flag some as required, etc.
(If anybody should feel like writing a long weblog on this, I will provide technical detail, plus examples offline.)
The interesting database tables are these PHTMLB_FLI* ones. Part of the agreement was that the application itself provides for a UI to update the table. Also, the application itself controls which fields are changable.
If you really want to play, look at SBSPEXT_PHTMLB, the formLayout example. In the top part, there are also a serious of dropdown listboxes. What these do, is that they update the customization tables first, before the formlayout is rendered. So what you are seeing is actually the formlayout as it has been programmed, plus then the effects of a (customer) customization on it.
Also the example shows the effect of using an XML bee to dynamically add entries into the fieldLayout (if the application added these hooks).
brian

Hallo Thomas,
No, unfortunately we never build something to also customize the labels. They HR colleagues did not ask for this :).
I first started to write you here a loong text with answers. But then I got lazy, and searched my archive mailbox. Here below is the draft input that I wrote initially for the documentation. It describes everything pretty good. (But it is draft document, never proofread again, so read it lightly!)
bye, brian
Why?
Typically when an application is developed at SAP, the developer must make provision for all possible fields of information that must be displayed and/or queried from the user. However, in specific business cases, or depending on specific country laws, all fields might not be required. Also in some cases, fields in one scenario can be flagged required, versus in another they are only optional.
The typical starting point will be a complete formlayout done during the development. On top of this a customization layer is placed. The automatic reading and applying of the customization layer is automatically done by the phtmlb fL.
What?
For each field, a default behaviour is assumed. This is the behaviour that is defined by the developer during development time. For example, it could be specified that email address must be required. During the runtime it is now possible to overwrite the default behaviour with a customization entry for the field.
The following options are supported:
As Defined: The formLayoutItem in displayed as it has been defined during development.
Invisible: The formLayoutItem is not placed on the formLayout. It is immediately removed. All following items below it, will be moved up to fill its position.
Hidden: In this case, the formLayoutItem is placed on the formLayout, but not displayed. The item reserves its slot, and an empty slot will be displayed. However, after all items have been placed on the formLayout, a row "compression" is done, whereby all rows that contain only hidden elements are removed. Hidden is important for cases where columns next to one another must align. A typical example would be name & surname horizontally aligned. If now one item is invisible before this row, the two items will not be aligned anymore. With hidden, this alignment will be kept, and we still have the benefit of empty rows been removed.
Required: Sets the required flag for the item. Label of item will be rendered an indication that it is required (usually little red asterix after the label).
Optional: Can be used to customize a required field to be not required.
Read Only: Field value is only displayed.
What is index?
Customization is stored for a formLayout under the key that is build from the BSP application namespace, BSP application name, plus the page/view on which the formLayout is placed. It is assumed that there will only be one formLayout per view. A typical example would be:
SAP/SBSPEXT_PHTMLB/FORMLAYOUTSAMPLE.HTM
In addition, a customization key must be specified. Typical examples would be to say this is the default customization for USA, or for the specific branchen Losuegn. The customization key must be supplied with the <phtmlb:fL> tag, and only then will the customization data be read from the database.
Tables
For customization there are three interesting tables.
The first table PHTMLB_FLI is completed by the developer, and defines a list of all the formLayout items that can be customized. Only for those flItems which customization is possible, will entries be made in this table. The table contains three components:
NS_APPL_PAGE This is the unique key that identies the formLayout, consisting of namespace, application and page/view.
FLI_ID Id string of the specific formLayoutItem.
COMPONENT This is software component to which development applies, for example SAP_BASIS for all BSP development work done by us.
The second table PHTMLB_FLI_TEXT is just a language dependant text table that describes each item in the formLayout.
The tables PHTMLB_FLI and PHTMLB_FLI_TEXT are not using during the runtime. They are only of interest for design time. Note that NO tools are provided to make any entries in these tables. This is considered to be in the application domain, and will usually be part of the customization process of the application.
The third table PHTMLB_FLI_CUST is the only table that is read during the runtime. It is assumed that a customization tool has made the relevant entries for this table.
NS_APPL_PAGE see above
VARIANT_KEY This is the specific customization layer that is currently active. This string is equavalent to <pthmlb:fL customizationKey>. It is used to pull a specific customization.
FLI_ID see above
MODIFIER This is the new value to apply. For the possible values, see DDIC domain PHTMLB_FLI_MODIFIER.
For an example of customization, see BSP application SBSPEXT_PHTMLB, pages formLayout.htm. In this example, the customization can quickly be set via dropdown listboxes. On each request the PHTMLB_FLI_CUST is quickly updated and then the formLayout will find the set of new customization data to use.

Hiding fields in Review button in ESS iviews

Similar Messages

Maybe you are looking for