*Reject* PO in background?

[Mike Pokraka]

Sounds like the easiest workaround so far and would fit our scenario
perfectly. I'll run that past the business and see if they'll go for it.
Thanks!
Mike

On Thu, March 1, 2007 8:18 pm, Stevens, Seth wrote:
> Alon,
>
> I used BAPI_PO_GETITEMS to get the line items for the PO.  I then built
> an internal table out of the results with the deletion indicator set on
> each line then passed the table into BAPI_PO_CHANGE po_items table.
>
> To reset the releases I simply used the standard ResetRelease method on
> BUS2012 and pass in the lowest release code.  Depending on your release
> procedure configuration the releases may automatically reset.  We are
> dealing with header level release.
>
> Hope this helps.
>
> Thanks,
> Seth
>
>
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Alon Raskin
> Sent: Thursday, March 01, 2007 2:09 PM
> To: SAP Workflow Users' Group
> Subject: RE: *Reject* PO in background?
>
>
> Hi Seth,
>
> Yes I remember you posting it.
>
> Logical Deletion is a good way to go. Since Mike is being lazy...can you
> share some code?
>
> Alon
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu on behalf of Stevens, Seth
> Sent: Thu 3/1/2007 15:05
> To: SAP Workflow Users' Group
> Subject: RE: *Reject* PO in background?
>
>
>
> Alon,
>
> We had the same issue.  I also posted the question with no luck.
>
> Our finial solution, although not the best, was to reset all the
> releases and then logically delete all the line items on the PO.
>
> Thanks,
> Seth
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Thursday, March 01, 2007 12:20 PM
> To: SAP Workflow Users' Group
> Subject: RE: *Reject* PO in background?
>
> Hi Alon,
>
> Oops of course I meant to write *Reject* in the last subject, not
> release!
>
> Thanks, I think I even found your post & that's what it started to look
> like when we dug around :-(
>
> Cheers,
> Mike
>
> On Thu, March 1, 2007 5:54 pm, Alon Raskin wrote:
>> Mike,
>>
>> I posted this question quite a while ago but no one seemed to have an
>> answer. I hope you have better luck.
>>
>> I spent quite a bit of time debugging and then writing my own code to
>> do the 'rejection'. I ended up giving up as the code that SAP provides
>
>> is very difficult to replicate (a lot of the logic is mixed in with
>> the presentation logic).
>>
>> Alon
>>
>>
>> ________________________________
>>
>> From: sap-wug-bounces at mit.edu on behalf of Mike Pokraka
>> Sent: Thu 3/1/2007 12:47
>> To: sap-wug at mit.edu
>> Subject: Release PO in background?
>>
>>
>>
>> G'Day folks,
>>
>> Does anyone have a shortcut, secret function module or equivalent to
>> BAPI_PO_RELEASE to *reject* a Purchase Order on 4.7? There's
>> BAPI_PO_RESETRELEASE, but alas no reject.
>>
>> I admit I'm being a little bit lazy here but
>> a) an hour searching/debugging has been fruitless
>> b) this seems normal enough that someone's come across this before,
>> and
>> c) it's hometime and I'm hoping someone has a simple answer :-)
>>
>> Any input appreciated,
>> Mike
>>  (Crossposted to WUG and SDN)
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
> --
> Mike Pokraka
> Senior Consultant
> Workflow Connections
> Mobile: +44(0)7786 910855
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> -----------------------------------------
> *Please note my E-Mail Address has changed.  Please update your
> contact list*
>
> Anadarko Confidentiality Notice:
> This electronic transmission and any attached documents or other
> writings are intended only for the person or entity to which it is
> addressed and may contain information that is privileged,
> confidential or otherwise protected from disclosure.  If you have
> received this communication in error, please immediately notify
> sender by return e-mail and destroy the communication. Any
> disclosure, copying, distribution or the taking of any action
> concerning the contents of this communication or any attachments by
> anyone other than the named recipient is strictly prohibited.
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
>
>
> -----------------------------------------
> *Please note my E-Mail Address has changed.  Please update your
> contact list*
>
> Anadarko Confidentiality Notice:
> This electronic transmission and any attached documents or other
> writings are intended only for the person or entity to which it is
> addressed and may contain information that is privileged,
> confidential or otherwise protected from disclosure.  If you have
> received this communication in error, please immediately notify
> sender by return e-mail and destroy the communication. Any
> disclosure, copying, distribution or the taking of any action
> concerning the contents of this communication or any attachments by
> anyone other than the named recipient is strictly prohibited.
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


-- 
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855