Skip to Content

Event handler type

Hi experts,

have changed the EM customizing settings recently. Have created a custom application object type for FUs and FOs.

Have done the following Settings:

1. create application object type for FUs and another one for FOs

2. create custom condition for custom AOT and assign it to the event handler type

3. create rule set and activities for FUs and FOs and expected event profiles as copy of the standard

2. create Event handler types for Fus and FOs

2. assign Event Manager to each AOT and activate

3. assign Standard mapping Profile to Logical system and custom application object type in "assign Parameter"

4. assign custom AOT to FU type and FO type

The FU is saved and an Event handler is generated, but it has the standard event handler type and not the custom event handler type.

Would someone tell me what is the thing that determines the event handler type?

Thanks in advance

Points will be rewarded quickly.

Regards

Petra

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Aug 19, 2015 at 06:29 AM

    Hi Petra,

    could you post some screenshots from your EH Type customizing and the condition assigned to it?

    In general the logic is if you have a BPT in your case TMS_TOR with more than 1 EH Type in /SAPTRX/TSC0TT:

    - EM sorts it according to Sequence Number

    - Then it goes through it ascneding

    - Checks the condition

    - The first EH Type where the condition is true will be taken

    I think here is the problem in your case. Check the sequence numbers and the conditions.

    Best regards,
    Steffen

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 18, 2015 at 06:54 PM

    Try diabling the standard AOT configurations.

    Have you create a new BPT or using the existing TMS_TOR?- I think new BPT need an enhancement in standard BADI.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Affan,

      yesterday, I read the EM book again and I saw that setting an AOT explicitly as inactive would lead to updating the related Event handlers with the correct data. so, your answer was actually correct.

      If Event handler types and/or application object types are changed, the "old" AOTs can be explicitely de-activated and then, the system does not have tp live with inconsistencies.
      I am not 100% sure because I have not tested it.

  • Aug 19, 2015 at 01:16 AM

    Hi Petra,

    For your config "2. create custom condition for custom AOT and assign it to the event handler type", I am sure you mean't assign custom AOT to Custom EH Type. Isn't it?

    Then during FU/FO create/change, see if the flow is through you custom AOT by putting a break point. If it hits the breakpoint then you should be able to create custom Event Handlers.

    So, to your question, custom AOT condition on your custom EH type should work provided right BPT is there.

    Also, as Affan said, disable/remove Event Manager from standard AOT. If they have to be there, make sure your sequence is right and/or there is no check on the "Stop AO Determination" on the standard AOTs.

    Otherwise, your config seems good to create custom EH type ( double check you Assign Profile to Mapping ).

    Let us know if you still don't see Custom EHs.

    Thanks.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 19, 2015 at 03:37 AM

    Hi Petra,

    1. I echo Vishnu comment on "Stop AO Determination" should be unchecked for standard AOT Type, because you custom AOT type will not find once standard AO determined.

    2. Can you enable log of EH posting in standard and custom Event handler type "3 - Verbose - Details for Each process" and check why it is calling standard EH in SAP EM side.

    3. Change standard Event handler type priority to 2 or 5 and make customer EH type priority to 1.

    Check and let us know.

    Regards


    GGOPII

    Add comment
    10|10000 characters needed characters exceeded