SAPKE60027 - "T591A" contains invalid key fields

Hi,
I'm busy applying Support Packages for ERP 6, the BASIS and ABA patches were loaded success fully, but when loading the HR queue the implementation of SAPKE60027 stops with an error:
Error in phase: XPRA_EXECUTION
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package SAPKE60027, tp step R, return code
0008
Post-import method AFTER_IMP_NROB started for NROB L, date and time: 20100913210327
2EENR397HThe subobject value table "T591A" contains invalid key fields
2EENR893INumber range object "HR_ZA_LABR" " "
Errors occurred during post-handling AFTER_IMP_NROB for NROB L
AFTER_IMP_NROB belongs to package SZN
The errors affect the following components:
BC-SRV-NUM (Number Range Management)
Post-import method AFTER_IMP_NROB completed for NROB L, date and time: 20100913210328
does anyone have an idea what to check?
thanks,

Hi Rainer,
Thank you, I got the same problem and resolved by implemention the SAP Note 1484591
Regards,
Sandeep

Similar Messages

What Oracle Table contains Partition Key Field Name?

What Oracle table/view maintains the partition key field name?
All_Tab_Partitions does not appear to maintain such information.
When I use Toad -> Schema -> Tables -> Partitions, it lists the partition key field name that the partition is based.
Thank You

all_part_key_columns
or
USER_part_key_columns
Edited by: OrionNet on Dec 5, 2008 3:56 PM

Add key fields for FM REUSE_ALV_HIERSEQ_LIST_DISPLAY

Hi everyone,
I would like to ask if it is possible or is there a way to increase the number of key fields used in FM REUSE_ALV_HIERSEQ_LIST_DISPLAY. The table parameter for the key fields is IS_KEYINFO. It can only contain 5 key fields. My program needs to have 7 key fields. I cannot modify type group SLIS to add more fields in its type declaration since it is a global object.
Thanks,
Eric

Hi everyone,
I would like to ask if it is possible or is there a way to increase the number of key fields used in FM REUSE_ALV_HIERSEQ_LIST_DISPLAY. The table parameter for the key fields is IS_KEYINFO. It can only contain 5 key fields. My program needs to have 7 key fields. I cannot modify type group SLIS to add more fields in its type declaration since it is a global object.
Thanks,
Eric

Invalid text value. A text field contains invalid data. Check the value and try again

Hello,
I am having a problem with the error mentioned in the title. I see alot of others have experienced the same problem, but I have quite a twist to it.
I see the problem when I try to edit a list item, and then try to save the changes.
Here what I see in the ULS log:
System.Runtime.InteropServices.COMException: Invalid text value. A text field contains invalid data. Check the value and try again
at Microsoft.SharePoint.Library.SPRequestInternalClass.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId,
Boolean bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter
pListDataValidationCallback, ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
at Microsoft.SharePoint.Library.SPRequest.AddOrUpdateItem(String bstrUrl, String bstrListName, Boolean bAdd, Boolean bSystemUpdate, Boolean bPreserveItemVersion, Boolean bUpdateNoVersion, Int32& plID, String& pbstrGuid, Guid pbstrNewDocId, Boolean
bHasNewDocId, String bstrVersion, Object& pvarAttachmentNames, Object& pvarAttachmentContents, Object& pvarProperties, Boolean bCheckOut, Boolean bCheckin, Boolean bMigration, Boolean bPublish, String bstrFileName, ISP2DSafeArrayWriter pListDataValidationCallback,
ISP2DSafeArrayWriter pRestrictInsertCallback, ISP2DSafeArrayWriter pUniqueFieldCallback)
I have 3 front end servers(fx wfe1, wfe2, wfe3). And here is the twist.
If I access the library directly through wfe1 and wfe2, I get the error. If I access the library via wfe3 if works just fine.
So because of this, I think it is safe to assume that is has nothing to do with the character limit of 255. Nor does it have anything to do with the field type, since it is already set to mulitible lines of text.
So. Any ideas?
Regards,
Michael
mic

Check if there is any change in web.config of these servers
http://support.microsoft.com/kb/2880758
To work around this issue, limit the length of the personal message in the invitation to 256 characters or less.
This is a known issue. Microsoft is working to resolve this issue.
http://social.msdn.microsoft.com/Forums/en-US/7bb16e51-e7cc-439e-a8b3-755683ccac1a/max-length-on-custom-field-types
To solve the problem you may have to change the field's parent type to "note". To do that you have to open your fldtypes... file under Templates/xml and change the line to:
"<Field Name="ParentType">Note</Field>" from "<Field Name="ParentType">Text</Field>"
You might also have to add a sql type if your text needs to be longer than 255 characters
<Field Name=”SQLType”>ntext</Field>
and inherit from SPFieldMultiLineText instead of SPFieldText
If this helped you resolve your issue, please mark it Answered

Data Fields & Key Fields IN DSO

Hi Guys,
Can any one tel me what exactly key field holds & Data field hold in DSO.
Thanks,
Venkatesh

Hi,
A DSO serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level. This data can be evaluated using a BEx query.
A DSO contains
Key fields (such as document number, document item) and data fields that, in addition to key figures, can also contain character fields (such as order status, customer). The data from a DataStore object can be updated with a delta update into InfoCubes (standard) and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.
Key fields : It will contains both Chars and KeyFigures.
Data Fields : Based on this i.e. the charecterisctics which you will keep in this Data Fields, the DSO will over write the Data in DSO.
Overwriting functionality will works based on Data Fileds.
http://help.sap.com/saphelp_nw2004s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm
Thanks
Reddy

Key fields and data fields re-arranged

Hello SDN,
Which design contains more records due to it showing more granularity? :
1. ODS with more infoobjects assigned as Keys.
2. ODS with less infoobjects assigned as Keys.
assuming the total number of infoobjects remain the same.
Where data fields can contain characteristics that can be used as keys or non-keys, depending on choice of design.
My understanding is with more keys, less details available due to aggregation. Could you kindly help to confirm this is correct?
I need to ask this because I am trying to change the re-arrange the keys by putting data fields as keys but not sure how this will turn out / behave.
Thanks,
Suzie

Hi,
BUT! I cannot say that it will increase. That means, I think the record number remains the same!
I do not think that this is Right?
for ex:
1)
Key fields:
Billing document
Data Fields
Sales Office
Customer
Net sales
So in the update rules , you can see the Overwrite for all Data fields. If the sales office is chaged for a record , the the OLD value will be over written by new value. So Before and after change to the records, the no of records are equal to 1.
2)
Key fields:
Billing document
Sales Office
Data Fields
Customer
Net sales
So in the update rules , you can see the Overwrite for all Data fields(now not for 'Sales Office'). If the sales office is chaged for a record , the the OLD value will not be over written by new value. It creates 2 records in Active table with respect to one change in new table. So Before the change , the no of records was 1.now after change, the records' number becomes 3.
With rgds,
Anil Kumar Sharma .P

ODS Key Fields allows blank values in Transformation

Dear Experts,
I have two layers:
1. Datawarehouse layer (purpose is to represent exactly data at the backend)
2. Consolidation Layer
Scenario 1:
In Datawarehouse layer, the fiscal variant is a key field in ODS and I have two other key fields i.e. combine to form a composite key.
When I load the data from PSA to this ODS, I have a record which contains blank value for the fiscal variant. It successfully loads into the Datawarehouse ODS.
Sceanrio 2:
In the consolidation layer, i have 4 key fields out of which fiscal variant is one of them. Now when I load the data from the datawarehouse ods to consolidated ods, it throws an error saying:
Diagnosis
     An exception fiscvarnt_missing was raised while executin
     module RST_TOBJ_TO_DERIVED_TOBJ .
System Response
     Processing the corresponding record has been terminated.
The transformation mapping for the fiscal varaint in both sceanarios is 1:1 mapping with the rule type 'Time Characteristic'.
My questions is:
1. Why different behaviour during scenario 1 and sceanario 2
2. Solution to the above issue
Thanks
Jain

Thanks J.S.
Yes the format selected in the field for the datasource is 'Internal'.
When loading the data from R3>PSA>ODSX(Datawarehouse Layer), I have no problems even when the field is blank.
When loading from ODSX-->ODSY(Consolidated Layer) the empty (blank) field for that records throws error.
Any ideas?
Jain

Key fields and non-key field of condition table

Hello Gurus,
what is key fields and non-key field of condition table?
thanks very much!

Key field
Each condition table contains keys that can be used for creating dependent condition records.
for example let take condition type PR00.
PR00 uses access sequence PR02 .
Access sequence PR02 has following tables associated with it namely 304, 305 & 306
When you create a conditon record for PR00 with transaction VK11 or VK31, you have a button 'key combination' which is nothing but fields associated with tables 304, 305 & 306.
In brief, Condition records are always created using specific keys. Condition tables are used to define the structure of the keys of a condition record.
Non key field
For example take condition table 144 - sales deal basic data.
Table 144 is associated with access sequence PBUD.
If you check the fields associated with this table (click technical view button), there are three fields at bottom which do not have 'key' check mark -KDATU, PLTYP, KSTAF
So, when you create a condition record for PBUD, system does not propose these 3 fields in 'key combination' and hence are non key fields.
Please reward points for good answers as this would help increase the total donation that SAP will make to the United Nations World Food Programme.

Invalid Key code Error while installing crystal report server 11

While installing crystal report server 11,i am facing an erro which says Invalid Key code Error.I had raised this issue to SAP customer support and attaching the conversation that we had.PLEASE HELP me to resolve the issue.
MAILS--Dear Mohit,
Thanks for the patience.
We have received the below update from the Licensing Team.
You received your permanent key in respect of these licenses - the key is for Crystal Reports Server XI.
You did not purchase these licenses for Crystal Reports Server, but purchased it for Crystal Reports and a 5-named user license for Crystal Reports was included as a special offer. The software included was version XIR2, but you elected to use version XI instead and received key .
You would need to enroll the licenses in maintenance if you want to upgrade them.
In case of any queries please create a ticket via the Service Market Place.
Regards,
Jessy
Customer Interaction Center
SAP Active Global Support
Hello Jessy,
The customer received their permanent key in respect of these licenses - the key is for Crystal Reports Server XI.
They did not purchase these licenses for Crystal Reports Server, they purchased Crystal Reports and a 5-named user license for Crystal Reports was included as a special offer. The software included was version XIR2, but they elected to use version XI instead and they received key .
They cannot decide to upgrade now - they must enrol these licenses in maintenance if they want to upgrade them.
Kind regards,
Rosemary
From: BOSAPASIA
Sent: 29 September 2009 05:49
To: Savage, Rosemary
Subject: FW: Crystal Reports Server Installation Issue
Importance: High
HI Rose ,
Need your assistance on the below issue.
Customer purchased Crystal Report Server XI R2 in 2005. When he is trying to install it now, he is getting an Invalid Key code Error.
He has provided us the Scanned copies of the Key code and the registration number.Can you please help and check if he can be provided with a Keycode.
Regards,
Jessy
CIC Team Lead
Customer Interaction Center
Global Support Centre India
SAP Labs India Pvt Ltd
Hi,
Providing you with the required details to proceed further
Registration Number-
Registration Email Address-taxmantra.support
And also please find attached the scanned copy of the Registration key we got for the Crystal report server.
Dear Mohitk,
Thank you for your information.
I checked with the concerned colleague and received the below update:
Please check from where you got this key code. If from a paper, please scan it to us. Please let them track to the original paper or email.
If you have registered the key code, please provide us the registration number or registration email address so that we will try to check for you.
If you did not register before, as the promotion is over so the key code could not be replaced.
I request you to kindly check the same at your end and revert with the details.
Moreover, there are two ways for Crystal Report customer to get support.
One is customer with bundled product such like BOE and under maintenance. These customers will have an S-user ID and password to log a case in service market place via http://service.sap.com/message
A learning map was provided, listed on left column.
The other is customer with only Crystal report product, the support is via SDN.
http://service.sap.com =>Crystal Reports and Xcelsius Support=>Crystal Reports and Xcelsius Forums
Customers can first check whether other customer has got the same issue and find the reply from our engineers.
You may also post your own thread for support.
Anything else I could help, please do not hesitate to contact again.
Hi,
I am providing you with the details required to resolve the issue related to Crystal report installation,for reference of the issue please refer the mail below.
Please find attached the Scanned Document containing the details as per the details required by you.
Hope to see a quick resolution for the issue.
Dear Mohit,
Thank you for your e-mail.
As discussed, I understand that youu2019ve procured Crystal Reports Server 11 in 2006. However youu2019re facing issues with key codes while reinstalling the same. We request you to kindly provide us with below details for further assistance.
Your customer number:
Your customer name and address:
Purchase order number:
Any other products purchased along with Crystal Reports Server 11
Any S-User Id:
Any old case ID:
Please feel free to contact us if any further queries.
Hi,
I am raising this concern on behalf on Taxmantra project (Tata Consultancy Services noida).
We have bought licensed Crystal Reports Server 11 near by 2006.We are trying to install the crystal server but while installing ,we have encountered with an error message that:-
"The product key code you have entered is incorrect"
We are facing the same issue in 2006,I am attaching with this email the conversations that was held in 2006 to get the correct key code.
Please help us to resolve the issue as early as possible.
My contact number:
If you need any further information do let me know

Ajit,
By design, the product is not able to be installed under the superuser account.
1. Create a new user and specify a home directory for the user without a quota set.
2. Copy or move the installation files to a directory that the new user can read. I suggest you move the installation files directly into the new user's home directory.
3. Logon as the new user (or su - newuser)
4. run the installation shell script using that new user's account.
NOTE: Ensure the system meets the requirements from the supported platforms documents.
.Tony

Changing the length of a key field in a table

Hi,
I want to increase the length of the field from 2 to 4 in a standard SAP table and deliver it to the customers. This field is a key field in table. This field from this table is also used in view and view clusters.
What is the implication of changing the length to the customers. The customers would have already data in this field and they should not loose any data. Will the existing data for customers remain at length 2 or do they have to do some conversion?
Regards,
Srini.
Edited by: Srinivasa Raghavachar on Feb 7, 2008 12:45 PM

hi,
The database table can be adjusted to the changed definition in the ABAP Dictionary in three different
ways:
By deleting the database table and creating it again. The table on the database is deleted, the inactive
table is activated in the ABAP Dictionary, and the table is created again on the database. Data
existing in the table is lost.
By changing the database catalog (ALTER TABLE). The definition of the table on the database is
simply changed. Existing data is retained. However, indexes on the table might have to be built again.
By converting the table. This is the most time-consuming way to adjust a structure.
If the table does not contain any data, it is deleted in the database and created again with its new
structure. If data exists in the table, there is an attempt to adjust the structure with ALTER TABLE. If the
database system used is not able to do so, the structure is adjusted by converting the table.
Field 1     Field 2,    Field 3
NUMC,6 CHAR 8    CHAR, 60
Field 1    Field 2       Field 3
NUMC,6 CHAR, 8     CHAR,30
The following example shows the steps necessary during conversion.
Starting situation: Table TAB was changed in the ABAP Dictionary. The length of field 3 was reduced
from 60 to 30 places.
The ABAP Dictionary therefore has an active (field 3 has a length of 60 places) and an inactive (field 3
still has 30 places) version of the table.
The active version of the table was created in the database, which means that field 3 currently has 60
places in the database. A secondary index with the ID A11, which was also created in the database, is
defined for the table in the ABAP Dictionary.
The table already contains data.
Step 1: The table is locked against further structure changes. If the conversion terminates due to an
error, the table remains locked. This lock mechanism prevents further structure changes from being
made before the conversion has been completed correctly. Data could be lost in such a case.
Step 2: The table in the database is renamed. All the indexes on the table are deleted. The name of the
new (temporary) table is defined by the prefix QCM and the table name. The name of the temporary
Step 3: The inactive version of the table is activated in the ABAP Dictionary. The table is created on the
database with its new structure and with the primary index. The structure of the database table is the
same as the structure in the ABAP Dictinary after this step. The database table, however, does not
contain any data.
The system also tries to set a database lock for the table being converted. If the lock is set, application
programs cannot write to the table during the conversion.
The conversion is continued, however, even if the database lock cannot be set. In such a case
application programs can write to the table. Since in such a case not all of the data might have been
loaded back into the table, the table data might be inconsistent.
You should therefore always make sure that no applications access the table being converted
during the conversion process.
Step 4: The data is loaded back from the temporary table (QCM table) to the new table (with MOVECORRESPONDING).
The data exists in the database table and in the temporary table after this step.
When you reduce the size of fields, for example, the extra places are truncated when you reload the
data.
Since the data exists in both the original table and temporary table during the conversion, the storage
requirements increase during the process. You should therefore verify that sufficient space is available in
the corresponding tablespace before converting large tables.
There is a database commit after 16 MB when you copy the data from the QCM table to the original
table. A conversion process therefore needs 16 MB resources in the rollback segment. The existing
database lock is released with the Commit and then requested again before the next data area to be
converted is edited.
When you reduce the size of keys, only one record can be reloaded if there are several records whose
key cannot be distinguished. It is not possible to say which record this will be. In such a case you should
clean up the data of the table before converting.
Step 5: The secondary indexes defined in the ABAP Dictionary for the table are created again.
Step 6: The temporary table (QCM table) is deleted.
Step 7: The lock set at the beginning of the conversion is deleted.
If the conversion terminates, the table remains locked and a restart log is written.
Caution: The data of a table is not consistent during conversion. Programs therefore should not access
the table during conversion. Otherwise a program could for example use incorrect data when reading the
table since not all the records were copied back from the temporary table. Conversions therefore
should not run during production! You must at least deactivate all the applications that use tables to
be converted.
You must clean up terminated conversions. Programs that access the table might otherwise run
incorrectly. In this case you must find out why the conversion terminated (for example overflow of the
corresponding tablespace) and correct it. Then continue the terminated conversion.
Since the data exists in both the original table and temporary table during conversion, the storage
requirements increase during conversion. If the tablespace overflows when you reload the data from the
temporary table, the conversion will terminate. In this case you must extend the tablespace and start the
conversion in the database utility again.
If you shorten the key of a table (for example when you remove or shorten the field length of key fields),
you cannot distinguish between the new keys of existing records of the table. When you reload the data
from the temporary table, only one of these records can be loaded back into the table. It is not possible
to say which record this will be. If you want to copy certain records, you have to clean up the table
before the conversion.
During a conversion, the data is copied back to the database table from the temporary table with the
ABAP statement MOVE-CORRESPONDING. Therefore only those type changes that can be executed
with MOVE-CORRESPONDING are allowed. All other type changes cause the conversion to be
terminated when the data is loaded back into the original table. In this case you have to recreate the old
state prior to conversion. Using database tools, you have to delete the table, rename the QCM table to
its old name, reconstruct the runtime object (in the database utility), set the table structure in the
Dictionary back to its old state and then activate the table.
If a conversion terminates, the lock entry for the table set in the first step is retained. The table can no
longer be edited with the maintenance tools of the ABAP Dictionary (Transaction SE11).
A terminated conversion can be analyzed with the database utility (Transaction SE14) and then
resumed. The database utility provides an analysis tool with which you can find the cause of the error
and the current state of all the tables involved in the conversion.
You can usually find the precise reason for termination in the object log. If the object log does not
provide any information about the cause of the error, you have to analyze the syslog or the short dumps.
If there is a terminated conversion, two options are displayed as pushbuttons in the database utility:
After correcting the error, you can resume the conversion where it terminated with the Continue
adjustment option.
There is also the Unlock table option. This option only deletes the existing lock entry for the table .
You should never choose Unlock table for a terminated conversion if the data only exists in the
temporary table, i.e. if the conversion terminated in steps 3 or 4. table for table TAB is therefore QCMTAB.
Hope this is helpful,Do reward.

Value 'KIRBYu00A0' of characteristic 0SORTL contains invalid characters

hello experts!
i am facing this error while activating 0vendor. data not available either in info object master neither in psa.
Error Message: Value 'KIRBY ' (hex. '004B004900520042005900A0') of characteristic 0SORTL contains invalid characters
Message no. BRAIN060
Diagnosis
Only the following standard characters are valid in characteristic values by default:
!"%&''()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
Furthermore, characteristic values that only consist of the character # or that begin with ! are not valid.
You are trying to load the invalid characteristic value 1. (hexidecimal representation 004B004900520042005900A0).
Procedure for System Administration
Try to change the invalid characters to valid characters.
If you want values that contain invalid characters to be admitted into the system, make the appropriate setting in BW Customizing. Refer to the documentation describing the requirements for special characters and the possible consequences.
For more information on the problems involved with valid and invalid characters, click here.
regards
vijay

Hi Vijay,
after KIRBY is a characteristic value which cannot be interpreted by BW properply / is not in the valid char list.
KRIBY is hex value 004B0049005200420059
the invalid char is hex value 00A0 -> online hex converter didn't found a ASCI match.
To solve the problem you will need to fix the record in the source. Or you go to PSA -> delete all in teh field and re-enter KRIBY.
Best regards,
Axel

Date / / contains invalid characters IN MODULE POOL

Hi,
I have a display field in infotype creation which will take always take current date.I have tried using the screen field as sy-datum and also tried using z-field with data type char or dats.but when ia am inserting values in a editable field on the screen and pressing enter ,it is giving the error: "Date / / contains invalid characters" .And afetr pressing cancel ,it goes back to the PBO and then pressing f8,it shows the infotype screen designed* but the other functionalities which have been coded in PAI of screen like activating checkboxes,radiobuttons etc. are not there .Even i have tried passing sy-datum to the date field in PBO of the screen.Pls help.

Hello Sir,
Were you able to sort out this issue.
Would appreciate if you can share the solution. One of our users have this issue in the ADOBE form.
Let me know please.
Thanks,
Akshay...

Add a new key field in an InfoObject

Hi all,
I have to add a new key field in a standard InfoObject (0vendor) in order to extract data correctly from a table in R3 which has both the vendor and the plant as keys.
Doubts:
1. the 0vendor InfoObject is already used in several InfoCubes
2. it contains data
3. we have another object built with reference to 0vendor
Any problem with the existent InfoCubes and queries if I change the structure of this InfoObject?
Have I got to delete data on it first?
any problem on the object built with reference to 0vendor?
I have just thought of updating the object 0vendor (this would avoid lots of substitutions and lot of work) instead of developing a brand new object..
Do you agree with this kind of solution or would you do something different?
Thanks
Elisa

Hi Elisa,
"In R/3 the vendor sub-range is blank and we use only one Purch Org, so no matter."
This is OK but remind that it shall remain like this ALWAYS; because if you design your model with these assumptions and later you start getting sub ranges and/or a second P.O then you can forget your model...
Replacing 0VENDOR by ZVENDOR completely will depend on your requirement; I don't know which content you are using but you should try to keep 0VENDOR as such because ZVENDOR will be compounded with 0PLANT and that's not the same... (e.g. the key will be displayed like "PLANT/VENDOR" in reports unless you drilldown the PLANT in front of ZVENDOR... your users may perhaps not appreciate...)
In this matter, how are you going to proceed?
- fill the vendor ID in ZVENDOR and have 0PLANT as compounding key? In this case you'll have to add 0VENDOR attributes in ZVENDOR as well. With this scenario you will end with redundant data since attributes for 0VENDOR will be the same for each combination 0PLANT/ZVENDOR.
- wiser: have 0VENDOR and 0PLANT both in the compounding key. This way you could have ZVENDOR key CHAR1 and leave it empty (it would be a "dummy" key you wouldn't use in reports)
The good thing here is that you don't have to replicate your 0VENDOR design in the ZVENDOR. the bad thing for you is that you NEED to keep both IObjs; thus manage your DIM issue.
Your approach to fill the cubes is absolutely right! What are the sizes of your cubes?
You should take this opportunity to check you cubes datamodel:
- are the dimension well deisgned? (run report SAP_INFOCUBE_DESIGNS in order to see the cardinality of your DIMs). I am sure this can be improved.
- are the cubes partitioned? Every cube should be partitioned for performance reasons.
- if the cubes are huge, wouldn't it be good to do a logical partitioning? E.g have one cube per year and a multicube on top...
Finally use dimension number range buffering when loading data into an empty cube and other techniques like dropping all indexes in order to speed up your load process and minimize reporting downtime. If your reports are based on multicubes and your model is not too complex you could even keep the copy cube instead of moving your data back to the original; you would then just have your multicube transport to make the switch of the new model available for reporting...
hoping this help you to go with the right path...
regards,
Olviier.

Table Key field Question

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

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

Problems deleting a primary key field in a table.

Hello Guys,
I deleted a primary key field in a custom table by clicking 'delete row' icon and then tried activating it through se14 - database utility. It is throwing an error saying 'Primary key change not permited for the value table zxxxx'. What is the problem???
How can I delete a primary key in a table??
Please help.
Thanks,
Naren

I am pasting the detail explaination over that error.
Primary key change not permitted for value table ZTV_RANGE_NUMBER
Message no. AD 300
Diagnosis
This table is defined as a check table. For reasons of consistency, changes to the primary key of the table are not allowed.
Procedure
If it is essential that you change the primary key, you must delete the relevant foreign keys. Refer to the where-used list to find all tables containing a field that is checked against this table. Delete the foreign keys for these fields.
If necessary, maintain the deleted foreign keys again.

SAPKE60027 - "T591A" contains invalid key fields

Similar Messages

Maybe you are looking for