No adjustment Reason for Flexbens Enrolment-UK in portal

Dear all,
I am getting the "No correct adjustment reason specified" error for the "FlexBens: Open Enrollment" link on the Portal.
I specified enrollment reasons (infotype 378) for the employee assigned to the portal user
I am working for UK Benefits in R/3 it is working fine and all the adjustment reasons/Events are coming but in EP under Flex bens Enrollment I am getting the above error.
here I want to enrol the plans against the adjustment reasons.
So pl. suggest me what I can do and is there any config settings require for this it is very urgent.
Hong: can you pl. helpme out.
Regards,
Sushma

Hi Barin,
Pl find the detailed error through Portal for the same.
<b>No correct adjustment reason specified</b>
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)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
     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:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     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:1244)
     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:319)
     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)

Similar Messages

Reason for disabling browswer caching in Portal

Can someone tell me the technical reason for disabling browswer caching in Portal.
This is a big problem for our client who have central rollout of software and the corporate decision is to allow automatic browswer caching in IE 5.0.1.
Why does the Portal framework not generate the cache-control header directive to prevent the browser from using its caching facility? See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1 for more info on this.
Cheers,
John

Can someone tell me the technical reason for disabling browswer caching in Portal.
This is a big problem for our client who have central rollout of software and the corporate decision is to allow automatic browswer caching in IE 5.0.1.
Why does the Portal framework not generate the cache-control header directive to prevent the browser from using its caching facility? See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1 for more info on this.
Cheers,
John

T-code HRBEN0005 calling different form for open enrollment

Hi,
I have to create two different forms for different adjustment reasons for open enrollment(t-code HRBEN0005).
But in the config table T74HL we can call only one form so I am looking for an enhancement where i can pass the form name according to the adjustment reason.
I am not able to find any such enhancement, please let me know if anyone has done this scenario.
Regards,
Manu

Hi,
As I understand, you have a custom edit form, you would like to click a button and jump to another edit form. Correct me if there is any misunderstanding.
If that is the case, you could create different view for a list edit form. Then use a button to switch among views to show different view. For more information:
http://office.microsoft.com/en-in/infopath-help/add-delete-and-switch-views-pages-in-a-form-HA101732801.aspx
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Enrollment Form Not Visible for Adjustment Reasons

Hi Experts,
I am having an issue with the Benefits enrollment not being displayed in the ESS portals. We are using an adjustment reason based open enrollment . The link is visible if give the event name as BENP_EVENT = OPEN which points to the form with standard open enrollment form listing all plans but we want to use 'OPN' (custom reason) instead of 'OPEN'. If i change the event to BEN_EVENT= OPN, it is displaying the link but not unable to read the employee and throwing an error saying, "infotype IT0171 doesnot exist for 00000'. Listed below is my configuration.Your help is much appreciated.
Adjustment Reason:
Form Setup:
Launchpad Link:
Launchpad Config:
Ess Page:
Thanks,
Vishnu

Hi Shankar,
Thanks!! for the reply. The application is in active mode only. The system is only taking the event name(BENP_EVENT = OPEN). I have to create another adjustment reason with 'OPEN' name just for form purpose and keeping my 'OPN' as is for my enrollment purpose. The problem is with 'OPEN' it lists out all the plans , even the ones that we don't want to show.
Thanks,
Vishnu

FlexBens:Open Enrollment/Print form- No correct adjustment reason specified

Hi Experts,
Need help on Flexible benefits of UK.
I have done all the necessary configuration, but somehow im facing the "No correct adjustment reason specified" on the ESS pages of FlexBens:Open Enrollment & FlexBens:Print Form Screen. However, im able to view Participation screen.
Also, i have maintained 171 and 378 aswell. but still this error comes. I have used Tcode HRFBN0001 for enroll ment from R/3. Its working fine here. Also I looked in functional module HR_BEN_ESS_RFC_ENRO_REASONS. Data is shown properly.
I doubt if this is an authorization issue. If anyone of you know what should be the portal Role to access Flexible Benefits ok UK. or if you think the reason is something else, the please share with me your thoughts.
Regards,
Pranitha

Hello Bhargava,
Please assign/ Configure General Benefits Information (Infotype 0171) for PERNER.
Go thru this link it will help you
[http://help.sap.com/erp2005_ehp_03/helpdata/EN/7e/8a62e6545711d1891c0000e8322f96/content.htm]
Thankyou,
Regards
Vijai

Open Enrollment error for US - No correct adjustment reason specified

Hi,
We are getting this error "Open Enrollment error for US - No correct adjustment reason specified". Please help if you know the resolution to this.
Regards,
Anand Jalan

I have found the solution for this.
Maintain the Open enrollment period dates in IMG->Personnel administartion -> Benefits ->Flexible administration->Define Administrative Parameters

ESS Benefit Enrollment - No correct adjustment reasons specified

We are in ECC 60. When testing ESS benefit open enrollment (under Content Admin - Portal Content - Content Provided by SAP - End user content - ESS - Iviews - Benefit and Payment - then either test on 'Enrollment' or 'Flex Bens Enrollment)', we keep getting error 'No Correct adjustment reasons specified' .
I already configured 'Benefit Area Admin Paramenter' to have open enrollment period to be active for month of April (for testing), and also assigned proper role in 'URL of PCD Page' for resource key 'EMPLOYEE_GENERICENROLLMENT_SERVICE05', and yet still get the error message. Searching SDN for this issue, I see that some people also had similar issues before, but there doesn't seem to be a concrete / clear solution. Appreciate if someone can shed some light on what I'm still mising .
Thanks.

Hi Ted,
Not sure if this would help.
You can try the below thread..... It also has reference to an OSS Note.
[Adjustment Reason;
Good Luck !!!
Kumarpal Jain.

Change BEGDA when enrolling in adjustment reason plans from ESS/HRBEN0001

Hi Experts, ,
Please provide your inputs/let me know if any BADI or User Exit exists, for acheiving following requirtement in ESS -
Following a life event change or at the time of hire, eligible employees log on to ESS to adjust available benefits plans. The requiremnet is to change the effective dates (E.g. if enrolling in health plan - P0167-BEGDA) of the plans during enrollment. The idea is to have a custom table created which would hold Adjustment reason, Benefit plan and effective date calculation rule (1st day of next month, last day of month etc.. ) and derive effective date from this Ztable when employee enrolls in any plan from ESS/HRBEN001.
Any inputs on acheiving this requirement would be of great help.

Thanks for taking ur time and relplying to this question...
I have seen the class and the function module being called in this class .. BEGDA is an importing parameter and hence any change done to it will not be captured .. and moreover I guess this will not trigger from HRBEN0001 ..
any comments ?

Control ESS Open Enrollment to use adjustment reason instead of open offer

Hi :
We would like to control open benefit enrollment with adjustment reason instead of standard open offer. Plans are configured for adjustment reason 'OPEN', IT0378 created for the ee with this reason, and open enrollment period is configured . I use
'EMPLOYEE_OPEN_ENROLLMENT_SERVICE05' as my resource.
However, it keeps bringing up plans from standard open offer as versus to plan configured for adjustment reason 'OPEN'. Debugging through, I could see that it passes enrollment type 'O' (for open) instead of 'E' (for event) in 'SELECTED_ENROLL_REASON' to function 'HR_BEN_ESS_RFC_INIT_SELECTION' which in turn would cause it to select plans from standard open period instead of plans configured for 'OPEN' adjustment reason.
What could I do to force ESS to use 'E' instead of 'O' ? I try to avoid having to create an enhancement point for the above fucntion to alter the field.
Thanks.

Double-post - closed

Adjustment Reason based Enrollment Issue

My Open Enrollment ESS piece is working fine. The issue is with the Adjustment reason based ones.
Basically our Open Enrollment service is enabled via regular Open Enrollment object in Benefits Adminsitration under Personnel Management ( and this works fine when I use the OPEN_ENROLLMENT service since it picks up the OPEN event).
We also have another plan which is given to employees via 378 and so is based on an Adjustment Reason.
When I try to enable the EMPLOYEE_GENERICENROLLMENT_SERVICE service, I get the first page which lists all the available plans for my user. But when I try to click on a particular plan, it takes me to a blank page.
I have set the PCD URL for the Resource to the corresponding page and that is why I think the first page shows up - this is all good but I can't get to the actual enrollment from there. Any ideas?
Thanks,
BR

Now, I am confused....
You say that you are pointing your resource for OE to the area page of Benefits - and it is working fine.
I cannot verify it since I am on ECC 6.0 and using all the services ending in 05.
This is what I see in my system:
EMPLOYEE_OPENENROLLMENT_SERVICE
ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.ess.employee/com.sap.pct.ess.roles/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.area_benefits_payment/com.sap.pct.ess.serv_benefits_payment
EMPLOYEE_GENERICENROLLMENT_SERVICE
ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.ess.employee/com.sap.pct.ess.roles/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.area_benefits_payment/com.sap.pct.ess.serv_benefits_payment
EMPLOYEE_BENEFITPAY_PAG
ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.ess.employee/com.sap.pct.ess.roles/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.area_benefits_payment/com.sap.pct.ess.area_benefits_payment
The first two resources above are pointing to a Service page. (Page you see as "Enrollment" in the standard role)
The third one points to the Area Page (Page you see as "Benefits and Payment" in the standard role)
You should be using the PCD path of the Service page in your resources for OPEN enrollment and Generic Enrollment
Anyway, to just quickly test your new Generic Enrollment service, you can edit the existing resource for OE and enter the URL parameter and see if it works...
Try these things and let me know how it goes ...
- Shanti

NO CORRECT ADJUSTMENT REASONS.

Hello All,
When we access the Benifits enrollment under ESS we are getting a message that "No Correct Adjustment Reason Specified". The ITS version of this IView is working fine, but for the WebDynpro I am getting the above message. Can somebody guide me what tasks I need to perform to get this working.
Thanks a lot in advance for your response!
Chakri.

Did you check with SAP via OSS? could be WebDynpro related as can be seen from this <a href="https://forums.sdn.sap.com/click.jspa?searchID=762563&messageID=2912240">Thread</a>.
~Suresh

SAP HCM Benefits: No correct adjustment reason specified

Dear All,
We are implementing Benefits through portal.I do have error whicle enrolling a pernr even though entires are maintained in IT0171 & ITo378.
The corresponding FM "hr_ben_ess_rfc_enro_reasons" is called and executed without having any entries under the internal table "ERROR_TABLE". After the FM is executed, the portal dump is displayed which is shown below.
Kindly help me trace from where we get this error message.
"No correct adjustment reason specified"
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.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.isConsistent(VcBenefitsEnrollmentReasons.java:218)
     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasons.isConsistent(InternalVcBenefitsEnrollmentReasons.java:190)
     at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasonsInterface.isConsistent(VcBenefitsEnrollmentReasonsInterface.java:173)
     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface.isConsistent(InternalVcBenefitsEnrollmentReasonsInterface.java:152)
     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface$External.isConsistent(InternalVcBenefitsEnrollmentReasonsInterface.java:228)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:508)
     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
Thanks in Advance
Nazia

Dear Nazia,
This error looks like configuration mapping of iViews. Please check with the portal team, whether the correct iView is configured for the country specific setting. In general, for any particular pernr if the error comes, Please check whether the particular pernr as any Unicode issue (like junk character).
Thanks,
Ganesh R K

Is adjusting permissions for LightRoom based archive management worthwhile?

I'm trying to set up an archive that is managed through a LightRoom Catalog. I was wondering if anyone has done this before and adjusted the permissions of their files to read only to ensure that LightRoom Catalog metadata changes do not alter or get saved to files.
I plan to have the archive set up in 3 locations with copies of the LightRoom Catalog. I will need to be able to add keywords and collections to a catalog at 2 of the locations. I am interested in using permissions to ensure that the catalog is the only file that needs to travel between the locations. I don't want to get into a situation in which altering the LightRoom Catalog might alter files and necessitate that I either save new metadata to files with each keyword/collection addition or that I regularly synchronize the entire archive to ensure all 3 copies of the archive are mirrors of one another.
I have three serious concerns about the longterm viability of managing file permissions:
1. I worry that it will be difficult to manage the user/s who have the privileges to manage these permissions and that it will be difficult to do so in different locations and on different computers
2. I worry about whether permissions management might introduce some form of file corruption
3. I worry about the time involved in altering an entire archives worth of permissions to read only and the time involved in reversing this every time I want to unarchive content for new projects
I have also posted this question to Luminous Landscape here: Adjusting Permissions for LightRoom Catalog Based Archive Managment. Worthwhile?

... and adjusted the permissions of their files to read only to ensure that LightRoom Catalog metadata changes do not alter or get saved to files.
By default, Lightroom does not write anything to your photo files. Of course, there's no way to prevent a user from changing this default behavior and writing information to the files. I suppose making the directories read-only helps, but people could still change that. If the directories are on a server, then only the server admin could change the permissions.
2. I worry about whether permissions management might introduce some form of file corruption
I never heard of such a thing, but this is an operating system issue, not a Lightroom issue.
I worry about the time involved in altering an entire archives worth of permissions to read only and the time involved in reversing this every time I want to unarchive content for new projects
I don't think you understand how Lightroom works. There would be no need to reverse anything to "unarchive" the content — although in my opinion, the idea of "archiving" content in the first place doesn't feel right ... if the photos are imported into Lightroom at one time, leave them in Lightroom, don't go through an archive process removing the photos from Lightroom followed by unarchive process, that is something that is ineffective and causes numerous problems with non-expert users. When you import photos into Lightroom, the photos still remain on your hard disk somewhere, Lightroom does not actually keep a copy of the photo. Lightroom keeps pointers to the photo's locations and stores any metadata and edits. Removing a photo from Lightroom (archiving) is the equivalent of deleting the metadata and edits, and I cannot see a reason to do that.
So, bottom line, to answer your title question, "Is adjusting permissions for Lightroom based archive management worthwhile?" — without further discussion of your setup and goals, I see no reason to even spend your time on this, unless you are the server admin of the location where the photos are stored, in which case then the answer is go right ahead and make them read-only.

:FRM-30085: Unable to adjust form for output.

I have built a form on my laptop running Oracle Developer Suite 10g (10.1.2.0.2) and runs fine. I started having the message below
:FRM-30085: Unable to adjust form for output.
when I tried to open this form on another version of Forms running Oracle Developer Suite10g (9.0.4.2.0) on another computer.
Could this be the reason - non-backward compatibility.
If this is the reason, Is there a way to around it.
Many thanks
cube60

Yes, you are correct - you cannot create a form in 10.1.2 then try to run it in 9.0.x. There is no way to avoid this.
In order to go from an older version to a newer version, you must recompile the source code (FMB, MMB, PLL) in the version where you expect to run it. You cannot simply take an FMX file which was created in 9.0.4 and expect it to run in 10.1.2. This would fail. New executables would need to be created using the 10.1.2 compiler.

Reason for Change LOV

Hi
Anyone know where the LOV is configured for the Reason for Change when an administrator updates an enrollment status? I'm sure I've done this before, but have a complete blank on it now!
Regards
Tim

As they say in the Simpsons "Dooh!!". Of course, thanks very much.
Regards
Tim

No adjustment Reason for Flexbens Enrolment-UK in portal

Similar Messages

Maybe you are looking for