Same condition type different value fields

same condition type is used for
1. sale of product
2.scrap sales
3.spares sales
condition typr (pr00) should be assigned to three diff value fields
(revenue ,scrap revenue &spares revenue) ,because they should not be summed up (need separate value)

Hi,
Can u sum up what is ur exact question/problem?

Similar Messages

Condition types and value fields

hi Gurus,
Can anybody please explain me what is condidion type and value field and the purpose of these two in costing??
Regards,
S.Sumana

Dear Sumana,
Condition types and Value field conjuction is used in Profitability Analysis.
Condition type is an element in pricing procedure. For e.g price of the product consist of several things like base price, discount, tax, etc. so each compenent is called condition type.
Value fields are grouping of cost elements for e.g. you have created a cost element Sales revenue then all revenue cost elements which consist of revenue.
Condtion type Base Price is revenue which is mapped to value field Sales revenue. So as soon as the billing document is created value field is updated.
For more information on Profitability analysis please read the documentation provide in www.help.sap.com
Regards,
Chintan Joshi.

Change the Condition type to Value Field Assignment in KE4I

Hi All,
I have a requirement where a condition type which has been assigned to a Value Field needs to be changed/re-assigned to a different value field.
There are already some postings into the current value field.
How can I handle these postings once I change the assignment in KE4I.
Please help me.
Thanks in advance,
erp.warrior.

Hi
Once you change in KE4I - It would impact only the subsequent postings... Historical postings wont be impacted...
If you want to impact them as well - Follow one of these 2 approaches
a. Then reverse the billing documents which have posted to this Value Field.... Change KE4I and post them again...
b. Do a KE21N upload i.e. a -ve amount on the Old value field and a +ve amount on the new value field
Regards
Ajay M

The same condition type calculates different amount !

Hi there,
On the print out of an invoice (VF03) I have realized that two different rows at the end of the invoice with the same description (Min Freight Charge) display 2x different amount of freight, once I check the condition type, on the header level, I see the same condition type (ZS..) with two different amount. Can anybody explain how can the same condition type (Min Freight Charge) be found calculating 2x different amounts
Thanks
Kami

Hi,
Check your pricing procedure at SPRO-> sales and distribution -> Basic functions -> Pricing control ->Define and assign pricing procedures ->maintain pricing procedures.
There might be two condition types used to calculate the frieght value. Each might be assigned with different routines under Alternative formula for condition base value column. I assume only one frieght condition type is needed to calculate the final value with reference to another condition type. Check the settings.
Regards

Same Condition type with different G/L Accounts

Dear All,
Our customer wants to maintain different set of G/L accounts with the same condition types in case of Service tax.
We have three different condition types for Service taxes.
JSV4 - Service tax
JES4 - ECS on Service tax
JSE5 - SECS on Service tax
We have Two different Services
1. R & D Services
2. IT Services
For these two services, service tax condition types are common but we need different G/L Accounts for different Services.
How to achieve this?
Regards,
Mullairaja

Create two tax codes in FTXP, one for R&D Service and another one for IT Services.
Now go to OB40, select the required Transaction, say for example MWS and assign these tax codes with the required G/L Account there.
Finally, in VK11, for tax condition type, assign these tax codes and save.
Now do one sales cycle for each scenario and update the forum.
thanks
G. Lakshmipathi

Same condition type used in MM , error?

Hi ,
I am (SD) using the same condition type which is used by MM and maintained different condition records in VK11. when I created STO , MM condition value is posting right , But with relevant to STO and Del , I create billing document , here The condition records what I maintained in vk11 are missing. I have check each and every step. where could be the error exists? cant we use the same condition type used by MM , though we maintained different acceess seq and condition records in VK11?
Thank you,
Kanna Palle.

Hi,
I copied the condition type and changed the name , but its already used by MM. Its a STO process .STO to DEL to IV Billing.I maintained condition records in vk11.In the combination of plant and material , I find different field name for material (but its still named as material and the data element is different from what MM material field). Its confusing I think.
Precisely , I created access seq for plant and material , they field names are z123 and zabc. when I maintained condition records in vk11 , condition record saved in ZAAA and ZBBB fields. now at the time of Billing document , system throws an error saying, * condition record is missing * The system checks z123 and zabc for condition records , which are not there becos they are in the fields ZAAA and ZBBB.
At the time of Acc Seq creation , I tried to pick the same field which it shows in billing document.but that is not available in SD , its available only in ALLOWED FIELDS in MM. Pls Throw some light on this.
Thanks,
Kanna Palle.
Any updates on this Pls?

How to stop this multiple entry against same condition type in pricing

My client is using manual condition type for the basic price "ZBPR". Now system allowing multiple entry against this condition type in the pricing screen during order creation i.e in the first line if we put ZBPR 00 , in the second line system allowing to put another value against same ZBPR say for example 2000 & doing all subsequent calculations on the basis of 3000 .which is not at all acceptable by my client .Please suggest how to stop this multiple entry against same condition type

You have to make the condition type as Mandatory and not manual.
If you are entering many condition records of the ZPR0 then the latest entry will be taken for further processing for subtotal rebate and total price.
For all the other entered condition records will have yellow traffic signal which is not active.
you can assign a routine with the help pf your abaper...
In the Transaction VOFM define a requirement such that
you condition type takes value only one at the time of order entry.
regards,
Amlan Sarkar

How to transfer SRM PO Condition Type and Custom fields to ECC?

Hi All,
I have a scenario to transfer SRM Line item condition types and few custom fields to ECC.
I have found the following things but structure 'CI_EKPODB' does not exists in ECC.
I am using 'SRM 5.00' and 'SAP ECC 6.0'.
NOTE: I have to transfer condition records when PO is getting created / modified.
1) Earlier I was planning to use BADI 'BBP_CREATE_BE_PO_NEW' in SRM and this will transfer the data to ECC in case of PO
    Creation.
               It contains the Condition fields to be passed to ECC.
But i am unable to implement the same, whenever i create implementation when i click 'Activate' its getting activate then after few seconds its getting deactivate, i think this is because this BADI is not allowed for multiple use and SAP has already made one implementation on the same.
2) I need to implement BADI 'BBP_ECS_PO_OUT_BADI' in SRM and 'BBP_PO_INBOUND_BADI' in ECC.
SRM BADI will pass verified field details to ECC as a custom fields
       It does not contains the Condition fields to be passed to ECC, so i was planning to pass the same as custom field(s).
ECC BADI 'BBP_PO_INBOUND_BADI' will be used to map the fields to correct place and this should work.
i need to modify the structures and pass all the custom fields (z-fields) - (CI_EKPODB but does not exists kindly suggest) as data.
Other required details:
      Transfer of PO does not supported by SAP for service PO's, any suggestion on the same?
Expecting quick reply from your end.
Thanks in advance.
Regards,
Hemant

Naresh,
Thanks for quick response.
My concern is this BADI 'BBP_CREATE_BE_PO_NEW' will trigger only in case of creation, not when PO is changes.
I have to transfer condition types and custom fields to ECC in both the case (create / change)
If i have to do this only in case of creation then i can pass Condition types / custom fields then i can use parameter 'CS_PO1_DOCUMENT' from method 'FILL_PO_INTERFACE1'.
this parameter contains 'IT_POCOND', 'IT_POCONDX' and 'IT_EXTENSIONIN' as parameter so my problem will be solved.
But i dont think this will trigger in both the cases and 2nd thing i cann't implement the BADI since its not marked for multiple use so i am unable to implement the same.
Kindly correct me if i am wrong.
Once again thanks for your reply.
Please suggest on the same.
Regards,
Hemant

LinkedHashMap problem (Same key but different value)

Dear Friends,
There is problem in LinkedHashMap for same key but different values.
I want both values of same key as Output.
Plz help me from an example code & it's output
LinkedHashMap<Object, LinkedList<Object>> linkhash = new LinkedHashMap<Object, LinkedList<Object>>();
LinkedList<Object> ll6 = new LinkedList<Object>();
          LinkedList<Object> ll7 = new LinkedList<Object>();
          LinkedList<Object> ll9 = new LinkedList<Object>();
objectName="Listitem";
          ll6.add("id\tlisti");
          ll6.add("tag\tlistcell");
          ll6.add("tag\tlistcell");
          linkhash.put(objectName, ll6);
          System.out.println("List is "+linkhash);
          objectName="Listcell";
          ll7.add("id\tlistc");
          ll7.add("label\tCEO");
          linkhash.put(objectName, ll7);
          System.out.println("List is "+linkhash);
          objectName="Listcell";
          ll9.add("id\tlistc1");
          ll9.add("label\tNKC");
          linkhash.put(objectName, ll9);
          System.out.println("List is "+linkhash);
output is
List is {Listitem=[id     listi, tag     listcell, tag     listcell]}
List is {Listitem=[id     listi, tag     listcell, tag     listcell], Listcell=[id     listc, label     CEO]}
List is {Listitem=[id     listi, tag     listcell, tag     listcell], Listcell=[id     listc1, label     NKC]}
I want output as
List is {Listitem=[id listi, tag listcell, tag listcell],Listcell=[id   listc, label CEO], Listcell=[id     listc1, label NKC]}
Plz help me
Thanks Friend
Edited by: kkcnkc on Apr 1, 2009 6:47 AM

Double post. Locking.

Restrict same condition type in pricing procedure

Is there a way to restrict the condition type so that there can only be one occurrence of the same condition type in a order item?
Example:
System reads condition type ZXXX from system, then a user adds the same condition type on the same order item. I would like the system to then give a error message saying ZXXX can only occur once.
Kind regards

Hi,
As this is manual condition and the user are inputing it by themselves then you won't like to change the way the manual changes are maintained/allowed.
What you want that is user have given it once then they should not be able to input is again in the same sales order item. For this you should take help of requirement. Preapre logic that before the condition system check if there is existing condition of this type in this sales order item.
Hope it helps ..

Query parameters with the same name and different values

According to HTTP, multiple query or post parameters with the
same name and different values are permitted. They are transfered
over the wire in the following format -
name1=val1&name1=val2&name1=val3
The problem is that I can't see anyway of assigning multiple
parameters with the same name and different values to the request
object of mx.rpc.http.HTTPService. I have tried using the
flash.utils.Dictionary object as it does strict key comparison but
that doesn't work too. I have tried setting an array of values to a
property of the request object but that sends the request to the
server in the following format -
name1=val1,val2,val3
The java servlet engines throw exceptions when they see this.
Any help would be greatly appreciated.

If you're not on 8.1.4 move there. 8.1.3 had limitations in the wsrp
release.
wrote:
I have an html select box that contains several values, and multiple
selection is enabled. When my code runs as a remote portlet, the
following is showing up in the soap monitor when I select multiple
values and submit the form:
<urn:interactionParams>
<urn:portletStateChange>cloneBeforeWrite</urn:portletStateChange>
<urn:interactionState>_action=addEmployeesToGroup</urn:interactionState>
<urn:formParameters
name="P62005wlw-select_key:{actionForm.selectedEmployees}OldValue">
<urn:value>true</urn:value>
</urn:formParameters>
<urn:formParameters
name="P62005wlw-select_key:{actionForm.selectedEmployees}">
<urn:value>beatest1</urn:value>
</urn:formParameters>
In this case, I selected beatest1 and beatest2, but only beatest1 comes
through to the remote portlet. Is this a known bug, and, if so, is
there a patch or workaround available?
Thanks in advance,
Andy

Same condition type on header and item level = printing problem

Hi
I have a customer using some condition types on both item level and header level in quotations, orders, invoices ...
In the pricing procedures it is customized (V_T683S-DRUKZ) that the conditions must be printed on header level (that is at the bottom of the documents).
My job is to make the Smartform to print the documents, and I want it of course to be as close to SAP standard as possible.
SAP standard will print these conditions on header level even if the conditions are at item level, but my customer wants the conditions created on header level to be printed on header level and conditions created on item level to be printed on item level.
I'm no pricing expert, so my question is:
Will it be fair if I tell the customer that using the same condition types on header and item level is bad practices - or at least bad karma?
Best regards
Thomas Madsen Nielsen

Hi Shiva Ram and Madhu
I have no problem understanding header vs. item conditions, so I really don't see anything in oss note 876617, that is relevant in this case.
Madhu - I do not agree that everything is fine. My issue is that I want to stick as closely to SAP standard customizing as possible. In SAP standard customizing of a condition type you can use the flag V_T683S-DRUKZ to determine if the condition should be printed on header OR item level - you can not choose both header AND item level.
I have a SAP standard smartform using two functions modules for reading header and item conditions. RV_PRICE_PRINT_ITEM and RV_PRICE_PRINT_HEAD. These function modules are based on the DRUKZ customizing flag and a condition marked for printing on header level will be supplied by RV_PRICE_PRINT_HEAD even when the condition is on item level.
My point is: SAP standard customizing does not support printing of same condition on both header and item level. I can of course write tons of code to work around this problem, but that would be bad practices

Pricing - Manual Condition Type with value = 0

Hi gurus,
I need to insert a manual condition type with value = 0 into the billing data set.
I realize that if its valiue is 0 it is not active.
Anyone knows how to make it active despite its value = 0?
Thank you.

Dear Customer,
if you have customized the condition as price then the condition will be inactive if the condition is set to zero.
This is calling in:
LV61AA55
inactivate prices with rate / condition value zero
      if xkomv-koaid eq 'B' and xkomv-kbetr eq 0 and komp-kposn ne 0 and
         xkomv-kgrpe eq ' ' and xkomv-kinak ca ' Y' and xkomv-kwert eq 0
         and xkomv-kntyp ne 'e' and komp-fareg na '45'.
        xkomv-kinak = 'X'.
      endif.
If you need an active condition with value zero, then the condition class should not be 'B' (price)
I hope that the information are helpful.
regards
Claudia

COPA - Split of Value from condition type into different value fields

Dear All,
Customer is having several free schemes to customer the same is set up by SD and Cost of free goods is attached to One Z condition type, this flows along with Main product as characteristic. So we have Main product cost in VPRS and Scheme cost in Z Condition and there is possibility of more than one scheme cost flowing in one Z condition for single billing document. Whereas customer request is to see the each scheme cost separately in COPA. Since Value from SD will be flowing through only one condition type , it will be difficult to me to Split this in COPA. We have given a thought of having more than one condition type from SD ( one Z condition for one scheme) but this resolve our issue at hand. If we look at long term whenever customer introduces new Scheme new condition type need to be created and related COPA changes etc, Which doesn't seem to be working out.
Request Experts help in this, thanks in advance for the help.

Hi Santosh
Having a Z cond type for each scheme is preferrable.... This would address the issue with Standard SAP itself...
Reason being, if you dont do that, then you will have to maintain a mapping somewhere in a Z Table where by system would come to know of the ratio between the schemes... This will be more cumbersome to develop and maintain... Still you wanna do that, here is the logic....
Maintain the schemes in a Z Table... Where each scheme will have a scheme ID - The ratio applicable to various schemes and also the relevant value fields of COPA to be updated for each scheme....
Now, add a Custom Field to the Sales Order and while creating the SO this field needs to be updated with the scheme ID(Relevant Exit to make it mandatory MV45AFZZ / ZB).... If Scheme ID is populated, your Billing should read the Split from Z Table using Exit RV60AFZZ and Update COPA using Exit COPA0002
br, Ajay M

Different base value reference steps for same condition type

Dear Gurus
I have a scenario where I have single pricing procedure for normal sale and Intercompany billing.
Condition type GRWR should take the base value from step 350 in standard scenario
But in Inter company billing it should take the base value from a different step.
Want to check the possible way to determine these.
Regards,
Neeraj Srivastava

In the pricing procedure, in the step that you're interested in intercompany billing put in the subtotal field the indicator "carry over value to KOMP-KZWI". Make sure that the KOMP-KZWI field that you'll choose is not used in any other step.
Then with the help of an ABAPer you should maintain a routine (Tc VOFM -> Formulas -> condition base value) that in the case of intercompany billing (if billing-type is XXX ... etc) will take the KOMP-KZWI* value that you chose previously.
Then back in the pricing procedure, assign your new routine in the field "Alternative formula for condition base value" (BasType).
Agis

Same condition type different value fields

Similar Messages

Maybe you are looking for