Add department entity to Purchase Order Approval workflow

​@Leahth 

Could you not use Employee.DepartmentID instead? 

Alternatively, add a data view for the Department as is in RQRequestEntry:

[PXViewName(RQ.Messages.Department)]
public PXSetup<EPDepartment, Where<EPDepartment.departmentID, Equal<Optional<RQRequest.departmentID>>>> depa;

For the new field, you would add it as normal (through Screen Editor or code) and add the PXDefault as so:

[PXDefault(typeof(EPEmployee.DepartmentID))]

//Or with FieldUpdated on PO Owner (OwnerID)

protected virtual void _(Events.FieldUpdated<POOrder, POOrder.OwnerID> e, PXFieldUpdated b)
{
    b?.Invoke(e.Cache, e.Args);
    POOrder row = e.Row;
    if (row == null)
        return;

    if (row.OwnerID == null)
        return;

    EPEmployee employee = SelectFrom<EPEmployee>.
        Where<EPEmployee.defContactID.IsEqual<P.AsInt>>.View.Select(Base, row.OwnerID);
    if (employee == null)
        return;

    e.Cache.SetValueExt<YourPOOrderExt.usrDepartmentID>(row, employee.DepartmentID);
}

Hello,

I agree with Aleks:  I have routed many POs for approval using Entity = Employee and Field Name = Department. 

In Configurations, Employees… Departments will need to be accurate on Employees, for the above routing to work. (I have also used Subaccount to route PO’s by line to Department heads, when Subaccounts represent Departments of a Company.)

Also, Each PO will need accurate Owners representing the persons who requested the items, not the person who types in the Purchase Orders:

Hello,

I agree with Aleks:  I have routed many POs for approval using Entity = Employee and Field Name = Department. 

In Configurations, Employees… Departments will need to be accurate on Employees, for the above routing to work. (I have also used Subaccount to route PO’s by line to Department heads, when Subaccounts represent Departments of a Company.)

Also, Each PO will need accurate Owners representing the persons who requested the items, not the person who types in the Purchase Orders:

 

Apologies I should have included the detail that we already explored employee / department but the issue is that sometimes a user creates POs for various departments that are not their own

[PXViewName(RQ.Messages.Department)]
public PXSetup<EPDepartment, Where<EPDepartment.departmentID, Equal<Optional<RQRequest.departmentID>>>> depa;

[PXDefault(typeof(EPEmployee.DepartmentID))]

//Or with FieldUpdated on PO Owner (OwnerID)

protected virtual void _(Events.FieldUpdated<POOrder, POOrder.OwnerID> e, PXFieldUpdated b)
{
    b?.Invoke(e.Cache, e.Args);
    POOrder row = e.Row;
    if (row == null)
        return;

    if (row.OwnerID == null)
        return;

    EPEmployee employee = SelectFrom<EPEmployee>.
        Where<EPEmployee.defContactID.IsEqual<P.AsInt>>.View.Select(Base, row.OwnerID);
    if (employee == null)
        return;

    e.Cache.SetValueExt<YourPOOrderExt.usrDepartmentID>(row, employee.DepartmentID);
}

Thank you. Can you see a way for this to work where a user can select a different department from their own?

We are thinking for it to default to the employee’s own department but they can select a different one, as sometimes a employee creates POs on behalf of other departments.

We would want the same option on a purchase order as currently on requests:

Hello,

Employee who enters POs may simply enter the  Owner for the PO  = person who is requesting the merchandise, or person in the Department who is requesting the merchandise. 

Then routing POs will work without effort or customization.

Laura