jdtrent
(Joe D Trent)
January 5, 2024, 9:27pm
1
Hey,
The purchasing folks would like to keep in some kind of snapshot history of a PO whenever it’s revised.
I’m thinking something like this:
Add UD field POHeader.RevisionNum_c.
When the PO is approved, a BPM increments POHeader.RevisionNum_c, generates a PDF copy, and stores it in a network folder.
We could use APR to generate and email the PDF, but it might not be printed for each approval.
I’m not immediately seeing a way to do this from a BPM. Any experience here?
Thanks,
Joe
ridgea
(Alex Ridge)
January 5, 2024, 9:47pm
2
Hi @jdtrent ,
Conceptual I guess you could look at kind of cloning the PO tableset in a UD100 / UD100A table I guess, the main variables will be if there are specific things that they would like to track.
I guess you could dump:
POHeader —> UD100
SupplierID
TotalAmmount
MiscCharfesTotal
Etc…
Iterate over PORels with some
Detials from PODetail → UD100A
Qty
Partnum
Unit price
Cost code
Due date
Or something along those lines
Set some of the UD100A bools by comparing field changes unmodified row vs update/added/deleted
jdtrent
(Joe D Trent)
January 5, 2024, 10:12pm
3
Cool. That’s an option to present to the purchasing folks.
Thanks, Alex
Joe
SueLowden
(Sue Lowden)
January 8, 2024, 11:09am
4
Have you looked at Change Logging the fields that they want to monitor?
jdtrent
(Joe D Trent)
January 8, 2024, 4:39pm
5
A little. But it doesn’t really keep a snapshot of the PO. And if you delete a PO line the log detail is deleted too, unless that functionality has changed.
Thanks,
Joe
SueLowden
(Sue Lowden)
January 12, 2024, 2:49pm
6
Deletions in change logging has always been an issue, but you can get around that by using a UD table