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

FIPP.COMPLETED event

$
0
0

Hi,

 

We are trying to trigger a custom workflow for park documents. I have done all the necessary configurations like OBWA, OBWJ & OBWE.

Also I have activated the event linkage.

 

Issue #1:

  • When I park a document using a standard tcode, say FB50 workflow is not triggered. Then when I go to change and save the document as 'Save as complete', the workflow is triggered. This works absolutely fine.
  • THE ISSUE IS when I create a document and instead of clicking on 'Park', if I click on 'Save as complete', then the workflow is not triggered. In this case even if I go to change and again try to save it as complete, it won't trigger workflow, since I guess VBKPF-XPRFG is already updated with 'X' value initially.
  • I want to trigger the workflow with document complete status, irrespective of when the document is saved as complete.

   

Issue #2:

  • I am using a custom program for mass upload of parked documents. By default the system updates the custom tcode in VBKPF-TCODE field.
  • Again for this documents workflow should be triggered. In workflow I have used FIPP.RELEASE method, if the user clicks on 'Release' button then I have called FIPP.POST method in background. Now the method returns an error saying "Field BSEG-VALUT. does not exist in the screen SAPMF05A 0300". When I evaluated, I found it is because of custom tcode populated in field VBKPF-TCODE. If I update this field value as FB01 it posts successfully.
  • The same works absolutely fine when I triiger the workflow using standard tcode like FB50.

   

Issue #3:

  • When I post the document through workflow using FIPP.POST method, the system update BKPF-USNAM value as WF-BATCH instead of approver. Can I pass the approver name over there.

 

Regards,

Ashish.


Viewing all articles
Browse latest Browse all 3160

Trending Articles



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