Idoc ORDERS PRICE CONDITIONS

Hi Experts,
I'm facing a problem.
I have to load some Idoc of type ORDERS05 into the system, but I'm not able to pass to the order the pricing conditions.
They are manual conditions and percentage. I'm using segment E1EDP05.
Please let me know how to fill this segment to achieve the correct result.
Thanks in advance,
Paolo F.C.

Usually the processing of the conditions in the ORDERS-IDoc is ignored or fails completely. The reason is, that many companies do not want to accept random conditions sent by their customers. Just imagine you give your stuff away for free.
So usually the SAP system calculates the conditions for your customers and materials automatically. So maintain the conditions in your master data is the best practice.
Anyway you can alter this.
Pricing conditions need to be configured to allow manual update via an incoming ORDERS05.
See also:
http://help.sap.com/saphelp_46c/helpdata/en/12/084c0a470311d1894a0000e8323352/frameset.htm
Make sure you enable the condition type for manual entries and disable the pricing sequences or better: set the condition type to be the last condition type so the SAP system does not override your condition type. To avoid side effects it is necessary to use this condition type just for the IDoc ORDERS in an exclusive way.
In case this has already been done or the condition processing in your IDoc is already enabled make sure you fill the following fields in the E1EDP05 Segment:
ALCKZ
KSCHL
BETRG or KRATE
See transaction WE60 for IDoc documentation and detailed values for those fields.

Similar Messages

Sales order: price condition not working when i change the sold to party

Hi guys,
I've a strange problem by making the following steps:
1. Create a sales order:
By VA01 i create an order by filling the SOLD TO and one material - all OK. The price is calculated correctly.
2. Change SOLD TO:
I change the sold to by filling another payer that has a different price list (PLTYP) - the price is not re-calculated
If i change with another payer with the same price list everything is ok.
Can you tell me what could be the problem?
Many thanks

Did you actually change the sold-to party though or just the payer? The sold-to party's price list type controls the price list type value copied into the order header. Even if the payer has a different value, it's not copied to the order header. You can see this behavior in FV45KFKD_VBKD_FUELLEN. If you switch sold-to's then you should get a pop-up that new pricing was carried out; you should also see your new price list type value in the order header and you can use the 'analysis' function at the item level to verify that the correct price was used.

R/3 Order price reset on changes in CRM

Dear Experts,
I'd like to ask you about pricing synchronization problem.
At my company, sales order created in CRM 4.0 will be distributed to R/3 ECC 6.0.
R/3 sales order price conditions are not similar with CRM sales order price condition. Not all of R/3 pricing conditions exist in CRM due to complexities in R/3 rate determination.
The problem is whenever changes are made in CRM SO Document , the pricing will be transferred to R/3 SO, but in the same time other pricing components in R/3 SO will be reset to zero by SAP function SD_SALES_ITEM_MAINTAIN .
Beside creating similar price conditions in both CRM and R/3, is there any configuration to enable price synchronization without changing the pricing conditions that are not similar ?
Thank you in advance,
TS Winedya

Hi Satish,
Go to BP transaction click Extras --> change history --> for this partner
you will get all the changes done for this partner. select any one of the field from pop-up press enter, you will get detailed report.
Reward if it helps
Regards,
Srinivas Maddineni

Price conditions on Sales Orders via EDI

Hi,
I need to know if there is a way to bring prices over on the IDOC while posting a sales order via EDI. I have a situation where the price does not have to be determined based on condition records setup within SAP but rather update the price sent on the IDOC itself.
Thanks
MR

Hi,
Let the inbound Idoc have the price field and the price of the material. And keep the price condition type open/manual entry allowed. Once this is done the system will not do it from the condition record and will populate the data that is there in the Idoc.
Hope this helps.
Kind Regards
Chakradhar

How to avoid user from entering new price condition in return order

Dear Expert
We are facing a scenario where we make return order; the Price is copied from the invoice. And it is working perfectly. The system does not allow us to change the price.
The issue we are facing here is that user can input new condition like discount /premium and change the net value for the return order pricing, and this will reflect in the credit note for returns.
Is there a way to restrict the user from entering any pricing condition in the header or item conditions tab.
although we cannot change the original price coming from invoice referenced for return order, but the user can input new price conditions as below. This must not be allowed.
The price must come according to the Qty being referenced.
While making the credit for returns, the user has a chance of further making changes to the net value by adding new conditions. Hence this must also be restricted for any changes.
Thanks
Edited by: Lakshmipathi on Jan 31, 2012 6:55 PM
Thread Locked - Reason Cross Post

okie .... i will tell briefly what is the problem ....
Take a scenario wherein a user has logged into my application and he is performing a task which will put his user id and his employee id into the session. Then he opens another window by using either ctrl+n or through files->new window.
So now a new browser will open but the session will be same ..... in this newly opened browser, user performs some operation which will remove the user id and employee id from the session .... Now if he again comes back to the first window and tries to do some operation, then a null pointer exception will be thrown saying that the employee id is null .... because he has deleted that in the newly created browser ..... to avoid this situation what can we do ???? can you please help me in this regard ??? you got my problem right !!!

Two prices for one material in sales order according condition type

Hi,
I configure the condition type according to following condition record:
Plant/ Sales Organization/ Distribution channel/ Material / Customer
(because system should calculate two prices for one material in two plants)
In the sales order screen, when user firstly select material , quantity, plant , system calculate the related price correctly but if user select the material and quantity and enter and after that select the plant, system will show the error message in pricing procedure and to have a price for material, user should update the price in the price condition in sales order.
It is so difficult for user to update one by one, because there are several sales orders which need to update.
Is it any way to solve this problem?
Thanks,

> In the sales order screen, when user firstly select material , quantity, plant , system calculate the related price correctly but if user select the material and quantity and enter and after that select the plant, system will show the error message in pricing
Hi,
Why to let the user press Enter button before entering plant value Obviously, system will give error, because it doesnt get all the required value based on which you have maintained condition records.
Ask the user to enter all the value at item level otherwise you will have go for the option that you are doing currently.
It is said prevention is better than cure
Hope you get some inputs
regards,
Sagar

Changing Price Conditions in Sales Order with SD_SALESDOCUMENT_CHANGE

Hello there!
I need to change the value of a price condition in a sale order ;I'm using the f.m. SD_SALESDOCUMENT_CHANGE.
It doesnt' work as I want, 'cause it creates an other price conditions instead of just changing the price value of the actual one.
Waiting for your tips,
thanks.
This is how my code looks like:
PARAMETER: p_vbeln LIKE vbak-vbeln.
data: st_order_header_inx   TYPE bapisdhd1x,
        st_conditions LIKE bapicond,
        st_conditionsx LIKE bapicondx,
        tb_conditions TYPE TABLE OF bapicond,
        tb_conditionsx TYPE TABLE OF bapicondx,
        tb_return TYPE TABLE OF bapiret2.
st_order_header_inx-updateflag = 'U'.
st_conditions-itm_number = '0010'.
st_conditions-cond_type = 'PR00'.
st_conditions-cond_updat = 'X'.
st_conditions-cond_value = '100'. "Value I want to enter
APPEND st_conditions TO tb_conditions.
st_conditionsx-itm_number = '0010'.
st_conditionsx-cond_type = 'PR00'.
st_conditionsx-updateflag = 'U'.
st_conditionsx-cond_value = 'X'.
APPEND ls_conditionsx TO tb_conditionsx.
CALL FUNCTION 'SD_SALESDOCUMENT_CHANGE'
    EXPORTING
    salesdocument                = p_vbeln
      order_header_inx          = st_order_header_inx
    TABLES
      return                           = tb_return
      conditions_in               = tb_conditions
      conditions_inx              = tb_conditionsx .

Get the conditions records first from the Sales Order with BAPI BAPISDORDER_GETDETAILEDLIST
CALL FUNCTION 'BAPISDORDER_GETDETAILEDLIST'
EXPORTING
    i_bapi_view          = lw_bapi_view
TABLES
    sales_documents      = lt_order
    order_conditions_out = lt_conditions_out.
Then populate the conditions internal table with the data that you get from the previous code
move-corresponding lw_conditions_out to lw_order_conditions_in.
lw_order_conditions_in-cond_value = '100'   " the value that you want to modify
APPEND lw_order_conditions_in TO lt_order_conditions_in.
CLEAR lw_order_conditions_inx.
lw_order_conditions_inx-itm_number = lv_kposn.
lw_order_conditions_inx-cond_st_no = lw_conditions_out-cond_st_no.
lw_order_conditions_inx-cond_count = lw_conditions_out-cond_count.
lw_order_conditions_inx-cond_type = lw_conditions_out-cond_type.
lw_order_conditions_inx-updateflag = 'U'.
lw_order_conditions_inx-cond_value = lc_x.
APPEND lw_order_conditions_inx TO lt_order_conditions_inx.
You didn't populate the fields cond_st_no and -cond_count. Then just call BAPI SD_SALESDOCUMENT_CHANGE to change the Sales order.
Hope that helps.
Erwin

How to limit the number of price conditions in a sales order

Dear experts,
We've created discounts in our pricing procedure, and they are added manually. They have a maximum.
But the problem is that the user can add several discount price conditions in the sales order!
Is there any customizing to limit the number of occurrences to 1 in the pricing procedure?
Thank you for your help
Marjolaine

HI,
You can make use of feature to maintain maximum and minimum limits per condition type.
SPRO > SAP Implementation Guide > Customer Relationship Management > Basic Functions > Pricing > Define Settings for Pricing > Create Minimum/Maximum Limits
In this activity you can restrict manual processing of pricing conditions in transactions using minimum and maximum limits per condition type.
Kindly reward with points in case helpful
Sharif

How to block post price conditions in purchase order

I need to block post price conditions in the purchase order, after doing MIGO.
The problem is that somtimes buyers people go to the purachse order with ME22N, even if MIGO has already been made for this purachse order. They change The amount of certain price conditions in some or all the posts of the purchase. when people of accounting receive the invoice, there are problems of price differences.
i need help to do it
Thank you in advance for your help

The system will not allow to change the price once goods receipt takes place on that particular order. It happens only when we reverse the reciepts and make the po open. In such case the persons can change with ME22N. Its simple that only authorised user to have this transaction code and other users should not have this transaction code authorization.

Manual price condition (%) in order creation (using ABAP)

Dear community members,
I could use some help on a problem I have encountered while creating a sales order (in the CRM system) using ABAP programming, the details are given hereunder:
I have two manual price conditions used to set a possible discount, one using a straight value and one using a percentage:
1. When the order is generated using the value (let us say 100€) it cointains the correct price condition.
2. On the other hand, when the order is generated using percentages (i.e. 10%), it is created without explicit errors or warnings but with no price condition in it.
For the latter case I have checked the IPC logs (from transaction SM53) finding this error message:
Message: Condition cannot be processed manually
--> com.sap.spe.pricing.transactiondata.exc.ManualChangeNotAllowedException: Condition YSCP cannot be processed manually
at com.sap.spe.pricing.transactiondata.impl.PricingCondition.changeConditionRate(Ljava/math/BigDecimal;Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;)V(PricingCondition.java:3124)
at com.sap.spe.pricing.transactiondata.impl.HeaderCondition.changeConditionRate(Ljava/math/BigDecimal;Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;)V(HeaderCondition.java:387)
at com.sap.spe.pricing.transactiondata.impl.PricingDocument.addHeaderCondition(Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;Ljava/math/BigDecimal;Ljava/lang/String;C)Lcom/sap/spe/pricing/transactiondata/IHeaderCondition;(PricingDocument.java :1472)
at com.sap.spe.document.rfc.AddPricingConditions.handleDocRequest()V(AddPricingConditions.java:131)
at com.sap.spe.document.rfc.DocHandlerAdapter.handleRequest()V(DocHandlerAdapter.java:72)
at com.sap.spe.base.util.jco.HandlerAdapter.handleRequest(Lcom/sap/vmc/RFCContainer/Call;)V(HandlerAdapter.java:117)
at com.sap.vmc.remserver.RFCDispatcher.handleRequest2(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:995)
at com.sap.vmc.remserver.RFCDispatcher.handleRequest(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:746)
at com.sap.conn.jco.rt.VMCServer.dispatchRequest(Lcom/sap/conn/jco/JCoFunction;)V(VMCServer.java:911)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(Lcom/sap/conn/jco/rt/ServerWorker;Ljava/lang/String;)V(MiddlewareJavaRfc.java:3415)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(Lcom/sap/conn/jco/rt/ServerWorker;)V(MiddlewareJavaRfc.java:2468)
at com.sap.conn.jco.rt.VMCServer.listen()V(VMCServer.java:766)
at com.sap.conn.jco.rt.VMCServer.run()V(VMCServer.java:689)
at com.sap.vmc.remserver.RfcServer.run()V(RfcServer.java:376)
at java.lang.Thread.startup(Z)V(Thread.java:1954)
I have already debugged FM CRM_ORDER_MAINTAIN but to no avail, maybe I just missed something and I can assure that the customizing is correct and aligned between the systems and both the conditions are set to be processed manually.
At this point, since the condition is applied when the commit is yet to be done I wonder whether it is possible to apply a discount percentage on prices which are yet to be generated, it would be illogical to do so and then again while using a straight value (which does not require a calculation) the order is correctly generated.
Furthermore when I add the conditions in an order (from both the GUI and the WUI) the table IT_PRIDOC is alway empty, even if CT_INPUT_FIELD is populated.
I know that there are similar posts here in SCN but sadly I was not able to find a solution so any help would be greatly appreciated.
Thanks in advance for any replies given,
Alessandro.

Dear Padma,
apologies for my late reply. I also thought it should be possible to use a percentage but I was not sure.
Sadly the debugging did not bring about any positive result.
I also tried to make a second CRM_ORDER_MAINTAIN call after the system generated all the pricing conditions but that also did not work.
There is one thing that caught my attention though:
- YSCV (fixed amount): still no problem at all (passed to KBETR);
- YSCP (percent): if I assign a value to KWERT or if I leave all the fields empty, the condition is created in the sales order but it is always set to 0%. However, if I try to assign it to KBETR, I always get the message: "Condition YSCP cannot be processed manually".
I made some attempts with the customizing, for example adding the condition to the "easy entries" or playing with the options of "Create Condition Types" (always aligning the systems) without getting positive output.
I am beginning to think that it could be an IPC-related problem (which is not my area of expertise... yet).
Alessandro.

How to block post price conditions in purchase order after doing MIGO

I need to block post price conditions in the purchase order, after doing MIGO.
The problem is that somtimes buyers people go to the purachse order with ME22N, even if MIGO has already been made for this purachse order. They change The amount of certain price conditions in some or all the posts of the purchase. when people of accounting receive the invoice, there are problems of price differences.
i need help to do it
Thank you in advance for your help

The system will not allow to change the price once goods receipt takes place on that particular order. It happens only when we reverse the reciepts and make the po open. In such case the persons can change with ME22N. Its simple that only authorised user to have this transaction code and other users should not have this transaction code authorization.

Restrict new price conditions in the return order and credit note

Dear Expert
We are facing a scenario where we make return order; the Price is copied from the invoice. And it is working perfectly. The system does not allow us to change the price.
The issue we are facing here is that user can input new condition like discount /premium and change the net value for the return order pricing, and this will reflect in the credit note for returns.
Is there a way to restrict the user from entering any pricing condition in the header or item conditions tab.
although we cannot change the original price coming from invoice referenced for return order, but the user can input new price conditions as below. This must not be allowed.
The price must come according to the Qty being referenced.
While making the credit for returns, the user has a chance of further making changes to the net value by adding new conditions. Hence this must also be restricted for any changes.
Thanks

Hi
Firstly,In copy control maintain anyone of the pricing types
D: Copy pricing elements unchanged
E: Copy pricing elements and values unchanged
To avoid all these things go with USEREXIT_FIELD_MODIFICATION but before going with the user exit,also check with transaction variant SHD0.
Regards
Srinath

ABAP: How to add a Price Condition Item to an order item

Hi experts,
Is it possible to add a Price Condition Item to an order item by BAPI or Function in sap crm? (like: 0k04 10 USD 1 EA)

Hi,
You need to use CRM_ORDER_MAINTAIN and have to use structure IT_PRIDOC to update or add new pricing data.
But do remember, you have to call FM 'BAPI_TRANSACTION_COMMIT' once you are done with call to FM CRM_ORDER_MAINTAIN, else all your updation will remain in buffer and will have no effect in Database, which will let u feel as if things are not working they should be.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

CRM 5.0 ISA insert new price condition from order entry screen

In CRM 4.0 we wrote a custom field on the order entry screen that shows the list price (sub 1), we allow the user to change this value (inserts a PB00 price condition in the item pricing) and validates the change is within a certain % of the list price.
The jco method we used in 4.0 no longer exist in 5.0, been using the 55 page IPC VMC PDF in note 809820 but still can't figure out how to replicate.
Any help on what class / method might help us insert a manual price condition from ISA would be appreciated.

It could be possible to use CRM BAdI to do this function.

IS-MAM: using statistical price condition in the order

Hi all
In this period, I am involved in a job project to an Advertising Management company.
The sales process implies the revenue recognition occurs when the advertisement is published (publishing doesn't temporally concide with invoicing).
After publishing, it is necessary to introduce a billing plan in order to split the sales order amount in a predefined number of billing with a predifined amount.
In order to determine the right amount for billing, We thought to apply the following SAP solution:
- to add in an order a statistic price condition relevant just for billing and not for relevat recognition.
Through test cases, we verified that this statistical price condition determines
a delta position in account determination.
is this a standard SAP functionality? should be possible to avoid a new account determination in revenues accounts?
Thanks in advance for your help
Best Regards, Lucia

Hi,
the path to define the access sequence is
IMG>>>MM>>>Purchasing>>>>Conditions.>>>>Define price determination process>>>define access sequence (M/07).
for this you can actually use the existing ones which suits your condition records level. otherwise create a new table for it and then use it in the access sequence.
then assign this access sequence to your condition type in M/06.
for your reference
Step to create new access sequence
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm

Idoc ORDERS PRICE CONDITIONS

Similar Messages

Maybe you are looking for