EMMA case is created when it is not expected to be created

[Former Member]

Hello SDN's,

EMMA case is created with EB10 case category for move out scenario with two installation numbers. One installation number is shown under objects tab and another one appeared under message tab. The installation reported under message tab has the actual problem with billing because two billing orders exist at the same time (one periodic billing order and one final billing order). So this case is a valid case under EB10 category according to the standard SAP functionality shown below.

However the installation under u201Cobjects tabu201D doesnu2019t have problem. The user is confused with two different installation numbers (one under objects tab and another under messages tab) being reported on EMMA case.

The user looks at the installation number under objects tab and checks if there is a problem with billing for the contract associated with the installation. User does not find any problem with that contract and thinks that EMMA case is created unnecessarily.

Could you please suggest why the case is being created with two installations which shown in objects tab and messaged tab.

Please let me know if you need more information.

Regards,

KV

[Former Member · Accepted solution]

How are you creating the BPEM case ?..EMMA batch job, custom batch job or on Adhoc basis ?

[Former Member]

Hello,

Thank you for quick reply.

We are creating EMMA cases by using EMMA job in FPEMMAMA transaction code.

Thank you.

Regards,

KV

[Former Member]

kv,

My first thought is that the object customizing might not be specific enough.

Did you check the customizing for installation in the objects tab (message pool binding) if the binding is correct? You could try to connect object "intallation" (objects tab) to the installation in the object container that starts with "VAR_" . This might solve your problem.

Regards,

Alex

[Former Member]

Thank you for your inputs