Unable to transport custom table entries having * in its key field

[former_member553808]

One of the key fields in a z table has data type char1 and it can hold values like C or D or *.

When entries are maintained with value C or D and transported, entries are available in Prod.

But only when the value * is in that field and transported, table entries are not reflecting in higher systems.

Transport log has no errors.

As a workaround solution, deleted all entries in Q and Prod. Maintained all entries including *, C or D at a time in Q and transported to production, entries with * also available in Prod.

Please advise for a permanent solution or what could be the issue here.

[former_member553808]

Hi All,

I am waiting for your inputs. Please help

[kiran_k8]

Strange.May be we are missing something here in the problem statement.

Hope this query will attract the attention of the experts.

K.Kiran.

[matt]

What's the stucture of your table. What are its technical settings? How is it defined?

[former_member553808]

Table fields below:

MANDT Key field, data type CLNT, Length 3
INTERFACE_ID Key field, data type CHAR, Length 20
KONTO Key field, data type CHAR, Length 10
LOSSY Key field, data type CHAR, Length 1
DIR_IND Key field, data type CHAR, Length 1
SAKNR data type CHAR, Length 10
BEWAR data type CHAR, Length 3
LDGRP data type CHAR, Length 4

Delivery Class : C

Data Class : APPL0

Size Category : 0

Recording Routine: Standard

Transparent table

In tcode SOBT, Category - CUST

Transport - Automatic transport

Adjustment - Automatically adjustable

Here, when fields LOSSY or DIR_IND have '*' as its value, those entries are not transported from Quality to Production.

[Domi]

Hi

Can you please check the key values for the table content transport entry (R3TR TABU)

Since * is used there for generic key values this may cause some troubles:

e.g.: key entry '010*' will include all entries from the current client (010) in the transport request

regards

Domi

[former_member553808]

Thanks. Rreceived response from SAP through OSS message. Recommended not to use * as it is not supported.