New document number make the FIPP object flip out

[C_J]

Hi there,

We have a WF solution that approves FI documents. Our urgent problem now is that documents that was parked with a 2007 year date and where the user tries to post with a 2008 year date the document receives a new document number. Then the document loses its reciver key.

Does any one know about any work around of this problem?

Best regards

Carl-Johan

[Former Member]

Hi,

What do you mean by "flip out"? And "the document loses its reciver key"?

This is a known 'issue'. After you have closed the previous fiscal year, you cannot anymore post documents to it without creating a "new document" and deleting the old one. This will of course cause some not-so-nice issues within workflow (depending of course that how the workflows has been built at the first place).

Check SAP notes: There is a report which you can use to mass change the documents from the previous fiscal year to the current year. That might help you with your possible problem with manually handling of every parked invoice of previous year.

Regards,

Karri

[Former Member]

Hi,

Yes..this is a known problem, because at the year end when you run the report ( SAP Note based solution) to mass change the documents from old year to new year, all the workflows which are running based on old FIPP object key ( with old new year) will have problems when access the FIPP Object from Workflows. For example in some cases if you have a link which is pointing to FIPP object (with old key) and tries to open,it will say document doesn't exist.

We did face this problem in our workflow and solved it by doing below

1. In the same report which is trying to chnage FIPP object key to new fiscal year, we raise a custom event and our workflow will capture this event ( using a fork and wait for event step in the fork)

2. Once we receive this custom event in workflow, we find out the current Inprocess step of our workflow and play a bit with Container and modify the container of FIPP object to change the key with new year. This worked fine.

However another way can be to just stop the running workflow and start a fresh one, but not a good idea as you might be running it through another approval process when the original docuement might have passed through some of the approvals required !!

Regards

Krishna Mohan