Updating OrderRel.ReqDate

You should double check and make sure that when you manually change the ReqDate, check all the tables that get updated at the same time.

 

I remember doing this once and I believe there was a difference between the Sales Order date and the PartDtl date which is used by MRP.

 

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of gracefulthreads@...
Sent: Tuesday, March 25, 2014 12:48 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Updating OrderRel.ReqDate

 

 

Solved my own problem... since this was on pre-process, the other BPM (a data directive on OrderRel) was firing to blank the dates. I put a CallContextClient.ProcessID on the data directive and all is now well.

 

Thanks for listening,

 

Ernie Lowell

Diba Industries


I'm trying to update OrderRel.ReqDate in a method BPM called from CreditManager.UpdateCMOrderHed. The BPM fires, I can get messages and even change other fields, but the ReqDate (and also the NeedByDate) fields will not update.


I know it's reaching the OrderRel table because I can InfoMsg out other fields, and when using updatetablebuffer I can change the field OrderRel.Reference.


All I can figure is that there is some other flag/trigger inhibiting the update of dates.


Our subsidiary in the UK has a large number of prepay only customers, so I'd like to set them all up on Credit Hold. I already have a BPM in place and working that blanks the Need By and Ship By dates on the order release, so they don't generate job and PO suggestions in MRP (which runs every night). My goal is when they UN-check the "credit hold" box on the order in Credit Manager upon payment receipt, the system can take the Need By and Ship by dates from either OrderHed or OrderDtl (the OrderHed values are actually pulled into ttCMOrderHed) and automagically update OrderRel.


Any ideas?


Ernie Lowell

Diba Industries

Solved my own problem... since this was on pre-process, the other BPM (a data directive on OrderRel) was firing to blank the dates. I put a CallContextClient.ProcessID on the data directive and all is now well.


Thanks for listening,


Ernie Lowell

Diba Industries