Creation of condition table without copy

During creation of Condition table ( without copying any condition from available tables), Is it possible to see all field catalouges available? and if possible then how can we see all fields available to add desired ones into our table?

Hi,
SPRO >Sales and Distribution->Basic Functions>Pricing>Pricing Control-->Define Condition Tables
In the above menu path you can find out the Field catalog what SAP has given if you want to add new field you can add provided
If you done the Enhancements
Regards,
Prasanna

Similar Messages

Creation of Condition table & assigning in Key Combination(FV11)

Dear all,
I have created a new Condition table(M/03) for Plant/Vendor Code/Tax code/Material,and i am getting the condition table in the key combination in FV11,and maintained,getting the values in the condition table.But my problem is i am not getting the maintained values in my Purchase Order.Please give any suggestions to solve this problem
Regards,
PR

To get the values in PO, maintain the condition records in MEK1.
FV11 is for tax calculation conditions
Regards

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

Activate Release Status in condition table

HI,
Some has created a pricing condition table and it is being used since 5 years.
Now client had a requirement where he wants release mechanism for any new condition records created.
For this SAP provided a standard functionality of release status.
In our case release status button is not checked while creation of condition table.
Now how to reactivate the release button in the condition table.
Regards,

Hi Uday
We can't activate release function in old tables just like that. You have to create new table with same fields but with release status activate. For copying old condition records in this new table you can use
SD_MOVE_A004_TO_A304 report. As you can see with its name this report is for tables 004 and 304. If you want to copy records from 004 to 304 you can use this report. In your case you must have some other tables but if you show this report to your ABAPer he would be able to generate a new report using your tables.
You can take a look on following document provided by SAP and see the conversion section at the end of this document.
http://help.sap.com/saphelp_46c/helpdata/en/9b/3b1a2bc925d311b60f0060b03c2bff/content.htm
Thank$

Condition table missing: Access JST1 60 (Pricing Taxes)

Dear All,
We had gone for the updation of patches related to 2007-08 budget changes. Our SAP version is 4.7EE.
We are getting the below message, when giving the tax code in purchase order creation.
"Condition table missing: Access JST1 60 (Pricing Taxes)"
TAXINJ is being used.
Please provide a solution on this issue.
Regards,
Venkat.

check all the condition type and there access sequences

When I copy and paste a chapter from MS Word into Pages my tables and equations are trashed. But importing them results in no control over my template How do I get my chapter into my template without copying

When I copy and paste a chapter from MS Word into Pages my tables and equations are trashed. But importing them results in no control over my template How do I get my chapter into my template without copying?

Try just Opening the Word .doc from within Pages and see if that gets closer to what you want, then copy the chapter you want from the Pages version.
Peter

Creation of output condition table

Dear Experts,
I am trying to use V/57 for creation of new condition tables for sales documents output. I am not finding the new tables creation option here.
Can you please guide me as to how new tables can be created for output determination ?
Best Regards,
Kumar

Hi,
You are correct, in V/57 Initial screen shows only change Condition table
From the menu, select Condition> Create
Then you can create condition table.
Regards,
Sharan

Creation of Customized field for Pricing Condition tables

Hi Friends
I have a requirement to create a Pricing condition table with Customized field starts with 'Z' and
Field length should be more than 80.
After creating New Customized Field, system is not allowing to create Pricing Condition table and giving error 'Too Many fields selected (larger than 100 bytes)'.
Could you please advice how to over come this error and Maximum field to create Pricing condition table .
Thanks
Ravi

Hi there,
Table & table attributes are defined by the ABAPers. Not by finctional consultants.
You need to have an access key to define new tables & access sequence.
Check with your ABAPer. He will be able to help you with that.
Regards,
Sivanand

Condition table creation in pricing procedure

Dear Sir ,
I have some queries relating to Condition table used in aceess sequence in pricing procedure .
Whether a ne w condition table is transportable from DEV to Production server or not . OR it is to be directly created in Production server .
thanks & regards
Shailendra

For access sequence Workbech request is created. If you want to transport in developenment server from one client to another then their is no need to transport as these comes under cross client. And if you want to transport it to quality server or production server then you need to transport through proper work bench request
Please create a request not create directly into production server
hope this will help you
Edited by: Roy Anamika on Jul 2, 2009 7:51 AM

Condition Table creation for Taxes (TAXINN)

I want to create a condition table for Taxing procedure with application TX with the following fields : Plant , Control Code
Kindly tell me the SPRO path where i can create a condition table for Taxes.
Regards
Jyotsna

Dear Jyotsna,
We can create taxes in two ways.one is FICO side and another one is SD side
in FICO side you can do in FTXP
in SD you can do OVK1
hope this helps you
Prem.

SAP Pricing Condition Tables

Hello All,
Kindly look at this situation and recommend a possible Solution.
There is a SAP Standard Table XXX with combination Sales Org/ Dist Chan/Division/ Material and the description as Sales Org/ Dist Chan/Division/Material.. With Validity Period Checked and Release Status Unchecked.
I want to have a Pricing Condition Table as Sales Org/ Dist Channel/Division/ Material but with description Division/material. with Validity Periods Checked and Release Status Unchecked. When i try to do this i am getting a message " This table combination Already exiits", and i am unable to create further. Is there a way to create the Said table without this error.
Kindly Suggest a possible Solution. Your help will be highly appreciated.
Regards
Vittal

Hi Sai,
the message you are getting is not an error but just a warning message indicating the same combination of fields with which you are trying to create a table is already existing. And the descriptions of the fields are copied as it is as per their field names when you create a condition table.
Practically, the condition records that you can store against the available condition table and the one you are trying to create if at all with a new description is absolutely same. so there is no reason why you should create a condition table with the same combination again. However pl clarify if i could answer your query.
Regards,
sadhu kishore

Condition Tables with Release status

When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?
Thanks,
Venkat

hi,
The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
Release status has the following characteristics:
no entry: released
A: blocked
B: released for price simulation
C: released for price simulation and planning
The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
The release status of conditions in an agreement can only be changed, if
the condition record has release status in the key
the agreement has the release status released
Otherwise the condition record always has the release status of the agreement.
The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
source : Library.
regards

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

Issue with creation of ADF Table from ADF Tree selection

Hi,
Following is the usecase.
I've created ParentVO & ChildVO from a single table with view criteria to filter the nodes.And then created two View links ParentToChild & ChildToChild.
Added VOs & corresponding ViewLinks to ApplicationModule. It's got created hierarchy as Parent1->Child1->Chiled2 in Data model section of AM.So Iam done with tree creation process in Model.
As VC can't be applied for sub levels. In order to set the VCs for sublevels, followed the below approach.
Created a bind variable for tree. I've set the VC for both parent & child VOs in managed bean before setting the tree variable in setTree method. So now Iam able to display the required tree in UI with applying VCs.
Now , I can select the required nodes from tree and then click on command button to display the selection list as a table.
In order to achieve this, I tried below two options.
1) Created separate Child VO instance (Child3) from Child VO and applied same view which applied initially. and the dragged the Child3 from Datacontrol to UI(jsff) as a table. When I run the application,it's displaying all the records from the DB table without applying VCs.
2) Dragged the Child2 as a table on UI. When I run the application, it's displaying first record from the table without applying VC.
But no luck in getting the required functionality.
I've Following queries.
a) If we update any transient attribute value for an VO instance, will it effect at VO level or only for that particular instance?
Why because, I've created new instance of same VO. But the changes are not effecting for transient attributes in the new instance of VO.
b) Can some one suggest on my usecase to display the selected nodes from a tree in table format?
I tried my level best to explain the usecase. But let me know,if you have any queries on my usecase.
Thanks in advance,
Samba.

This is my code:
<af:column id="c1" headerText="Sponsor Status">
<af:selectOneChoice label="Label 2" id="soc1" value="#{row1.sponsorStatusDesc}"
validator="#{backingBeanScope.EditSponsorDetails.OnSponsorStatusChange}"
valuePassThru="true">
<f:selectItems value="#{pageFlowScope.confLists.spStatus}"
id="si1"/>
</af:selectOneChoice>
</af:column>
and this i what HTML code says..
<select id="confSponsor:r2:0:tbIEEEsp:0:soc1::content" class="x2h" name="confSponsor:r2:0:tbIEEEsp:0:soc1">
<option _adftmpopt="t" value="" title=""></option>
<option value="4" title="Approved">Approved</option>
<option value="3" title="Declined">Declined</option>
<option value="6" title="New">New</option>
<option value="2" title="Not Valid">Not Valid</option>
<option value="5" title="On Hold">On Hold</option>
<option value="1" title="Pending Approval">Pending Approval</option>
<option value="7" title="Unidentified">Unidentified</option>
</select>
Stll i cannot see any value populated in SelectOneChoice

Use of Release Procedure / status in Condition Table

What is the purpose of Release Procedure / Release status when creating condition tables ?

Hi
Release procedures are used in condition tables to control whether the condition types for these condition tables have to be read during pricing condition determination or not.
If the condition table status is released then only the condition types will be read during pricing determination. If the status is not released, then they can be used for information purposes or for simulation of pricing.
The release status is controlled by processing status too, which can be seen in condition record creation screen.
So in crux, the processing status with Release status help in simulation of pricing, blockign the condition records from being read during pricing etc.
For more information an F1 help on the following path will give you some more information.
SPROSD-BF-PRICING-DEFINE PROCESSING STATUS----Here read the documentation meant for this link. You will get some more clarity on this.
Rwd point if it helps.
Reward points if it helps.

Creation of condition table without copy

Similar Messages

Maybe you are looking for