Assigning a value to a Read-only Segment of DFF

Hi Friends,
I have a read-only segment of DFF. I want to assign a value based on the value entered in other segments to this read-only segment. There are a couple of issues I am facing. I am not able to get a handle to this read-only segment and also how can we assign the value to this segment..
Any ideas please
Thanks in advance

Similar Messages

Can you force a value into a read-only numeric data member?

I have code that will force a value into a numeric data member. Unfortunately the numeric data member in question is read-only. Can you force a value into a read-only numeric data member?

Andre,
I think you should get together with the other engineers there at NI. I spoke to one on the phone yesterday and he told me that the read-only aspect relates to writing between the database and PLC. I'm trying to write to the database and he told me that I could do it.

Value of a read only check box is always null

Hi,
I have a read-only check box in my form which fetches its values using Y or N value from table. If the value fetched from the table is 'Y' then check box is checked.
But when I tried to assign the value of this check box to some other item it is always showing null. When I made the check box editable then it started showing the value.
I appreciate if some one can share their thoughts if dealt with similar kind of issue.
Thanks in advance.
-Raj.

Read-only items often have the "disabled" attribute which prevents them from being POSTed so you can't pass their values from the browser to the application. Since you get the value from the database, why not simply fetch that value again after the page is submitted using a computation to set the other item's value?
Scott

Read-only radio group losing value on validation error

It took quite a while to track this down, but I think I've got it narrowed down properly. I have an APEX form for updating a record in a databse table with a radio group which is conditionally read-only. If that radio group has a value AND is read-only, when the form is submitted and hits a validation error, the value of the radio group is lost.
For example, the radio group SUBMITTED_FOR_APPROVAL is set to Y and is read-only for a given user. That user then changes something else on the form and submits it. However, the form now hits a validation error for some field. When the form reloads with the validation error displayed, all the fields are restored except the read-only radio group which is now blank. If a select list is used with the identical read-only condition, it works fine. Likewise, if a radio group is used, but the read-only condition is removed, it works fine. It is only when it is a radio group and it is read-only, that the value does not appear to be submitted to the session with all the form values whent he form is submitted.
Is this a bug or am I simply missing something?
Apex 3.1.2
Rgds/Mark M.

It's using a shared component LOV cleverly called LOV_YN which consists of a static LOV with
1 Display=Yes, Return=Y
2 Display=No, Return=N
The settings in the LOV section on the item iteself:
Named LOV: LOV_YN
Display Extra values: No Dynamic translation: Not translated
Number of columns: 2 Display null: No
Null display value is blank as is null return value
Item was setup as a radio group and was only converted over to a select list to work around this issue. Let me know what else you need and thanks again.
Rgds/Mark M.

How to get the value of a parameter/field in a ADF Read-Only Form

Hi,
My requirement is as follows. Could anyone shed some light on this issue.
I am showing the records from db table using ADF Read-Only Form ( which uses ViewObject created for the table). Now I want to capture(get) the value of a field in this form and then have to invoke an action based on the value in this field. I mean to say the next page depends the value of a field in this form.
Please suggest how can I achieve this functionality?
Thanks in advance.
~Sivaji

That's indeed what Sivaji needs.
In the page definition you can add a value to the parameters of a certain method. Like RJundi mentioned, point to the attribute of the current row.
Example:
The value of the read only textfield will be something like this:
#{bindings.EmployeeName.inputValue}points to an attribute value in the pageDef of the page:
    <attributeValues id="EmployeeName" IterBinding="AllEmployees">
      <AttrNames>
        <Item Value="EmployeeName"/>
      </AttrNames>
    </attributeValues>The attribute value has also an iterator binding defined in the page def:
    <iterator id="AllEmployees" RangeSize="10"
              Binds="AllEmployees" DataControl="MyService"/>If you want to 'pass' the attribute of the current row to the service, you can create a methodaction (eg: public void printEmpName(String name)) in the page def or you can drop the method from the datacontrol on to the page. After dropping the method, a screen will appear asking to fill in a value for the parameter ('name' in this example). Fill in '#{bindings.EmployeeName.inputValue}' if you want to pass the EmployeeName of the current row.
Hope it helps,
Koen Verhulst

Upload a value in read-only field using Webservices or Workflow

Can you please let me know if is feasible to upload a value into a read-only field using webservices or workflow
If so, can you please provide an example?
Thanks

Using WS, you cant update the field value, if it is set as "Read-Only" @ the object - Field definition level, but you can update that using WS if it is set as "Read-Only" @ the layout level. Same applicable to Workflows too
-- Venky CRMIT

Read-only radiogroup with default doesn't save state in 2.0

Hi,
I upgraded to HTMLDB 2.0 and noticed a change in behavior. Namely, when I have a read-only radio group with a default value and a not-null validation, the validation claims fails although a radio button is selected from the disabled radio group.
Here's a small app I generated to demonstrate the issue:
http://htmldb.oracle.com/pls/otn/f?p=34464
Go there and try to create a new EMP.
The only things added after the generation are:
1. Not-null validations on several of the fields
2. Changed MGR to a "Select List"
3. Changed DEPTNO to a radio group with these properties:
a) default value type: static; default value: 20
b) read-only when: P2_EMPNO is Null
This used to work fine in 1.6 - namely, the default value got it to the session state and consequently the validation succeeded and the new record was created with the default value.
It also works fine if the Radio Group is not read-only.
I was able to fix the problem by adding a calculation to the P2_DEPTNO item to set the default value there. This of course does not show the default on the form for the new record, so I had to keep the default on the item level as well - which is a potential source of bugs when those two defaults somehow get different values (e.g., when I change only one of them and forget about the other) - the user will see one thing displayed while another will be saved. So any solutions involving keeping the default value on only one place AND visible to the end user when creating new records are welcome.
I haven't had time yet to test with other item types - maybe next week...
Have a nice weekend!
Flado

Scott,
Yes, in 1.6 this used to work fine - the radiogroup was displayed as disabled, and the default value was selected, and the not-null validation succeeded, and all I did was set the default value of the radiogroup. I have no 1.6 environment anymore to test it, but I'm sure it was working, because after I upgraded to 2.0, it stopped working and I got a bug report from a user very, very quickly :-(.
By "adding a calculation to the P2_DEPTNO item" I mean "adding a computation of the P2_DEPTNO item to the page". Sorry about me being lazy here. It was (still is, in my production application) a conditional after-submit computation (if <primary key item> is null, set <radiogroup item> to <default value>)
Thank you for the suggestion. I implemented it in the demo app. What I did was:
1. remove the default value from P2_DEPTNO
2. Add an unconditional after-header computation that assigns P2_DEPTNO with the static value 20
I am able to create new EMPs now, but nothing is selected in the disabled radiogroup on the create page, although the value 20 is saved in the session state before the items are rendered, according to the debug info (you can try it out and see).
To recap, I still need to keep the default value in two places: default of the radiogroup (to get it displayed on the create form), and in a computation (to set the session state).
Cheers,
Flado

OVS on read-only input field

OVS will not allow me to change the value of a read-only input field. If the input field is set to read-only, the OVS selection table does not display an 'OK' button, only close.
Value cannot be copied (field is not editable)
I do not want the field to be editable on the screen, but only allow input via the selected row in the OVS. Any suggestions?
Edited by: Bob DeNuto on Jul 31, 2008 1:22 AM

Using Dictionary Search Help and OVS in this case will disable the Copy button and you don't have any control.
Use Freely Programmed Value Help, this will solve your problem
https://wiki.sdn.sap.com/wiki/display/WDABAP/Freelyprogrammedinput+help
how to provide f4 help to the read only input field
Abhi

Coulmn should be read only

Hi every one,
I want to set field values to be read only
I have chosen responsibility “Employee Self-Service” and then function “Personal Information” under that.
Under section “Phone Numbers” I have , click on Update
By default Number column is always editable.
here I have to implement ,
If I select Type as “Home Fax”, Number column should be read-only.
How can I do this?
Edited by: Want Java on Nov 15, 2010 3:18 AM

Hi,
Below steps for Vo extension:
---Copy the package in which that seeded vo exists to your local machine where you have jdeveloper installed.
---Create a new OA Workspace and project.
---Create your Custom package and in that create new View Object with new Query including your new attribute.
Ensure in the extends you select the Seeded VO.
---While creating VO select in extends property standard vo and create tr attribute.
---Double click on your jpx and go to substitution and select seeded VO in available list and Custom VO in Substitute List Click on Add.
---FTP the new package you created to $JAVA_TOP
---Run jpxImport utility for your substitution to take place.
---Bounce apache.
---Through personalisation set read only for Number as i given in SPEL.${oa.seacrhVo1.readonlytr}.
---While you will attach VO to that field ensure View Instance name is your Seeded View Instance name while view Attribute will be your new Attribute added.
Refer:
http://oracle-hack.blogspot.com/2008/03/how-to-extend-view-object-in-oa.html
Regards
Meher Irk
Edited by: Meher Irk on Nov 15, 2010 6:39 PM

Lifecycle issue with table binding + read-only attributes: ADF BUG

Hello all,
I have found what I believe to be an easily reproducible bug in ADF that reproduces in 10.1.3.x, but not in 11g (at least not in drop 6). The best way to describe the bug would be to walk through a simple set of steps to reproduce the bug:
1). Create a new application (ADF BC + ADF Faces).
2). In the model project, create a new Entity Object from the Employee table in the default HR schema. Allow JDev to create an updatable view object and an AM as well.
3). Put a validation rule on the first name attribute of the EO (can be anything, really - I made mine so that the first name cannot be "foo").
4). Test everything using the BC tester if you like.
5). In the UI project, create a new JSPX page.
6). Drag the updatable VO on to your page as an updatable af:table.
7). Put an af:commandButton on the page. Bind its Action or ActionListener to a method in a new backing bean. Put some simple code (I used System.out.println) in the backing bean method.
8). Run the jspx page.
9). Put some invalid data in (e.g. "foo" in the first name field) and click the af:commandButton. Verify that you get an error message and that the Action/ActionListener method DOES NOT fire. So far, so good.
10). Now, to demonstrate the problem. First, look at the page definition for the jspx file. Identify the first attribute that is mentioned (in my case, it was the employee id).
11). Go to the updatable view object and make the attribute from #10 read-only or updatable when new only.
12. Now, repeat step 9 - you should see the error message AND also see that the Action/ActionListener method was executed. You will also see in the messages window that ADF attempted to set the value of the read-only attribute, and thus got a ReadOnlyAttrException.
This issue only happens if the first attribute mentioned in the table binding is read-only. A workaround would simply be to re-order the attributes in the table binding of the pagedef so that the first attribute isn't read-only.
Don't ask how I figured this out ;)
Best,
John

Hi Frank,
Yes, I simply scripted it out this way to contrast the behaviour if the first attribute was read-only vs not read-only. I found the issue on a page in our app that was simply drag-and-drop the VO from the data control on the page.
It's quite annoying, because our particular use case that hit this error is a "save" button on the page. If the commit operation doesn't return any errors (and it doesn't in this use case!), we add a JSF message saying "save successful" - then the attribute errors are further added later in the page lifecycle, so we get 3 messages: "Save successful" and "Fix this error" and "Tried to set read-only attribute" - quite confusing to the end-user when the only message they should see is "fix this error."
At any rate, the fix is to simply re-order the attributes in the page definition - that doesn't affect the UI at all, other than to fix this issue.
John

Key flexfield - protecting one of the segment as NON-UPDATABLE/ READ-ONLY

Key Flexfield setup for "People Group Flexfield" consists of seeg1,seg2,seg3,seg4.
We would like to make Seg1 of this flexfield "READ ONLY" / "DISPLAY ONLY" / "Non-Updatable".
Please advise possible way of making this functionality.
I have tried, following but no luck :
1) Limitations of Forms Personalization [ID 420518.1]
Forms Personalization is not possible for any key flexfield structure or segments.
This is a limitation of Forms Personalization on Flexfield. There was an enhancement request Bug 5506506 - "PERSONALIZE FLEXFIELDS BY USING FORMS PERSONALIZATION" but it was rejected the enhancement request as this is not feasible. A Flexfield is a single field in a form but then when you click into it and it opens up the flexfields window, the multiple fields you see is actually a user exit with multi segment values, not form fields. No Form Personalization events are passed to flexfield windows (user exits). No Form Personalization events are passed to segments inside the flexfield window (user exit).
2) Key Flexfield Security Rules Enabled
Defining security rules on any segment in key flexfield makes all segments as read only. Per Oracle Document:"Defining security rule on key flexfield combination on one or more segments allows all segments to be not updatable"

In SSHR, I believe it is possible although I have not done it before, I have spoken to people who have.
You need to have access to jDeveloper and be able to open up the SSHR page in question. Find the internal ID of the flex item within the SSHR page in question.
Then you create a new item in personalization and set that new item to have the same ID as you retrieved from jDeveloper. Make that item read only and configured the 'default' flex to not show the segment in question.
That is basically the way this can be achieved but it is not straightforward and requires a cursory understanding of OAF.
I do not know if it is possible to do this in the PUI. Would be interested to know requirement behind essentially showing a static read only field in a professional form - can the admins not be trusted to leave it alone? One workaround would be coding a user hook or custom library to error if that field is updated. Not read only but would stop those pesky Administrators meddling with it!

ME21N, Account Assignment, to set G/L Accout field 'read only

Hi,
I am creating PO with reference to Purchase Requisition (using T-Code ME21N). The fields 'Cost Centre' and 'G/L Account' under Account Assignment Tab are needed to be rendered 'Read only'.
The 'Cost Centre' Field has been made Read Only using User Exit. I am not able to do the same for 'G/L Account' field. Please suggest a possible way to do the same. Field Exit is not working and i have experimented with lots of BADIs, but to no avail.
Thanks,
Ranjan

Hi Venu,
I have done as you have told. This is working fine while creating
PO with reference to Purchase Requisition, but the problem arises when we try to create PO by simply putting Account Assignment Category 'K' along with other relevant data.
The G/L Account field is in display mode, obviouly due to configuration i have done, and thus we are not able to put value in it. It is interesting to note that SAP is itself determining and displaying G/L account in this case.We are checking if this is the case with all test cases. If so then our problem can be considered solved.
Thanks,
Ranjan

Making a JSP Form read only based on the form value present in DB

I need suggestions/examples as i am newbie into java stream.
I have two JSP pages 'Add Page' and 'Edit Page' .
Add Page -> In add Page,I have many text boxes,select drop-downs options. In one select drop-down I have values as Locked and open .I can save this page contents in DB by entering those form values.
Edit Page -> In eidtPage,once saved in DB, based on 'select drop-down- Locked and open' If it is locked i have to make all the fields (text boxes and select drop downs) as read only and if it is open i have to make it editable.
I am taking all the values from DB,setting to 'form bean' and then setting up the values in session and forwarding it to JSP page to populate there .I am using beehive net UI tages in JSP. Please help me out.

Not sure I'm following what you want, but this might help:
In your select tag, put something like an 'onchange' event that calls a javascript function. In the javascript function it you add code to enable or disable your other fields based on the item selected from the drop down box.
To determine what item was selected in a select tag, you write something like the following. I'm not sure of the exact syntax. You can look it up in a javascript book:
var optionSelected = document.forms[0].selectTagName.options[document.forms[0].selectTagName.selectedIndex].value;
To enable or disable a textfield, search for this in google:
'jquery disable input'

How to make an assignment block in an overview page read only

Hi Experts,
We have the following requirement:
In Campaign overview page we need to make the Partner and Product assignment block read only.
Can this be achieved through coding or through configuration?
Please give detail steps for the appropriate approach.
Thanks in advance.
Regards,
Sayan

Hi Leon,
Is there any authorization group which can be customized to take care of this situation?
For Product Assignment block in DO_PREPARE_OUTPUT method of class CL_CPGOE_AB_OVELPRODUCTS_IMPL (Component : CPGOE_ABLOCKS :: View : OVELProducts) it is checking some authority. Any pointers where those authorities are maintained will be helpful.
Creating a new configuration is not helping as the views are 'Table View'.
We are looking for an approach which will avoid coding or involve minimum coding.
Regards,
Sayan

How to display the "display values" in READ Only mode for a SHUTTLE

Hi,
I have a form item of type *'Shuttle'* and using the following LOV.
   select DEPTNAME d, DEPTNO r
    from DEPTIn normal mode..it displays the department name and internally store the Deptno..
Now I converted this item to Read Only mode using Read Only Condition Type
the problem is as soon as it becomes read only...it displays the deptno....not the department name
            Department-   10:20:30How can I display the "display values" i.e the actual department name in read only mode..
            Department-   Department1:Department2:Department3Thanks,
Deepak

Hi,
It seems feature. Shuttle is span tag when it is read only.
Work around could be that
you compute display as text item with LOV display value according shuttle session state and show shuttle and this item conditionally depend case
Br, JAri

Assigning a value to a Read-only Segment of DFF

Similar Messages

Maybe you are looking for