Sage 100

FYI / Heads up. v2014 standard PU4. Created an RMA, customer replacement. This should generate a sales order. Enter the RMA receipts and generate transactions. The journal shows ""Yes"" for Sales Order and Credit Memo. The credit memo gets created but the sales order does not. Works on my test system but not on the client. Determined the reason the sales order does not get created is because there is a UDF required field (Quote Request Date). reported this to Sage and engineering is currently looking at it. At a minimum I would want the journal to be changed to warn that the So is not being created because of a required UDF. A more elegant method would be to allow the sales order to be created with a default value. Holy smokes... Unable to use an RMA to create a sales order replacement if sales order has a required field.

Ummm You are working with the Blackhawk's on TV????

What's a Blackhawk?

Can it be defaulted, to at least get the order in?

@BrettLyder If it can I don;t know how to do it.

@JeffSchwenk Absolutely! Here come the Hawks, the mighty Blackhawks. Take the attack, yeah. and we'll back you Blackhawks.

I ran into the same situation a while back and ended up having to make the UDF not be required.

Sigh.....

$25 says you wait three weeks and when you call to inquire it's deemed WAD. Nobody will call you until you finally wind up calling them to check. At least that's how my cases seem to go.

Maybe the Wild will be there next year @ThereseLogeais .

I'd think you could script it to default to today's date or something like that on the pre-write.

Good idea. I wonder if it would make a difference. The PVX code could just test for the existence of a required UDF and then abort the write if true. Don;t really want to waste time writing a script for nothing unless, as Wayne suggests, Sage doesn't get back to me with a reasonable solution.

However, the PVX code may not even test for the required UDF but fail because the business object disallows the write when trying to create the new order.

I dealt with this in October 2012 and was told WAD

That figures.

I don't follow. Pvx code? I'm talking about writing a little BOI vbscript that sets the date udf to today if it's

Blank.

PVX is Providex. I mean the off the shelf code. What I mean is that there is a possibility the BOI script wouldn't help because the off the shelf code may test for the existence of a required UDF and if it is found then abort the creation of the sales order. Adding a script to default the required date wouldn't help. HOWEVER, most likely, the BOI script would work, particularly if the off the shelf (PVX) code fails because the business object disallows the sales order creation when a valid date is not found. Not sure spending the time to write the script and test this is worth it... I will wait a few days for Sage then give the client the options.

Gotcha. Sorry, I know what pvx means just didn't quite follow what you meant. I do a lot of scripting and would have to guess that it could be done. But I'd wait until I was sure it was necessary too.

Sorry @ThereseLogeais I can't help bragging a little. @JeffSchwenk

Congrats @DougHiggs and @JeffSchwenk ... Sigh.....

Doug, Can you assigned a ""coded"" default value to the UDF?

Thanks @MichelleTaylor I will try that tonight when everyone is out of the system and I can update the UDF. I am also going to try creating the same UDF in RMA Entry and passing the value through to the sales order during the generate process.