Follow us on Facebook Follow us on Twitter Get the latest job postings quicker!
Follow us on Facebook and Twitter!
Sponsors

Like this Page? Share it!
HomeHomeManhattan Assoc...Manhattan Assoc...GeneralGeneralHow to reference the E_CRIT_MSG_LOG table in an LM free-form text UOM condition?How to reference the E_CRIT_MSG_LOG table in an LM free-form text UOM condition?
Previous
 
Next
New Post
5/16/2017 5:49 AM
 

Hi,

 

In our LM configuration, we do all our UOM conditions using the free-form text field. To reference the E_HDR_MSG_LOG table, we use the prefix HDR; for the E_DTL_MSG_LOG table, it's DTL. We've recently implemented some configuration that requires referencing the E_CRIT_MSG_LOG table, and following the same convention used for the other two tables, we assumed that we'd reference it using the prefix CRIT. Unfortunately, no such luck. We've also tried CRT, but that didn't work either. What we'd like to do is something like this for each detail line that comes through in the message:

(CRIT.CRIT_TYPE = 'CARTON_TYPE' AND CRIT.CRIT_VAL = 'TOT')

We must be missing something, but so far we've had no luck figuring out what it is. Is there maybe some config somewhere that tells the system to use "HDR" and "DTL"? Maybe we're missing something that tells it to use "CRIT"?

 

 

Thanks.

 

 
New Post
5/16/2017 8:42 PM
 

Hi John,

From what I know, these tables and their aliases of 'HDR' and 'DTL' are in the code - Pretty stupid if you ask me.

To get around this we create functions to return the desired data from required new tables and link the hardcoded 'HDR' or 'DTL' to retrieve the correct values. e.g.

FN_GET_xx(HDR.TRAN_NBR, HDR.WHSE) = 'xx' AND HDR.TRAN_NBR > 0 AND DTL.TRAN_NBR IS NOT NULL

I've obviously masked some of the name/values there, but that's a way around it if you want to give that a try.

Cheers

Dan

 
New Post
5/17/2017 8:38 AM
 

Yes, I agree that it's pretty stupid to have HDR and DTL hard coded, especially since many other things are configurable. That's why I thought there must be a system code where we can adjust that if we wanted to, but I haven't been able to find one. We used to have a customer function referenced in one of our UOM calculations, but had to remove it because it was causing a full table scan every time it was called, which was making the messages take sometimes hours to transfer from WM to LM. I'm assuming it was someone within my company who wrote the function though, so admittedly that's not Manhattan's fault. It was just a poorly written function. I didn't write it. :)

We think we figured out how to reference the criteria, but it is absolutely NOT intuitive. We had it set up within WMS to add the string "CARTON_TYPE" to the WORKINFO_Q_DTL_015 (or 016) table in the CRIT_TYPE field, and the actual carton type in the CRIT_VAL field, but there's some config within LM to do as well. We found the Criteria Maintenance screen in LM, and added CARTON_TYPE as a criteria code. That seemed to create a temporary table T_TEMP_159241, with five fields - ELS_TRAN_ID, TRAN_NBR, TRAN_SEQ_NBR, CARTON_TYPE, and TESTCRIT. It was the TESTCRIT thing that originally put us onto this idea, because we knew we had come across that somewhere before. Once we had that, we were able to do this in our UOM's free-form text field:

(CRT.CARTON_TYPE = 'TOT')

So far, it seems to be working, but we noticed that there's 45 tables named something like T_TEMP_000000, each with a different number at the end. I don't know how the system knows which one of those to reference, and I don't know why it doesn't clean up the obsolete ones when new criteria is added. 

 
Previous
 
Next
HomeHomeManhattan Assoc...Manhattan Assoc...GeneralGeneralHow to reference the E_CRIT_MSG_LOG table in an LM free-form text UOM condition?How to reference the E_CRIT_MSG_LOG table in an LM free-form text UOM condition?


Copyright 2010-2011 by WMS Support Forum   |  Privacy Statement  |  Terms Of Use