Early archiving of inbound invoices in SAP 4.6B

[Gregory Kowalik]

You can't use object BKPF since MR8M is working on BUS2081.
BKPF can only be used for pure FI documents,
 
My recomendation to you would be to try late archiving scenario (cancel LIV
invoice using MR8M) and then assign image to it.
I haven't tried it though, did not have a need to image canceled invoices (or
any documentation associated with it).
Sorry,
 
Greg
 
 
 
 
 
"MacPherson, Graeme (AU - Melbourne)" <gmacpherson at dc.com> on 04/03/2001
04:02:50 AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  Re: Early archiving of inbound invoices in SAP 4.6B
 
 
 
Hi Greg
 
I have a similar problem to the one which you have provided a solution to
below. I am working in 46B and I am  trying to link a scanned image to a
cancelled LIV invoice (transaction MR8M) using Early archiving. Since the
archiving config only allows instance independent object methods, the method
BUS2081 Cancel cant be used. Instead I am using a BKPF CREATE method and
passing the parameter MR8M as the transaction code. When the work item is
executed, the transaction is called and an invoice is successfully reversed
but the event IMAGE Assigned is not raised and therefore no link to the
posted document is created and the work item remains in the inbox.
 
I have configured a direct invoice reversal similar to that described above
(using transaction FB08 and BKPF CREATE) which works perfectly. The work
item dissappears and the image is linked to the reversal document.
 
Any ideas ?
 
Regards
 
Graeme MacPherson
Senior Consultant
Deloitte Consulting, Melbourne
Ph: +613 9208 7100
Mob: 0414 473 554
 
 
-----Original Message-----
From: Gregory Kowalik [mailto:gkowalik at ashland.com]
Sent: Saturday, 31 March 2001 2:15
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Early archiving of inbound invoices in SAP 4.6C
 
 
I use BUS2081 and MIRO and it works fine.
 
Do not use wizard (I had problems with it before).
In SOA0 change object type from BKPF to BUS2081, method CREATE still must be
used. Task for entry: TS30001128
In OACA delete parameters you previously had for object BKPF. BUS2081-CREATE
does not have any parameters.
Assign agents in OAWS.
And at the end create the link to the external system in OAC3 for BUS2081
and
your doc. type.
 
One cool think about BUS2081 and MIRO is that you will see the image link in
both MM and FI document. Users love it.
 
in the type linkage for IMAGE doc type SWETYPV I have 2 entries for object
IMAGE
event ASSIGNED:
1. Receiver type is TS30001128:
   Receiver FM : SWW_WI_CREATE_VIA_EVENT
   Global checked,
   Type linkage active checked
2. Receiver type workitem:
   Receiver FM : SWW_WI_COMP_EVENT_RECEIVE
   Check function : ARCHIV_WORKFLOW_ASSIGN
   Global unchecked
   Type linkage active checked
   Enable even queue checked
 
Let me know if it worked. I am really curious. And again - do not use the
wizard.
 
Greg
 
 
 
 
 
"Sheth, Neeraja" <Neeraja.Sheth at fnc.fujitsu.com> on 03/30/2001 12:11:47 AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  Early archiving of inbound invoices in SAP 4.6C
 
 
 
I need urgent help with the early archiving of inbound invoices.
 
With 3.1I, we used the workflow object BKPF, method CREATE with task TS
00007869, and call transaction MR01. In SAP 4.6C, we modified this to call
transaction MIRO. This did not work. We tested with OSS note 338818 which
exactly describes our problem - the workitem can be executed, the invoice
gets
created using transaction MIRO, but after executing the workitem, the image
does
not go away. The invoice is created, but the image is not assigned, and the
workitem stays in the inbox. It still does not work.
 
We also tried with the Document type customizing wizard - object BUS2081 and
the
method CREATE, with the task for entry and the task for assignment both
being TS
30001128. But this has not worked either.
 
 
Thanks in advance,
 
Regards
 
Neeraja
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20010403/ac809374/attachment.htm