Conditionally coloured fields

Hi
I have a client who has asked whether fillable fields on an Acrobat form can be colored until they are filled in. So for example the unfilled form would initially have all the fields fill colour set to red. Then, as each field has information entered into it, the fill colour would change to none.
As well as this, they have a requirement to have all the fields reset to red when they reset the form (ideally combined with a button that I already have that triggers the built in reset form function).
From what I have gleaned on these forums and elsewhere, it looks like this is possible, but I haven't managed to work out exactly how.
Any pointers would be much appreciated.
Thanks.

Yes. If you know the RGB or CMYK values you can use color arrays instead of one of the predefined colors. For example:
event.target.fillColor = event.value ? color.white : ["RGB", 218/255, 25/255, 125/255];
event.target.fillColor = event.value ? color.white : ["CMYK", 0, 0.794, , 0.427, 0.145];

Similar Messages

SD-Pricing Conditions: Allowed Fields

Hi Guys
basic functions > pricing> condition table> conditions:allowed fields > new fields
when I try to add a new field: VOLEH ( selected using F4), system throwing following warning message: "Choose the key from the allowed namespace". We can save by ignoring this message.
But when I try to create condition table, this field is not visible.
Please suggest me how to add field VOLEH(Volume unit).
Regards
Uma

When you open the possible entries you usually find the field twice, once in the structure for header or item, and once in the communication structure. Most likely your field is only in the item structure, you need to add it to the communication structure as well (or better a developer needs to do that).
You might need to fill the field in the Pricing_Prepare user exit too.
The warning usually appears, because it is SAP namespace, if you need to add the field, you might consider putting ZZ in front of the fieldname (ZZVOLEH).
Edited by: Markus Müller on Jun 27, 2008 3:33 PM

Not able to create conditional required fields at Tcode CJ20N Proj Systems

Hello experts,
I have a requirement to create a few custom fields under custom enhancement tab in CJ20N transaction, and depending on a particular value for one of the fields, another set of fields need to be set to required. (If FIELD1 = 'Y', FIELD2 & FIELD3 should be set to required)
My approaches..
1. Assign a screen group to FIELD2 and FIELD3. If FIELD1 = 'Y' then LOOP AT SCREEN, and set screen-required = 1 for that specific screen group.
Problem with this approach is that, if I select FIELD1 = 'Y' (hit space or enter -> sy-ucomm = TOGGLE), the fields are successfully set to required. However, now if at this point I go and change value for FIELD1 = 'X' (hit space or enter), FIELD2 and FIELD3 still remain set to required, and keep requesting value.
2. Do not set any fields to required. Instead set it to an information message in PAI, informing user that this field requires a value when FIELD1 = 'Y' on TOGGLE and SAVE.
Problem with this approach is that even though during TOGGLE event user is provided with an informational message, if the user directly decides to SAVE (no change for TOGGLE event), in this case the same message is displayed, and the project screen itself is closed. I do not think it would be ideal for the user to see the entire project close on SAVE everytime they miss a conditionally required field.
I am just not sure at this point how to handle this at SAVE so that I can still have the same control as I would when TOGGLE event is triggered.
Experts please help if you have come across such a situation!!! Your insight would be greatly appreciated!
Edited by: akkinair on Dec 16, 2011 1:25 AM

Please find below the response.
1. Assign a screen group to FIELD2 and FIELD3. If FIELD1 = 'Y' then LOOP AT SCREEN, and set screen-required = 1 for that specific screen group.
Problem with this approach is that, if I select FIELD1 = 'Y' (hit space or enter -> sy-ucomm = TOGGLE), the fields are successfully set to required. However, now if at this point I go and change value for FIELD1 = 'X' (hit space or enter), FIELD2 and FIELD3 still remain set to required, and keep requesting value.
--> When FIELD1 chnage used module with additon CHAIN-REQUEST and check its value if it is to be set to optional by using loop at screen and set screen-required =0.*_
2. Do not set any fields to required. Instead set it to an information message in PAI, informing user that this field requires a value when FIELD1 = 'Y' on TOGGLE and SAVE.
Problem with this approach is that even though during TOGGLE event user is provided with an informational message, if the user directly decides to SAVE (no change for TOGGLE event), in this case the same message is displayed, and the project screen itself is closed. I do not think it would be ideal for the user to see the entire project close on SAVE everytime they miss a conditionally required field.
--> Can you please clarify it.
Thanks
Nabehet

Conditional Required Fields

Is it possible to have conditional required fields. As in if a certain box is selected, certain fields will become required. Take a look at this example if this needs clarification. In this example, the left 3 text boxes are required. If I check the middle checkbox, can I make it so the 3 text fields in the middle now become required as well. Furthermore, if I check off the 3rd check box (rightmost one), can I make all of the text boxes as required fields. Thanks!

Hope You have the code on the check box change event, which decides the need of required or not.
if(this.rawValue =='1')
TextField1.mandatory = "error";
TextField2.mandatory = "error";
TextField3.mandatory = "error";
Gender.mandatory = "error";
Gender.border.edge.color.value = "225,0,0";
else{
TextField1.mandatory = "disabled";
TextField2.mandatory = "disabled";
TextField3.mandatory = "disabled";
Gender.mandatory = "disabled";
Gender.border.edge.color.value = "0,0,0";
If you have facing any problem send me ur form to [email protected] if possible, If need sample give me ur email id so that i can post the form.
RAGHU.

Condition type field when Define Pricing Procedure Determination

Hello Gurus,
there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
Many thanks,
Frank Zhang

Here is are the details of various fields while configuring pricing procedure.
A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERFu2026u2026u2026u2026.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
Kalpesh

How to conditionally encapsulate fields within ECC 6.0

I'm interested in strategies to conditionally encapsulate fields within ECC 6.0.
The requirement would be to mask specific fields (e.g. Vendor Name) within a particular data set (e.g. a particular Company Code) by default while allowing those fields to be visible by some users. The key is that we do not want to mask these fields globally, nor do we want them masked for every user. Even more important, we do not want to modify all the transactions and programs where these fields are available.
I know one option is to add custom code at the Domain level of the fields. We're currently investigating this further to see if it will satisfy all our needs and perform well.
I'm looking for any other options we should explore, including 3rd party options.
Thanks,
~Matt

Alex Ayers wrote:Taking the example of the vendor master, i dont think retrcition on F_LFA1_AEN would really help. when a display transaction is used the protected fields are also shown. I understand it is a "no worry' on the complaiance front, but i suppose there could be a valid reason for not allowing users to display something (the operator can shed light on that)
And from what i understand, the object doesnt get checked during the creation of master records too - its primarily to control the changes made on certain fields of the master record.
and it needs a certain amount of effort to understand & check the implications before starting with the filed group customizing
>
> For the benefit of Shekar there may be the opportunity to use transaction variants
thanks, Alex. This need could in all fairness end up with that.... a transaction variant
> 1. Don't give access to the transaction if you can't trust users to use it properly
> 2. Use a detective control to identify where users have changed things that they shouldn't have.
Why do i feel an Auditor posted this????
> Finally, using parameter ID's for this purpose generally will not work and should not be considered for security reasons
100% agree with you

Condition Update field

Hi,
I know we can set the condition update field in the condition type so that, it can store accumulated values, for example, discount only upto maximum of 3000pcs.
But this is one is based on Sales Order value and not Billing value. how can I set so that it considers only the invoice quantity and not the order quantity?
If I reject the Sales Order (using reason for rejection).. the accumulated value is not deducted or reset back to zero.. it still considers the quantity of the rejected item. What should we do so that it will not

I am not sure that will function, but check the customizing options behind the reason for rejection.
Another option would be to force a new price determination in the billing document (look at the copy control between the delivery note and the billing document at the item level).
Best Regards,
Franck

Tutorial: 8 Adding a Conditionally Dependent Field

Hi,
I am trying to implement chapter 8 Adding a Conditionally Dependent Field. However, the Commission percentages stays enabled no matter what the value of the jobid is.
Is this a bug or am I doing something wrong here?
Thanks, Joep

Joep,
If you send your testcase for the LOV problem, we will also look at this issue.
The conditionally dependent items work for me, so may be you made some typo.
Steven Davelaar,
JHeadstart Team.

AS92 with grey colour field

Hi all,
I must use AS92 to take over value but the fields are grey colour, how to change grey colour fieles to white colour fields.
Thanks very much
Ray

Hi,
In AS-92 takeover value entry is based on the asset transfer date. Cumulative Acquisition Value, Accumulated Ordinary Depreciation and Cumulative unplanned depreciation fields can be modified only if the asset capitalization date falls in the year, prior to year of, date of transfer.
If the asset is acquired in the year of transfer and before the date of transfer, then Ordinary depreciation posted and unplanned depreciation posted are the modifiable fields.
For the assets acquired after the date of transfer, you can find the entries in the transaction tab.
Hope this helps you,
regards,
Rengaraj

Set background color for conditional text fields by click of button.

Hi,
I am new to apex, the scenario is when i click on a button i.e. Save, it shoulld compare 2 fields P1 and P2 which are text fields.
If the value of P1 is greaterthan P2 then the whole P1 text field background color should change to "Red" otherwise in any other condition the P1 field should be "Green" color.
In which section the color function should be called on the Save button?
On the page in the HTML Header section i have added the below code but the background color is not getting set.
<script type="text/javascript">
function fncChangeColor()
var num1 = $v('P1');
var num2 = $v('P2');
if ( num1 > num2 ) {
document.getElementById("P1").style.background = "RED";
else {
document.getElementById("P1").style.background = "GREEN";
</script>
Can any one help me in moving ahead with this scenario with a detailed information.
Thanks,
Priyanka.

Hi,
Call function on button URL target
javascript:fncChangeColor()If button should submit page, then I think you do not need color field to green.
Just change to run submit function.
<script type="text/javascript">
function fncChangeColor(){
var num1 = $v('P1');
var num2 = $v('P2');
if ( num1 > num2 ) {
$x("P1").style.background = "RED";
return false;
apex.submit({request:"YOUR_REQUEST"});
</script>Regards,
Jari

Price condition creation & fields catalog update

Hello all SAP experts,
I am trying to create a pricing condition that will be applied in stock transport order based on shipping conditions. Depending on the shipping conditions used in the STO, the amount of this condition will change.
The thing is, I cannot get it to work.
<b>What I did:</b>
- created a new condition type
- included this condition in the current calculation schema
- added the shipping condition field (VSBED) in the field catalog for condition tables (it was not in standard field list)
- created a condition table with the shipping condition field embedded
- created an access sequence with reference to the above condition table
- linked the access sequence to the condition
- created a few condition records for the new condition type
<b>Result:</b>
When creating a STO, the system tries to populate but it is not working. When I look at the price deter;ination analysis, the system that the value of the shipping condition was not found, though it is defined in the STO.
<b>One step further</b>
I tried to change several things, but it isn't working. Looking at the access sequence, I noticed that the field for shipping conditions (VSBED) was stored in an internal document structure valid for document header (so-called 'KOMK' in the document structure column). I am a bit surprised because the system should look for the information at item level, not at header level. I tried to change the value to 'KOMP' (item level), but I don't know how to do it.
I realize my post is a bit lon and might get a bit confusing, but would you have any hint / idea on how to retrive the shipping conditions infomation properly?
Any info highly appreciated!
Thanks in advance,
Morgan

Please go through the steps below
- created a new condition type
This is file
- included this condition in the current calculation schema
this is fine
- added the shipping condition field (VSBED) in the field catalog for condition tables (it was not in standard field list)
This is fine
- created a condition table with the shipping condition field embedded
make sure the table is created properly
- created an access sequence with reference to the above condition table
Make sure the access sequence is created based on the way you want to defualt the condition in PO
like if you access seq should contian
e.g. your criteria is suppose STO type ST and vendor X and shipping condition is 01 then insert that condition in the PO
- linked the access sequence to the condition
check the access sequence in the condition record bu hitting Record for Access and here you should able see the value as per the criteria
- created a few condition records for the new condition type
This is fine
Now check you calculation schema that this condition should not checked as Manual determination in schema.
Hope this will help you to resolve ur problems

Pricing condition MM in reference to a SD condition : vendor field in VK11?

Hello everyone,
I am facing a problem with a MM condition type which has been defined in the custo with a SD "Reference condition type" (Reference application "V").
If I want to create the condition record for this condition, I have to use VK11 transaction instead of MEK1.
When I use MEK1 transaction on a classic MM condition, if I go to the "details", I can seize a payment term or the vendor.
But with the condition defined with a SD "Reference condition type", with VK11 transaction the field "vendor" is not reachable in the details tab.
Is there a way to add the field "vendor" in the details tab of the transaction VK11 ?
Thanks a lot for your help,
Benjamin.

You can create new access sequence and assgin the particular field in that aceess sequence

Condition table field order

Hello folks,
Is it important to list the fields in a condition table in the proper order ?
I do not think so and like to clarify with you pls.
regards
Ravi

Hi
A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.
Example
Example of a Condition Table
A sales department creates condition records for customer-specific material prices. The standard R/3 System includes condition table 005 for this purpose. The key of table 005 includes the following fields:
Sales organization
Distribution channel
Customer
Material
The first two fields identify important organizational data and the last two fields express the relationship between customers and specific materials. When the sales department creates a condition record for a material price or discount that is specific to one customer, the system automatically uses condition table 005 to define the key and store the record.
AS per SAP Help
regards
Prashanth

Conditional Mandatory Field in Material Master (Sugg. Needed

Hi ,
I am having a requirement where i need to make a particular field to be mandatory for a certain condition in Material Master.
Say for a Product Hierarchy i want to make Volume Rebate Group mandatory ( Sales Org 2 View).
Please suggest the possible solutions for the same.
Thanks,
Rachita.

Hi,
It is possible to get access to all other fields from within a field exit by using the below code. This is a field exit on GMG_HEADER_FIELDS-grant_type within program SAPLBDT_GMGR but by using the code below you can get data stored in any field within the program. i.e. GMG_HEADER_FIELDS-GRANT_NBR
Field-symbols: <status>.
assign ('(SAPLBDT_GMGR)GMG_HEADER_FIELDS-GRANT_NBR') to <status>.
if SY-SUBRC = 0.
message e003(zr) with <status> .
******other code*****************
endif.
Reward points if found helpful....
Cheers,
Rakesh.

Conditional Mandaotry field in Material Master (Suggestion Needed)

Hi ,
I am having a requirement where i need to make a particular field to be mandatory for a certain condition in Material Master.
Say for a Product Hierarchy i want to make Volume Rebate Group mandatory ( Sales Org 2 View).
Please suggest the possible solutions for the same.
No userexit is possible , Screen exit is also out of picture as i will not get the value of second variable -
Thanks
Rajiv

Hi Rajiv,
there is a user-exit that can be used .. MGA00001.
We use it to make some plausibility checks before saving a material and also some additional authorization checks.
<pre>FUNCTION EXIT_SAPLMGMU_001.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(WMARA) LIKE MARA STRUCTURE MARA
*"     VALUE(WMARC) LIKE MARC STRUCTURE MARC
*"     VALUE(WMARD) LIKE MARD STRUCTURE MARD
*"     VALUE(WMBEW) LIKE MBEW STRUCTURE MBEW
*"     VALUE(WMLGN) LIKE MLGN STRUCTURE MLGN
*"     VALUE(WMLGT) LIKE MLGT STRUCTURE MLGT
*"     VALUE(WMVKE) LIKE MVKE STRUCTURE MVKE
*"     VALUE(WSTAT) LIKE MGSTAT STRUCTURE MGSTAT
*"     VALUE(WMFHM) LIKE MFHM STRUCTURE MFHM
*"     VALUE(WMPOP) LIKE MPOP STRUCTURE MPOP
*" TABLES
*"      STEXT STRUCTURE SHORT_DESC
*"      SSTEUERTAB STRUCTURE MG03STEUER
*"      SSTEUMMTAB STRUCTURE MG03STEUMM
*"      WMEINH STRUCTURE SMEINH
*"      SMEAN_ME_TAB STRUCTURE MEAN
*" CHANGING
*"     VALUE(CMARA) LIKE MARU STRUCTURE MARU
*" EXCEPTIONS
*"      APPLICATION_ERROR
INCLUDE ZXMG0U02.
ENDFUNCTION.</pre>
Just prompt an error message in case the required field is not filled.
MESSAGE ennn(xx) RAISING application_error.
I am sure it will help to solve your problem.
Best regards
Ferdi

Conditionally coloured fields

Similar Messages

Maybe you are looking for