BPM delete PO suggestions

Yahoo Archive
1
Update
I got it working. It turns out that the deletion of PO suggestion appears to allow multiple deletion. It allows multiple row selection and then click delete, gets some flashes and records blipping, etc. However, multiple deletion does not actually occur. Only one reocrd truly gets deleted.

The update bpm below does work on the single record that is actually getting deleted.

--- In vantage@yahoogroups.com, "Nancy" wrote:
>
> Good Afternoon,
>
> We are having difficulties with the deletion of PO suggestions that were based on Requisitions. Once deleted, the suggestion doesn't come back, mrp doesn't generate it, and there is no clue to it ever existing.
>
> To deal with this, I am trying to write a bpm to warn the user that the suggestion, or one of the suggestions he is deleting is associated with a Requisition and is he sure that he wants to continue. if continue, then fine, allow program to proceed with deletion, if abort, throw exception on the whole deletion.
>
> I got it working for single record deletion at a time using POSugg.update method with condition = number of rows in query not < 1 (query is: for each ttSugPoDtl no-lock where ttSugPoDtl.ReqNum > 0 And ttSugPoDtl.RowMod = 'D' )
> then call up bpm data form and then run subsequent bpm on the answer to the buttons. This isn't a problem for one record.
>
> However, whenever I have > 1 PO suggestion selected for deletion and one in the group has a ReqNum I don't get the action. Is there something I'm missing for handling this for multiple record deletion? is there a better way then the Update method?
>
> Thanks for your consideration,
> Nancy
>
2
Good Afternoon,

We are having difficulties with the deletion of PO suggestions that were based on Requisitions. Once deleted, the suggestion doesn't come back, mrp doesn't generate it, and there is no clue to it ever existing.

To deal with this, I am trying to write a bpm to warn the user that the suggestion, or one of the suggestions he is deleting is associated with a Requisition and is he sure that he wants to continue. if continue, then fine, allow program to proceed with deletion, if abort, throw exception on the whole deletion.

I got it working for single record deletion at a time using POSugg.update method with condition = number of rows in query not < 1 (query is: for each ttSugPoDtl no-lock where ttSugPoDtl.ReqNum > 0 And ttSugPoDtl.RowMod = 'D' )
then call up bpm data form and then run subsequent bpm on the answer to the buttons. This isn't a problem for one record.

However, whenever I have > 1 PO suggestion selected for deletion and one in the group has a ReqNum I don't get the action. Is there something I'm missing for handling this for multiple record deletion? is there a better way then the Update method?

Thanks for your consideration,
Nancy