Skip to Content

2LIS_13_VDITM - records missing


I have a problem with the delta of 2LIS_13_VDITM.

Some records are missing and I don't understand why. If a do an init of the setup table with the missing bill numbers and a full repair in BW, it works. It's my work around for the moment. But why the delta doesn't work?

Every month about 10% of the bill number are missing...

Thanks for your help.


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

5 Answers

  • Best Answer
    Jan 08 at 07:58 PM

    Hi Steph,

    I'm assuming you've checked that the relevant records do not appear in the PSA. If that is the case, you may want to try and identify a specific document or change in document that didn't arrive, and try and recreate them in a test environment. You need to test and see if the records arrive in the queue seen in LBWQ, if so whether running the job defined in LBWE moves them to the relevant queue in RSA7, and if they appear in RSA7 whether they are loaded to the PSA.

    My experience with missing records in LIS datasources usually had to do with changes to values in fields that were not defined as delta relevant in the extractor. However if documents are missing entirely, that's certainly strange. There seems to be a note describing a logging mechanism used to investigate such issues, although it's not something I've had a chance to use.



    Add comment
    10|10000 characters needed characters exceeded

  • Jan 14 at 01:14 PM

    Thank shai for your answer.

    Yes I have checked the PSA, and the records are not in.

    The problem to test if the records arrive in the queue, is that most of them arrive... I have about 5% of missing records... and until now I couldn´t identify something different between a record which arrive in the PSA and one which doesn't arrive... Its, very strange... It's the fistr time I meet this problem.

    And As you said, it's not a problem of some adding fields would not be relevant, because the missing records are news created billing document, not modified...

    If I find the reason, I will advise you.

    Thank you for your help.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 15 at 11:28 AM

    Hi Stephane,

    Another possible culprit is some incorrect coding in a SD user-exit.

    Some notes describing this behaviour:

    Note 216448 - BW/SIS: Incorrect update / SD user exit

    Note 757361 - Additional data records in BW when document changed

    They mention the case of duplicate records, but if field UPDKZ is modified missing ones can also occur.



    Add comment
    10|10000 characters needed characters exceeded

  • Jan 16 at 01:07 PM

    Thank you for your answer Miguel too.

    I have a doubt... my client have done a change of machine in december. They have changed the ERP machine and the BW machine. And after the connection of the 2 new machines, they didn´t excute a new initializacion. The delta continued to work.

    May be set-up tables should have been emptied, filled again and an init load executed in BW...

    What do you think?

    Add comment
    10|10000 characters needed characters exceeded

    • As long as logical system names were kept the same, the RFC connections were configured and the delta

      queue data was transfered before the "machine change", I don't think is neccessary a delta initialization.

      The decisive factor would be finding how those 5% missing records differentiate from the other ones, (a new bill type, are created in a different process, ...)

  • Jan 17 at 08:46 AM

    Hi Stephane,

    I have the same problem. How did you fix this issue?

    Thank you.


    Add comment
    10|10000 characters needed characters exceeded