Jira - [Link]
net/browse/OPS-805
The below details are from Jira :
Original Issue: PO Header Revision is being created when Notes are being updated in Classic, but
not in LUI.
On analysis (OPS-681), it was found that the PO Header Revision was being created because of a
bug in VF which needs to be corrected.
OPS-681: PO Header Revisions are not created properly in Lightning, as compared to ClassicClosed
Sam’s Spec:
Current Behavior
We have these fields:
Purchase Order Header - Notes (POHDR_NOTES)
Purchase Order Line - Notes (POLINE_NOTES)
Neither one of these fields has a counterpart on the Revision records (POHDRREV, POLINEREV) and
making changes to these fields does not cause a Revision Change or the subsequent status change
to ‘Submit Changes to Vendor’
We do have on the POLINEREV these fields:
POLINEREV_BUYERCOMMENTS
POLINEREV_VENDCOMMENTS
Changes to these fields does cause a new Revision to be created and also causes a status change
to ‘Submit Changes to Vendor’
Spec Comment
Object Changes
o POCNTL - add field to existing object
POCNTL_REVNOTES Checkbox Rev Purchase Order on Notes
Changes
Help: When enabled, this feature causes a Purchase Order Revision
on the change of Notes on either the PO Header or Line
o POHDRREV - Add field to existing object
POHDRREV_NOTES Text Area(255) Notes
Help: This field carries the PO Header Notes as entered by the user
o POLINEREV - Add field to existing object
POLINEREV_NOTES Text Area(255) Notes
Help: This field carries the PO Line Notes as entered by the user
PO Control Maintenance (VF Page)
o Add the new POCNTL_REVNOTES field to the bottom of the right column of the
main top section of PO Control Maintenance (checkbox control)
POHDR Trigger - change event
o On any change to the value in the POHDR_NOTES field, when POCNTL_REVNOTES =
TRUE perform the ‘revision’ logic just as is done on a change to one of the other
fields controlled by the Rev (for example: POHDR_CARRIER). Depending on the
state of the PO and any existing Revisions, this might cause the creation of a new
POHDRREV, or the update of an existing POHDRREV, or nothing at all. (Again,
follow what happens on a change to POHDR_CARRIER and do the same on a
POHDR_NOTES change).
If a POHDRREV is to be created or updated, set POHDRREV_NOTES =
POHDR_NOTES
POLINE Trigger - change event
o On any change to the value in the POLINE_NOTES field, when POCNTL_REVNOTES
= TRUE perform the ‘revision’ logic just as is done on a change to one of the other
fields controlled by the Rev (for example: POLINE_CARRIER). Depending on the
state of the PO and any existing Revisions, this might cause the creation of a new
POLINEREV, or the update of an existing POLINEREV, or nothing at all. (Again,
follow what happens on a change to POLINE_CARRIER and do the same on a
POLINE_NOTES change).
If a POLINEREV is to be created or updated, set POLINEREV_NOTES =
POLINE_NOTES
Functional Explanation :
PO Header Revision and PO Line Revision are two distinct objects used to track changes made
to a Purchase Order (PO) and its individual lines, respectively.
When a field in the PO header is modified, a new PO Header Revision record is created the first
time. Subsequent changes to the header will update this same revision record However, each time
the PO header is submitted or re-submitted to the vendor, a new PO Header Revision record is
generated to capture the state at the time of submission. All the above is what happens for
POHDR_CARRIER field referenced under POHDR Trigger - change event.
The same explanation goes for PO Line and PO Line Revision as well.
POCNTL – PO Control is an Object which has all the Division level control flags or setting that should
be defaulted or used across the Purchasing process and here we will add a new flag “Rev Purchase
Order on Notes Changes”
