Early Archiving

[Mark Peterson]

Hi Serge,

We have a Early Archiving process with workflow for processing incoming
invoices. Here's how it works, we keep track of the users actions by using
EXPORT / IMPORT of some document parameters. We use a BAdI that's called
just after the transaction is exited. In the BAdI we export the document
parameters using the EXPORT statement and in a custom method of a subtype of
BO IMAGE we IMPORT the document parameters from memory and check if the
document no. is initial. If it's initial, then the user has opted to cancel
the transaction.

I think the actual image is linked to the document using the method ASSIGN
of the BO IMAGELINK.

Hope this helps. Get back to us if you need more help.

Thanks and Regards,
Mark


On Nov 22, 2007 10:16 AM, Serge Boulay <serge.boulay at n-spro.com> wrote:

>  Hi All,
>
>
>
> In the Early archiving process using the standard SAP Workflow task, the
> transaction is to create, let say a PO, is called and wait until the PO is
> created (which creates an  IMAGE.ASSIGNED event) before the task gets
> completed. If anyone is using this, how do you manage the fact the user may
> not want to process the PO and cancel everything?
>
>
>
> Thanks,
>
>
>
> Serge Boulay
>
> Associate/Associé
>
>
>
> */n Spro Inc*
>
> 314-A Lakeshore Blvd
>
> Pointe-Claire (Québec)
>
> H9S 4L5
>
>
>
> c: 1.514.830.0750
>
> o: 1.514.907.2505 x205
>
> f: 1.518.207.9005
>
> e: serge.boulay at n-spro.com
>
>
>
> www.n-spro.com
>
>
>
> P Merci de penser à l'environnement avant d'imprimer ce courriel.
>
> Thank you for thinking about the environment before printing out this
> e-mail.
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071210/9ea0d2ba/attachment.htm