SAP OSS Notes
200021 SAP OSS Note - Performance - long runtime of transaction
SAP OSS Note 200021 version 0002 contains details of a know issue related to Performance - long runtime of transaction . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.
...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.
Note 200021 Details:
When does this problem occur
The runtime of Transaction MR11 is very long and/or terminates after a
long time.
Cause of the problem and Pre-requisites
In the 'Criteria' box, you entered values which are too large in fields
'Qty difference smaller than' and 'Purchase orders older than'
for the selection and in the 'Selection criteria' box you chose areas
which are too large in fields 'Vendor', 'Purchasing group', 'Pu
rchasing document' and 'Plant'.
Solution instructions
When you choose the selection criteria enter smaller areas and run
Transaction MR11 in several steps.
When selecting the criteria make sure that you do not choose 100% in
field 'Qty difference smaller than'. Otherwise, all invoices whic
h are still open or goods receipts are selected.
Example:
You select delivery surplus and 100% difference.
Now also all goods receipt are selected which do not yet have
an invoice receipt since here the quantity of goods received is
larger (100%) than the invoice quantity (0%).
For field 'Purchase orders older than' you have to ensure not to choose
a number of months which is too high. Otherwise the system has
to read too many purchase orders since the purchase orders already
completely settled are read, too. Here you should archive the alre
ady settled purchase orders.
Description of problem
MR11, performance, selection, buffer
Solution instructions
Please import the corrections attached to this OSS note into your SAP system using SNOTE.
You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.
You can also check if a new version of note 200021 has been released as well as see if the note is valid for your current SAP system landscape.
Check if SAP OSS note 200021 has already been downloaded and is valid
To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
From here you can just enter the note number 200021 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.
If note 200021 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.
Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)