Finance Workflow FIPP

[Former Member]

Good day gurus,

I'm working on a new workflow that will start with the event CREATED of the object FIPP. This workflow is supposed to work only for a specific type of document, so I was thinking of creating a copy of FIPP and use delegation to add a new method that check for the document type and terminate the workflow if itu2019s not the type that I want to process.

Can any tell me if thereu2019s a different approach for this? Iu2019m new with workflows and I need all the help I can get.

Also, Iu2019m supposed to send out a workflow that lets the user see Parked Document Release: Overview in order to Release or Reject the document. Any idea of how to do this? I tried creating a new Task with the method RELEASE of FIPP but itu2019s giving me an error of u2018No Input Transferredu2019.

Any help will be greatly appreciated guys, take care!

[former_member185167 · Accepted solution]

Hello,

The usual approach is to create an appropriate attribute for the BOR object and test it in the start condition of the workflow, instead of starting a workflow and then terminating it.

regards

Rick Bakker

hanabi technology

[Former Member · Accepted solution]

Hi,

Add document type as a attributes to FIPP and check that document type in the start condition of the workflow. You can use the release method in the FIPP to release the document if it is giving the error then it will be a issue with the binding. Make sure you are passing all the mandatory import parameters to that method.

Regards,

Devananda A J

[Former Member]

I still have issues, since when I moved it to Quality Servers for further testing, it went back to have the field left blank and the RELEASE workflow is not working... if anyone has any idea how to fix this, please feel free to write me back.

[former_member185167]

Hello,

If it works in one system and not the other then it could be that a transport hasn't been done, or done in the wrong order, or the config is different or authorizations are different... Look for differences.

You may get more responses if you open a new thread.

regards

Rick Bakker

hanabi technology

[Former Member]

Just for anyone's knowledge ,

In order to have this field set up correctly, you need to do some configuration in SPRO (transactions OBWA and OBWJ) in order to create a workflow variant that has the attribute "Release Required" chequed and apply that workflow variant to your company code. Once this is done, then it will have the RELEASE option enabled and the workflow will be able to RELEASE the documents once they are parked.

Hope this helps anyone in the future, take care!

[Former Member]

Hi guys,

I just founded out there's a field when you review the header of a parked document that's called Release necessary (VBKPF-XWFFR). This has to be checked in order for the method FIPP.RELEASE shows the RELEASE/REJECT buttons. What I'm trying to figure out is how do get this field checked as a default for future documents.

Anyone has any idea how?

[Former Member]

Hello,

Thanks for your response, but I already checked these two points:

Iu2019m passing the object ZFIPP through the task binding.

I used TCODE FBV0 to try and post the same document in question and was able to post it using the transaction without any problems, so I think the issue remains in the workflow. I read on another post that the correct order is suppose to be Parked u2013 Complete u2013 Post, but I canu2019t seem to find how to the Complete part if this is required. Also, I have read as well about level of approvals needed before a post can be done to a parked document, but also donu2019t know how to implement this in my workflow.

Has anyone has done this in the past? Any help will be greatly appreciated guys.

Take care,

[Former Member]

I still can't find an answer for this :(. Does anyone here knows why my work item does not let me see the options REJECT/RELEASE when the method FIPP.RELEASE is executed? Also it gives me the message 'Document not relevant for release'.

Any help will be GREATLY appreciated!

[Former Member]

Hi Alexander,

It can be due to 2 reasons:

1. You have not done the binding correctly for your task. You need to pass the whole BO FIPP for this in the WF -> Task binding.

2. Also there can be some issue relevant to FI customization for the this document type. Try doing it manually using the relevant transaction.

Regards

Gautam

Edited by: gautam maini on Feb 15, 2011 12:55 PM

[Former Member]

Good morning everyone,

Thanks so much your answers! I checked my task that calls the method RELEASE of FIPP but it only has one parameter and itu2019s not set as Mandatory. Anyhow I tried passing that parameter which is u2018Execute_Together_Notu2019 and the error stopped happening! Apparently even if itu2019s not set as Mandatory you still need to pass this value.

Now after I click the work item and go to REJECT/RELEASE the document, these options are not appear and the message u2018document not relevant for releaseu2019 appears. Iu2019m researching why this happening and will post if I found why.

I will try later the option of adding Document Type as one of my ZFIPP attributes and do a conditional check in the start event of the workflow for an specific document number. I will let you guys know how that went.

Thanks so much!