Configurator and Order Entry

pfd

Reputable Poster
We use the vanilla JDE Configurator during the sales order entry process and our users have made a request, that they should be able to see the configurator string, as an additional column in the order entry screen. At the time of order entry this string is in cache. So my question is has any of you attempted to retrieve the configured string and display it on on the order entry screen as the order is being entered. After the order is entered the configured string does get stored in F32943.

Thanks,
Matt

One World Xe,SP23_U1,AS/400 v5r3
 

Remo Williams

VIP Member
matt, in W32942A this is pretty easy to do: check out the call to Cache Process All Components under the Calc button. u can get the CFGSID by simply mapping the CFGSID output parameter in that call. the problem with calling that same function in W4210A (right after returning from W32942A), is that u don't have all the cache keys available: as far as i can see, mnConfigurationIDNumber is determined in W32942A. one way to solve this would be to add CFGSID to the form data structure of W32942A, and use it to return the CFGSID value to W4210A.

hoewever, to avoid having to modify the Form Data Structure of a standard JDE object, I just tested a different solution, which also seems to work:

1. in W4210A, in the Form Interconnect to W32942A (which can be found in BUTTON Kit and Configurator processing [HIDDEN]), map FI mnConfigurationIDNumber to a new variable so that the missing cache key mnConfigurationIDNumber becomes available in W4210A;
2. right after the Form Interconnect, call Cache Process All Components to get the CFGSID, and map it to new gridcolumn CFGSID.

here's the code:


Call( App:p32942 , Form: W32942A )
(. . .)
VA evt_TEST_CFGID <- FI mnConfigurationIDNumber
(. . .)

Cache Process All Components
"1" -> BF cCacheActionCode
"1" -> BF nIndexNumber
"1" -> BF nNumberOfKeys
FI Jobnumber -> BF mnJobNumber
VA evt_TEST_CFGID -> BF mnConfigurationIDNumber
GC UniqueConfiguration ID <- BF szUniqueConfigurationID

hope this helps.
 
matt, in W32942A this is pretty easy to do: check out the call to Cache Process All Components under the Calc button. u can get the CFGSID by simply mapping the CFGSID output parameter in that call. the problem with calling that same function in W4210A (right after returning from W32942A), is that u don't have all the cache keys available: as far as i can see, mnConfigurationIDNumber is determined in W32942A. one way to solve this would be to add CFGSID to the form data structure of W32942A, and use it to return the CFGSID value to W4210A.

hoewever, to avoid having to modify the Form Data Structure of a standard JDE object, I just tested a different solution, which also seems to work:

1. in W4210A, in the Form Interconnect to W32942A (which can be found in BUTTON Kit and Configurator processing [HIDDEN]), map FI mnConfigurationIDNumber to a new variable so that the missing cache key mnConfigurationIDNumber becomes available in W4210A;
2. right after the Form Interconnect, call Cache Process All Components to get the CFGSID, and map it to new gridcolumn CFGSID.

here's the code:


Call( App:p32942 , Form: W32942A )
(. . .)
VA evt_TEST_CFGID <- FI mnConfigurationIDNumber
(. . .)

Cache Process All Components
"1" -> BF cCacheActionCode
"1" -> BF nIndexNumber
"1" -> BF nNumberOfKeys
FI Jobnumber -> BF mnJobNumber
VA evt_TEST_CFGID -> BF mnConfigurationIDNumber
GC UniqueConfiguration ID <- BF szUniqueConfigurationID

hope this helps.
Hey buddy.... Any way I can contact you directly? I'm a tech consultant working on a DOD account and have a question about CFGSID that I think is right down your alley.... [email protected]
 
Call Orchestrations From Excel – The Easy Way to Make the Orchestrator Work for You.
Top