Ansicht
Dokumentation
HR_PBS_00_WB_RP2 - Define Substatus Change Based on Substatus Change
Addresses (Business Address Services) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
In this Customizing activity, you control how the substatus is set in subprocess scenarios (SPS).
If a subprocess scenario is set to a specific substatus, other subprocess scenarios in the background can also be set to a new substatus without the processor having to explicitly change these subprocess scenarios.
Important information about the function to change dependent subprocess scenarios when revoking a preceding subprocess scenario that has already been completed: If a subprocess scenario that has already been set to status Completed (SCMP) is changed again at a later stage, the subprocess scenarios dependent on this are set to substatus initial. This function is not created by maintaining the view in this activity but by combining the entries in view (VV_T7PBSWB5A) in activity Process Workbench Engine -> Enumerate Business Rules for Process Scenario -> Specify Relationships Between Subprocess Scenarios. The substatus of all secondary subprocess scenarios entered for a primary subprocess scenario with relationship 4 "Prerequisite" is set to initial if this subprocess scenario is also entered in the grouping of the subprocess scenario. This is done in view VV_T7PBSWB3A_PW using activity Process Workbench Engine -> Define Groupings -> Grouping of Subprocess Scenarios-> Assign your Sub Process Scenarios to Sub Proc. Scenario Group (Exit-Class). A subprocess scenario that is not displayed such as subprocess scenarios VAP3 (Create Originals) and VAP4 (Release) within grouping VA0P "Assessmt Pension Recip. for Approver" must also be included here so that the initialization of the substatus values for the dependent subprocess scenarios can be carried out in full.
Example 1:
Subprocess scenario VA01 with status New(SNEW) is set to In Process (SINP) when a processor saves it.
| Grouping of subprocess scenarios: | VAS0 (Assess. Pension Recip. for Administrator) |
| Subprocess scenario: | VA01 ( Pension Master Data ) |
| Status: | SNEW (New) |
| Subprocess scenario: | VA01 (Pension Master Data) |
| Valid from: | 1/1/2002 |
| Valid to: | 12/31/9999 |
| Status: | SINP (in process) |
With this setting, subprocess scenario VA01, which is saved with status Newis set to status In Process and saved with the new value.
Example 2:
A processor saves subprocess scenario VAP1 with status Complete previous SPS and for checking(SSET). Subprocess scenario VA03 is then set to status Completed(SCMP).
| Grouping of subprocess scenarios: | VAS0 (Assess. Pension Recip. for Administrator) |
| Subprocess scenario: | VAP1 (Prepare Check) |
| Status: | SSET (Complete Prev. CA and Submit for Check ) |
| Subprocess scenario: | VA03 (employment periods) |
| Valid from: | 1/1/2002 |
| Valid to: | 12/31/9999 |
| Status: | SCMP (Completed) |
This setting allows the processor to set a status field to Complete previous SPS and for checking, which sets the status fields of the other sub process scenarios to Completed before the process scenario is passed on to the reviewer. Subprocess scenario VA03 (Employment Periods) is given as an example here.
ROGBILLS - Synchronize billing plans ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 4582 Date: 20240523 Time: 193733 sap01-206 ( 82 ms )
