SAP OSS Note 2020320 version 0002 contains details of a know issue related to Superior order can be closed despite unsettled suborder
. 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 2020320 Details:
When does this problem occur
You can close a superior maintenance order even though a suborder still
hast costs that should be settled to the superior order (the s
uborder has a settlement rule for the superior order).
If you attempt this without order hierarchy (order settles order, which
we do not recommend), the system checks whether there are stil
l costs for the order to be settled during the business completion.
Cause of the problem and Pre-requisites
The source code that is responsible for the symptom described processes
PP collective orders that are principally treated differently.
In the case of plant maintenance, however, a different logic is
After you implement the corrections, maintenance orders of an order
Description of problem
hierarchy are treated as in the case of order settling order.
PM order, order settlement, IW36, KO88
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 2020320 has been released as well as see if the note is valid for your current SAP system landscape. Check if SAP OSS note 2020320 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 2020320 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 2020320 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)