Hi, we currently use the Reference field in the orders to enter purchase order numbers. When we print the packing slips, it pulls the PO# from this field, which has always worked great. However, sometimes when we are rushed, we print a packing slip for an order and forget to check whether the PO# has been entered into the Reference field. You can imagine the frustration the customers experience when this happens.

I realize we can create alerts and reminders that pop-up when we open orders for certain customers, but is there a way to create an alert that pops up just before we print a packing slip? Better yet, is there a way that we could prevent printing of the packing slip for certain customers if the Reference field is blank?

We are using AR 8.1A(070920) and OE 8.1C(100208).

Thanks!

No, there is no such facility.

However, it would be fairly easy to create a GridView View that displayed Orders where this condition existed and have it displaying "live" on someone's desktop.

Cam:

We can provide you with this solution. PO# missing, then the packing (picking) slip would not print.

The problem would be that anything in that field would be accepted as a valid PO unless there was some way to validate the data. Validation would greatly increase the cost of this solution.

Hi Acrylon

You might want to consider using an Optional Text Field to key in the PO#s instead of the reference field. Optional fields can be validated to prevent blanks.

The PO# won't flow through to the customer's account, though. If you needed that, you would want to key it into both fields.

Steve

Steve:

To get the validation you describe, the PO numbers would need to be added to the validation table (as you cannot just type in random data into a validated optional field). This would quickly become unmanagable (too many PO's to choose from).

Hi Doug

I don't think you are correct. I set up an Optional Field with Finder Field selected and none of the Detail Options selected, and it let me type in and save anything I wanted in the field, but wouldn't let it remain blank.

Steve

Hi Guys,

I believe Steve is correct that an Optional Field can be validated in such a way that the only validation it checks for is that the field is non-blank, however, I'm not so sure that the Optional Field data could not flow through to the customer account - I think it can.

I know that Optional Field data can already flow between modules at some level but flowing at a transaction/detail level is more of an issue. I haven't tested this but I seem to remember that, while it has not made it to ALL modules yet, both OE and AR can have Optional Fields at a transaction level (OE Invoices and AR Batches) and if the Optional Fields in both modules are given the same name the data should flow across. Depending on where you need to see the info in AR you may need to customize the appropriate grid to show the appropriate optional field.

Give it a whirl and let us know how it works out. If you need assistance, I'm sure your Adagio consultant would be glad to help.

Interesting thread and a good demonstration of Adagio's flexibility - if it works out
If it doesn't, sorry to have misled you

Pete

PS: Last time I checked, OE's "Detail" Custom Fields were only at the invoice "header" level. I'm hoping that they will SOON make it to the invoice line item level as well with flow to Sales Analysis.

Steve:

You are correct, I didn't look at the combination of options that would allow this to happen.

Pete is also correct that with a matching optional field in AR the PO number would be passed to that field.

However (without testing so I may be wrong) the options fields are not available on the customer transaction drill down or the customer statement.

Hi Doug,

It is available on the customer's statement. Don't know about the drill down.

The optional fields are available through the Grid editor on the drill down.