Quantcast
Channel: SCN : Unanswered Discussions - Supply Chain Management (SAP SCM)
Viewing all articles
Browse latest Browse all 5579

Inconsistencies BALHDR / BALDAT (?)

$
0
0

Hello experts,

 

before opening an OSS-note I wanted to ask here, maybe someone has similar experiences. I found a lot of similar discussions, but most of it were about data volume, not about quantity of ABAP-table-entries.

 

We use Report SBAL_DELETE to reduce entries in tables BALHDR and BALDAT daily. If my understanding is correct the link between both tables is done by field LOG_HANDLE. When using the report we can see that the number of entries in the tables are decreasing. I checked this, selected logs were deleted in both tables BALHDR and BALDAT.

 

But it seems there is a big gap between both tables, in our System we have 13608 entries in BALHDR and 105.642.247 entries in BALDAT. So I made some Analysis on the base of linking LOG_HANDLE-field. I found out that a lot of LOG_HANDLE's in BALDAT are NOT in BALHDR. For my understanding this shouldn't be... am I right? I just found 1 hint in scn wiki:

 

     LOG_HANDLE record in BALDAT and BALHDR tables. - ABAP Development - SCN Wiki

 

Or can there be processes (especially in SCM-System) where BALDAT entries exist without linked BALHDR data?

 

If this is really a problem...

1. Is my suggestion correct that report SBAL_DELETE can't handle BALDAT if BALHDR is missing for the same log?

2. Did someone have a similar Situation? Or does someone have an idea how this can happen (we don't use any Z-reports related to log-creation / deletion)?

3. Does someone have an idea to solve it (except of opening OSS note )? Is there maybe a report to clear such entries?

 

Many thanks in advance!

 

Best regards

Harald


Viewing all articles
Browse latest Browse all 5579

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>