Movement Type 340 doesn't have Storage Location Associated with it

Question

When a batch is given a new valuation type, there is no storage location associated with that movement, because the movement would be for the entire batch obviuosly.  In BI though, that creates a problem, because the movement needs to have a storage location assigned to it. Here is an example of the problem:
Storage Location----Batch--Xbuy Current Stock-----Cert Current Stock
..........0001...................122....................100......................................0
Then batch 122 is moved from xbuy to cert.  But, since there is no storage location associated with that movement, the current stock now looks like this:
Storage Location----Batch--Xbuy Current Stock-----Cert Current Stock
............#.......................122...................-100...................................100
..........0001...................122....................100......................................0
But it should look like this:
Storage Location----Batch--Xbuy Current Stock-----Cert Current Stock
..........0001...................122......................0......................................100
We are using the standard SAP Extractor for this inventory model, and I am curious as to whether there is a fix to this out there, or how we should go about fixing it?
Thanks,
Owen

Answer 1

The problem I am having is kind of a display and a data issue.  All the data from the source system is coming over to BI in this case, but the problem is that the two systems are fundamentally different.  In ECC, a batch can change from one valuation type to another with no thought to storage location, and that works just fine.  However, when that same record is in BI, if it doesn't have a value for every characteristic in the model (including storage location in this case), then the ad-hoc report won't drill down correctly.
To answer your options:
1.  We don't have the option of just not showing storage location, because this problem would render storage location useless because of data inconsistencies, and storage locations are an important part of our business.
2.  We have several storage locations, so this will not work either.
Also, since we have several different storage locations we use, there is no way to just assign storage location 0001 to every empty record.  However, I am thinking of a solution along these lines.  If there was somewhere we could go to see the storage location of the particular batch, then we could fill the storage location at the time of the data load.  The problem we would need to overcome though is timing.  How do we do this for historical data that has moved storage locations?  What if the movement goes to the delta queue, and then the storage location changes?
Thanks,
Owen