Which R.O. Is Each P.O. For?

[timbre4]

Got a call from a rep about a new customer concern that he needs to know which repair orders each of his P.O.s is for. I suggested that if ordering electronically, the R.O. # is included in the data we transmit to the vendor during parts ordering. Depending on vendor, the Ref/Inv# data is referenced on the parts invoice.

Manual P.O.s would rely on Ref/Inv# data for lookups. I further suggested the shop write the R.O. # on the parts invoice if it is not otherwise visible.

Seems like a workflow issue to me; any thoughts on this?

[timsince]

I think the RO number should be visible on the PO if ordered electronically. If it is automatically transmitted to the vendor, why not just make a spot for it to be visible to the user when reviewing open POs after ordering?

[timbre4]

I think the RO number should be visible on the PO if ordered electronically. If it is automatically transmitted to the vendor, why not just make a spot for it to be visible to the user when reviewing open POs after ordering?

It's probably Closed P.O.s since the shop would process it by receiving parts and closing it.
In any event, the R.O. # is visible in the blue title bar the entire time:

PO RO.png (19.69 KiB) Viewed 7453 times

I'm just trying to sort out why they think a report is necessary.

[MURRI513]

I think the RO number should be visible on the PO if ordered electronically. If it is automatically transmitted to the vendor, why not just make a spot for it to be visible to the user when reviewing open POs after ordering?

It's probably Closed P.O.s since the shop would process it by receiving parts and closing it.
In any event, the R.O. # is visible in the blue title bar the entire time:

PO RO.png

I'm just trying to sort out why they think a report is necessary.

I write all PO manually & in the comments section I write customer name and RO # associated with it. It not only prints at the bottom of PO it is retained in that section forever. That way if there is a question of who the part was for its right at our fingertips.

[Gerald Martin]

It would sure be helpful the the PO list would have RO numbers visible without opening each one...

[Rich]

It would sure be helpful the the PO list would have RO numbers visible without opening each one...

I was thinking a "name" column would be great.

[ricmorin]

I'm wondering if a ref field column would be generically helpful?

ref_column.png (17.06 KiB) Viewed 7368 times

That way users can easily use the existing field, but now can see it from the PO main window.

[Rich]

That would work PERFECT for us, we'd only have to enter info once.

[Gerald Martin]

Good ideas! What if the system would auto-populate that field with the RO number unless the user typed in something else, such as vehicle or customer details?

[Silky7]

I've noted this as an enhancement request.

[ambertsi]

If you open an RO and start a PO through the open order from the pick list for the RO, the RO will appear on the PO. If you order electronically via an open RO, the RO number will show on the PO as well.

I also agree that having the RO/Reference # on the main PO screen would be very helpful as well as having a field dedicated to the RO specifically within the PO. Currently, if you add something to the field for the invoice number/reference number within a PO, it populates on the reports as the vendor invoice number, even if you're referencing an RO number.

Within reports, I can't even find where the RO number, even when present on the title bar of the PO, is even listed. This has been an ongoing issue with us since we've started using Mitchell. The only workaround we have is to include the RO and vendor invoice number in the reference field of the PO. Even that is a pain because it doesn't allow you to sort efficiently if both of the numbers aren't listed in the exact same format on each PO.