Article number is missing for a sales document in VBAP table compared to BW data.

Question

Hi,
We are loading data from 2LIS_11_VAITM and 2LIS_11_V_SSL to 0SD_O01, when we execute a report based on this DSO we are getting Article number 2224859 (for example) for sales order 573345 (for example) but when we check in VBAP/VA03 for the same sales order/document (573345)  we don't have the Article Number.
It is delta load to the DSO from the two datasources and will executed daily once.
Please suggest me any one on this.

Answer 1

All,
Thanks for your replys.
Here are the more details about this.
We are using 3.X flow in BW. (3.x Data sources)
In BW                                           Mapping                In ECC     
0DOC_NUMBER    Sales document  ----------->  VBELN          Sales Document
0MATERIAL           Material  -----------------------> MATNR           Article Number
In VBAP table, I have entered Sales document 573345 and executed then I got so many Article Numbers and Filtered with Article Number 2224859 then got no data.
As I told earlier in BW for the same Sales Document number we have Article Number.
We have start routine.
PROGRAM UPDATE_ROUTINE.
*$*$ begin of global - insert your declaration only below this line  *-*
*$*$ end of global - insert your declaration only before this line   *-*
* The follow definition is new in the BW3.x
TYPES:
  BEGIN OF DATA_PACKAGE_STRUCTURE.
     INCLUDE STRUCTURE /BIC/CS2LIS_11_VAITM.
TYPES:
     RECNO   LIKE sy-tabix,
  END OF DATA_PACKAGE_STRUCTURE.
DATA:
  DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
       WITH HEADER LINE
       WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
FORM startup
  TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
           MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
           DATA_PACKAGE STRUCTURE DATA_PACKAGE
  USING    RECORD_ALL LIKE SY-TABIX
           SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
  CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
*$*$ begin of routine - insert your code only below this line        *-*
* fill the internal table "MONITOR", to make monitor entries
  LOOP AT DATA_PACKAGE.
    IF DATA_PACKAGE-doc_categ NE 'C' AND
       DATA_PACKAGE-doc_categ NE 'I'.
      DELETE DATA_PACKAGE.
    elseif DATA_PACKAGE-recordmode eq 'R'.
      DATA_PACKAGE-recordmode = 'X'.
      modify DATA_PACKAGE.
    ENDIF.
  ENDLOOP.
* if abort is not equal zero, the update process will be canceled
  ABORT = 0.
*$*$ end of routine - insert your code only before this line         *-*
ENDFORM.
I think there is no much more lookups. ( I don't have much knowledge in ABAP)
I have checked in another tables also like VBFA VBAG VBAK, VBKD, VBUK and VBUP but in those tables I don't have Article (MATNR) field.
One more Question.
Can any one tell me how the Queued Delta mechanism will work.
As of now I know that, when ever any changes have been done to the tables this will pickup the changes and move into LBWQ after that RSA7.
My Question is, If some one has forcefully deleted one Article number from the table for a Sales Order then this Queued delta will pick that also?
Please let me know If you need any more details