Transport for SCAL 'factory calender' or administer SCAL in prod system?

[Former Member]

Hi togehther,

we could change the factory calender in the development system and afterwords transport this changes by using a transport request and STMS.

But our Consultants recommend not to transport these changes. They recommend to open the prod System with SCC4 to open status (Changes are allowed) and then make the changes in the prod system.

I think, this is the wrong way. How do you solve this probem?

Carsten Schulz

Teamlead SAP-Basis

[former_member197616 · Accepted solution]

Hi,

Seems it is better to do it in Development system and compare the Prod with development at OY19 T code and and transport.

Regards,

[jason_gordon]

This message was moderated.

[JL23]

Use the transport. dont change it in production.

your consultants probably fear unwanted side effects. MAybe they are right, but then only because they did it wrong from the very beginning and always used this wrong approach.

When you transport SCAL, then ALL calendars will be transported, not just the changed one.

If you use always the transport sytem, then your calendars in development and production system are in sync.

But if former changes where done directly in production, and never repeated in development, then you may screw up production if you transport the calendars now.

[Former Member]

Hi,

now I have the exactly problemdescription.

The reason why the SCAL is only maintened in the prod system is, that the consultants fear about testchanges in the development system and the circumstance that if we transport the calendar, we allways transport all calendars from all countries and all holiday days.

Two Questions:

Now we want to look for the checkbox to open the customizing the scal in the productiv system? Where is the checbox in SPRO for scal?

How can we syncronize the SCAL from Productive to Development? How to make the export in produktive system?

best regards,

Carsten Schulz

[JL23]

allowing cusotmizing changes in production has to be done in SCC4 transaction.

A developement system is not a sandbox. so there should not be testchanges.

I do not know a smart option to copy the production setting into the developement system, looks like it has to be done manually

[former_member199502]

Hi ,

You are consultants are right because SAP clear tells that "You cannot transport individual public holidays or calendars. 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".

As from your mail i understood that in development system,all users have access to to SCAL transaction,if some users have craeted or changed the factory calendar changes.all this changes get in to trnsport request which in turn affect the calendars in production system.

Thats Y in some industries,Consultants will do the changes through fire fighter ID directly in production or in some industries for development system SCAL authorization will not be given to all.so that as Juregn pointed development and production system will be in SYnc and you can do transport.

In this situation you can try one more option,after generating the transport request go to SE01 ,go to change mode and edit the request (double click on the request).

then go to obects tab you will see lot of tables related to factory calendar.check each tables in SE16 for the calendar you made the changes.if entries are there retain the table else delete the table.

If entries are there,then double click on the table,you will get the table key.in that put calendar id if there is only one entry,if more entries are ther e put calendar id suffix star.and save.

Check this solution first intest system and ensure whether it is trnsaporting only the particular changes