Calendar Modification and Transport From Development To Production Environment

Calendar Modification and
Selective Transport from SAP

Development to Production
Environment
Applies to:
This document is applicable to all SAP implementations where Plant Calendars are involved in Planning and
Execution.
Summary
This paper describes the process on how to add, update particular parameters of individual SAP Plant
Calendar/s in development environment and custom transport those changes to the production environment
with-out affecting rest of the calendars.
Author: Digambar Narkhede

Company: Infosys Technologies Limited
th
Created on: 09 July 2012
Author Bio
Digambar is a Supply Chain Management Consultant working with Infosys Limited.

With core competency in Advanced Planning, he has expertise in developing and
managing solutions for various types of industry verticals around SAP R/3 and APO
module for various versions.
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 1
Calendar Modification and Selective Transport from SAP Development to Production Environment
Table of Contents
Definitions: SAP Plant and Calendars ............................................................................................................ 3

SAP Calendar Structure .................................................................................................................................. 3
Transport to next SAP Installations ................................................................................................................. 4
Current Limitation and Rationale for Custom Transport Process ................................................................... 4
Few Scenarios for Calendar Change .............................................................................................................. 5
Custom Solution for restricted change Transport ........................................................................................... 5
a. Modify or Edit Holidays / Calendars - Use Transaction Code: SCAL .................................................... 6
b. Create a Transport Request from the SAP Calendar Main Menu ......................................................... 9
c. Edit / Modify the Transport Request to contain restricted changes ..................................................... 10
d. Release the Transport Request to next / productive environment ...................................................... 15
© 2010 SAP AG 2
Definitions: SAP Plant and Calendars
SAP Plant is one of the most important organizational units in Enterprise Structure of a business which
produces a material or provides services. The working schedule of this organizational unit is setup in the
Calendars.
Calendars are used in many functions of business like Planning, Logistics and in Human Resources etc.
Calendars specify working & non-working days.

• Non-working days can be: Civic or religious holidays any other non-working days unique to a
company
• Several calendars could apply to a single company, since non-working days often vary by region,
state/province and country
• Special holidays are required for specific period and are not through-out the validity of Calendar.
• Some customers may require invoices to be processed periodically, so that all deliveries due for
billing by a certain time are put into one collective invoice
• Modifications are most of the times required due to legal changes, wrong customizing or due to
some special rules requirement in a business etc.
• Public holiday calendars become customer responsibility after first installation.
SAP Calendar Structure
The calendar system consists of the following components:
© 2010 SAP AG 3
 Public holidays
Definitions for public holidays: Calculation rule for date, religious denomination etc.
 Public holiday calendar

Any composition of public holiday rules.
 Factory calendar
Definition of workdays including special regulations, under the assignment of a particular public
holiday calendar.
These Factory calendars are then assigned to SAP plants that provide them the schedules for different
activities in planning and execution.
Transport to next SAP Installations
SAP transports are used to implement some new features in a production system.
This whole process is divided into several phases:
1. A development and a testing installation is created using backups from the production system
2. The new features are implemented into the development installation
3. This is imported into the testing (or quality assurance) installation using a transport
4. After the new features are thoroughly tested, it is imported into the production system using another
transport
For the calendar data to be utilizable in another testing / client productive system, use the function Transport
in the initial screen of the maintenance transaction.
Current Limitation and Rationale for Custom Transport Process
You can only transport the factory/public holiday calendar as a whole. Transporting individual public holidays
or calendars is not supported.
Since a production system (especially a business-dependent one) cannot be used for development (and
testing), Direct changes in the production systems are not recommended. The factory/public holiday calendar
should be maintained and changed in a separate development/testing installation or Customizing
client/system. It can then be transported to next / productive environments.
Specific changes to calendar data are not automatically included in a correction request. So you
cannot transport individual public holidays or calendars in a standard process. You can only
transport calendar data in its entirety.
When you do this, all public holidays, public holiday and factory calendars existing in the target
system are deleted and in case if there are any mismatches between source and target systems the
risk involved would be high on target system with transporting all the changes which are not
unwanted in destinations systems.
So with this custom process we are going to modify the Transport Request which originally includes changes
related to all the calendars. It is modified in such a way that it only contains restricted changes for transport.
© 2010 SAP AG 4
Few Scenarios for Calendar Change
Calendar Changes and transport could be of following types:
1. Addition of new Public holiday / Holiday Calendar / Factory calendar

2. Modify definition of existing Public holiday / Holiday Calendar / Factory calendar which could be
 Definition of a new date for a movable holiday
 Assignment of a new public holiday to Holiday calendar or delete the existing assignment
 Change validity period of Holiday calendar & Factory calendar
 Assign new holiday calendar to factory calendar or delete the existing assignment
 Define special rules of working non-working days in a week for factory calendar
Custom Solution for restricted change Transport
Following steps are involved in the whole process.
 Modify or Edit Holidays / Calendars - Use Transaction Code: SCAL
 Create a Transport Request from the SAP Calendar Main Menu
 Edit / Modify the Transport Request to contain restricted changes
 Release the Transport request to next / productive environment
Let`s see these steps in details:
Case: Define special rules for additional non-working days in a week for existing Factory calendar
A Factory calendar is already available with set of Holidays which are grouped in a Holiday Calendar but
there is a need to have additional Holidays over and above those in Holiday Calendar for specific year of the
plant Calendar, so need to define additional holidays in Holidays list with Special Rules.
© 2010 SAP AG 5
a. Modify or Edit Holidays / Calendars - Use Transaction Code: SCAL
Factory Calendar with regular Holiday Calendar attached
© 2010 SAP AG 6
Factory Calendar Initial Screen: Predefined Holiday Calendar attached and Special Rule Option
Assign special rules to the Factory Calendar :Special rule could be range of Holidays or any particular day
© 2010 SAP AG 7
Factory Calendar with these additional holidays defined in Special Rules can be seen as below
Additional Holidays
as defined in
Special Rule
On the similar background there could be different type of changes possible and will be carried out in the
similar way for Holidays, Holiday Calendar and Factory Calendar.
© 2010 SAP AG 8
b. Create a Transport Request from the SAP Calendar Main Menu

Once the changes are ready in the development system, need to transport them to next systems in transport
route like quality and then production installations.
Icon to start
Transport
Warning
Message
So irrespective of the changes done, all Public Holidays, Holiday Calendars & Factory Calendars will be
deleted from the destination SAP system and then new set will be transported from Development system.
To avoid this we should edit the Transport Request such that only specific changes are transported to next
system
© 2010 SAP AG 9
c. Edit / Modify the Transport Request to contain restricted changes

Transaction Code: SE01
Go to Transport organizer and get the selection for your Transport Requests
Select the respective Modifiable TR
Request Nos.
List Of Tables
© 2010 SAP AG 10
Goto Change mode of a Transport request
To delete a Table, select the particular row & click on ‘Delete row’. Delete TCALS row.
Make changes to each & every applicable row. Different table contain different data related to Holiday or
Holiday Calendar or Factory Calendar and each table key is different for different table.
Relevance of Tables with the Calendar objects:
1. TCALS - Central entry for factory Calendar
Tables carrying Factory calendar related data
2. TFACD - Factory calendar definition

3. TFACS - Factory calendar display (days/months)
4. TFACT - Factory calendar texts
© 2010 SAP AG 11
5. TFAIN - Calendar: Intervals for company holidays, special shifts

6. TFAIT - Calendar: Text for factory calendar intervals
Tables carrying Holiday calendar related data
7. THOC - Public Holiday Calendar IDs

8. THOCD - Public holiday definitions / Public holiday link to holiday calendar
9. THOCI - Public holiday calendar index
10. THOCS - Public holiday calendar display (days/months)
11. THOCT - Public holiday calendar texts
Tables carrying Public holiday related data
12. THOL - Public Holidays

13. THOLT - Public holiday texts
14. THOLU Dates of movable public holidays
 If changes are done only to Factory calendar (e.g. Change validity dates etc.) Then edit Tables 2 to 6
only. Delete rest of the table rows from the TR.
 If changes are done only to Holiday calendar (e.g. Assign new public holiday etc.) Then edit Tables
7 to 11 only. Delete rest of the table rows from the TR.
 If changes are done only to Public holiday (e.g. Create new holiday etc.) Then edit Tables 12, 13 &
14 only. Delete rest of the table rows from the TR.
To make changes double click on the respective row. Below screen will appear. Enter the calendar ID of
those calendars which have been edited. e.g. Here changes are done in E3 calendar only so restrict the
changes by filtering it in Table Key for Calendar E3 only.
© 2010 SAP AG 12
After saving this entry that object will be marked as Object with Key as shown below.
Update all relevant objects for that specific Calendar ID like e.g. Table key is ‘E3’ for object ‘TFACD’, ‘E3*’ for
object ‘TFACS’ & so on. Which object is updated with which Table key depends on the column position of
that Table Key in respective Table. Following matrix of “Table” “Column no.” and “Table Key” helps to update
the object with Key.
“Table Key” is the primary key for respective table which can be found by checking the tables through
transaction SE11.
If primary key is in first column of table then the table key is Primary key followed by *. If primary key
is in any other column then table key is “*primary key*”.
For example: Calendar ID “E3” entry
Table Name Primary Key Column No. Sample ID Table key
TFACD Calendar ID 1 E3 E3
TFACS Calendar ID 1 E3 E3*
TFACT Calendar ID 1 E3 E3*
TFAIN Calendar ID 1 E3 E3*
TFAIT Calendar ID 2 E3 *E3*
THOC Calendar ID 1 E3 E3*
THOCD Calendar ID 1 E3 E3*
THOCI Calendar ID 1 E3 E3
THOCS Calendar ID 1 E3 E3*
THOCT Calendar ID 1 E3 E3*
THOL Public holiday key 1 234 234
THOLT Public holiday key 1 234 234
THOLU Public holiday key 1 234 234
© 2010 SAP AG 13
If changes are done to more than 1 public holiday then include the public holiday key for all the calendar IDs
in the objects. Ensure that Public Holiday ID is included to see the text of the holiday in next system.
Once all the objects are modified and included for the restricted change:
Transport Request Object screen will look like as below
Transport Request main screen will look like as below
Object Names
Table Key
© 2010 SAP AG 14
d. Release the Transport Request to next / productive environment
With all these modification in the Transport Request it is now ready for release to next system in the path.
Release the Sub-Transport Request and main Transport Request now with standard release process so
that the request status appears as Released from current status of Modifiable
Once this Transport Request is released successfully to next system Calendar with only specific changes
(additional Special Rules) are transported & can be seen in the next system as below.
Additional
Holidays as
defined in Special
Rule for E3
This shows changes done to E3 Calendar are transported to next SAP installations and rest of the calendars
are not affected due to the custom transport process.
© 2010 SAP AG 15
Related Content
Note 538344 - Transporting calendar dates
Note 86621 - Calendar: Change or transport is not possible
Note 501670 - Public Holiday Calendar Creation/Change
For more information visit Supply Chain Management homepage.
© 2010 SAP AG 16
Copyright
© Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
© 2010 SAP AG 17

Calendar Modification and Transport From Development To Production Environment

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Calendar Modification and Transport From Development To Production Environment

Uploaded by

Copyright:

Available Formats

Calendar Modification and

Selective Transport from SAP

Author: Digambar Narkhede

Digambar is a Supply Chain Management Consultant working with Infosys Limited.

Definitions: SAP Plant and Calendars ............................................................................................................ 3

Definitions: SAP Plant and Calendars

Calendars specify working & non-working days.

SAP Calendar Structure

The calendar system consists of the following components:

 Public holiday calendar

Transport to next SAP Installations

Current Limitation and Rationale for Custom Transport Process

Few Scenarios for Calendar Change

Calendar Changes and transport could be of following types:

1. Addition of new Public holiday / Holiday Calendar / Factory calendar

Custom Solution for restricted change Transport

Following steps are involved in the whole process.

 Modify or Edit Holidays / Calendars - Use Transaction Code: SCAL

 Create a Transport Request from the SAP Calendar Main Menu

 Edit / Modify the Transport Request to contain restricted changes

 Release the Transport request to next / productive environment

Let`s see these steps in details:

a. Modify or Edit Holidays / Calendars - Use Transaction Code: SCAL

Factory Calendar with regular Holiday Calendar attached

b. Create a Transport Request from the SAP Calendar Main Menu

c. Edit / Modify the Transport Request to contain restricted changes

Select the respective Modifiable TR

Goto Change mode of a Transport request

Relevance of Tables with the Calendar objects:

1. TCALS - Central entry for factory Calendar

Tables carrying Factory calendar related data

2. TFACD - Factory calendar definition

5. TFAIN - Calendar: Intervals for company holidays, special shifts

Tables carrying Holiday calendar related data

7. THOC - Public Holiday Calendar IDs

Tables carrying Public holiday related data

12. THOL - Public Holidays

Table Name Primary Key Column No. Sample ID Table key

Transport Request main screen will look like as below

d. Release the Transport Request to next / productive environment

For more information visit Supply Chain Management homepage.

You might also like