2008 Mar 18 9:46 PM
Hi All,
According to the requirement I have to make the CURR type field as the key field in one of the table. But dureing activation it's throwing the below warning :
Key field <Field name> has num. type CURR: Buffering not possible, Transport restricted
Message no. DT607
Diagnosis
A numeric type was used for a key field. A table of this sort cannot be buffered.
When buffering, the table records for numeric values cannot be stored in plain text. Therefore, no entries are found when buffered numerical values are compared in the WHERE condition, although the table can contain entries satisfying the compare criterion.
The contents of the table cannot be transported if you specify the full key. You can only tranport table contents specified with a character field, up to the first occurrence of a numeric key field.
Procedure
You can enter "no buffering" as an attribute of the technical settings and then repeat the activation process. The table is not buffered.
If you want to buffer the table, you must replace the type in the key field by a character type, i.e. that you must modify the table.
If you want to transport the contents of a table, you can only do so for records specified by a character key, up to the first occurrence of a numeric field.
Is this will be a problem when we transport the entries of the table from DEV to QA ???
If yes how we can solve this problem??
Thanks for your help in advance.
Thanks,
Greetson
Hi All,
According to the requirement I have to make the CURR type field as the key field in one of the table. But dureing activation it's throwing the below warning :
Key field <Field name> has num. type CURR: Buffering not possible, Transport restricted
Message no. DT607
Diagnosis
A numeric type was used for a key field. A table of this sort cannot be buffered.
When buffering, the table records for numeric values cannot be stored in plain text. Therefore, no entries are found when buffered numerical values are compared in the WHERE condition, although the table can contain entries satisfying the compare criterion.
The contents of the table cannot be transported if you specify the full key. You can only tranport table contents specified with a character field, up to the first occurrence of a numeric key field.
Procedure
You can enter "no buffering" as an attribute of the technical settings and then repeat the activation process. The table is not buffered.
If you want to buffer the table, you must replace the type in the key field by a character type, i.e. that you must modify the table.
If you want to transport the contents of a table, you can only do so for records specified by a character key, up to the first occurrence of a numeric field.
Is this will be a problem when we transport the entries of the table from DEV to QA ???
If yes how we can solve this problem??
Thanks for your help in advance.
Thanks,
Greetson
2008 Mar 19 6:42 AM
you cannot transport entries with a transport request (TABU)
but it should be no problem to fill table in another system with your own export-/import program per file-download/upload or per RFC.
hope that helps
Andreas
2008 Mar 19 6:47 AM
Hi,
chk if this blog can help u
/people/community.user/blog/2007/01/07/transport-table-entries
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |