How to implement the Reference Condition Type

Dear Friends,
My Client is using the Refernce Condition type ZMWS which is referencing MWST condition type. He has implemented the same for one company code already. When I am creating a Sales Order, I am able to get the condition type MWST for the newly created condition type ZMWS through the condition record maintained for MWST.
But when I am doing the same for other company code I am getting a pricing error as it is saying mandatory condition ZMWS is missing.
I am not getting any clue what to do. Do I need to maintain any settings?
Thank you,
Prakash K M

Dear Prakash,
In V/06, detail screen of condition type, under under master data you have to give the reference condition.
Regards,
Abhee.

Similar Messages

How to give the header condition type in the CRM Sales Order for freight ?

Hi,
     We are creating Sales Order(SO) using FM 'CRMXIF_ORDER_SAVE'.And we are unable to track the FREIGHT condition type in the above FM to pass value.
     We want to check this value in CRMD_ORDER tcode.
    Pls let us know how to make it possible of the above issue.
Thanks,
Siva..

Siva,
   I guess you posted in Wrong Thread. You need to post in WAS section.
   check for any BAPI's available in CRM.
Nagesh Ganisetti.

How to give the header condition type in the Sales Order for freight?

Hi,
     We are creating Sales Order(SO) using FM 'CRMXIF_ORDER_SAVE'.And we are unable to track the FREIGHT condition type in the above FM to pass value.
     We want to check this value in CRMD_ORDER tcode.
    Pls let us know how to make it possible of the above issue.
Thanks,
Siva..

Siva,
   I guess you posted in Wrong Thread. You need to post in WAS section.
   check for any BAPI's available in CRM.
Nagesh Ganisetti.

How to change the manual condition type value in change sales order BAPI

Hi All,
My scenario here is, i want to either add/change the manual condition type value during change of SO.
When i'm trying to pass the order_conditions_in and order_conditions_inx tables in 'BAPI_SALESORDER_CHANGE'.
Condition type is coming at item level but the value is setting to zero. Pls. help if anyone has any idea how to handle this.

Siva,
I guess you posted in Wrong Thread. You need to post in WAS section.
check for any BAPI's available in CRM.
Nagesh Ganisetti.

How to get the created condition type and make it possible to view it in PO

Hi,
Can anyone tell me how to make my condition type created will appear in the condition type selection list.
Regards,
Sairam

Dear,
You can see the <b>Pricing Procedure</b> & the<b> condition type</b> & analysis in the <b>Conditions</b> tab of the item detail of the PO.
Pl note the pricing procedure attached to the vendor thro' the <b>Schema group Vendor</b> and analyse for yourself by creating a PO for this Vendor.
Thanks ,
Nagarajan

How to update the z-condition type in pricing procedure in a quote

Hi Gurus,
I need your help to solve my issue.
I have created a RFC which will trigger any time there is a CRM Quote/ CRM Order create or change occurs. IN response of the RFC i will get the rate and rate type for the line items .
When the service returns with rate value the SAP system will insert this value by inserting z-condition type in to the pricing structure. The normal pricing function module will then carry the process forward.
Todo this ,Can i code the RFC call in Order_save badi ,but where can i get the pricing sturcure data to update the returned rate values in the pricing.
and also one more thing ,In ecc I am using the CUCB_GET_CONFIGURATION to get product configurations. for the same which FM can i use in CRM.
Please reply me ASAP.

hei,
you can use field KOMP-KZWI1 - KZWI6 to store your condition type. then it can be used for analysis in SIS.
if you want to put more than one condition type to field KOMP-KZWI1, go to V/08 (pricing Procedure), put "1" in condition subtotal.
Best Regard,
Hendry

How to make the PR00 condition type madatory

Hi Guys,
We need to prevent any sales order without PR00 from being posting. Where should we set this customization?
Best Regards
Jerome

Hi,
Go to Pricing Procedure in V/08... Select your pricing procedure and mark PR00 as mandatory condition by selecting mandatory check box for PR00.
This will resolve your problem...
Muthu
Edited by: Muthupandiyan C on Mar 6, 2009 2:00 PM

Reference Condition type

Hi,
Can someone share with me on the usage of the reference conditon type field in the condition type field? If i put in the PR00 as the reference condition type in PB00?
How this will affect the price determination?
Still quite new to price determination in MM. Hope someoneone can give me some guidance on it.
Thanks.

hi
A condition type which can be used as a reference so that you only have to create condition records once for condition types that are very similar.
Ex: AMIW and AMIZ, these both condi types are used for minimum order value.
If u maintain AMIW- (min ord value) condition type We have to assign this condition type to AMIZ (surcharge value) cond type as reference condition type. then only it will work it.
Edited by: Roddick Redy on Apr 21, 2008 7:29 AM
Edited by: Roddick Redy on Apr 21, 2008 7:32 AM

How to create Reference Condition Types

Hi ,
Please tell me how to create Ref.Condition Types?
I have a requirement.."I should create a Zdiscount(13%) which should be copied to the sales order automatically based on PR00"
How to do that?
Points for sure
RamChandra

Hi,
You can use condition supplement functionality.
Check the link [Condition Supplements|http://help.sap.com/saphelp_47x200/helpdata/en/93/7432de546011d1a7020000e829fd11/frameset.htm]
You can also check the field RefConType for the discount condition type in SPRO -> Sales and distribution -> Basic functions ->Pricing -> Pricing control ->Define condition type.
Regards,

How to get the reference of the cell id in validate method in adf

Hi All,
I am using Jdeveloper 11.1.1.2 and i am using custom validator where i have registered the validator in facesconfig.xml.I need to know how can i get the ID of the inputtext box which is present in the hierarchy as Panel Header->Table->column->textbox :-
Below is my custom validator class source , please tell me how to get the reference of the textbox which is present in such hierarchy.:-
package validator;
import java.io.Serializable;
import java.util.Date;
import javax.faces.application.FacesMessage;
import javax.faces.component.UIComponent;
import javax.faces.context.FacesContext;
import javax.faces.validator.Validator;
import javax.faces.validator.ValidatorException;
import oracle.adf.view.rich.component.rich.input.RichInputDate;
import oracle.adf.view.rich.component.rich.input.RichInputText;
import oracle.adfinternal.view.faces.bi.util.JsfUtils;
public class ValidateConversion implements Serializable, Validator {
public ValidateConversion() {
super();
public void validate(FacesContext facesContext, UIComponent uIComponent,
Object object) throws ValidatorException {
System.out.println("*************");
System.out.println((String)object);
//get component id by get("AttributeName");
String conversionComponentId = (String)uIComponent.getAttributes().get("UncommittedOrder_PH:t7:it14");
System.out.println("conversionComponentId=" + conversionComponentId);
RichInputText conversionComponent = (RichInputText)uIComponent.findComponent(conversionComponentId);
Integer conversion = (Integer)conversionComponent.getValue();
Integer quantityInBags = (Integer)object;
//get labels from the two inputDate component.
String conversionLabel = conversionComponent.getLabel();
String quantityInBagsLabel = ((RichInputText)uIComponent).getLabel();
Integer remainder = (quantityInBags % conversion);
//throw error if valiation fails
if (remainder > 0) {
throw new ValidatorException(new FacesMessage(FacesMessage.SEVERITY_ERROR,
"The " + quantityInBagsLabel + " should be in multiples of" + conversion +".",
null));
Thanks,
Plese reply!!!

Thanks Jabr,
This is my jsff page source and i need to find the reference of it14 which is the textbox :-
<af:panelGroupLayout id="pgl1" styleClass="AFStretchWidth">
<af:panelHeader text="Results" id="Results_PH" size="1">
<af:table value="#{bindings.queryProductResponseType.collectionModel}"
var="row"
rows="#{bindings.queryProductResponseType.rangeSize}"
emptyText="#{bindings.queryProductResponseType.viewable ? 'No data to display.' : 'Access Denied.'}"
fetchSize="#{bindings.queryProductResponseType.rangeSize}"
rowBandingInterval="1"
filterModel="#{bindings.queryProductResponseTypeQuery.queryDescriptor}"
queryListener="#{bindings.queryProductResponseTypeQuery.processQuery}"
filterVisible="true" varStatus="vs" id="ResultTable_t"
width="99%" partialTriggers="::cb1 ::cb2 ::cb3 it14"
binding="#{viewScope.GrowerOrderBean.resultTable}"
columnStretching="last" rowSelection="multiple"
sortListener="#{viewScope.GrowerOrderBean.sortResultTable_action}"
autoHeightRows="8" first="0"
inlineStyle="height:196px;margin:10px"
selectionListener="#{viewScope.GrowerOrderBean.resultRowSelect_action}">
<af:column filterable="false" sortable="false" headerText="Select"
id="c9" width="55" rendered="false"
filterFeatures="caseInsensitive">
<div align="center">
<af:selectBooleanCheckbox value="#{row.bindings.booleanFlag.inputValue}"
label="#{bindings.queryProductResponseType.hints.booleanFlag.label}"
required="#{bindings.queryProductResponseType.hints.booleanFlag.mandatory}"
shortDesc="#{bindings.queryProductResponseType.hints.booleanFlag.tooltip}"
id="it19" autoSubmit="true">
<f:validator binding="#{row.bindings.booleanFlag.validator}"/>
</af:selectBooleanCheckbox>
</div>
</af:column>

<af:column sortProperty="quantity" headerText="Quantity in Bags" filterFeatures="caseInsensitive"
id="c54" rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterable="true" sortable="true">
<af:inputText label="Quantity in Bags" id="it14"
partialTriggers="it19" autoSubmit="true"
readOnly="#{row.activeYN == 'N' or row.availability < 0 or row.availability ==0}"
valueChangeListener="#{viewScope.GrowerOrderBean.compare}">
<af:validateLongRange id="RangeCheck_Val1" minimum="1"
maximum="#{row.availability * row.conversion}"
messageDetailNotInRange="You have entered a quantity more than is available. Quantity entered must be in the range of {2} to {3}"
messageDetailMinimum="Minimum {0} allowed is {2}"
messageDetailMaximum="Maximum {0} allowed is {2}"
hintNotInRange="#{'Quantity In Bags to Order'}"/>
<af:validateRegExp pattern="^[1-9]+[0-9]*$"
messageDetailNoMatch="Quantity In Bags must be in whole number format."/>
<f:validator validatorId="custom.conversionValidator"/>
</af:inputText>
</af:column>

<af:column sortProperty="quantity" filterable="true"
sortable="true" headerText="Quantity" id="c3"
width="60"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive" visible="false">
<div align="center" >
<af:inputText value="#{row.bindings.quantity.inputValue}"
label="#{bindings.queryProductResponseType.hints.quantity.label}"
required="#{bindings.queryProductResponseType.hints.quantity.mandatory}"
columns="#{bindings.queryProductResponseType.hints.quantity.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.quantity.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.quantity.tooltip}"
id="it5" partialTriggers="it19"
readOnly="#{row.activeYN == 'N' or row.availability < 0 or row.availability ==0}">
<f:validator binding="#{row.bindings.quantity.validator}"/>
<af:validateLongRange id="RangeCheck_Val" minimum="1"
maximum="#{row.bindings.availability.inputValue}"
messageDetailNotInRange="You have entered a quantity more than is available. Quantity entered must be in the range of {2} to {3}"
messageDetailMinimum="Minimum {0} allowed is {2}"
messageDetailMaximum="Maximum {0} allowed is {2}"
hintNotInRange="#{'Quantity to Order'}"/>
<af:validateRegExp pattern="^[1-9]+[0-9]*$"
messageDetailNoMatch="Quantity must be in whole number format."/>
</af:inputText>
</div>
</af:column>
<af:column sortProperty="brand" filterable="true" sortable="true"
headerText="Brand" id="c10" width="80"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive" displayIndex="-1">
<af:inputText value="#{row.bindings.brand.inputValue}"
label="#{bindings.queryProductResponseType.hints.brand.label}"
required="#{bindings.queryProductResponseType.hints.brand.mandatory}"
columns="#{bindings.queryProductResponseType.hints.brand.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.brand.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.brand.tooltip}"
id="it7" readOnly="true">
<f:validator binding="#{row.bindings.brand.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="seedsz" filterable="true" sortable="true"
headerText="Seed Size" id="c7" width="50"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive">
<af:inputText value="#{row.bindings.seedsz.inputValue}"
label="#{bindings.queryProductResponseType.hints.seedsz.label}"
required="#{bindings.queryProductResponseType.hints.seedsz.mandatory}"
columns="#{bindings.queryProductResponseType.hints.seedsz.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.seedsz.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.seedsz.tooltip}"
id="it11" readOnly="true"
contentStyle="text-transform:uppercase">
<f:validator binding="#{row.bindings.seedsz.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="pckSize" filterable="true"
sortable="true" headerText="Pkg Size" id="c11"
width="50"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive"
inlineStyle="#{row.conversion > 1 ? 'background-color:Yellow;' : 'background-color:White;'}">
<af:inputText value="#{row.bindings.pckSize.inputValue}"
label="#{bindings.queryProductResponseType.hints.pckSize.label}"
required="#{bindings.queryProductResponseType.hints.pckSize.mandatory}"
columns="#{bindings.queryProductResponseType.hints.pckSize.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.pckSize.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.pckSize.tooltip}"
id="it8" readOnly="true">
<f:validator binding="#{row.bindings.pckSize.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="conversion" filterable="true"
sortable="true" headerText="Conv" id="c4" width="50"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive" displayIndex="-1">
<af:inputText value="#{row.bindings.conversion.inputValue}"
label="#{bindings.queryProductResponseType.hints.conversion.label}"
required="#{bindings.queryProductResponseType.hints.conversion.mandatory}"
columns="#{bindings.queryProductResponseType.hints.conversion.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.conversion.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.conversion.tooltip}"
id="conversion_it" readOnly="true">
<f:validator binding="#{row.bindings.conversion.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="treatment" filterable="true"
sortable="true" headerText="Treatment" id="c13"
width="70"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive">
<af:inputText value="#{row.bindings.treatment.inputValue}"
label="#{bindings.queryProductResponseType.hints.treatment.label}"
required="#{bindings.queryProductResponseType.hints.treatment.mandatory}"
columns="#{bindings.queryProductResponseType.hints.treatment.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.treatment.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.treatment.tooltip}"
id="it20" readOnly="true">
<f:validator binding="#{row.bindings.treatment.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="availability" filterable="true"
sortable="true" headerText="Availability" id="c15"
width="60"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive">
<af:inputText value="#{row.availability> 500 ? '>=500': (row.availability> 100 and row.availability<500 ? '100-500' : row.availability) }"
label="#{bindings.queryProductResponseType.hints.availability.label}"
required="#{bindings.queryProductResponseType.hints.availability.mandatory}"
columns="#{bindings.queryProductResponseType.hints.availability.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.availability.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.availability.tooltip}"
id="it9" readOnly="true">
<f:validator binding="#{row.bindings.availability.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="desiredDeliveryDate" filterable="true"
sortable="true" headerText="Desired Delivery Month" id="c2"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive" width="90">
<af:selectOneChoice id="soc1" partialTriggers="it19"
unselectedLabel="#{viewScope.GrowerOrderBean.desiredDeliveryDate}"
value="#{row.bindings.desiredDeliveryDate.inputValue}"
readOnly="#{row.activeYN == 'N'}">
<af:forEach var="item"
items="#{viewScope.GrowerOrderBean.selectItems}">
<af:selectItem label="#{item.label}" value="#{item.value}"/>
</af:forEach>
</af:selectOneChoice>
</af:column>
<af:column sortProperty="maturity" filterable="true"
sortable="true" headerText="Maturity" id="c5"
width="60"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive">
<div align="center">
<af:inputText value="#{row.bindings.maturity.inputValue}"
label="#{bindings.queryProductResponseType.hints.maturity.label}"
required="#{bindings.queryProductResponseType.hints.maturity.mandatory}"
columns="#{bindings.queryProductResponseType.hints.maturity.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.maturity.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.maturity.tooltip}"
id="it16" readOnly="true">
<f:validator binding="#{row.bindings.maturity.validator}"/>
</af:inputText>
</div>
</af:column>
<af:column sortProperty="technology" filterable="true"
sortable="true" headerText="Technology" id="c14"
rendered="true" filterFeatures="caseInsensitive">
<af:inputText value="#{row.bindings.technology.inputValue}"
label="#{bindings.queryProductResponseType.hints.technology.label}"
required="#{bindings.queryProductResponseType.hints.technology.mandatory}"
columns="#{bindings.queryProductResponseType.hints.technology.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.technology.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.technology.tooltip}"
id="it15" readOnly="true">
<f:validator binding="#{row.bindings.technology.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="prdLine" filterable="true"
sortable="true" headerText="Product Line" id="c6"
width="70"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive">
<af:inputText value="#{row.bindings.prdLine.inputValue}"
label="#{bindings.queryProductResponseType.hints.prdLine.label}"
required="#{bindings.queryProductResponseType.hints.prdLine.mandatory}"
columns="#{bindings.queryProductResponseType.hints.prdLine.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.prdLine.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.prdLine.tooltip}"
id="it12" readOnly="true">
<f:validator binding="#{row.bindings.prdLine.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="brandMktName" filterable="true"
sortable="true" headerText="Marketing Brand" id="c8"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive" width="80">
<af:inputText value="#{row.bindings.brandMktName.inputValue}"
label="#{bindings.queryProductResponseType.hints.brandMktName.label}"
required="#{bindings.queryProductResponseType.hints.brandMktName.mandatory}"
columns="#{bindings.queryProductResponseType.hints.brandMktName.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.brandMktName.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.brandMktName.tooltip}"
id="it17" readOnly="true">
<f:validator binding="#{row.bindings.brandMktName.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="itemID" filterable="true" sortable="true"
headerText="Item#" id="c1"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive" width="60">
<af:inputText value="#{row.bindings.itemID.inputValue}"
label="#{bindings.queryProductResponseType.hints.itemID.label}"
required="#{bindings.queryProductResponseType.hints.itemID.mandatory}"
columns="#{bindings.queryProductResponseType.hints.itemID.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.itemID.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.itemID.tooltip}"
id="it6" readOnly="true">
<f:validator binding="#{row.bindings.itemID.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="descp" filterable="true" sortable="true"
headerText="Description" id="c17" width="105"
rendered="#{row.bindings.booleanFlag.inputValue != 'E'}"
filterFeatures="caseInsensitive">
<af:inputText value="#{row.bindings.descp.inputValue}"
label="#{bindings.queryProductResponseType.hints.descp.label}"
required="#{bindings.queryProductResponseType.hints.descp.mandatory}"
columns="#{bindings.queryProductResponseType.hints.descp.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.descp.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.descp.tooltip}"
id="it10" readOnly="true">
<f:validator binding="#{row.bindings.descp.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="primaryUOM" filterable="true"
sortable="true"
headerText="#{bindings.queryProductResponseType.hints.primaryUOM.label}"
id="c16" rendered="false"
filterFeatures="caseInsensitive">
<af:inputText value="#{row.bindings.primaryUOM.inputValue}"
label="#{bindings.queryProductResponseType.hints.primaryUOM.label}"
required="#{bindings.queryProductResponseType.hints.primaryUOM.mandatory}"
columns="#{bindings.queryProductResponseType.hints.primaryUOM.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.primaryUOM.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.primaryUOM.tooltip}"
id="it18">
<f:validator binding="#{row.bindings.primaryUOM.validator}"/>
</af:inputText>
</af:column>
<af:column sortProperty="secondaryUOM" filterable="true"
sortable="true"
headerText="#{bindings.queryProductResponseType.hints.secondaryUOM.label}"
id="c12" rendered="false"
filterFeatures="caseInsensitive">
<af:inputText value="#{row.bindings.secondaryUOM.inputValue}"
label="#{bindings.queryProductResponseType.hints.secondaryUOM.label}"
required="#{bindings.queryProductResponseType.hints.secondaryUOM.mandatory}"
columns="#{bindings.queryProductResponseType.hints.secondaryUOM.displayWidth}"
maximumLength="#{bindings.queryProductResponseType.hints.secondaryUOM.precision}"
shortDesc="#{bindings.queryProductResponseType.hints.secondaryUOM.tooltip}"
id="it21">
<f:validator binding="#{row.bindings.secondaryUOM.validator}"/>
</af:inputText>
</af:column>
</af:table>
<af:spacer width="10" height="5" id="s7"/>
<af:toolbar id="t1">
<af:commandButton id="AddToOrderButton2"
actionListener="#{viewScope.GrowerOrderBean.addToOrder_action}"
partialSubmit="true"
styleClass="addToOrderButton">
<af:clientListener method="setFocus" type="action"/>
</af:commandButton>
</af:toolbar>
<f:facet name="context">
<af:group id="g1">
<af:spacer width="60" height="10" id="s1"/>
<af:commandButton id="cb4"
actionListener="#{viewScope.GrowerOrderBean.addToOrder_action}"
partialSubmit="true"
styleClass="addToOrderButton">
<af:clientListener method="setFocus" type="action"/>
</af:commandButton>
</af:group>
</f:facet>
<f:facet name="info"/>
<f:facet name="legend"/>
<f:facet name="menuBar"/>
<f:facet name="toolbar"/>
</af:panelHeader>
</jsp:root>
Please reply !!
Thanks.

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Adding the tax condition type after customer pays

Hi,
I have a strange situation.
The customer has payed the invoice amount and evrything is cleared and the complete Order to Cash cycle is complete.
Now my client wants to charge the customer with the tax amount (implemented later) on the invoice that is already been cleared.And that amount should as usual go to the tax G/L account. There are not many Condiiton types but just the base price condition type and tax condition type.
I have maintained a necessary condition record for MWST.
SAP transaction wise I am thinking to create a normal sales order of the invoice amount (Base + Tax condition type) and then complete the order to cash cycle.And once it is completed I would create a debit memo request and subsequent debit memo for the base price which would be adjusted later.
This will solve my basic purpose of Tax amount goin to the tax account.
This is only for few SO in the production
Please let me know in case anyone has a better idea.

Hi ronaldo
You create a sales order with document type L2 ( debit process) . so you create the sales order with reference to billing . Now manually you enter the tax condition type (MWST) at the sales order level and then do billing.Make sure that in the tax condition type details you have maintained the option C "Manual entries are possible" .So that you can enter the the tax condition type manually at the sales order level.
So some additional taxes are being charged to the payer.So he will be paying some extra taxes as he has already paid for the billing document that has been passed to FI
Regards
Srinath

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

How to copy the Pricing conditions from one Distribution Channel to another

Generally we use VK11 transaction to create conditional records .
but I Need to Know whether is it Possible to copy the Pricing conditions from one Distribution Channel to another with same name and same internal Characteristics .
Since we have around 70+ of Condition type with different parameter Sequence.So Instead of Going for BDC whether is there any standard Funct Modules/programs/BAPIs to do this?
How to make a copy Condition types from One Distribution Channel to another.
since SAP has already provided to copy conditions from Customer to customer.
Likewise i need to know whether SAP is facilitating for these feature also.
Iam Dubious in this issue.
Hope Fully looking for the answers.
Harish.N

- IDOC_INPUT_COND_A (you can create IDOC, but also call directly)
- call transaction / batch input (use transaction XK15, as used by LSMW)
- use group of function modules RV_CONDITION_COPY, RV_CONDITION_SAVE, RV_CONDITION_RESET + commit.
if you search SDN on 'RV_CONDITION_COPY' you'll find more info I believe.
Someone mentioned BAPI_PRICE_CONDITIONS as well.

How to make the pricing condition to be displayed in print

Hi all,
Please let me know how to print the pricing element in the print of the purchase orders
Thanks in Advance
Kumar

Hi
For this you have to mark "X" for the print field of the specific condition type in the pricing procedure.
warm regards
sairam

How to implement the Reference Condition Type

Similar Messages

Maybe you are looking for