Tolerance limits for Sales Orders

Hi SAP Gurus,
I have a situtation here. Customer "A" has a credit limit of 300,000 but the sales rep entered an order for 350,000. The credit analysts didn't receive any warning message while releasing the order and it's been shipped and invoiced.
How do we control such levels on sales orders?
Points guaranteed.
Regards
Asif

Hi,
In our company we have entered a credit check on the delivery level.
This is specified in transaction OVA8:
Credit check: Static check
Indicates whether the system carries out a static credit check.
Use
The customer's credit exposure may not exceed the established credit
    limit. The credit exposure is the total combined value of the following:
o   Open sales documents
o   Open delivery documents
o   Open billing documents
o   Open items (accounts receivable)
You can specify in the adjacent fields whether the system takes into
    account all open orders and all open deliveries.
Kind regards,
Linda

Similar Messages

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Tolerance limits for contract

Hi all,
   Is there any possibility to maintain tolerance limits for Quantity in Quantity Contract (doc type MK),,,
ex: Quantity Contract (MK) -- target quantity = 100
      it should allow me to create release orders (Purchase orders) for 105 quantity(tolerance of +5%)
regards
urendra

Hi,
By using Purchasing Value Key in Material Master you can control over and under deliveries.But its applicable to that material.
If Purchasing Info Record exists for that material then tolerance limit which is given in inforecord takes priority.
Regards,
Ramesh
Message was edited by:
        Ramesh

Tolerance limits for Price Variation

Dear All,
I have set the Following in Customizing.
In the following node : IMG-------> Materials Management ----------> Purchasing -----------> Purchase Order ---------> Set tolerance limits for price Variance.
In this, For Company code & Tolerance Key "PE" combination, it has been set " Check Limit 20%" in the Percentage field ( Upper limit ).
Now, I have a material having a Moving Average price of 100 INR in the material master Accounting view. When I create a PO for 130 INR, there is no warning/error message that is popping up? Isn't the system supposed to throw a message here, since 130 inr exceeds 120 INR, or am I missing something out here ?
Note : 120 INR = 100 + (20%)(100) = 120 INR.
Regards
Sathya

Hi Sathyanarayana Rao V N
You can benefit from M8 messages for incoming invoices with tolerances to solve your problem. You have to configure your system messages with error.
Regards.
M.Ozgur Unal

Tolerance limits for PO,MIGO..etc..?

Dear all
Can anybody explain me about the tolerance limits in SAP-MM,
1.what is tolerance limits..?
2.Why tolerance limits need in SAP-MM..?
3.How to configure in SPRO
Which are all the area has to maintain Tolerance limits according to MM point of view
Advance thanks
goods answers will be highly rewardable.
Thanks
sap-mm

Hi
tolerance limits for price variancesin Purchase order
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
For Invoices specify the tolerance limits for each tolerance key for each company code.
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, 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.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
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: Blanket purchase order time limit exceeded
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 with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Thanks & Regards
Kishore

Maintain tolerance limits for tolerance key PE (CoCode S001)

Dear all
im getting error when i creating PO
Maintain tolerance limits for tolerance key PE (CoCode S001)
Please help me
Regards
venu gopal

Hi
You need to maintain the Tolerance key
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
Maintain the tolearnce key in
SPRO-> IMG-> Materials Management-> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
If you want the sytem to propmt for a warning or Error message you can configure the same in
SPRO-> IMG-> Materials Management-> Purchasing-> Environment Data-> Define Attributes of System Messages

Maintain tolerance limits for tolerance key PE

Hi,
How can I correct the error below?
"Maintain tolerance limits for tolerance key PE"
Thanks

REFER BELOW SDN POST
Re: TOLERANCE KEY ERROR DURING MIGO
MAINTAIN TOLERANCE LIMITS FOR TOLERANCE KEY PE ACCOUNT ASSIGNMENT -
> Please follow this link --> SPRO -> MM-> Purchasing --> Purchase Order --> Set Tolerance limits for price variance --> Here you have to set for Tolerance keys PE and SE. Just copy them from std co. code.
Message was edited by:
SHESAGIRI.G

Set Tolerance Limits for Price Variance when PO-based Purch.Requisition

We must garanty that Price from Purch.Requisition will be the same at PO.
IF some variance occur a error messag must be sent to user and PO could not be saved.
I found at customzing under SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance .
Reading the help of customizing it mean the system consists what we need..
I have created tolerance limit NB, and set limits for all checks as 0,01.
When I will activate messages as recommended on help no messages 601 and 602 have the text that guide us to correctly setting.
The help mention that after create tolerance limit we must set this tolerance by document type..but I didnt find this field at customzing
Does anyone can help me ?
See the help on customizing below
Set Tolerance Limits for Price Variance
In this step, you can define percentage-based and value-based (absolute) tolerance limits for price variances between purchase orders and purchase requisitions. Variance types are mapped out in the SAP system by tolerance keys.
You define the tolerance limits for each tolerance key and assign your tolerance key to the document types for purchase requisitions. The tolerance limit then applies for all documents of this document type.
When processing a purchase order, the system checks whether the unit price of a purchase order item differs from the unit price of a purchase requisition item. If you have configured, activated and defined tolerance limits in document types, variances are permitted in the tolerance limits. If the variance exceeds the tolerance limit, the system issues a warning. If you have defined a percentage-based and a value-based absolute tolerance limit, the strictest of the two variances will apply for this check.
Note
You can determine whether the system messages (601 and 602) appear as warnings or error messages in step "Define Attributes of System Messages".
To do this, go to the Materials Management IMG and choose Purchasing -> Environment Data -> Define Attributes of System Messages.
Requirements
The tolerance key must be defined in step Define Tolerance Key.
Activities
1. Define tolerance limits for each tolerance key.
2. Define the tolerance key in step Define Document Types.
Thx and best regards,
Ale

HI
SET TOLERANCE LIMITS FOR PURCHASE REQUISITION UNDER THE DEFINE DOCUMENTS FOR PR
AFTER SETTING TOLERANCE LIMITS WHILE CREATING PURCHASE U WILL GET BASED ON TOLERANCE LIMITS THERE FOUR WAYS TO SET TOLERANCE LITS
1
ABSOLUTE VALUE
2
PERCANTAGE
3
TOTAL PO VALUE
4
QUANITY BASED PRICE PER UNIT
OK BYE

GR Tolerance Limits for Date and quantity..??

Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.

Hi,
GR tolerance limits can be set based on the quantity only .It is configuration settings .
MM-->Inventory Management-->Inventory Management and physical Inventory --->set tolerance limit/
Following are the standard settings:
B1 ( order price quantity variance with error message): 50 %
B2 (order price quantity variance with warning): 20 %
VP (variance from moving average price) 25 %
In case of dates, the tolerance limit settings based on delivery date can be achived by using user exists or create a Z t.code goods receipt copying standard one & write a code to apply your logic while you do the GR.
Thanks,
AMIT

Tolerance limit for STO orders

HI
I want to set the tolerance limit for under delivery and over delivery qty tolerance. Where can we set the tolerance limits for stock transfer orders from plant to plant ?

Please check OSS notes:
Note 1093582 - FAQ: Delivery complete indicator ELIKZ
5. Question
In which cases does the system automatically set ELIKZ in stock transport orders?
Answer
ELIKZ will be set at the goods receipt stage automatically, if the GI = GR quantity. This behaviour applies to intra-company stock transport orders and cross-company stock transport orders. See note 196280.
With stock transport orders the 'delivery completed' indicator is only relevant when there is no stock in transit The tolerance quantities from the purchase order are not taken into account.(see note 34737).
It is possible to modify the standard to allow to set the "delivery completed" indicator for cross-company stock transport orders. This modification is contained in note 167795.

Tables for Sales Order,Delivery Doc, Billing Doc

Hello All,
Can anyone list the tables that are relevant for Sales Order,Delivery, Billing-Header,Item,Schedule line level as applicable.
Regards,
Raj

Hi Raja Sekhar,
Customers
         KNA1   General Data
                  KNB1   Customer Master Co. Code Data (payment method, reconciliation acct)
                  KNB4   Customer Payment History
                  KNB5   Customer Master Dunning info
                  KNBK   Customer Master Bank Data
                  KNKA   Customer Master Credit Mgmt.
                  KNKK   Customer Master Credit Control Area Data (credit limits)
                  KNVV   Sales Area Data (terms, order probability)
                  KNVI   Customer Master Tax Indicator
                  KNVP   Partner Function key
                  KNVD   Output type
                  KNVS   Customer Master Ship Data
                  KLPA   Customer/Vendor Link
Sales Documents
VBAKUK VBAK + VBUK
                  VBUK   Header Status and Administrative Data
                  VBAK   Sales Document - Header Data
                  VBKD   Sales Document - Business Data
                  VBUP   Item Status
                  VBAP   Sales Document - Item Data
                  VBPA   Partners
                  VBFA   Document Flow
                  VBEP   Sales Document Schedule Line
                  VBBE   Sales Requirements: Individual Records
SD Delivery Documets
LIPS   Delivery Document item data, includes referencing PO
                  LIKP   Delivery Document Header data
Billing Document
VBRK   Billing Document Header
                  VBRP   Billing Document Item
SD Shipping Unit
VEKP   Shipping Unit Item (Content)
                  VEPO   Shipping Unit Header
REWARD POINTS IF HELPFUL
Regards
Sai

Query for Sales Order Analysis

Dear Experts
I have written a Query for Sales Order Analysis and would like to have help on this.
The query is used for generating daily report for Sales Order on number of documents (Sales Order), total amount of sales orders and total GP of Sales Order. The query is written as below:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum] ORDER BY T0.[DocNum]
where U_Total_GP is a UDF for storing the GP of each order.
After executing the query, a selection criteria of date appears and after a date is selected, the report shown information required. However, the query does not calculate column total for total amount and total GP. Although I know the total for each column can be displayed by pressing "Ctrl" + Click on the column title, it would have to be done from time to time.
Therefore, I would like to modify my query in order to calculate the column totals when executed. Are there any suggestions for this?
Thank you
Regards
Elton

Hi Elton,
Try this:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT '', SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]
ORDER BY T0.[DocNum]
Thanks,
Gordon

Workflow for Sales Order Release via Status Profile

Dear all,
i want to make a workflow for sales order which have 4 User Status in One status profile.
Once Event triggered for sales order
1.   Mail should go to main authority with sales order number.
2. Once authority will do some changes in the required field then he/she changes
     the user status-1 from defauts as per line Item and mail should go to department no-1 (Head authority).
3. Once again same changes in sales order but now user status-2 from user status-1
     as per line Item and mail should go to department no-2 (Head authority).
4. Once again same changes in sales order but now user status-3 from user status-2
     as per line Item and mail should go to department no-3 (Head authority).
5. Once again same changes in sales order but now user status-4 from user status-3
     as per line Item and mail should go to department no-4 (Head authority) .
and parrally for each changes of Status mail should also go to User (Event Creator).
6. Finally mail sholud go to User as you are permitted to do next business transaction for this sales order
Please tel me the process as i am very new this topic and i am always going to stuck in Binding.
please help me out.
Thank You

Hi Neeraj,
First of all start with SWELS and SWEL T-Code to check if any standard event is getting triggered or not. If event is getting triggered, then use the same event to trigger the workflow; otherwise create a custom event of BO and use the same to trigger the workflow.
Hope you are aware of T-Code SWO1 and delegation of BO. The BO used for your requirement will be BUS2000115.
As you want the workflow to get triggered only for one status profile and one of its status, so use check function module. There set the condition for you status profile and status.
The FM which you will be using the most is CRM_ORDER_READ. To read the status, you can also use CRM_STATUS_READ_OW.
Now simply make the approval steps in the workflow using activity. In the activity, you can use the standard method USERSTATUSPOPUP to send the workitem for approval. In each step use the same activity with different agents as approvers.
Just go with these things and let me know if you get stuck up somewhere.
Regards,
Guddan

User exit for Sales order

hi,
i need to eliminate leading zeros for PO number which comes in SO created trough ALE.i found the enhancement for the FM idoc_input_orders.in that enahancement we have 12 FM's.my Leading zeros are comming for field belnr which comes in e1edk01 segment of idoc orders05.now i had coded my part of coding in FM exit_saplved.._oo1 and i had activated that.but it is not working for me.than i tought of going to other FM exit_sapl..._009.in which i'm not able go into the include either.plz help me out.thank you.

Hi, Krishna!
With IDOC_INPUT_ORDERS during IDoc interpretation PO number is assigned to XVBAK-BSTKD field which is later used for sales order creation with reference to PO.
So all you need is to use some customer exit with changing parameters containing XVBAK after IDoc interpretation is completed. For example you can use EXIT_SAPLVEDA_009 which is called at the end of IDoc check after interpretation.
Regards,
Maxim.

RBA GATP check is not getting invoked for Sales Order

Hi Everyone,
RBA GATP check is not getting invoked for Sales order.
I maintained the configuration settings for 'Rules-Based Availability Check', APO general settings (check mode, check instruction), carried out integrated rule maintenance, Rule determination for the combination of order type & product, associated the check mode to product master. Also maintained all the settings in ECC towards Req class, Req type, checking control etc.
However, sales order is not invoking RBA Check though it is showing up the 'Rule' icon in the screen. Also, in the APO Availability check in Sales order when I click onto 'check instruction', I get the checking mode that pertains to RBA for business event 'A' (Sales order). Though I have not maintained any stock for the main material for which I have the sales order, yet system is confirming any quantity that I put in.
I would expect that system would propose the same material in an alternate location where we have stock through RBA.
Request you to share ideas on this.
Regards,
Avijit Dutta

Hi Avijit,
You should used No Checking Horizon in Checking instructions and also Check your rule control settings.
What you have defined in 1st and 2nd steps. Check whether product substitution is carried out or Location Substitution.
Thanks,
Bala.

Tolerance limits for Sales Orders

Similar Messages

Maybe you are looking for