ESS Benefits Generic Enrollment - Different behavior backend v/s portal

We are using the ESS Benefits generic enrollment service for enrollment kicking off the adjustment reasons on IT 0378.
Here is the configuration set up, trying to simplify to explain the matter. We are on ECC 6.0 with EHP2.
1.  Configured one plan type in savings category.
2.  Within this plan type,  configured 2 plans.
3.  Configured all other related configuration to set up the 2 plans.
4. Configured the adjustment reason and the appropriate plan type created in step 2.
5.  Created the required adjustment reason on 378.
In HRBEN0001 transaction via backendwe can  see the 2 plans configured within the plan type.
But when Trying to enroll from ESS - only one plan can be seen for that plan type, the other plan is not shown at all.
OK - eventually, debugged and found this piece of code in FM HR_BEN_ESS_FILL_SELECTION_DISP.  The 2 different plans are there until this piece of code takes one of them Off...
  CODE -
3.) Reduce entries to one entry per type and period
  delete adjacent duplicates from selection_display_gt
    comparing pernr
              barea
              bpcat
              pltyp
              begda
              sprps.
CODE -
This FM is called only for ESS application and not for backed program.
What we do not understand is why is it behaving differntly on backend v/s portal.
Any information or experience with this form any one of you will be highly appreciated.
Thanks.

Siddharth,
Thanks for your reply. Yes ESS has its own FMs.  The UI, user exits, BADIs etc are different for backend v/s front end.
What we are not clear with, is the different behavior in core functionality --  i.e. When the adjustment reason is processed from the backend using HRBEN0001 - The 2 plans within the Plan Type are available for elections. BUT the same adjustment reason for the same penr when processed from  ESS - there is just one plan available for elections.
It's clear from the code, that it is deleting one plan and this code is within the FM which is called only from ESS.  But we are still not sure why it should behave differently i.e. 2 plans via backend v/s one plan  via ESS. 
Wanted to see if anyone can share any information if they have a similar benefits set up .. 2 plans within one plan type FOR savings plan category and then having a adjustment reason set up.
Regards.

Similar Messages

  • Generic Enrollment link not showing up on Portal

    Hi,
    Generic Enrollment link not showing up in portal. I have Adjustment reason record in 378 and openenrollment is open.
    Both are open but I do not see General enrollment link in portal.
    Even I took off proxy class entry from genral enrollment CL_BENEFITS_AREAPAGE for testing  then only open enrollment link come up.
    How can I show both generic enrollment and open enrollment together.
    I appreciate immidiate help.
    Regards
    Mark

    Hi Mark,
    Please ensure that the user has read access to Infotype 171 (General Benefits Information) for Authorization Object P_PERNR. 
    You don't have to take the Proxy Class entry out. The proxy class is required as it determines which links are displayed based on the employee country code and benefits adj reasons.
    Thanks,
    Zubair Khan
    Edited by: Zubair Khan on Nov 16, 2011 11:22 PM

  • ESS Benefits open enrollment - Issue

    Hi,
    When we click on the benefits open enrollment link, we do not want some of the plans to be displayed to the ess user. Is there any way to control it ( SPRO or BAdI ).
    Env - EP 7.0, ECC6.0
    Thanks,
    Ravi

    I posed the same question to an ESS consultant who responded with the following:
    "The plans presented in benefits enrollment (PZ14) and Participation Overview (PZ07) are list output from ABAP.  You can go into the program and select or exclude some of them based on certain criteria.  I've seen customers extend the Plan infotype to add a flag field to make it configurable to show, not show a given plan."
    Since specific instructions weren't given, I wouldn't consider the issue answered.
    However, I can provide the following work around:
    Due to the fact that different populations have different open enrollment period timeframes, and all populations have been configured under one benefit area...we decided to create an "Open Enrollment Adjustment Reason" for each group instead.  Thus, the Adjustment Reason permissions will only display the plans we want the employee to see via ESS.  Prior to the open enrollment period for the population, we will run the Mass Adjustment Reason report to create IT378 for all relevant employees.  The OE offer will appear as another Adjustment Reason under the Enrollment service in ESS.

  • ESS: Benefits: OPEN ENROLMENT NOT VISIBLE in ESS

    Hi Gurus,
    This is regarding a SAP HR implementation for US.
    Open Enrollment Service is giving a dump with error
    u201CNo Correct Adjustment Reason Specifiedu201D.
    Following has been checked, still unable to view it in ESS.
    u2022     Employees are configured for running Open Enrollment for employees.
    u2022     Employees are assigned to appropriate PA and PSA. Country grouping for both the employees is USA: 10.
    u2022     Maintained appropriate data in Infotype 0171(General Benefits Information). Correct benefit program grouping is done for both employees ie maintained first and second program grouping for both employees.
    u2022     Maintained Benefit Adjustment Reasons for both the employee i.e. Infotype 0378(Adjustment Reason Data).
    u2022     Maintained Open Enrollment Offer for employees between 09.13.2008 and 10.13.2008. (MM/DD/YYYY).
    u2022     Program HRBEN001 is running correctly in backend. Both employees are able to choose different benefit plans during the open enrollment period.
    u2022     User  is having SAP_ALL authorizations.
    u2022     Resources and Services are correctly defined and linked in the backend.
    u2022     HR_BEN_ESS_RFC_ENRO_REASONS is a SAP defined function module to fetch benefit data from Benefit module and post it to ESS internal tables. Testing it in the background using transaction se37 gives correct results in the backend. It is displaying Open Enrollment as one of the Benefit Reasons.
    Kindly help with any pointers at the earliest.
    Thanks & Regards
    Kumarpal Jain

    Kumarpal,
    did you check this thread
    https://forums.sdn.sap.com/click.jspa?searchID=17218337&messageID=6299502
    Thanks
    Bala Duvvuri

  • ESS - Benefits - Open enrollment  (Concurrent employment is enabled)

    We are trying to set up ESS open enrollment. After adding/editing/changing plans --> review enrollment --> Save.
    On saving, getting an error "rfc_error_system_failure" on the ESS screen.
    Checked with ST22 for the error details. The name of runtime error is "uncaught exception" and the exception is "CX_HRPA_VIOLATED_PRECONDITION". 
    Based on a  Similar thread on the forums --> Link : [Re: CX_HRPA_VIOLATED_PRECONDITION using HR_INFOTYPE_OPERATION to insert rec; and Sap note #  493984  , the error seems to be related with concurrent empoyment.
    Analysis:
    1. If CE is disabled, there is no error - open enrollment works fine both in R/3 (HRBEN0001) and via ESS
    2. If CE is enabled," open enrollment" in R/3 using HRBEN0001 - there is no error.
    3. Error occurs only when "open enrollment" is accessed through ESS, when CE is enabled.
    Would like to know if some one can share their experience on using ESS open enrollment when CE is switched on?
    Version details: ECC 6.0 (support pack level 22 for SAP-HR and EA-HR), EP 7.0 , ESS BP 1.0
    Thanks,
    Javed.

    Problem solved after deploying note # 1020389

  • Generic Enrollment error

    Hello,
        I am trying to set up ESS. When I click on ESS --> Overview --> Generic Enrollment, I am getting the following error:
    The initial exception that caused the request to fail, was:
       java.lang.StringIndexOutOfBoundsException
      at java.lang.String.substring(String.java:1067)
        at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.setLeadSelectionFromURLParam(VcBenefitsEnrollmentReasons.java:255)
        at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.onBeforeOutput(VcBenefitsEnrollmentReasons.java:184)
        at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasons.onBeforeOutput(InternalVcBenefitsEnrollmentReasons.java:182)
    at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasonsInterface.onBeforeOutput(VcBenefitsEnrollmentReasonsInterface.java:129)
    ... 53 more
    Could anybody please guide me as what could be wrong with the ESS configuration?
    We are on EP 7.0, ECC 6.0, ESS SP 11.
    Thanks much for you information in adavnce!!
    ~~~LB

    Hello Naga -
       Thanks for your information. I talked to our functional team and they said, they are able to manually do this through the HRBEN0001 transaction. So, they do not think anything is wrong with the value of the adjustment reason.
    Could it be anything related to the Webdynpro program that executes this?
    Here is the detailed exception information:
    The initial exception that caused the request to fail, was:
    java.lang.StringIndexOutOfBoundsException
    *     at java.lang.String.substring(String.java:1067)*
    *     at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.setLeadSelectionFromURLParam(VcBenefitsEnrollmentReasons.java:255)*
    *     at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.onBeforeOutput(VcBenefitsEnrollmentReasons.java:184)*
    *     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasons.onBeforeOutput(InternalVcBenefitsEnrollmentReasons.java:182)*
    *     at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasonsInterface.onBeforeOutput(VcBenefitsEnrollmentReasonsInterface.java:129)*
    *     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface.onBeforeOutput(InternalVcBenefitsEnrollmentReasonsInterface.java:132)*
    *     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface$External.onBeforeOutput(InternalVcBenefitsEnrollmentReasonsInterface.java:208)*
    *     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)*
    *     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)*
    *     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)*
    *     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)*
    *     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:748)*
    *     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)*
    *     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.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)*
    *     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)*
    *     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)*
    *     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)*
    *     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)*
    *     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)*
    *     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)*
    *     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)*
    *     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)*
    *     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)*
    *     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)*
    *     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)*
    *     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: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: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(AccessController.java:215)*
    *     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)*
    *     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)*
    Please trhow in some light on this.
    Tahnks for your suggestion in adv,
    ~~~LB

  • ESS Webdynpro – Benefits – Open Enrollment

    We currently have the ITS application for benefits open enrollment (PZ14) up and running. We are trying to setup the Webdynpro service for Open Enrollment.
    We are on ECC 6.0, EP 7.0 latest SPs and we are using XSS 600 webdynpro Software Components.
    Problem:
    When we click on Open Enrollment service (Webdynpro), the following message comes up:
    “No plan selections could be prepared for the specified enrollment reason. Contact your Benefits Administrator for assistance”.
    The same service works fine with the ITS service for the same PERNR. The ITS service is able to show up the Open Enrollment without any problem.
    Even if I include an entry in Infotype 0378 – Adjustment Reasons, the new enrollment reason can be seen under the ITS Service but not under the webdynpro service.
    Is there any additional customization (configuration) required for the Webdynpro Service for Open Enrollment.
    thanks,

    Experiencing the same issue.  Did someone find a solution to this?
    Thanks!

  • ESS Benefits and Payments

    Hi,
    I am getting the following errors when i click the "FlexBens: Open Enrollment" as well as "FlexBens: Print Form" on ESS benefits and payments
    No correct adjustment reason specified:
    com.sap.pcuigp.xssfpm.java.FPMRuntimeException: No correct adjustment reason specified
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
         at com.sap.xss.hr.fbn.enrollmentreasons.VcFlexBensEnrollmentReasons.isConsistent(VcFlexBensEnrollmentReasons.java:206)
         at com.sap.xss.hr.fbn.enrollmentreasons.wdp.InternalVcFlexBensEnrollmentReasons.isConsistent(InternalVcFlexBensEnrollmentReasons.java:174)
         at com.sap.xss.hr.fbn.enrollmentreasons.VcFlexBensEnrollmentReasonsInterface.isConsistent(VcFlexBensEnrollmentReasonsInterface.java:183)
         at com.sap.xss.hr.fbn.enrollmentreasons.wdp.InternalVcFlexBensEnrollmentReasonsInterface.isConsistent(InternalVcFlexBensEnrollmentReasonsInterface.java:152)
         at com.sap.xss.hr.fbn.enrollmentreasons.wdp.InternalVcFlexBensEnrollmentReasonsInterface$External.isConsistent(InternalVcFlexBensEnrollmentReasonsInterface.java:228)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:507)
    We are on ESS 6.0, EP 7.0.
    Thanks for your help...

    Hi Sharadha,
    Thanks for your quick response, i followd your steps now i am getting diff error.
    Flexible benefits is not activated for benefit area 10:
    com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Flexible benefits is not activated for benefit area 10
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
         at com.sap.xss.hr.fbn.FcFlexBens.reportRFCError(FcFlexBens.java:1104)
         at com.sap.xss.hr.fbn.FcFlexBens.reportRFCError(FcFlexBens.java:1070)
         at com.sap.xss.hr.fbn.FcFlexBens.callRFCInitSelection(FcFlexBens.java:1364)
         at com.sap.xss.hr.fbn.FcFlexBens.readPlanSelection(FcFlexBens.java:525)
    Thank you..

  • "Edit Personal Profile" - ESS Benefits

    Hi
    We have a requirement to open the "Edit Personal Profile" in ESS Benefits "New Hire Enrollment" (GAF) in place rather opening in external window. I changed the property in the launchpad ESS/MENU for the "Personal Profile" under Benefits Enrollment to Force Inplace or Inplace but it is not taking effect in portal. Still opens in the external window. Am I missing something or it is handled by the code? Any suggestions would help.
    Thanks, Raj

    typically its meant to launch a new window 1926925 - READ_ONLY_PERSONAL_PROFILE in ESS Benefit Enrollment WDA its coded in the code, so above changes wont take effect in ESS/MENU Webdynpro component:HRESS_C_BEN_ENRL_CONFIG met:ON_EDITCLICK ls_parameter-value = 'EXTERNAL'. change it to ls_parameter-value = 'EXT_HEAD' in both the places. check here if you can get more information on this http://scn.sap.com/thread/3508230

  • Restricting certain plans from ESS during open enrollment

    Hi Experts,
    We have a requirement to restrict plans from ESS during open enrollment. Please let us know the best possible solution to acheive the same.
    We have found that Proxy class CL_BENEFITS_AREAPAGE which is assigned to the service can be copied and enhacned to filter the plans, is this the right approach?

    I had that exact same delima, but one of our consultants pointed us to the transaction: HRBEN00ADJRSN
    This is a mass load of adjustment reasons.  You just need to feed the program the total time allowed for adjustments and things like start of records date and end of records date.  Because of the dates and the potential for different plans to have different dates, we actually have two open enrollment adjustment reasons.  We have one for Flexible spending where I give the 1/1 begin date and a 12/31 end date since it is only effective for the year in question.  Then we have our main open enrollment for all other plans where the begin date is 1/1 of the new year and 12/31/9999 for the endda.  I then run the HRBEN00ADJRSN twice for the population:  once for the flex enrollment, and then again for the main open enrollment adjustment reason.
    DP

  • ESS Benefits error - No entry for period parameter 04/payroll year/payroll

    Hi,
    When I click on Annual Enrollment link under ESS Benefits section, I get an Error from Standard WebDynro Application - No entry for period parameter 04/payroll year/payroll period. What config could be missing in the R/3 ?
    Any suggestions?
    Cheers,
    Murali.

    Hi,
    Employee assigned Payroll area (refere to  IT0001- Org Assignment) not moved into prd Payperiods. And as per you Payroll area assigned to "00", Ask your payroll consultant assign payroll area period parameters and generate periods through T.code "OG00"
    Issue is with T549Q..

  • ESS benefits and payment not displaying after support pack update

    Hi All,
    After the latest HR support pack update ESS benefits and payment not displaying
    SAP ECC 604 EPH5
    SAP_ABA 702
    SAP Kernel :  720_EXT_REL
    Kernel Patch number : 439
    Netweaver portal version - 7.30
    please help
    Regards
    Rahul

    Hi Siddharth & Jwala,
    the issue got fixed, by changing the order of Payment above the Benefits
    1. i made some options to be disabled & enabled in both benefits and payment
    2. Then in the portal i could see the benefits and payment
    3. inside the benefits & payment i was able to see two option 1 is for benefits & other is for payment
    4. we only wanted payment functionality to be displaying
    5. so i tried to hide the benefits then noting was getting displayed in the portal
    6. finally i changed the order of the payment just above the benefits
    then then i was able to see the benefits and payment inside that i was able to see the payment where i was able to see the payslip
    i am not sure what i have done but i is working but please let me know what the problem was actually
    Regards
    Rahul

  • Different behavior of movewindow with different windows is (xp or windows 7)

    we have a windows wpf stand alone application which must be integrated within a windows form 2.0 stand alone application. given to the particular implementation of the windows form application we decided to use a light integration trying to change the parent
    handle of the wpf main window setting  as parent the handle of a windows of the windows form 2.0 application.
    in order to reposition the wpf windows on top of the parent windows form window, we have a thread which keeps doing two operations: (1) invoke getwindowsrect on the parent windows form windows to get the parent absolute position and (2) invoke movewindow
    on the wpf main window handle to reposition the window.
    when we move the windows form window, the wpf windows follows the parent remaining in the correct position. we tested this solution with windows xp, windows 7, windows 8 in our office. when we went to the customer to complete the installation, both on a
    windows xp and on a windows 7 the behavior was different. the size of the wpf window was much bigger than the size of the windows form parent window. back in office we found the same strange behavior in windows xp wirtual machine. in order to fix the problem
    (at least partially) we had to change the operation sequence within our code as follows in the monitoring thread: (0) get parent windows position with getwindowrect (1) set the parent of the wpf main window to (null) 0 invoking setparent, (2) invoke the movewindow,
    (3) re set the parent handler of the wpf main window to the handler of the windows form window.
    with last solution it works but clearly there are more flikering when the window is moving or resizing respect to initial implementation.
    any idea about this different behavior of movewindow function? any suggestion?
    thanks
    Paolo

    Hi Paolo,
    You'll need to post it in the dedicated WPF or Windows Forms forum for more efficient responses, where you can contact the experts.
    http://social.msdn.microsoft.com/Forums/en-US/home?forum=wpf WPF forum
    http://social.msdn.microsoft.com/Forums/windows/en-US/home?forum=winforms  Windows Forms forum
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Calling a ESS WDJ COmponent with different Client no

    Hi,
    my task is to make ESS available on a different Client (100) instead of 001.
    i was reading about the "Mapping Logical Systems" using the parameter sap-wd-arfc-useSys :
    http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/content.htm
    I did the following :
    1. Create a new JCODestination :
    SAP_R3_HumanResources_MetaDataHNL and SAP_R3_HumanResourcesHNL with the new client.
    2. Call the URL
    http://<portal>:<port>/webdynpro/dispatcher/sap.com/ess~lea/com.sap.xss.hr.lea.appl.LeaveRequest?sap-wd-arfc-
    useSys=SAP_R3_HumanResources:HNL&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:HNL
    Result : i get a 500 internal Server error after the login for this client.
    Test 2: The same with the default JCO Destinations : same error
    Test 3: The same without the additional parameter : working
    The JCO Destination is only SAP_R3_HumanResources when i looked it up the Content Admin Area for Web Dynpro.
    What is the point i am missing ? Has someone done it successfully to connect to 2 systems per sap-wd-arfc-useSys ?
    Regards,
    Kai

    Hi Arun,
    the JCODestination Tests (Metadata) are successful.
    The Assignment for ess~lea is only for :
    SAP_R3_HumanResources
    SAP_R3_HumanResources_MetaData
    It is a standard ESS iview. How and why should i assign additional JCODestinations ?
    I overweite it per parameter sap-wd-arfc-useSys
    Regards,
    Kai

  • Different behavior with decimal data on same version of CF

    I have a linux/apache/mysql/CF MX 7 Enterprise server. I insert decimal data using the cfqueryparam that looks like
    <cfqueryparam value="#BudgetSet.BUD_SET_DETAIL_COST_PER#" CFSQLType="CF_SQL_DECIMAL">.
    No problems the decimal data does not get rounded, 123.45 inserts as 123.45.
    I'm building applications for my neighborhood association, so I'm having godaddy.com host the web site with CF and MySQL.
    Like a good developer, I took code from my CF server, moved some of the more useful programs to the godaddy.com, set up the database and started testing some apps. Now any decimal data inserted gets rounded using the same cfqueryparam syntax from my CF server (like above). The decimal data on the godaaddy.com inserts as 123.00, when I'm trying to insert 123.45, of course if I insert 123.99 I get 124.00, rounding. So I called godaddy.com and of course I get the standard technical answer "its your code". So off to testing I go. Only to determine, by not using the cfqueryparam, I could stop the rounding, more testing I determined that I need to use
    <cfqueryparam value="#BudgetSet.BUD_SET_DETAIL_COST_PER#" CFSQLType="CF_SQL_MONEY"> or
    <cfqueryparam value="#BudgetSet.BUD_SET_DETAIL_COST_PER#" CFSQLType="CF_SQL_DECIMAL" scale="2">. The version of CF @ godaddy.com is also MX 7 Enterprise. Finally the question, what in configuration could cause such different behavior ?
    Thanks for reading my short novel.

    The database drivers determine how the cfqueryparam values are
    interpreted (behind the scenes ColdFusion generates a prepared
    statement using the driver interface and sets the values using
    standard JDBC calls). Unfortunately, like you found out, not all
    drivers are created equal and have slightly different behavior or
    defaults.
    I would check and compare the driver versions.
    Mack

Maybe you are looking for