hi S.,
take a look oss note 545923.
i think you won't have problem, we had enhanced 100+ fields with total 300+ infoobjects and no problem.
hope this helps.
545923
Symptom
[1.] Question: What are the technical restrictions for characteristics?
[2.] Question: What is the length restriction in the SAP Data dictionary?
[3.] Question: What are the technical restrictions when loading data?
[4.] Question: Is there a limit to the tRFC structure?
[5.] Question: What restrictions are there in the customer namespace?
[6.] Question: What characters are allowed in BW?
Solution
[1.] Question: What are the technical restrictions for characteristics?
Answer:
The technical restrictions for characteristics are as follows:
Length:
Characteristic values can have a maximum of 60 characters. This includes the concatenated value, which is the total of the lengths of the characteristics in the compound plus the length of the characteristic itself.
Length of the texts:
The text table can have up to 3 text fields, a short text (20 characters), a medium text (40 characters) and a long text (60 characters).
Compound characteristics:
A characteristic can contain a maximum of 13 more characteristics in the compound.
Attributes:
A characteristic can have a maximum of 250 attributes up to BW 2.0, and a maximum of 750 attributes up to 3.0.
[2.] Question: What is the length restriction in the SAP Data dictionary?
Answer:
SAP supports all standard hardware and software platforms for its products. With the database systems supported by SAP, there are different length restrictions for tables. With the restriction to 1962 bytes, the possible use of a two byte solution is already taken into account so that an increase of the value to 4000 bytes is in fact possible in almost all environments.
Unicode is enabled with SAP Basis 6.20. However, the required minimum release of the database platforms support a larger table width, so that that restriction was extebded ti 4030 characters with Basis Release 6.20. The enhancement is contained in Support Package 25.
As a result, the restriction of 1962 characters in lower releases is no longer valid. It can be extended to 4000 characters. We recommend that you do not extend it any further than this.
See note 636217.
<b>For detailed information, see note 355898 (Restrictions for transparent tables) and note 636217 (DDIC activation errors due to table widths less than 1962 bytes).</b>
[3.] Question: What are the technical restrictions when loading data?
Answer:
The technical restrictions when loading data are only apparent by the maximum width of the PSA table. This is 1962 bytes. It includes the request number, date packet number, partition ID and record number.
This applies to flat files, export data sources and to staging BAPIs, since all must have the transfer structure.
[4.] Question: Is there a limit to the tRFC structure?
Answer:
No. The 1000 byte field in the tRFC structure does not act as a limit, because the structure has a continuation indicator. This allows you to split up longer transfer structure records into several parts.
[5.] Question: What restrictions are there in the customer namespace?
Answer:
In the customer namespace of objects in BW 1.2B and BW 2.0, BW 3.0 with standard character set there are restrictions for InfoObjects, InfoSources, InfoCubes, queries, aggregates and InfoPackages and InfoPackageGroups.
For more detailed information see note '160317 Customer namespace of objects in BW'.
[6.] Question: What characters are allowed in BW?
Answer:
In BW, characteristic indicators can usually only be loaded if they consist of the following characters:
!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ
Special national characters are not included here. These can be additionally allowed in the BW customizing guide, provided they are capital letters.
If there are very many special characters (for example Asian character set), this procedure cannot be used.
If you enter the character string "ALL_CAPITAL" and nothing else when maintaining the allowed additional characters, characters are permitted during data loading that are capital letters in the codepage. For detailed information, see note 173241 (permitted characters in BW).
355898
Symptom
Transparent tables cannot be activated.
Other terms
Activation, SE11, limitation, restriction
Reason and Prerequisites
One of the restrictions of the table activation program becomes effective.The restrictions are specified in a way that the SAP database independence can always be granted.This note summarizes the restrictions on transparent tables.
Solution
The following restrictions apply:
Table width 1962bytes or less (4030 bytes or less as of Release 6.20 SupportPackage25 )
Key length 255 bytes or les
Field number 249 fields or less (749 fields or less as of Release 46A )
Key columns 16 fields or less
Bufferingis only possible if key length is 120 bytes or less.
Generic buffering is only possible if key length is 32 bytes or less(64 bytes or less as of Release 40A)
636217
Symptom
Activation error DO 322 occurs when a transparent table is activated, since the table width exceeds 1962 bytes.
Other terms
D0322, D0 322
Reason and Prerequisites
Since SAP supports several different database platforms, the ABAPData Dictionary must ensure that tables are defined so that they can be created on all of the supported platforms. The limit of 1962 bytes already takes into account the possibility that you may want to use a two-byte Unicode solution. In each case, we have also considered the minimum release of the database platforms for an SAP R/3 Release.
Unicode is enabled as of SAP Basis 6.20. However, the minimum releasesof the database platforms that are compatible with this SAP release support a larger table width, so the restriction has been extended from 1962 to 4030 characters as of Basis Release 6.20. This enhancement is implemented in Support Package 25.
This also renders obsolete the restriction to 1962 in earlier SAP releases.You can increase the table width restriction to 4030 characters. We do not recommend that you increase the restriction to a value greater than 4030 characters.
Solution
To increase the restriction, the value of the TABLES constant in the RADTBCON program must be changed.
The following paragraph only applies to Basis releases lower than 610:
Once you have changed the constant in RADTBCON, this change must alsobe made for RESULT_WA in the LSDFCTOP include. Otherwise "SAPSQL_SELECT_WA_TOO_SMALL" terminations would be triggered if the program were to use a table that exceeds the former limit as a check table in a foreign key dependency.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.