Condition table field order

Hello folks,
Is it important to list the fields in a condition table in the proper order ?
I do not think so and like to clarify with you pls.
regards
Ravi

Hi
A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.
Example
Example of a Condition Table
A sales department creates condition records for customer-specific material prices. The standard R/3 System includes condition table 005 for this purpose. The key of table 005 includes the following fields:
Sales organization
Distribution channel
Customer
Material
The first two fields identify important organizational data and the last two fields express the relationship between customers and specific materials. When the sales department creates a condition record for a material price or discount that is specific to one customer, the system automatically uses condition table 005 to define the key and store the record.
AS per SAP Help
regards
Prashanth

Similar Messages

SDIMA: Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ

Hi Experts,
when checking condition records consistency between CRM and ERP via transacation SDIMA we get the following error for one of the conditon records: 'Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ'. Can anybody explain to me where this message could come from? To my understanding field 'SUPP_EXIST' only exists in CRM condition tables for technical reason. So no way to compare this against an ERP condition table field, is there?
And related to this: I found that this error message is triggered from method CL_CND_DIMA_CRM->COMPARE_MBDOC. As the DIMA-Compare is triggered asynchronously and just setting a break-point is no option therefore, I was wondering if anybody knows a way of debugging this method in order to find out what the coding does in detail before the message is thrown.
Thanks a lot for your help!
Cheers,
Jens

Hi Brian and the other Experts,
thanks for your help. Unfortunately, I don't have a single record with this problem but a lot more. So it is not possible to correct this manually. Also, I would not know how to correct this anyhow as I don't understand what field in R/3 should map to field SUPP_EXIST in CRM condition tables. Let me explain:
From my understanding, in CRM (leave aside scales) we have two database tables for each condition table, a central and a supplemental table. A condition record always creates a data record in the central table and nothing is inserted in the supplemental table in case that the fields form the supplemental table are not needed. However, when there are less common condition features involved (e.g. uppler limits), then an additional data record will be created in the supplemental table with the relevant data. And this is when field SUPP_EXIST comes into play as it is an indicator for the system that a data record exists for that condition record also in the supplemental table.
The condition record data model in R/3 is completely different. For CRM condition table CNCCRMPRCUS801 the following tables in R/3 are involved: A801, KONH and KONP. And there is a data record for each of them for a given condition record. There is no concept of having a supplemental table as far as I understand it so where exactly would I find this SUPP_EXIST in R/3 so that I can make sure it does not deviate from the data in CRM?
Would be great if someone could give me another hint. What am I getting wrong?
Cheers,
Jens

Condition Table Link to Condition Types

Please Explain me How it is logical/useful/consistent to assign a particular Condition Table to More than One Condition Types ( Via Access Sequence).

As access sequence is used to find valid data for a particular condition type. It determines the sequence in which the system searches for data, as the accesses tell the system where to look first, second, and so on, until it finds a valid condition record [maintained in condition table fields] for the condition types.
<b>Example:</b>
Condition table 001 is for Sales org/Plant
Access seq A001 is having the following search
Sales Org/Dist channel/division
Sales Org/Plant [001]
Access sequence A002 is having the following search
Sales Org/Dist channel/division
Sales Org/Country
Sales Org/Plant[001]
Sales Org/Sold-to
Now the condition table 001 is defined in access sequence A001 and A002 at different level and these access sequence would be used for different condition types.
The same condition table can be used in different access sequence and at different level also depending on the business need and avoiding repeation of data.
Hope this clear your query, Reward Points if resolution appropriate for you.
Regards,
Gaurav

Condition table for access sequence (taxes calculation procedure)

Hi,
We need to perform tax calculation procedure in which there will be fields in condition table for a particular access sequence such that whenever we give the Country, Region and city in the condition table it will pick up the corresponding tax value.
Condition table field -- KOTABNR.
Path -->
FI -- **** -- Taxes on sales / purchase -- Check calculation procedure -- Access sequences.
Select tax calc say for country US with jurisdiction and check acess sequence. There we have condition table referred to as 53 and we can see the fields by clicking on fields.
How to create a new condition table.
Please guide me through asap.
Thanks and regards,
Priyajit Ghosh

Hi,
This does not allow us to create a new condition table. However we are allowed to change a standard SAP standard condition table. Is there any way to create a new Z table (condition table) . Please revert back asap.
Thanks and regards,
Priyajit

Addition of field to field catalog in order to create condition table

hi,
I need to add field to SAP 5.0 Field Catalog to allow for creation of custom Condition Table. A field named Serial no. profile exists in SAP 4.6c. The equivalent should be added or created in the SAP 5.0 Field Catalog.
How do i do this. Plz help.

Thank you. i've got the solution

What is table field name for order status report of rate per unit and bal

hi i want to make FS for order status report i almost get all table and field but i don't get only two field rate per unit and balance value table field didn't get please help me searching in field and table
i want to develop my status report

Hi,
Check tables VBAK and VBAP wherein you will get all header and item details.
VBUK and VBUP for header and line item statuses.
KONV would give you rates/pricing details for each condition type determines in the sales order.
VBAK-KNUMV = KONV-KNUMV is how you relate both of them.
Hope that helps.
Regards,
Amit

Field catalog not appearing in the condition table for output determination

Hello,
I wanted to include WBSTK as a condition table entry in the output determination for outbound deliveries, WBSTK is available as field catalog , but not available during condition table creation.
Can you pls help me out?
Regards
Vaidee

Check OSS Notes
379619 - Preference process in SD order: Prefrnc ID missing
595984 - Preference indicator in SD order
379269 - Preference in SD doc: User exit: Set pref. indicator PREFE
Regards

Field is missing in Create condition table screen

We are going through one minor issue.We are trying to configure output types for billing docs.I am trying to create a condition table with sold to party field.It is displaying in field catalog,but not displaying in create condition table screen.Any idea how to get it?
Thanks

Hi VCS
As you want to create a condition table at billing level and at billing level for sold to party it is KUNAG where as in sales order level it is KUNNR.
VBRK- KUNAG (SOLD TO PARTY AT BILLING LEVEL )
VBAK- KUNNR (SOLD TO PARTY AT SALES ORDER LEVEL )
so you need to select the sold to party KUNAG and if that sold to party is not available , create that sold to party feild (KUNAG) . and save it
Now when you cerate a condtion table check wheather that cerated feild is there are not . sometimes it will be there and sometimes it wont be there . if that feild is not there then , we need to take the help of ABAPer's and they will copy the standard table into Z table and in that they will write the ALV report or any program . so that it gets triggered in that feild catlog.
example :
KUNAG is availabe in VBRK table
so ABAP'ers will be copying hte standard VBRK table in ZVBRK table and in that ZVBRK table they will write the program where this feild KUNAG is also inserted.
so when you create a condtion table then you can see this KUNAG feild, in the list of feild catlog,if that feild is not there just maintain . the feild. automatically it gets triggered in the feild catlog
Reward if useful
Regards
Srinath

How to find table / field where condition records are saved?

Hi,
We want Sales Order Rate ( Condition type ZR00 calculated with backward pricing ), as a column in a Z report.
I am not able to find out the table / field where system saves condition records for this condition type. I can only see structure.
Please help to trace down the field where this data is stored.
Regards
Trupti

Hi Vishal,
KNUM is the internal number under which system saves the conditions that apply to a Sales Order.
So first to derive this KNUM from sales order we use Table VBAK
AFter this we use this KNUM and the condition type in table KONV to get the value for that perticular condition type.
Please check following.
SE16> VBAK> enter any sales order in field VBELN and note down number in field KNUM.
SE16 --> KONV --> enter this KNUM and the condition type --> you would receive condition record value for this condition type, for that sales order.
KNUMH is a similar field in the table A503( in our case), but we also wanted link of the sales order to this record.
Thanks for your help anyways!!
points provided.

Cannot find a field for creating a condition table

Hi all,
I m trying to create a shipment scenarios which involves shipment cost based on prices,boxes,material....etc. to start with i tried to create a condition table, here the key combination needs to have the filed 'boxes' in it. I am not able to find it even in the master table. Is there any other place whr i can find it or how can i add this into the list?(master table)
any input is highly appreciated.
regards/aryan.

Hi
Try to ad the filed from the field catalog ,In case the required combination field is not there u can add the field through the following process to filed catalog and create the condition table.
It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.
Here Aim giving a simple guide to add fields to the Pricing Field Catalogues:
For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
Reason and Prerequisites
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
Proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component Component type
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.
3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
For header fields, use structure KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.

New Condition table / access not getting picked in purchase order.

I have created a new condition table for the tax to be calculated for Site / Material combination. The access sequence is also crated.
When I created the purchase order the condition / tax is not getting picked. When I checked in the analysis, I found that the error was Access not made (initalize field) for the site. The material is being picked up.
Please note that the site is getting picked from KOMK table ( I think it is a header table), while the site is actually there in the line item level in the po.
Request your help at the earliest.
Regards,
Veena.

TCODE OBQ2
Select the tax access sequence. Click on accesses. Tick the right combination required site / article . then click on the fields tab. This will take you to the next screen. There click on the field for which you want to change the selection table and then click on field catalog at the bottom of the screen.
This will take you to the field catalog screen. there select the table and field and then save.
With this procedure you can select the required field into KOMK OR KOMP.
Regards,
Veena.

Add fields in fieldctlg in Create condition table in SPRO

Hi Experts,
How can we add more fields in fieldCatlg table which appears in 'Create Condition Table' in Sales Distribution head in SPRO.
Please Suggest.
Rajiv Ranjan

Hi Rajiv
Please go through this extract from documentation:
Creating New Data Fields in a Communication Structure
Data fields are created in the Data Dictionary. You create data elements and fields in the Data Dictionary as well as integrate them in the relevant structures. Use following check list when you create new data fields:
1. Check whether an identical data field already exists in the standard system
If you want to use the order reason (AUGRU) for pricing, for example,
the data element already exists.
If you want to use parts of the product hierarchy, for example, you must create a new data element (e.g. ZZPRODH1).
Remember that new data fields must begin with the letter "ZZ" or "YY" because SAP has selected this name convention to protect modifications of the customer during a release changeover. Create a new domain for the new data element.
If you want to use a new partner function, such as a selling agent (Z1) you have to create a new partner function (Z1) and a new data element (ZZVRTZ1) in Customizing.
2. Using the source tables, check wether the field is used at header or at item level, which determines the structure in which the field is included. The source tables are listed in the section "Supplying Fields Within the Communication Structure and Using Them in Condition Tables" below.
The order reason, for example, is included in table VBAK, the product hierarchy in table VBAP.
3. Integrate the field in the appropriate communication structure by means of an INCLUDE.
For pricing, for example, you include header fields in KOMKAZ, item fields in KOMPAZ: For the field name enter the field description new fields and make sure that they begin with ZZ or YY. For example, enter ZZAUGRU, ZZPRODH, and ZZVRTZ1 and assign them to the SAP data element AUGRU, or the new data elements you have just created ZZPRODH1 and ZZVRTZ1.
The description of the individual functions will inform you about the structures into which the fields must be integrated.
4. Activate the structure.
5. Include a new field in table T681 and allocate it to the application in which is to be used.
Example
A new field for pricing, has the allocation A, V, 001.
When you have succesfully added the new fields in the communication structure, you will be able to find the same in FIELD CATALOG under the acess squences definition. Please check the same...
Regards
Eswar

Adding SERVICE_ORG_RESP_SHORT field to Condition Table

Dear Experts!
We want to use the SERVICE_ORG_RESP_SHORT field in our Condition Table to define product Pricing. The problem is it doesn't exist in a Field Catalog (SPRO -> CRM -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Field Catalog).
We see two possible ways of dealing with this issue:
1) Adding SERVICE_ORG_RESP_SHORT field into Global Field Catalog (SPRO -> CRM -> Master Data Conditions and Condition Technique -> Condition Technique: Basics -> System Configuration for Condition Technique -> Set Up Usage -> folders "Global Field Catalog: Fields" and "Global Field Catalog: Data Elements").
2) Using BAdI (SPRO -> CRM -> Basic Functions -> Pricing -> Define Settings for Pricing -> Adopt User-Defined Fields).
Please, tell us, which of these ways is correct?
Kind Regards,
Alexander Smirnyagin.

Hi Alexandr,
the first step mentioned above is required to define the field, so that you can use it to create a conditon table based on it and maintain master data for that condition table. In addition, you should implement the /SAPCND/ROLLNAME BADI for the field.
The second step described above is required to integrate the field for transaction processing, e.g. in a sales or service order. You need to define which order value should get passed to your pricing attribute.
Best Regards,
Michael

Fields in Field Catalog not available when creating condition table

I see that field HIEBO01 to HIEBO12 are available in Field Catalog, but I don't see these fields when creating condition table
Please let me know what I am missing here.
Any insight on this would be really helpful. Thanks guys!

you need to get them added to the pricing structure KOMKAZ or KOMPAZ based on whether you need @ header level or @ item level respectively.
and then add the logic in the sales order user exit for these added field in the pricing_prepare_TKOMK or pricing_prepare_TKOMP...again based on header level or item level.....
Then go back to the field catalog and select from the respective structure and add them, Then you can see them when creating cond tables.
Hope this helps. Hope i havent misunderstood your query.,
Regards
Sai

Pricing condition tables for Sales Order

Hi experts,
please can you tell me the code I have to write into a query's field to retrive the value of a specific header pricing condition saved into a Sales Order?
Thank you very much
Kind Regards
Andrea

1) From sale order header table VBAK fetch the condition number KNUMV for a particular sale order VBELN.
2) From conditions table KONV fetch the conditions for condition number KNUMV with item number POSNR as 000000.
This way you can fetch the header conditions. Our ABAPers normally do a loop on the line items and total up the values to arrive at the header condition value. If you use this way then you need to pass another field condition origin KHERK with value D while fetching data from KONV.
Regards,
GSL.

Condition table field order

Similar Messages

Maybe you are looking for