Skip to Content
author's profile photo Former Member
Former Member

Dynamic action not updating until Back button clicked in PA40

Hi all,

Not been able to find an answer for this on the forums so thought I'd post a question.

We are performing a leaver action in PA40 and all the data for the infotypes gets written up front except for 2 entries into It0015.

We have discovered that the data only gets written to the DB once you click the "Back" button in the menu bar (after the action is finished).

If we exit using /n etc the data isnt written.

It seems like this is some sort of commit that needs to be done at some point but can't get the system to commit the data using COMMIT WORK etc.

The It0015 is written using dynamic actions as are other infotypes but the other Dynamic actions are commiting.

I did orginally write a routine using HR_INFOTYPE_OPERATION but this didnt write anything at all so moved to dynamic action which we thought was working but now seems like it is not working as expected.

Anyone had any problems with this in the past and managed to overcome it.

Many thanks

Gaz

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 11, 2014 at 04:26 PM

    Got it!!!!

    In the function call (type F) I commented out the code and put the code into a separate program.

    Then in the Function call in the dynamic action I do a :

    submit ZHRPROGXXX
    with p_pernr = p0000-pernr
    with p_date = p0000-begda
    and RETURN.


    This runs the program in s different session and allows all dynamic action to work and do the update itself as well...


    also note to use the following in the called program to stop short dump:


    LOAD-OF-PROGRAM.
    * an event to avoid a short dump due to CE framework*
    * refer to SAP NOTES: 0000611782 / 0000716914
    PERFORM do_nothing(sapfp50p).

    Answer was in this thread:

    Thanks for all the input it is appreciated

    Cheers

    Gaz

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 09, 2014 at 01:17 PM

    Please paste your dynamic action entries here.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 11, 2014 at 08:36 AM

    Hi,

    Done a bit of testing with some other code and found something that may be significant.

    There is another dynamic action (type F) fired off later than the one listed above that calls a routine in a program that delimits current records and deletes future records from a number of infotypes.

    this is done using HR_INFOTYPE_OPERATION with a the no_commit set as space (so it does commit).

    If I exit out of this routine without doing any processing the IT0015 records are commited (without having to Back arrow out of PA40).

    I have tried setting the no_commit to 'X' but this didnt make a difference to the overall processing.

    So it seems that HR_INFOTYPE_OPERATION is causing an issue.... is this because it is called from a dynamic action?

    Also why do some Dynamic actions work and others not.... very odd.

    Any ideas or suggestions welcomed... will keep testing and update with anything I else I find.

    Many Thanks

    Gaz

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Chris,

      I may try this but just wanted to clarify that the function (type F) call to delete and delimt is not within the dynamic action above .

      as in:

      *---- First Entry ------------ P P0000-MASSN='D3' P T001P-MOLGA='08'/X P T001P-MOLGA='11'/X I INS,0015/D F GET_DATE(ZSDATE) W P0015-BEGDA=RP50D-DATE1 W P0015-LGART='7541' W P0015-ANZHL='1.00' W P0015-ZEINH='025' *---- Second entry ------------ P P0000-MASSN='D3' P T001P-MOLGA='08'/X P T001P-MOLGA='11'/X I INS,0015/D F GET_DATE(ZSDATE) W P0015-BEGDA=RP50D-DATE1 W P0015-LGART='7519' W P0015-ANZHL='1.00' W P0015-ZEINH='025' * *--- THIRD ACTION TO DEL -- F DEL_STUFF(ZSDELSTUFF)

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.