The reason behind this was
the descision to keep the interface simple: Highlighting should be used
for records (or days on the calendar) for which action might be required
by the user. No matter if a record is approved or still to be approved,
the next step in the workflow is not for the user to perform but for
the approver.
If a record has been rejected, action is required by the user and
therefore the record is highlighted. Currently, there are no plans to
change this.
This could be changed on a project-basis, of course. Such a change
would require action in Java as well as in ABAP, since we do not
transfer the status to the frontend except for the detail screen, which
is for one record only. What would have to be done?
1) Add a new semantic state "approved" to the DDic element used for
semantic states.
2) Set this semantic sate within the RFC-layer (using the method
"build_timesheet", IIRC).
3) Possibly do the same for the calendar as well.
4) Adopt the Java-side to take this new semantic state into account.
This would of course be a modification, so please understand that I
just wrote down a rough outline of the changes that would have to
be introduced. I didn't actually do an analysis or design for such
a modification but simply noted all the steps that I am aware of that
would have to be performed.
Please refer the help.sap.com for further information on this
or SPRO path.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.