Regarding requests

[Former Member]

what is the change request and what is the difference between workbench request, customizing request and change request?

What is the change request document?

[Former Member]

Hi,

Workbench requests contain changes in ABAP objects like programs, tables, data elements, domains, function modules etc.

Customizing requests contain changes whic we mainly do using SPRO, also the changes related to org structure and table data some times.

Regards,

Pankaj

[Former Member]

1) workbench req. = objects of the workbench (se80)

-Tables, structures, data elements

-programs

-function modules

-transactions

2) customizing req. implicate the content of a CU-table

-configuration

1. Customizing Request: This request is generated if we are doing configuration changes to meet the scenario.

2. Work Bench Request: This are normally development Request or request which are generated during customization such that it impacts all client on the same server.

Change Request / Transport Request carries out the changes in the other server, when it is imported to it & we need not repeat the configuration in other servers, other than development server.

Customizing request is the one created through any configurations

Workbench request usually gets created by abap programmer, or if any tables are updated.

Customising request is the request generated when you do any configuration changes.Ex.creating new sales off.and assigning it to Sales area.

The flow is you define and assign in DEV Server and later on move it to QAS and then PRD,i.e.,DEV->QAS-->PRD.

When you drill down the request,it will show all the details of changes,you can easily find wheather it is Functional or Tec.

Workbench request is concernd to ABAP

Whenever you are creating any new condition tables,this request is of the nature Workbench request and not customizing request

Hope this makes the doubt clear,encourage by rewarding points

Regards,

Madhavi

[Former Member]

hi naveen,

->A Change Request is a list in the system containing the objects to be transported and information on the purpose of the transport, the transport type, the request category, and the target system . A change request has one or more Change tasks.

->When a request is created, the system assigns a number to it automatically known as change request number . The format of this number is normally The request task. A request may have one or more tasks. But when a request is copy of some other request there is no need of a task.

The changes are actually saved in the task by the end user who is making the changes. Before releasing a request to quality system the task has to be released.

Customising requests(change request of category CUST) record client-specific customising settings within a client.A request/task of the category CUST only contains clent specific customising objects of category CUST that originate from exactly one client(source client)

Requests/tasks of the category SYST contain objects that also belong to the category SYST.

These are ABAP/4 repository objects and customising objects intended for all clients.

Requests/tasks of the type SYST can also caontain objects belonging to the category CUST,ie.,they allow a combination of both categories.However,as above,all the objects may only originate from one client(the source client).

Change request:

Definition

A parallel object created to record changes to a collateral entity (collateral object or collateral agreement) that has been released and set to status Active.

Use

Use change requests to maintain planned changes to collateral entities that have been released (set to system status Active). A change request passes through a life-cycle similar to that of any other collateral entity. To save the planned changes on the parent collateral entity, you must release the change request using appropriate business activities.

The Request function is enabled only for collateral entities that have already been released. To view existing change requests, select the list arrow on the Request button on the application toolbar. To view change requests that have not been released (inactive), select List of Change Objects. If active change requests already exist for the entity, you can display them by choosing Active.

Choose with the quick info text Display Release History, to view changes made using a change request. This function can be used only if the change request has not yet been released.

Structure

A change request has a structure similar to that of parent collateral entity. You can however determine the values that can be changed in a change request using the Customizing settings.

Customizing Settings for Change Request

To create change requests, you must define the necessary settings by choosing Process Control ® Change Request in the Customizing for respective collateral entities.

Change request types that you need to make specific changes to the collateral entities. For example, for a real estate lien, you may be required to furnish a notary declaration or a trust order.

Status profiles that must be assigned to change request types. By this assignment, you determine the possible user statuses that collateral entities must assume when change request business activities are performed on them.

Required business activities relevant for change request types. The business activities would determine the process control (including field statuses, authorizations and status transitions) on the change objects.

For example, you can use the object screens assigned to business activities to determine the fields that can be changed in the change requests.

The standard system provides the authorization object CMS_PCN_02. You can assign authorization profiles of this authorization object for all change request types.

Release procedures for generating work items to enable workflow for change request. You also define status transition on release for change request types.

Collateral Management uses the change request concept to implement the special arrangements function for collateral agreements. Therefore, you must define all special arrangement types (defined in the Customizing for collateral agreements) as change request types.

Example

Some possible change request types are:

1. New valuation

2. Trust order

3. Notary declaration

4. Declaration of property developer

rewrad if helpful

regards,

sravanthi