MRBR - Invoice not automatically released

Hi
I have the following scenario
PO raised for qty 1 value 100
GR completed for qt1 value 100
Invoice created for qty 1 value 110
The invoice is automatically blocked which is correct, then a credit note is entered in MIRO for 10.
Now when I run MRBR with the auto release option the invoice is not unblocked, do you know why this is is the case?
thanks Joe

Hi,
Do refer the below KBA, which explains you why MRBR not released the Invoice with credit memo and corresponding solution.
KBA: 1781064 - MRBR transaction not releasing payment block on credit memo
You may also can have a look on below KBA's which may help you..
1906013 - FI Block can not be released via MRBR
1790472 - MRBR - Invoices not released Automatically

Similar Messages

Transports not automatically released SDMJ

Hi-
I am at the step where I confirm a successful test in my charm scenario. According to the SAP process for normal corrections (sdmj), at this point the status turns to Consolidated and the original transport request gets released automatically. The transport is not being released.
Any thoughts?

There is one possible reason.. check your all transport of copies has been imported or not. . Because once you select "Confirm successful teat" first system change status to "Consolidated" then after trying to release transport. Before releasing actual transport.. system check all transport of copies has been successfully imported in QA or not. If one of request is waiting for import then transport will not be released. Please check Display/Close message window. Your CR will return status message over there... Hope this will help you to understand.
Thanks
Jignesh

Invoice not automatically cleared while reversed

Dear SAP experts,
we are facing the problem which lasts from year 2002. There was posted an accrual invoice in period 06/2002. This invoice was reversed in period 07/2002 with Reversal Reason "Actual reversal in closed period (RED)".
Both invoices (invoice and its reversal) are now showing as not cleared in FBL3N. Also there does not exist the field "Clearing date" on any of line items. But at the document header we can see the connection to the reversal (Reversed by....).
When we try to simulate the same situation in the test system, there is always the connection field "Clearing date" and it is not showing in FBL3N.
Is there any possibility to connect the invoice and its reversal (item by item)?
Thank you very much for your ideas.
Alena

Hi Alena,
You have to include the field BKPF-STBLG in the below path if you are in versions less than ECC
FBL3N (G/L account line item display)
Financial Accounting
General Ledger Accounting
    G/L Accounts
      Line Items
        Display Line Items with ALV
          Define Special Fields for Finding and Sorting Data
Once the changes are done, you can see the reversed document against the line items display in FBL3N.
For more details please have a look at SAP Note 984305 - Line item: Definition of special fields (T021S)
Thanks
Aravind

Report on Manual and Automatic release of Invoices - MRBR

Hi Gurus,
What is the difference between Manual Release and Automatic Release of Invoice in MRBR?
How can i get the report of invoices release automatically and invoices released manually?
Please revert asap.
Thank You

Hi,
Rlease Manually
The system creates the list of blocked invoices as soon as you choose Execute. On this list, you can release invoices or delete individual blocking reasons!
Release Automatically
If you select this field and choose Execute, the system deletes all blocking reasons that satisfy the criteria entered in the group box Selection of blocked invoices and that are no longer relevant. A list of the released invoices appears.
That's it!
Good day
Tao

Automatic release of blocked Invoices

Note - Posted this qns in Financial forum & the user suggested to post the same question in this forum.
Hi All,
Scenario - A PO is placed with GR based IV unchecked. The vendor is sending the material & invoice to us. But the material is to arrive from overseas & hence there is a delay, but in the meantime i have posted the invoice in the system & the system blocks this invoice. I can check the blocked invoices in MRBR. At the moment to release it, i would have to use transaction MRBR, but I would like to know is there anyway, that the system can be configured to automatically release this blocked invoice, once the GR for that material is done, without me having to use any t-code?
Vivek

Hi Steve,
   There are 3 blocking reasons in MRBR,
1. Blocked due to variances
2. Manual Payment Block
3. Stochastically blocked
   In this case, what is the reason for blocking?. If it is reason 1, then if i schedule a MRBR with automatic release, then would it release all those invoices as well which have been blocked due to price variation? or would it only release those Invoices which have been blocked due to non-receipt of GR?
   Also would like to know, is there anything in customizing, where i can define, say if the Purchase Order has got a Shipping Notification control key entered, then release this invoice?
   In customizing Financial Accouting -> Accounts Receivable & Accnts Payable -> Business Transaction -> Release payment
    Would this be of any help to me for resolving the issue at hand?
Vivek

Issue - automatic release block in MRBR for planned costs (tol KW/PP)

Tolerance key KW is defined for planned costs. The tolerance is correctly selected in MIRO and invoices are blocked appropriately; there is no issue in MIRO.
The block for planned costs is indicated as a price variance in MRBR and the condition is listed. When MRBR is executed in 'Release Automatically' mode, system checks the tolerances defined under tolerance key PP rather than KW. MRM_TOLERANCE_CHECK is called for tolerance key PP.
Because the tolerance amount for tolerance key PP is checked rather than tolerance key KW (planned costs), invoices are released erroneously. The tolerance for KW should be checked instead.
Has anyone encountered this issue? If so, what action did you take?
Thank you in advance.

Thank you for your input. However, this does not solve the issue. The tolerances should be checked appropriately in MRBR in the same way as in MIRO. KW should be checked for planned costs and PP for the articles.

Automatic Release of invoice with price differance

Hi
All price differences when matching the PO, GR and invoice ends up in MRBR with price difference block. It works fine for POs with goods. But when a service is entered in the PO we can not get it released automatically.
We create a PO (service)
Service entry sheet of the full amount of the PO
Create invoice with price difference
Change PO to invoice price
Run MRBR....
But it is not released. The price difference is still there even though we have changed the PO.
What have I not thought of?
Sincerely
Anders

Hi
Standard SAP states:
During the entry of an invoice for a service, the system proposes the value from the service entry sheet but not the purchase order value.Correspondingly, the invoice value is compared with the value of the entry of services during the invoice release and not with the purchase order value, as is the case with another purchase order.
Will I have to change the price in the service entry sheet for the invoice to be released?
Sincerely
Anders

Automatic release of Blocked Invoice by Doing Further GR

I have the following Scenario:
P.O is for 100 nos. GR is made against the P.O for Qty:50 nos. Invoice is made in MIRO for Qty:70 nos. Now the invoice is posted and is "Blocked for payment".
To release this invoice, as per SAP documentation, the following are possible:
<b>1. Posting a Credit Memo for the difference Qty of 20 nos
2. Creating delivery for additional 20 nos.</b>
In actual, in the first instance, the invoice gets released automatically in MRBR after posting the credit memo.
However in second case, after doing MIGO for additional 20 nos, Invoice does not get released automatically.
Can you throw some light on the "Delivery" option and Is there a configuration setting which can take care of this issue.
Thanks
Vinay & Sanjog

Hi,
If the "difference qty" comun is not getting updated then there is no difference qty and the invoice would NOT have been blocked due to a qty difference.
The status of "fully delivered" is not relevant.
If you have a PO for a qty of 100 , a GR of 100 but an invoice for 120. The status would be "fully delivered" but the invoice would be blocked due to a qty difference.
Posting another receipt of 20 (providing the delivery tolerance allows it) would result in the invoice being released.
I am sorry but the system appears to be doing what it should do.
If the invoice was blocked and there was no qty difference displayed (and if the blocking flag was not highlighted in yellow) in MRBR, then there is NO qty difference and the block is due to something else (such as price etc.)
If posting a further receipt has now cleared the invoice for payment then there WAS a qty block and the invoice qty must have been greater than the PO qty (the "fully delivered" status means nothing here, it just means that the delivery qty matches the PO qty, it does not relate to the invoiced qty.
Steve B

Excise Invoice Not creating automatically

Hello!
while doing Billing document using VLO1N,Excise invoice is not creating for a particular material. I checked Material Master for this particular item.I compared the Material Master for the item which is creating Excise Invoice automatically and the for the item Excise Invoice not creating automatically. Every thing is same for both the items but the excise invoice is creating automatically for one material and same Excise invoice is not creating automatically for another item.I don't know where is the exact problem is.could anyone tell me why the Excise Invoice is not creating for the particular item.
-M.Suba

Excise Invoice creation depends on Customizatoin of Excise group which is specific to Plant.
Check Customization settings-
IMG: Logistics General - Tax on Goods movements - INDIA - Basic Settings - Maintain Excise Group,
select your excise group & choose details,
You will observe, check box " Excise Invoice during Billing" in 'Outgoing Excise Invoice' section. This check box should be marked.
Note: To create Billing documents - Tx :VF01 is used , not VL01N ( this is for Creating Outbound Delivery document)
Regards,
Reazuddin MD

Output Type not automatically determined at invoice creation

Hi Friends,
I am facing a problem that while i am generating the invoice for a particular billing document type, the output type is not automatically being determined. Instead, I have to go into the invoice in change mode (VF02) Header>Output and assign the output type to it and select the local printer and save in order to print the invoice.
I am generating the invoice for this Invoice Type/Output type for the first time.
Please suggest the possible causes.
Regards,
Pankaj

Hello Pankaj,
Suppose you are using output type RD00 for invoice print out. You have maintained the condition record for RD00 in transaction code VV31. The most important thing here is the assignment of the printer.
Suppose for output type RD00 you are maintaining the condition record for key combination - Sales Organization + Distribution Channel + Division.
At the header level you will see the Sales Organization & Distribution Channel & at the item level you will see the Division.
Sales Organization = BP01
Distribution Channel = 01
Division.............Name..........Funct.........Partner............Medium......Disp. Time.....Langu
01............... Std Division..........BP............--......................1......................3................---
Select the line item & click on Communication. Here assign the output type which you will use for the print out. Now Save the condition record.
After doing this try running one sales cycle - sales order - delivery - invoice. Save the invoice & now check in the change mode (transaction code VF02) the system will determine the output type RD00 automatically.
Note:
1. In the create mode the system will not display the output type RD00, after you have saved the invoice the output type will be determined automatically.
2. Also check if there is any requirement assigned for the key combination in the access sequence (IMG - Sales and Distribution - Basic Functions - Output Control - Output Determination - Output Determination Using the Condition Technique - Maintain Output Determination for Billing Documents - Maintain Access Sequences)
With best regards,
Allabaqsh.
(Idhasoft Ltd.)

Bill doc could not be released to accounting automatically

I have a problem on a particular billing type (document category P u2013 debit note) where the billing document could not be released to accounting automatically upon saving. The message VF050 is shown with Document xx saved (no accounting document generated). Subsequent release of the billing document to the accounting manually has no problem and no error was thrown. Looking through the account determination analysis shows that the correct revenue account is determined, so there should be no problem with the account determination setup. The billing type is also not set up with posting block, so it should release to accounting automatically.
What could be the possible problems or any other areas that I could check to trace the problem?
kt

Hi KT
First of all check in VOFA wheather Posting block has been maintained or not
Secondly also check wheather Revenue Account determination procedure has been done or not
Run VFX3 and finally pass it on to FI and while passing it on to FI you can check why the error has occurred
Regards
Srinath

SolMan Charm: wbch and customizing TR not always automatically released

Dear solman experts,
In Charm, when users save a status linked to the background action "release_all" in order to release their transport requests, the transports are not always released.
I know this could happen with ToC and also with TR (mostly for workbench), but this is happening to lots of customizing transports.
I tested it with some small configuration (like for instance a TR with roles in it), the release works fine.
So the configuration of solman seems ok.
Does anyone have already faced the same issue and has an idea on what to do in order to avoid this issue?
Thanks for your help,
Kr,
Alice

Hello Khalil,
In the maintenance cycle, the ongoing phase is "development with release" so it is ok.
Also, all tasks have already been released as one of the previous status/action triggered the creation of a ToC (and for that the check of all released tasks is performed). So we have like two testing cycle (a first one with ToC where all tasks are already released) and if it is ok you can then set a status which triggers the "release_all" action to release the orginial transport requests.
What is really strange is that in the tasklist, the release request activity is correctly launched but has an error " /TMWFLOW/TRANSPORT_N643" which says that :
- Diagnosis --> The request BRDK922172 has already been released (but it is not the case)
- System Response --> The system does not allow you to create a transport of copies. (but it is not the action concerned here "the activity on which I receive this error is "release_all""
- Procedure--> It is not usually necessary to create a transport of copies for a request that has already been released.Perhaps you entered an incorrect request, in which case you have to enter a different one.
I do not get what is this error message about. And what is really strange is that for some transport requests the release works and for other not (but more and more are not working)
Have you an idea?
Thanks a lot for your help,
Alice

Block is not automatically Removed

Dear All ,
The system does not automatically remove the blocking reason I, if an acceptance decision is made for the inspection lot concerned. the blocking reason I must be removed in the invoice inspection/invoice release function.
Release of invoice block u2013 can it be automated from the IL release process ?
Thanks & Regards,
Deepu.

Use MRBR for release, you can schedule a job run for this program to run every night if required.
Regards,
Vivek

Automatic release to accounting

How can I make my cancellation of invoice automatically release to accounting? Thank you.

Hi Rumar,
By default, automatic postings will happen if the posting block is not ticked.
If your cancellation document is not posting automatically, that means the accoutn keys and the GL accounts are not mapped correctly.
So go to the cancelled invoice, in change mode,and now do a account determination analysis. In this you can capture the errors if at all any.
Once all the automatic account assignments are done, if your VOFA posting block is unchecked, automatic posting will take place.
Reward points if this approach helps.

Applets and memory not being released by Java Plug-in

Hi.
I am experiencing a strange memory-management behavior of the Java Plug-in with Java Applets. The Java Plug-in seems not to release memory allocated for non-static member variables of the applet-derived class upon destroy() of the applet itself.
I have built a simple "TestMemory" applet, which allocates a 55-megabytes byte array upon init(). The byte array is a non-static member of the applet-derived class. With the standard Java Plug In configuration (64 MB of max JVM heap space), this applet executes correctly the first time, but it throws an OutOfMemoryException when pressing the "Reload / Refresh" browser button or if pressing the "Back" and then the "Forward" browser buttons. In my opionion, this is not an expected behavior. When the applet is destroyed, the non-static byte array member should be automatically invalidated and recollected. Isn't it?
Here is the complete applet code:
// ===================================================
import java.awt.*;
import javax.swing.*;
public class TestMemory extends JApplet
private JLabel label = null;
private byte[] testArray = null;
// Construct the applet
public TestMemory()
// Initialize the applet
public void init()
    try
      // Initialize the applet's GUI
      guiInit();
      // Instantiate a 55 MB array
      // WARNING: with the standard Java Plug-in configuration (i.e., 64 MB of
      // max JVM heap space) the following line of code runs fine the FIRST time the
      // applet is executed. Then, if I press the "Back" button on the web browser,
      // then press "Forward", an OutOfMemoryException is thrown. The same result
      // is obtained by pressing the "Reload / Refresh" browser button.
      // NOTE: the OutOfMemoryException is not thrown if I add "testArray = null;"
      // to the destroy() applet method.
      testArray = new byte[55 * 1024 * 1024];
      // Do something on the array...
      for (int i = 0; i < testArray.length; i++)
        testArray[i] = 1;
      System.out.println("Test Array Initialized!");
    catch (Exception e)
      e.printStackTrace();
// Component initialization
private void guiInit() throws Exception
    setSize(new Dimension(400, 300));
    getContentPane().setLayout(new BorderLayout());
    label = new JLabel("Test Memory Applet");
    getContentPane().add(label, BorderLayout.CENTER);
// Start the applet
public void start()
    // Do nothing
// Stop the applet
public void stop()
    // Do nothing
// Destroy the applet
public void destroy()
    // If the line below is uncommented, the OutOfMemoryException is NOT thrown
    // testArray = null;
//Get Applet information
public String getAppletInfo()
    return "Test Memory Applet";
// ===================================================Everything works fine if I set the byte array to "null" upon destroy(), but does this mean that I have to manually set to null all applet's member variables upon destroy()? I believe this should not be a requirement for non-static members...
I am able to reproduce this problem on the following PC configurations:
* Windows XP, both JRE v1.6.0 and JRE v1.5.0_11, both with MSIE and with Firefox
* Linux (Sun Java Desktop), JRE v1.6.0, Mozilla browser
* Mac OS X v10.4, JRE v1.5.0_06, Safari browser
Your comments would be really appreciated.
Thank you in advance for your feedback.
Regards,
Marco.

Hi Marco,
my guess as to why JPI would keep references around, if it does keep them, is that it propably is an implementation side effect. A lot of things are cached in the name of performance and it is easy to leave things laying around in your cache. Maybe the page with the associated images/applets is kept in the browser cache untill the browser needs some memory and if the browser memory manager is not co-operating with the JPI/JVM memory manager the browser is not out of memory, thus not releasing its caches but the JVM may be out of memory. Thus the browser indirectly keeps the reference that it realy does not need. This reference could be inderect through some 'applet context' or what ever the browser uses to interact with JPI, don't realy know any of these details, just imaging what must/could be going on there. Browser are amazingly complicated beast.
This behaviour that you are observing, weather the origin is something like I speculated or not, is not nice but I would not expect it to be fixed even if you filed a bug report. I guess we are left with relleasing all significatn memory structures in destroy. A simple way to code this is not to store anything in the member fields of the applet but in a separate class; then one has to do is to null that one reference from the applet to that class in the destroy method and everything will be relased when necessary. This way it is not easy to forget to release things.
Hey, here is a simple, imaginary, way in which the browser could cause this problem:
The browser, of course needs a reference to the applet, call it m_Applet here. Presume the following helper function:
Applet instantiateAndInit(Class appletClass) {
Applet applet=appletClass.newInstance();
applet.init();
return applet;
When the browser sees the applet tag it instantiates and inits the new applet as follows:
m_Applet=instantiateAndInit(appletClass);
As you can readily see, the second time the instantiation occurs, the m_Applet holds the reference to the old applet until after the new instance is created and initlized. This would not cause a memory leak but would require that twice the memory needed by the applet would be required to prevent OutOfMemory.I guess it is not fair to call this sort of thing a bug but it is questionable design.In real life this is propably not this blatant, but could happen You could try, if you like, by allocating less than 32 Megs in your init. If you then do not run out of memory it is an indication that there are at most two instances of your applet around and thus it could well be someting like I've speculated here.
br Kusti

MRBR - Invoice not automatically released

Similar Messages

Maybe you are looking for