Skip to Content

Cannot createa Wo for all User using BAPI_ALM_ORDER_MAINTAIN

Hi All,

I have a requirement that need to create a Work Order automatically when a notification is saved, according with a Z customizing table.

I have created Function module that is launched in UPDATE TASK when notification is saved in an implementation of BADI IF_EX_NOTIF_EVENT_SAVE this function call BAPI_ALM_ORDER_MAINTAIN FM to create Work order Linked to a notification.

For me and my colleague users, both are in Spain, it works fine, but for the customer who is in USA doesn’t.

I send to the customer my Logon User, to try it in her equipment and it does not work.

The customer has the right authorization to create Work orders in background and in online mode.

Any Ideas that who can happen?

Regards

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Dec 30, 2016 at 08:02 PM

    And what does 'it does not work' mean?

    Is the BAdI-implementation called? If so, is the BAPI executed? If so, then you must be able to get the Return-Messages? What does the RETURN-table say?

    (Maybe this is too obvious, but they are executing in the same System / Client are they?)

    You could start Debugging with the 'USA'-user account and find out for yourself ...?

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 03, 2017 at 09:57 AM

    Hi Nic,

    Badi-implementation is being called for any user, there are other developments that are called from this BADI,

    I'm sure that user is executing it in the same System/Client.

    we cannot debugg with the 'USA'-user while user don't let us her User.

    Thank you for you help.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 10, 2017 at 01:08 PM

    Get a USA test user created in your system and debug using this test user.

    PeteA

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 03, 2017 at 10:16 AM

    Are you trying to execute a BAPI in an update task FM, that should trigger some dump (at last when you COMMIT) Were you actually successful with the true transaction and not during some execution of the FM/BAdI out of context?

    Could you consider replacing the IN UPDATE TASK with a IN BACKGROUND TASK so it executes in another LUW?

    Regards,
    Raymond

    Add comment
    10|10000 characters needed characters exceeded