I have not received this specific error, so I can't help with this specific question. I will add though that we are trying to reduce our dependency on BSEG due to it being our longest running load and most error prone (due to it being a cluster table no doubt). If you want to try this route I would suggest to rewrite your applications using BSEG and try to utilize the various subledger tables that comprise BSEG: BSIS/BSAS (GL Open/Cleared), BSIK/BSAK (Vendor Open/Cleared), and BSID/BSAD (Customer Open/Cleared). On the SAP side these are the tables that are combined to create BSEG, so you should be able to stop using BSEG and utilize these tables instead. Since these 6 tables are transparent tables (physical tables) you should notice that they load much better then BSEG - especially if you are doing an incremental load.
If you find that you need BSEG specifically then try to reduce the number of fields you are pulling (pull only what is needed). When SAP receives your query it analyses the fields you are requesting and then builds the view of BSEG - therefore reducing the number of fields you request will improve query performance as you may not require SAP to join as many tables). Also, try to utilize all the key fields in your query and see if this helps. We only pull what we need from BSEG today, and have noticed dramatic performance hits adding specific fields to our query. One field might cost us minutes, while a different one costs us 20x more time.
- Trevor
.png "prasad_dumbre"){kind=avatar}
