Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Rebate Agreement Upload: Condition data

Former Member
0 Likes
1,050

Hello Gurus,

My client system is undergoin SAP to SAP implementation, which requires conversion of all the Rebate Agreements. We are providing the SAP table data extracts to the technical team for the conversion.

The conditions for the Rebate agreements are stored both in condition table KONH/ KONP and Condition table for Rebate: KOTE001. What is the significance and difference between data in the two tables??

Is it possible that data in KOTE001 is sent along with general rebate agreement data and KONH KONP data is later migrated while doing Sales Pricing conversion..

Please advise. Reward pts for useful answers.

Thanks, C Mehra.

Hello Gurus,

My client system is undergoin SAP to SAP implementation, which requires conversion of all the Rebate Agreements. We are providing the SAP table data extracts to the technical team for the conversion.

The conditions for the Rebate agreements are stored both in condition table KONH/ KONP and Condition table for Rebate: KOTE001. What is the significance and difference between data in the two tables??

Is it possible that data in KOTE001 is sent along with general rebate agreement data and KONH KONP data is later migrated while doing Sales Pricing conversion..

Please advise. Reward pts for useful answers.

Thanks, C Mehra.

2 REPLIES 2
Read only

Former Member
0 Likes
720

I am facing the same problem.

I am creating rebate agreements using the FM:MM_ARRANG_NEW_ARRANG_INSERT. This FM successfully inserts the records into all the related tables

KONA - Rebate agreements

KONH - Conditions header

KONP - Conditions item

I am able to view the rebate in VBO3 tcode, but I am not able to view the related conditions. It is just because the relation b/w KONA and Conditions [ KONH/KONP] happens in KOTE001. This entry is missing. In development I forced the entry into the table and then it started working.

Can anyone guide me on how to create the relevant entries in the table KOTE001 using a FM or some standard means?

Read only

0 Likes
720

This is how I bridged the gap. May not be best solution intown but this meets the requirement.

I created a implicit enhancement on the FM:MM_ARRANG_NEW_ARRANG_INSERT and added the following code.

Logical Position:    \FU:MM_ARRANG_NEW_ARRANG_INSERT\SE:END\


*

CONSTANTS:

     lc_action  TYPE c VALUE 'I' .


DATA:

     lv_subrc   TYPE sy-subrc .


** Core logic

IF sy-subrc EQ 0 .


**  Insert the records to the table KOTE001

  PERFORM db_update IN PROGRAM rv13e001

        TABLES t_new_vakedb

        USING lc_action lv_subrc .


  IF lv_subrc NE 0.

    sy-subrc = lv_subrc .


  ENDIF.

ENDIF.