Ansicht
Dokumentation

_ISPSFM_WOROLAN - Role Definition for Requests

_ISPSFM_WOROLAN - Role Definition for Requests

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

The role definition for requests is used in the workflow template WS80500027 for the standard task Decision: Document Release (TS80500065).

Workflow template

To activate the workflow template you must make the following entry in the event type linkage table:

Object type FMPSO
Event CREATED
Receiver type WS80500027
Receiver call function module
Receiver function module SWW_WI_CREATE_VIA_EVENT
Check function
Destination
Linkage activated X

To define these entries, choose the following in the SAP menu: Tools -> ABAP Workbench -> Development -> Workflow -> Administration -> Event Manager -> Type Linkages (transaction SWETY)

You must also assign the following standard tasks in the organizational structure:

  • 80500066 change request
  • 80500065 release request

To define these settings:

  1. Choose the following in the SAP menu Tools -> ABAP Workbench -> Development -> Definition Tools -> Tasks/Task Groups -> Display (transaction PFTC_DIS) and enter a standard task.
  2. Choose Additional Data -> Processor Assignment -> Maintain and assign the standard task to the processor types relevant for you.

Role definition

All G/L account lines of all documents that are grouped together in the request are used for role definition.
Example: The request consists of 2 documents each having 3 G/L account lines.
4 different processor groups are determined
4 parallel processing branches are generated.
The request must also receive a 4-fold approval before it can be approved at its current level.

Number of workflow approval levels

The control parameters of workflow template MaxWFLevel determine the number of workflow approval levels.
The levels determine the sequential order of the approval. The next higher level is reached if an approval has been given for the previous level.
If a rejection occurs at a level, the request must be changed accordingly. The current level is reset to 1. All approval levels must be gone through again.
You define the number of approval levels necessary for a certain request (document type) in step "Create workflow variant for requests".

Dependency of FI parked workflow

A request is comprised of parked FI documents, as long as the request has not yet been posted.
If parked FI documents belong to a request which must be approved in the request workflow, these FI documents cannot also be relevant for the FI workflow at the same time. You must bear this dependency in mind if you want to implement both workflows in parallel.

Take note:
As of release 4.62, it is possible to flag requests as relevant for workflow independently from the Customizing settings made here. SAP provides process 00107030 and reference function module SAMPLE_PROCESS_00107030 in order that you can change the workflow indicator.
The enhancement of the workflow function for requests is based on the business transaction event technique. For more information on this topic, see Business Transaction Events.






Addresses (Business Address Services)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4198 Date: 20240523 Time: 184454     sap01-206 ( 59 ms )