GR tolerance in MFBF

Hello,
Can I give a tolerance when I do GR for the planned order in MFBF, to restrict the GR qty?
Thanks,
Harvey

Dear Harvey,
In my understanding all the material which is been produced in REM scenario will not be having a work scheduling view and it's
not required.In this case the advantage of REM is even if there is no planned order still you can carryout assembly backflush
directly for a material,plant combination by mentioning the quantity.
Additonally if you make the planned order field as mandotory you may be able to achieve this,but GR tolerance cannot be given
at planned order level.And additonally even if you make GR,this will be adjusted for the later future requirements.
So in standard SAP I dont think it's possible to assign a GR tolerance value at planned order level.
Check and revert back.
Regards
Mangalraj.S
Edited by: Mangalraj.S on Jul 14, 2009 10:40 AM

Similar Messages

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

Purchase Order Goods Receipt quantity tolerance setting not working.

Team,
We are using the IS-Oil solution, ECC 6.0 REL 605 SP LEVEL 009 .
The issue that I have is as follows:
Purchase Order Goods Receipt quantity tolerance setting not working, I had set up a 10% tolerance on QTY received in the GR process via the PIR and also the Purchase Value Key in the material master and also changed the message to a warning in OMCQ for message number M0722.
I had performed a similar configuration and master data maintenance on a different NON IS-OIL client install and it worked fine.
I believe it is the IS-OIL component in the Inventory update portion of the GR process that is causing the error.
I have searched for OSS notes, however they mention that there is no solution.
Setting the PO line item as Unlimited will not be best practice for the business and will not be used.
Has anyone come across this issue? and how was it resolved, your help and guidance will be greatly appreciated.
Thanks

Hello,
Please check the Tolerance levels in O588
Also you can use the BAdI OIB_QCI_ROUND_QTY: A new method, CHECK_TOLERANCE
Best Regards,
R.Brahmankar

Transaction BORGR: No tolerance on goods receipt for Kanban calloff

Hello,
we have the following situation:
- MM scheduling agreement with tolerance of 10% for under and overdelivery, production supply "summarized JIT call" is set.
- KANBAN cycle has 1 empty container with a summarized JIT call for replenishment, quantity 10 pieces.
- ASN has been created with BORGR transaction, it contains: 1 line item for the material with delivery quantity 9 pieces, assigned to this line item is the JIT call with notified quantity 9 pieces as well.
My expectation was that the JIT call can be booked with 9 pieces as it is inside the 10% tolerance defined for the scheduling agreement. In addition, I expected the KANBAN container be set to full.
Instead, the following error message is given:
'Post GR' carried out without success
(Message no. BORGR215)
Because of previous error, dispatching is not possible for ID 0180573431
(Message no. /SPE/ID_HANDLING011)
Inbound Delivery 0180573431 00010
(Message no. BORGR210)
Total of the summarized JIT calls does not match the current delivery qty
(Message no. BORGR540)
Changing the delivery quantity and the notified JIT quantity to 10 pieces, the goods receipt is booked correctly.
I only found the following notes that deal with tolerances but they are outdated, as we are using DIMP release 603:
https://service.sap.com/sap/support/notes/393421
https://service.sap.com/sap/support/notes/508215
Has anybody faced a similar problem or can help me with this?
Thanks!

Hello Jiaul,
Sorry I may have mislead you. The actual error message is "Goods Receipt for Production Order XXXX can only be made on 2010.08.25 to 2010.08.27". These two dates are the Start Date and FInish Date for the Production Order in CO03,
The Basic Start Date for the current Production Order is 2010.08.25
The Basic Finish Date for the current Production Order is 2010.08.27
I think what it means is that you can only Post Goods Receipt for the Production Order only after the Basic Start Date of the Production Order. Do you know where I can find the configuration for this message?
Thanks

DUMP in MFBF transcation

Hi Folks,
Users getting the frequent dumps in production systems. actaully we observed that dumps are coming when the users accessing the MFBF transaction manually when the batch job was running for backflush and NRIV (number ranges) table is getting locked.
The dump details is:
ABAP/4 runtime error DBIF_RSQL_SQL_ERROR
Occurred on 16.04.2007 at 15:57:10
>> Short dump has not been completely stored. It is too big.
SQL error 60 occurred when accessing table "NRIV ".
What happened?
The database system detected a deadlock and avoided it by rolling back
your transaction.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLSNR3" in
"READ_NRIV".
The main program was "SAPLBARM".
The termination occurred in line 231
of the source code of program "LSNR3F01" (when calling the editor 2310).
The error occurred during batch input processing
Source code extract
002010 NRIV-TOYEAR = BNRIV-TOYEAR.
002020 G_FOUND = YES.
002030 WHEN 4.
002040 WHEN OTHERS.
002050 G_ERROR_IN_BUFFER = YES.
002060 ENDCASE.
002070 ENDIF.
002080
002090 IF BUFFER_ACTIVE = NO OR G_ERROR_IN_BUFFER = YES.
002100 * Die Pufferversion ist nicht aktiv oder es wurde bereits
002110 * ein Fehler im Puffer oder NrKreisServer festgestellt.
002120 * Gⁿltiges NrKreisIntervall mit Bis-GeschΣftsjahr aus der
002130 * DB ermitteln
002140 *
002150 SELECT * FROM NRIV WHERE OBJECT = P_OBJECT
002160 AND SUBOBJECT = P_SUBOBJECT
002170 AND NRRANGENR = P_NR_RANGE_NR
002180 AND TOYEAR >= P_TOYEAR
002190 ORDER BY PRIMARY KEY.
002200 G_FOUND = YES.
002210 EXIT.
002220 ENDSELECT.
002230 ENDIF.
002240
002250 IF G_FOUND = YES.
002260 * Intervall lesen, um zu sperren
002270 SELECT SINGLE FOR UPDATE * FROM NRIV WHERE
002280 OBJECT = NRIV-OBJECT
002290 AND SUBOBJECT = NRIV-SUBOBJECT
002300 AND NRRANGENR = NRIV-NRRANGENR
> AND TOYEAR = NRIV-TOYEAR.
002320 IF SY-SUBRC <> 0.
002330 MESSAGE E751 RAISING INTERVAL_NOT_FOUND WITH P_OBJECT
002340 P_NR_RANGE_NR.
002350 ENDIF.
002360 ELSE.
002370 MESSAGE E751 RAISING INTERVAL_NOT_FOUND WITH P_OBJECT
002380 P_NR_RANGE_NR.
002390 ENDIF.
002400 ENDIF.
002410
002420 IF NRIV-EXTERNIND <> SPACE.
002430 MESSAGE E752 RAISING NUMBER_RANGE_NOT_INTERN.
002440 ENDIF.
002450
002460 * LΣnge (maximale Anzahl Stellen) der Nummern berechnen
002470 G_NR_LENGTH = STRLEN( NRIV-FROMNUMBER ).
002480
002490 * Nummern in numerische Felder fⁿr spΣtere Berechnungen ⁿbernehmen
002500 ASSIGN NRIV-FROMNUMBER(G_NR_LENGTH) TO <G_F>.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 1
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 32 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
Chosen variables
Any help will get full points.
Regards
TAJUDDIN

Hi Prabhu,
This problem is in 3.1i for which there is no SAP note. Notes are available for 4.6c.
Is there any possibility that we can modify the SAP note of 4.6c and implement in 3.1i?
Regards
TAJUDDIN

DUMP in the MFBF transaction

Hi Folks,
Users getting the frequent dumps in production systems. actaully we observed that dumps are coming when the users accessing the MFBF transaction manually when the batch job was running for backflush and NRIV (number ranges) table is getting locked.
The dump details is:
ABAP/4 runtime error   DBIF_RSQL_SQL_ERROR
       Occurred on     16.04.2007 at 15:57:10
>> Short dump has not been completely stored. It is too big.
SQL error 60 occurred when accessing table "NRIV ".
What happened?
The database system detected a deadlock and avoided it by rolling back
your transaction.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLSNR3" in
"READ_NRIV".
The main program was "SAPLBARM".
The termination occurred in line 231
of the source code of program "LSNR3F01" (when calling the editor 2310).
The error occurred during batch input processing
Source code extract
002010             NRIV-TOYEAR    = BNRIV-TOYEAR.
002020             G_FOUND        = YES.
002030           WHEN 4.
002040           WHEN OTHERS.
002050             G_ERROR_IN_BUFFER = YES.
002060         ENDCASE.
002070       ENDIF.
002080
002090       IF BUFFER_ACTIVE = NO OR G_ERROR_IN_BUFFER = YES.
002100   *          Die Pufferversion ist nicht aktiv oder es wurde bereits
002110   *          ein Fehler im Puffer oder NrKreisServer festgestellt.
002120   *          Gⁿltiges NrKreisIntervall mit Bis-GeschΣftsjahr aus der
002130   *          DB ermitteln
002140   *
002150         SELECT * FROM NRIV WHERE OBJECT    = P_OBJECT
002160                              AND SUBOBJECT = P_SUBOBJECT
002170                              AND NRRANGENR = P_NR_RANGE_NR
002180                              AND TOYEAR   >= P_TOYEAR
002190                       ORDER BY PRIMARY KEY.
002200           G_FOUND = YES.
002210           EXIT.
002220         ENDSELECT.
002230       ENDIF.
002240
002250       IF G_FOUND = YES.
002260   *          Intervall lesen, um zu sperren
002270         SELECT SINGLE FOR UPDATE * FROM NRIV WHERE
002280                                     OBJECT    = NRIV-OBJECT
002290                                 AND SUBOBJECT = NRIV-SUBOBJECT
002300                                 AND NRRANGENR = NRIV-NRRANGENR
>                                 AND TOYEAR    = NRIV-TOYEAR.
002320         IF SY-SUBRC <> 0.
002330       MESSAGE E751 RAISING INTERVAL_NOT_FOUND WITH P_OBJECT
002340                                                    P_NR_RANGE_NR.
002350         ENDIF.
002360       ELSE.
002370       MESSAGE E751 RAISING INTERVAL_NOT_FOUND WITH P_OBJECT
002380                                                    P_NR_RANGE_NR.
002390       ENDIF.
002400     ENDIF.
002410
002420     IF NRIV-EXTERNIND <> SPACE.
002430       MESSAGE E752 RAISING NUMBER_RANGE_NOT_INTERN.
002440     ENDIF.
002450
002460   *    LΣnge (maximale Anzahl Stellen) der Nummern berechnen
002470     G_NR_LENGTH = STRLEN( NRIV-FROMNUMBER ).
002480
002490   *    Nummern in numerische Felder fⁿr spΣtere Berechnungen ⁿbernehmen
002500     ASSIGN NRIV-FROMNUMBER(G_NR_LENGTH) TO <G_F>.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 1
SY-TABIX 1                             SY-DBCNT 1
SY-FDPOS 32                            SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1
Chosen variables
Any help will get full points.
Regards
TAJUDDIN

Dear All,
Notes are available for 4.6c version. This problem is in 3.1i and for this there is no note. Can we modify this 4.6c note and use in 3.1?
Regards
TAJUDDIN

EBS Customer open items automatic clearing within tolerances

Hi Experts,
We have already implemented Elecronic Bank Statements automatic uploading functionality. As part of this process, customer open items need to be cleared automatically.
As per the standard process, SAP will be able to clear off the open items ONLY if the collection amount (reflected in MT940) is exactly equal to the invoice amount (reflected in the open item). But general practical situation is that customers may under / over pay. For example, if the customer invoice is for USD 100,005 the actual payment from the customer could be for USD 100,000. In this case, it is normal business practice that open item will be cleared off rather than keeping balance USD 5 in ledger and chasing the customer.
So tolerances are already set up both at GL account level (Trans OBA4) and customer level (Trans OBA3) with blank tolerance group with permitted payment difference of USD 15. And no tolerance group is assigned to the customer master. Also account determination is maintained for the differences with nil reason code.
Inspite of all these settings, I am getting an error message indicating that the difference is too large for clearing while trying to upload this bank statement. Here the difference is only USD 5.
My doubts are:
1. Does the standard EBS program RFEBKA00 considers the permitted payment difference tolerances set in transaction OBA4 and OBA3 ? I don't need to post the differences with reason code. That's why account determination is maintained with blank reason code as well.
2. SAP Note 124655 (Point No 3) says that entering reasons for differences is not possible in the standard system through EBS. Does that mean clearing of open items WITHOUT reason code is possible ?
3. SAP Note 549277 (Point No 5) says that even though Note 124655 specifies certain functionalities as not supported in standard system, they can be achieved by customer through user exits. Does that mean it is possible to code in the user exit saying that system should consider the payment difference tolerances for clearing off of the open items ?
Could you kindly let me know your experience with these questions. I will be very glad to hear from you. Thanks for your time.
Warm regards,
Sridhar

Hi Experts,
I got this resolved by using the enhancement FEB00001. If the field "Distribute by age" is activated through this enhancement, then system will be able to match the paid amount and the combination of open items for automatic clearing. If there is no exact match, then automatic clearing through FF.5 is not possible as indicated in SAP Note 124655.
There is no more necessity to use BAdI FIEB_CHANGE_BS_DATA. Complete relevant logic can be maintained directly in the enhancement itself.
Have a nice day.
Regards,
Sridhar

GR IR CLEARING TOLERANCE LIMIT.

We are clearing in F.13the GR and IR account there is difference in the GR and IR amount by Rs 100 ,SO IT IS NOT CLEARING.
WHERE IS THE SETTING MADE FOR TOLERANCE FOR GR IR CLEARING.PLEASE PROVIDE THE PATH.
Pls help.
Edited by: mysap query on Feb 6, 2009 12:45 PM

resolved

GR/IR clearing with tolerances

Hi,
Where do you specify the tolarences for GR/IR clearing?

Hi,
I believe In MR11 transaction itself you can give the tolerances in the selection-screen..
Thanks,
Naren

IR and GR Tolerant

Hi,
Kindly advise the path for checking the GR and IR tolerant setting.
Thank you.

Hi
For invoice tolreance, you have to as below,
LIV
IMG---> MM-> LIV--> Invoice block----> Set tolerance limits, here you need to define for which activity you need to establocs tolerance limits. That is variances between the invoice and the purchase order or goods receipt.
There are different keys for each stage, there are 12 std. entries available for different variance posting, you can simply copy all of them and enter your company code. Once done, now go to each individual TLKEY and set the tolerance limits for the tolerance keys as required.
GR
You need to set the Purchasing value key in material master which controls the GR quantity , you can have tolreance key attached to the master and during GRN it behaves accordingly.
IMG-->MM>Purchasing>material master>Define Purchasing Value Keys-> Create your own tolerance keys inside uner GR/IR for under delivery and over delivery.
if you have left the field empty in Material master then , during PO creation in the delivery tab you can have the under delivery tab/over delivery tab fileds filled.
Finally check
IMG->MM>Inventory Management and Physical Inventory->Goods Receipt->Set Tolerance Limits-->Set the tolerance level, but this is for price variance level only and i do not think it is useful for you. Please use the purchaing value key or enter the tolerance levels in PO level for GR.
Best Regards
Edited by: samuel mendis on Apr 20, 2009 9:21 AM

Using tolerances in SAPF124 - GR/IR Clearing Program

Hi,
Could anyone tell me what all configuration we need to make to use the include tolerances functionality in program SAPF124. I need to know all the configurations I need to make for using this. I am aware that we need to define tolerances in below Path and also the clearing account respectively
Financial Accounting>General Ledger Accounting>Business Transactions>Open Item Clearing>Clearing Differences>Define Tolerance Groups for G/L Accounts
And
Financial Accounting>General Ledger Accounting>Business Transactions>Open Item Clearing>Clearing Differences>Create Accounts for Clearing Differences
Using these I am not able to clear the differences in GR/IR clearing account. Do I need to maintain some more configs.
Regards,
Vijay

Have you checked "GR/IR account special process" on SAPF124 selection screen...
What about OB74 settings ...
Regards
Siva

PO Tolerance Limit

Hi ,
We have a problem with processing our PO ' s.
For a PO , we have the GR posted , howevre the IR is not getting posted. And this process is automated ( through IDOCS ).
When we analysed the issue, found out that the reason it is not posting is because of this :
" Because there is a diffrenece between the Debits and Credits ( that is the GR and IR Amount ) Say the GR is 500 $ and IR is 600 $ , the system is not posting as the difference is beyond the tolerance limit " ..
So how do i change the Tolerance limits for the POs so the IR posting takes place...
And why does the IR value be greater thatn GR ? If i want to see at what value the IR will post..where can i see that ?
Thanks for any help...
srikanth.

Dear,
There are various tolerance keys are coded in the standard SAP program, few of the example...
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.
Likewise other tolerance keys used by program are BD,BR,BW,DQ,DW,KW,LA,LD,PPPS,ST,VP
These keys are determined by stadard functionality.
Regards,
Chintan Joshi

I am getting error while doing MFBF for semifinisg good

Hi,
i am getting error while doing MFBF for semifinisg good
Existing standard cost estimate cannot be used
Message no. RM175
Diagnosis
This error appears under the following circumstances:
The existing standard cost estimate cannot be used for backflushing activities as the repetitive manufacturing profile was not maintained correctly when the standard cost estimate was carried out.
The standard cost estimate must come from product costing. Other cost estimates (such as base object controlling) are not possible.
Procedure
The repetitive manufacturing profile assigned to the material at the time of the planned cost estimate must be a profile for repetitive manufacturing with product cost collector.
Use product costing to create the standard cost estimate.

I had already check REM profile repetitive mfg profile final backflush w. activities.
this particular material is semifinish material attached in BOM of finish material.
backflush of finish good is possible but now new requirement is to do production booking for the semifinish material.
i had assign production version , done routing and maintain REM profile,
created material cost with quantity structure ck11n then run the costing in ck40n.
still getting the error what else is to done to able to book this thru MFBF.

Gl Tolerance set up for Autoposting

Hi ,
We have EBS files posting to SAP ( autopost) to GL's and some of the entries in this autpost are not cleared automatically the automatic clearing differences are too high. I checked the tolerance group for those GL's in OBA0 ( both From and To ) for a given company code and its Blank there is no tolrance group defined , the limits on the blank tolerance group is very less and it fails to autpost when it is more than 50 million . Can some one let me know what changes I need to make for this autopost to be sucessful when the amounts from the bank file are too large ?
Thanks in advance .

Hi,
maybe I understand you wrong, however the whole purpose of tolerance in deviations is to minimize manual process in the case those differences are immaterial. E.g. your expected incoming payment amount from one of your Customers is EUR 10,00 (ten Euros), however due to whatever reason you receive just 9,95. So instead of starting a manual work flow in your office and negotiating difference of EUR 0,05, which might cost you much more in terms of alternative costs - some time of your human resource, also some correspondence relevant costs, etc. - let's assume EUR 5, you just clear that item, putting that difference amount to some P&L account - this is fully traceable in SAP.
on the other hand, if you talk about deviations of around 50 mio, I don't think it makes any sense, cause it is very huge risk and direct high-way to financial errors and/ or frauds. And, of course, in this case every item should be dealt with proper diligence. also, I assume a number of those material deviations is usually limited, so this is another reason why no automation is expected there.
hope this will help you.
Rgds,
Renatas

SAPSQL_ARRAY_INSERT_DUPREC dump in MFBF

Dear All,
i am getting a problem in MFBF, when we post the document, this gives me
the document successfully posted massage with the document number. But
when we check the document number in MF12 & MB03, There is no document
on that document number.
I have check the short dump, there is a dump in ST22 with
name u201CSAPSQL_ARRAY_INSERT_DUPRECu201D.
Also when i check the update request, there is also a update request
with error.
I have applied the support pack on our server last night that may be
the reason. I have applied SAP_HR 470 from 86 to 91 & SAP_APPL 470
from 29 to 30.
Plz help.
Thanks with regards,
Ankit

Dear,
Please check the number range?It is data base releated problem so take help from technical person some SAP notes are also available please go through it like 1041098.
Regards,
R.Brahmankar

GR tolerance in MFBF

Similar Messages

Maybe you are looking for