on 02-22-2006 9:50 AM
Hi,
While assigning infosource to datasource, we are getting an error saying "Field length in the structure is greater than 16 (Message type E)".
After debugging we found that in the table RSADMIN there should be an entry with
object = RSAR_LONG_FIELDNAME and
Value = Comm.structure name.
We were not able to find the maintanance view or transaction to maintain this entry.
Any idea from where can we maintain this value would be very much helpful.
Thanks .
Regards
Nimesh
hi Nimesh,
there is oss note, run program (transaction se38) SAP_RSADMIN_MAINTAIN to maintain.
hope this helps.
660239-Transfer rule: Enable 'long field names'
Symptom
Due to an error with the field length check (see note 660200), PSA tables may be generated with field names that are too long.
In the case of existing DataSources with field name lengths that do not correspond to the SAA Standard, you can enable the continued use of the relevant PSA tables for specific objects.
Note the following points:
These tables are identified as incorrect during the check with the repository tool and cannot be checked or activated with transaction SE11, for example. The tables in question belong to the '/BI+/B*' namespace.
In general, no restrictions in BW functions are to be expected with such PSA tables.
However, problems may occur with migration. The contents of these tables may not be transferred.
Therefore, in the long-term, you should use PSA tables that conform to the SAA Standard. Here you should note that a a new PSA version is generated after the field names are shortened if the current version contains data.
If a reconstruction from the PSA is required, the old PSA versions cannot be processed using the 'new' transfer rules. In this case, a generic DataSource must be generated for the 'old' PSA table with its own transfer rules, so that the contents of the changed field names can be transferred into the InfoObjects.
Never use this workaround as the 'default' for 'new entries' to enable long field names in the case of PSA tables. It is only provided so that you can continue to use your existing transfer rules even if the maximum field name length is exceeded. You can also use it to enable long field names for other reasons. In this context, explicit reference is made to the potential conflict described above.
Reason and Prerequisites
Note 660200 is a prerequisite for the workaround below.
<i>Solution
Proceed as follows:
Execute the SAP_RSADMIN_MAINTAIN program.
Enter the value RSAR_LONG_FIELDNAME in the 'OBJECT' field.
As of Support Package 16 (3.0B) and 10 (3.10 Content), you can take the name of the transfer structure from the longtext of error message RSAR 492. Enter this in the 'VALUE' field.
For lower Support Packages, you can take the name of the transfer structure from the TRANSTRU field of the RSISOSMAP table with:
OLTPSOURCE = Name of the DataSource
LOGSYS = Name of the source system</i>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi AHP,
Thanks for the perfect solution.
Regards
Nimesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
you need to shorten the datasource field. Replicate the datasource again, do the mapping and activate the transfer rules. It will work then.
If will create a entry in table rsadmin, try fm RSA2_RSADMIN_PUT.
regards
Siggi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.