AW: AW: EDI Invoices and Archiving attachments

Schmidinger, Heinz (Unaxis IT BZ) heinz.schmidinger at unaxis.com
Mon Apr 28 02:18:37 EDT 2003


Hi Steve,
 
'delelting' IDCOS is best done by archiving it.
 
With Tx WE47 you can define which IDOC-Status is allowed to be =
archvived.
 
Archving itself is done by Tx SARA; the archiving Object is IDOC.
 
Please note, that DATA-Archiving is in my expirence a very seriuous job =
wher
you have to look for a lot of dependencies from bussiness view as well =
as
from technical view. Thre are significant differneces between Releases =
and
Level of Hotpackages too.
To start could be an analyses of the Database (Tx DB02)  to find out =
e.g.
the 30 lagest tables and the most growing table and looking back to the
basic-archive-objects to this tables. Than you have to find out the
dependencies of this this archvie-objects wher you will find, that you =
have
to archivie  objects before.=20
If you have archvied these chain of objects successfully you will be
expirenced enough to go on with addinional objects.
 
Regards
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: Steve Johnson [mailto:steve_basis at yahoo.com]
Gesendet am: Montag, 28. April 2003 02:40
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: AW: EDI Invoices and Archiving attachments
 
Hello All,
 
Help here, we are live with SAP from last 8 years. We
have lot of departments went spiltting and we have now
lot of unwanted data. I heard from diff. people that
the first thing to delete is IDOC from the systems.
 
Can any one please advise me how to start this and
reduce the data in DB level.
 
Please help!!
thanks,
steve
--- "Schmidinger, Heinz (Unaxis IT BZ)"
<heinz.schmidinger at unaxis.com> wrote:
> Hi Lola,
>
> maybe what you are looking for is 'assign and
> store'.
>
> I haev defined defined doctyes for applictions not
> equal fax.
> In Tx OAWS I have defined this doctype for scenario
> 'assign and stor, in
> SOA0 I have defined the related Objecttype (e.g.
> LFA1 for Creditor) and
> TS00007869 methode CREATE.
>
> Maybe this gives an idee.
>
> Regards
>
> Heinz
>
> -----Urspr|ngliche Nachricht-----
> Von: Lola Oluwa [mailto:Lola.Oluwa at outokumpu.net]
> Gesendet am: Freitag, 25. April 2003 13:34
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: Re: EDI Invoices and Archiving attachments
>
> We already have a live solution with the 'normal'
> ixos scan, early and late
> archiving scenairo...I am talking about "late
> archiving" WITHOUT scan
> client.
>
> Thanks and Regards,
> Lola.
>
>
>
>                       Richard Marut
>                       <rvmarut at earthlink.
> To:
> SAP-WUG at MITVMA.MIT.EDU
>                       net>
> cc:      (bcc: Lola
> Oluwa/Outokumpuext)
>                       Sent by: SAP
> Subject: Re: EDI Invoices
> and Archiving attachments
>                       Workflow
>                       <Owner-SAP-WUG at MITV
>                       MA.MIT.EDU>
>
>
>                       25.04.2003 14:27
>                       Please respond to
>                       "SAP Workflow
>                       Users' Group"
>
>
>
>
>
>
> Lola,
>
> We did early archiving via a scan client software
> that was provided by
> IXOS that scans the document and stores it on a
> content server. From
> there we have a custom transaction that uses
> function module
> ARCHIV_CONNECTDEFINITION_GET to get the archive id
> and then
> ARCHIVOBJECT_CREATE_DIALOG to get the archived
> document number(s). The
> document number is then stored on a custom table
> that is reference
> throughout a Workflow that eventually late archives
> the document.
>
> Prior to all this, you need to configure via
> transactions OAC2, OAC3,
> SOA0, OACA, OAWS, OAG1 and OAD5. When you get to
> OAD5, it will appear
> that you've already done the work but this wizard
> updates a certain
> field on one of the TOA... tables that the other
> transactions don't do.
>
> We've had a few problems with the scanning software
> which was dependent
> on the Windows OS version in combination with the
> amount of memory the
> PC had.
>
> I've been told that the desktop scanning software
> provided with Windows
> works but none of us have had the time to
> investigate.
>
> I hope this helps.
>
> Richard...
>
>
> -----Original Message-----
>> From: SAP Workflow
> [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Lola Oluwa
> Sent: Friday, April 25, 2003 1:47 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: EDI Invoices and Archiving attachments
>
> Hi Richard,
> Thanks for your response, it appears that your
> solution relies on the
> fact
> that the document already exists in the content
> server (perhaps scanned
> through a scan dialog)? The desired solution here is
> to avoid any manual
> input.
> To re-iterate my question a bit clearer, how do I
> get the initial link
> to
> the content server from say my pc. I know that this
> requires some
> detailed
> knowledge of the archivelink interface.... I was
> hoping that someone
> might
> have done this before (content server is ixos).
>
> Best Regards,
> Lola.
>
>
>
>                       Richard Marut
>                       <rvmarut at earthlink.
> To:
> SAP-WUG at MITVMA.MIT.EDU
>                       net>
> cc:      (bcc: Lola
> Oluwa/Outokumpuext)
>                       Sent by: SAP
> Subject: Re: EDI
> Invoices and Archiving attachments
>                       Workflow
>                       <Owner-SAP-WUG at MITV
>                       MA.MIT.EDU>
>
>
>                       24.04.2003 18:45
>                       Please respond to
>                       "SAP Workflow
>                       Users' Group"
>
>
>
>
>
>
> Hi Lola,
>
> I used a few SAP function modules to do linking and
> archiving.
>
> My early archiving used the following
>
> ARCHIV_CONNECTDEFINITION_GET to get the archive id
> ARCHIVOBJECT_CREATE_DIALOG to get the archived
> document number
>
> The document number was initially stored on a custom
> table.
>
> My late archiving to an Accounts Payable document
> used
>
> ARCHIV_GET_CONNECTIONS to establish the connection
> between the archive
> and SAP object
> ARCHIV_CONNECTION_INSERT to provide the actual link
>
> Of course there was a lot more to this such as
> configuration and custom
> code to carry the information throughout the
> process.
>
> Richard...
>
>
> -----Original Message-----
>> From: SAP Workflow
> [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Lola Oluwa
> Sent: Wednesday, April 23, 2003 7:30 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: EDI Invoices and Archiving attachments
>
> Hi,
> I have the following requirement:
>
=3D=3D=3D message truncated =3D=3D=3D
 
 
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
 


More information about the SAP-WUG mailing list