Logistic Invoice verification

[ASSY, SOSTHENE]

Hi Phillips,
 Let me show what I did.
 
1. I've  a copy of 1060
 
 
 
2. I've include the the call funion in the function module.
 
 
 
 
 
 
Is the process good ?
 
Please Advice
 
 
Thank you
 -----Original Message-----
From:   Phillips, Tim [mailto:Tim.Phillips at ser.com]
Sent:   Monday, September 16, 2002 4:45 PM
To:     Assy, Sosthene          (AFDB)
Subject:        RE: Logistic Invoice verification
 
Hi Sosthene,
 
Actually, I think it's 1060 you want.
 
The report you want is transaction BERE (accessible through the FIBF menu).
 
It exists in 4.0b of SAP, and I've just had it confirmed from a friend that
it's also in 4.5b.
 
You don't need to enter any additional selection criteria.  When you execute
the report, you should get a list of all interfaces available - I think you
want the one:
 
00001060 POST DOCUMENT: Invoice Check
 
This is called when you post an IV invoice; not sure about LIV - you may
have to test to be sure.  If it isn't, look at 00001030 and see if you can
put your code in there - you can use t_bkpf-awtyp = 'RMRP' or even
t_bkpf-tcode = 'MR1M' to see whether it's the right kind of invoice, so
you're not raising events willy-nilly.
 
Regards,
 
Tim
 
-----Original Message-----
From: ASSY, SOSTHENE
To: SAP-WUG at MITVMA.MIT.EDU
Sent: 16/09/2002 11:27
Subject: Re: Logistic Invoice verification
 
HI Philipps
 
Thank you for your answer.  I,ve executed the Tcode FIBF but I didn't
find
the the code 1050 for Invoice verification. We're working on 4.5B.
Please advice
 
Thank you
 
 
 -----Original Message-----
From:   Phillips, Tim [mailto:Tim.Phillips at ser.com]
Sent:   Monday, September 16, 2002 12:54 PM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: Logistic Invoice verification
 
Hi Sostene,
 
I think you need to set up the triggering event via a business
transaction
event (FIBF).
 
Select: Environment --> Info system (P/S), then execute the report.  See
if
there are any interfaces that would work - normally you use 00001050 for
IV
invoices.
 
Once you've found your interface, you can register your own function
module
against it (using the same interface as the provided sample - field
T_BKPF-AWKEY will contain your business object keys), and raise your
event
using 'SWE_EVENT_CREATE_FOR_UPD_TASK'.
 
Hope that helps,
 
Tim
 
-----Original Message-----
From: ASSY, SOSTHENE
To: SAP-WUG at MITVMA.MIT.EDU
Sent: 16/09/2002 06:24
Subject: Logistic Invoice verification
 
I've developed a WF for Logistic Invoice verification using Object
BUS2081,
the event Created and the Tcode MR1M.
 When triggered manually, the workflow works. Automatically, the WF is
not
triggered.
Is there a way to make it run with the event created.
 
Please Advice
 
 
This e-mail and any attachment sent with it are confidential and
intended
solely for the use of the individual to whom it is addressed. If you
have
received this e-mail by error please delete it immediately. No reference
should be made of the information contained in this e-mail.  The views
or
opinions expressed in this message, unless otherwise clearly indicated,
are
solely those of its author and do not necessarily represent those of the
ADB.  Unauthorized publication, use, dissemination, forwarding, printing
or
copying of this e-mail and its associated attachments is strictly
prohibited.  ADB believes but does not warrant that this e-mail and any
attachments are virus-free.  You must therefore take full responsibility
for
checking for viruses therein. ADB disclaims any responsibility and
liability
arising from your unauthorized use of the contents of this e-mail or
your
failing to ensure that it is virus-free.
 
 
This e-mail and any attachment sent with it are confidential and
intended
solely for the use of the individual to whom it is addressed. If you
have
received this e-mail by error please delete it immediately. No reference
should be made of the information contained in this e-mail.  The views
or
opinions expressed in this message, unless otherwise clearly indicated,
are
solely those of its author and do not necessarily represent those of the
ADB.  Unauthorized publication, use, dissemination, forwarding, printing
or
copying of this e-mail and its associated attachments is strictly
prohibited.  ADB believes but does not warrant that this e-mail and any
attachments are virus-free.  You must therefore take full responsibility
for
checking for viruses therein. ADB disclaims any responsibility and
liability
arising from your unauthorized use of the contents of this e-mail or
your
failing to ensure that it is virus-free.
 
 
This e-mail and any attachment sent with it are confidential and intended
solely for the use of the individual to whom it is addressed. If you have
received this e-mail by error please delete it immediately. No reference
should be made of the information contained in this e-mail.  The views or
opinions expressed in this message, unless otherwise clearly indicated, are
solely those of its author and do not necessarily represent those of the
ADB.  Unauthorized publication, use, dissemination, forwarding, printing or
copying of this e-mail and its associated attachments is strictly
prohibited.  ADB believes but does not warrant that this e-mail and any
attachments are virus-free.  You must therefore take full responsibility for
checking for viruses therein. ADB disclaims any responsibility and liability
arising from your unauthorized use of the contents of this e-mail or your
failing to ensure that it is virus-free.