Changing Non key field to Key field in a custom table

Hello Abap gurus:
I have a requirement in which i need to change a non key field in my custom table(Z TABLE) to key field.
For example; i have field sequence as
field 1 key field
field 2 key field
field 3 key field
field 4 non-key field
field 5 non-key field
field 6 non-key field
field 7 non-key field.
i want to change field 7 as key field.
Can i do perform operation??
when i am tryingto perform bove operation it is taking long time to get the table activated.
Could any one please help me in getting this resolved.
regards,
Sravanthi.

Use DB Utility (se14) to perform alter table or conversion. The latter is used when atemps to perform first operation fails. Which one is used, really depends on system and current DB table state (i.e. if has any content and what is being adjusted).
The way Max suggested is similar to [conversion process|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21f1b8446011d189700000e8322d00/content.htm] which system takes care of itself.
Refer [Adjusting Database Structures|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21f1ab446011d189700000e8322d00/content.htm] and already given link to conversion.
Please also consider potential errors while doing conversion . This can lead to data loss, so you should think of some backup to prevent that.
Regards
Marcin

Similar Messages

How can we add a field with drop down in a custom table

Hello,
I have a requirment in which I have to add a extra field in a custom table.
Secondly I need to have a drop down with some values in it.
Can you let me know how can we go about this.

hi..
your requirement is not very clear..
but if you are adding a field and want drop down with values....... it is possible by providing search help for that field.
Hope the requirement is same.

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

Key fields are not visible in output condition table

Hi,
     I have created few conndition tables using V/61. But i can not see Key field. It is not displaying. But when I check thru VK11 i can see that all fields are marked as key fields. example of table B018.
My problem is that , i want to make few filed non key fields rest of fileds as key fields so that there should not be any duplicate ntry based on key fields. also I do not want to maintain these two fields for each record.
Is there any exit to modify and view thesefields? or it is a security issue...bold
Your earliest response is highly appreciated.\
Thanks,
AKS

Hi Raga,
Please check the documentation under the customizing path:
IMG -> Sales and Distribution -> System Modifications ->
Create New Fields (Using Condition Technique) ->
New Fields For Pricing
Then click on the paper icon
Here is explained how to setup additional fields for pricing,
not present in the standard.
Notice the following rules:
1. the new fields must have name beginning with 'ZZ' or 'YY' in order
   to avoid problem after upgrade
2. add the new field in the table T681F for the application 'V' and the
   usage 'A'
3. these new fields must be appened to the structures KOMKAZ or KOMPAZ
   (depending they are header or item fields)
4. you should provide these fields by implementing the userexits
   USEREXIT_PRICING_PREPARE_TKOMK (header fields)
   USEREXIT_PRICING_PREPARE_TKOMP (item fields)
   in program MV45AFZZ for sales order, RV60AFZZ for invoice.
In that documentation there are some examples too.
Please check it.
Regards,
Alex

FIELD SELECTION KEY

Hi,
       I have a query regarding Field Selection Key.
I want to know the difference between Field Selection Keys AKTH, ME21, and ME21N.
I have observed during Testing that, AKTH and ME21N are almost the same.
But, I like to know the difference.
Which is to be used when?
Please give suitable suggestions in this regard.
Thanks in advance.
Thanks & Regards,
Srinivasa M.S
+91-9910077829

Hi,
Go through following information.
Field selection key: -
You should not delete the field selection keys listed below, which the dialog program uses for control purposes, otherwise the dialog may terminate during processing:
1. Field selection key: transaction
The field selection key that corresponds to the transaction code: for example, field selection key ME22 for the transaction "Change Purchase Order". For the Enjoy Purchase Order transactions (creating, changing, displaying), there is only field selection key ME21N.
2. Field selection key: activity type
Is set from the activity type as follows:
AKTH    In creation mode
AKTV    In change mode
AKTA    In display mode
AKTE    With PO extension
You should note that you can also add items in change mode (for example, transaction ME22). Field selection key AKTH would be used for this item.
3. Field selection key: purchasing document type
The field selection key that you have assigned to the document type for the purchasing document. For example, field selection key UBF is assigned to document type UB, which is used for stock transfer orders (within a company code). In this key, the fields Price and Price unit are suppressed.
4. Field selection key: item category/document category
This is determined from the item and document categories as follows: The first two characters consist of the letters 'PT', the third character of the item category (internal representation), and the fourth of the document category:
A   for RFQs,
B   for purchase requisitions
F   for purchase orders
K   for contracts
L   for scheduling agreements
Accordingly, field selection key PT3F would be used for a subcontracting item in a purchase order.
Field selection key: function authorization/release status
Purchasing documents: Used for authorization control. If the user parameter EFB (function authorizations in Purchasing) has been assigned and a field selection key has been assigned to the relevant value, this field selection key is used. Otherwise, field selection key $$$$ is used if the user has insufficient authorization to display prices.
Purchase requisitions: If the purchase requisition is subject to a release strategy and a field selection key has been assigned to the current release indicator, this field selection key is used.
Field selection key: subitem/creation indicator
Purchasing documents: Is only used in the case of subitems. The field selection key is put together in the same way as for the item categories (field selection key 4), with the string 'UP', the subitem category, and the document type.
Purchase requisitions: the field selection key that is derived from the creation indicator in the purchase requisition, that is, ESTV, ESTF, or ESTD, is used in the case of purchase requisitions generated from within Sales and Distribution, from a production order, or through direct procurement.
5. Field selection key: purchase requisition
In addition to the available field selection keys, you can define a field selection key at function authorization level to influence the input characteristics of fields in the Enjoy Purchase Requisition.
You can use this field selection key to set up groups of users that have certain restrictions when editing purchase requisitions.
SAP Recommendation: -
SAP recommends that you accept the settings defined in the standard system. In this case, no action is required on your part.

Field Selection Keys related to Purchase Order

Hi,
I have a query regarding Field Selection Key.
When we go to Field Selection Screen connected to Purchase Order, we can find so many Field Selection Keys viz., $$$$, $$$2, AKTH, ME21N, etc.
How to judge which is to be used when?
I like to know how these Field Selection Keys are linked to Purchase Order Screen in the background.
Please guide me in this regard by giving proper suggestions in this regard.
Thanks in advance.
Thanks & Regards,
Srinivasa M.S
+91-9910077829

Hi Karthik,
Thanks for your valuable information.
I like to know few more things.
1) Is it possible to create our own Field Selection Key?
2) If you observe the list of Field Selection Keys related to Purchase Order Screen, you can see that there are Field Selection Keys by name ME21N, ME21, AKTH, etc.
If the Field Selection Keys are predefined by SAP, it is OK. But, if there is an option to create our own Field Selection Key, then what is the procedure to do the same?
It seems that ME21N, ME21, and AKTH are used for Create Purchase Order Screen.
There are also keys ME22N and ME23N used for Change Purchase Order Screen and Display Order Screen.
I am little bit confused about this.
We are linking the Field Selection Keys to the Document Types.
But, I think it is only for create Purchase Order Screen. Please correct, if I am wrong.
Also, I like to know how we are linking the Field Selection Keys related to Change Purchase Order Screen and Display Purchase Order Screen?
Please clarify all my doubts by giving proper suggestions.
Thanks in advance.
Thanks & Regards,
Srinivasa M.S
+91-9910077829

Use of field selection Key.

Hello
I am implementing the release strategy for the Purchase requisition. can anyone please tell me what is the significance of "Field selection key" and "Value change" under the release indicator.
Regards

Dear,
In the standard system, SAP will not allow changes to the quantity, unit of measure, or price when an approver is executing the release
transaction. If you require that other fields, such as delivery date, plant, etc., not be modified via the release transaction, this field selection key is useful.
Field selection key: If you want to allow certain fields to be changed during or after a release, you can modify the Field Selection Key. To modify the Field Selection Key, follow the menu path in the IMG: Materials Management > Purchasing > Purchase Requisition >
Define Screen Layout at Document level. Once you have created a custom field selection key, you should create a custom release indicator by maintaining a new entry in the u201CCreate Release Indicatorsu201D screen.
It is also possible to configure the release to not be restarted if the amounts have only changed a specified percentage. To do this, enter u201C4 - Changeable, new release in case of new strategy or valueu201D and a percentage in the u201CValue chgsu201D field.
Regards,
Syed Hussain.

Field Selection Key In Release Indicator For PR

Hi,
Can you explain what is the use of Field Selection Key in Release indicator for PR on what basis to select this value.
regards,
zafar

Hi
Field selection key directs which values can be changed after the relevant release indicators have been set
Eg suppose you want to supress the field for PR after first release indicator has been set you have to assign the relevant field selection key to Release indicator
you can assign the same to the release indicators in
spro-mm-Purchasing -PR-Procedure with classification-set up Procedure with classification-release indicators
you can set the field selection key in
spro-mm-purchasing -PR- define screen layout at document level
Regards
Sandeep

DSO - What key fields and data fields in dso

Hi experts,
I need to create a dso in between the cube and 2 data sources(2lis_11_vaitm, 2lis_12_vcscl) to stage the data. My question is: what key fields and data fields to choose for the dso? is there a standard dso to copy? please explain in detail the model to set up, whether to connect both the ds's to dso and then to cube or one ds to dso and the other to the cube. more details will help.

Check this for standard DSO:
http://help.sap.com/saphelp_nw04/helpdata/en/43/fcdc387f34384f94c3227baf3837a8/content.htm
Thanks...
Shambhu

Infoset Join condition on Key feilds and data fields

Hi Guys,
I have a requirement to biuld the Info set with join conditon on two DSO's the info objects which i am using in the JOin condition are defined as data fieds in one DSO and defined as key fields in another DSO, is it possible to define join condition on key fields and data fields.
The two info objects are
                       0AC_DOC_NO
                       0ITEM_NUM
These two info objects are defined as data fields in DSO :   0LIV_DS1   Invocie verificaion
                                                        key fields in DSO:    0FIAP_0o3 FI AP Line Item
Please suggest me is it possible to define join the condtion on the data fields and key feilds.
Thanks
Best regards
SG

Hi
yes you can create join, you will get any issue in reporting level.
example: Say i want to create Info Set on 0MATERIAL and Sales DSO.
In 0MATERIAL Info Object it is key filed, but in my DSO 0MATERIAL is data field.Still we can create
Creation of join is dependent on fields common in your source objects.
check out the below document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7?QuickLink=index&overridelayout=true
Regards,
Venkatesh
Edited by: Venkateswarlu Nandimandalam on Sep 27, 2011 2:26 AM

Key fields and data fields in a DSO ??

i have a question regarding key fields and data fields in a Standard DSO...
i am using 2 datasources to build a open sales report 2LIS_11_VASTH and 2LIS_11_VASTI i am pulling in data from these 2 data sources to a DSO and i am wondering what infoobjects should be in the key fields and data fields .....does this reflect back to table VBUK and VBUP tables and does the key field in the DSO have to be the key fields in VBUK and VBUP tables ???? or what really should be included as key fields and data fields ????
please help....

If you look at the various SD tables, VBELN and POSNR are commonly used as the document number and document line item.
For VBAP and VBUP, it's referring to the Sales Order Line Item with the columns VBELN and POSNR as the key for both tables. However, if you look at the LIPS table, which is the Delivery Line Item table, it too has VBELN and POSNR as the key. Likewise, the VTTP table, which is the Shipment Line Item table, also has VBELN and POSNR as the key.
While using RSOSFIELDMAP as a map is a fairly good "rule of thumb", it still needs to be used with a level of skepticism.

Prerequsites for deciding Key fields and data fields

Hi
I would like to know the criteria to decide upon KEY fields and Data fields for an infoprovider.

Hi,
What is a Key field in a Database and How should I choose one?
Keys are crucial to a table structure for many reasons, some of which are identified below:
They ensure that each record in a table is precisely identified.
They help establish and enforce various types of integrity.
They serve to establish table relationships.
Datafields may be Charecteristics and it may be keyfigures
Regards,
Marasa.

Key Fields and Data Fields in ODS

Hi Guru's ,
Can u Explain what are Key Field's and Data Field's in ODS,and How they work.
Thanx in Advance.

Hi Pradeep,
An ODS key fields forms a unique combination of chars according to which data in the ODS will be summed up. Data fields are additional fields, chars or key figures.
For example, you have the following key fields:
Doc No, Doc line item (item no in the doc) and you load the following data:
Doc# Item# Amount CALDAY
1234 1        100       26.09.2005
1234 1        150       27.09.2005
1234   2        300      27.09.2005
1235   1        400      27.09.2005
The first two rows with the same key fields (1234-1) will be aggregated and into ODS will go amount of 250.
What I said is true if for Amount key figure the Add option is set.
But if you set an Overwrite option, then the second record will overwrite the first one and only amount of 150 will go to ODS!
But if CALDAY is also a key field, then into ODS will go all records without any aggregation, because key fields combination is different for all records.
So, ODS key fields choice and KFs settings are very important for data aggregation in the ODS.
Best regards,
Eugene

Data fields and key fields

Hi,
Data fields and key fields are same as Characteristcs and key figures? Or they are diffrerent?
Thanks,
Radha

HI
Key Fields = Acts as Primary Key for The ODS like Primary of Tables in R3.
Data fields = Apart from Key fields We consider rest as data fields.
Ususally we use Characteristic info Objects and Dates in Key Fields and Key figures in Data fields.
It's decisive factor for overwriting property of ODS or DOS.
Hope this helps.
Regards,
Rangzz
Edited by: Ranganath Kodiugane on Feb 7, 2009 12:14 PM

Identify key fields and data fields

Hi
i have datasource 0co_om_cca_9 .
i want build 1 DSO, how can i identify what are key fields and data fields to build DSO based on that datasource.

Hi sunnel,
The DSO are like 2-D database tables.
We use the technical keys here in counterpart to the business keys in Infocubes.
The key fields are the one based on which the records are identified uniquely in the database table.
And the data fields are the ones which are aggrgated or summarised or overwritten based on the value in key filed.
For example:
The ID no.s of the employees will be unique and it can be used as a key field.
The feilds like the Salary taken by the employee every month :"SALARY"
and the no. of leaves they taken: " NO. OF LEAVES" can be used as data fields.
So that the salary or the leaves taken by a particular employee can be aggregated based on her/his ID no.
The key fields in DSO doesnty mean Key figures.The key field means any unique key or a key based on which the records are sorted in the DSO
And key figures are the data fields.Some of the Characteristics can also be data fields in DSO.
Please give points if u r satisfied wit the information
Also let me know if u hav any doubt and if any thing is wrong.
Regards,
Kalpana M

Changing Non key field to Key field in a custom table

Similar Messages

Maybe you are looking for