This is my understanding, and I hope I am wrong.
Basically, I am asking if there is any way to interact with PO Suggestions other than a DD? I know I could do an In Transaction and/or Standard DD on SugPODtl, but is that it?
It is a black box. You can run a post processing BPM, but that runs immediately after it’s submitted, not after it’s done.
If you use a process set on a schedule, then you can at least run a function after suggestions are completed. But that only works in a process set.
Thanks @Banderson for confirming!
Pretty much. I suppose you could schedule a Function that runs after the job if you’re nervous about slowing the process down with Data Directives.
What are you trying to do? I’m intrigued. We have done some things with PO suggs.
Problem with AUOM is that you lose all of the relevant data when PO Suggestions runs. In reality, you need 2x2, 6x9, and 8x4 pieces of material, but PO sugg lumps it all together and says you need 1532 sqin (don’t even try checking the math, I just smashed keys). You lose all of the data that makes it relevant for purchasing.
I know about the “comment” trick with suggestions, but that would not work because the AUOM data is wiped no matter what. Even if I was able to get each suggestion be for one piece of material, the attribute sets still won’t be there. It would make it easier to bring the data back in to PO sugg, but 
.
I could do a Standard DD that calls a function to identify the records in PartDtl and populate the AUOM data. But now you would have to code in a bunch of the PO sugg logic with the cutoff date and DOS, etc .
It seems like there is no “good” way to do it, which is probably why Epicor has not addressed the issue yet. I’m thinking the “best” option is to create a BAQ that looks up the part number in PartDtl, and return all rows with dates and maybe throw in inventory levels too. It would not be bad if I could make it be in line with the suggestions. Like, you could uncollapse something and all the data is there under the sugg row. 
Yeah, I think that’s what I would do. A mini Time Phase grid that shows up when you load a suggestion. And if the data changes after the suggestions are made, that’s probably not a bad thing anyways. As long as the users understand that.
@jkane I have a routine that aligns the suggestion to the demand(s) that created it that runs post processing on POSugg.GetRowsPlant and uses PartDtl to get all of the data.
Hi John,
Still testing and planning our AUOM implementation but FWIW:
Our take is: you either want to order STD sizes and want AUOM to calc pcs of that size or you want to order cut sizes and prevent AUOM calc. In our testing we couldn’t see how to do this automatically using ‘CUT PIECE’ in our theoretical attribute in DynAttrClass but we found we could prevent the lumping calc if we purchase direct.
Purchase Direct prevents AUOM from doing it’s magic. For ‘CUT’ pieces we’re thinking we will always Purchase Direct so we get unique suggestions rather than lumped in with STD sizes.
For other cases, you can see the lumped AttrSet detail in TimePhase and change AttrSet on POSuggestion if wanted.
HTH,
Josh
Thanks @jbooker , I’m going to put my customization into a later phase as they can just use Time Phase for now. Completely forgot about that.
The fact that Time Phase shows only one planning set at a time is not ideal. For example, if some demand is for STD:48x96 and other for STD:96x120 it’s tough for buyers to look across and determine whether they want to combine across STD sizes.
Some sort of ‘what-if TimePhase’ customization around this would be interesting.
