Watching price condition in sales order during configuration product

Hello evrybody,
I have a little question about product configuration during the sales order creation.
I have done all my configuration structure and I have add prices on certain characteristics.
However, I would like to see the price of each value of characteristic when I click on the matchcode to select the component what I need (column Condition scheduled to dysplay "Pricing information on a value").
Can you help me please ?
Thanks a lot for your help !!!
Thierry

Hi Rieu,
I believe you are referring F4 to display the prices values instead of the conditions. You need two notes to avail the functionality. Notes 1259021 (VC ) and 1267335 (SD). If you want the values to be shown then please ensure that c_condition_price is set to X in INCLUDE LCEI0FS4
Regards
Amber
SAP Support

Similar Messages

Creation of IBase with reference to sales order for Configurable product.

Hi Experts,
Can any one tell me How to create Ibase with reference to sales order for Configurable Products. I know we can create this using IB63, but what i need to do in this Transaction code and what settings i need to do in SPRO.
pls send ur replies to [email protected]
Thank you..

Hi
You can create IBase using T-Code-IB53 and in there you can give Parent and child products.
A)Define Installed Base Category and Installation Rules-CRM
B)Define Object Families
C)Define default settings for equipment replication
D)Define Serial Number Profiles-ECC
E)Txn BF31-ECC
F)Set up attributes for individual objects
G)Set up set types
H)Set up category
I)Set up views
J)Allow reference product for IO
I hope it helps
If you require further help let me know.
Cheers
Raj

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

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

Add price conditions in sales order and purchase orders

Hi,
I need add five price conditions in a sales order, and a purchase order.
I need filled KOMV table, however, i don't found the user-exits appropiated (example: the exit EXIT_SAPLMEKO_002 haven't parameter KOMV),
Regards,

Quite a few years ago I did something like this in sales orders... found the code in my notes, here it is.
I used USEREXIT_PRICING_PREPARE_TKOMP in include RV60AFZZ.
* Check if this condition record exists already
read table xkomv with key kschl = c_condition_name
                            kherk = 'C'             "(depending on the task)
                            kposn = vbap-posnr.
if syst-subrc ne 0.   "condition wasn't added yet
      clear xkomv.
      xkomv-kschl = c_condition_type.
      xkomv-kbetr = condition_amount.
      call function 'PRICING_CHECK'
        exporting
          comm_head_i = tkomk
          comm_item_i = tkomp
          komv_i      = xkomv
          preliminary = 'X'
        importing
          comm_head_e = tkomk
          comm_item_e = tkomp
          komv_e      = xkomv.
      xkomv-KWERT = xkomv-kbetr.
      append xkomv.
endif.
Keep in mind that I haven't used this logic for years, so you'll have to test if it still works, but it worked for me back then.
If I'd have to do this now, I'd probably try to find a suitable enhancement point though...

Specific Price conditions at Sales Order level

Dear Gurus,
We have introduced some Pricing conditions and their calculations at Sales Order level and we have made it to appear at the Sales Order Output which is for Internal reference.
We dont want the Pricing conditions to be shown in Customer Invoice.
Kindly advise.
Regards,
RK

Create the new Document Pricing procedure of the Billing Type & don't assign the Document Pricing Procedure to the Sales Area / Document Pricing procedure / customer Pricing procedure.
Best Regards,
Ankur

How to import (create) a sales order of configured product from third party web store

Background:
EBS is used for order, produce, deliver and invoice configured products. Oracle configurator is in internal use.
Screnario:
Start to use third party web store. Configuration information will be loaded into web store.
How to import or insert orders done in web store so that configuration information is equal to orders entered firectly into OM (with configuration)?
Any experiences or examples are welcome.

.There is some documentation on this on Metalink. See:
Importing Configurations [ID 411880.1]

Net Price of a Sales Order

Hi All,
In standard system the net price of a sales order is given by the condition type PR00. Is it possible to change the source of net price to customer-defined condition type like ZFMA?
Thanks + Best Regards
Jerome

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type 'PR00' & copy as 'ZMFA'.
General process for configuring pricing procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
Step 5.
Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Regards,
Rajesh Banka
Reward points if helpful.

Price change summary report & approach of price change on Sales Orders

Hi,
I have made the setups for updating the price on Sales Order via profile options (i update the list price field on SO line the SO line price gets updated). The Customer have manual price overide in their existing system in place so they want same in oracle system as well. Their price change doesn't have any serious logic,,it is quite erratic based on market condition on that day.
(1) How can I get the report fro the changed price wrt price on price list for all the items on Sales Orders (during a period). It seems, Audit trial functionality for changing list price is not available.
(2) For the system whether required price change as above is better approach or maintaining new price list all the time is preferable option. In case of new price list, do we have any standard report which fetches itemwise price change details on Sales Orders for a period.
Thanks.
With Best Regards,
Nirabh Nayan

Nirabh,
Did you say you update the List Price itself in the Order Lines? In my opinion you should never update List Price. Set the profile OM: Discounting Privilege to 'Unlimited' to allow update of Selling Price, but switch off 'OM: List Price Override Privilege' for the responsibilities so that List Price field is not Editable. So that List Price always reflect the price with which Order Line was created (From the price List). Now create a custom report wherever Unit Selling Price does not match Unit List Price.
If you really want to go a little further then create a modifier with Application method 'New Price' that should kick in everytime the Unit Selling Price is updated. Let me know if that helped.
Dipanjan
Edited by: Dipanjan Maitra on May 25, 2012 2:25 PM

How to change pricing Conditions in Sales order in change sales order bapi

Hi Experts,
How to change pricing Conditions in Sales order in change sales order bapi.
I have used the 2 function modules bapi-changesalesorder and sd salesdocument change, But it is creating the new record , instead of changing the existing one, Could please assist regarding the same
Thanks in Advance .
NLN

HI NLN
I have just tried on my system and managed to overwrite the existing price by passing the following parameters.
Import Paramters:
 SALESDOCUMENT - Sales Document Number
 ORDER_HEADER_INX - UPDATEFLAG as 'U'.
 LOGIC_SWITCH - Import Structure - Pass 'X' to LOGIC_SWITCH-COND_HANDL.
Tables:
 CONDITIONS_IN - ITM_NUMBER,
 COND_COUNT, -> Condition counter same as KONV-ZAEHK generally it is '01'
 COND_TYPE,
 COND_VALUE,
 CURRENCY.
 CONDITIONS_INX - ITM_NUMBER,
 COND_COUNT,
 COND_TYPE,
 UPDATEFLAG as 'U',
 CURRENCY.
 Hope i have clarified your query.
Kind Regards
Eswar

Final price of the Sales Order calculation on payment term

Hi,
Out Business requirement as follows.
1) one ZNAP pricing condition will be maintained by the monthly wise by business for pricing. this is a statistical condition only checking at sales order level only. this condition will check with Final price of the Sales order.
Now the requirement is
1) based on payment term of the Sales Order. plus if its a credit payment if the its CASH payment. these deduction should be added to ZNAP condition, and same will calculate with Final price, while creating Sales order.
For Example:
ZANP condition maintained 1000 USD.
while creating the SO:
If the payment term of the customer: PT30, ( it means payment with be in 30 days of the bill creation date)
system should do the below calculations
1) Scenario
Sales Order: Final price :                                       1500 USD( maintained by the Sales User while creating the SO)
ZNAP price                      :                                    1000 USD
according payment term 30 days                            20 USD ( as per table maintenance for calculation of the payment term.)
Calcuation:                                                          1000+20= 1020 (approximate need to add as interest rate)
Then final it should display final price 1500-1020= 480 USD.
2) Scenario:
If the payment term Cash:
ZNAP                                                            : 1000 - 20= 980 ( approximately and deduct, from the condition due to cash payment its like discount)
calucalte"                                                       1500-980= 520 difference
this purely internal pricing calculation with final price...
pl let me know how to get this in the pricing. and payment could be 30 days, 45 days 60 days etc.
Thanks.

Hi M Sham,
I believe your requirement can not be met with Standard pricing and you will have to create Routines for getting this result.
From scenario I believe you will be doing below points:
You should Create Z-Table with Payment Term and respective rates against those payment Term.
You should create a statistical condition type(Ex. ZNP1) and create Calculation Type routine with Logic to get KOMK-ZTERM field and derive value from Z-Table and update XKWERT field.
Calculate addition of ZNAP and ZNP1 (With +ve or -ve Signs)
And then again make deduction of derived value from Finale Value.
Do let me know if I have misunderstood your question.
Regards,
MJ.

Price chnage at sales order level but not in billing

Hi
I want to maintain the price manually in sales order but donot want to allow user to change the price in billing. I understand it is controlled at condition type level but not at document level.
Need your advise as to how we an achieve it.
Regards,
Neeraj Srivastava

Hi Neeraj,
You can achieve this by following below setting:
Go to into the condition for which you want to maintain price manually.
put C in manual entry field.
Set check mark for Header cond., Item cond & Delete only. Remove check mark for Amount/percent & value. Save it.
Go to pricing procedure and mark this condition for manual entry and mandatory.
Only thing in this is you need to put this condition in sales order manually & maintain price for this condition before pressing "Enter". Once you press "Enter" it will go in gray mode.
Ramchandra

Expected Price ED1 EDI2 Sales Order & Incompletion issues re: Delivery/Bill

Hi,
We are using ED1 and EDI2 conditions for expected price on the sales order to trigger incompletion. This works fine, and it's possible to use V.25 to release or manually adjust the pricing conditions to match.
However we have problems in the way it is working re: Header/Item - if say we have two lines, line10 EDI1/2 prices are ok, complete; line 20 EDI1/2 conditions also added but incorrect and therefore incomplete.
Now when user trys to create a Delivery - they can create a delivery for line 10 but the line 20 errors because it is incomplete. This at line level would be ok, if we could subsequently Bill this line, but doing this through VF01 errors because of message 'VF055 (VF)055 Pricing error in document'
The only way to clear it is to clear line 10 on the sales order, say V.25 which then allows Line 10 to also be Delivered and Billed.
The above is with incompletion status group 06 which should prevent Delivery & Billing. Alternatively we could use Incompletion status 02, which blocks Delivery but allows Billing.
However this is inconsistant with the EDI1/2 conditions - Delivery seems to be blocked at the Item Level, but Billing at Header Level.
Is there a solution? Ideally we want the either:-
i) Delivery to prevented if any line is incomplete for EDI1/2, or
ii) Billing to be prevented only if the line Billed on the Delivery is incomplete on the Sales Order, not any line.
Any advice appreciated.

Hi,
I suggest you check copy control (delivery->billing) at item level in tr. VTFL.
Do you use standard routine in 'copying requirements' ? If needed you can also create custom routine that would not raise error for your scenario.
Regards,
Dominik Modrzejewski

Price in the Sales Order

Dear SD,
Normallly we enterd the Price in the Sales Order for a Finished Goods. Is there any other way, that Sales Order Directly Picks the Cost from Pricing Procedure.
REgards

Hi,
I understood that you need the following clarifications.
1.     VPRS: This is cost price. For example, you are doing trading business and you buy an item for Rs. 125. This is cost price. This price is maintained in material master in Accounting view in the field Standard Price.
2.     PR00: This is selling price. This includes the profit. In this example, say it is 200. This is maintained in Condition records. The transaction code is VK11.
3.     Pricing Procedure: Both of the condition types (VPRS, PR00) are maintained in the pricing procedure. Please check the standard pricing procedure RVAA01.
If the condition type is not maintained in your pricing procedure, you can add the condition type VPRS in your pricing procedure and assign the requirement as 4 (Cost). Enter tick mark in u2018Statisticsu2019.
If you create a sales order, you will get the value of PR00 (selling price) and the Cost price (VPRS) in the sales order. Sales order is a document that can be sent to the customer to confirm the sales. So, here you do not want to show the cost price of the item. That is why the condition is not selected for print. If you are dealing with your associate companies and you want to print the cost price in the sales order, you can print the cost price VPRS in the sales order. To do this, select u2018Xu2019 in print column of the pricing procedure for Condition type VPRS. Hereafter you can print the cost price of the item in the sales order. But it should be printed appropriately with the help of an ABAPer.
4.     VPRS u2013 Statistical: VPRS is always maintained as statistical. This is not used for updating financial entries while creating billing; but it is used to find the profit margin. Whenever the cost price of the material changes, we have to update the cost price (VPRS) by transaction code MR21.
5.     Stock value: While calculating warehouse stock by transaction code MB52, the system takes the value given in the material master in accounting view. The value shown in VPRS and Value taken for stock valuation are one and same. Stocks are evaluated on cost price; not on selling price.
Hope this information will be useful to you.
Regards,
K Bharathi

Bottom/base price check in Sales order processing

Hi
In my company we are using process Sales Order > DO > Billing. Same pricing procedure for sales document types and billing types. No pricing procedure for DO. Our management wants to implement bottom price check in sales order processing e.g there must be one sale price on which sale invoice will be booked and there must also be one static price maintained and system will check after all taxes and discounts calculation that net value should not be less then bottom price.
Currently we are using user exit in enhancement MV45AFZZ. Our ABAPER has written logic in this of following scenario. We have maintained commercial price in ZCOM condition type and bottom price in ZBAS condition type. Lets take and example
ZCOM = Sale price= 500
ZDIS = Discount = 100
Net value/Amount for credit check 500-100 = 400
ZBAS Bottom price = 450
In above scenario system should not allow to save sale order/billing document and give error "Sale price is below bottom price" Then user will change the discount from 100 to 50 and Net value will be then 450 and system will allow to save sale order/billing document.
I want to to do this in Pricing procedure pricing routines. Please tell me is it possible with calculation types? Im wondering if we can do this in enhancement then we must write the same logic in VOFM pricing routine and we can control this from there too. In our current ABAP check everything is working fine but I just want to minimize the use of ABAP checks and enhancements and control the things from functional side not from ABAP.
Please let me know if someone need more clarification or someone have any productive suggestions in this regard. If there is any other solution it will be highly appreciated.
Thanks in advance.

Similar functionality is already there, where if the net price of an item differs from "Customer expected price" (conditions EDI1/EDI2) then SAP automatically pushes the order into incompletion. You can ask the developer to see how EDI1 is used in the pricing logic.
However, the condition EDI1 is used to check if the item value is different to Customer expected price in case of EDI orders and is not standard for your requirement. But you get my drift, that you can have your own condition in the pricing procedure that will fetch the base price value and can be used in the logic to show an error message (to stop order processing) or push into incompletion log similar to condition EDI1

Watching price condition in sales order during configuration product

Similar Messages

Maybe you are looking for