Posting date change during workflow process - BUS2081 -urgent]
viveka.schwartz@implema.se
viveka.schwartz at implema.se
Sat Jan 10 04:55:42 EST 2004
Hello,
opposite to what Carsten wrote we did have success by implementing note
87700. Maybe we are on a different patch level than Carsten which might
explain the difference in the result. We are on 4.6C, abap/basis support
pack 45 and HR support pack 79. Another explanation of the difference
might be that we are using different number range definitions. In my
installation we are using year-independent number ranges.
Before the note implementation both FIPP and BUS2081 workflow logs were
Not transferred to the new document in the new fiscal year.
Instead the FI application program as well as the MM application program
raised the events CREATED for the new document in the new fiscal year as
well as DELETED for the old document in the previous fiscal year. This had
the consequense that a new workflow instance was created for the document
in the new fiscal year, and a logically deletion of the workflow
instance of the old document in the previous fiscal year - if the workflow
implementation contained a wait step for event DELETED.
After installing note 87700, for both FIPP and BUS2081- these events are
no longer raised. The worflow log of the old document in the previous year
were assigned to the new document in the new fiscal year as well. The
result is that the workflow log can now be displayed via both the old
document in the previous fiscal year (via FB03) and the new document in
the new fiscal year.
However, the systems handling of the assigned images seem to be different.
The image assignment link were rather transferred/moved from the old
document in the previous fiscal year to the new document in the new fiscal
year: This means the image assignment link of the old document is no
longer available in the assignment link table (TOA01 etc.) - there is only
an entry for the new document in the new fiscal year. From a book keeping
point of view I guess this is not allowed that the linkage between the
original business document and the scanned document has been erased and
replaced by a linkage to another document number.
Best regards
Viveka
"Jaeger, Carsten (Calgary)" <Carsten_Jaeger at nexeninc.com>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
2004-01-07 15:13 MST
Please respond to SAP Workflow Users' Group
To: SAP-WUG at MITVMA.MIT.EDU
cc:
bcc:
Subject: Re: [Fwd: Re: Posting date change during workflow process - BUS2081
-urgent]
Hi, we ran into this problem last year (46c) and found that Note 87700
did not fix it completely. Look at 549381 and 598018 (Support pkgs 38
and 45 respectively). We also found that we had to give a bit more
authority to our Invoice Approvers to be able to delete an attached
image (done in background) via auth obj S_WFAR_OBJ. We use IXOS to
manage our scanned invoices and since table TOA01 is your Archivelink
table which contains the document key (eg 520000..2003), it too needs to
be updated with the new document number that was created due to the new
year.
cj
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
viveka.schwartz at implema.se
Sent: January 7, 2004 9:38 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: [Fwd: Re: Posting date change during workflow process -
BUS2081 -urgent]
Hello Susan,
there is a note related to parked documents, N87700 and the tranferring
of workflow logs for documents transferred into a new fiscal year via
the change of posting date. This note is developed by the FI-team and is
related to "FIPP-documents". We are implementing it right now (in 46C)
to see if it also works for the workflow log transfer of parked BUS2081
documents.. I'll write a new reply to this list after we've checked if
this note works for parked MM invoices as well.
Best regards
Viveka
"Susan R. Keohan" <skeohan at mit.edu>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
2004-01-07 16:03
Please respond to SAP Workflow Users' Group
To: SAP-WUG at MITVMA.MIT.EDU
cc:
Subject: [Fwd: Re: Posting date change during workflow
process - BUS2081 -urgent]
Hi Swami,
You wouldn't have that OSS Note number that you mentioned, would you ?
Thanks in advance, Sue
Swami Bala wrote:
> Hello Jocelyn / Fred,
>
> We were able to work around the solution. We are using
> BAPI_INCOMINGINVOICE_PARK to park the document but using custom event
> to trigger our custom workflow. When the fiscal year changes (due to
posting
> date change ) system deletes the old invoice number but creates a new
> document number invoking a new workflow.We also came across a OSS note
> which explains about tranferring workflow log into the new workflow
> though we donot have the patch level available.
> But for time being we ended up identifying those documents, delete it
and
> recreate with new posting date.
> Thanks a bunch for the suggestions and advise,
> Swami Bala
>
>
>
>
>
>>> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
>> Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>> To: SAP-WUG at MITVMA.MIT.EDU
>> Subject: Re: Posting date change during workflow process - BUS2081
>> -urgent
>> Date: Tue, 6 Jan 2004 03:50:04 +0100
>> MIME-Version: 1.0
>> Received: from mc11-f17.hotmail.com ([65.54.167.24]) by
>> mc11-s11.hotmail.com with Microsoft SMwTPSVC(5.0.2195.6713); Mon, 5
>> Jan 2004 18:51:03 -0800
>> Received: from cherry.ease.lsoft.com ([209.119.0.109]) by
>> mc11-f17.hotmail.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 5
>> Jan 2004 18:51:02 -0800
>> Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by
>> cherry.ease.lsoft.com
>> (LSMTP for Digital Unix v1.1b) with SMTP id
>> <7.00C95311 at cherry.ease.lsoft.com> Mon, 5 Jan 2004 21:51:00 -0500
>> Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP
release
>> 1.8e) with spool id 4836 for SAP-WUG at MITVMA.MIT.EDU; Mon, 5
Jan
>> 2004 21:50:44 -0500
>> Received: from MITVMA (NJE origin SMTP at MITVMA) by MITVMA.MIT.EDU
(LMail
>> V1.2d/1.8d) with BSMTP id 4470; Mon, 5 Jan 2004 21:50:09 -0500
>> Received: from smtpde02.sap-ag.de [155.56.68.170] by mitvma.mit.edu
>> (IBM VM
>> SMTP Level 320) via TCP with ESMTP ; Mon, 05 Jan 2004
>> 21:50:08 EST
>> Received: from sap-ag.de (smtpde02) by smtpde02.sap-ag.de (out) with
>> ESMTP
>> id DAA01570 for <SAP-WUG at MITVMA.MIT.EDU> Tue, 6 Jan 2004
>> 03:50:08
>> +0100 (MEZ)
>> X-Message-Info: SuyIeF3cBu+ScdBt/LmKU3tjGRpUuir6FZjIHAUMPS8=
>> X-Comment: mitvma.mit.edu: Mail was sent by smtpde02.sap-ag.de
>> X-Mailer: Internet Mail Service (5.5.2656.59)
>> X-SAP: out
>> Approved-By: "Dart, Jocelyn" <jocelyn.dart at SAP.COM>
>> Message-ID:
>> <A54EC476B74FD31186340008C791CBD00D18D7DB at ausydx30.syd.sap.corp>
>> Precedence: list
>> Return-Path: owner-sap-wug at MITVMA.MIT.EDU
>> X-OriginalArrivalTime: 06 Jan 2004 02:51:02.0906 (UTC)
>> FILETIME=[EC2DEDA0:01C3D3FF]
>>
>> Swami,
>> Suggest you test it and see. If you are using the standard workflow I
>> would expect it to cope with this common situation.
>> Jocelyn
>>
>> -----Original Message-----
>>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
>> Kouw, FA - SPLXE
>> Sent: Monday,5 January 2004 7:57 PM
>> To: SAP-WUG at MITVMA.MIT.EDU
>> Subject: Re: Posting date change during workflow process - BUS2081
>> -urgent
>>
>>
>> Hi Swami,
>>
>> First of all: happy new year to all SAP-WUG maillist contributors!
>>
>> I think you need to answer the following question:
>>
>> * (How) does the newly created document(s) impact your workflow,
i.e.:
>> o does is start a new workflow (f.i. by an event)?
>> o are there instances that are waiting for a specific event
>> related to the 'old' document (that are not
>> triggered because a new document is created and no event
>> for the old document is raised)?
>>
>> As you will probably know the logistic invoice object (BUS2081) is
>> something else than an accounting document (that is created when
>> posting the invoice). Maybe the document created you
>> refer to does not impact your
>> workflow(s) at all?
>>
>> Hope this helps a bit.
>>
>> Regards,
>>
>> Fred Kouw
>>
>> Swami Bala wrote:
>>
>> > Hello All,
>> >
>> > We have several documents that involves posting date change during
>> approval
>> > process of Logistics Invoice ( BUS2081 ).But today we noticed,
because
>> of
>> > fiscal year change, that SAP actually creates another document if
>> > the posting date differs between the actual posting date when
>> > parked and
>> when it
>> > gets approved. ( For example documents parked in the last month
>> > being
>> posted
>> > this month.)
>> > Since the SAP creates another document number what would be the
effect
>> on
>> > the workflow ?
>> > Any idea ?. Since we are trying to tackle the problem with posting
date
>> > change we havenot started looking at the impact of the workflow. We
>> > are in 46c.
>> >
>> > Swami Bala
>> >
>> > _________________________________________________________________
>> > Tired of slow downloads? Compare online deals from your local
>> high-speed
>> > providers now. https://broadband.msn.com
>> >
>> >
>>
________________________________________________________________________
_________________
>>
>> > This inbound message from KPN has been checked for all known
>> > viruses
by
>> KPN IV-Scan, powered by MessageLabs.
>> > For further information visit: http://www.veiliginternet.nl
>> >
>>
________________________________________________________________________
_____________________
>>
>>
>>
>> *********************************************************************
>> *
>> This e-mail and any attachment may contain confidential and
privileged
>> material intended for the addressee only. If you are not the
>> addressee, you
>> are notified that no part of the e-mail or any attachment may be
>> disclosed,
>> copied or distributed, and that any other action related to this
>> e-mail or
>> attachment is strictly prohibited, and may be unlawful. If you have
>> received
>> this e-mail by error, please notify the sender immediately by return
>> e-mail,
>> and delete this message. Koninklijke Luchtvaart Maatschappij NV
(KLM),
>> its
>> subsidiaries and/or its employees shall not be liable for the
>> incorrect or
>> incomplete transmission of this e-mail or any attachments, nor
>> responsible
>> for any delay in receipt.
>>
**********************************************************************
>>
>>
________________________________________________________________________
_____________________
>>
>> This outbound message from KPN has been checked for all known viruses
by
>> KPN IV-Scan, powered by MessageLabs.
>> For further information visit: http://www.veiliginternet.nl
>>
________________________________________________________________________
_____________________
>>
>
>
> _________________________________________________________________
> Expand your wine savvy and get some great new recipes at MSN Wine.
> http://wine.msn.com
>
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu
More information about the SAP-WUG
mailing list