SD-Pricing Conditions: Allowed Fields

Hi Guys
basic functions > pricing> condition table> conditions:allowed fields > new fields
when I try to add a new field: VOLEH ( selected using F4), system throwing following warning message: "Choose the key from the allowed namespace". We can save by ignoring this message.
But when I try to create condition table, this field is not visible.
Please suggest me how to add field VOLEH(Volume unit).
Regards
Uma

When you open the possible entries you usually find the field twice, once in the structure for header or item, and once in the communication structure. Most likely your field is only in the item structure, you need to add it to the communication structure as well (or better a developer needs to do that).
You might need to fill the field in the Pricing_Prepare user exit too.
The warning usually appears, because it is SAP namespace, if you need to add the field, you might consider putting ZZ in front of the fieldname (ZZVOLEH).
Edited by: Markus Müller on Jun 27, 2008 3:33 PM

Similar Messages

Maintaining pricing condition with field group

Hi
I want to check the linkage between condition maintenance table for pricing with the Contract.
Can any body tell me how to maintain the pricing condition with the field group of Contract.(provide me the detail path)
I am getting one error"Internal error in condition maintenance" when i click on product tab for any of contracts.
So I guess it may be due to any linkage failure between condition table and field group or tabstrip. please tell me how could I proceed forward to check this error.
Thanks

Hi, I hope that this linck to serve.
[condition fields table|condition fields table]
Cordial greetings.

Pricing Condition Field

I would like to use the 5 material groups in the material master as part of the pricing condition table fields. How can this be done?
I added the fields RKE_MVGR1-5, but getting this error during pricing in the order ' 102 access not made (initialized field) "

I don't believe you are using the correct fields. The order uses MVGR1-5 not RKE_mvgr1-5. I believe the RKE versions are used in COPA. I would recommend the following:
1. append MVGR1-5 to kompaz and activate
2. Add MVGR1-5 to the field catalog under IMG->SD-> Basic Functions-> Pricing-> Pricing Control-> define cond tables -> conditions allowed fields
3. re-create your tables using mvgr1 through mvgr5
4. Replace your new tables in your access sequence you are using in your condition types
This should give desired results.
It is also possible to leave RKE_mvgr1-5 as is and move vbap-mvgr1-5 to corresponding tkomp-rke_mvgr1-5 in mv45afzz form userexit_pricing_prepare_tkomp. however, I am not sure of impact to COPA using these fields.
Hope this helps, Matt
Edited by: Matthew Menzies on Mar 4, 2010 4:00 PM

Pricing - Add to Field Catalog

I want to use KDKG1 Condition Group 1 as a Pricing Field. It is listed in Conditions: Allowed Fields, but when I try to create a Pricing Table, that field is not listed. As a matter of fact, about 30 fields are not listed when trying to create a Pricing Table as compared to what is listed in Allowed Fields. When I try to add it as a new field in Conditions:Allowed Fields, it says 'Choose the key from the allowed namespace' and then it says 'An entry alread exists with the same key'. How can I get this existing field to be available when creating my Pricing table? Do I have to create a Z field and add it to the pricing structures?
Thanks,
Karyn

Refer OSS Note 167926 - Condition Group Field not avail for Condition Tables
Per this note append the field with structure KOMG using an append structure.
Also refer the thread Re: wants to add field in field Catlog
Regards,

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

New Field Addition in Allowed Field Catalogs -Pricing.

*Hi,
We have requirement of having Material Description field in the Allowed Field Catalogs in SPRO --> SD --> Basic Functions --> Pricing --> Pricing Controls --> Define Condition tables --> Allowed Field Catalogs in order to fetch the same for Pricing Condition Table creation with Mtrl Description as Key Combination.
Hence, as a first step, have added the MAKTX field inside the "ZStructure" (which was created before) inside Main Structure KOMP and activated the same. Then i have added the same field MAKTX in Allowed Field Catologs of Pricing using New Entries.
Now i have tried to create a new Pricing Condition Table with field catalog of Material Description (the added field), but there is no such field is available for selection.
Is there anything i missed to do, so that the newly added field is available during New Condition Table Creation with key combination of the added field.
Appreciate your promot response.*
Rgds,

Hi,
Thanks for your response.
Have added the required field in Structure KOMG now and it is available for selection in Condition Table Field Catalogs. However, am allowed to select this field only when creating a New Condition Table and if i want to add this field in the already created condition table in change mode, it thows an error message - "Function Code cannot be selected".
How to proceed further.
Rgds,

Not allow to change pricing condition in Billing,,,

Hi ,
I want to know the user exit or other solution for following:
System should not allow to change the value of basic pricing condition type in billing.
Ex. In sales order value of condition PR00 is 100, then it should not allow
to change the value of condition type PR00 in billing. If requires to change, it should allow
to change in sales order only.
Thanks & Regards,
Sachin

For this no need to use user exit
goto V/06 condition type details
choose which condition type u want to give display view
go to controlling tab or changes can be made , uncheck the value and amount fields. than system should not allow to change the condition type in sales order level also.
(or)
if u want in billing document only
configure copy controls between delivery document to billing document (VTFL)
goto item category, select item category (TAN)> details and add pricing type E.
try this
regards
siva

Condition type field when Define Pricing Procedure Determination

Hello Gurus,
there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
Many thanks,
Frank Zhang

Here is are the details of various fields while configuring pricing procedure.
A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERFu2026u2026u2026u2026.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
Kalpesh

Field catalog for pricing condition not present

Hi experts,
i want to create a princing condition so for this i have to add one field to structure KOMPAZ. So, i have included required field (manufacturer) in this customer structure KOMPAZ but even with this modification I can't see manufacturer field in field catalog (t-code V/03)
Why??
Please someone help me.
Any help would be apppreciated.

Hi
SPRO--> u2018Sales and Distribution -> Basic Functions -> Pricing -> Pricing Controlu2019 and execute u2018Define Condition Tablesu2019. Choose u2018Conditions: Allowed fieldsu2019 and include Conditions: Allowed fieldsu2019 and include (Customized "Manufacturer" ) Field as a new entry.
Now you can use field (Customized "Manufacturer" ) as a key field when you create a condition table
Further Info refer the URL Below
[ Add New Fields To Field Catalog |http://sapsdforum.com/2007/10/23/pricing-in-sd-in-great-detail/]

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

CRM Pricing - BADI to Populate pricing conditions fields

Hello All,
We have CRM 5.0 installed in our customer.
We are facing problems when we tried to replicate the pricing from R/3.
Basically, all Brazilian formulas we have in R/3 are Z. We tried to replicate them in JAVA (IPC) with no success. At this time, it is imposible for us to move to the standard because of the decision of the business.
We are trying to find one BADI where we can populate all the pricing conditions retrieved via RFC from R/3. Unfortunatelly we don't have good luck with this.
Our idea is to use this BADI to call R/3 and retrieve the conditions needed, and then populate the CRM pricing fields..
Could you please help us? Do you have any other idea to solve this issue?
This is very critical for us.
Thanks in advance.
Martin

Hi Ntk,
Thanks for your reply.
I tried to search in se18. I found one BADI that runs when users enter new materials or changes the quantity of the sales order.
This one does not help us too much, because when you go to conditions tab (into CRMD_ORDER or via ICWEB) all conditions are redetermined with the pricing determined in IPC.
We want to fill the conditions of the sales orders or the sales quotations at running time. In the BADI we would use the function module RFC SD_SALESDOCUMENT_CREATE (in simulation mode) in R/3 and retrieve all conditions fields and then populate the pricing conditions in CRM.
Do you know any BADI with this behaviour? Or another similar?
THANKS!

Create pricing condition with default value in processing process field

hi all,
when i maintain the pricing conditions with vk11 or vk31, i want the price maintained is set default as blocked (the processing status field-KBSTAT). can it be done? i am using 4.6c.

You should try to use transaction variant
<i>Transaction variants simplify transaction flow by:
Inserting default values in fields
Changing the ready for input status of fields
Hiding various screen elements and menu functions, or even entire screens
Adjusting table control settings
When you create a transaction variant, you run through the transaction in a special mode. In this mode, you decide which elements you no longer need in your transaction and which values should be inserted where. If you choose to hide an entire screen, the system will no longer display that screen in the transaction and will proceed on to the next screen in the series. You can also adjust table control settings and determine the width of columns and the order in which you want them displayed. In tab strips, you can suppress tabs that you no longer need by setting them to invisible.
You may also create as many variants for a transaction as you desire. One of these variants can be defined as a standard variant. This variant is then valid across all clients. You may also assign different variants to specific users.
This is done using Variant Transactions. Variant transactions are then places in those users user menus instead of the standard transaction. </i>
To use this : Tools -> Accelerated SAP -> Personalization (transaction SHD0)
Regards

2 pricing conditions in PP

Hi everyone,
This is a RETURNS scenario.
We create a Credit Memo Request (Sales Order type: CR) when the customer calls in for a Return and we make another Sales Order (Sales Order Type: RE) when the goods actually come in. A credit memo is created against the CR initially and later a billing doc. is created against deliv. made from the RE order.
Now the requirement is to have 2 pricing conditions in PP of the CR order. Say ZR00 and ZR01, where ZR01 = -(ZR00). This is coz' ZR00 is posted to the sales account and ZR01 to Accrual account. When RE is created the -ve price in Accruals account from the CR is cleared.
Now standard SAP allows only one pricing condition in a PP, any ideas on getting around this?
Temporarily I have made ZR01 a 100% discount....but I knw thats not the way to go about it.
Any help is appreciated
regards

Hi,
Maintain a single Price Condition Type, say ZR00, in your PP.
In T. Code: V/06, maintain Field: Plus/ minus as "Blank" for Condition amount as both: Negative (a Discount) or Positive (a Surcharge), or whether both positive and negative amounts are possible.
{Condition Class: B - Prices}
In T. Code: V/08, insert your condition type: ZR00 and maintain other column entries as, for example, Column: Account Key as "ERL - Revenue"; Column: R as "Checked for Mandatory, if reqd." etc..
You may insert other condition types, based upon Condition Type: ZR00, in subsequent rows, such as "Material", "Customer Discount", "Customer/ Material" or Tax Conditions etc..
In Acct Determination, T. Code: VKOA, Maintain G/L accts. for "Cust Grp./ Mat. Grp/ Acct Key" and maintain Provision Acct, next to G/L Acct for account determination takes place in the billing document with the field, relevant for accrual.
Rest will be assured from FI-Consultant as maintain G/L accts and postings is FI-job.
There is no need of maintaining 2- Condition Types in PP, at all.
Best Regards,
Amit.
NOTE: Hope, I have understood the problem and answered to your query, up to some extent.

Multiple Variant pricing conditions in a Pricing Procedure

Hi,
I have a scenario regarding variant configuration pricing in a sale order. I need to attach multiple pricing condition like VA00 in my pricing procedure .
A material M1 has many characteristics under the category Basic and Special for example.
Under Basic I have the following characteritics and its respective values maintained in VK11
B001- Basic Spec 1 USD 100
B002- Basic Spec 2 USD 200
B003- Basic Spec 3 USD 300
Likewise under special category ,
S001- Special Spec 1- USD 500
S002- Special Spec 2- USD 1000
In the pricing procedure the varaint condition VA00 will carry the price of the characteristics. My requirement is as follows
1. The prices of the Basic spec should be added first and later the special spec
VA00- Basic Spec 1      100
VA00- Basic Spec 2      200
VA00- Basic Spec 3      300
Sub total Basic spec Value 600
VA00 Special Spec 1    500
total basic and special spec - 1100
The problem I faced in the above format was that the pricing procedure will allow only one entry of VA00. To over come that I copied the condition VA00 and named a new one, for e.g, ZVSP.
Now when I use the condition ZVSP, it does not fetch the values like VA00.
Could any one suggest a method in which I can introduce varaint conditions in multiple levels in a pricing procedure.
Thanks and regards
Rasheed

Hi,
When you copied the VA00 condition type, did you also copy the associated access sequences? Your new condition type should have an access sequence with an access that transfers the value of the doc. field KOMP-VARCOND into the condition VARCOND; use transaction V/07 to check this.
Regards, Jesper

What is the mean of condition index in pricing condition

hi
my question is what is the mean of conditon index in pricing condition type what is the use of it give me ascenario.

hi nag
A customer-defined list of conditions that allows quicker access to condition records or a group of condition records.
<a href="https://forums.sdn.sap.com/click.jspa?searchID=4774296&messageID=3962335">condition index</a>
Condition Index can be created for particular condition type to maintain condition record. The condition index along with the condition update field in condition type (T.Code: V/06) restricts the usage of condition type for limited sales orders, condition base value or condition value.
Features of condition Index:
When checked this specifies whether the system updates one or more condition indices when maintaining condition records.
This makes it possible to list or maintain condition records independently of condition type and condition table
Message was edited by:
Prashanth Goud

SD-Pricing Conditions: Allowed Fields

Similar Messages

Maybe you are looking for