Quantcast
Channel: SCN : Unanswered Discussions - SAP Business Process Management
Viewing all articles
Browse latest Browse all 3160

Quality Notification to trigger Work item to Persons Responsible in Sequence.

$
0
0

Hi

We are Indian Public Sector Steel Plant, went live on SAP ECC 6.0 with all latest EHPs recently. Extended Quality Notification processing was configured  for taking various business approvals through a notification initiated (IQS1). The coordinator/initiator after creating the Notification, puts the user ID of next immediate approver in the 'Person Responsible" field and puts the notification "in process". This is generating the work item in the inbox of the recipient approver and he is able to access the Notification.  Until this, every thing is fine. The first approver puts his remarks and he selects next higher approver in the "Person Responsible" and saves the Notification. It is expected that the 2nd Approver also receives the Work item in his SAP inbox. But this is not happening. The workflow was getting terminated and red deletion flag is appearing in the SAP BWP workflow at the first approver level.

 

The Business requirement is, work item to be generated for all the approvers  in sequence and Notification should be accessible from SAP BWP instead of IQS2(inputting the Notification number). Also once the Notification was sent to next approver , it shouldn't be editable for the creator as long as it remains as the work item in next person's inbox. Creator/approver should be able to access only when it stays in his in-box.

 

Also the attachments to the notification made by the creator/approver  through the "Services for Objects' link should not be editable/removable by the other persons. Kindly let me know whether this scenario is achievable. Though I am not on Technical side, I would be happy to take, if a development (ABAP) is necessary.

BRGDS

KISHORE HARI


Viewing all articles
Browse latest Browse all 3160

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>