Tolerance limits & Number ranges

1. What is tolerance limits ? Why we need to use it ? What are the steps to configure tolerance limits ?
2. What is number ranges ? How to create number ranges ?

Hi,
IN PO tollerence limit:
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.
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.
MIRO Tolerence limit: OMR6
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.
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.
SAM

Similar Messages

Control chart tolerance limits lines not shown

As Run chart displays values of Single result, SPC Control charts also Displays these reults with tolerance limit with Showing lines of uper and lower limit Tolerence. I have an issue while showing these lines .when i am doing result recording control charts Some times shows tolerance limit lines and some times not ? Kindly clarify me the SPC control chart process too?but my main question is that why SAP some times shows Results and sometimes not .
More over I already did all settings as below
Sapmling procedure with Fixed samples ,and SPC inspection crieteria,
Inspection plan -Inspection task list cahracterstics
MIC
      Sampling proceudre -active
      SPC - Active
      Required Chrac.-Active
      Single result -Active
      Fixed scope -Active
All settings of number ranges is set
Control chart 115 -Shewchart X bar is using .

Hi Vineeth,
We are using SPC inspection chars, in results recordin it is not calulating the control limits automatically. When i click to calculate the control limits, getting the message Control limits for track 1 could not be calculated.
Can you please let me know
1) The process flow for SPC inspection results recording
2) How to get the control limits automatically for SPC inspection chars.
3) System will require some results to calculate control limts, right? So, till system calculates those control limits, how system will valuate results (will it be with specificaiton limits specified at inspection characteristics level), do we have any option of entering preliminary results so that system can control limits on bases of those results and so from very first inspection lot we have control limits for valuation?
Thanks in advance
Bob

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

Set Tolerance Limits

In this step, you 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:
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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.
u2022     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).
u2022     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.
u2022     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.
u2022     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).
u2022     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).
u2022     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.
u2022     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.
Activities
Configure the tolerance limits for the individual tolerance keys.
             Lower limit             Upper limit
             Absolute    Percentage Absolute    Percentage
AN          -           -           X           -
AP          -           -           X           -
BD          X           -           X           -
BR          -           X           -           X
BW          -           X           -           X
DQ          -           -           X           -
DW          -           -           X           -
KW          X           X           X           X
LA          -           -           X           X
LD          X           -           X           -
PP          X           X           X           X
PS          X           X           X           X
ST          -           -           X           -
VP          -           X           -           X

1) "Powered by Jive Software" ....
2) 我看看有没有机会通过什么渠道反映这个问题..

Restriction in number range setting

Hi in t-code cc01 ( create change Master )
Number Range Object Change Master Record
No From number          To number            Number status          Ext
01 000000000001         199999999999                                       X
02 200000000000         299999999999         200000000001
already given numbers are      200000000000   nd 200000000001 ( while implementation ) and object types contains number of options ) and then   P2001 is used and for the number object types has limited options ( does not contain Routing , Inspection Plan etc ) How to get full object types options ?
now when i give 200000000002   message is coming External number assignment not supported for change number 200000000002
How to solve this issue ?
Thanks

Hi ,
What is the meaning of Number range ? in T-code CC01. there is one tab Number Range (Ctrl+F11).
Number Range Object Change Master Record
No                           From number                      To number                        Number status                        Ext
01                           000000000001                   499999999999                                                                 X
02                           500000000000                   999999999999                  500000000001
as obve defined. When i am giving number   500000000002 . it is showing external number not supported for change number
500000000002. (it is taking 500t0000002 etc. )
but when i gave 000000000002. it is taking this number.
What's wrong with 500000000002 series
please clarify

Number Ranges in Txn. CRMD_ORDER

Dear All,
While creating an order in Txn. CRMD_ORDER, we need to define our custom logic for number ranges.
Please suggest on the same.
Regards,
Ramki.

Hi,
Following Logic you can use for number ranges
1. Find out Standalone CRM Transaction & create Internal Number Range for that which will remain in CRM only.
2. Find out CRM transactions which are replicating to ECC .For those transactions create INTERNAL Number range & Note down the interval limits of the number ranges. Same Interval you have to create in ECC as EXTERNAL
For all sales related transaction Use object CRM_SALES
For all service related transaction Use object CRM_SERVIC
Best Regards,
Rajendra Sonawane

PO number range per Company code

Hi all,
we have a requirement to assign a separate purchase order number range for each company code. I know there are several user exits for number ranges but does anyone have any specific advice / experience about this?
Many thanks
Phil.

check this one .
Develop Enhancements for Purchasing
In this step, you develop enhancements for Purchasing.
The following SAP enhancements are available for the Purchasing area:
AMPL0001
User subscreen for additional AMPL data (Manufacturer part number)
LMELA002
Adoption of batch number from shipping notification at time of posting of a goods receipt
LMELA010
Incoming shipping notification: adoption of item data from IDoc
LMEQR001
User exit for source determination
M06B0001
Role determination for release of requisitions
M06B0001
Changes to communication structure for release of requisitions
M06B0003
Number range and document number
M06B0004
Number range and document number
M06B0005
Changes to communication structure for overall release of purchase requisitions
M06E0004
Changes to communication structure for release of purchasing document
M06E0005
Role determination for release of purchasing documents
ME590001
Grouping of requisitions for PO split in transaction ME59
MEETA001
Determination of schedule line type (backlog, immediate requirement, forecast)
MEFLD004
Determination of earliest delivery date for checking at time of goods receipt (PO only)
MELAB001
Generation of forecast delivery schedule: realization via creation profile
MEQUERY1
Enhancement for document overview ME21N / ME51N
MEVME001
Calculation of default GR quantity and over/underdelivery tolerances
MM06E001
User exits for inbound EDI messages and outbound purchasing documents
MM06E003
Number range and document number
MM06E004
Control of import data screens in purchase orders
MM06E005
Customer fields in purchasing documents
MEREQ001
Customer's own data in purhcase requisitions
MM06E007
Change document for requisitions when converting into POs
MM06E008
Monitoring of contract target value in case of release orders
MM06E009
Relevant texts for "Texts exist" indicator
MM06E010
Field selection for vendor address
MM06E011
Activation of requisition block
MM06L001
Exits for determination of ratings in vendor evaluation
MMAL0001
ALE source list distribution: outbound processing
MMAL0002
ALE source list distribution: inbound processing
MMAL0003
ALE purchasing info record distribution: outbound processing
MMAL0004
ALE purchasing info record distribution: inbound processing
MMDA0001
Default values for delivery addresses
MMFAB001
User exit for generation of releases
MRFLB001
Control items during release creation
LWBON001
Enhancement of LIS update through extension of the communication structure MCKONA (business volumes and rebate income)
LWBON003
Change settlement data for end-of-period rebate settlement before creation of settlement documents
LWSUS001
Customer-specific source determination in Retail
Activities
1. Either create a new project or use an existing one and then enter the enhancement.
2. Activate the project
Your enhancement will only become effective after activation.
Further notes
In contrast to modifications, enhancements are basically release-insensitive since they are not implemented in the SAP original but in a name range that is reserved for the customer.
The general procedure for creating enhancements can be found in the enhancement transaction at Help -> Application help.
If you want to display the documentation for an enhancement, choose Goto -> Documentation in the enhancement transaction.
Regards
Prabhu

Problem of number range object

hi experts,
the user use PA40 to record events and create an employee, the user wants the system to warn if the total number of employee beyond limits.
so i found an exit 'PBAS0001' and implements it, if the total number beyonds limits, and popup to warn user and exit. But the number of employee is got from the number range object. when the program runs to the PBAS0001, the number range object has already add one, and next time when employee created, the employee number wouldn't be continuous.
if the employee number must be continuous, so how to solve this problem? or is there other exit fm runs before the number range object adds? i found an exit named HRBAS00_STRUAUTH runs befor the range object but the necessary parameter is not all ready.
hunger for your advices, and thanks a lot.

hi,
please describe in a more detailed way ....
when you start the transaction the numer is for examle 2000 you save the employee. And now you start your transaction again which number is shown now ?
regards

External Number Range for Billing documents in CRM

In CRM, billing document external number range can only be numeric or alpha, but NOT alphanumeric. Is this a bug or is there some legitimate reason to have this limitation.
This question stems from a data conversion where the legacy system invoice numbers are alphanumeric. So when we try to convert those invoice numbers, CRM cannot handle the external alphanumeric number.

Check this thread
[Re: Customize Billing Number Format|Re: Customize Billing Number Format]
thanks
G. Lakshmipathi

Is it possible to gater three data in one number ranger (Ecc - CRM)

Hi, all.
Now, we plan to gather three data types in CRM
: employee in HR, students in CM, BP(Gen.) in CRM
In other words, we want to dowload two data types from ECC to CRM
and to save BP in one number range in CRM .
Then we want to save the three data in one number range in CRM, for employee.
Is this possilbe?
If it is possible, do I implement something special?
Regards,
Han Kyu

Han,
It appears you can control the number range for replication of the employee record when using ALE. Now the here are the limitations for your scenario to work:
- You must use an internal number range that is either the default internal range, or explicit configure a grouping to be used. By default the system will download into the default grouping.
If your goal is for all partners to exist in one grouping called ZALL.
Then ZALL needs to be assigned an internal number range and marked as the standard internal number range for all CRM business partners.
Once this is done, then your employee download will use this ZALL grouping, you then will want to "hide" all the non-standard groupings for creation in CRM.
Your CM application then needs to replicate it's business partners to your ZALL grouping.
Take care,
Stephen

Validity & Number range for permits

Hi,
Can we map validity for permits in SAP PM permit standard functionality. I was advised for WCM however that seems a complex system as per our requirement.
Validity of permits, auto permit number assignment while assigning permit is the requirement.
Any inputs?
Regards

Hope you have gone through that blog.
Permits are approvals which will be created as one time master data & the same can be used for many orders.
So, it doesn't have any number range. Also, this master data is very limited.
You can't set the validity date range for permit, I feel.
Instead, in IPMD, you can sen Usage Block that will avoid the usage of that specific permit further.
Suggest you to read some documents & links on permits to understand the concept.
You can get the links in google.

Creating Multiple Number Range

Hi
I am required to create strings of the following format: XXXXYYYYY. A customized program will read in a string of 4 characters (XXXX) and generate a running number (YYYYY) for it. Every unique XXXX has its own running number range. The strings XXXX are stored in the database. More XXXX could be added to the database in the future.
For example,
TA0100001,TA0100002....
SB0200001...
SB0300001...
Is there a function to create the number ranges? Any advice on how I should approach this problem? Thanks!

Hi,
I will suggest two idea's for the same.
Create one number range object for YYYYY and then append it to XXXX that is there in database, but here the number of strings that you can generate are limited.
Another Idea is to create say 5 Nmber range objects.
And have it like if XXXX is in range1 to range 2 use Number range object1 to get YYYYY.
And if XXXX is in range 2 to range 3 then use number range object2 (Or interval 2 of the same number range object 1 that is if you want only one number range object and have 5 intervals instead of 5 number range objects.) to get YYYYY. With this you will more options for generating the required XXXXYYYYY.
Transaction for creating number ranges is SNRO.
Regards,
Sesh

Why most of the number range are maintain year wise

Hi,
I want to know why most of the number range like Part1 and part2 57F4 Challan goods issue , GR, number range are maintain year wise.
regards,
zafar

Hi ,
There may be a lots of documents in a business . But SAP has provied limited no for documents ( upto 999999999). So if you are running your business for a long time , it may happen that the no. of documents may go beyond this no.Year wise no range allows us to use the same no . in another year . So that the combination of fiscal year and document no is sufficient to uniqly identify one document .
Regards,
Anupam

Excise invoice and domestic invoice sharing same number range

Hi,gurus,my question is addresed to the sap cin gurus
Scenario:-- Normally sap has provided provisions that the domestic invoice and the excise for the export will have different number range object
Transaction-snum or snro(As per the rule the no range has to be approved by excise authorities)
Requirement:--The present requirement of the client is that as per their requirement they will be using the same excise number range both for domestic and the export(They have got the approval from the excise department as per the amendment,that specifies the same)
so i request you to pls guide me as how can it be done in sap that two different business process will share the same number range.
as per my knowledge local excise number range is-J_1IEXCLOC
and for exports is-J_1IEXCEXPand the both will use the same number range and,suppose 1 local invoice is created and say if the no is 1,then if the export excise invoice is created the number will be 2,pls guide me how is it possible that the same number range should be used.
Thanks in advance---Anshuman chakraborty

Dear sir,Thanks for attention towards the issue,but still i need to clarify some details-
the number range forJ_1IEXCLOC are already configured .It is not the case like i have to configure it for the first time however ,so the issue remains how shall i proceed in this case
Sir,i have already checked the transaction j1iin,it does not give any such box to check the-use local no range
infact the error message which the system was throwing to the user that-number range object not assigned for Object: J_1IEXCEXP.
The question remains from my side is what are the complete configuration steps I need to do ,to make the check box appear so as to select-use local number range,and is there any thing to be conveyed to my developer,so that the same appears,
or is it the case like the anything should earlier have been done before the number range for J_1IEXCLOC was created.i would request u to pls guide me giving the complete details of the step to be followed.
Thanks in advance
Anshuman chakraborty

Maintain tolerance limits in the Tolerance key

Hi,
Could any one help me how to maintain these Tolerance limits in the Tolerance key. This is an error I receive while creating a PO.
Best Regards,
Sridhar.k

What is the Error Mesaage no you are getting??
Solution is as Follows
Set Tolerance Limits for Price Variance
In this step, you define the tolerance limits for price variances.
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 <b>Environment -> Define Attributes of System Messages.</b>
Activities
Maintain the tolerance limits for each tolerance key per company code
Regards
Biswajit

Tolerance limits & Number ranges

Similar Messages

Maybe you are looking for