For plant my client is requesting that 26 December 2014 be marked as a non working day. The plant is all taking this day as one of their floating holidays and need it considered as non work day in factory calendar to extend their Christmas break.
Is there any impact if we do this for other module etc.,,what would be best way if we do through open client or landscape.
I believe that any changes to Public Holidays, Holiday Calendars and Factory Calendars should be done in your development environment (DEV), and a Workbench Transport will enable you to bring the changes to your quality & test environment (QAT) and eventually to your production environment (PRD).
Note that there are many discussion threads on Calendars available on this site and elsewhere on the web.
While I try to create a workbench request it shows the target system deletes the Holiday calendar.Factory Calendar etc.,after moving the TR it deletes the initial and overwrites ?
when I try to check for transport conflict analysis it takes production logon which never happens before.
Also here I have made the changes for Factory calendar alone in special rule,whereas no changes to holiday calendar,for this case is it require to run the work schedule rule.
Wether a change was made to a Public Holiday, to a Holiday Calendar or to a Factory Calendar, the transport will pick up the content of all related tables and overwrite what was in the QAT and PRD environments.
I do the process a few times each year since we have many Holiday Calendars, and I have never had any problems.
If it is the first time for you to transport the "Calendars", perhaps you should first do a Table Compare (t-code scmp) between DEV and PRD of all the tables that are included in the transport.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.