ABAP OO - 2 Attributes are Key Fields - Constructor & m_por-instid

Hi,
we are running 6.40
In my class there are 2 attributes that are key.
In my CONSTRUCTOR, how do I set m_por-instid when I have two attributes as key? Do I concatenate the 2 attributes into a variable and then do m_por-instid = variable?
Any other ideas?
Much thanks and regards,
Cristiana

Hi,
Kjetil is spot on about the structure. It's easy enough:
On the types tab create a type t_key, then click on the code-arrow-icon-thingy between the type and description fields
types:
    begin of t_key,
      po_number   type ebeln,
      item_number type ebelp,
    end of t_key .
then in your methods:
data: lv_key type t_key.
lv_key-po_number = im ebeln.
lv_key-item_number = im_ebelp.
m_por-instid = lv_key.
Regarding reducing the key to 32 characters, it's not a Microsofty idea for a change. It is a standard 32 byte GUID which is compatible with anything that talks BPEL, WF-XML, SOAP or similar. If you need longer keys then you need to work with persistent class GUIDs - i.e. get your key fields and use the GUID from a persistent class.
It's even documented <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/4d/e52f6af36db84999a937146382f0e6/frameset.htm">in the SAP help</a>
Hope that helps,
Mike

Similar Messages

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

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

Adding 2 new fields as Primary Key field in a Z Table which is existing PRD

Hi Friends,
I have to add two new fields as primary key fields in a Z TABLE, which is existing in Quality and Production Systems with Data.
If I incorporate these two new fields (Primary Key fields) in development and if the TR is moved to Quality and Production sytems, is there any possibility of loss in data will happen at Quality and Prd systems?
At present, Table is having 20 fields with 2 primary key fields and i have to add 2 more primary key fields.
I have checked in SCN and not find relevant threads.
Please help me out.
Regards,
Suresh.

NO . It wont be a problem .
For ex :
If you have VBELN , POSNR are key fields now , you have an unique reord with that combination .
If you add one other field in it fo ex VKBUR then records will be like this
VBELN     POSNR     VKBUR   MATERIAL   QTY
10020      10                            abcxyz      1
10020      10            1234        abcxyz     1
So your previous records before adding new primary keys , will have new fields balnk , and the new records will have data filled up in all primary key fields .
However , if you try to update the existing records that will be in existing PRIMARYKEY combination only .
for example if you try update record 1 above with VKBUR value 85858 , it creates a new record , it wont be updated in existing record.
Hope this helps , Pls let me know if u have any more doubts.

ABAP code help to replace one field with another

Hi All,
I have one DSO which is holding data for fields WBS(Old) and Company Code(Old).
and I have one table which holds the information for Ols WBS and Ols Comp Code along with their New WBS and New Comp code.
for eg:
In DSO :
Old WBS , Old Comp.Code
abc        , 001
xyz        , 002
In Table:
Old WBS , Old Comp.Code , New WBS , New Comp.Code
abc,           001,                    ABC,            001-04
xyz,           002,                    XYZ,            002-04
Now my requirement is ,
search record by record from DSO and look into the table .
If abc record in DSO matches with abc record in table, then in DSO it should replace with new WBS and Com.Codes.
after the code, data in DSO shuld be lik this.
WBS , Comp.Code
ABC , 001-04
XYZ,   002-04.
Thanks in advance,
Sai Chand.S

Hi
If these fields are key fields dont think its possible to overwrite. Else plz write the following Code in End Routine it will overwrite the existing values in DSO.
Select * from DSO into it_dso_temp. "U can even select only key fields WBS and CC fields.
If sy_subrc=0.
Sort it_dso_temp by WBS CC.
endif.
Select old WBS
           old CC
           new WBS
           new CC
from Table
into it_table
for all entries in it_dso_temp
where old WBS = WBS and old CC = CC.
if sy_subrc=0.
sort it_table by old WBS, old CC.
endif.
Loop at it_dso_temp assigning result_fields.
Read it_table into wa_table with key old WBS = fs_dso_temp-WBS
                                                           old CC = fs_dso_temp-CC Binary SEarch.
If sy_subrc = 0.
result_fields-WBS = wa_table-new WBS.
result_fields-CC = wa_table-new CC.
endif.
Endloop.
Refresh result_package.
result_package[] = it_dso_temp[].
Also if incoming data has only old values u can loop at result package instead of it_dso_temp. let me know in case of issues.
hope this helps !
Reg
Aparna

BAPI - Key field & Attributes

Hi Experts,
I had created a method in the BAPI by choosing the ADD METHOD option from the menu item.
I am able to see the method name in SWO1 transaction but nothing is there in ket field and attributes section.
Whether the key field and attribute will populate from the created RFC as like the method is populating out of RFC?
How to create a key field and attributes in SWO1...? Many thanks in advance!

> Whether the key field and attribute will populate from the created RFC as like the method is populating out of RFC?
Not sure to understand your question. You mean that a method may be converted into a BAPI automatically (right), and you ask whether keys and attributes are also converted? No, they are not used by BAPIs, but they may be used in workflow.
> How to create a key field and attributes in SWO1...? Many thanks in advance!
To create keys and attributes, use SWO1, position the cursor on the node and click create.

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

What are the key fields used to group double orders in t-code SDD1?

What are the key fields used to group double orders in t-code SDD1?
Cheers,
VT

Hi,
You can group the duplicate sales documents with the help of the following fields,
Sold-To-Party,Document type,date and sales area details.
Regards,
Gopal.

Which are the Key fields in the iTunes Music Database

I assume that the iTunes Music folder is really a database for all the music. I further assume that this database has a Key Field (1 or more) which are necessary for it to function.
Which fields are these and what are their names??
I am still hunting for the songs that are missing in iTunes but are in the library.

Ignore the question. I found the missing files. Had nothing to do with "key fields". Thanks

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.

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

Entering multiple entries in ZTABLE after changing a key field to nokey.

HI Experts,
This is Hema Iam new To ABAP.
My senario is I have created a ZTABLE with companycode, GLAccount, costcenter,profitcenter,plant.
AT first my table has companycode and GLaccount has key fields..
But to enter the multiple entries for cocode and GLaccount (ZBUKRS and ZHKONT) i have changed GLaccount has non key fields and table maintainence regenarated for the same.
my issue is as there are repeating entries for cocode and glaccount it is not possible to enter the entries as it is saying the entry is repeated and asking me to skip because cocode is primarykey there...
how can i overcome thsi issue to enter multipel entries for cocode and GLaccount.
As it should be done quickly ur help would be usefull
Thanks In Advance
L.Hemalatha.

Hi
I created zslno field and made it has primary key field aslo but still iam getting eror message while entrying entries as
"an entry already exists with the same key"
wht should be done i maintainance recreated after adding this field nad in se14 i adjusted the table too still what steps should be done ?
eg i need to enter data:
client cocode zslno GLacount Cost center profit center plant
010 1000 1483100 1001199 0035
010 1000 226100 101199 0076
so while entering second record and trying to save iam getting that error.... help me out

File Content Conversion - Key Field Value

Hi Experts,
I am using File to Idoc scenario for my mapping. In the receiver Communication channel, I am using File Content Conversion. My scenario is as follows :
I have a recordset with Header and Line items with Key Field Indicator as 'H' and 'L'. In some cases, the value for this Key Field is coming in as something other than 'H' and 'L'. I need to throw an exception when this Key Field is not 'H' or 'L'.
In the 'Content Conversion' tab, my attributes are as:
Header_Structure.keyFieldValue = 'H' and Line_Structure.keyFieldValue = 'L'. Is there any more attributes that I need to add ?
Please advise. Thanks a lot.
Regards,
Freddy.

>>multiple key field values in FCC configuration i.e Line_Structure.keyFieldValue = H or L
AFAIK it is not possible but lets wait for other experts to comment on this...
>>Can keyFieldInStructure (add, ignore) parameter help me in this case ?
No. this parameter is only used when you want to include key filed in ur XML structure(add) or not (ignore)...
Chk this:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

Select query on key field for different time format

Hello Experts,
I am working in Sender ABAP proxy <===> SAP PI 7.31 JAVA <===> Oracle database.
Oracle Database stores all records of material sold where the date is maintained in 01/15/2010 01:48:20 which has date and time format.
In ECC , I will be sending a proxy request with system date as the only field and this would be key field to select all the material records sold for 01/15/2010 in Oracle Database i.e. Select statement.As we can observe that the system data of ECC does not have time stamp.
I am clueless how to get this done in Message Mapping or in some way? If I maintain just the date stamp of ECC as the key field, would I be
able to fetch all the records from Database?
Regards
Rebecca

Dear Hareesh and Harish,
Ooopps the names are confusing. but very close..
Yes I changed my receiver structure and added <compareOperation> under the key field Material Number. In the Message Mapping , I assigned a constant EQ to <compareOperation>.
Now tested the proxy will value of Material with no 100 , expecting a response from database for Material 100. But getting error as below.
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 53cc7fab-e712-0b20-e100-8000ac10134c(OUTBOUND) expired. at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505) at
I am not sure whether there was any response from database.
I am close to end of this thread..
Please guide.
Regards
Rebecca

ABAP OO - 2 Attributes are Key Fields - Constructor & m_por-instid

Similar Messages

Maybe you are looking for