SAP Roll-In/Out Processing Overview

During the roll-in, pointers to the roll area and user context are populated in the work process. This enables the work process to access the data in those areas and so perform processing for that user and that program. Processing continues until the program sends a screen to the user.

At that time, both areas are rolled out. Roll-out invalidates the pointers and disassociates these areas from the work process. That work process is now free to perform processing for other requests. The program is now only occupying memory, and not consuming any CPU. The user is looking at the screen that was sent, and will soon send another request.

When the next request is sent from the user to continue processing, the dispatcher allocates that request to the first available work process. It can be the same or a different work process. The user context and roll area for that program are again rolled in to the work process, and processing resumes from the point at which it was left off. Processing continues until the next screen is shown, or until the program terminates. If another screen is sent, the areas are again rolled out. When the program terminates, the roll area is freed. The user context remains allocated until the user logs off.

In a system with many users running many programs, only a few of those programs will be active in work processes at any one time. When they are not occupying a work process, they are rolled out to extended memory and only occupy RAM. This conserves CPU and enables the R/3 system to achieve high transaction throughput.

Roll Out:

Extending the business functionality from corporate to its branch office.Example: You have main office in German and they implemented SAP.Also they have branch in India and want to implement in India.When implementing SAP in India office( having same company in corporate level and assigning a company code for India to the same company), you can say it’s a roll out project.

Upgradation projects in SAP:

Replacing older verion to new version.Example:Upgrading from SAP 4.6C to ECC 6.0.

Roll out example

IF client is on SAP and runing SAP now he purchases new p-lant or set up new plant then going on to sap for this new plant is roll out

The difficulties which a SD Consultant might come across during a Roll Out Project: 

1. Since their might be multiple other companies running on the same system hence during the roll out for a new Company we need to verify the business process which the Roll Out requires to match the Business process of other companies as well.

Some times same config settings or same order types are being used across different Sales organizations by modifying their begaviour by using User Exits so that same config works perfect for different company codes.

Hence you need to find out if you are modifying a standard process then is their any other Sales Company which gets affected by the same?

For example when we talk about Info Structures then if the standard Info Structures are shared by various companies and now you want to change the Update Rule from Day to Month then an analysis has to be done for the impact of this change to other companies.

So a check list can be prepared and main functionality used by other Sales Companies can be noted so that it can be reused.

Also See:What is the usage of User Exits in SAP SD