PO : Invoice value in ME23N is not matching with 2LIS_02_SCL field BWGEO

Question

Hi Expert,
              1) Invoice value in ME23N tcode is not matching with datasource 2LIS_02_SCL field BWGEO in item level
for few item BWGEO field contain the data with tax but for few item the value is not coming correctly.
2) The value is not matching for that particular item which has same material document in other Item level.
eg. PO(eg 60000XXXXX) if item 1 has invoice value with tax is 1300+52 and its material doc is XXXX1234. if same material doc XXXX1234 is present in
item 2 for another invoice of same material invoice value with tax is 1200+48. In that case the value which is coming in
BWGEO field is 1300 only.
I am working in 7.0 system for AFS specific. My whole transaction is in INR.
Thanks and Regards
Lalit Kumar

Answer 1

Please review the information below from one of our deverlopers       
- it may explain the behaviour you are seeing on your system: 
When posting a GOODS RECEIPT for a DELTA UPLOAD process you only will    
have the information regarding the GOODS RECEIPT values (XMCEKET-WEMNG   
and XMCEKET-WEWRT) and not the invoice values (XMCEKET-REMNG and         
XMCEKET-REWRT).                                                                               
When posting an INVOICE for a DELTA UPLOAD process you only will         
have the information regarding the INVOICE values (XMCEKET-REMNG         
and XMCEKET-REWRT) and not the GOODS RECEIPT values (XMCEKET-WEMNG and   
XMCEKET-WEWRT).                                                                               
The DELTA INIT process is different, because for this process, all       
information about posted documents against a purchasing order need to    
processed again and this means that all documents related to an order    
(invoices, goods receipt, deliver costs, goods issue, etc)               
are read from database and rebuild one by one in the same process, and   
of course this information in available.                                                                               
When posting an invoice, the goods receipt information is not            
available because of the following reasons:                                                                               
1 - System standard fields.                                              
In datasource 2LIS_02_SCL, there is only                                 
fields BWMNG - that represents quantity, BWGEO and BWGEO that            
represent values. The information under these fields are dependent       
from the information of field BWVORG (BW transaction key). This field    
determines whether these values are from a purchasing order, goods       
receipt or an invoice. You never have a missing information, but when    
you want to get goods receipt values, you need to check where the        
BWVORG correspond to goods receipt process and not invoice.                                                                               
2 - Performance                                                          
There are documents as purchasing orders and schedule agreements that    
are opened for years in some customer system (it may not be your case),  
where goods receipt and invoices have been posted during all this time.  
Every time that a new document is posted in order to built the           
cancellation sentence (ROCANCEL = X) and in order to add the new         
value in the old, system need to process all previous posted documents,  
and this means processing time. For this reason when posting invoices    
only previous documents that are invoices are taken into account and     
not goods receipt.                                                       
The delta fields, DBWMNG and DBWGEO, are the difference between the 
purchasing order quantity and values and the goods receipt quantity 
and values, then is natural that this information is only available 
when processing a goods receipt and not when processing an invoice. 
I'm sorry if this is not the system behavior that you are expecting,
but this is the normal standard behavior and this is really necessary
because of the system performance when dealing with documents that  
have a long order history.                                          
Hope this information is useful for you
Best Regards
Barry