2LIS_13_VDKON and agreements (datasource field KNUMA_BO)

[Former Member]

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

[Colin4]

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.

[Former Member]

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.

[former_member224224]

Did anyone find a solution to this issue?

To add further complexity I have actually filled the setup tables with a document range and done a Repair Full Request thus allowing my deltas to continue, I have had delta loads since my setup table fill and Full Repair that have values for KNUMA_BO, yet no values for the full load. I look in RSA3, no values for any of the records, I look in KONP and can see values for certain conditions that have been extracted, and of course no values coming across into the BW.

Did anyone manage to progress this at all, I don't want to change the extractor via user exit as my deltas are working fine and I would prefer to leave well alone.

Thanks in advance.

Brendan.

[Former Member]

Hello,

Were you able to resolve this ?

Thanks,

VSK

[former_member186445]

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

[Former Member]

Hello BI-Experts!

Thanks for your fast replies!

I also thought about filling the field via customer exit. But in my opinion this should not be necessary for fields which are already offered in business content and can be selected in the standard datasource. This should be only the last option as workaround. The field should be filled by standard business content.

In our data model neither the flag <i>"Hide field"</i> nor the flag <i>"Field only known in customer exit"</i> is marked.

Therefore the field should be filled when checking in Extractor-Checker (transaction RSA3). But the according agreement numbers are still not populated into this field.

Is there anybody around who asked SAP via OSS-message and already received a solution to solve this problem?

Kind regards,

Richard

[former_member186445]

just to make sure...

did you delete and filled again the setup tables after your changes?

[Former Member]

Yes, for checking purposes I deleted content of setup tables of appl. 13 and filled it again with example billing documents, which contain condition records having agreement numbers.

When checking in RSA3 condition records are listed in result but agreement field is always empty.

[former_member186445]

did you take a look at oss notes 387625 and 1062462

[Former Member]

Yes, I checked these notes, <b>BUT</b>:

OSS-note <b>387625</b> is not relevant due to the fact, that 387625 was released 04.11.2001, i.e. at a point of time when no standard extractor was supported by SAP to extract conditions. But 2LIS_13_VDKON is now a new datasource which was just created for this purpose: <b><u>to extract conditions records of billing documents</u></b>.

OSS-note <b>1062462</b> points out, that only active conditions will be extracted, i.e. conditions having KONV-KINAK = initial. But this is indeed true for all the relevant condition records, which I would like to extract in my data model (otherwise I also would not see the corresponding entry of the relevant condition type and record in RSA3).

Message was edited by:

Richard Peter

[former_member186445]

then i'm afraid i can't help you anymore. this ds is not used in our system so i can't compare your situation with ours. you could try to run the setup program (for one billing doc) in debug mode and try to find out why the knuma_bo field is not transferred to the structure.

sorry

[Former Member]

Dear Mti, thanks anyway!

[Former Member]

Hi Richard,

We do have the same issue. Can you please let me know if you were able to resolve this.

Appreciate your help.

Thank you,

PVK

[Former Member]

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