ER CTMS 040-008: Difference between revisions
From Calidus HUB
(Created page with "<!-- MEDIA LANDSCAPE YES --> {{#vardefine:System|CTMS}} {{ERHeader |SystemVersion=CTMS 11.0 |ERNumber=ER040-008 }} {| class="wikitable" border="1" width="100%" |- bgcolor="sil...") |
m (Text replacement - "[[Category:{{#var:System}} ER]]↵</noinclude>" to "[[Category:{{#var:System}} ER]]Category:ER CTMS 040 </noinclude>") |
||
| Line 37: | Line 37: | ||
<noinclude> | <noinclude> | ||
[[Category:{{#var:System}} ER]] | [[Category:{{#var:System}} ER]][[Category:ER CTMS 040]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 09:57, 14 July 2025
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER040-008
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
|---|---|---|---|---|---|---|
| TRIPSUM.fmx | TRIPSUM Oracle Form | 2.447 | 246967 | - | 3 | The Three forms TRIPSUM, TRIP_PLAN, and PLANNING are modified, so that the trip stops will be found for the matching Load and Unload locations and the planned times for the stops and the orders. Any empty stops then will be assessed and used only when they match the planned times, the functionality depends on this system parameter 'UPDATE_ORDERS_TO_TRIP' set to 'Y' for customer. |
| TRIP_PLAN.fmx | TRIP_PLAN Oracle Form | 1.281 | " | " | " | " |
| PLANNING.fmx | PLANNING Oracle Form | 1.121 | " | " | " | " |
