Maintaining Processor Assignment
At runtime, the relevant task is addressed to the processor(s) (processing staff member(s)) to whom the release code has been assigned via a role resolution. You must make the following settings in Customizing for this:
_ In Task-Specific Customizing for SAP Business Workflow you must list all organization management objects that are generally permitted to work with workflow-relevant release codes (e.g. jobs or positions).
Prior to this, the organizational plan (defining the organizational structure) must be finalized.
By assigning a release code to a processor in Customizing for Purchasing, you specify who in concrete terms may process a document (i.e. effect releases) using this code. Take care that this assignment is compatible with the processor assignment in Task-Specific Customizing. If you enter a user, for example, the latter must also be the holder of a position in Task-Specific Customizing. If you enter a position, precisely this position must also be defined in Task-Specific Customizing and have users assigned to it.
It is also necessary for the release codes to be marked as “relevant to Workflow”.
Determining the Processor
In determining the processor (the person who is to process the document), the system searches the Purchasing Customizing facility for the processor ID for a release code. This is achieved via role resolution.
For this purpose, the following roles are defined for the relevant task:
Request for Quotation (RFQ)
Role 20000030 (Person responsible for releasing RFQ)
Purchase Order (PO)
Role 20000027 (Person responsible for releasing PO)
Scheduling Agreement
Role 20000028 (Person responsible for releasing scheduling agreement)
Contract
Role 20000029 (Person responsible for releasing contract)
Input for the role comprises the release code and the relevant document. These were passed on to the role container from the task container.
Tasks: Release (MM-PUR-GF)
<- _WI_OBJECT_ID ReleaseCode <- ReleaseCode Then, using this data, the Customizing settings for Purchasing containing the linkage between release code and processor ID are read. After this, the system checks whether these settings agree with those of Task-Specific Customizing. If they do not, the workflow terminates and the system administrator responsible for workflow is informed by mail accordingly. Terminating Events The standard task Release is terminated by the events Release effected, or
significantly changed.
Tasks: Release Effected (MM-PUR-GF)
Via these tasks, the creator of the document is informed that release has been effected (approval has been signified). He or she receives this information via the text of the work item representing the task. The creator processes the work item and thus concludes it. There is no further functionality besides this conclusion of the work item.
Request for Quotation (RFQ)
Task: TS20000177
Identifier: mm_qr_ok
Description: Release of RFQ effected
Referenced Object Method, Attributes
Object type: BUS2010 (RFQ)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Purchase Order (PO)
Task: TS20000168
Identifier: mm_po_ok
Description: Release of PO effected
Referenced Object Method, Attributes
Object type: BUS2012 (PO)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Scheduling Agreement
Task: TS20000171
Identifier: mm_pa_ok
Description: Release of scheduling agreement effected
Referenced Object Method, Attributes
Object type: BUS2013 (Scheduling agreement)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Contract
Task: TS20000174
Identifier: mm_pc_ok
Tasks: Release Effected (MM-PUR-GF)
Description: Release of contract effected
Referenced Object Method, Attributes
Object type: BUS2014 (Contract)
Method: InfoReleaseEffected (Info: release effected)
Attributes: None
Maintaining Processor Assignment
These tasks should be classified as general tasks. General tasks do not have to be assigned to a processor because anyone may execute them. The processor (= creator of the document) is determined from the context of the workflow.
Workflow: Release of Purchasing Documents (MM-PURGF)
If the system recognizes that the release code with which a user must next signify approval in accordance with the release strategy is workflow-relevant, a workflow is started. An individual workflow is started for each workflow-relevant release code. A central task of workflow control is to determine the processor (several may be involved) to whom this release code has been assigned.
Request for Quotation (RFQ)
Workflow: 20000080
Identifier: wf_qr_rel
Description: Workflow for release of RFQ
Purchase Order (PO)
Workflow: 20000075
Identifier: wf_po_rel
Description: Workflow for release of purchase order
Scheduling Agreement
Workflow: 20000078
Identifier: wf_pa_rel
Description: Workflow for release of scheduling agreement
Contract
Workflow: 20000079
Identifier: wf_pc_rel
Description: Workflow for release of contract
Triggering Event for Workflow
The event ReleaseStepCreated has been entered as the trigger for the workflow for the
relevant object type.
This “linkage” between the event and the workflow to be triggered is deactivated in
the standard system and must first be activated in Customizing for SAP Business
Workflow if the workflow is actually to be started.
Workflow Container and Data Flow The most important information that must be available within the course of the workflow comprises the object reference to the document to be processed (_EVT_Object) and the release code (ReleaseCode), as well as the name of the person who the created the document Workflow: Release of Purchasing Documents (MM-PUR-GF)
(_EVT_Creator). The information is available as an event parameter in the container of the triggering event and must be passed on from there to the workflow container via data flow.
Therefore, the following data flow definition between the triggering event and the workflow container is defined in the standard system:
Workflow container Event container
Initiator <- _Evt_Creator <- _Evt_Object Release code <- ReleaseCode In the standard system, the element Initiator exists in the workflow container. The elements and ReleaseCode have been created in addition to the standard elements that exist.
0 comments
Post a Comment