Early archiving of inbound invoices in SAP 4.6C

[Gregory Kowalik]

In 4.5B you have to trick the system like Brian says.
Since 46b, you don't have to, the image gets attached to both MM and FI doc.
You can use early archiving and the image will get attached as I said to both MM
and FI doc.
Why don't you try taking out the assignment task TS30001117 out from your
configuration (watch out, wizard might not work), and just do early archiving.
Then after you enter the invoice, from your LIV doc. display transaction, branch
to accounting document and do system-links. You will see 2 entries: one for
accounting doc. with acc. doc. number, second for Invoice document with your LIV
doc. number. Pick the LIV invoice entry and it will take you to display the
image.
 
Greg
 
 
 
 
 
 
Brian Bennings <bennings.bj at pg.com> on 04/05/2001 06:32:17 PM
 
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.6C
 
 
 
The accounting document is a BKPF object.  Setting it up this way will prompt
you for the doc number, company code, and fiscal year.
 
We are doing this in 4.5b and when you either early or late archive link to LIV
is does not automatically link to the FI document.  We have created new methods
in a new ZIMAGE business object that we delegated back to IMAGE.  In these
methods after the initial LIV link is made, we look up the FI number and send it
through the same function module, creating the FI link.
 
Brian
 
 
 
 
 Internet Mail Message
 Received from host:      cherry.ease.lsoft.com
 [209.119.0.109]
 
 
 
From: "Sheth, Neeraja" <Neeraja.Sheth at fnc.fujitsu.com>@MITVMA.MIT.EDU> on
04/05/2001 05:10 PM
 
                                "Sheth, Neeraja"           To:
SAP-WUG at MITVMA.MIT.EDU
 <Neeraja.Sheth at fnc.fujitsu.com>@MITVMA.MIT.EDU>           Cc:    (bcc: Brian
Bennings-BJ/PGI)
                                                   Subject:      Re: Early
archiving of inbound
                                                        invoices in SAP 4.6C
                          Sent by:  SAP Workflow
                  <Owner-SAP-WUG at MITVMA.MIT.EDU>
                             04/05/2001 06:10 PM
   Please respond to "SAP Workflow Users' Group"
                        <SAP-WUG at MITVMA.MIT.EDU>
 
 
 
 
 
Thank you for your timely input, Mark, Brian and Greg. I waited till we had
tested and transported to production before replying.
 
Greg, I had already used the customizing wizard to configure the workflow by the
time I read your mail. I used BUS2081 method CREATE, and TS30001128 for entering
the image and TS30001117 for assigning it. We are on 4.6C and this invokes MIRO
and F-43 correctly as per configuration and creates the invoice.
 
As per your email, I checked step by step, and the wizard has done exactly the
same things. Where we differ is - I only see the link in the Logistics Invoice,
and not in the accounting document.  I execute transaction MIR4, and click on
the Services for objects icon and then click on the Attachments (second) icon in
the popup box (alternatively menu path System > Services for Object > second
icon on the Attachments popup box). This is my first question - how do you have
a link with the accounting document? Even if I execute FB03, I have to go to
invoice from there, and then look at the image. Also, after archiving, the
mesage at the bottom of the screen gives the invoice number - we would like to
be able to see the accounting doc number.
 
My second question is - how do I execute late archiving using the accounting
document number? When I go for late archiving, the popup box asks for invoice
number (Logistics invoice) whereas in Accounts Payable, they swear by the
accounting doc number which they religiously write on the paper document.
 
Any help is appreciated.
 
Regards
 
 
Neeraja
 
 
 
 
 
> -----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
>