1.Rate yourself in pl/sql and Order to cash cycle.
2 Types of cursor
3.Explicit and implicit cursor
4.Order to Cash cycle.
5.How to personalise a LOV
6.back to back flow
7.Table related to Order Managemnt
8.TCA architecture ,Customer and the party tables
9. Shipping Exceptions
Friday, December 3, 2010
Sunday, November 28, 2010
Oracle apps Form Personalisation Debugging Steps
Most of the time we do personalisation and it doesnt behave as we assumed it to be .
Then we end up wasting most of the time checking and testing why it is not working.
In this article i will be covering how to debug the form personalisation .
WHY FORM PERSONALISATION IS NOT WORKING?
A rule or action may not run for a variety of reasons:
a.The Rule or Action is not enabled
b.The Condition has evaluated to FALSE
c.The Trigger Event and/or Trigger Object were not what you expected
The scope of the rule only consists of Responsibility, Industry and/or User, and none is true for the current context
d.An action is executing the Builtin 'RAISE FORM_TRIGGER_FAILURE' . That will abort all further processing for that event.
e.The Language of the Action, if not ‘All’, is different than what you are currently running
f.You have set Custom Code to ‘Off’ or ‘Core code only’ in the pulldown menu.
g.Rules are created for a Function. You might be running the same form, but as a different function.
h.You need to re-open the form so that the new personalization get applied.
To test whether its running or not
There can be a case that form personalisation is running but it is not working. So to test that Create a message type of 'SHOW' and add some useful test after the interested action.
Now re-run the form and you will be able to see the message when that event occurs.
Form Personalisation is running and action is getting fired but personalization is not getting applied.
Often an Action may execute, but by the time control returns to the user the property you set has been overridden. What can you do?
Try performing the action at a ‘lower’ event.
Properties that affect all records of a block: set at WHEN-NEW-BLOCK-INSTANCE or WHEN-NEW-RECORD-INSTANCE
Properties that affect a specific item in a block: set at WHEN-NEW-ITEM-INSTANCE
The downside of the ‘lower’ events is that they fire more frequently
Another Method of Debugging the Form Personalisation is to set teh debug to step-by-step .
This help in knowing the exact condition getting processed and the result after evaluation of the conditions
Now It will pop up the message every time a trigger or its condition is getting evaluated.
This way you can easily debug the form personalisation .It will be also helpful in getting more insight on how a personalisation is getting fired and why it is nt getting fired.
Please leave a comment in case you like this or need more details .
I will get back to you
Then we end up wasting most of the time checking and testing why it is not working.
In this article i will be covering how to debug the form personalisation .
WHY FORM PERSONALISATION IS NOT WORKING?
A rule or action may not run for a variety of reasons:
a.The Rule or Action is not enabled
b.The Condition has evaluated to FALSE
c.The Trigger Event and/or Trigger Object were not what you expected
The scope of the rule only consists of Responsibility, Industry and/or User, and none is true for the current context
d.An action is executing the Builtin 'RAISE FORM_TRIGGER_FAILURE' . That will abort all further processing for that event.
e.The Language of the Action, if not ‘All’, is different than what you are currently running
f.You have set Custom Code to ‘Off’ or ‘Core code only’ in the pulldown menu.
g.Rules are created for a Function. You might be running the same form, but as a different function.
h.You need to re-open the form so that the new personalization get applied.
To test whether its running or not
There can be a case that form personalisation is running but it is not working. So to test that Create a message type of 'SHOW' and add some useful test after the interested action.
Now re-run the form and you will be able to see the message when that event occurs.
Form Personalisation is running and action is getting fired but personalization is not getting applied.
Often an Action may execute, but by the time control returns to the user the property you set has been overridden. What can you do?
Try performing the action at a ‘lower’ event.
Properties that affect all records of a block: set at WHEN-NEW-BLOCK-INSTANCE or WHEN-NEW-RECORD-INSTANCE
Properties that affect a specific item in a block: set at WHEN-NEW-ITEM-INSTANCE
The downside of the ‘lower’ events is that they fire more frequently
Another Method of Debugging the Form Personalisation is to set teh debug to step-by-step .
This help in knowing the exact condition getting processed and the result after evaluation of the conditions
Now It will pop up the message every time a trigger or its condition is getting evaluated.
This way you can easily debug the form personalisation .It will be also helpful in getting more insight on how a personalisation is getting fired and why it is nt getting fired.
Please leave a comment in case you like this or need more details .
I will get back to you
Subscribe to:
Comments (Atom)