I am sure, the scariest and most tensed moment of SAP Consultant can not be other than project Go Live Date. We have few ways like through to minimise the risks like
1. Good Quality of Testing considering all positive and negative scenarios called as regression testing by few clients.
2. Making sure all the transports are moved to final destination that is production server.
3. Some clients prefers Dry Run option, where objects like reports can be executed, transactions can be executed making sure that data is not posted. and error free delivery can be assured.
These steps will make sure that transports are well reached to production but still we have huge load of cutover activities, which I will try to simplify in this Blog :
Table Maintainace :
We should always avoid maintaining table maintainace data directly in production, and most simple reason for the same is a simple entry like table maintainace can have huge impact like Interface not getting trigerred or sending incorrect data. I will show how can we maintain data in Development or Golden Client, test the changes throughly and then pulling the changes in the tranports and applying in production enviornment.
Step1:- GOTO SM30 and open the table selecting the entries which is to be sent to production system as shown in the screenshot below
Step2:- After entries to be transport is selected then goto following path
Step3 After selecting transport option, following popup comes which shall ask for transport number or you can create a new transport as well
Step4 – Most important, these entries will only be visible in transport , when following step is performed.
By clicking on highlighted button, we can make sure that table entries are included in transport and one overhead of table maintainace is reduced.
We normally maintain Variants in the Live system, but somewhere we may come across the scenario where we want to to transport the Variants along with program from Development system to the Live System or Testing System.
SAP has provided a standard program to pull a Variant into a tansport, in the doucment below, I will be showing the usage of the same.
Step 1 : Goto SE38 and enter program Name – RSTRANSP and Execute
Step 2 – Provide the program name and name of the variant that needs to be transported to next level and execute the report, constarint is that variant should be available in the system where this report is being executed (mostly Development system).
Step 3 – Popup comes with program name and variant name which needs to be selected. Checkbox needs to be ticked.
Step 4 – Popup window for transport organiser appears where we can create a new Transport or use our own request.
These are few basics thing which will I am sure most of us know but still can bring down lot of manual activities, if performed from the begining.