Help Ataching an just scanned bill image by documents in R/3

Wed Jan 18 09:04:43 EST 2006

  Thanks a lot my friend.

  You don't know what it means to me. I was trying to find some documentation like this a long time ago. And alone without know how, it was so hard to do... or impossible to do. I've already had debuging OAWD and FB03 to see how it (GOS) works.

  Thanks a lot. I think this will help me a lot to do this work!

  Glauco S. Kubrusly
  Abap/Workflow consultant
  Brazil/Rio de janeiro

"Tiwari, Rammanohar" <rammanohar.tiwari at logicacmg.com> escreveu:
  May be my scenario is similar...

After reading the document imagine my ZFRIENDS as your ZDOCUMENT and so on...

http://www.geocities.com/rmtiwari/Resources/Training/BusinessWorkflow/SAPApplicationDevelopment.pdf

or 
http://www.geocities.com/rmtiwari/Resources/Training/BusinessWorkflow/SAPApplicationDevelopment.htm

Cheers,
Ram

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Glauco Kubrusly
Sent: Sunday, January 15, 2006 2:59 AM
To: Breslavets Sergey; Process Control Step
Subject: RE: Help Ataching an just scanned bill image by documents in
R/3

Hi Sergey, ok. I will try to explain my problem and I
will try to be more especific.

thanks for your atention. My English is not good, but
I will try.

I've already read some documents about my issue, but I
didn't understand some specific parts, like:
- must programme with methods ?
- How do I get the image scaned by IXOS (I'm using
IXOS to scan)?
- Where can I store it ?
- I know that the image can be linked with R/3
documents by some table... but, im my case, my
"document" is created... is a Zdocument that we called
here as "Protocolo", that hold some bill's data, as
number, serie, date etc. And we want to get the bill
image and link with our protocol Zdocument that have
its own table.

the workflow will follow by a Ztransaction, that is
the same that the user received the bill and the
material and will starts the workflow... the 2nd user
of the flow will receive a task and will open this
Ztransaction again and would see this scaned image and
click in a button to open MIGO to him.

this workflow will follow this flow until payment.

1- how can I get the image scaned by ixos and store it
on R/3 ?
2- how can I put a funtionality to show this image in
this Ztransaction ?

Please, I'm stoped here.... without having sucess ...

thanks,

Glauco

--- Breslavets Sergey 
escreveu:

> Hi Glauco,
> 
> i can help you. 
> 
> This kind of application is commonly known as
> Imaging (AP) workflow or Incoming Invoice Ledger.
> I'm specializing in this and have implemented ton of
> different scenarios - i actually have developed my
> own product in the process. It's not terribly
> difficult once you know what to do, but not a
> trivial as well. Couple of other companies in US do
> that, one of them is IXOS - was my client - i have
> developed the product(commercial) version of the
> Imaging workflow for them. 
> 
> Basically there are several components to the
> solution:
> 1. Invoice reader (can be OCR module, manual -
> Zransaction, RFC feed, etc)
> 2. Incominig Invoice Ledger - the main repository
> for the scanned invoices and attributes 
> 3. Approval/Posting workflow that routes the image
> for approval, creates MM documents, post invoices,
> etc.
> 4. Invoice Ledger Viewer - end-user browser to
> monitor the scanned invoices and control the process
> process
> 
> There are many variations to this depending on the
> way customer processes invoices. e.g. Do they
> process MM invoices only, or Services too. do they
> process multy or single line invoices, how do you
> want to keep the images, retention periods, etc... 
> 
> It's hard to try to explain step-by-step what do you
> have to do in order to develop the solution from
> scratch. 
> 
> 1. You can start from determining what information
> you will need in order to process/post the invoice
> (e.g. invoice date, amount, currency, vendor, etc.)
> and what information will be required for reporting
> purposes for your client (they will probably want to
> see some summary report of processed invoices). when
> you know that, you can then figure out what
> information you shall obtain from the indexer (the
> person who will run ztransaction), and what can be
> gathered later in the process. Look at the sample of
> invoice and see what can be extracted from there. 
> 
> 2. you will need to create your own business object.
> I can show you structure and methods.
> 
> 3. these fields are the reference key to the
> logistic document. You don't have to bother about
> them now.
> 
> 
> Please ask if you have any specific questions and
> i'll try to answer them. 
> 
> 
> Best Regards,
> Serge
> 314-761-5217
> sergey.breslavets at sapbpm.com
> 
> 
> 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu]On Behalf Of Glauco
> Kubrusly
> Sent: Thursday, January 12, 2006 11:05 AM
> To: sap-wug at mit.edu
> Subject: Help Ataching an just scanned bill image by
> documents in R/3
> 
> 
> Hi friends,
> 
> I'm sorry because my English isn't good but I'll try
> to explain my situation here.
> 
> I need to create a link between my own "SAP object"
> (for example billing data) and archived image stored
> in IXOS.
> 
> My process here is to develope a control to
> materials received using workflow. The vendow will
> delivery to us, the user will scan the bill and put
> some data in some fields in a screen in a
> Ztransaction. All I want is atach this new bill
> (just scanned by him).
> 
> The customer here thinks that the user can't have
> difficult things to do, so we have to develop a
> solution that give him a practical process to do it.
> 
> We have the follow solution: 
> We want to develop an aplication that starting from
> our application, in save moment, calls the ixos scan
> client and scan one bill by process only ('cause we
> think the user can complicate thi! s process if he
> scan a lot of documents and it can start wrong bills
> by processes). And we want to create another
> solution instead the standard OAWD transaction (that
> is the IXOS standard solution).
> 
> then... we want (if possible):
> 1-the user receive the bill,
> 2-the user fill the screen, field-by-field and save
> (it is one bill by each process);
> 3-(in the save moment) our transaction can start the
> ixos scan client and give to the user the
> opportunity to scan the bill;
> 4-after that, we will start the workflow to aprove
> this bill, MIGO, MIRO and finally do the payment.
> 
> Is it hard to do ?
> 
> a) I've already have an object in SWO1 with the
> methods: GetApplLinks and GOSAddObjects.
> 
> b) I've read documents about Object oriented
> programming, utilizing methods but I didn't
> anderstand what I must do to can atach a just
> scanned bill on a Ztransaction.
> 
> c) I've read about 3 fields AWSYS! , AWKEY and
> AWTYP, but I couldn't make it work.
> 
> What must I do ?
> 
> 
> 
> 
> Glauco S. Kubrusly 
> 
> 
> _____ 
> 
> Yahoo! doce lar. Faça 
>

> do Yahoo! sua homepage.
> 

_______________________________________________________ 
Yahoo! doce lar. Faça do Yahoo! sua homepage. 
http://br.yahoo.com/homepageset.html 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

Glauco S. Kubrusly

---------------------------------
 Yahoo! doce lar. Faça do Yahoo! sua homepage.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060118/6a9c9bf8/attachment.htm