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.
Example:
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

Similar Messages

Sales Order Unable to Use New Condition Tables for Tax Condition Type

Dear All,
I am currently working on SAP R/3 4.0. I have a new requirement for my tax where I need to create new condition tables other than the 4 standard SAP tables which are Customer/Material, Division/Customer, Departure Country/Destination Country, Domestic Taxes and Export Taxes. My new tables consists of Departure Country/Destination Country/Shipping Point/Tax Code. The requirement is that the tax code is based on the chosen destination country and shipping point. The problem I am facing now is that no matter what types of table I create or even I generate with reference to the standard table, the access sequence will only refer to the 4 standard SAP tables above. Even if I put my own table in the highest priority for the access sequence, the same thing happens. My sales order will only pick up date from the standard table.
I wonder if anyone encountered the same problem as me.
Kindly advise.
Thank you.
Regards,
Yvonne

Hi
Yvonne
I suggest fist check a simple thing ,whether u have successfully determined shipping point for each line item ,it is possible that just adding a line item will not trigger shipping point determination . So after u update the shipping point on line level u can rerun pricing and check agian if u r getting it .
Secondly for tax purposes I suggest Try to have Customer and material tax classification approach this allows to u have long term flexibiliy and also reduces your maintenance activity . As if u change or add number of shipping points and business changes using the sequence of shipping point ,the logic of just using shipping point will not work.
In Tax classification u cna add new condition table for each new tax category and use it in different access sequences.
This information can be passed on to FI using Different Tax code for Different combination.
I hope this helps
Regards
Mandar

Redetermination of condition table for a condition type

Hai Friends,
I have a quiery regarding condition table redetermination from order to delivery.I have pricing procedure in which "ZMRP" is the mrp price for calculating other condition types.Here i have scenario While raising sales order ZMRP condition type is determining with the combination of "Distribution channel and material".But when it comes to delivery i want that(i.e.,ZMRP condition type) to determine with the combination of "Material and batch".How to do this
Thanks & Regards,
A.sudhakar

Hello Sudhakar,
As said above the pricing procedure for order and delivery documents are different, adding to that we can't transfer the condition value from order to delivery document and nor we use same pricing procedure in delivery document.
Order pricing procedure- calculates the prices for the material (price + tax - deduction)
Delivery pricing procedure - Calculates the prices for feright charges or postage charges.
the values for conditions in the billing document can flow from both order and delivery based on the copy control table.
price tax and deduction comes from order and feright comes from delivery document.
Note: we don't use delivery document pricing procedure to calculate the price i.e ZMRP in your case for the material.
Hopes this helps
Regards
Naveen K.

Condition Tables and Condition Types

Hello,
I need to Define the condition tables, Access Sequence,Condition types.I need steps to do this in COPA under master data/valution/Define Condition and costing sheets.Please let me know how i do it or any info regarding this.
Nettem

Hi Sekhar
Check the config in M/06 for condition types.
Condition types are pricing elements (Price, discount, freight, insurance etc).
Some condition types have access sequence assigned to them (check in M/06). Access sequence facilitates users to maintain condition masters (check Txn MEK1) from which condition types&rates can be defaulted in 'conditions' screen in PO.
Condition tables (Txn M/05) are used in Acces Sequence (check the settings in M/07). They contain the key fields for which condition master(Txn MEK1) can be maintained.
Pl go through this link to know more:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/75/ee12b855c811d189900000e8322d00/frameset.htm
Best regards
Ramki

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.

Ouput determination for sales documents - Condition table

Hello All,
In the condition table I currently have the following fields - Sales org/Dist channel/Sales doc type/Order reason/User.
The field User is Created By VBAK-ERNAM. I want to change this to display the name of theperson that last modified the document. What field is this? CDHDR-USERNAME maybe?
And more importantly how do I go about making the change?
Would you recommend creating a new condition table?
Thanks in advance,
Suhas

Hi ,KIndly do the below settings
1.Delete the condition table from the access sequence :
SPRO-IMG-Sales &dist->Basic functions->Output Control>Out put determinationMaintain Output detrmination for sales documents---Maintain Access sequence
2.Then go to the condition table and delte the ERNAM and add the AENAM and generate .
SPRO-IMG-Sales &dist->Basic functions->Output Control>Out put determinationMaintain Output detrmination for sales documents---maintain condition table
3.Same condition table assign to the access sequence then access sequence will be assigned to out put type condition type
SPRO-IMG-Sales &dist->Basic functions->Output Control>Out put determinationMaintain Output detrmination for sales documents---Maintain output types.
4.Assign the out put type to the partner function
SPRO-IMG-Sales &dist->Basic functions->Output Control>Out put determinationMaintain Output detrmination for sales documents---Assign Output type to partner functions
5.Maintain the Out put type in out put determination procedure
SPRO-IMG-Sales &dist->Basic functions->Output Control>Out put determinationMaintain Output detrmination for sales documents---Maintain Output determination procedures
6.Assign out put determination procedure to the sales document type and item categoiry
SPRO-IMG-Sales &dist->Basic functions->Output Control>Out put determinationMaintain Output detrmination for sales documents---Assign Output determination procedures
OR
Delete the old condition table and create the new condition table and assigned to new access sequence.
REgards
Damu

New field creation in Condition Table?

Hi Gurus
I want to know whether it is possible to add a new field in field catalogue whle creating a condition table. I want to add Chapter Id of the material.
Thanks
Rishi

Hi Rishi,
Follow below example-
Add a Field To New Condition Table in Pricing
Add a field to a new condition table in Pricing (Condition Technique):-
I will explain you the process with below example...Please follow steps in below sequence-
Try to add the filed from the field catalog. In case the required combination field is not there, you 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 I'm 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.
Regds
MM

Return item (RETPO) as a key field in condition table

Hi,
I would like to know how we can utilize return item indicator as one of the key fields in the PO pricing condition table.
[Requirement]
Condition record
Use Retrun item as a key
e.g.) Table A999: POrg | Vendor | Return item | condition rate
#1: 1000 | M123456789 |blank | 3%
PO pricing
If the PO item is NOT marked as return, #1 should be applied to that item.
If the PO item is marked as return, no condition record should be determined.
[Question]
Though I've configured as above, return item indicator seems to be ignored.
When I tick the initial indicator in access sequence, the condition rate is always applied to the PO item for both with and without return item indicator.
When I tick-off the initial indicator in access sequence, the condition rate is not applied to the PO item for both with and without return item indicator.
Why does it happen?
Is it possible to apply the condition record only to the PO without return item?
I'd like to know how to make it effective in the condition table, RETPO=blank.
As long as searched, I couldn't find any similar question.
Your help would be much appliciated.
Best Regards,
Mari

Hi Manosij,
Thank you for your reply.
I've already done as your instruction.
However, the result is not what I'm expecting.
I believe I'm right to creating the condition table.
But I think something wrrong in access sequence...
Though I do as your instruction, creating the condition record in MEK1 only for blank one, the record is applied to those with X when creating PO.
If you have another clue on my question, it would be much appreciated.
Best Regards,
Mari

HOW TO DELETE A CONDITION TABLE??

HI
DOES ANYONE KNOWS HOW TO DELETE CONDITION TABLE?
THANKS

Vikas,
Do you want to delete a pricing condition table?
T-Code: V/04
In Change Mode, enter the condition table number and press enter. You can delete the condition table using menu Condition>Delete
If this condition table is part of a access sequence then you have to remove the table from the access sequence and then delete the table using the steps above.
Chandan

Create condition table

Can anybody explain how to create a condition table in a detailed manner step by step?
Thanks in advance for the answers.

HI
You can change and maintain the condition tables in the standard system. You can also create new condition tables to meet the needs of your own organization. You create and maintain condition tables in Customizing.
From the initial screen of Customizing for Sales and Distribution, you reach the condition table screens by choosing Basic functions --> Pricing -->Pricing Control -->Define condition tables. Then select the mode you want to work with (create, change, display).
ou can create new condition tables to meet the pricing needs of your organization. When you create a new condition table, you select a combination of fields from the list of allowed fields. The selected fields define the key for the subsequent condition records.
Before you select the fields for the key, there are two things to consider:
The sequence (or hierarchy) of the fields
Which fields you want to appear in the header and item areas of the corresponding fast-entry screens
Important Fields
In sales, the fields you should take into consideration are Sales organization and Distribution channel. The sales organization is nearly always used as a criteria in pricing, because different sales organizations often want to use their own prices, discounts, and surcharges. If you use the sales organization as a criterion in pricing, you should also use the distribution channel. If you do not want to establish different prices, discounts, and surcharges for each distribution channel, use the field anyway. In Customizing for Sales, you can use one distribution channel as a reference for all others (thereby sharing the same pricing data).
Deciding the Sequence of Fields
The order of the fields in a condition table affects the performance of the system during pricing. Two general guidelines will help you create an efficient condition table:
1. If you select fields that are connected to the structure of your organization (for example, sales organization and distribution channel), assign the fields according to the level of general applicability: Put the most general field, for example, the sales organization in the highest position and the most specific field in the lowest.
2. After organizational fields, place fields from the document header before those that come from the item level. (For example, Customer comes before Material)
After you have selected the fields for the key on the screen where you maintain and define condition tables, choose F16 Generate to generate the table in the system. Generation prepares the condition table for storing condition data.

Creation of New Table for Delivery Output Type.

Hi Guys,
I need to replace an existing table by creating a new Table in the existing Access Sequence with the combination of "Ship to Party/Product Hierarchy".
Logistics>Shipping>basic Shipping functions>Output determination>Maintain Condition Tables-->maintain output condition table for deliveries.
I am choosing a new table by the name 902, but i am not getting the field " PRODH Product Hierarchy" on the right hand side to choose from.
I checked the field catelog also. Firstly the field catelog was also not having the field, and then i added the field in it by choosing new entries.
I guess i am missing some step in between, thats why the new field (PRODH) is not showing on the right hand side while creation of the condition table.
One more thing, when i am seeing the Field Catelog, i am able to see a very large number of fields, then why only a few are appearing during creation of a new table??????
Can you guys correct me and let me find a way.????
Thanks very much indeed.
Regards,
Vivek

Hi If u have already the field in FC u can add with new entries .
Try with ,enter t- code SE11, enter KOMB- it will ask for access key get from basis and add u r Field catalog
Field catalog for condition key: output determination
If at all u want a new field tao add to u r FC u Can try with userexit.
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields.
 The fields which are not in either of the two tables KOMK and KOMP
cannot be used in pricing .Sometimes a need arises when the pricing
is to be based on some other criteria which is not present in the form of fields in either of the two tables.
This problem can be solved by using USEREXITS which are provided for pricing in SD.
Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP
program SAPMV45A. The name of the userexits are same. i.e
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely
created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that
has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose
includes are provided in each of them .
To create the field in header data(KOMK) the include provided is KOMKAZ
and to create the field in item data(KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2)The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
Message was edited by:
 SHESAGIRI GEDILA

Table links from Purchase order to condition types

Hi,
I am looking for the tables to go from purchase order, and to read the conditions associated with the PO.
I have EKKO, and EKPO, but I cannot find the table where the condition information is stored. I have KONV and KONP, but they seem to be the tables where the condition type info is stored, not the link table where the purchase order specific information is stored.
Can somebody please point in the right direction?
Regards
Piet
Edited by: Piet Strydom on May 12, 2009 12:52 PM

Hi,
The PO and the Condition Record Number Link happens in the Table EKKI.
from this table get the condition Record number line item wise and execute in KONV.
Hope so it helps
Regards
Anjanna
you can check the below thread posted by self for further ing
Re: PO item Condition Record number and delivery address of PO - Need a table n
Edited by: Shiva Rajanala on May 12, 2009 1:42 PM

Pricing condition table and condition type question

hi guys,
We can use same condition table in pricing for multiple condition types.I am wondering how system knows which condition records should be applicable for which condition type in the same table.
I know the structure KOMV has those details,but thats used during the run time.
Do we have database table which preserve this relation /link ? Please help.
I also would like to know the tables / fields /structures which can be used at run time for defining requirements in pricing procedures.
Thanks
Dona

Hi,
Condition types are assigned with access sequences.
These are the determining sequences in order to select which condition table is to be selected for that particular scenario.
Generally the access sequences are tested to the condition records on their priority basis.
pricing procedure
condition type
access sequence
condition table
selection records.
hope this would help you understand the concept.
regards,
Siddharth.

Table name for condition type

Hi,
Could any one please tell me in which table name the Condition type values are saved and how to retrieve it.
Reg,
Ashok

Hi Blue,
I checked with SE16 by giving KONP table name. But its showing wrong value.
The condition type value is 14.000but its showing the value for 7.60.
Reg,
Ashok

Wrong condition table for condition type

Hi,
I have a big problem during pricing. while creating the sales order the system takes the wrong condition table for the specified condition type (I have created a new condition table and changed the access seq, did the initial load and in customizing everything looks fine). To picture the customing i have created ZXXX access seq with a 901 cindition table (sales org, dist ch. and product hierarchy 2 with a standard field PRODH2) unfortunately I had to change the field to ZPRODH2 I decided to create a new table 902 with the Z field. The new access seq has now 902 table in customizing. In CRM the two condition tables and view exists for 901 and 902. Acording to customizing the system should take the 902 condition table but insteed he takes the old 901 which shouldn't be used.
Do anybody has some ideas why the system responds like that ? I have tried to delete the old table with the standard report and it didn't worked.
What can I do ?
Thanks for some ideas !!
BR
Tomasz

Hi Tomasz
Please check assignment of that new access seq to c.type in v/06
That table might hv used somewhere in another acc.seq so unable to delelte
Regards
Sachin

Condition Table Link to Condition Types

Similar Messages

Maybe you are looking for