EMMA / BPEM : automatic cases creation

[Former Member]

Hi Experts,

I am working on a special scenario with EMMA and I would like to know your advices.

I would like that the system create automatic EMMA cases on IS-U when the replication from CRM fails for some reasons. I am already using ECRMREPL to process the failed contracts. But this transaction is not user-friendly and I would be interested on creating automatic cases when special messages are processed. We can see these messages on SLG1, so I assume it is possible to create automatic EMMA cases ? Right ?

I created a new case category as automatic for my message but it is not working. I can see in the cookbook that a business process need to be defined. But it is not a transaction, and I guess there is no standard business process for ECRMREPL. How I can set the EMMA session for my scenario ? Any idea ?

Hope it is clear...

Regards,

Nick

[Former Member]

I guess nobody can give me some tips, or this is not clear enough ?

Thank you.

Nick

[dhiraj_kathet]

Hi Nick,

If you want to create emma cases automatically for any message, and you have already created business process and case category for the same. You just need to assign the message class and message number in the message pool of the case category. Once you have done that you can execute transaction EMMA for the business process(you can enter only tcode ECRMREPL). Execute the transaction for preparing jobs for jobs not prepared yet(select both checkboxes) once and then execute again with create clarification case and prepared jobs(both checked) for creating cases. Log will display if the cases are created.

Do revert if you need any clarification.

Thanks,

Dhiraj

[Former Member]

Hello Dhiraj,

Thanks a lot for your answer.

I understand well what you say but in transaction ECRMREPL, there is no log process started (for example, this is the case in transaction EA00) by the standard.

Do I need to start the log process by a specific enhancement ?

Nick

PS : when I talk about log process start, i mean FM "EMMA_LOG_PROCESS_START".

[Former Member]

Hello Nick,

In order to activate EMMA for transaction ECRMREPL, you have to maintain entry for this transaction in the IMG path

Financial Accounting -> Contract Accounts Receivable and Payable-> Basic Functions

-> Enhanced Message Management

-> Specifications for Customer Transaction and Messages

-> Define Customer Transactions for Message Management

For this,

First of all you have to create a custom Business area (eg:ZCRM)  and a Custom Business process code (eg: ZCRMCONTR)  for this Bus area  with respective job analysis class (eg:CL_EMMA_ANALYZE_JOB_APPLLOG) and  analysis class ( eg :    CL_EMMA_PROC_APPLLOGMSGS_V2 ) and messages for identification of Execution/Bus Obj).

You have to assign this Business Process Code

(eg: ZCRMCONTR)  for maintaining entry for   Custom Transactions for Message Management.

Then you can create clarification category based on the messages writing to Application log while executing the transaction ECRMREPL., which can be used to  create respective cases using EMMA .

Regards,

Riyas.

[Aswathi_a2]

I am working on a BPEM case creation for a custom message class xreated previously and displayed in slg1. This is triggered via EL18.

So i created a new case category with reference to another case category giving standard message class error. The problem is that in slg1, while my standard error message is displayed under start business process and end business process, my custom error not displayed between any business process and may be thats why no clarification case is created upon executing emma.

[EMMAX-Hans]

Hi Ashwathi,

To use your own exceptions there are some requirements (see screen shot below):

1. You need to check if EL18 is available in the customizing setting Enhanced Message management -> Specifications for Customer-Defined Business Processes and Messages -> Define Customer Transactions for Message Management. 
   If not, add it.
2. You need to add your exception to the BPEM customizing setting and provide the data contained in the parameters of the exception in Enhanced Message management -> Specifications for Customer-Defined Business Processes and Messages -> Define Business Objects for Customer-Defined Messages

Once done, you can run EL18 again so that it produces the SLG1 entry.

Identify the EL18 transaction you just ran in EMMAJL and prepare the job found, check if your exception is in the job log and see if it is identified as an error. If so, after preparation, create cases and the case should appear. If the exception is not there, make sure your coding where the exception is written, is using the same BP Code as the EL18 transaction.

Hope this helps, otherwise, let me know.

Best Regards,

Hans Kardol 

[Aswathi_a2]

Thank you so much for your response, my issue is that i am getting the error in slg1, but in EMMAJL my message is displayed in error as "messages without reference to business object".

The case category is created as category business object specific.

But my custom message class and number doesnt have any business process start and end code included in it. How can that be included in the code. Is there any standard code that can be added to include my message class between start and end business process in slg1.

[EMMAX-Hans]

As I said: your coding, where the exception is written, must be using the same Business Process Code as the EL18 transaction. 

I did send you a coding example, it is based on our EMMAX product, won't work with copy and paste, but it will give you an idea of how to write the wrapper for the exception.

Hope this helps, otherwise, please let me know and I will get you in touch with our developer.