Skip to Content
-4

AMDP database extract returning dubious records.

I have a select query for all entries. I am moving this to AMDP and doing an inner join of VBRP table with the internal table moved. The extract is not the records expected.

Does the AMDP call up a different schema? How do we set default schema when calling AMDP? I am also passing client number. How do we know which schema should the AMDP go to?

Add comment
10|10000 characters needed characters exceeded

  • I really admire your patience ;-)

  • For all entries return 2050 records, AMDP query below gets me 717 records.

    Select <vp.fields>

    From vbrp as vp inner join :intrnal_table as CP on vp.<fields> = cp.<fields>;

    Question again to you is if you know the query kindly share it. As this extracted result is not per extraction from the ABAP for all entries.

  • First, you should give all information about your issue. This forum is not here for writing solutions. It's for answering "why" and "how". I think you've got all the answers from Horst.

Further commenting has been locked.
  • Get RSS Feed

1 Answer

  • Jul 15, 2017 at 10:31 AM

    "Does the AMDP call up a different schema?"

    No.

    "How do we set default schema when calling AMDP?"

    You can't. AMDP only uses the standard connection or a service connection to the ABAP schema.

    "How do we know which schema should the AMDP go to?"

    By reading the documentation.

    This completely answers your three questions.

    If you don't receive the expected results you simply have an error in the implementation that you must correct. First you have to understand the semantics of your FOR ALL ENTRIES then you have to transfer that to SQLScript. Did you bother about DISTINCT?

    Add comment
    10|10000 characters needed characters exceeded

    • Addendum: I realize that the 2 full codes from the ABAP documentation are globally equivalent, but this excerpt is not equivalent. In fact, the DISTINCT used here is from a performance perspective, but what you were looking for is a DISTINCT placed in the first SELECT (in your case: Select DISTINCT <vp.fields>)