cancel
Showing results for 
Search instead for 
Did you mean: 

BBPCF02 transaction timed out..

Former Member
0 Kudos

Hi All,

One of the user is trying to perform confirmation using the transaction BBPCF02. Every time the user tries to go into the transaction, system is throwing timed out message.

Any clues on this? Is there any way to reset the Extended search criteria, which might be active, because of which the transaction is timing out.

Best Regards,

Mahesh. J

Accepted Solutions (0)

Answers (3)

Answers (3)

summer_wang
Contributor
0 Kudos

Hi ,

Please check the note :

1087040 BBPCF02: Performance problems for POs wit

Please check how big the PO is , condition entries accout data entries

There is no problem right now when we retrieve purchase order details since now we keep it in the buffer and there is no need to do RFC call. The most time consuming part is when we do validation of accounting data. When validation of accounting data is performed we also keep all data in the buffer, so that RFC call will not be executed if this data was already retrieved. In your case RFC calls are performed most of the times since in the PO there are different accounting data set.

If the account data is huge , you have to disable FI validation for the logical system.

If this is not the case in your system , you have to create a SAP ticket with Dump file and trace log attached.

I hope this information will help you.

Summer Wang

summer_wang
Contributor
0 Kudos

Hi ,

Please check the note :

1087040 BBPCF02: Performance problems for POs wit

Please check how big the PO is , condition entries accout data entries

There is no problem right now when we retrieve purchase order details since now we keep it in the buffer and there is no need to do RFC call. The most time consuming part is when we do validation of accounting data. When validation of accounting data is performed we also keep all data in the buffer, so that RFC call will not be executed if this data was already retrieved. In your case RFC calls are performed most of the times since in the PO there are different accounting data set.

If the account data is huge , you have to disable FI validation for the logical system.

If this is not the case in your system , you have to create a SAP ticket with Dump file and trace log attached.

I hope this information will help you.

Summer Wang

Former Member
0 Kudos

Hi

I had the same problem before. Please refer SAP on this. I thik you need to do some inbex a for Confirmation table.

Regards,

Satish B.