Transport Table T77PR and T77PQ

hi
Is it possible to transport the following table from DEV to PRD, from tcode :OOSP
or any other way ?
The tranport option in OOSP is greyed out
thanks
Jonu

In some unusual cases, you might have to transport data of a SAP table.
Go to transaction SE16,
-->select your entries
-->Assign the selected table entries to the transport request using the Include in request function.
-->This marks the entries for inclusion in the transport request.
-->Save your changes.
-->The selected table entries are added to the transport request
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
Double-click on the created line and, depending on your need, put '' in the key field or double-click on it and select the key you need to transport.If you give '', it will transport all the entries of the table from DEV to PRD. First make sure the table structure is there in PRD. If it is not there first move the table structure and then the table entries. For this give the
PgmID = R3TR
Obj = TABL
Object name = Name of your table
Regards,
Bharath

Similar Messages

Transport table and table entries

Hi,
I need to create a table and table entries, here I need to transport table and its entries to another system,
what steps i need to follow for this?
Please help me

Entries
Create entries by Se11-> utilities-> table content -> create entries
For Transport
Go to SE10.
Click on the 'Create' icon.
Select 'Workbench Request'(assuming your table is not customizing table).
Enter description and click 'Save'.
Put cursor on the task (lower number of the two) and in menu, 'Request/task>Change Type>Development/correction'.
With cursor on the task(lower number), click 'Object List' icon on the toolbar.
Once in, you need to toggle to 'Change' mode using the pencil icon.
Then click on 'New Entries'. Now add the R3TR, TABU, <ZTAB> in the first row.
Again in the menu, select 'Extras>Change object function>Key according to key list'.
Now go to the menu, 'Goto-->Key list'. In the subsequent screen, click on 'Insert line' icon(with a + sign).
Click on 'Key fields' button and it will now allow you to enter the values for each key field.
Regards
Shashi

Table copy and transport

Hi all,
           i have copied a few existing tables and used it in my program.after activating my tables(tables that are copied)
i ve sent it for transport from development to quality.but my basis consultant replied me with RC = 8.
and in the report output it showed like this.
Activate table YQM_TBL_TC_REF
     / | Key field TCNO has unpermitted type                                                                                |
     / | Field TCNO: Component type or domain used not active or does not exist                                                              |
Field TCNO cannot be used as key field because no default exists for type
     / | Nametab for table YQM_TBL_TC_REF cannot be generated                                                                                |
Table YQM_TBL_TC_REF was not activated
Activate table YWBG
     / | Field EXCESSM: Component type or domain used not active or does not exist                                                           |
     / | Field MOIST: Component type or domain used not active or does not exist                                                             |
     / | Nametab for table YWBG cannot be generated                                                                                |
       |   Table YWBG was not activated
but i have activated all the tables and even adjust and activated.i have to transport these tables along with the program. any help in resolving wud be greatfull.
Thanks,
naren

Hi Naren,
First activate all the Data Elements, Domain in the Package. Then activate all the structures and then finally the Database Tables. It so happens that sometime during Generation, some problem happens and this doesn't gets generated properly. And hence inactive Objects are locked in a Transport Request. And when it reaches the Q system, the dependent transport fails.
So, I would suggest you to regenerate all the Objects. And then check for any generation related errors. Then lock them in a new transport and release the request. I hope this will solve the problem.
Have a look at the Runtime Object of the DDIC Tables. The way to navigate is SE11 --> Open the DDIC Table --> Utilities --> Runtime --> Check. This will tell you the status of all the Runtime Object.
Hope this helps.
Thanks,
Samantak.

How can I save the first dept. for an employee in a transport table?

Hi All,
I have created a table to store the transports to an employee from department to another department.
the first department number to every employee is stored at the parent table called employees.
when I insert a new record to the transports table (which is the child for the parent employees) for an employee and the manager agrees for this transport the original value of department number in employees table will be changed to the new one. I done this process through a db trigger on the transport table.
Now the problem is that the original value of the first department number will be lost cause of the db trigger that changes this value after manager agreement!
I looked to solve the problem by adding a new column in employees table to save the first dept. no. for each employee only if Count of records = 1 for that employee like this:
-- Before Update DB Trigger on Transports Table:
DECLARE
pragma autonomous_transaction;
N NUMBER;
BEGIN
SELECT count(EMP_SID) -- emp-sid is the FK referenced from employeess.emp_sid
INTO N
FROM TRANSPORT_TRANS
where emp_sid=:NEW.EMP_SID
GROUP BY EMP_SID;
     IF :NEW.AGREE_FLG = 1 AND N = 1 THEN -- If the manager agrees and this record is the first one for that employee
     UPDATE EMPLOYEESS E
     SET E.FST_AD=E.ADMINISTRATION_SID, -- E.ADMINISTRATION_SID has the oroginal value for admin no. and FST_AD is the new column to save the first value
            E.FST_HE=E.HEADQUARTERS_SID,
            E.ADMINISTRATION_SID = :OLD.ADMIN_SID, -- changing the value with then new one added on the table
            E.HEADQUARTERS_SID = :OLD.HEAD_SID
           WHERE E.EMP_SID = :OLD.EMP_SID;
     ELSIF :NEW.AGREE_FLG = 1 AND N != 1 THEN -- if the manager agrees but the record is not the first record for that employee
     UPDATE EMPLOYEESS E
        SET   E.ADMINISTRATION_SID = :OLD.ADMIN_SID, -- only change the original values
                 E.HEADQUARTERS_SID = :OLD.HEAD_SID
                 WHERE E.EMP_SID = :OLD.EMP_SID;
     END IF;
END;But the form gives me this error if I deleted (pragma autonomous_transaction;) st. :
ORA-04091: table transports is mutating, trigger/function may not see it
But when I keep it, the form gives me this error:
ORA-06519: active autonomous transaction detected and rolled back
Edited by: Dev. Musbah on Aug 18, 2009 2:09 AM

Dev. Musbah,
First make sure that the insert statement executes. And check whether other error messages are getting. Currently you are checking only NO_DATA_FOUND. so change the exception part with
EXCEPTION
     WHEN NO_DATA_FOUND THEN NULL;
     WHEN OTHERS THEN MESSAGE('Some Error Occured');Regards,
Manu.
If this answer is helpful or correct, please mark it. Thanks.

Transporting table entry with primary key 120 char

Hi all,
I have 2 separate questions which I feel are closely related.
In the url:
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eb6e446011d189700000e8322d00/content.htm
It says:....
If the key length is greater than 120, there are restrictions when transporting table entries. The key can only be specified up to a maximum of 120 places in a transport. If the key is larger than 120, table entries must be transported generically.
How do I transport the table entries "generically" for such a table?
To further illustrate my actual problem:
My problem in the real world lies with the MIMETYPES table, maintained in trx SMW0.
I select the mime types row by row and do a Table Entry > Transport Entries, but get an error that says
"Key entry for table MIMETYPES may only be generic".
As a result it fails to attach to my transport.
(Note: the primary key of MIMETYPES is 128 chars long)
The Diagnosis long text says "The key is longer than allowed by the Change and Transport System (120 characters)."
The Procedure says:
1. Make sure that you only specify the character fields before the
 first non-character key field. You must enter the key with a generic
 ending. Enter the generic symbol directly after the specified part
 of the key.
2. You must enter the generic symbol at the latest in the 120th
 character of the key. 
What is this generic symbol that i need to insert at the 120th position??
Message was edited by:
 Kevin Wong
Message was edited by:
 Kevin Wong
Message was edited by:
 Kevin Wong

Thanks Nick!
So the mysterious "generic character" is actually the asterisk (*). It works.
Strange tho as the error long text says to insert the "generic character" at the 120th character position of the key, but I found that altho I can save it, the transport still fails with the same error.
I tried placing the * right after the key value e.g.
KEY123*
and it worked.
Thanks again!

Transport table+data one server to another server

Hi expert,
i have 2 servers DEV1 & DEV 2 with ecc 6.0 oracle 10g.
Both server have same patch level and same version of OS,DB & Patch.
in DEV1 have a table which consist 54500 rows i want move to this table and data in DEV2 server.
Please suggest How can i do this if i create a transport or copies request it move only structure not data.
Regards,

Hi,
It is possible through SAP by creating transport request.
See the below link for how to:
Transporting Table entries from one server to another
[http://****************/Tips/Basis/Transport/TableEntries.htm|http://****************/Tips/Basis/Transport/TableEntries.htm]
Regards.
Rajesh Narkhede

Transport an Appraisal and Objective Setting Template

Note the following advice pertaining to transporting an appraisals and objective setting template (I have not found documentation about this anywhere else, so hopefully some of you find this useful):
Scenario:
You have maintained your templates in PHAP_CATALOG_PA in the main config client, and you have transported all other configurations (basic settings, etc.) to your unit test/integration test environment.
However, although you have right-clicked the category groups and templates to be transported and included them in a transport request, you find that only some of your configuration (or perhaps none at all!) is arriving in the target client when the transport is performed.
You may initially be able to work around this by downloading/uploading your config, but once your templates contain more complex configuration (such as using dynamic element references, etc.) you will find that this is no longer a feasible approach.
Cause & Resolution:
The problem is caused by outdated information in the workflow definition environment (transaction SWU3), and specifically the section labeled "Check Entries from HR Control Tables".
Run transaction SWU3, expand tree node "Maintain Definition Environment" (which should be marked with a red cross at this stage) and click on "Check Entries from HR Control Tables". The information presented in the right-hand pane indicates that:
If there are errors regarding the transport objects PDST or PDWS, the relevant entries are not maintained in table SOBJ. You can use the report RHSOBJCH to rectify this later.
Proceed as suggested and run report RHSOBJCH (through SE38 or SA38) in the config client (i.e. where the templates are to be transported from). This has no side-effects I am aware of other than updating the reference information required.
If you now run SWU3 again you should find that the "Check Entries from HR Control Tables" node is marked with a green tick.
Simply go back to the catalog, include your cat.groups & templates in a transport again, and Voila! Our work here is done.
Happy transporting...
Side-note: You may ask (as I did) what transporting of appraisal templates has to do with workflow, but it just so happens that the PD objects and infotypes associated with appraisals (VA, VB, VC, etc.) are transported through the same mechanism as workflow templates (which are also PD objects). if you peek inside the transport you will note that everything to do with the template and category group configuration is bundled inside PDWS and PDST transport objects...
Edited by: Francois Van Lille on Jun 29, 2009 9:58 AM

>
A. Jimenez wrote:
> Hi Francois,
>
> I have successfully transported Categories and Templates, but I have customized "appraisals process", which seems to create VH Objects, and this objects or customizations are not added in the transport order.
>
> You or anyone know how to transport this customization?
>
> Thanks in advance
Hi Abe,
what is the appraisal process you are talking about? The new stuff in ep4 where you define the process and steps which create the roadmap at the top of the document? if so SAP does not have a great straightforward solution, but they did provide us some options.
you can check out this thread and if you want I can send you the full document that is referred to in the post.
EP4: Performance Management-Flexible-Transporting the Tab & Process config

Performance Management - Transporting "Define Tabs and Process config"

Good Morning Experts,
We are moving from Development into our PPT (pre-production test) environment and have successfully transported the Performance management category settings/values, as well as the Template itself.
Upon executing the Performance Management toolset from the portal side, I see that my tab configuration for the template did not transport. I have searched high and low for any reference to transporting this config step, but have been unsuccessful, thus this post.
Does anyone have any suggestions for transporting this configuration. As you know the IMG Personnel Management > Personnel Development > Objective Setting and Appraisals > Define Tabs and Process Configuration for Template launches a webdynpro app to make this configuration step, so saving these setup selections is the only option. How can I force these changes across ? I look forward to your responses !
Chris Thomas
Duke University and Health System

All - the solution:
SAP Note 1428054, implement the corrections according to the note.
Run the report, RHHAP_Transport_tab_config which will generate the transport containing entries from tables:
hrhap_tab
hrhap_tab_data
hrhap_tab_t
Basis implemented, I ran report, transported the tabs and and all is well.
Chris

Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

Good day to all of you!
I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
Any help, pls?
Good day and thank you!

Hi Alex,
In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
and
Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
      1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
      2. Enhancing online maintenance in customized material master maintenance:
      Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
      In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
      If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
      Application examples for standard field selection:
      The field is mandatory and is to be flagged with a "?".
      The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
      The following data is required for each field:
            a) Field name        (T130F-FNAME)
            b) Field selection group (T130F-FGRUP)
            Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
            You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
            Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
            c) Maintenance status (T130F-PSTAT)
            List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
            d) Reference        (T130F-KZREF)
            This indicator must be set if the field from the reference material should be proposed during creation with reference.
Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
In addition, you must not add new standard fields to table T130F.
      3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
      Add the fields to central field table T130F (see above).
      Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
      Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
      For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
      If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
      Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
      As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
            a) Add the customer-specific fields to include CI_MMH1.
            The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
            Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
            b) Activate include CI_MMH1.
            c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
            d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
check this link. It may helps you to solve your issue.
Thanks
Sravan

Transport Table with Data from Development to Quality

Hi
Requirement:
Transporting Table with Values from Development to Quality System.
I have a Z* - table, appended one field at the end.
I need to transport data along with the table structure from Development System to Quality System.
In Development System, I have assigned the Transport request in Client 100(We can't add data to the table in this client).
What needs to be done to migrate the new table structure with Values.
Thanks in Advance
Regards,
Baburaj
NOTE: the requirement is to transport table and table entries through a transport request.
There should not be any manual update for the table in the target System (Quality System).

Check the delivery class assigned to the table. Please see the documentation
Delivery class
    The delivery class controls the transport of table data when installing
    or upgrading, in a client copy and when transporting between customer
    systems. The delivery class is also used in the extended table
    maintenance.
    There are the following delivery classes:
    o   A: Application table (master and transaction data).
    o   C: Customer table, data is maintained by the customer only.
    o   L: Table for storing temporary data.
    o   G: Customer table, SAP may insert new data records, but may not
        overwrite or delete existing data records. The customer namespace
        must be defined in table TRESC. (Use Report RDDKOR54 here).
    o   E: System table with its own namespaces for customer entries. The
customer namespace must be defined in table TRESC. (Use Report
RDDKOR54 here.)
S: System table, data changes have the same status as program
changes.
W: System table (e.g. table of the development environment) whose
data is transported with its own transport objects (e.g. R3TR PROG,
R3TR TABL, etc.).
or during client copy
the data of client-specific tables is copied.
Classes C, G, E, S: The data records of the table are copied to the
target client.
Classes W, L: The data records of the table are not copied to the
target client.
Class A: Data records are only copied to the target client if
explicitly requested (parameter option). Normally it does not make
sense to transport such data, but is supported to permit you to copy
an entire client environment.
or during installation, upgrade and language import
behavior differs here for client-specific and cross-client tables.
nt-specific tables
Classes A and C: Data is only imported into client 000. Existing
data records are overwritten.
Classes E, S and W: Data is imported into all clients. Existing data
records are overwritten.
Class G: Existing data records are overwritten in client 000. In all
other clients, new data records are inserted, but existing data
records are not overwritten.
Class L: No data is imported.
Cross-client tables
o   Classes A, L and C: No data is imported.
o   Classes E, S, and W: Data is imported. Exisitng data records with
     the same key are overwritten.
o   Classe G: Data records that do not exist are inserted, but existing
     data records are not overwritten.
ehavior during transport between customer systems
Data records of tables of delivery class L are not imported into the
target system. Data records of tables of delivery classes A, C, E, G, S
and W are imported into the target system (this is done for the target
client specified in the transport for client-specific tables).
se of the delivery class in the extended table maintenance
The delivery class is also analyzed in the extended table maintenance
(SM30). The maintenance interface generated for a table makes the
following checks:
o   You cannot transport the entered data with the transport link of the
    generated maintenance interface for tables of delivery classes W and
    L.
o   When you enter data, there is a check if this data violates the
    namespace defined for the table in table TRESC. If the data violates
    the namespace, the input is rejected.
Thanks,

Object extraction to transport table is not complete.

I had applied the patch for BUG 2472140 and BUG 2451096 and exported the transport set with a one page group. I downloaded the Windows NT Command Utility and I saved it as export.cmd
When I run the script with the Export mode set I get an error:
C:\>export.cmd -mode export -s portal -p portal1 -c iasdb -pu orcladmin -pp sszp
ortal1 -company OKSystem -d c:\test.dmp -automatic_merge -check_mode
Mode Selected is EXPORT
Error: Object extraction to transport table is not complete.
Please try again later.
Export/Import aborted.
I have waited for 2 days, but it doesn't help. I tried the same with application and it worked fine.
Thanks for help.
Martin Rosol

This could have happen when the background job in the Job_Queue is still waiting to get executed completely. You could do the following...
1. Login to SQL*Plus as Portal Owner.
2. Execute the following SQL statements...
select export_id,name,status from wwutl_export_import$;
(This will list you all the transport sets available ; Identify your transport set here)
delete from wwutl_export_import$ where export_id = '(Export Id you found out just now)';
3. Then Export the Pagegroup again to create a new transport set.
4. Download the script and run it after the status of the transport_set becomes 'EXTRACT_COMPLETE'
Thanks,
Arun

Transport Table Maintainance

Hi,
I am currently working on merging two SAP systems. I was wondering what the best way is to transport table maintainance?
Thank you.
/Elvez

Hi Elvez,
This is very easy..
You will need to transport the function group of the table maintenance in a transport.
There are two ways:
1) You can transport the database table and this function group together and there will be no problem.
2) If you are transporting the function group in a separate transport, make sure that the transport for the database table is already moved.
Thanks and Best Regards,
Vikas Bittera.
**Points for useful answers**

Transport table settings of standard transaction (Exemple CS02)

Hello,
Do you know how to transport tables setting ?
Especially system variants which are visible to all users in the current client (although user-defined
variants, where they exist, override system variants). They can be edited using the 'Administrator' function.
Best regards,
MV

Hi,
Running RPULCP00
The simplest way is to go into the table through SM31
Then in your top row of buttons there should be one called 'utilities' from here select 'adjust',
Then select the client that you want to compare/copy from (you need to have an RFC destination set up).
This will then show you the contents of the table in both clients and identify the status of each record, they will fall into the following categories:
ML Differences, logon client entry
MR Differences, comparison client entry
L Entry only exists in logon client
R Entry only exists in comparison client
Identical entries
(M) Differences only in hidden fields
You should be able to scroll down the table, select the entries that you want to import, then hit the 'adjust' button, then hit the 'copy all' button, then back out with the green arrow, and save your table.
That should do the job.
Program variants
If you have several program variants in a development system that you want to transport, use the following method to transport them:
Execute program RSTRANSP (via se38) and inform the program and/or variant names (you can transport variant of several programs in one shot).
Regards
Sreedhar Reddy

Copy Z table structure and contents

Hi all,
I am looking at a quick and easy way to copy a Z Table structure and its contents from
one system to another completely different system on different servers and locations.
Is this possible?
Thanks

Yes its possible Try to transport the request
The request should contain your required objects
Contact your basis admin he will do the transport the request from OS level.
Then Go and change the SID in the table TADIR
And Give the object name and change the SID of the object then it allows you to change as per the new requirement.
Hope This will help you.
Regards,
Madan Mohan.

Pooled tables m_vmvlb and m_vmvla in ECC6.0

Hi,
We are upgrading system from 4.6C to ECC6.0. But in ECC6.0 pooled tables m_vmvlb and m_vmvla have been deleted. Now these tables have been used in a customize program. So do we need to create the tables with similar structure or there is any OSS note that need to be implemented ??
Please reply as soon as possible. Our deadlines are near.
Regards
Puneet.

just transport the table from the development server to production server or viseversa.
see if you are upgrading the server PRD then Tranport it from the DEV.orelse
if You are upgrading the server DEV then Tranport it from the PRD .
Girish

Transport Table T77PR and T77PQ

Similar Messages

Maybe you are looking for