Skip to main content
Skip table of contents

06.23.05-00

R2

Improvements

  1. All New' PO Approval Process with multi-level approvals (R2-20430)

    The methodology of PO approvals in R2 has been enhanced. We have made it hierarchical and streamlined. Let's walk you through the exciting changes we have made.

    • Multi-level approvals by different set of Approvers

      • Now based on the PO Approval Policies as defined, your PO may have to be approved through a multi-level (Employees, Employee Positions, Order PM, Order LP) process. specific Employee.

    • Multi-criteria-based PO Approval Policies.

      • Now the PO Approval Policies are based on several parameters such as Sites (One or More), Department, Raised by

    • Even Custom PO type can defined.

      • The person submitting the PO can track the approval flow in the 'Approvals' tab in PO Window.

    • Approval Status is now a part of the PO's lifecycle.

      • It has been merged into PO Status. And changes as the PO progresses though its lifecycle.

      • The statuses are β€” New, Pending Approval, Approved, Rejected, Open, Received, Closed, AND Void.

    • People who have to approve the PO will receive individual E-mail notification.

      • This email informs them about required/pending action.

      • To support this a new set of E-mail templates have been introduced. We strongly recommend you to use these.

        • PO Approved Rule - PO Approved_V2

        • PO Rejected Rule - PO Rejected_V2

        • PO Approval Rule - PO Approval Request_V2

    • The 'Authorizer' field is now known as 'Approver'.

      • Since there can be multiple approvers, the column in PO search will show multiple approvers.

Caution

  • If you had the PO screen already customized even before upgrade, you will not be able to view the 'Approvals' tab in the PO screen.

  • To be able to see the 'Approvals' tab, you will need to reset the customizations on the screen by selecting 'Reset from Original’ in screen design mode.

Modifications to Data Conversion CSV payload:

If you plan to use 'Purchase Order Header' data conversion module to update changes to a PO, then you must ensure that the below mentioned field is removed from your CSV payload for 'Purchase Order Header' before it (the CSV file) is used.

Column Name

Data Type

Description

Default Value

Is Mandatory

Can be updated

Authorizer ID

Varchar2(21)

PO Authorizer Employee ID

NULL

No

Yes

CIDs introduced to support PO Approval workflow:

Description

CID#

Choice ID

Prints the Full Name of the final approver for a PO which is in Approved / Open / Received / Closed statuses.

547

Prints the Date on which PO is marked as Approved for a PO which is in Approved / Open / Received / Closed statuses.

548

Prints the Approval Status of the PO based (Mapped) on the PO status.

549

3410007

Mapping of Approval Status with PO Status

Approval Status

PO Status

New

New

Pending Approval

Pending Approval

Approved

Approved

Rejected

Rejected

Open

Approved

Received

Approved

Closed

Approved

Void

Void

Changes to generation of custom reports and column structure

Columns like 'Approved Status', 'Approved by', 'Approved on' and 'Authorizer' will be derived from the 'PO Approval levels' for the following listed Custom Reports

  1. REP_POHeaderView

  2. REP_PODetailView

  3. Rep_POHeaderAndVoucherInfoView

  4. Rep_SubRentalview

  5. Rep_POReceivelineview

  6. Rep_SellitemPOview

  7. Rep_unreceiptedpoview

  8. Rep_PoApprovalPolicyDetailView

Read more about the feature changes here:


  1. Availability Script (R2-20647)

    No R2 session must be active or live when the afore-mentioned GAS script is executed.

    As per the solution, the GAS program would delete the respective product’s Undoable actions table entry with whatever the option (All, Daily, Weekly).

  2. Delegates will receive reminder E-mails when their delegation tenure begins. (R2-19658)

Bug Fixes

  • SR-13643 β€” R2 is not allowing to fill assets from other sites.

  • SR-13722 β€” R2 displays error message 'Unable to validate license due to unknown error' when opening Service Module.

  • SR-13828 β€” R2 does not adjust the return date if the Order's Prep date is in future. i

  • SR-13895 β€” Vendor Filter does not defaults to checked when selecting vendor for a existing PO.

  • SR-14218 β€” Items tagged to an exchange group, do not get listed in BOLD, in Search Inventory window stock column.

  • SR-14516 β€” If the department name in the 'Main TO' is modified, the changes do not reflect in the 'Return TO'.

  • SR-14558 β€” R2 is not allowing to print pick-list, and system throws Oracle error, "Returned row count is more than expected count'.

Labor

Bug Fixes

  • SR-10156 β€” Total cost is displayed as incorrect after the 'Timesheet' was approved, if the pay policy was already defined.

  • SR-12844 β€” Removing the 'Description field column on planning order history, since it does not display any information.

  • SR-13725 β€” The resource does not receives the confirmation request E-mail, if the EWT for the resource is longer than 3 months.

  • SR-14428 β€” Alerts and messages sent by Planner, are not visible for the Crew.

  • SR-14465 β€” R2Labor is not able to load the modified TS and EWT Line details after changes to it were made and approved.

API

Improvements

  1. New PUT Items API introduced (R2-20661)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.