E10 (9?) - Site Setup - Time Zone Offset - Arizona

I don't think it will fly with management to spend several thousand dollars on servers to avoid a simple manual change to a site's time zone offset.  The other suggestion for using Windows to track time changes sounds similar but we VPN from Phoenix to Minneapolis where the only servers are and the offset is built in to the site (plant) configuration relative to the server time.  We will go manual initially and later I might try to get fancy and put something on a schedule to poke a new value in the offset for the site automatically twice a year.
 
Thanks for the suggestions though.
 
-Todd C.
 


From: "mitchelljohn@... [vantage]" <vantage@yahoogroups.com>
To: vantage@yahoogroups.com
Sent: Monday, July 28, 2014 11:29:55 AM
Subject: [Vantage] Re: E10 (9?) - Site Setup - Time Zone Offset - Arizona

 

I actually just went over this with Epicor for a China subsidiary. Here is what I got back:


PAGE: 16384MPS

 

PROBLEM DESCRIPTION:

I have multiple AppServers and I need them for users in different countries in different time zones. How can I set the time zone for AppServers?

 

Using Central time zone only is not a solution as we are running Seattle sites and a China site.  It will cause a one day time difference especially on the transactions date, which would cause issues with any reporting as we can't grab data in a month range.

 

PROBLEM RESOLUTION:

 

At this time (as of Epicor 10.0.400.2) the approach would be the following:

                * one Windows server per time zone with the regional settings set appropriately for that time zone.

                * one Epicor IIS appserver on each of those servers pointing to the same Epicor database.

                * all users in that time zone need to have their clients point to the appserver in that time zone.

                * it is important to have all users for a specific company using the same time zone. (this is critical).


John


<!-- #ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mkp { border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mkp hr {
border:1px solid #d8d8d8;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mkp #ygrps-yiv-2133888615hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mkp #ygrps-yiv-2133888615ads {
margin-bottom:10px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mkp .ygrps-yiv-2133888615ad {
padding:0 0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mkp .ygrps-yiv-2133888615ad p {
margin:0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mkp .ygrps-yiv-2133888615ad a {
color:#0000ff;text-decoration:none;}
#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-sponsor #ygrps-yiv-2133888615ygrp-lc {
font-family:Arial;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-sponsor #ygrps-yiv-2133888615ygrp-lc #ygrps-yiv-2133888615hd {
margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-sponsor #ygrps-yiv-2133888615ygrp-lc .ygrps-yiv-2133888615ad {
margin-bottom:10px;padding:0 0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615actions {
font-family:Verdana;font-size:11px;padding:10px 0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615activity {
background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615activity span {
font-weight:700;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615activity span:first-child {
text-transform:uppercase;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615activity span a {
color:#5085b6;text-decoration:none;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615activity span span {
color:#ff7900;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615activity span .ygrps-yiv-2133888615underline {
text-decoration:underline;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615attach {
clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615attach div a {
text-decoration:none;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615attach img {
border:none;padding-right:5px;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615attach label {
display:block;margin-bottom:5px;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615attach label a {
text-decoration:none;}

#ygrps-yiv-2133888615 blockquote {
margin:0 0 0 4px;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615bold {
font-family:Arial;font-size:13px;font-weight:700;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615bold a {
text-decoration:none;}

#ygrps-yiv-2133888615 dd.ygrps-yiv-2133888615last p a {
font-family:Verdana;font-weight:700;}

#ygrps-yiv-2133888615 dd.ygrps-yiv-2133888615last p span {
margin-right:10px;font-family:Verdana;font-weight:700;}

#ygrps-yiv-2133888615 dd.ygrps-yiv-2133888615last p span.ygrps-yiv-2133888615yshortcuts {
margin-right:0;}

#ygrps-yiv-2133888615 div.ygrps-yiv-2133888615attach-table div div a {
text-decoration:none;}

#ygrps-yiv-2133888615 div.ygrps-yiv-2133888615attach-table {
width:400px;}

#ygrps-yiv-2133888615 div.ygrps-yiv-2133888615file-title a, #ygrps-yiv-2133888615 div.ygrps-yiv-2133888615file-title a:active, #ygrps-yiv-2133888615 div.ygrps-yiv-2133888615file-title a:hover, #ygrps-yiv-2133888615 div.ygrps-yiv-2133888615file-title a:visited {
text-decoration:none;}

#ygrps-yiv-2133888615 div.ygrps-yiv-2133888615photo-title a, #ygrps-yiv-2133888615 div.ygrps-yiv-2133888615photo-title a:active, #ygrps-yiv-2133888615 div.ygrps-yiv-2133888615photo-title a:hover, #ygrps-yiv-2133888615 div.ygrps-yiv-2133888615photo-title a:visited {
text-decoration:none;}

#ygrps-yiv-2133888615 div#ygrps-yiv-2133888615ygrp-mlmsg #ygrps-yiv-2133888615ygrp-msg p a span.ygrps-yiv-2133888615yshortcuts {
font-family:Verdana;font-size:10px;font-weight:normal;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615green {
color:#628c2a;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615MsoNormal {
margin:0 0 0 0;}

#ygrps-yiv-2133888615 o {
font-size:0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615photos div {
float:left;width:72px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615photos div div {
border:1px solid #666666;height:62px;overflow:hidden;width:62px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615photos div label {
color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615reco-category {
font-size:77%;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615reco-desc {
font-size:77%;}

#ygrps-yiv-2133888615 .ygrps-yiv-2133888615replbq {
margin:4px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-actbar div a:first-child {

margin-right:2px;padding-right:5px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mlmsg {
font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mlmsg table {
font-size:inherit;font:100%;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mlmsg select, #ygrps-yiv-2133888615 input, #ygrps-yiv-2133888615 textarea {
font:99% Arial, Helvetica, clean, sans-serif;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mlmsg pre, #ygrps-yiv-2133888615 code {
font:115% monospace;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mlmsg * {
line-height:1.22em;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-mlmsg #ygrps-yiv-2133888615logo {
padding-bottom:10px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-msg p a {
font-family:Verdana;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-msg p#ygrps-yiv-2133888615attach-count span {
color:#1E66AE;font-weight:700;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-reco #ygrps-yiv-2133888615reco-head {
color:#ff7900;font-weight:700;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-reco {
margin-bottom:20px;padding:0px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-sponsor #ygrps-yiv-2133888615ov li a {
font-size:130%;text-decoration:none;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-sponsor #ygrps-yiv-2133888615ov li {
font-size:77%;list-style-type:square;padding:6px 0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-sponsor #ygrps-yiv-2133888615ov ul {
margin:0;padding:0 0 0 8px;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-text {
font-family:Georgia;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-text p {
margin:0 0 1em 0;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-text tt {
font-size:120%;}

#ygrps-yiv-2133888615 #ygrps-yiv-2133888615ygrp-vital ul li:last-child {
border-right:none !important;
}
–>


I’ve been reading through the E10 implementation guide and noticed there is a time zone offset setting from the server.  We have a plant in Phoenix that will need to be addressed.  They stay on Mountain Standard Time all year so part of the year (standard time) one hour different from Central time and in Summer two hours.

 

Is this a setting I can deal with on a schedule, programmatically, or must it be manually adjusted twice a year?  If it is automatic is there a routine floating around to do this?

 

Thanks,

-Todd C.

 

I would assume that it uses the Standard Windows Time Zones as options, no? Arizona has it’s own special setting in Windows time settings, shouldn’t the same thing exist in E10 since it’s using the standard MS pieces?

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Sunday, July 27, 2014 10:51 PM
To: vantage@yahoogroups.com
Subject: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona

 




I’ve been reading through the E10 implementation guide and noticed there is a time zone offset setting from the server.  We have a plant in Phoenix that will need to be addressed.  They stay on Mountain Standard Time all year so part of the year (standard time) one hour different from Central time and in Summer two hours.

 

Is this a setting I can deal with on a schedule, programmatically, or must it be manually adjusted twice a year?  If it is automatic is there a routine floating around to do this?

 

Thanks,

-Todd C.

 




<html
#ygrps-yiv-270334436 .ygrps-yiv-270334436ygrp-photo-title { TEXT-ALIGN:center;WIDTH:75px;HEIGHT:15px;CLEAR:both;FONT-SIZE:smaller;OVERFLOW:hidden;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436ygrp-photo { BORDER-BOTTOM:black 1px solid;BORDER-LEFT:black 1px solid;BACKGROUND-COLOR:white;WIDTH:62px;BACKGROUND-REPEAT:no-repeat;BACKGROUND-POSITION:center 50%;HEIGHT:62px;BORDER-TOP:black 1px solid;BORDER-RIGHT:black 1px solid;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436photo-title A { TEXT-DECORATION:none;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436photo-title A:active { TEXT-DECORATION:none;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436photo-title A:hover { TEXT-DECORATION:none;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436photo-title A:visited { TEXT-DECORATION:none;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436attach-table DIV.ygrps-yiv-270334436attach-row { CLEAR:both;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436attach-table DIV.ygrps-yiv-270334436attach-row DIV { FLOAT:left;} #ygrps-yiv-270334436 P { PADDING-BOTTOM:3px;PADDING-LEFT:0px;PADDING-RIGHT:0px;CLEAR:both;OVERFLOW:hidden;PADDING-TOP:15px;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436ygrp-file { WIDTH:30px;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436attach-table DIV.ygrps-yiv-270334436attach-row DIV DIV A { TEXT-DECORATION:none;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436attach-table DIV.ygrps-yiv-270334436attach-row DIV DIV SPAN { FONT-WEIGHT:normal;} #ygrps-yiv-270334436 DIV.ygrps-yiv-270334436ygrp-file-title { FONT-WEIGHT:bold;}
I believe you have to set this manually every time there's a change between the server's time zone and the plant. For example, Germany uses a different Daylight Time Schedule than Pacific Time where our server is located. So we have to adjust the normal 9 hour difference +/-1 twice a year in the Plant Configuration Control.
 
----- Original Message -----
Sent: Monday, July 28, 2014 6:23 AM
Subject: RE: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona

I would assume that it uses the Standard Windows Time Zones as options, no? Arizona has itÂ’s own special setting in Windows time settings, shouldnÂ’t the same thing exist in E10 since itÂ’s using the standard MS pieces?  

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Sunday, July 27, 2014 10:51 PM
To: vantage@yahoogroups.com
Subject: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona

IÂ’ve been reading through the E10 implementation guide and noticed there is a time zone offset setting from the server.  We have a plant in Phoenix that will need to be addressed.  They stay on Mountain Standard Time all year so part of the year (standard time) one hour different from Central time and in Summer two hours.

Is this a setting I can deal with on a schedule, programmatically, or must it be manually adjusted twice a year?  If it is automatic is there a routine floating around to do this?

Thanks, -Todd C.

<html
#ygrps-yiv-423189668 .ygrps-yiv-423189668ygrp-photo-title { TEXT-ALIGN:center;WIDTH:75px;HEIGHT:15px;CLEAR:both;FONT-SIZE:smaller;OVERFLOW:hidden;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668ygrp-photo { BORDER-BOTTOM:black 1px solid;BORDER-LEFT:black 1px solid;BACKGROUND-COLOR:white;WIDTH:62px;BACKGROUND-REPEAT:no-repeat;BACKGROUND-POSITION:center 50%;HEIGHT:62px;BORDER-TOP:black 1px solid;BORDER-RIGHT:black 1px solid;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668photo-title A { TEXT-DECORATION:none;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668photo-title A:active { TEXT-DECORATION:none;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668photo-title A:hover { TEXT-DECORATION:none;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668photo-title A:visited { TEXT-DECORATION:none;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668attach-table DIV.ygrps-yiv-423189668attach-row { CLEAR:both;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668attach-table DIV.ygrps-yiv-423189668attach-row DIV { FLOAT:left;} #ygrps-yiv-423189668 P { PADDING-BOTTOM:3px;PADDING-LEFT:0px;PADDING-RIGHT:0px;CLEAR:both;OVERFLOW:hidden;PADDING-TOP:15px;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668ygrp-file { WIDTH:30px;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668attach-table DIV.ygrps-yiv-423189668attach-row DIV DIV A { TEXT-DECORATION:none;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668attach-table DIV.ygrps-yiv-423189668attach-row DIV DIV SPAN { FONT-WEIGHT:normal;} #ygrps-yiv-423189668 DIV.ygrps-yiv-423189668ygrp-file-title { FONT-WEIGHT:bold;}
Oops. Meant 4 times a year. When they get off then back on in both the spring and fall.
----- Original Message -----
Sent: Monday, July 28, 2014 7:20 AM
Subject: Re: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona

I believe you have to set this manually every time there's a change between the server's time zone and the plant. For example, Germany uses a different Daylight Time Schedule than Pacific Time where our server is located. So we have to adjust the normal 9 hour difference +/-1 twice a year in the Plant Configuration Control.
 
----- Original Message -----
Sent: Monday, July 28, 2014 6:23 AM
Subject: RE: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona

I would assume that it uses the Standard Windows Time Zones as options, no? Arizona has itÂ’s own special setting in Windows time settings, shouldnÂ’t the same thing exist in E10 since itÂ’s using the standard MS pieces?  

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Sunday, July 27, 2014 10:51 PM
To: vantage@yahoogroups.com
Subject: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona

IÂ’ve been reading through the E10 implementation guide and noticed there is a time zone offset setting from the server.  We have a plant in Phoenix that will need to be addressed.  They stay on Mountain Standard Time all year so part of the year (standard time) one hour different from Central time and in Summer two hours.

Is this a setting I can deal with on a schedule, programmatically, or must it be manually adjusted twice a year?  If it is automatic is there a routine floating around to do this?

Thanks, -Todd C.

Use the Arizona time setting as Ned suggested - that is what we use.



Mountain Time goes on daylight savings.





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Monday, July 28, 2014 6:24 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona





I would assume that it uses the Standard Windows Time Zones as options, no?
Arizona has it's own special setting in Windows time settings, shouldn't the
same thing exist in E10 since it's using the standard MS pieces?



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Sunday, July 27, 2014 10:51 PM
To: vantage@yahoogroups.com
Subject: [Vantage] E10 (9?) - Site Setup - Time Zone Offset - Arizona









I've been reading through the E10 implementation guide and noticed there is
a time zone offset setting from the server. We have a plant in Phoenix that
will need to be addressed. They stay on Mountain Standard Time all year so
part of the year (standard time) one hour different from Central time and in
Summer two hours.



Is this a setting I can deal with on a schedule, programmatically, or must
it be manually adjusted twice a year? If it is automatic is there a routine
floating around to do this?



Thanks,

-Todd C.













[Non-text portions of this message have been removed]
I actually just went over this with Epicor for a China subsidiary. Here is what I got back:

PAGE: 16384MPS

 

PROBLEM DESCRIPTION:

I have multiple AppServers and I need them for users in different countries in different time zones. How can I set the time zone for AppServers?

 

Using Central time zone only is not a solution as we are running Seattle sites and a China site.  It will cause a one day time difference especially on the transactions date, which would cause issues with any reporting as we can't grab data in a month range.

 

PROBLEM RESOLUTION:

 

At this time (as of Epicor 10.0.400.2) the approach would be the following:

                * one Windows server per time zone with the regional settings set appropriately for that time zone.

                * one Epicor IIS appserver on each of those servers pointing to the same Epicor database.

                * all users in that time zone need to have their clients point to the appserver in that time zone.

                * it is important to have all users for a specific company using the same time zone. (this is critical).


John