Price mandatory in sales order

Hi SAP Experts,
I want to make price ( PR00) mandatory in sales order . The sales order should not be allowed to save with out the price. How do I achieve this? I have made the following setting.
1. Made PR00 mandatory in pricing procedure.
2. Assigned an incompletion log at the item level with screen PKON and status 06
but I still can save my sales order.
Kindly help
Beena

Hi Beena,
You have done it right by making the Condition Type PR00 as Mandatory in the Pricing Procedure and also using the Item Condition PKON in the Incompletion log.
All you need to do is in the same Incompletion log mark the field as WARNING.
Hope this works for you.
REWARD if it helps you!!
Regards,
Ajinkya

Similar Messages

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

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.

How To Add a new column for ZPR0 price in open sales order report ??

HI,
my requirement is To Add a new column for ZPR0 price in open sales order report if the order/scheduling agreement is a cross-company code transaction l(company code of order/scheduling agreement <> company code of delivering plant), price = ZPR0 price as at estimated GI date

k

Sales Area mandatory in sales order

Dear Sir,
I want to make Sales area as mandatory in sales order and Inquiry .
When we enter T. code VA01, in initial screen of sales order, without entering sales order document type in sales order VA01, system does not allow to process further.
In the same way I want to make sales area should be mandatory, system should not allow to enter in 2nd screen without entering sales area.
Waiting for your reply.
With Regards
Mamta

Dear Mamatha,
Even if you don't enter the sales area data in the initial screen of VA01 transaction system will ask you to enter sales area data in the second screen of the VA01 transaction,here sales area data is mandatory only, you can't go further with out entering the sales area data.
But I don't know why you want that in the first screen itself.
I hope it will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Jul 10, 2008 10:00 AM

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.

How to make all fields mandatory in sales order T- code VA01 initial screen

Dear all,
how to make all fields mandatory in sales order T- code VA01 initial screen itself
The fields are
Sales Organization
Distribution Channel
Division
Sales Office
Sales Group
Regards,
Amar Reddy

Hi,
You can use Transaction Variant to achieve this functionality.Please go through the following link which helps you in creating the same.
[Link|http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation]
Regards,
Phani Prasad

Can we edit Gross Price field in Sales Order

Hi experts,
According Help document (help - under Sales A/R/Sales Order-Sales document content tab ) as follows, userwe should be able to edit gross price field in Sales order
Enter in this field the unit price including tax. SAP Business One calculates automatically the unit price before tax and the tax amount, based on the tax code in the row. After pressing the TAB key, the Unit Price field and the Tax/Unit field are updated accordingly.
The tax amount is calculated as follows:
*Gross Price / (1 + Tax %) * Tax % = Tax Amount*
But when I set up in form setting visible and active for Gross Price, though I AM NOT ABLE TO EDIT GROSS PRICE FIELD
Is it bug in SAP ? I
BR
Samir Gandhi

Hi Samir Gandhi,
You may check SAP Note Number: 1060666 to see if it applies to you.
Thanks,
Gordon

How to make field mandatory in Sales Order Item level?

Hi SDN's,
I need to make Shipping type field(Item level) mandatory in Sales order.
Can any one tell me what is the user-exit to achieve this?
Thanks in advance..
Regards,
Rahul

Rahul,
U can check the BADI 'BADI_SD_SALES_ITEM'
othewise u can check
Exit Program MV45AFZZ.
Check the program SAPMV45A
V45W0001
V46H0001

How to make a field profit center mandatory in sales order?

Dear GURUS,
Please help in getting answer for following question.
How to make a field profit center mandatory in sales order?
With Regards
Sandeep D.

Hi,
There are 2 ways to make profit center mandatory
1.Transaction Variant
2.Incompletion procedure
1.Transaction Variant
Step 1:Goto Tcode shd0 and input transaction as va01 and give name of transaction variant as ( example. zva01 ) and click on create or F5
Step 2.Then it takes you to sales order screen.Just click on enter untill you see profit center field.
Step 3.check the box required against profit center.
Step 4.click on save ( under a package name or as local object ) and exit
Step 5.Assign transaction variant to your sales order type through tcode v0v8.
2.Incompletion Procedure
You can add the field table-vbap,field- prctr,status-04,check-warning to your existing incompletion procedure Tcode- ova2 assigned to your order type in tcode vov8 and check the box - incomplete messeges for your order type through tcode vov8.
If incompletion procedure is not assigned to your order type than you have to create a new incompletion procedure and assign it to order type.

How to make tax classification field mandatory in sales order ?

Hi,
while creating sales order, " how to make tax classification field mandatory ".
Please tell me the procedure.
In tcode OVA2. what are the entries for fields,table.
Regards,
sapsduser

Dear ,
Could you please share why you want to make tax Classification field mandatory in sales order.
Maintain Tax classification field for customer in Customer Master Data = (Sales Area Data - Billing document Tab page)
Tax Classification field for Material in Material Master Data = Sales Org. 1 View.
While creating sales order and enter customer and material system automatically fetch the tax classification related data into sales order.
Tax is calculated based on the ship to party.
Hope this will help you.....
Regards,
Manoranjan.

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

Cannot set item's price in new sales order using E-Commerce for ByDesign.

Hello,
I'm working on a program to create zero value sales orders in my companies SAP system to help track warranties. Every portion of this program is straight forward except for setting an item's list price to zero. I'm using C# .NET. Below is my code to create the SalesOrderMaintainRequestItem. Any advice would be greatly appreciated.
private SalesOrderMaintainRequestItem[] GetItems(Warranty warranty) // Custom Warranty Object
 int count = warranty.LineItems.Count; // Warranty object has an array of line items
 SalesOrderMaintainRequestItem[] item = new SalesOrderMaintainRequestItem[count];
 for (int i = 0; i < count; i++) // for each line item in the warranty object
 item[i] = new SalesOrderMaintainRequestItem();
 item[i].BuyerID = _ID;
 item[i].ItemProduct = new SalesOrderMaintainRequestItemProduct();
 item[i].ItemProduct.ProductID = new NOCONVERSION_ProductID();
 item[i].ItemProduct.ProductID.Value = warranty.LineItems[i].ReplaceWith;
 item[i].PriceAndTaxCalculationItem = new SalesOrderMaintainRequestPriceAndTaxCalculationItem();
 item[i].PriceAndTaxCalculationItem.ItemMainDiscount = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemMainDiscount();
 item[i].PriceAndTaxCalculationItem.ItemMainDiscount.Rate = new Rate();
 item[i].PriceAndTaxCalculationItem.ItemMainPrice = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemMainPrice();
 item[i].PriceAndTaxCalculationItem.ItemMainPrice.Rate = new Rate();
 item[i].PriceAndTaxCalculationItem.ItemMainPrice.actionCode = ActionCode.Item01; // tried all the options for this one
 item[i].PriceAndTaxCalculationItem.ItemMainPrice.Rate.DecimalValue = 1.0M; // trying to set it as $1 just for testing, will be 0 when live
 // past tests that didn't work
 //item[i].PriceAndTaxCalculationItem.ItemPriceComponent = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemPriceComponent[1];
 //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0] = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemPriceComponent();
 //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate = new Rate();
 //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate.BaseDecimalValue = 1.0M;
 //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate.DecimalValue = 1.0M;
 //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate.CurrencyCode = "USD";
 //item[i].PriceAndTaxCalculationItem.itemPriceComponentListCompleteTransmissionIndicator = true;
 item[i].ItemScheduleLine = new SalesOrderMaintainRequestItemScheduleLine[1];
 item[i].ItemScheduleLine[0] = new SalesOrderMaintainRequestItemScheduleLine();
 item[i].ItemScheduleLine[0].Quantity = new Quantity();
 item[i].ItemScheduleLine[0].Quantity.Value = warranty.LineItems[i].ReplaceQty;
 return item;

Hi Joshua,
it's a long time ago and I hope you were able to solve your issue. For others who want to change prices in sales orders the following might be helpful:
It is not possible to set the price of a sales order in the create webservice call. You need to create the sales order first and then call the webservice a second time with actionCode="02" (Update).
The following is an extract from the sales order webservice documentation:
Node – PriceAndTaxCalculation
A price and tax calculation is the summary of the determined price and tax components for a business case. A specification of the general procedure for price and tax determination and valuation using attributes those are characteristic or relevant for the whole object.
Note: PriceAndTaxCalculation cannot be created but can only be modified. So this means that if the customer wishes to change the Discount or Freight charge, then the customer has to create the order first and then make a second web-service request to the update this sales order with the pricing information that is to be changed.
For the update you only need to send the ID of the sales order, the IDs of the items and the PriceAndTaxCalculation node.
The following would be an easy XML example for the update call:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
 <soapenv:Header/>
 <soapenv:Body>
 <glob:SalesOrderBundleMaintainRequest_sync>
 <SalesOrder>
 <ID>1234</ID>
 <Item actionCode="02">
 <ID>10</ID>
 <PriceAndTaxCalculationItem actionCode="02">
 <ItemMainPrice>
 <Rate>
 <DecimalValue>5.00</DecimalValue>
 <CurrencyCode>USD</CurrencyCode>
 </Rate>
 </ItemMainPrice>
 </PriceAndTaxCalculationItem>
 </Item>
 </SalesOrder>
 </glob:SalesOrderBundleMaintainRequest_sync>
 </soapenv:Body>
</soapenv:Envelope>
If you need further help with webservices or C#, let me know.
Best regards,
Felix

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

Price mandatory in sales order

Similar Messages

Maybe you are looking for