LIV - Method to release invoice in background
Kouw, FA - SPLTX
fa.kouw at td.klm.com
Fri Oct 10 10:40:43 EDT 2003
Hi,
Don't know if this helps, but I have modified standard SAP workflow WS20000397 (MMIVBlockedP, Treatment of inv. blkd for price, Log.IV) which uses methods BUS2081.BlockedPriceCheckUpdate (function module MRM_BLOCKEDPRICE_CHECK_UPDATE) and BUS2081.BlockedPriceDeleteUpdate (function module MRM_BLOCKEDPRICE_DELETE_UPDATE). Maybe these function mudules (that remove price blocks instead of quantity blocks) offer a solution to your problem (a
function called in the mentioned function modules is MRM_INVOICE_RELEASE_UPDATE for releasing the invoice)?
Regards,
Fred Kouw
John Soden wrote:
> Have a look at what RM08RELEASE does - you might find a function in function
> group MRBR that you can call in a method to do what you want...
>
> -----Original Message-----
>> From: Cristiana D'Agosto [mailto:cristiana.dagosto at au1.ibm.com]
> Sent: Thursday, 9 October 2003 12:01 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: LIV - Method to release invoice in background
>
> Thanks for clarifying that.
>
> It seems that what I want to do is different from what you are doing; I want
> the report to run but with radio button 'Release automatically' switched on,
> in the background, within my workflow.
>
> Regards
>
> Cristiana
>
> John Soden <John.Soden at newmont.com.au>
> Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
> 09/10/2003 11:33 AM
> Please respond to "SAP Workflow Users' Group"
>
> To: SAP-WUG at MITVMA.MIT.EDU
> cc:
> Subject: Re: LIV - Method to release invoice in background
>
> RM08RELEASE is run within the workflow for manual unblocking when there is a
> variance between PO and IV and supply want to pay as invoiced but they cant
> change the PO to effect the 3 way match.
>
> It also runs outside the workflow in auto mode via a background job to
> unblock any invoices where GRs have been entered, the PO has been changed or
> a credit raised to effect the 3 way match - when the invoice is released any
> outstanding workflow items are cancelled
>
> -----Original Message-----
>> From: Cristiana D'Agosto [mailto:cristiana.dagosto at au1.ibm.com]
> Sent: Thursday, 9 October 2003 9:55 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: LIV - Method to release invoice in background
>
> Hello John,
>
> do you run RM08RELEASE within your workflow? That's where I am having
> problems. I want to call RM08RELEASE from a bakground method and I have been
> able to do so. I mean, the report runs but the output is still displayed on
> the screen; I wanted the report to run and then, in a later step, I will
> check an attribute in my object type to verify if the invoice is still
> blocked or not.
>
> Regards
>
> Cristiana
>
> John Soden <John.Soden at newmont.com.au>
> Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
> 09/10/2003 09:32 AM
> Please respond to "SAP Workflow Users' Group"
>
> To: SAP-WUG at MITVMA.MIT.EDU
> cc:
> Subject: Re: LIV - Method to release invoice in background
>
> I've just set up an invoice block workflow - part of the process is to run
> RM08RELEASE in background nightly (auto mode) to unblock any invoices that
> block only because the GR was missing, if there is a variance between PO line
> GR and IV, a workflow item goes to supply, if they can't fix it, they send it
> on to accounts to raise a credit or to the AP super to unblock manually if
> they want to accept the difference (uses a method that calls RM08RELEASE in
> manual mode with the invoice number) . If supply can fix it by changing the
> PO, the block will be removed the following night.
>
> Hope this helps
> Cheers john
>
> -----Original Message-----
>> From: Cristiana D'Agosto [mailto:cristiana.dagosto at au1.ibm.com]
> Sent: Thursday, 9 October 2003 8:16 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: LIV - Method to release invoice in background
>
> Thanks Eric,
>
> at least now I know what SingleRelease is used for! I thought it would do the
> same thing as RM08RELEASE does, and it would only release the FI doc if the
> block could have been removed from MM.
>
> Not sure how I will execute the report (RM08RELEASE) in the background
> though, I was hoping somehwere else in the group would have done that before!
>
> Regards
>
> Cristiana
>
> eric.esten at philips.com
> Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
> 08/10/2003 04:15 PM
> Please respond to "SAP Workflow Users' Group"
>
> To: SAP-WUG at MITVMA.MIT.EDU
> cc:
> Subject: Re: LIV - Method to release invoice in background
>
> Hi Christiana,
>
> Just finished a course on SAP Workflow and tried also BUS2081.SingleRelease
> for releasing the invoice. As you know in the Logistic Invoice Verification
> you both get a MM- and FI document in the system.
>
> In my workflow I saw that the FI document is released with SingleRelease
> while the MM document remains blocked, which of course is not correct. I
> didn't manage to unblock the MM document with this method.
>
> The old invoice verification is worked out pretty good in SAP Workflow while
> the 'new' LIV still needs a lot of improvement.
>
> Kind regards,
>
> -----------------------------------------------------------------------------
> -----------------------------------------
> Eric Esten
> Philips Consumer Electronics Eindhoven
> SAP Competence Center / Bldg. SK6-66
> Business Analyst FiCo
> E-mail: eric.esten at philips.com
> Tel: +31 (0) 40 27 34817 Fax: +31 (0) 40 27 32199
> Vienna: +43 1 60101 1556
> -----------------------------------------------------------------------------
> ------------------------------------------
>
> "Cristiana D'Agosto" <cristiana.dagosto at au1.ibm.com>
> Sent by:
> SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
> 2003-10-08 02:42 AM
> Please respond to "SAP Workflow Users' Group"
>
> To: SAP-WUG at MITVMA.MIT.EDU
> cc: (bcc: Eric Esten/EHV/CE/PHILIPS)
> Subject: LIV - Method to release invoice in background
> Classification:
>
> G'day all,
>
> we are in 4.6c
>
> I am building a workflow to handle MM invoices blocked for quantity reasons.
>
> The workflow will send a work item to someone and after this someone executes
> one of the options the next step is to run report RM08RELEASE (Release
> Blocked Invoices - transaction code MRBR) in the background for the relevant
> invoice number and setting radio button 'Release automatically'.
>
> Not being very successful!
>
> I am still figuring out what method BUS2081.ReleaseSingle does? Maybe it does
> what I am trying to do?
>
> I wrote a little method that looks like this:
>
> SUBMIT RM08RELEASE
> WITH SO_BUKRS-LOW = '1000'
> WITH SO_BELNR-LOW = object-key-invoicedocnumber
> WITH SO_GJAHR-LOW = object-key-fiscalyear
> WITH PA_XMANU = ''
> WITH PA_XAUTO = 'X'
> EXPORTING LIST TO MEMORY
> AND RETURN.
>
> The report runs okay but it does show me the output screen (e.g 'Blocking
> reasons deleted in 0 lines' message is displayed in the bottom of the
> screen), and I would like to avoid that (that's why I used EXPORTING LIST TO
> MEMORY). I just want to run the report for that invoice and later in my
> workflow I will check if the block was removed or not.
>
> Any other ideas?
>
> Thanks and regards
>
> Cristiana
>
> Scanned by Newmont Australia Ltd. Anti Virus gateway
>
> IMPORTANT NOTICE - By storing, copying, relying upon or otherwise using this
> e-mail, you agree to be bound by our Terms Governing Electronic
> Communications. A copy of these terms can be reviewed at
> www.newmont.com.au/eComm-terms.htm or obtained by phoning us on +61 8 8303
> 1700. If you do not accept these terms or suspect that you may have received
> this e-mail message in error, please notify the sender and promptly delete
> this e-mail.
>
> Scanned by Newmont Australia Ltd. Anti Virus gateway
>
> IMPORTANT NOTICE - By storing, copying, relying upon or otherwise using this
> e-mail, you agree to be bound by our Terms Governing Electronic
> Communications. A copy of these terms can be reviewed at
> www.newmont.com.au/eComm-terms.htm or obtained by phoning us on +61 8 8303
> 1700. If you do not accept these terms or suspect that you may have received
> this e-mail message in error, please notify the sender and promptly delete
> this e-mail.
>
> Scanned by Newmont Australia Ltd. Anti Virus gateway
>
> IMPORTANT NOTICE - By storing, copying, relying upon or otherwise using this e-mail, you agree to be bound by our Terms Governing Electronic Communications. A copy of these terms can be reviewed at www.newmont.com.au/eComm-terms.htm or obtained by phoning us on +61 8 8303 1700. If you do not accept these terms or suspect that you may have received this e-mail message in error, please notify the sender and promptly delete this e-mail.
>
> _________________________________________________________________________________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************
_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________
More information about the SAP-WUG
mailing list