Select language:

Inbound Processing 

What can be Processed?

  • Prices and conditions (master conditions)
  • Axxx Condition table

    Client + Application + Condition type + VAKEY + Valid_to

    Konh Condition header

    Client + Condition record number (knumh)

    Konp Condition item

    Client + Knumh + current number

    • Condition supplements (Purchasing and Sales and Distribution)

    Konp Condition item

    • Scales

    Konm Quantity scale

    Client + knumh + current number + current no. scale

    Konw Value scale

    Client + knumh + current number + current no. scale

    for purchasing info records

    • Document-related conditions

    for contracts

    for purchasing rebate agreements (and the period condition records)

    no other agreements

    Processing module

    • The inbound processing module IDOC_INPUT_COND_A is assigned to the Idoc type COND_A01.
    • The Idoc data is read, checked, formatted and transferred to the SD standard function module RV_CONDITION_COPY.
    • Transfer to dialog module RV_CONDITION_MAINTENANCE
    • Preparation of the data; for example, adapting time periods and posting condition records with RV_CONDITION_SAVE to the database
      • IDoc_Input_Cond_A carries out the same checks that the condition installation carries out per dialog before transferring further to Rv_Condition_Copy. This means that only syntactically correct condition records make it into posting.
      • Incorrect records remain in Idoc inbound processing and list all of the errors that have occurred in their logs.
      • In the target system new conditions records are always created, this means that a new condition record number is always assigned.
      • If there are time gaps due to condition changes remaining in the source system, these do not always exist in the target system.
      • Time links via the condition record number get lost
      • The maintenance of conditions can not be split up, for example, prices in the source system and scales in the target system.
      • When sending with change documents all validity periods concerned >= today’s date are sent for each condition record number (Consistency)

      Gaps in the target system:

      Source system: 1.) AAAAABBBBBCCCCC

      2.) AAAAA BBBCCCCC abbreviation of BBBBB

      3.) sent from BBB

      4.) AAAAA BBBCCCCC current status of the DB

      Target system: 1.) DDDDDKKKKKEEEEE identical to source

      2.) Initial data creation of BBB

      3.) DDDDDKKBBBEEEEE a part of KKKKK remains

      New condition record number:

      Source system 1.)AAAAABBBBBAAAAA AAAAA has the same Knumh

      2.) complete dispatch

      Target system 1.) DDDDDKKKKKEEEEE each with different Knumh