Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-BP (Application Component) Business Partners⤷
FB0C (Package) Financial Accounting customers
IMG Activity
| ID | SIMG_CFMENUORFBOBWE | Assign Release Approval Procedure for Parking Documents |
| Transaction Code | S_ALR_87004400 | IMG Activity: SIMG_CFMENUORFBOBWE |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORFBOBWE | Assign Release Approval Procedure for Parking Documents |
| Customizing Activity | SIMG_CFMENUORFBOBWE | Assign Release Approval Procedure for Parking Documents |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORFBOBWE |
For each workflow variant and release approval path, you determine as from which amount which release approval procedure is triggered and carried out. These procedures are referred to as "subworkflows" in workflow terms. They control how the release is to proceed in detail, for example, how many release levels are to be run.
Standard settings
The standard system comes with subworkflows predefined as workflow templates for use as a reference for your own subworkflows. The first of these (WS10000052) contains a single-level release, the second, (WS10000053), a two-level release and the third, (WS10000054), a three-level release. The single-level requires just one person to release the document. The two-level version supports dual control, whilst the three-level procedure allows for triple control of payment releases. Each subworkflow is triggered the first time parked documents are entered.
Activities
Assign the release approval procedure (subworkflow) that you require dependent on the workflow variant, release approval path, and amount.
You can also enter your own subworkflows here. However, they must receive the same data from the workflow (WS10000051) as the predefined workflow example (WS10000052, and so on).
You can also specify the release levels to be executed. You set this specification in the parked document and it should correspond with the number of release levels of the subworkflow. However, this specification is not evaluated by the predefined workflow examples and in this case, has only an explanatory nature.
Since the number of release levels is stored in the parked document, (and this number is accessible within the workflow as Attribute for object type FIPP), this number could be used in customer subworkflows.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUORFBOBWE | 0 | HLA0008962 O HLA0001264 O HLA0008976 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_VBWF06 | V - View | OBWE | 1 | Assign Release Approval Procedure |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
