Question Re: WORKFLOW_LOCAL_CCC Configuration in Technology Q&A

WORKFLOW_LOCAL_CCC Configuration

Former Member — Mon, 19 Oct 2009 22:06:19 GMT

Hi All,

We have a somewhat strange requirement here. There are existing workflow processes for AP that use the WF-BATCH user id to perform background steps. However, in our new journal entry approval workflow (document parking, FIPP), after the approver releases the work item (does an amount release on the FI document), the document is posted in the background. The requirement here is that the approver's name or the creator's name should be used to post the document instead of WF-BATCH.

We have found that if the RFC destination is configured with the "current user" checkbox turned on, the document will be posted with the approver's name instead of WF-BATCH. However, the RFC destination WORKFLOW_LOCAL_CCC (CCC=client) appears to be common across the workflow system. Is there any way to configure the system to use one RFC destination with "current user" turned OFF for the rest of the workflows, but use a different RFC destination with the "current user" turned ON for our journal entry workflow? Any input would be greatly appreciated.

Re: WORKFLOW_LOCAL_CCC Configuration

Former Member — Tue, 20 Oct 2009 14:34:56 GMT

Hi,

I wouldn't mess with RFC destinations if I were you. I would simply regards this as a new functional issue and search for the best approach to solve this.

I've encountered the same sort of requirement many times, but had to resort to various solutions.

The simplest would be if there is an option for providing the changed by user in the functionality to park the document.

Another way is to check if the document can be altered after it was parked and provide the correct user.

If the previous step was a dialog step, you can change the next step to foreground and enable advance with dialog for these steps, this way the process will get carried out in the background, but it will use the previous user.

And lastly, but which is not recommended is to create a custom report to park the document and in your method you're going to schedule that report in background with the correct user as the one who executes is.

Maybe there are more options, but since I haven't worked with FIPP before I can only give global advice, not specific.

Kind regards, Rob Dielemans

Re: WORKFLOW_LOCAL_CCC Configuration

Former Member — Tue, 20 Oct 2009 15:47:13 GMT

Is there anyway to configure different RFC destinations for different workflow streams, by object type or some other criteria? I don't want to affect the whole client.

Re: WORKFLOW_LOCAL_CCC Configuration

chaiphon — Tue, 20 Oct 2009 19:10:47 GMT

It would be hard to do that and configure your workflow to use specific RFC destination.

I would suggest you to write abap code in your task when workflow is creating a document.

If you use bapi to create the documents, some bapi allow you to put username as an importing parameter or field in importing structure.

If you are using BDC or other methods, try setting sy-uname = workflow initiator or any user name and run bdc. then change the user back to WF-BATCH once the transaction is done. In some transaction, it works. In some transaction it won't. So Good luck.

Regards,

Chaiphon

Re: WORKFLOW_LOCAL_CCC Configuration

narin_nandivada3 — Wed, 21 Oct 2009 10:10:37 GMT

Hi Murali,

I think For a Particular task you can set, try using SWDC

Hope this may work.

Regards

Narin

Re: WORKFLOW_LOCAL_CCC Configuration

Former Member — Wed, 18 Nov 2009 00:04:38 GMT

We had to implement a custom workflow that will advance the approver as the posting user.