transporting z table

[Former Member]

whats the best way to transport a z table

[Former Member]

whats the best way to transport a z table

[Former Member]

if you create the ztable with fields... then it will ask you the request number ...

so goto se10 relaease the task and then release the request .... by pressing the Truck ICON.

if you want to release the data within that z* table , then do save the data with in that request by ....

open the z* table in the change mode execute it ... then see the data ... in front ther will be the check box ... select the data you want to transport .

in the menu table entry -> transport Entries is there press on it .. so that the selected data will be transported the Change request ...

rewaerd points if it is usefull ......

Girish

[Former Member]

goto SE10 :

check the transport req which contains ur table.

release all tasks inside than that req.

release the req.

then transport the table.

The contents of the table should be transported in a req.

when u were making entries thru Sm30 then u might have been asked for the req. that req contains the contents of the table.

U should transport it in the above way.

Reward if useful

Regards

Prax

[Former Member]

Extended Transport Control

Use

Extended transport control has the following functions:

As well as specifying an SAP System as the transport target of a consolidation or delivery route, you can also specify a client. This means that you can configure the transport of client-specific objects just as securely as the transport of cross-client objects.

You can set the standard transport layer that you use to define the transport target of Customizing requests, among other things, as client-specific.

You can set up several parallel consolidation targets in target groups. This is often required by ALE.

Extended transport control makes daily transport tasks easier, and it increases security. It also reduces the need for communication between project leaders and system administrators, since the transport routes can now be configured completely. No additional details about the target client need to be given at the time of import.

Features

You can make use of the following extended functions when you configure transport routes in Transport Management.

Client-specific standard transport layer

When you create Customizing requests, the default transport target of the requests is determined by the standard transport layer. When you use extended transport control, you can set a different standard transport layer for individual clients from that set in the SAP System. This means that you can forward Customizing requests from different clients into different transport targets.

The client-specific standard transport layer is also the default transport layer for new packages that have been created in a client. If you accept this default, then the cross-client objects that have been created in cross-client Customizing are transported along the same route as the corresponding client-specific Customizing.

Client-specific transport targets

The transport targets of consolidation and delivery routes do not just specify a system, they also specify a client. Client-specific transport targets are entered in the form: <system_name> <client> (for example, QAS.013).

Target groups

Target groups combine several client-specific transport targets under a symbolic name. You can specify target groups when you define consolidation and delivery routes.

To differentiate them from traditional transport targets you must start and end the names with "/" (for example, /EUROPE01/).

When you release a request which has a transport group as a transport target, then the request is flagged for import into every individual transport target <system_name>.<client> in the group.

Client-specific consolidation routes

Consolidation routes determine (for each transport layer) where changes made in the SAP System are transported after the request has been released.

If you have activated extended transport control, then the transport target can be a particular client in a target system or target group.

If you do not activate extended transport control, you can specify systems only as consolidation targets. This means that the transport administrator has to specify the correct target client at the time of import.

Client-specific delivery routes

Delivery routes determine whether change requests are to be flagged for import into subsequent systems/clients, after they have been imported into a system.

If you have activated extended transport control, then you can set the delivery routes as client-specific. This makes it possible to supply several clients in one system in sequence.

You can also specify a target group as the target of a delivery route.

Improved import controls

If you work with extended transport control, you can import requests into different clients in a system without using unconditional modes.

When you first import a request into a system, all the objects are imported completely. Any subsequent imports into other clients in the system only import client-specific components.

This makes it possible to set up consolidation routes and delivery routes between different clients in the same system.

This means that you can also transport client-specific objects (Customizing) into another client in the development system. Client-specific Customizing and Repository objects are ignored by the import.

Example

The following graphic shows an example of two production systems, PR1 and PR2, linked by ALE. Both of the production systems are preceded by a QA system (Quality Assurance System). The two QA systems are also linked by ALE.

The example merely portrays the options available with extended transport control. It is not a recommendation for setting up your own system landscape.

Development takes place in three clients in the system DEV.

Development, client-specific Customizing and general Customizing take place in client 222, and are released with transport target /COMMCUST/. The target group /COMMCUST/ contains four elementary transport targets:

QA1, client 010

QA2, client 312

System DEV, client 100

System DEV, client 300

The latter two transport targets are the development clients for country-specific settings. Requests with the transport target /COMMCUST/ are flagged automatically for import into all four targets.

Alternatively, you can specify just the targets "system DEV, client 100" and "system DEV, client 300" in the target group /COMMCUST/, and set up a delivery from "system DEV, client 100" to "QA1, client 010" and a delivery from "system DEV, client 300" to "QA2, client 312". This defers the imports into the QA systems.

In both cases, the ALE functions remain stable, since both QA-PRD routes are being supplied in parallel.

Country-specific settings are made in the clients 100 and 300 of the system DEV. They are then released directly to the corresponding country QA systems (the target client is specified). This is done with a client-specific standard transport layer.

The QA systems automatically deliver to the correct target clients in the production systems, since the target client is specified when the delivery routes are defined.

Activities

Transport route configurations are activated according to an 'all or nothing' rule; either the parameter is set in all systems connected by transport routes, and these systems only use transport routes with specified target clients, or the parameter is deactivated for all systems, and only target systems are specified.

You can, however, configure two separate system groups, only one of which uses extended transport control.

Background:

The buffer format that has been used until now does not include target clients (buffers are the operating system files in which the transport requests are flagged for import).

Extended transport control introduces a new format for the buffer lines. This format has, among other things, space for the target client.

For security, versions of the transport control program tp that do not recognize this new format are not permitted to process the new buffers. An appropriate entry in the transport profile prevents this in the system.

when you do a configuration for your module you will be doing this in development server and you need to transfer this into QA for testing.For this you have to create a request that you have finished x nos of settings and this to be released to a basis guy.He will be transferring to qa server.

example release

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.

For more information about the SAP Change and Transport System (CTS), visit the following link:

http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm

Reward points if this is helpful.

http://help.sap.com/saphelp_nw2004s/helpdata/en/1b/9dc2d6e59911d184810000e8a57770/content.htm

[Former Member]

Hi,

1. Create Ztable by going se11 Tcode. While saving the ztable in development class it will create CTS for your object. Create the fields and assign those fields to the Ztable.

2. Go to se10 tcode select modifiable and then click on display.

3. Select your CTS then click on truck symbol.

it will release the selected CTS.

Reward points if useful.

Thanks & Regards,

Vasudeva Rao.

[Former Member]

hi timothy,

To transport the entries U need to have 2 things:-

1, The Delivery Class must Be 'C'. (Customizing Table)

2, U must a TMG (Table Maintenace generator ) for this table.

Steps :-

1. Go to se11

2. Enter ur Table Name

3. Menu --> Utilities --> Table Maintenance Generator.

4. Give the AUthoriazation Group (&NC&)

5. Give the Function Group ( AS per ur client )

6. Press Find Screen Numbers Push Button on the menu bar

7. Press Create.

Now create entries for ur table.

Then Transport.

Plz Reward points if contents are useful,,,,

Regards ,

Mandeep.

[Former Member]

In some unusual cases, you might have to transport data of a SAP table.

Go to transaction SE16,

select your entries and go to

Table entry -> Transport entries.

It's only possible for some tables...

If you cannot do it that way, you have to create a Workbench transport order with transaction SE10.

When created, click on it,

go in menu Request/task -> Object list -> Display object list.

Go in modification mode and add a new line with:

PgmID = R3TR

Obj = TABU

Object name = Name of your table

R3TR TABL <tablename> for the table structure, fields and definition

R3TR TABU <tablename> for the table contents

regards,

srinivas

<b>*reward for useful answers*</b>

[Former Member]

Hi,

check the below blog .

/people/community.user/blog/2007/01/07/transport-table-entries

Steps :-

1. Go to se11

2. Enter ur Table Name

3. Menu --> Utilities --> Table Maintenance Generator.

4. Give the AUthoriazation Group (&NC&)

5. Give the Function Group ( AS per ur client )

6. Press Find Screen Numbers Push Button on the menu bar

7. Press Create.

Regards