Never tried. It is a multi-record batch process manipulating Business Object method (like order job wizard) so it may not expose what it is doing sufficiently for a VB client customization to leverage.
Put Tracing on and actually convert some suggestions to POs.
Then review the trace log to see if the PO numbers created are listed in the trace (and in a way that they can be related to the originating PO suggestion record for each).
If they are, you have a shot at it (although it may be better suited to BPM instead of client VB.NET).
You may find it can be done by not directly in one pass. You may be have to pass you PO suggestion ud field data to a UDXX table (as temp storage) BEFORE the PO generation BO method kicks in and then rely on a PO Entry mod to complete the work (when new generated PO loaded, pull in your ud info from the UDXX table temporarily holding it - then null out the UDXX record).
Hopefully you find it can be done more directly.
I can't pull up the data dictionary at the moment & look but if the PO suggestion detail table retains records after a suggestion is converted to a PO AND the record is perhaps (ideally) updated and references the PO created from it, you should then have a way to directly pass the ud field values (not needing a UDXX table intermediary).
Again though, probably better suited for BPM as you don't want VB.NET modified client apps bogging down trying to keep up with a server batch process BO method.
Rob
Put Tracing on and actually convert some suggestions to POs.
Then review the trace log to see if the PO numbers created are listed in the trace (and in a way that they can be related to the originating PO suggestion record for each).
If they are, you have a shot at it (although it may be better suited to BPM instead of client VB.NET).
You may find it can be done by not directly in one pass. You may be have to pass you PO suggestion ud field data to a UDXX table (as temp storage) BEFORE the PO generation BO method kicks in and then rely on a PO Entry mod to complete the work (when new generated PO loaded, pull in your ud info from the UDXX table temporarily holding it - then null out the UDXX record).
Hopefully you find it can be done more directly.
I can't pull up the data dictionary at the moment & look but if the PO suggestion detail table retains records after a suggestion is converted to a PO AND the record is perhaps (ideally) updated and references the PO created from it, you should then have a way to directly pass the ud field values (not needing a UDXX table intermediary).
Again though, probably better suited for BPM as you don't want VB.NET modified client apps bogging down trying to keep up with a server batch process BO method.
Rob
--- On Mon, 3/2/09, melissa hietala <kevmel822@...> wrote:
From: melissa hietala <kevmel822@...>
Subject: [Vantage] 8.03.4XX PO Suggestion Entry
To: vantage@yahoogroups.com
Date: Monday, March 2, 2009, 12:33 PM
Does anyone know if there is a way to capture what PO is being created when a user "generates" purchase orders in PO Suggestion Entry? What I am ultimately looking to do is add a UD field to the PO Suggestion Entry screen, and have the value that is entered into this field flow into a UD field for the PO that is created. Any thoughts!?!?
Thank you,
 Dustin Biniek
UMC, Inc.
DustinB@ultramc. com
[Non-text portions of this message have been removed]