Dynamic actions in sequence

Hi all,
I have 5 dynamic actions in a page.
I want to know whether there is any way to execute these dynamic actions in order ( i.e when the 1'st action is completed then only the 2'nd and 3'rd should be processed)..
waiting for ur replies
with regards
BalaG

If the dynamic actions need to work in sequence, then you can put them as "TRUE" actions in one and the same dynamic action.
Regards,
Vincent
http://vincentdeelen.blogspot.com

Similar Messages

Dynamic action with function works, doesnt refresh textfield

Hi all,
experimenting with dynamic actions so I got the following setup:
I've built a screen with 2 text boxes
P7_input
P7_output
The goal is to put some tet in P7 input and have it returned with additional text in P7_OUTPUT
CREATE OR REPLACE PROCEDURE PRC_ECHO
P_INPUT IN VARCHAR2 DEFAULT 'LEEG'
, P_OUTPUT OUT VARCHAR2
) AS
BEGIN
p_output := 'Ingevoerd: ' || p_input;
END PRC_ECHO;I've created a dynamic action on the LOSE FOCUS event of item P7_INPUT.
The true action executes PL/SQL (sequence number 10)
Begin
eigen_apps.uga_prc_echo (:p7_input, :P7_OUTPUT);
end;"Page items to submit" are set to P7_INPUT, P7_OUTPUT
(and I tried with just P7_INPUT).
The second true action (sequence number 20) does a REFRESH on ITEM P7_OUTPUT (and I tried refresh region and other things I thought would make it work.)
When I enter something in P7_INPUT and tab, click or enter away from the P7_INPUT field, nothing changes in my P7_OUTPUT textfield.
Only when I hit the refresh button in my browser P7_OUTPUT is filled with 'Ingevoerd: <P7_INPUT value>.
So. The procedure does return the value into P7_OUTPUT, but I cant get an instant refresh of the P7_OUTPUT to work.
Can any of you help me?
Robin

Getting some other errors now, will look into this tomorrow.
1 error has occurred
ORA-06550: line 4, column 18: PLS-00382: expression is of wrong type ORA-06550: line 4, column 7: PL/SQL: Statement ignoredNeed to check my procedure...
Robin

Problem setting a hidden item value when button clicked with dynamic action or pl/sql process

Apex 4.1
Oracle 11g
I have a page that consists of a main region and several sub regions. I have a pl/sql process in After Header SET_DISPLAY(:P400_DISPLAY :='MAIN';)
Three subregions have a contional display where P400_DISPLAY = STORE. This works in hiding the sub regions.
Now I want to change the P400_DISPLAY value to STORE to show the subregions when I hit a button.
I tried creating a dynamic action for on click of the add button but get the following error:
The selected button uses a 'Button Template' that does not contain the #BUTTON_ID# substitution string
I went to the templates and found:
Substitution Strings
Substitution strings are used within sub templates to reference component values. This report details substitution string usage for this template.
Substitution String
Referenced
From
Description
#LINK#
Yes
Template
To be used in an "href" attribute
#JAVASCRIPT#
No
To be used in an "onclick" attribute
#LABEL#
Yes
Template
Button Label
#BUTTON_ATTRIBUTES#
No
Button Attributes
#BUTTON_ID#
No
Generated button ID will be either the button's Static ID if defined, or if not will be an internally generated ID in the format 'B' || [Internal Button ID]
I then tried creating a page process, pl/sql, :P400_DISPLAY :='STORE'; when the appropriate button is pressed. The button action is submit page. However, it does not change the P400_DISPLAY value and the subregions stay hidden.
Suggestions please on how to fix the template or change the P400_DISPLAY value?

The root issue is that, although you change the value of your page item, it isn't visible to other areas of the page until it is in the session. So, any other action based on the value of your page item; the visibility of a control, a report based on the item's value, etc. will all be unaffected by changing the value of the page item until it has been changed in the session. Even after this the items are stored in the session, you must thereafter do something to cause the value to be reevaluated. To see the effect of this, observe that your page loads and evaluates the value of your page item, it sees that is "MAIN" and hides the regions. However, it doesn't reevaluate them after this.
So; your choices to get this value set in the session are to either Submit the page, or use JavaScript to set the value in the session. If you use the latter of these, you'll have to do some further work to cause the visibility tests to be re-run, So, let's stick with with the submit method.
What you've done above sounds correct for this but, there are a lot of decisions you could have made that might have caused things not to happen in the correct sequence.
Firstly, let's confirm that what I describe above is your problem. From the development environment, load the page, click the button to change the value and submit. Now, click the link labelled Session. Is it still set to MAIN? If so; this is your issue.
Let's start with the your After Header computation. Did you set it to *only* run if the current value of your page item is NULL??? If not, that's your problem.
Load Page -> Item set to 'Main' by Computation -> Click Button -> Item set to STORE -> Submit -> Load Page -> Item set to 'Main' by Computation
See the problem?
Assuming this isn't the issue, you created a Branch to the same page, right? What is your process point for the Branch? Is it *After* Validation, Computation etc? Because if not, you aren't changing the value before the submit happens.
I bet it is the first issue but, take a look at these.
Cheers,
-Joe

Dynamic action on LOV using tabular form

Hello,
I realize this has likely been dealt with somewhere already, but I'm going to ask anyway.
I have a master/detail form. The detail form has an option to add rows. I have created a dynamic action as defined below...
True Action:
Sequence: 10
Action: Javascript Expression
Fire On Page Load: No
Code: $(this.triggeringElement ).val()
Sequence: 20
Action: SQL Statement
Fire On Page Load: No
Code: select travel_status from territories_summary_v where territory_code=:P3_FIND_COUNTRY_CODE and language='US';
Sequence: 30
Action: Javascript Expression
Fire On Page Load: No
Code: $(this.triggeringElement).closest("tr").find("td[headers='TRAVEL_STATUS_CODE'] input").val($v('P3_FIND_COLOR'));
The P3_FIND_COLOR and P3_FIND_COUNTRY_CODE are defined as hidden fields.
This DA seems to partially work. It will update the travel status code with the proper value for each line. I can see it on screen. But when I apply changes it doesn't save this particular value to the database. If I physically go to the field and type something in, it will save this field. All other values save ok... just not this column .. regardless of the number of detail lines.
Further to this, when I add a row and a new blank row appears, if I change the country, the DA does not fire at all. I've put an alert in on sequence 10 and the alert will fire for a pre-existing row in the table... but not a new row. I would have thought that because it's an onChange DA associated with the country code, it would work for each new row regardless of how many rows are added or whether its a new row vs existing row.
So the first issue is why it won't save the data that is populated in travel status code when I can clearly see it there? Secondly, why this DA is not firing when I add a new row?
If anyone can help me it would be appreciated. I've done a lot of searches but have not come up with much where these issues are concerned.

There is no way to make a good guess on this without an example. It is hard to say what the reason could be.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.apress.com/9781430235125
https://apex.oracle.com/pls/apex/f?p=31517:1
http://www.amazon.de/Oracle-APEX-XE-Praxis/dp/3826655494
-------------------------------------------------------------------

Custom dynamic action not firing

Using Apex 4.2.2 on 11g
I have a standard report A1
There is a column link on report A1 which refreshes chart C1 using a custom dynamic action.
The column link on report A1 has the URL set to javascript:$.event.trigger('RefreshTrend_2', [{key_2:'#COL01#' }]);
and there is a dynamic action D1 RefreshTrend_2 which sets the value of the chart filter P17_KEY_2 to the value of the javascript variable key_2 and then refreshes chart C1
The dynamic action is custom with a type DOMObject of document and no condition
This works fine but when I add another report/chart (report A2, chart C2) combination with a similar dynamic action (D2), D2 is a copy of D1 with the values for the variables and chart region changed.
The A2/C2 functionality works fine on its own, D2 gets fired when I click the column link, but not when there are 2 dynamic actions of custom/document on the page.
This column link on A2 only fires the dynamic action D2 if dynamic action D2 has a higher sequence than D1 (if i move it above D1 in the list it will fire, but then D1 does not fire for the column link on A1
Am I missing something?
Thanks
Kathryn

Here is my page source from the browser (i put in some blank lines here to separate the 3 dynamic actions)
<script type="text/javascript">
apex.da.initDaEventList = function(){
apex.da.gEventList = [
{"triggeringElement":"P17_IS_OK","triggeringElementType":"ITEM","triggeringConditionType":"NOT_NULL","bindType":"bind","bindEventType":"change",actionList:[{"eventResult":true,"executeOnPageInit":true,"stopExecutionOnError":true,"affectedElementsType":"BUTTON",javascriptFunction:apex.da.enable,"action":"NATIVE_ENABLE"},{"eventResult":false,"executeOnPageInit":true,"stopExecutionOnError":true,"affectedElementsType":"BUTTON",javascriptFunction:apex.da.disable,"action":"NATIVE_DISABLE"}]},
{"triggeringElement":"document","triggeringElementType":"DOM_OBJECT","bindType":"live","bindDelegateTo":document,"bindEventType":"RefreshTrend_2",actionList:[{"eventResult":true,"executeOnPageInit":true,"stopExecutionOnError":true,"waitForResult":true,"affectedElementsType":"ITEM","affectedElements":"P17_KEY_2",javascriptFunction:apex.da.setValue,"ajaxIdentifier":"3BB4667C9E25BFB8DCF63639507A062A88F713A193C0D30DDF1CEA8D6875A7F9","attribute01":"JAVASCRIPT_EXPRESSION","attribute05":"this.data.key_2","attribute09":"N","action":"NATIVE_SET_VALUE"},{"eventResult":true,"executeOnPageInit":true,"stopExecutionOnError":true,"affectedElementsType":"REGION","affectedRegionId":"R2959102626294614",javascriptFunction:apex.da.refresh,"action":"NATIVE_REFRESH"}]},
{"triggeringElement":"document","triggeringElementType":"DOM_OBJECT","bindType":"live","bindDelegateTo":document,"bindEventType":"RefreshTrend_1",actionList:[{"eventResult":true,"executeOnPageInit":true,"stopExecutionOnError":true,"waitForResult":true,"affectedElementsType":"ITEM","affectedElements":"P17_KEY_1",javascriptFunction:apex.da.setValue,"ajaxIdentifier":"51D6B9673F7096076392A95D9D00B417D49DEB96D878B419FC6D1E482D0AB2F0","attribute01":"JAVASCRIPT_EXPRESSION","attribute05":"this.data.key_1","attribute09":"N","action":"NATIVE_SET_VALUE"},{"eventResult":true,"executeOnPageInit":false,"stopExecutionOnError":true,"affectedElementsType":"REGION","affectedRegionId":"R2925517394066336",javascriptFunction:apex.da.refresh,"action":"NATIVE_REFRESH"}]}];
</script>
Only the first "document" dynamic action will fire, even though I fire them by name using
javascript:$.event.trigger('RefreshTrend_1', [{key_1:'#COL01#' }]); from the column link.
Kathryn

Creating two dynamic action in a page

Hi,
I have created two dynamic action under the page_items(p6_item,p6_item1 both are hidden).
First dynamic action under p6_item is action1.
properties of action Event-> Change
Selection_Type->Item
Item-> p6_Item
Value-> show
(When i Hit the button viewall it should only display region1)
True Action:
sequence->10, Action->Show, Fire->Yes, Selection Type->region, Region->region1
sequence->20, Action->Hide, Fire->Yes, Selection Type->region, Region->region2
False action:
sequence->30, Action->Hide, Fire->Yes, Selection Type->region, Region->region1
Second Dynamic action under p6_item1 is action2
properties of action Event-> Change
Selection_Type->Item
Item-> p6_Item1
Value-> show
(When i Hit the button Search it should only display region2)
True Action:
sequence->10, Action->Show, Fire->Yes, Selection Type->region, Region->region2
sequence->20, Action->Hide, Fire->Yes, Selection Type->region, Region->region1
False action:
sequence->30, Action->Hide, Fire->Yes, Selection Type->region, Region->region2
Here the problem is, when i hit the viewall button it is not displaying region1 instead region2 is displayin region1 is hidden. when i hit the Search Button it is displaying region2 , region1 is hidden. Foer me, When viewall hitted region1 should only display not region2. When Search button hitted region2 should only display not region1.

Hi little foot,
I have created my page in apex.oracle.com. you can clearly see the issue which i am having in the page.
Workspace:listen
Username: [email protected]
Password:apex
Application Name: 45665
Page: page1

Dynamic actions and PA-PD integration a problem

Are you aware of an update problem with MSS and PA-PD integration? This information was made available in a presentation to us last year. Was this issue resolved in mySAP ERP 2004?
Dynamic actions and PA-PD integration a problem
Dynamic actions and PA-PD integration are not
processed on updates made from the web (but in the
background through a batch or call transaction session)
Thats why most standard PCRs require HR to process
the transaction using the SAP GUI in the foreground
This normally affects changes to infotypes 0000 &
0001
Then the next slide states:
Workaround for dynamic actions
Review dynamic actions in table T588Z (use SE16 to
display) and document the infotypes and values that
trigger dynamic actions
Incorporate those infotypes into your background
processing and web forms (if necessary)
Workaround for PA-PD integration
Include the integration steps for these infotypes in your
background processing (just as in conversions)

Hi John,
Not sure if it is fixed.. or can be fixed.. we are still in 47 & Use custom code to account for Dynamic Actions.. the PCR processes use the function module HR_MAINTAIN_MASTERDATA to update the infotypes. This function mimics a BDC & hence cannot handle Dynamic Actions... Basically, the issue is not with MSS but it is the way Dynamic Actions work.. to quote SAP "Dynamic actions are not correctly processed in batch input sessions since in batch input the sequence of the screens needs to be predefined correctly. To be able to process dynamic actions in batch input, the checks of the dynamic actions need to be programmed when creating the batch input session. To avoid errors when programming and running the session, the static actions only are processed in batch input. Calls of infotypes that are triggered by dynamic actions should be realized by separate Transaction calls.
Please take a look at OSS Note #386027 for additional info about Dynamic Actions.
Regards,
Suresh Datti

Dynamic actions and tabular forms

I'm trying to attach a dynamic action to a tabular form item, and it's not working the way I'm expecting it to. Since you can't attach dynamic actions to parts of a tabular form in the "normal" way that you can for page items, I'm using JQuery selectors to pick the parts to link to. For links (such as opening a pop-up window with more information about a row), this is working fine. But I'm really struggling to attach to a simple checkbox.
On my tabular form, I've got a simple checkbox. I've tried putting text in the Element Attributes, Element Option Attributes, CSS Class, CSS Style, and HTML Expression fields, but none of them appear to be making it through to the source code of the generated page. Which means, I think, that I'm limited to using a jQuery Selector along the lines of "input[name=f07]", but creating a dynamic action on click or on change with that selector doesn't seem to ever fire.
What am I missing?
-David

Ok, this is interesting. When I tried to mock this up on apex.oracle.com, I was able to make it work (though I had to change the selector to "input[name=f07_NOSUBMIT]", which means I'm going to have to walk the DOM to get the actual value...but I'm pretty sure I can handle that). After a bit of scratching my head, I eventually found that my pop-up dynamic action was somehow or other blocking the checkbox dynamic action from firing. Changing the sequence so that the checkbox DA happens first allows them both to fire.
Here's the javascript from the pop-up DA (it's based on this post by Havard Kristiansen):
/* prevent default behavior on click */
var trgt = this.triggeringElement.href;
var e = this.browserEvent;
e.preventDefault();
/* Trigger JQuery UI dialog */
var horizontalPadding = 30;
var verticalPadding = 30;
$('<iframe id="modalDialog" src="' + trgt + '" />').dialog({
     title: "Item Details",
     autoOpen: true,
     width: 570,
     height: 400,
     modal: true,
     close: function(event, ui) {$(this).remove();},
     overlay: {
          opacity: 0.5,
          background: "black"}
}).width(570 - horizontalPadding).height(400 - verticalPadding);
return false;At this point, the checkbox DA's action is simply an alert box. Like I said, I'm not sure what's going on, but I'm at least able to move forward...
-David

Dynamic actions - how to create an infotype with a date - 1 day.

Hi everyone,
I need a requirement to change an infotype through dynamic action with ENDDA = BEGDA of maintaned infotype(0000) - 1 day.
In other words when a personel action is performed, another infotype (2001) should appear for change, and in the validity period of this infotype should end with the day before the start of the personel action.
is it possible to achieive this using dynamic actions? how?
Thanks!
Stanislaw Adamski

Hi Adamski,
A dynamic action has the following components.
Infotype Number (INFTY): specifies the infotype for which you want the dynamic action triggered
Subtype (SUBTY): narrows the focus to a specific subtype
Field Name (FIELDN): starts your action when a maintenance function is performed on a particular field
Function (FC): specifies the various maintenance operations to which your dynamic action would respond. They are 02 (change); 04 (create); 06 (create and change); 08 (delete); 10 (change and delete); 12 (create and delete). Dynamic actions are only applicable in maintenance operations, not in display functions.
Sequence Number (NO): refers to a sequential number.
Step (A): specifies a particular type of action. No dynamic action is executed if the function character has a value other than one of the following:
             P: Plausibility checks, which allow you to check certain conditions.
             I: Calls an infotype for processing
             W: Called after the I statement and used to assign values to screen fields while creating or copying another infotype record through the I statement
              F: Calls a FORM routine (subroutines in ABAP) during your action. The routine may reside in or out the module pool MPNNNN00.
             V: Lets you treat collectively a number of fields for which you want to define a common dynamic action
              M: Sends SAP Office mail
Variable function part: The variable function part along with the step indicator forms the core part of your action. It specifies the processing details when the dynamic action is triggered. For example:
you have to look for the scenario what you are planning tyo create .
The maintenance of dynamic actions is done via the view V_T588Z, as shown in 1 (IMG menu path Personnel Management>Global Settings in Personnel Management>Basic Settings>Infotypes>Create Dynamic Actions
Here you havev to use conditions INS for the infotype what you want to create..
Please brief the light on the scenario.
Warm Regards,
Kapil Kaushal

About creating an AJAX page with DML procedures using dynamic actions

About creating an AJAX page with DML procedures in APEX using dynamic actions. Help with limitations.
I want to share my experience, creating AJAX procedures in APEX 4.0.
LIMITATIONS
•     How Can I Hide UPDATE button while I press NEW button. ??
•     How Can I Hide CREATE button while I’m UPDATING A RECORD. ??
•     How can I avoid multiple Inserts or Updates. ??
Here are the steps to create an AJAX Updatable Form using the sample table DEPTS. You can see the demo here: [http://apex.oracle.com/pls/apex/f?p=15488:1]
1)     Create a blank page
2)     Add a Report Region for departments (It shows the columns deptno, dname and loc).
3)     Add an HTML Region and create the elements to edit a Department.
a.     P1_DEPTNO (Hidden to store PK)
b.     P1_DNAME (Text Field)
c.     P1_LOC (Text Field)
4)     You also have to create a hidden element called P1_ACTION. This will help to trigger dynamic actions to perform DMLs.
5)     Open Page Attributes and in the HTML Header Section include the following code.
<script>
     function doSelect(pId){
          $x_Value(‘P1_DEPTNO’,pId);
          $x_Value(‘P1_ACTION’,’SELECT’);
</script>
6)     Modify the column DEPTNO in the report, to add column link. In the link text you can use #DEPTNO# , in target you must select ‘URL ‘ and in the URL field write javascript:doSelect(#DEPTNO#);
7)     Create the following Buttons in the Form Region.
CANCEL     Redirects to URL: javascript:$x_Value(‘P150_ACTION’,’CANCEL’);
NEW          Redirects to URL: javascript:$x_Value(‘P150_ACTION’,’NEW’);
SAVE          Redirects to URL: javascript:$x_Value(‘P150_ACTION’,’UPDATE’);
CREATE          Redirects to URL: javascript:$x_Value(‘P150_ACTION’,’CREATE’);
8)     Create the following Dynamic Action to Select a Department
Name:     Select Dept
Event:     Change
Selection Type:     Item(s)
Item(s):     P1_ACTION
Condition:     equal to
Value:     SELECT
Action:     Execute PL/SQL Code
PL/SQL Code:
SELECT dname, loc
INTO :P1_DNAME, :P1_LOC
FROM dept
WHERE deptno = :P1_DEPTNO;
Page Items to Submit:     P1_DEPTNO, P1_DNAME, P1_LOC
Don’t include any false action and create the Dynamic Action.
The first limitation, the value of page elements don’t do refresh so I added the following true actions to the dynamic action AFTER Execute PL/SQL Code.
Action:     Set Value
Unmark *‘Fire on page load’* and *‘Stop execution on error’*
Set Type:     PL/SQL Expression
PL/SQL Expression:     :P1_DNAME
Page Items to submit:     (none) (leave it blank)
Affected Elements: Item P1_DNAME
Action:     Set Value
Unmark *‘Fire on page load’* and *‘Stop execution on error’*
Set Type:     PL/SQL Expression
PL/SQL Expression:     :P1_LOC
Page Items to submit:     (none) (leave it blank)
Affected Elements: Item P1_LOC
These actions allow refresh the items display value.
9)     Create the following Dynamic Action to Update a Department
Name:     Update Dept
Event:     Change
Selection Type:     Item(s)
Item(s):     P1_ACTION
Condition:     equal to
Value:     CREATE
Action:     Execute PL/SQL Code
PL/SQL Code:
UPDATE dept SET
dname = :P1_DNAME,
loc = :P1_LOC
WHERE deptno = :P1_DEPTNO;
Page Items to Submit:     P1_DEPTNO, P1_DNAME, P1_LOC
Don’t include any false action and create the Dynamic Action.
Include the following True Actions BEFORE the Execute PL/SQL Code true Action.
Action:     Set Value
Unmark ‘Fire on page load’ and ‘Stop execution on error’
Set Type:     PL/SQL Expression
PL/SQL Expression:     :P1_DNAME
Page Items to submit:     P1_DNAME
Affected Elements: Item P1_DNAME
Action:     Set Value
Unmark *‘Fire on page load’* and *‘Stop execution on error’*
Set Type:     PL/SQL Expression
PL/SQL Expression:     :P1_LOC
Page Items to submit:     P1_LOC
Affected Elements: Item P1_LOC
These actions allow refresh the items display value.
Finally to refresh the Departments report, add the following true action at the end
Action:     Refresh
Affected Elements: Region Departments
10)     Create the following Dynamic Action to Create a Department
Name:     Create Dept
Event:     Change
Selection Type:     Item(s)
Item(s):     P1_ACTION
Condition:     equal to
Value:     CREATE
Action:     Execute PL/SQL Code
PL/SQL Code:
INSERT INTO dept(deptno,dname,loc)
VALUES (:P1_DEPTNO,:P1_DNAME,:P1_LOC);
Page Items to Submit:     P1_DEPTNO, P1_DNAME, P1_LOC
Don’t include any false action and create the Dynamic Action.
Include the following True Actions BEFORE the Execute PL/SQL Code true Action.
Action:     Set Value
Unmark *‘Fire on page load’* and *‘Stop execution on error’*
Set Type:     PL/SQL Function Body
PL/SQL Function Body:
DECLARE
v_pk NUMBER;
BEGIN
SELECT DEPT_SEQ.nextval INTO v_pk FROM DUAL;; -- or any other existing sequence
RETURN v_pk;
END;
Page Items to submit:     P1_DEPTNO
Affected Elements: Item P1_DEPTNO
Action:     Set Value
Unmark *‘Fire on page load’* and *‘Stop execution on error’*
Set Type:     PL/SQL Expression
PL/SQL Expression:     :P1_DNAME
Page Items to submit:     P1_DNAME
Affected Elements: Item P1_DNAME
Action:     Set Value
Unmark ‘Fire on page load’ and ‘Stop execution on error’
Set Type:     PL/SQL Expression
PL/SQL Expression:     :P1_LOC
Page Items to submit:     P1_LOC
Affected Elements: Item P1_LOC
These actions allow refresh the items display value.
Finally to refresh the Departments report, add the following true action at the end
Action:     Refresh
Affected Elements: Region Departments
11)     Create the following Dynamic Action to delete a department
Name:     Delete Dept
Event:     Change
Selection Type:     Item(s)
Item(s):     P1_ACTION
Condition:     equal to
Value:     DELETE
Action:     Execute PL/SQL Code
PL/SQL Code:
DELETE dept
WHERE deptno = :P1_DEPTNO;
Page Items to Submit:     P1_DEPTNO
Don’t include any false action and create the Dynamic Action.
Include the following True Actions AFTER the Execute PL/SQL Code true Action.
Action:     Refresh
Affected Elements: Region Departments
Action:     Clear
Unmark ‘Fire on page load’
Affected Elements: Items P1_DEPTNO, P1_DNAME, P1_LOC
12)     Finally Create the following Dynamic Action for the NEW event
Name:     New Dept
Event:     Change
Selection Type:     Item(s)
Item(s):     P1_ACTION
Condition:     equal to
Value:     NEW
Action:     Clear
Unmark *‘Fire on page load’*
Affected Elements: Items P1_DEPTNO, P1_DNAME, P1_LOC

I need some help to solve this issues
•     How Can I Hide UPDATE button while I press NEW button. ??
•     How Can I Hide CREATE button while I’m UPDATING A RECORD. ??
•     How can I avoid multiple Inserts or Updates. ??

Testing Dynamic Actions

Hello,
     I had created a dynamic action for a custom infotype 90X9 in which I am comparing a field(FIELD1) if it is initial i am maintaining a record in 90Y9 infotype.
    Through PA30 I created a NULL entry for the FIELD1 for a employee (EMP1) for infotype 90X9 and then I checked 90Y9 hoping that maintained value in dynamic action will fill the infotype 90YP, But this had not happend.
     Is this the correct way to TEST it? Please suggest a TEST method if it is wrong method to test this dynamic action scenario.

Hello
You know what is the most interesting thing about your test case? You are trying to copy the NULL value between infotypes. Well, is the test case not working only for NULL values or all values?
Can you also mention following about your dynamic action?
Infotype:
Subtype:
Field Name:
Function Character:
Sequence Number:
Indicator for Step:
Variable Function Part:
Thanks
Anand

Executing Dynamic actions in Background???

Hello Experts,
We have a requirement where we need to automate PA40. The data would be sent in csv file and we need to perform the required steps to insert data into Infotypes.
The issue is in batch mode (background mode), the dynamic actions wouldn't be called and the business wants the dynamic actions to be considered as well.
Pls let me know if there is any way we can interpret the dynamic actions dynamically; meaning the prog should be able to handle the newly created dynamic actions as well.
Any pointers to this are highly appreciated.
Regards
RK

Hello Raj;
In documentation of Dynamic Actions it is written so:
Note on creating a batch input session:
Dynamic actions are not processed in a batch input session.
In batch input, you must specify the exact sequence of the screens. To
ensure this is the case, you must have already programmed the dynamic
action checks before you create the batch input session.
To avoid errors only the static actions are processed when you program
and process a session. Infotypes that usually only appear in the system
as a result of a dynamic action should be updated by calling up the
transaction separately.
Hope this can help you,
Regards.
Okan

How to abort tasks in a Dynamic Action when apex.confirm = Cancel

I have a text field that has a Dynamic Action attached to it. When the field is changed, the Dynamic Action fires. There are 6 separate tasks in that Dynamic Action.
The very first task is a call to apex.confirm. I want to make sure that the user understand the implications of changing the value in this field. So, up pops the dialog, the user reads the information, and decides to click OK or Cancel.
If OK is clicked, I want to continue through the rest of the tasks in the Dynamic Action. If CANCEL is clicked, I want to just abort out of the Dynamic Action.
Is that possible?
Apex 4.1.1.00.23
Edited by: Mark T. on Mar 1, 2012 9:49 AM

Yes, I do see a different behavior.
I've set up an app on apex.oracle.com, #60312. Workspace is mavericksolutions. Login pwolf. Password A1B2C3 change on first login.
The first field is tied to a dynamic action. The first task in the DA is an apex.confirm. Type something into the first field then click TAB to bring up the dialog box. Whether I click OK or click CANCEL, the 2nd task is still occurring. It appears that the only difference is that if I click OK, I also get a submit of the page.
What I want, in fact, is twofold:
1. If I click CANCEL, then STOP the execution of the remainder of the tasks in the Dynamic Action.
2. If I click OK, go ahead and process the rest of the tasks in the Dynamic Action, but DO NOT SUBMIT.
Basically, I want to ask the user if it's OK to go ahead and make the on-screen changes, but I do NOT want to do an auto-save. I want the user to look at the results on the screen and click the actual SAVE (or CREATE) button after ensuring their accuracy. Right now, it appears that the apex.confirm is firing a page submit when I click OK (the fields get cleared out). I don't want that page submit.
I THINK I can accomplish goal #1 with a workaround, by splitting the DA into two pieces. Piece #1 would have only the confirmation dialog. Piece #2 would be fired from the same field change, would have a sequence number AFTER piece #1, and would be conditional on the value of the expression returned by the apex.confirm. So if the apex.confirm returned 'DOTHIS' when I click OK, I would look to see if Expression = DOTHIS for piece #2. If not, then piece #2 wouldn't fire.
The remaining trouble, then, is that if I click OK to fire piece #2, the page submit will subsequently fire following the completion of piece #2. And no matter what, I definitely do NOT want a page submit. Is there a function similar to apex.confirm that does not do a page submit?
Anyway, take a look at the app. It's not performing the way that I anticipated, which is the same behavior that you described. I expected that it would do exactly what you said. Alas...

Custom program for Dynamic Actions

Iam using BDCs for Actions and Org.Assignment infotypes. The dynamic actions are planned to be carried out by using separate function modules.
My query is, On the plausibility check conditions lots of structures are referred (eg: PSPAR,RP50D etc). How do i perform this condition check in the custom program (for dynamic actions) as these structures do not have any data?
Thanks
Message was edited by: SShenoy

1. PSAVE-FIELDNAME will use the old values in the FIELD. It will be used in cases when we have to do plausibility checks on the basis of new as well as old value, eg, we want to use dynamic action for employees whose status changes from 'inactive' to 'active'
2. Sequence no represents sequence no. If for a particular Infotype and FCode, we have to specify which step has to be performed first. Sequence no tells the system exactly this thing.
Regards
Lincoln

HCM Process and Forms Dynamic Actions

Hi
We are implementing HCM process and forms and presume that dynamic actions will have to be recreated as rules.
Can anyone give any guidance in this area as some of our dynamic actions are quite complex.
Many thanks
Ian

Hi,
For HR forms please follow the following link
HCM Processes and Forms (www.service.sap.com/erp: - SAP ERP Human Capital Management -> Workforce Process Management -> HCM Processes and Forms -> Media Library)
https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000081848&
A dynamic action has the following components.
Infotype Number (INFTY): specifies the infotype for which you want the dynamic action triggered
Subtype (SUBTY): narrows the focus to a specific subtype
Field Name (FIELDN): starts your action when a maintenance function is performed on a particular field
Function (FC): specifies the various maintenance operations to which your dynamic action would respond. They are 02 (change); 04 (create); 06 (create and change); 08 (delete); 10 (change and delete); 12 (create and delete). Dynamic actions are only applicable in maintenance operations, not in display functions.
Sequence Number (NO): refers to a sequential number.
Step (A): specifies a particular type of action. No dynamic action is executed if the function character has a value other than one of the following:
             P: Plausibility checks, which allow you to check certain conditions.
             I: Calls an infotype for processing
             W: Called after the I statement and used to assign values to screen fields while creating or copying another infotype record through the I statement
              F: Calls a FORM routine (subroutines in ABAP) during your action. The routine may reside in or out the module pool MPNNNN00.
             V: Lets you treat collectively a number of fields for which you want to define a common dynamic action
              M: Sends SAP Office mail
Variable function part: The variable function part along with the step indicator forms the core part of your action. It specifies the processing details when the dynamic action is triggered. For example:
Requirement: When the postal code or the city of an employeeu2019s permanent residence is changed in infotype 0006, an email should be sent to the administrator.
INFTY    SUBTY    FIELDN    FC          NO.    STEP       VARIABLE FUNCTION
0006           1             ORT01      06             001           V               PSTLZ
0006           1             PSTLZ      06             002           M               M0001
The V statement on line 001 is used to link the two fields to the M statement. The statements relevant to field PSTLZ are also applicable to the ORT01 field.
When a record is created or changed in infotype 0006 of permanent address, an email is sent using the feature M0001. Information such as the recipient address, subject, and content of the mail is derived from M0001.
Warm REgards,
Kapil

Dynamic actions in sequence

Similar Messages

Maybe you are looking for