ECC downtime and data loss management

[former_member477229]

Hi,

We need to confirm some data from shop floor to ECC using MII 12.2 with BAPI call.

We are using the JCo action.

We are concern about the data loss that can happen when ECC is down.

I am not sure how we can prevent this data loss and post this data back to ECC when ECC is up.

Is there a way in MII to handle this scenario or we need to build any custom solution as below.

1. Prepare a table in RDBMS to hold the data to confirm.

2 Schedule a trax which will post the data when ECC is up.

Thanks

Vishal Jadhav

[former_member193328 · Accepted solution]

Hi Vishal

You have 2 options (the third being a custom implementation).

The first and the easiest is to implement the data buffer option as mentioned by Nikhil earlier. In this you can buffer the JCo Action if there is a failure to deliver messages to ECC. The buffer takes care of retrying a certain amount of times before it fails finally. You can configure the no of times it retries and also the delay after which it tries to resend. Only drawback of this approach is that you cannot process any other steps after the JCo Action finishes.

The other approach is to push the XML payload to the MessageListeners. Create a transaction to read the messages from this list and send to ECC. This trx can be triggered either immediately or by a scheduler. If the message fails set the status to failed and you can retry them in the transaction. In your trx you can pull all messages with status Failed and Received and send them again.

Let me know if this helps.

Regards

Partha

[former_member477229 · Accepted solution]

Thanks guys and Partha..

The scenario is

There is a trax logic in place. From  this trx we are calling ECC BAPI to post data.

But the trax has other logic too , which needs to be executed even after JCo fails.

So Data buffer option cant be implemented.

The second approach is customize approach and for which we need to code the logic...

That answer my question.

Thanks for all your valuable inputs...

Vishal Jadhav

[former_member204240 · Accepted solution]

I hope, I have explained in detail flow in my reply for second approach through logic.

[Nikhil_Makhija]

how about using Data Buffer functionality in MII?

http://help.sap.com/saphelp_mii140sp04/helpdata/en/4c/72e154e631469ee10000000a15822d/content.htm?fra...

Nikhil

[former_member204240]

You have to write a Trx in MII to handle retry of error messages.

You need to Handle 2 types of errors

1.Connection Error and

2.Error due to Data.

You can try following things.

Create a Error Log table to save the data(message payload) and status in MII DB

1. Main Trx

Jco Call

Condition to check connection Error.

Condition block to check any data error.

Use an assignment block to assign status S for success and E for Error and original message payload.

Insert qry to store the Message payload and status in error log table

2. Retry Trx

Qry to read all error messages with Status E from Error Log table.

Repeat on that with repeater and

Jco call to confirm again

Schedule the Retry Transaction according to the required time period.

May be if needed you can also provide Email Notification if any errors.

Check link below for data buffering

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2016cebf-5a17-2e10-63b9-c37ac20b2...