Change change request

                                                                                                         CHANGE REQUEST

Change request to understand for SAP Basis

Change Request Type:

1. Customizing Change Request
2. Workbench Change
3. Transport Of Copies
4. Relocation of Objects

1. Customizing Change Request: It is used to save the changes made to Client Specific data or Objects. E.g.. Company Code, Sales Org.
2. Workbench Request : It is used to save the changes made to Cross – Client Objects and repository objects
E.g.. Programmes, report, Changes to DDIC Element
3. Transport of Copies: It is used to export the tables and table contents based on 
    Requirement. E.g.. : The System need to be crashed and the system dependencies
    need to be backup.
4. Relocation of Objects: The Object can be transported (exported) to a trans directory
  which can be imported later. The Objects such as Programmes, transactions,
  function module can be moved using this option.

When SAP Software could not satisfy the requirement of the customers, we may need to develop the objects in the customer name space i.e… Y and Z.

Fields : In order to fulfill the customer requirement we may need to develop fields.
Fields are defined with data type and length. This is referred to “DOMAIN” and is used to maintain the consistency in the system E.g.. Price, Place

Data Element: It is nothing but a domain with meaningful name. E.g.. Cost price, selling price, profit, loss.

TABLE: It is represented as rows and columns where columns represent data elements and rows represent data or record.
There are three types of table
a. Transport table
b. Pooled Table
c. Cluster table

Transport table represents table at database & dictionary level. Pooled and Cluster points to one table at D/B which points to more tables in dictionary.

Table can be defined in transaction SE11 or SE12

In order to insert, select , delete record in table we need to create programs. Programs are created in transaction SE38 and executed through transaction SA38.

In order to define re-usable component for insert, select, delete, modify we need to define functional module this are defined in tcode SE37.

In order to display , insert, modify data we define Screens. Screens are defined in tcode SE51.

In order to work with screens we need to define MENUS. MENUS are defined in transaction SE41.

We can also use predefined scripts such as invoices, delivery notes, purchase order, sales order and define in customer namespace i.e.. copying the pre-defined scripts in customer scripts through TCODE : SE71.

In order to execute a program the easiest way is to assign a program to transaction.

We create transaction using TCODE : SE93

For Message got to : SE91.

In order to develop all this objects user need to register as developer. Whenever any of the above are developed then it need to be assigned to development class or packages.

If you assign the package $TMP (name of package) then it save the same to local object. It is not eligible for transportation, so define any development in different package. We can create package using TCODE: SE80.

Create Package :  Go to SE80

Specify the application and software component. Assign Transport layer  and create
Used customized transport layer to move the object.