ESS FPM Application translation

Hi,
Could someone guide me through the process to translate an FPM application, configured with FPM Application Editor to several languages?
We have to translate an spanish app we developed to catalan.
We created our own cfg portal component with FPM Application Editor, but then I don't know how to translate the texts defined.
I tried to modify the cfg component in NWDS but I don't know in which perspective should we work with it.
Thanks,
Gabriel.

It's all done in portal.
Content Managment -> Portal Content Translation
Create the translation pool with the application created and then translate it.
Regards,
Gabriel.

Similar Messages

(ESS) FPM applications, cfg DCs & Enterprise Portal / Portal Content DC

Hi everyone,
I just replied to the Road Map Step Label Changes Issue thread in the Java Programming forum. Since I had a very specific question that seems more suitable in this forum, I decided to post it again over here.
short introduction
The SAP ESS SC contains FPM (Floor Plan Manager) applications that you can modify at runtime from within the portal using the Self-Service Administrator portal role. The point is that this content is also contained in the SAP_ESS SC in NWDI. It's contained in all those cfg DCs. They basically contain a (zip)archive that contains other (zip)archives that contain different XML files that eventually describe the FPM application. So what happens is that you can modify the FPM applications at runtime, but your changes are overwritten when the cfg DC is deployed afterwards.
the details... and the questions...
Concerning those cfg DCs. They're a very specific type of DC. The type is "Enterprise Portal" and the subtype is "Portal Content". In NWDS, this is described in the following XML file: C:\Program Files\SAP\IDE\IDE70\eclipse\plugins\com.sap.ide.eclipse.component.provider_2.0.0\componentTypes.xml When I was using NWDS 7.0 SP12, this particular type of DC was not visible (if I remember it correctly), i.e. I could not create a new DC of this type. NWDS SP12 also didn't contain the necessary plugin, com.sap.portal.pcd.ide.eclipse.nwdi.ui.NewPortalContentWizard, as described in the same XML file (or at least I couldn't find it). Since I installed NWDS SP14, the plugin is present and I can create this type of DC myself. But that doesn't help me that much, since the wizard just creates some empty DC and I don't have a clue how to populate it with the content of the FPM application. Unfortunately I also don't have a clue about how to modify the existing cfg DCs in SAP_ESS.
BTW, some changes, e.g. a small textual change, is relatively easy to do: unzip the archive(s) in the cfg DC, modify the text in one of the XML files (for some reason the translation of the roadmap steps are present 4 times, if my memory doesn't fail on me) and zip everything again. This works fine for me.
the $1 million question...
Obviously, what I really like to know: how to modify the FPM applications on the portal using the Self-Service Administrator role (that's easy) and export it to a suitable archive that can be imported in the (SAP_ESS) cfg DCs? As long as this is not possible, meaning I don't have a clue how to do it, I'm forced to deploy the modified FPM applications, which I exported as an epa file, after each NWDI transport. And this is not very practical...
I hope my (probably a bit too complex) explanation makes any sense.
If someone else knows more about this subject or how to deal with it, please let me know. tnx!
Kind regards,
/Sigiswald

Hi,
Did you ever found a suitable solution for this. We are facing the same problem at the moment.
Kind Regards,
Igor Vernelen.

How to modify a VAC in a standard FPM Application

Hello All,
I have a requirement in the project where I have to modify the standard SAP delivered FPM application. But this does not involve any creation of new webdynpro iview , but to modify a VAC in the application. It is related to essbensap.com, where I ahve to modify the VAC VcBenifitsPlanSelection.
Ploblem comes when I try to modify the implementation code of the view PlanSelectionView. It says:
Checkout is not possible. See below for details.
The operation requires the writeability of the following Objects:
View com.sap.xss.hr.ben.planselection.PlanSelectionView
======>problem: DTR workspace is not modifiable /DN1_XSS_D~ess~ben~sap.com/src/packages/com/sap/xss/hr/ben/planselection/PlanSelectionView.wdview.xlf
======>problem: DTR workspace is not modifiable /DN1_XSS_D~ess~ben~sap.com/src/packages/com/sap/xss/hr/ben/planselection/PlanSelectionView.wdcontroller
======>problem: DTR workspace is not modifiable /DN1_XSS_D~ess~ben~sap.com/src/packages/com/sap/xss/hr/ben/planselection/PlanSelectionView.wdview
My question is :
Is is possible to modify the standard VAC (VcBenifitsPlanSelection). If so, then my NWDI does not allow me to do so.How to solve this error message?
Is there any other way to solve this requirement, without any configuration issue?
Please help, as the requirement is very urgent.
Thanks,
Sonali.

Hi Sonali,
make sure have proper auths for NWDI.
Regards,
Raj

How do I create event links in the FPM Application Editor?

I'm am attempting to add a new step to the roadmap of ESS/BEN Benefits Application. I've created a new VAC component and a corresponding view (using the "self-service administrator" role).
When using the FPM Application Editor to create a new perspective, I need to add an event link but receive the error, "Either the perspective "Smoker Verify" has no view assigned to it or none of the view(s) assigned have any event assigned to them".
How do I assign events to my new view? Please assist and thanks in advance.
-Jeff Karls-

I see that the events are defined on the views themselves in the portal content.

Portal Workprotect in Talent Profile - WebDynpro ABAP FPM application

We are trying to implement Workprotect in ESS - Talent Profile application (HRTMC_EMPLOYEE_PROFILE). The requirement is that when user had entered data in either Internal work experience, External Work experience or other tabs; before he has saved the data, if the user clicks on some other link in portal or try to close the window, Portal work protect that is enabled should prompt the user to save the data or risk losing data.
What has been done so far:
1. Enabled Workprotect on Portal:
Step 1: In the portal, go to System Administration -> System
Configuration -> Service Configuration.
Step 2: In the portal catalog, Select
application "com.sap.portal.epcf.loader" and open the properties for
service "epcfloader" for editing
Step 3: Set property workprotect.mode.default = 3
Step 4: Save -> Restart service
Now, Portal Work protect is enabled.
2. On the Talent application end, I have seen many posts in forum & FPM related workprotect documentation. But, it is not clear as to how this actually works when it comes to FPM application.
The documents says FPM allows application to make use of work protect
mode offered by Portal. To achieve this, the application must u2018tellu2019 the
FPM whether it contains unsaved
(u201Cdirtyu201D) data. For this, the FPM provides the Web Dynpro Interface
IF_FPM_WORK_PROTECTION. In the is dirty method, you have to put
METHOD is_dirty.
if * component contains unsaved data
ev_dirty = abap_true.
else.
ev_dirty = abap_false.
endif.
ENDMETHOD.
Questions:
1. If you see the shared application component HRTMC_TP_SHARED_DATA, it implements interface IF_FPM_WORK_PROTECTION. But, the isdirty method in the component controller has already existing code
METHOD is_dirty.
ev_dirty = wd_this->mv_is_dirty.
ENDMETHOD.
Where should we put the code given below as described in FPM documentation. In shared component or in individual components like HRTMC_TP_WORKEXP_INTERNAL, HRTMC_WORKEXP_INTERNAL, HRTMC_TP_EDUCATION
etc.
METHOD is_dirty.
if * component contains unsaved data
ev_dirty = abap_true.
else.
ev_dirty = abap_false.
endif.
ENDMETHOD.
And, the line "* component contains unsaved data" as described in document- how do we code this for talent profile considering that there are multiple components, shared component etc? My requirement is that if user has entered some data in any of the tabs like internal work experience, external work experience, then work protect should work if
user tries to navigate away or close browser.
2. If you see general documentation for Work protect and webdynpro (not for FPM), it says that the application must define a special status (dirty flag), which tells the portal when there is unsaved data. You can set and cancel this status (TRUE, FALSE) using method
SET_APPLICATION_DIRTY_FLAG in interface IF_WD_PORTAL_INTEGRATION.
And it goes on to say that one must set application flag dirty
SET_APPLICATION_DIRTY_FLAG
exporting
DIRTY_FLAG = TRUE | FALSE
and also set work protect mode
call method L_PORTAL_MANAGER->SET_WORK_PROTECT_MODE
exporting
MODE = NONE | APPLICATION_ONLY | BOTH
3. Which is the correct way to enable Work protect in case of Talent profile applications? Which method of which component should should we add code to? Which of the above ways should we follow ( Interface IF_FPM_WORK_PROTECTION or IF_WD_PORTAL_INTEGRATION) ? Which component and which method should we Set Work protect and Set isdirty
Please advise.

Hi Experts,
Can you please provide some useful info in implementing work protect in Standard FPM WebDynpro ABAP applications? In this case, as mentioned above, the application is ESS Talent Profile application (HRTMC_EMPLOYEE_PROFILE).
Thanks,
Sandeep

ESS standard Application modification

Hello,
We are on ERP 6.0 EHP4.
We have got ESS and MSS implemented. Applications are working fine now.
However user has not yet reverted with any modification on standard one...but still I need to find out on how I can make changes to existing standard applications.
Below are places where it could be done...according to me :
1. Make service specific settings.
Here it is possible to hide fields and show new fields based on existing infotypes. These settings are done in R/3 SPRO Tcode.....
2. Iview Personalization.
Here you can make necessary changes in UI presentation/layout. Making fields disabled or readonly. These are done in portal PCD....
3. FPM modification.
you have to use Self services administrator role here. This is a separate business package which you need to get from SAP.
Please comment on whether my findings are correct ?
Secondly do I need NWDS to modify on any part of existing applications. Can anybody give 1 example where I need to modify WD Java code/view.
Is Self Services Administrator role free from SAP if you have already purchased ESS/MSS Self-Services Package.
I read an article which is below :
http://wiki.sdn.sap.com/wiki/display/profile/ESSPersonalInformationUIenhancementwithoutmodification
However I do not feel it is now applicable for our Business package version.
Can anybody throw a light on ...if I am missing out on something......

Hi Saurabh
1.     Once you install ESS and MSS business package you will get the Self Service Administrator role. We donu2019t need to buy the additional licenses separately for it.
                     About the modification of FPM application, we can modify the FPM applications/views but it is recommended not to modify the SAP delivered FPM configuration. We need to create a new FPM application.
2.     We need NWDS, to enhance the SAP delivered functionality or to fix any of the defects etc. for example I have seen some of the clients asking for the check image on the edit screen of bank application to show what is routing number and account number for the end users, some of the clients they need confirmation, accept terms and conditions etc while creating/updating a bank information etc.
For building the custom applications.
3.     NWDI and NWDS are different, they go together. If itu2019s a big project then we would need a dedicated system for NWDI. I believe it would need the license. If you are using NWDS and also ESS & MSS business package then you have to go for NWDI for creating custom apps or for modifying the standard apps.
NWDI: is used for source code repository, version control, build, transports etc for the java code. In simple terms, NWDS is the front end to the NWDI.
4.     The url u posted is not obsolete, its very important and still holds good. If we want to enhance the back end i.e. infotype and show the enhanced fields of the infotype on portal then we have to go in that route.
5. I think you have covered all the ways for modification and customization.
Regards
Yugandhar Reddy

Exception While Developing FPM application.

Hi All,
We are on EP7.0/ECC6.0.
I'm trying to develop a new ESS webdynpro application using FPM. I'm using the steps as given <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/43/3b709efa6c1bcbe10000000a1553f7/frameset.htm">here</a>
The application throws following exception while doing 'deploy new archive and run' from developer studio.
java.lang.NoSuchMethodError: com.sap.pcuigp.xssfpm.java.ApplicationContext.isSplitupApplication()Z
 at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:214)
 at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)
 at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)
 at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)
 at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)
Full Exception trace is:
java.lang.NoSuchMethodError: com.sap.pcuigp.xssfpm.java.ApplicationContext.isSplitupApplication()Z
 at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:214)
 at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)
 at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)
 at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)
 at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:190)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:707)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
It also gives Correction Hints as:
Correction Hints
The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
I have verified that NWDS and NWDI are on same level.
Any ideas how to resolve this??????
cheers~
avadh

Hi ,
I guess you have some lline..
with
getApplicationContext().isSplitUpApplication();
Are the versions of SCA s in NWDI ( i.e xssutils) which you have referenced in ur component.. and the ones deployed in your webAs java server .. the same ?
It seems to be a mismatch.. or the reference declaration might be jus build time .. something like that .. ?
Regards
Bharathwaj

How to change the webdynpro title of an FPM application

Hello All,
Currently my FPM application displays, the technical webdynpro application name as title, how can I set it to a translatable string?
Many Thanks,
Dhanz

Hi
create cutom IDR ..
Regrds
jayaprakash T

Custom FPM Application Issue

Hi all,
I developt a custom ESS WD application using FPM. On the last step I add the confirmation Links view (com.sap.xss.ser.xssconfview.vc.VcLinks)
In addition I cofigure the links that I want to display in the last step I set the application parameters in order to diplay the links.
On the last step of my application I set 3 links:
Go to Area Page (works fine)
Go to Overview Page (works fine)
Restart the application (does not work)
When I press the link I got the following error WDDynamicRFCExecuteException: Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
I also did a Trace of the RFC called and the application make an effective call to the HR_SSC_CREATE_SERVICE_OBJECT and HRXSS_SER_GETCONFSCRLINKS as any other ESS Application.
Do you have any idea of what could I be missing?
Regards,
Orlando Covault

clearly your confirmation link customised has no resouce assigned to it, you need to have a correct resource
for example in standard we have like this
IMG : personnel management -> Employee selfservice -> General Settings
    -> Homepage for self-sevice -> services
    -> Define links on confirmation page
    -> EMPLOYEE_TIMESHEET_RELEASE
    -> Restart Link Text EMPLOYEE_WORKTIME_RECORDWORKTIME05
take the cue from this and build yours correctly!

Custom FPM Application for MSS

Hi folks,
I am trying to create some custom portal pages for MSS that will contain the Employee Search and other iViews based on the Generic iView List and/or Generic iView Table templates.
The Business Package document for MSS (mySAP ERP) says that I have to create a new delta-linked FPM Application and assign the required views to the perspective, which I have done via the Self Service Administrator role.
The problem is, when I then try to create the new WebDynpro Java iViews, I can't see my FPM Application or views in the list.
I am aware that I can just add extra views to the standard FPM Applications for MSS, but I really don't want to risk having those overwritten by support packs later on.
Has anyone successfully done this before?
Regards,
John

btw, I was kidding about the creators of the old FPM sitting in the corner
When the new Java based ESS/MSS screens first came out they were so much better than the old IAC's, and we were very grateful for that. We used them extensively where they could just be deployed "out of the box".
Once we figured out how to integrate our own generic query iViews into the FPM framework for MSS we used lots of those too.
I guess in a way they were too successful, and as a result the business kept demanding more and more self service applications that often weren't delivered as standard.
Not being a Java shop (i.e. zero Java developers) we soon found that there was only so far we could go with the standard WDJ services. Even something relatively simple like adding another standard field to a standard ESS screen without going down the NWDI path proved to be a rather frustrating process (for us at least), so we just started buidling our own with WDA.
From a functional perspective, I don't really care if an application has been built in Java or Abap, as long as it does what I want, every time. I can't see us going back and changing the standard Java services that we still use over to Abap, but for future developments the reality for us and lots of other customers is WDA.
cheers.
John

SAPPCUI_GP for FPM Application

Hi All,
we are developing new FPM applications (not for ESS/MSS). To do that, we have created a track on JDI/CMS and imported SAP-JEE, SAP_BUILDT and SAP_JTECHS sca files. we know that PCUI_GP is required to build FPM application and couldnt find the same (SAPPCUI_GP.sca). We got PCUI_GP.sca file from ESS package.
Our question is,
Do we have a .sca file for PCUI?
Is that what we done is right?
Wont this (ESS PCUI) harm the actual ESS/MSS applications?
Waiting for your reply.
Thanks
Suresh

Hi,
Please find this you need to deploy this sap.com_SAPPCUI_GP
Cheers,
Apparao

ESS FPM

Hi sdn friends,
I´m triying to reduce the FPM steps of the banking service. I need to allow just-read data for my ess users (remove step 2 an 4. My problem is when I'm triying to remove an FPM step from the FPM application it's explodes when accesing the service.
Guru's can you help me.
NW 2004s and ERP ECC 6.0
Regards,

David,
For this you have to use the Self Service Administrator Role on the portal which comes in a separate package as a .sca file in Service Market Place ....download it and deploy it using JSPM....then assign the role to user and make the change there in FPM Applications....
Hope it helps...
Shikhil

Application Translation Not Working - Primary Key Error

I had created an application translation to Spanish but it wasn't displaying my Spanish translation. I was going to try and redo it so I tried creating a new mapping and then seeding the translatable text. I got a primary key error "ORA-20001: Seed insert error: WWV_FLOW_TOPLEVEL_TABS.TAB_TEXT ORA-00001: unique constraint (FLOWS_030100.WWV_FLOW_TRANSLATABLE_TEXT_PK) violated".
I went in and deleted what I had done through APEX for this app and tried to create a new application but still get the primary key error when I try to seed it. I gave it a new translated application ID but that doesn't seem to help. Anyone have this problem or no of the reason I'm having this issue?
Thanks.

Hi David,
Thanks for reporting this. This was an interesting problem to solve.
As it turns out, it was a logic error in Application Express (i.e., bug). When deleting a translation mapping, the associated strings in the translation repository would be deleted for that application, but if and only if you had actually published the application.
I think this is why you could never get Spanish working properly - you had never actually published the application the first time. So I'll bet what you did is deleted the original mapping, then you recreated the mapping for the same language but with a different translated application ID. Since you had never published the application from the original translation mapping, and there were orphaned rows in the translation repository, you encountered a "collision" when you tried to seed the second time with the different translated application ID.
Your action of deleting rows from WWV_FLOW_TRANSLATABLE_TEXT$ cleaned up these orphaned rows. As you stated, this isn't recommended to perform DML on the underlying APEX tables. A couple alternatives could have been:
1) Before deleting the translated application mapping, actually publish the application and then delete the mapping.
2) If you had deleted the mapping already, you could recreate the mapping for the same language and with the original translated application ID. Then, publish the application and then go back and delete the mapping.
I realize all this sounds crazy. But it was only an issue because you had not actually published the application. Not your fault, though, as this is a bug in APEX.
This bug will be fixed in Application Express 4.0. This way, you won't have to worry about if you published or didn't publish. The orphaned rows will be cleaned up when you delete a mapping.
Thanks again for reporting this.
Joel

How to call FPM application from a WD ABAP view

Hi
My requirement is to navigate to an FPM application on click of a button in a WD component. And along with the navigation I need to pass parameters (internal table) along with it.
Can anyone suggest ways to achieve this. And also how to get the parameter values in FPM application.
Regards
Prashant

Dear Prashant
Check this:
[Passing Data to Webdynpro from normal module pool screen;
Kind Regards
/Ricardo Quintas

Error in FPM Application / View Editor

Hi!
I am trying to use the FPM Application Editor and got the following error:
 
error. java.lang.NullPointerException at com.sap.xss.config.PcdNamingUtil.removePcdPrefixFromId(PcdNamingUtil.java:22) at com.sap.xss.cfg.edt.FPMApplicationEditor.doInit(FPMApplicationEditor.java:552) at com.sap.xss.cfg.edt.wdp.InternalFPMApplicationEditor.doInit(InternalFPMApplicationEditor.java:430) at...
 
I could solve this by following this Thread:
 
Re: Error in FPM Application
 
But not I get two new errors in the FPM Application Editor and FPM View Editor.
 
FPM Application Editor:
 
The initial exception that caused the request to fail, was:
 
 com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException
 
 com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException
 at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseException(MessageManager.java:430)
 at com.sap.xss.cfg.utils.FPMEditorUtilitiesInterface.raiseException(FPMEditorUtilitiesInterface.java:399)
 at com.sap.xss.cfg.utils.wdp.InternalFPMEditorUtilitiesInterface.raiseException(InternalFPMEditorUtilitiesInterface.java:203)
 at com.sap.xss.cfg.utils.wdp.InternalFPMEditorUtilitiesInterface$External.raiseException(InternalFPMEditorUtilitiesInterface.java:266)
 at com.sap.xss.cfg.edt.FPMApplicationEditor.doInit(FPMApplicationEditor.java:568)
 at com.sap.xss.cfg.edt.wdp.InternalFPMApplicationEditor.doInit(InternalFPMApplicationEditor.java:430)
 at com.sap.xss.cfg.edt.InconsistentObjectExceptionView.doInit(InconsistentObjectExceptionView.java:174)
 at com.sap.xss.cfg.edt.InconsistentObjectExceptionView.wdDoInit(InconsistentObjectExceptionView.java:100)
 at com.sap.xss.cfg.edt.wdp.InternalInconsistentObjectExceptionView.wdDoInit(InternalInconsistentObjectExceptionView.java:112)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
 at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:182)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:177)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

 
And in the FPM View Editor:
 

java.lang.NullPointerException
 
at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:70)
 at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)
 at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)
 at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)
 at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:76)
 at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)
 at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)
 at com.sap.xss.cfg.utils.FPMEditorUtilitiesInterface.loadFPMView(FPMEditorUtilitiesInterface.java:223)
 at com.sap.xss.cfg.utils.wdp.InternalFPMEditorUtilitiesInterface.loadFPMView(InternalFPMEditorUtilitiesInterface.java:195)
 at com.sap.xss.cfg.utils.wdp.InternalFPMEditorUtilitiesInterface$External.loadFPMView(InternalFPMEditorUtilitiesInterface.java:258)
 at com.sap.xss.cfg.edt.fpmview.FPMViewEditor.onInit(FPMViewEditor.java:381)
 at com.sap.xss.cfg.edt.fpmview.wdp.InternalFPMViewEditor.onInit(InternalFPMViewEditor.java:263)
 at com.sap.xss.cfg.edt.fpmview.FPMViewEditorBasicView.wdDoInit(FPMViewEditorBasicView.java:100)
 at com.sap.xss.cfg.edt.fpmview.wdp.InternalFPMViewEditorBasicView.wdDoInit(InternalFPMViewEditorBasicView.java:180)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
 at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
 at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:182)
 at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:177)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

 
Thanks for your help!

Hi Serkan,
I am also facing the same problem.
Getting the error "com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException "
for FPM application editor and "java.lang.NullPointerException " for FPM view editor.
Kindly Let me know how did you solve the problem?
The SAP note 1137578 did not help.
Thanks in advance!

ESS FPM Application translation

Similar Messages

Maybe you are looking for