|
Why do we really need an abstract status? In SAP, all the statuses are 4 Character statuses and these are language dependent. Moreover, this 4 character status can be customized also. The system statuses are delivered by SAP and the user statuses are customized at each customer location.
So, a status that represents 'Work has started' for an assignment could be customized differently at each customer location. I can call it STRT and you can call it BEGN.
If in MRS we were to code some logic that depends on statuses, then it would be big mess if we coded based on the 4 character statuses STRT or BEGN (because they would be different for different customers). So inside MRS we use "Abstract status" which can be mapped to the concrete statuses.
Thus the MRS code always depends upon the abstract status and on the UI, we always continue to show the 4 character concrete statuses (because this is what is shown in all other SAP applications and users are comfortable with this)
In this customizing step, there are mainly 2 settings to be maintained.
1. Define Abstract Status
Define abstract statuses for e.g. Work_Started.
2. Assign Status
Map this status to a concrete 4 character status like STRT or BEGN.
Important points to note:
You can assign exactly one abstract status to a concrete status. However, an abstract status can be mapped to multiple concrete statuses.
|
