Price multiplied by 2

When creating a new PO, everytime I press enter at the service or limits table the net price will be multiplied by 2. I also happens when you switch between these tables. Does anyone have any idea what could be the problem?

We are not using conditions in this case, only standard PBXX.

Similar Messages

How can I sum prices multiplied by a unity when it is checked?

Hi
In this shopping list example I've got a situation where the Total should return $ 3.00.
Does anyone knows a formula that will return the total cost of the price multiplied by the unity only if it is checked?
Thanks in advance.

Hi Alex,
Here's are two examples. The first calculates the amount for each item only if it is checked.
If "Unity" is equivalent to "Quantity", then the checkboxes are redundant. The second example dispenses with the checkboxes, and uses the Quantity column to trigger the calculation when an entry is made in that column.
Formulas:
Example 1
E2 and filled down: =IF(B,C*D,"")
E10 (Footer row): =SUM(E)
Example 2
D2 and filled down: =IF(LEN(B)<1,"",B*C)
D10 (Footer row): =SUM(D)
The bottom row, containing the total, must be defined as a Footer row to keep it separate from the column named as the column to SUM. Header rows and Footer rows are excluded from functions such as SUM, preventing the self reference error that would occur if this formula were placed in a non-header, non-footer row in the column being summed.
Constructed in Numbers '09.
Regards,
Barry

Inventory Controlling - Get history moving average price function - Urgent

Dear Experts,
Currently I have an issue that I want to calculate material history value at storage location level for each month. I tried to get history stock quantity and value from table S031, stock quantity is correct. But stock value (goods receive value minus goods issue value in table S031) is not correct.
Client requests the resulet should be same as transaction code MC.9 (valuation selection - standard). But what the result I got from table S031 is the value that without disctribution. Currently I do not know how MC.9 calculate stock value.
Does any expert know if there is a funciton that can get history moving average price. I may use this price multiply history stock to get history value. Thanks
Best Regards
Angela

Hello,
Moving average cost history is available in MBEWH-VERPR.
Thanks,
Venu

Multiplying two values???

Hello everyone, i am trying to simply multiply two values together, however one of my values is a BigDecimal and the other a string value, having never used a BigDecimal before could anyone tell me how i could manipulate the below snippet of code to allow the multiplication of the 2 values:
BigDecimal price =(BigDecimal)(table.getValueAt(i,3));
String qty = (String)(table.getValueAt(i,4));
System.out.println(price+"\t"+qty+"\t");//THIS DOES SHOW THE 2 VALUES
BigDecimal total = multiply(price);//CAN ANYONE HELP ME HERE MANIPULATING A BIGDECIMALThanks in advance to anyone who is willing to help me out!!!

BigDecimal total = price.multiply(new BigDecimal(qty));

Actual Cost for Finished Products

Hi All,
For Finished Goods calculation will use Semi finished Goods and Raw Material, while calculating the Finished Goods in cost object controlling system is picking the Standard Price Multiply Actual Quantity of semi finished goods.
My Client requirement is to calculate the Finished Goods based Actual Quantity Multiply Actual Price.
Is there any standard settings available or not?
Regards
Srinu

hi..
If you do not want to activate ML then all materials defined as price control "V" and Price deetermination as "2"
kkumar

Can't get iPhone 5 calculator to include tax in total - Help!

Bought my iPhone 5 July 25, 2013, but haven't had much time to learn how it works. About the calculator... On most calculators, if I enter 239.00 x .0825 = I get 19.7175. If I then enter + = I get the total including tax 258.7175. For some reason, I can't get the calculator on my iPhone 5 to do this. What do I need to do? Thanks!

Thanks to all for your input and attempts to help.
Hot Spur, I got an email where you said: "How is the iOS calculator going to know the tax in any given area? It's different everywhere." I already know the tax rate so I don't need the calculator to know it.
I was just hoping the standard iPhone 5 calculator would allow me to enter the sale price, multiply it by the tax rate, hit the equal sign to see the tax amount, hit the plus sign, then the equal sign, then see the total due, including tax. This is the order it typically prints out on a receipt, too.
Sale Price
x Tax Rate = Tax Amount
+ = Total Due, including tax
I'll use my WalMart and Staples calculators until Apple comes up with a calculator that can do this. I had no idea it was so complicated...

TableView updates not working when ValueFactory returns a new Binding

Hi,
When a cell value factory returns a newly created expression or Binding cell values will stop receiving updates at some point. It seems that the cell that requests the observable value from the value factory does not keep a strong reference to the returned value so the cell will only receive updates from the the Observable value as long as it has not been garbage collected. The code below reproduces this issue:
import javafx.application.Application;
import javafx.beans.property.DoubleProperty;
import javafx.beans.property.ReadOnlyStringWrapper;
import javafx.beans.property.SimpleDoubleProperty;
import javafx.beans.value.ObservableValue;
import javafx.event.ActionEvent;
import javafx.event.EventHandler;
import javafx.scene.Scene;
import javafx.scene.control.Button;
import javafx.scene.control.TableColumn;
import javafx.scene.control.TableColumn.CellDataFeatures;
import javafx.scene.control.TableView;
import javafx.scene.layout.HBox;
import javafx.scene.layout.HBoxBuilder;
import javafx.scene.layout.StackPane;
import javafx.scene.layout.VBox;
import javafx.scene.layout.VBoxBuilder;
import javafx.stage.Stage;
import javafx.util.Callback;
* Reproduce cell update bug. Compile and run the class. Press the update button a
* couple of times and note how the values in the total column update. Press the
* GC button a couple of times and then press the update button again. Note how
* the values in the total column do not update anymore.
* The Value Factory for the total column does not return a property that is
* held by the Order object, it returns a Binding that is created on the fly.
* The cell does not hold a strong reference to this object so it can be gc'd
public class CellUpdateTest2 extends Application {
 static class Order {
 String name;
 DoubleProperty price = new SimpleDoubleProperty();
 DoubleProperty qty = new SimpleDoubleProperty();
 Order(String n, double p) {
 name = n;
 price.set(p);
 qty.set(1);
 final Order items[] = {
 new Order("Item 0", 4.0),
 new Order("Item 1", 5.0),
 new Order("Item 2", 6.0),
 new Order("Item 3", 7.0),
 new Order("Item 4", 8.0),
 new Order("Item 5", 9.0),
 new Order("Item 6", 10.0),
 new Order("Item 7", 11.0)
 @Override
 public void start(final Stage primaryStage) throws Exception {
 final Button updateButton = new Button("Update Values");
 updateButton.setOnAction(new EventHandler<ActionEvent>() {
 @Override
 public void handle(final ActionEvent actionEvent) {
 for (Order i: items) {
 i.qty.set(i.qty.get() + 1);
 final Button gcButton = new Button("System.gc()");
 gcButton.setOnAction(new EventHandler<ActionEvent>() {
 @Override
 public void handle(final ActionEvent actionEvent) {
 System.gc();
 final TableView<Order> tv = new TableView<Order>();
 final TableColumn<Order, String> nameCol = new TableColumn<Order, String>("Item");
 final TableColumn<Order, Number> priceCol = new TableColumn<Order, Number>("Price");
 final TableColumn<Order, Number> qtyCol = new TableColumn<Order, Number>("Quantity");
 final TableColumn<Order, Number> totalCol = new TableColumn<Order, Number>("Total");
 nameCol.setCellValueFactory(new Callback<TableColumn.CellDataFeatures<Order, String>, ObservableValue<String>>() {
 @Override
 public ObservableValue<String> call(final CellDataFeatures<Order, String> d) {
 return new ReadOnlyStringWrapper(d.getValue().name);
 priceCol.setCellValueFactory(new Callback<TableColumn.CellDataFeatures<Order, Number>, ObservableValue<Number>>() {
 @Override
 public ObservableValue<Number> call(final CellDataFeatures<Order, Number> cellData) {
 return cellData.getValue().price;
 qtyCol.setCellValueFactory(new Callback<TableColumn.CellDataFeatures<Order, Number>, ObservableValue<Number>>() {
 @Override
 public ObservableValue<Number> call(final CellDataFeatures<Order, Number> cellData) {
 return cellData.getValue().qty;
 totalCol.setCellValueFactory(new Callback<TableColumn.CellDataFeatures<Order, Number>, ObservableValue<Number>>() {
 @Override
 public ObservableValue<Number> call(final CellDataFeatures<Order, Number> cellData) {
 return cellData.getValue().price.multiply(cellData.getValue().qty);
 tv.getColumns().addAll(nameCol, priceCol, qtyCol, totalCol);
 tv.setColumnResizePolicy(TableView.CONSTRAINED_RESIZE_POLICY);
 tv.getItems().addAll(items);
 final HBox hb = HBoxBuilder.create().children(updateButton, gcButton).build();
 final VBox vb = VBoxBuilder.create().children(tv, hb).build();
 primaryStage.setScene(new Scene(vb));
 primaryStage.setHeight(200.0);
 primaryStage.show();
 public static void main(final String args[]) {
 launch(args);
} Is this expected behaviour?
If so - what would the correct way to approach this?
If not - is there an easy workaround?

this seems to have worked....
 static class Order {
 String name;
 DoubleProperty price = new SimpleDoubleProperty();
 DoubleProperty qty = new SimpleDoubleProperty();
 DoubleProperty total = new SimpleDoubleProperty();
 Order(String n, double p) {
 name = n;
 price.set(p);
 qty.set(1);
 public void updateTotal() {
 total.set(price.get() * qty.get());
 }with
 qtyCol.setCellValueFactory(new Callback<TableColumn.CellDataFeatures<Order, Number>, ObservableValue<Number>>() {
 @Override
 public ObservableValue<Number> call(final CellDataFeatures<Order, Number> cellData) {
 System.out.println("in qty column");
 cellData.getValue().updateTotal();
 return cellData.getValue().qty;
 });and finally
 totalCol.setCellValueFactory(new Callback<TableColumn.CellDataFeatures<Order, Number>, ObservableValue<Number>>() {
 @Override
 public ObservableValue<Number> call(final CellDataFeatures<Order, Number> cellData) {
 System.out.println("in total column");
 return cellData.getValue().total;
 });I cannot explain why what you did did not work. I have a mistrust towards binding and I avoid it when ever possible.
thanks
jose

Purchase Order Condition WOTB - OTB Procurement

Hello All,
I would like to ask what is the Condition WOTB - OTB Procurement used for. It seems that it always takes the Net Price multiplied by the quantity. But in the column Actual Price I already get my net value, so I would like to ask what is the reason of having a double condition which displays the same figures. Thanks.
Thanks.

Hi,
In Tr.Code :M/08 deflag the 'Manual' for your condition.
regards

Purchase Order Response, tolerance on QTY

Hi Folks,
Just a quick question.
Scenario is as follows.
PO created for 2 EA a 12 USD per EA., there is no tolerance groups assigned to either USER or VENDOR.
In the POR I create a line with the price at 14. When I do the check is tells me that the price is outside the tolerance. Thats OK!!!!
When I create a line with price of 12 and qty of let say 120 I get no error message.
Is this correct?
No matter what I do I can not get it to issue a warning that QTY is to high mor something like that.
Any ideas?
Thanks in advance,
Thomas

Hi,
I do not understand this.
We are on SRM server 5.5.
In IMG it says that you can use the Tolerance keys PM, PZ and PR. (See below).
However I can not get them to kick in :o(
Anny advice?
/Thomas
In IMG for SRM you can read this in the IMG Doc.
"Tolerances for purchase order confirmations
SAP Enterprise Buyer uses the tolerances that you define here for the automatic data transfer from the purchase order confirmation to the purchase order and also for the manual data check in the vendor information. If the tolerances are exceeded, the system issues I messages.
You can assign the following tolerance keys:
PM: Quantity variance (converted to currency amount)
If a confirmation is expected for a purchase order item, the system calculates the purchase order confirmation net price multiplied by the purchase order confirmation quantity. The system compares this sum with the defined upper and lower limits. You can also define percentage limits for the quantity variance check. Then the percentage variance from the expected quantity calculated - independent of the purchase order price - and this is compared with the defined percentage limits.
PZ: Time overrun compared to purchase order
The system determines how many days the delivery date has exceeded the planned time interval by. If the delivery date of the purchase order confirmation is earlier than the delivery date of the purchase order, the system takes the purchase order date - the confirmation date; If the delivery date of the purchase order confirmation is later than the delivery date of the purchase order, the system takes the purchase order confirmation date - the purchase order date. The system compares the number of days with the defined absolute upper limit.
PR: Price variance (value variance from expected value)
Here the variance between the purchase order confirmation and the purchase order price is checked. The system determines for the items the price variance as the product of the quantity in the purchase order confirmation multiplied by the price in the purchase order confirmation, and it compares this variance with the defined percentage and absolute upper and lower limits."

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o In rounding rule 'B', values are always rounded down:
   1045.9 -> 1045 LIT
   1045.1 -> 1045 LIT
   In this example, the currency of the condition rate is Italian Lira.
   The Italian Lira does not have any places after the point.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

Lower Tolerance Checking for PM Key

Hi,
For our business process we accept every incoming quantity change made by the vendor in the purchase order response. We accept quantity increments as well as quantity descents. In order to prevent the POR from having to be approved/accepted by the responsible purchaser, we also need a lower limit to customize the same.
Therefore the question is, why is the lower limit input field missing in the PM key? When going through the help file of this customizing transaction we can read the following:
PM: Quantity variance (converted to currency amount)
If a confirmation is expected for a purchase order item, the system calculates the purchase order confirmation net price multiplied by the purchase order confirmation quantity. The system compares this sum with the defined upper and lower limits. You can also define percentage limits for the quantity variance check. Then the percentage variance from the expected quantity calculated - independent of the purchase order price - and this is compared with the defined percentage limits.
As you see above, it is clearly stated that u201CThe system compares this sum with the defined upper and lower limitsu201D. So according to SAP help, lower limit comparison should be possible.
In order for this to work we need the lower limit input fields.
---> Is there any other way to establish the above ?
Thanks and regards,
Aline

Hi,
Priority of tolerances is PO tolerance limit, TOG tolerance grp. for User, TOG tolerance grp. for Vendor (if user not logged on). Even absolute tolerance limit always has priority over percentage limit.
In your case, you need to check PO tolerance first then TOG for user.
regards,
rahul

Accounting in Purchasing

Hi,
What are the accounts will be hit..when we receive a item through PO?
Inventory AP accrual account...this will be debited
Material valuation account...this will be credited ???
can someone also share as when and what case invoice and purchase price variance..willl be hit?
Thanks
Mahendra

Purchase Price Variance Account:
====================
This is the account used to accumulate purchase price variance for this organization. The purchase price variance account is usually an expense account. This is the variance that you record at the time you receive an item in inventory, and is the difference between the purchase order cost and an item's standard cost. Purchasing calculates purchase price variance as:
PPV = (PO unit price - standard unit cost) X quantity received
You define this in the Define Organization (Nav > Setup > Organizations > Organizations) in the Other Accounts tab in the Organization Parameters form
Invoice Price Variance Account:
=====================
This is the account used to accumulate invoice price variance for this organization. This is usually an expense account. Invoice price variance is the difference between the purchase order price for an inventory item and the actual invoice price multiplied by the quantity invoiced:
Invoice Quantity x (Invoice Price - PO Price) x Invoice Exchange Rate. Purchasing uses this account on the PO distribution when the requisition or purchase order is created. When Payables creates accounting entries for the invoice, it uses the invoice price variance account from the purchase order to record invoice price variance entries. You define this in the Define Organization (Nav > Setup > Organizations > Organizations) in the Other Accounts tab in the Organization Parameters form.

Tolerance in SRM and ECC (BE R/3)

Hi,
During posting of invoice in SRM, why only TOG tolerance will be used for checking tolerance?
As per my understanding, ECC tolerance will not be checked during SRM invoice posting.
Is it correct system functionality in SRM?
regards,
Rahul Mandale

Hi
Have you maintained the same configuartion data both in R/3 as well as SRM system for the Tolerance group ?
Which SRM scenario you have maintained ? Whci SRM System release you are using ?
I guess, ECC will be checked only based on the EBP Scenario yo have maintained for the system. But the BAPI call checks the configuartion data in SRM as well as R/3 before posting the Invoice.
Here is the detailed reasons behind the same ->
Set Tolerance Checks
In this activity, you define the tolerances for value or quantity overruns for deliveries, invoices, or order confirmations. Quantities or values of deliveries, invoices, or purchase order confirmations may vary up to these tolerance values. This allows deliveries or invoices to still be posted or data to be transferred from the order confirmation to the purchase order. For the definition of these tolerances, use tolerance groups to which you assign tolerance keys with different values and quantities. In this way, you can assign the same tolerances to different users.
Example
You assign the tolerance key DQ to the tolerance group M (manager), define an upper limit of 1000 for the value-based limit and activate the value limit. You also assign the tolerance key DQ to the tolerance group E (employee), define an upper limit of 100 for the value-based limit, however, and activate the value limit.
Standard settings
You can assign the tolerance group to a user group via the attribute TOG (tolerance group). For example, you assign the value M to user Manager 1 in the user attribute TOG for the user group Manager. If a user is logged on, the system always uses his TOG. If the user is not logged on, (BAPI is being used), the system uses the TOG of the vendor (business partner master record).
You can create tolerance groups by checking the quantity against the purchase order and the price (value) against the confirmation.
If you do not define any tolerances, this means that it is not possible to enter a delivery/incoming invoice in EBP where quantity or value has been exceeded.
The tolerance can be specified as a value, percentage, days, depending on the tolerance key. Two differently structured tolerances exist for value variances (DA for cumulated values, PP or PR for single values).
Percentage and absolute limits
If you define both a percentage and an absolute limit in a tolerance key, then you cannot post an invoice or automatically transfer data from the first purchase order confirmation received into the purchase order, if either one of the tolerances is exceeded. An absolute limit always has priority.
Example (with respect to invoice verification): You have defined a percentage upper limit of 5% and an absolute upper limit of 10. You wish to enter an invoice with the amount 1000, that exceeds the order value by 30. Although the percentage upper limit of 5% is observed, the absolute limit is not. The invoice exceeds the tolerance and can therefore not be posted.
Tolerances for deliveries/invoices
You can assign the following tolerance keys:
CF: Over/underdelivery in the confirmation
You use this tolerance to check how the confirmation deviates from percentage limits for overdelivery and underdelivery. First, the system checks in the confirmation against the tolerances created in the purchase order. If none exist, the system checks against the tolerances in the relevant tolerance group (for example, the tolerance group of the vendor). If you select the value Unlimited , no tolerances apply. The system displays a controllable message when a tolerance is not reached or is exceeded (see Influence Message Control).
DA: Exceed value (cumulated)
You use this tolerance both for confirmations and invoice entry. You can either define an actual value or a percentage for the upper limit. The system checks whether the cumulated invoice value (that is the value of all previous invoice documents + current invoice documents) exceeds the order value. The check is always made against the purchase order. If a confirmation is expected for an order item, a second tolerance check is made to determine whether the cumulated confirmation value (value of the previous confirmation documents + current confirmation) exceeds the order value.
DQ: Quantity variance (converted to currency amount)
You use this tolerance both for confirmations and invoice entry.
If a confirmation is expected for an order item and has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)). If no confirmation is expected, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts. You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
LA: Amount of limit purchase order
You use this tolerance both for confirmations and invoice entry.
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Limit purchase order; time limit exceeded
You use this tolerance both for confirmations and invoice entry.
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the absolute upper limit defined.
PP: Price variance (value variance from expected value)
You only use this tolerance for invoice entry.
The variance from the expected value is checked here, based on the preceding document (purchase order price or confirmation value).
The system determines by how much each invoice item varies from the product of quantity invoiced multiplied by the order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
TX: Tax variance
You use this tolerance exlusively for invoice entry. You define tolerances for tax amounts that are used with the tax calculation.
Tolerances for purchase order confirmations
SAP Enterprise Buyer uses the tolerances that you define here for the automatic data transfer from the purchase order confirmation to the purchase order and also for the manual data check in the vendor information. If the tolerances are exceeded, the system issues I messages.
You can assign the following tolerance keys:
PM: Quantity variance (converted to currency amount)
If a confirmation is expected for a purchase order item, the system calculates the purchase order confirmation net price multiplied by the purchase order confirmation quantity. The system compares this sum with the defined upper and lower limits. You can also define percentage limits for the quantity variance check. Then the percentage variance from the expected quantity calculated - independent of the purchase order price - and this is compared with the defined percentage limits.
PZ: Time overrun compared to purchase order
The system determines how many days the delivery date has exceeded the planned time interval by. If the delivery date of the purchase order confirmation is earlier than the delivery date of the purchase order, the system takes the purchase order date - the confirmation date; If the delivery date of the purchase order confirmation is later than the delivery date of the purchase order, the system takes the purchase order confirmation date - the purchase order date. The system compares the number of days with the defined absolute upper limit.
PR: Price variance (value variance from expected value)
Here the variance between the purchase order confirmation and the purchase order price is checked. The system determines for the items the price variance as the product of the quantity in the purchase order confirmation multiplied by the price in the purchase order confirmation, and it compares this variance with the defined percentage and absolute upper and lower limits.
Automatic transfer
Enterprise Buyer automatically takes the data from the first purchase order confirmation to be received, however, the following conditions apply:
Data transfer is only possible if no contract exists for the purchase order item.
All existing tolerances (quantity, price and delivery date) are adhered to and/or the purchase order confirmation data matches that of the purchase order exactly.
If the purchase order confirmation consists of multiple items, then the system transfers the data as follows:
The sum of all quantities
The highest available price
The latest available delivery date for materials or the maximum period for provision of services and limit items
( The system does not take any tolerances into account when data is transferred manually from the purchase order confirmation.)
The system does not automatically transfer any data from other purchase order confirmations. This prevents the original data of the purchase order being changed repeatedly by several purchase order confirmations one after the other when tolerances are exceeded.
Activities
1. Create a tolerance group and select it.
2. Assign one or more of the defined tolerance keys to the tolerance group.
3. Enter an upper and/or a lower limit. If you do not make an entry, the check is made against the value zero.
Further notes
The following table shows the existing assignment possibilities(X) for upper limits (UL) and lower limits (LL) :
Key Absolute Absolute Percentage Percentage Percentage Day Day
LL UL LL UL unlimited LL UL
CF X X X
DA X X
DQ; PM X X
LA X X
LD; PZ X X
PP; PR X X X X
Hope this will help.
Please reward suitable points.
Regards
- Atul

SUS Quantity tolerance for confirmation -How to set an warning or error Msg

Hello All,
Does anyone knows how do i configure SUS, so the system will check quantity tolerance in PO confirmation so the Supplier can knows that he is within or over the tolerance?
I would like to set an error message so the supplier will confirm the PO within the tolerance or will reject it.
Thanx a lot,
Sheila Silva

try the following:
in transaction SPRO
goto supplier relatioship management-> cross application basic settings ->set tolerence checks ,
create a new tolerence group, for this group assign the folowing tolerence keys as required.
PM: Quantity variance (converted to currency amount) - this is the one relevant for you i guess.If a confirmation is expected for a purchase order item, the system calculates the purchase order confirmation net price multiplied by the purchase order confirmation quantity. The system compares this sum with the defined upper and lower limits. You can also define percentage limits for the quantity variance check. Then the percentage variance from the expected quantity calculated - independent of the purchase order price - and this is compared with the defined percentage limits.
PZ: Time overrun compared to purchase order
The system determines how many days the delivery date has exceeded the planned time interval by. If the delivery date of the purchase order confirmation is earlier than the delivery date of the purchase order, the system takes the purchase order date - the confirmation date; If the delivery date of the purchase order confirmation is later than the delivery date of the purchase order, the system takes the purchase order confirmation date - the purchase order date. The system compares the number of days with the defined absolute upper limit.
PR: Price variance (value variance from expected value)
Here the variance between the purchase order confirmation and the purchase order price is checked. The system determines for the items the price variance as the product of the quantity in the purchase order confirmation multiplied by the price in the purchase order confirmation, and it compares this variance with the defined percentage and absolute upper and lower limits.
then
in transaction PPOMV_BBP, search for teh relevant vendor,
assign the attribute "tolerence group"(TOG) to the newly created tolerence group for the relevent vendor.
Regards,
Chander

Totalling values in a variable??

Hi Swingers,
I am able to multiply two values together and print the result to the screen, within a loop however i need to take this multiplied value and put it into a variable and everytime in the loop a value is worked out i then wanna add the previous value with the new value , the code below may make my problem a little more clear:
public void getOrderTotal() {
 int count = table.getRowCount();
 for (int i = 0; i < count; i++) {
 if (table.getValueAt(i,4)== "") {
 else {
 BigDecimal price =(BigDecimal)(table.getValueAt(i,3));
 String qty = (String)(table.getValueAt(i,4));
 BigDecimal totalled = price.multiply(new BigDecimal(qty)); table.setValueAt(totalled,i,5);
 System.out.println(price+"\t"+qty+"\t"+totalled);
 totalTotal = totalTotal.add(totalled);//TRYING HERE TO PUT VALUES IN VARIABLE totalTotal AND NULL POINTER EXCEPTION OCCURRING
 System.out.println(totalTotal);
} The code does compile but has a NullPointerException error in line stated above - do u know why??
Thanks in advance

Cheers for the reply codeCraig,
I have changed the code to the below and the NullPointerException is still pointing at the same line, can anyone help me with this:
public void getOrderTotal() {
 int count = table.getRowCount();
 Vector totalTotal = new Vector();
 for (int i = 0; i < count; i++) {
 if (table.getValueAt(i,4)== "") {
 else {
 BigDecimal price =(BigDecimal)(table.getValueAt(i,3));
 String qty = (String)(table.getValueAt(i,4));
 BigDecimal totalled = price.multiply(new BigDecimal(qty));
 try {
 totalTotal = totalTotal.add(totalled);
 catch (Exception e) {
 System.out.println(e.getMessage());
 e.printStackTrace();
 table.setValueAt(totalled,i,5);
 System.out.println(price+"\t"+qty+"\t"+totalled);
 System.out.println(totalTotal);
 } Peace

Price multiplied by 2

Similar Messages

Maybe you are looking for