cancel
Showing results for 
Search instead for 
Did you mean: 

Bopf save method

Former Member
0 Kudos

Hi all,

we have scenario where we are updating multiple record in bopf tables.

in this we are using modify and save method of transnational manager.

if we are updating 10 records and if  5th record is getting error while saving .

it will not update remaining records.

and save method will have 5th record error and same error its giving for the 6th record and not updating data .

here 6th record data is correct and it should update.

how we should clear this eo_messages of previous record in save method.

any idea.

thanks.

Kesar.

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos


Hello Keser,

Since you use the transaction manager save , I assume that you are updating the records from a report or some kind of external service consumer. How do you do the update ? Do you do a mass update by building all records in the modifications table and make a single call , or do you make a separate modify call per record ?

If the error message leads to a failed save , it would mean that the BO has a consistency group of validations configured preventing the save from failing when the BO is inconsistent ( meaning if the validation return a failed key , the BO is inconsistent and shall not be saved ) resulting in the entire transaction failing.

From a consumer perspective , the BO service provider provides the message to the service consumer indicating what is wrong , subduing/ignoring/removing that message will not result in the whole transaction proceeding to a successful save.

You can do one of the two things here.

1. The bad way - create one transaction per record, so only the transaction with the inconsistent record fails , the others are successful. This is not a recommended approach , you should always make use of mass enablement wherever possible.

2. React to the error message from the first failed transaction , correct the inconsistent record and attempt the modification again. This method might require some user interaction , and goes against the idea of a fire and forget report.

Thanks,

Indranil.