cancel
Showing results for 
Search instead for 
Did you mean: 

VBBE Table taking time to get updated

0 Kudos

When we are creating a Sales Order .It is triggering an Event to a Third Party System .The event is getting triggered before the VBBE table is getting updated .Hence wrong information is flowing to the third party system .

But what we are observing that the VBBE table is taking time to get updated . We found some blogs on ATP_VBBE_CONSISTENCY .

Is it because Once the Sales Order is created the background job runs and it takes time to update the VBBE table .

If that is the case , is there any way we can imporve the perofrmance

stanislaslemaire
Participant
0 Kudos

Hello,

If actions done in event not critical, use function module as update module with low priority. Then VBBE should be updated before event will be called...

0 Kudos

stanislaslemaire

If I understand correctly, you are asking to use the option "Start delayed" .Is my understanding correct

Sandra_Rossi
Active Contributor
0 Kudos

"taking time to get updated" = probably the database updates are done via Update Task, usually it's done asynchronously. It's not specific to VBBE table, and not specific to sales orders.

Update Task queue may take lot of time to execute if workload is important => view it through SM13

Also, you should indicate which information is wrong in VBBE, because sometimes you may have some additional jobs which update specific columns separately.

NB: your assumption about "Start Delayed" is wrong.

Accepted Solutions (0)

Answers (1)

Answers (1)

Lakshmipathi
Active Contributor
0 Kudos

If you feel, VBBE is taking long time to get updated, you can consider creating an index as recommended in OSS note 540881