sap landsacpe

DEVELOPMENT: It  is where the  consultants do the customization as per the company's requirement.   

QUALITY: is where the core team members and other members test the customization. 

PRODUCTION: is where the live data of the company is recorded. 

# we will transport from DEV to QA and then QA to PROD. You will not transport from QA to DEV.

For your clarification you will not change any thing in QA. You will make the changes in DEV and transport them to QA. QA is only for testing.

Regarding two movement types - one is incoming and other one is outgoing.

the configuration/customization as per the company’s business process.

# Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.

# Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new development is done is development client and the request is transported to production.

These three are landscape of any Company. They organized their office in these three way. Developer developed their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.

Presentations Server- Where SAP GUI have.
Application Server - Where SAP Installed.
Database Server - Where Database installed.

Transport Req. means, For simple under stand its like a Folder. While developing we will save all the activities in the Folder ( Transport Req # ) and we will move the folder in Qc for testing if testing successful move to production for live.

·        These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.

·        Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward,

·        you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving every time. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).

·        You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful transport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.

·        But in the Testing client you cannot even access SPRO  (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV).

·        The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.

·        The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.

    

 Transport Request:

# Customizing Request - When doing or changing some customization.

# Workbench Request - When configuration is cross-client. Eg Generating new Table, making changes in access sequence, Abap development, etc.

Transport request is not generated for Master Data. For eg: Customer Master, Material Master, price master, etc.

Benefit of Transport Request:

SAP Landscape normally has 3- Tier system:

Development Server - Where customization takes place. Transport request is generated at this level & then first transported to Quality server for testing whether it meets the requirement or not. Once the requirement is met in Quality server then Request is transported from Development Server to Production Server (Actual / Live System)

Quality Server - Mainly useful for testing.

Production Server Actual / Live server, where the real transactions are created & posted.

Procedure to Release & Transport Request:

1. In development server, go to T.Code: SE10 & select the check box Modifiable & enter

2. In the next screen, you will see list of transport request created.

Note: Transport request consist of main request along with sub request. These sub request hold the object to be transported.

3. Expand the main request & you will be able to view the sub requests attached to main request.

4. First release the sub requests.

Note: To release the request, select the request ni & click on release request individually (Do not select release all request)

5. Next release main request.

6. Once the request is released sucessfully, imform the basis person to import the request to QA server.

or

If the authority is with you, through T.Code: STMS, select development server --> select request no & release to QA server. Here when it pops up client no, user id & password, maintain it of QA server & release the request to QA server.