Re-releasing PO

Content was last updated in 06.23.05-00

Revision History

Even after PO is fully approved or Rejected, it can be re-released by editing/updating any fields in the released PO.

Once PO is re-released, R2 considers shall consider it as new PO (A 'New Version' of the previous PO).

Though R2 does not change the original PO Number. It appends the Version number in the PO screen.

 For Re-releasing any PO, the approval status should be Open, Approved, Rejected. 

Let us understand through an example

Let's say, you have an existing PO with the status as 'Rejected'.

You have updated some fields in it such as Amount, Department, and Vendor and released it again.

R2 will display the following message:

On this prompt if you select:

• Save as 'New': R2 will create a new version of the existing PO, along with the changes you have made. The status of the PO at this stage will be 'New'.

• Release Now: R2 will submit the PO for approval along with the changes you have made. And the following prompt will be displayed.

• Abandon Changes: R2 will closed the PO and all the changes that you have just made will be lost. There will not be any change to the 'Version' of the PO.

Configuring 'Selected' fields for Re-Releasing the PO

R2 allows you to configure that 'Changes to which all fields in PO' would be considered as modification to PO by R2.

These settings can be done in the Configuration Module. And 'Only the fields selected in this settings' will be considered when R2 validates if a PO was modified or not.

To make these settings Go to Configuration and click on PO re-release button

Choose the required set of fields by 'Selecting the heck box' to customize re-release and save after selecting.