Query regarding Transporting Table entries

[Former Member]

Hi All,

I'm referring to a blog (http://wiki.sdn.sap.com/wiki/display/ABAP/TransportingTableEntriesinABAP+programmatically), and have written my program to add my table entries to a transport request. It's all working fine generally...

But I've some issues and queries, that I'm struggling with:

1. The field

lv_tabkey TYPE trobj_name

is of length 120 CHAR only. So I'm not able to add the keys of a table whose key fields incidentally span more than 120 CHAR total, when concatenated. So is there any other way such tables can be added to a transport request?

2. Does anyone knows if there'd be any problems in customer production systems if entries of a table with Delivery Class as W, are added to a transport request this way?

Thanks in Advance!

[Former Member]

Hi All,

I'm referring to a blog (http://wiki.sdn.sap.com/wiki/display/ABAP/TransportingTableEntriesinABAP+programmatically), and have written my program to add my table entries to a transport request. It's all working fine generally...

But I've some issues and queries, that I'm struggling with:

1. The field

lv_tabkey TYPE trobj_name

is of length 120 CHAR only. So I'm not able to add the keys of a table whose key fields incidentally span more than 120 CHAR total, when concatenated. So is there any other way such tables can be added to a transport request?

2. Does anyone knows if there'd be any problems in customer production systems if entries of a table with Delivery Class as W, are added to a transport request this way?

Thanks in Advance!

[JL23]

SAP OSS note 38298 explains how to do it manually.

follow the instructions, use the debugger and see how SAP is managing it if you have keys that exceed the 120

[Former Member]

Thanks Jürgen. That note just explains everything that I already know myself. I'm in fact trying to develop a program which can be used by customers to automatically add their specific table entries to a transport request automatically, so that they can transport these entries to their other systems within landscape.

Moreover, I did check the manual entry part, and noticed that SAP does NOT really handle this at all... Here's the error message I got:

Message no. TK320

Diagnosis

For technical reasons, you cannot specify the table key of table XXXX in its full length. Instead you must specify it generically. There are two possible reasons for this:

1. Table keys with packed fields or fields of type I can only be specified up to the first of these key fields.

2. The key is longer than allowed by the Change and Transport System (120 characters).

Procedure

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.

Edited by: Rob Burbank on Oct 18, 2011 12:50 PM

(Removed code tags)

[Sandra_Rossi]

Hi,

If you give the user the possibility to transport one entry, I don't see other choice than implementing a "before export" and "after import" methods (SOBJ transaction, these are in fact function modules with a specific interface), so that to encode and transfer the entry to a table with a shorter key, transport this entry, then during the import decode it and transfer it to the right table.

Sandra

[Former Member]

Hi Sandra,

As i mentioned, I need to provide a program that can add multiple records (specified by user) automatically. In fact the user would only select a set of functional objects, and the program would find out all the related table entries and add them to a transport request. Most of the table keys are fine, except one table that has the key length more than 120 CHAR