Workbench request for table entries

[Former Member]

I have created a z table (in $TMP)with following details:

1. Delivery class:: L

2. Maintenance allowed

3. Table maintenance generated with FM (in $TMP).

Now, it should be a local object and never be transported.

But when I creating enteries in that and trying to save it, its asking for a workbench request. If it would have asked a customizing request i would have understood, but my question is why workbench request for entries.

Further, If I am able to save an entry and later I want to change, how to do that.

Any helpful entry will be rewarded.

Warm regards,

Raman.

[jayakummar]

hai raman,

the thing is ,

table is one object and entries is one another object. thats why its asking request.

BEST EXAMPLE IS,

SPRO transaction.

in spro transaction. all customized data stored in table but it ask request .

plzz reward if useful

regards,

jai.m

[Former Member]

Hi,

Change requests are managed by the Transport Organizer. Changes to Repository and Customizing objects are recorded in change requests.

The CTS is the system which hadles all your change requests.

So that you can differentiate between global changes to the system and client-specific Customizing settings, the CTS records your changes in either a Workbench request or a Customizing request:

Workbench Requests

When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.

Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.

Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.

Customizing requests

Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).

Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.

Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually

For more info see the following link

http://help.sap.com/saphelp_47x200/helpdata/en/57/38e1824eb711d182bf0000e829fbfe/frameset.htm

Reward points if found helpful.....

Cheers,

Chandra Sekhar.

[Former Member]

Hi,

Create the table maintainace generator in t-code new entries in SM30. after saving the data. you can chage the existing entries also.

Regards

Vijaya

[Former Member]

Dear Raman,

Please check weather you have followed the steps as given below:

1) go to se11 check table maintanance check box under

attributes tab

2) utilities-table maintanance Generator->

create function group and assign it under

function group input box.

also assign authorization group default &NC& .

3) select standard recording routine radio in table

table mainitainence generator to move table

contents to quality and production by assigning

it to request.

4) select maintaience type as single step.

5) maintainence screen as system generated numbers

this dialog box appears when you click on create

button

6) save and activate table

Links:

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_46c/helpdata/en/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm

/message/2831202#2831202 [original link is broken]

One step, two step in Table Maintenance Generator

Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.

Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.

[joseph_manjiyil]

Hi Raman,

Workbench request is created for client independent data. ABAP programs and tables without MANDT field will request Workbench request.

Customizing request is created for client dependent data. Tables with MANDT field will have customizing entries which are dependent to the client and needs to be transported with SCC1 transaction. So it will prompt for entering the customizing request.

I have mentioned this, as this thread didn't have correct answer listed for the sake of others.

Regards,

Joseph M