http://www.sapyard.com/to-buffer-or-not-to-buffer-buffer-concept/

All customers who have dual SAP system landscape (Maintenance landscape & Implementation Landscape) have the challenge to ensure that synchronize the maintenance changes from Maintenance Landscape with the implementation landscape.

Need for Different landscape:-

Software changes are done in one system and will be transported to the system landscape which is linked to this system by transport routes of the Transport Management System. But sometimes it is necessary to implement these changes into another system landscape but without using the import function of the transport requests. Imagine this scenario with a Maintenance landscape and also an Implementation landscape, PRD would be the system that is already go live.

Now you want to implement a new functionality, you will use a second development system DEV to work in this new implementation, by working in DEV you will not disturb the maintenance of the PRD done in DEV system.

Usually DEV and TST is created initially as system copy from PRD system.

If a change is done in DEV this change must be done also in the MNT to maintain the synchronization, this is the reason of retrofit functionality, to help in getting the change done in DEV arrives to MNT.

 Changes of a Maintenance project also should be duplicated in an Implementation Project that will provide the same Production system of the landscape finally.

The main new features and advantages of the Enhanced Retrofit Functionality can be summarized to:

1. Automatic Categorization of Objects (Auto Import, Semi-automatic, and Manual)

The categorization takes place after the release of a transport request. The release creates the retrofit data.

  

Auto Import (Support of 100% of transportable objects!):

Semi-Automatic Retrofit with Correction Workbench (Note Assistant) or BC-Sets

Manual Retrofit

2. Conflict Detection is performed via Cross System Object Lock CSOL at object level

- Possibility to perform retrofit on object level

3. Detection of technical sequence dependencies

- Detection of same objects to be retrofitted in which order

- Advanced Control of Retrofit Sequence

4. Additional Features

- Enhanced Logging of Messages

- Comparison of compatible objects before retrofitting

- Various Customizing Possibilities

- Implementation of Customer Specific Requirements via Standard SAP BADIs

The Retrofit as it exists with Solution Manager 7.0 EHP 1 will still be available in Solution Manager 7.1, the new functionalities of Enhanced Retrofit can be activated separately per user, therefore do not have to be used if they are not required.

 How to Configure

Enhanced Retrofit customizing

1. Go to SPRO  and run this point “Activation of Retrofit” if you want to use the enhanced retrofit:

This is activating EXTENDED retrofit.

SM30: /TMWFLOW/EXTUSR

If you are moving from standard retrofit to enhanced retrofit you can activate enhanced retrofit for some specific users.

By adding * as the only entry the new retrofit is activated for all users.

2. Maintenance of Retrofit parameter: SM30 ->/TMWFLOW/RCONFIG

3. Status Customizing for retrofit objects: SM30 ->/TMWFLOW/EDT_CST

It is possible to allow or forbid certain manual changes to the objects inside the retrofit object list of a transport request.

4. Badis

BADI /TMWFLOW/RETRO_RELEASE: this badi can be used to influence the Retrofit behavior during the release (creation of the retrofit data)

BADI /TMWFLOW/RETRO_DURING_RETROFIT: this badi can be used to influence the behavior when the Retrofit screen is visible

BADI /TMWFLOW/RETRO_AFTER_RETROFIT: BADI methods are processed after the retrofit has been completed/processed

Prepare the logical components and the projects

1. Create the additional clients

Ensure that there are consolidation routes  (client dependent) from your development system to the quality assurance system and your quality assurance systems  are linked to the production systems via delivery routes (client dependent).

  
2. Domain links

Also establish a domain link between the two TMS landscapes!!! The maintenance TMS landscape and the TMS implementation landscape (if not you will have later problems to import the TOC created in 100 to client 101).

There must be a domain link from solman domain controller to these two TMS landscape too.

3. Create the RFC destination for the new clients in lmdb

4. Run “Read System Data Remote” in the domain controller of each TMS landscape to refresh the system data in SMSY,

 Note: There must not be any client with production role  for this example scenario, if not the BC set could not be activated in the retrofit system.

5. Create the ibase component for it  by running report _CRM_IBASE_GENERATE_71 for the  system.

6. Create two new logical components, one for the existing Maintenance landscape with a new system with role Retrofit and a second logical component for the implementation landscape:

 we have two aspects here :- 

1.column store 

2.Row store

to find column store utilization :-SELECT round (sum(MEMORY_SIZE_IN_TOTAL)/1024/1024) AS "Column Tables MB"  FROM M_CS_TABLES;

to find row  store utilization :

SELECT round (sum(USED_FIXED_PART_SIZE + USED_VARIABLE_PART_SIZE)/1024/1024) AS "Row Tables MB" FROM M_RS_TABLES;

If you want to migrate a particular table from one node of HANA to another for performance or space issue :- 

1. To view current location  of table - 

open SQL editor on HANA studio and run the sql query :- 

select * from "SYS"."M_TABLE_LOCATIONS" order by LOCATION, table_name

2. To view current location  decide the node where you want to move it and run the below  query on SQL editor of HANA studio:- 

ALTER TABLE MOVE TO ‘node:port number’

http://www.sapyard.com/steps-to-add-custom-tab-in-standard-miro-item-screen-using-badi-mrm_item_custfields/