Skip to Content

What type of transaction will not be captured in 2LIS_13_VDITM delta queue?

Hi guys,

I'm not sure of the reason but we have missing delta data in our 2LIS_13_VDITM via ODP DTP (without infopackage). I can't find any pattern if the missed delta data is related to billing type or what. Would you guys know what type of transaction will not be captured in the delta queue of 2LIS_13_VDITM? I'm thinking this might be a bug in ODQMON? Anyone here encountered missing delta in the extractor via ODP extraction or via the normal RSA7 infopackage?

What could be the possible reason for this? Any idea how to fix this? I already read some blogs and questions related to missing delta but still can't find the answer.


The missing billing documents are present in VBRP but were not extracted in BW. I think those billing documents did not go to delta queue ODQMON.

Thank you so much.


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Jan 16 at 11:26 PM

    Check the billing type of the missing records. Pro-forma invoices are not extractec by 2LIS_13_VDITM.

    John Hawk

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Loed,

      You need to have a conversation with your SD functional support, but I will try to answer the best I can.

      Pro-forma documents are created for reporting or billing purposes, but will not affect the general ledger. For example, a pro-forma invoice is required by customs authorities for taxation or shipping insurance to determine value in case of loss, but the "real" invoice won't be posted until receipt by the customer. In SD, there is a special "pro-forma" configuration which will create entries in VBRK, VBRP, and other SD tables to allow pro-forma document to be printed. These billing types are not included in 2LIS_13_VDITM.

      The ZEF2 is a custom billing type. Without a description, I would not hazard a guess to what it means.

      John Hawk

  • Jan 17 at 08:53 AM

    Hi Loed,

    Proforma invoices can be identified by the document type (VBRK-VBTYP = U).

    In my experience (few years and versions ago) they were extracted by the VDITM.



    Add comment
    10|10000 characters needed characters exceeded