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

2LIS_13_VDKON and agreements (datasource field KNUMA_BO)

Hallo BW-Gurus!

We are using datasource <b>2LIS_13_VDKON</b> to extract SD Billing document conditions into BW. In addition we need to get the <b>agreement no.</b> of a condition if there are any rebate agreements to any conditions.

Therefore we wanted to use the field <b>KNUMA_BO</b>, which is available in the standard extractor, to extract agreement-no.s of billing conditions.

Unfortunately when extracting condition records the field agreement-no. (KNUMA_BO) of the datasource 2LIS_13_VDKON is still empty although the according billing condition of a certain billing document contains agreement information.

Does anybody of you faced the same problem?

If so, how did you solve this issue? Filling KNUMA_BO via user-exit?

Kind regards,

Richard

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 26, 2007 at 11:02 AM

    Hi,

    If extracting condition records the field agreement-no. (KNUMA_BO) of the datasource 2LIS_13_VDKON is not populated then go for user exit.

    Add the field to the extractor structure and in the exit code as follows:

    Secet the KNUMA_BO field from the <TABLE>

    and populate that field using ABAP code.

    Thanks,

    Debasish

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 26, 2007 at 11:05 AM

    did you check in the datasource if the new field is flagged 'only known in user-exit'? if yes, delete the flag

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2008 at 06:01 AM

    Hi Richard, Also have the same problem with 2LIS_13_VDKON not populating KNUMA_BO, have you found a solution ? It should not be necessary to enhance via customer exit but it may work as a last resort. The alternative I am considering is to write a customised extractor (function module) from scratch.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 26, 2015 at 02:38 PM

    The solution to this issue is in the below note:

    1077169 - 2LIS_13_VDKON: Field KNUMA_BO is not filled

    • Add the following source code lines to EXIT_SAPLRSAP_001:

    *-------------------------------------------------------*
    *
    INCLUDE ZXRSAU01
    *
    *-------------------------------------------------------*

    CASE
    i_datasource.
    WHEN '2LIS_13_VDKON'.
    TABLES: konp.
    DATA: wa_mc13vd0kon
    TYPE mc13vd0kon.

    LOOP AT c_t_data INTO wa_mc13vd0kon.
    IF
    wa_mc13vd0kon-koaid = 'C'.
    l_tabix = sy-tabix.

    SELECT
    SINGLE knuma_bo INTO wa_mc13vd0kon-knuma_bo
    FROM konp WHERE
    knumh = wa_mc13vd0kon-knumh
    AND kopos =
    '01'
    AND kschl =
    wa_mc13vd0kon-kschl.
    IF sy-subrc = 0.
    MODIFY c_t_data
    FROM wa_mc13vd0kon INDEX
    l_tabix..
    ENDIF.
    ENDIF.

    ENDLOOP.
    WHEN
    OTHERS.
    EXIT.
    ENDCASE.

    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.