Skip to Content
author's profile photo Former Member
Former Member

Recs in DSO, but not in source table in R/3

Hi Gurus,

We have a few records in sales DSO(which is fed by 2lis_11_vaitm std d/s) which dont exist in the source table of VBAK/VBAP table in R/3 nor can i see in Rsa3. I need to reconcile between BW & R/3, but am unable to figure out how these recs hav landed in BW!

Pl suggest any way how can i figure it out?

Thanks in advance,

Vandana.

Add a comment
10|10000 characters needed characters exceeded

Related questions

7 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2013 at 09:50 AM

    Hi Vandhana,

    Check in CDHDR/CDPOS table for the Sales Order change history in ECC system, this might help you in finding the status of the SO.

    Regards,

    Raghu


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 27, 2013 at 07:23 AM

    Hi,

    May be its dummy record and deleted at ecc side.

    As my guess above data source have a field created date or created by.

    form bw data,find those details and check with that user id(created by) or take SD consultant help and track that record.

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2013 at 07:41 AM

    Hi,

    Those sales orders might be deleted at ECC, hence we cann't see in ECC.

    In BI, It flows both creation image and deletion image also. That means we'll have two transactional records one with positive value and other with -ve values.

    At reporting level we can see orders with no key figure values.

    Regards,

    Madhavi.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 27, 2013 at 07:24 AM

    Hi,

    Please check whether any logic at transformation level.

    Regards,

    Madhu

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2013 at 07:34 AM

    Hi Vandana,

    Please check the data at PSA level. PSA is resemble of Datasource.

    After that only you need to check the upper layers.

    Thanks,

    Purushotham.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2013 at 10:07 AM

    Hi Vandana,

    Option 1:

    RSA3 will show the data from the set up tables.

    Were those documents present when the set up tables were filled?

    If they were created during the delta loads were going on , you should have got them in the delta...

    Option 2:

    If you are not able to see those documents in RSA3 it means that they don't exist in the set up tables...

    I don't understand how you missed those documents when you say your deltas were happening daily...

    Someone deleted the extraction queue or may be some other reason....

    Follow the below steps...

    1. Run V3 update and empty LBWQ

    2. Load delta in BI so that no data is present in RSA7

    3. Delete and refill the set up tables

    4. you will have to take down time from the time till you fill the set up tables and make an init in BI

    5. Do a full repair in the DSO

    6. then init without data transfer and then again continue the deltas

    Regards,

    Baskaran

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2013 at 10:25 AM

    Vandana,

    Try this.

    In CDPOS table put VERKBELEG for "Change doc. object" and VA02 for "Transaction Code" and SO Number of the deleted SO in "Object value". You will get Date & Time of Deletion.

    Give OBJECTCLAS = VERKBELEG and CHNGIND = 'D' in CDPOS table.

    Also you can view change log of deleted Sales Order by using program RVSCD100

    Regards,

    S.Venkatesh Babu

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.