Skip to Content
Author's profile photo Former Member

Quick and Easy – EDI/ALE – Pricing Condition Records


So you know that SAP can send pricing condition records from your SAP system to another system using ALE/EDI. An investigation of transaction WE60 can show you the structure of the Basic Type “COND_A03”.

But what is the easiest method of sending the initial data load from SAP to another system for pricing condition records, or how do you use it?

Did you know?

An awesome transaction code in SAP related to EDI is WEDI. Use it and take a look around. Another great one is BALE.

Background 1

Presumption that the standard SAP IDoc structure and function module used to populate the data structure is acceptable for your needs. If not refer to a more advanced tutorial on IDoc structure adaption/creation. We will use standard Structure COND_A03 which uses message type COND_A.

Background 2

We now need to get the condition records placed into an IDoc and sent from our system. You may know if you use ALE the awesome transaction code BALM, this will give you access to nearly all master data distribution menu paths. But when sending purely condition records there is a easy technique to follow:

Step 1

Use transaction code VK13.

Enter the condition type for which you wish to send the data.

Step 2

Select the button “Condition Information”.

Step 3

Enter the selection parameters to narrow down the results.

Step 4

You will now see an overview of the condition records in a list format per condition table.

Select the records using the checkbox on the left hand side.

Step 5

Select the button “Send Condition”.

A dialog box will appear in which you may enter the:

– Message Type – COND_A

– Logical System – xyz.

Where xyz is the logical system partner as defined in WE20.


The system will now show you how many “Master IDocs” were created and how many “Communication IDocs” were created. You may view them in WE02.

Did you know?

A communication IDoc is an IDoc which has been created and can be located in WE02. The filter settings in the distribution model transaction BD64 (another Quick & Easy topic) may prevent the combination of receiver system and message type from creating the IDoc.

Did you know?

You can automatically send the condition records you create/change from your system using change pointers. (another Quick & Easy topic). But we save that for another day.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Manish Malakar
      Manish Malakar


      Thanks for the steps. However, can you please tell me in which tables all this data gets stored ? Is it just the KONV table or are there other tables involved ?