BUS2081, FIPP & the Good 'ol Fiscal Year End issue...

Thu Jan 19 04:24:49 EST 2006

Hi Serge

Thanks for the work-around help. I am coming round to thinking that I will
need to implement some form of tidyup, though thankfully that will
predominantly be limited to the clearing out orphaned workflows for
invoices that have now been posted. (...hmmm, though I will probably still
need to correct the containers etc for audit trail purposes...)

Is everyone having to implement a work-around, though? As mentioned, all
the OSS details [that I've come across so far] clearly suggest that the
workflows should automatically respond to the invoice number change,
following implementation of the fixes they describe. I also note that the
IXOS images appear to have been successfully re-assigned to the new
invoice, so some black-magic has been going on...

Does anyone understand more fully how the key is supposed to automatically
correct itself?

Confused of Birmingham...

|---------+----------------------------->
|         |           "Breslavets       |
|         |           Sergey"           |
|         |           <sergey.breslavets|
|         |           @volvo.com>       |
|         |           Sent by:          |
|         |           sap-wug-bounces at mi|
|         |           t.edu             |
|         |                             |
|         |                             |
|         |           18/01/2006 18:50  |
|         |           Please respond to |
|         |           "SAP Workflow     |
|         |           Users' Group"     |
|         |                             |
|---------+----------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       "SAP Workflow Users' Group" <sap-wug at mit.edu>                                                                |
  |       cc:                                                                                                                    |
  |       Subject:  RE: BUS2081, FIPP & the Good 'ol Fiscal Year End issue...                                                    |
  >------------------------------------------------------------------------------------------------------------------------------|

Hi Andy,

welcome to the 'Year-end convertion issue' club! :)

the converted invoice will have the old invoice Id as part of the reference
key field (XBLNR). create a small function module to listen to the
invoice.created event and determine if the invoice is created as a result
of the year-end conversion (check XBLNR). If yes, you can do the following:
1. find appropriate workflow instance relevant for the old number and (if
it's still active) replace invoice object key in the runtime container with
the new one (pointing to the new document). Make sure you replace it in all
appropriate containers, workflow and task!
2. get image id from the workflow and link it to the new document
3. replace the workitem for the last task so that it picks up new container
values

that should do it.

g'luck.
Serge

-----Original Message-----
From: sap-wug-bounces at MIT.EDU [mailto:sap-wug-bounces at MIT.EDU]On Behalf
Of Andy.M.Catherall at csplc.com
Sent: Wednesday, January 18, 2006 12:28 PM
To: sap-wug at MIT.EDU
Subject: BUS2081, FIPP & the Good 'ol Fiscal Year End issue...

Hi all

A New Year, an old problem... though I'm frustrated that it appears to be
continuing.

Summary of the problem:
Those invoice documents created last year, but posted this year, have a new
key created based on the new year. The active workflow instances,
listening out for events based on the original key, ignore the posting of
the new document.

Of course, there have been innumerable OSS notes & discussions about this
problem going back as far as the year 2000. After reading these, and a
number of WUG Archive entries, I think I have an understanding of what I
should be expecting to happen. It's just that it is not, so I'd like to
determine where my expectation has gone astray. I'll describe what I think
I understand to be true. Could someone clarify if I've missed something.

1) An invoice is created with a key which includes the year in which it was
raised
2) If that invoice is posted in the new year, the original one is deleted
and a new one is created.
3) Once upon a time, events would be raised to represent the deletion and
creation events, and the workflows would react. However, subsequent fixes
have modified the response so that active workflows for the original
invoice should have their keys updated to use that of the new object. I
should expect to see no events to trigger this magical process.
4) Any IXOS image attachments are 'reassigned' in the appropriate link
table (eg TOA01) to the new Invoice document.
5) These 're-keying' exercises occur as part of the save/create process for
the invoice and is not based upon some other external process being
manually called. No BO events would be seen as a result.

I seem to be missing step 3. As expected, I have no events, but the
underlying workflows have not had their keys changed and they have not
reacted in any way.

I have obviously looked into documentation about this. There are a number
OSS notes out there, all of which appear to 'resolve' this issue. One is
from around 2000 (OSS 87700); One is from July 2003 (OSS 549381); One is
from Feb 2004 (598018); we appear to be up to date with all these. There is
also a rather brief note from September 2004 which sounds exactly like my
problem ("Symptom: The change to the fiscal year is ignored for current
workflow instances), but is only valid from basis release 610 up.

We are on 46c, basis support pack 47.

Any ideas?

Thanks
Andy

***********************************************************************************

This e-mail is confidential and may contain privileged information.  If you
are not the addressee or if you have received the e-mail in error,  it may
be unlawful for you to read, copy, distribute, disclose or otherwise use
the information which it contains.

Under these circumstances, please notify us immediately by returning this
mail to 'mailerror at csplc.com' and deleting this e-mail from your system.

Any views expressed by an individual within this e-mail do not necessarily
reflect the views of Cadbury Schweppes Plc or its subsidiaries.  Whilst we
have taken reasonable steps to ensure that this e-mail and attachments are
free from viruses,  recipients are advised to subject this mail to their
own virus checking, in keeping with good computing practice.

Visit our website at www.cadburyschweppes.com

***********************************************************************************

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug