Transporting table entry with primary key > 120 char

[Former Member]

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:....

<i>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.</i>

<b>How do I transport the table entries "generically" for such a table?</b>

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 <u>Table Entry > Transport Entries,</u> but get an error that says

<i>"Key entry for table MIMETYPES may only be generic"</i>.

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 "<i>The key is longer than allowed by the Change and Transport System (120 characters</i>)."

The Procedure says:

<i>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. </i>

<b>What is this generic symbol that i need to insert at the 120th position??</b>

Message was edited by:

Kevin Wong

Message was edited by:

Kevin Wong

Message was edited by:

Kevin Wong

[Former Member]

You need to add an asterisk * to the end of the key, the transport will perform a match on every entry that starts with that key.

Regards,

Nick

[Former Member]

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!