Hi there,
Unfortunately, SAP mentioned in some notes that you always should use the transporttool to transfer changes/updates in calendars to Production client. Even a small update, like adding a new holiday, you should transport it from Development to Quality and then Production. Unfortunately you can only transport "everything" , that means all calendars all rules etcetera will be transported everytime
.
What problem do I have with it:
Suppose you are orded to transport a small change to production. You know everything will be transported. You change it first in DEV, the question / Problem is, How can you be sure that you don't transport temporary trials of other people who has changed something in a calendar of DEV as well?
The only way to avoid transporting "****/test" from others, to me is to check the contents of all tables related to Calendars
:
So can anybody tell me how to check that the contents of all underlaying tables are equal in DEV, QAS and PRD, before I make the change, to avoid the problem mentioned above? and
How can I be sure that after the check when doing my change, somebody else is doing the same before I release the transport?
Some remarkt to that:
- Offcourse everything needs to betested, but that isn't the question.
- It is a pitty that SAP wasn't able or didn't find it worthwhile to have the option to transport individual objects of a calendar, because if they did, then there was no reason to do the job in production. I did that many times though without any problems because I didn't want to transport all test objects as well, i did have some bad experience with that.
Regards Kees
