Lookup field in external data-object????

Hi All.
Is it possible to create lookup field in data object with external data-source?

Hi ,
yes you can create.look ups for any Data Objects.
Regards
Siva Sankar

Similar Messages

Using lookup field inside dimension + data base.

Good morning,
I'm trying to create drill down for my report with the follow caracteristics.
- Regions DataObject and this contains fields from an external data source.
- Exams DataObject and this contains lookup fields which uses fields from Regions.
- Exams DataObject contains a dimension and this one has a hierachy that uses my lookup fields.
When I access my report I try to do a drill down. But an exception occurs saying that field doesn't exists.
This concept that I've tried to create is correct ? If yes , what I'm doing wrong ?
Thanks

Hi Harold,
Here's a workaround that could turn into a solution.
Make sure that you're working on a COPY of the database, as there is potential for an error to cause loss of data. The easiest way to create a copy is to do a Save as... and make a small change to the DB name. The newly named version will be the active version, preserving the "old" version from inadvertent changes.
In the "new" version:
Go Layout > Define Fields...
Define a new Calculation type field with the formula 'fieldname' , using the name of the recalcitrant field where I've used fieldname. Set the Display as button to Text (if appropriate).
Click OK, then Done. (This step is necessary to force the calculation of values for this field,)
Go Layout > Define fields... (again)
Click on the "new" field to select it.
Change its Type to Text (or to whatever type the "old" field was).
Click Modify, then Done.
Remove the "old" field from each layout where it appears, and replace it with the "new" field. Set the format in Layout for each occurence of the field.
Return to Browse, and Print a test page to check the results.
Regards,
Barry

External Data Object

HI
I created a Data Object on top of an external data Source. TO export the DataObject if I give:
./icommand -cmd export -name "abc" -type eds -file abcd.xml I am able to export the external Data Source
but I am unable to export the DataObject which is based on this external Data Source
I tried using
./icommand -cmd export -name "FOlderName/DONAME" -type dataobject-file DOFIle.xml
to export the DataObject it gives error that no such DO exists
As per the document type eds should export the Data Soucre and the content..But I am getting just the connection details in the xml..
Can anyone guide how to export the external Data Object

This the the EDs export I get
<?xml version="1.0"?>
<OracleBAMExport Version="2024">
<EDS Name="ABC" ID="1" TypeID="EDSType.JDBC">
<Description> </Description>
<ConnectionDefinition
<ExternalDataSourceValues><Value id="Password" value="llf+M8AtAVD/QHI1DULzWBGOAP7yKqkZDipQH48u1dY="/>
<Value id="ConnectionString" value="jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = IP)(PORT = 1521))(ADDRESS = (PROTOCOL = TCP)(HOST = IP)(PORT = 1521))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = SID)))"/>
<Value id="Driver" value="oracle.jdbc.driver.OracleDriver"/>
<Value id="Login" value="username"/>
</ExternalDataSourceValues>
</ConnectionDefinition>
</EDS>
</OracleBAMExport>
The DO based on this EDS uses all columns as it is from a table in this user schema.

Field Catalog from data object..

Hi all,
data:
g_head_ref      TYPE REF TO data,
       g_item_ref      TYPE REF TO data.
    CALL BADI handle->set_header_item_data
      EXPORTING
        i_document_type    = g_document_type
        i_head_item        = g_head_item
        i_ab_document_type = doc_typ
        i_header_table     = g_header_table
        i_item_table       = g_item_table
        i_map_fields       = g_map_fields
      IMPORTING
        e_subrc            = l_subrc
        e_head_ref         = g_head_ref
        e_item_ref         = g_item_ref.
here i get the g_data_ref and g_item_ref filled with the values..
now i assigned these object to field symbols to display the same in the ALV.....
Issues is follwoing-->
I dont know the table structure or table name with which these ref object or the field symbols is type of now....
(in this case it can be a local prog type defined structure..)..
how can i create a fieldcatlog out of it..??
I have already tried
FM 'REUSE_ALV_FIELDCATALOG_MERGE' --> need an internal table with defined type...
cl_abap_structdescr=>describe_by_data --> need a DDIC structure (in this case it can be a local prog type defined structure..)..
if the class cl_abap_structdescr is the correct way to do it...please let me know exact flow of methods...if there is some other solution do let me know.
Regards,
Yadesh

Hi
i don't know what the variable g_map_fields, perhaps has it the definition of the table? if it's so you can use it to fill catalog table for ALV, else you can use CL_ABAP_STRUCTDESCR
data: g_head_ref TYPE REF TO data.
data: g_item_ref TYPE REF TO data.
field-symbols: <fs_head> type table.
field-symbols: <fs_wa> type any.
data: l_comp type flag.
DATA: MY_STRUCT TYPE REF TO CL_ABAP_STRUCTDESCR.
ASSIGN g_head_ref->* TO <fs_head>.
LOOP AT <fs_head> ASSIGNING <fs_wa>.
    MY_STRUCT ?= CL_ABAP_TYPEDESCR=>DESCRIBE_BY_DATA( <fs_wa> ).
    EXIT.
ENDLOOP.
Now in MY_STRUCT->COMPONENTS you have the definition of the table and u can use it in order to fill the catalog table for ALV
Max

Lookups to External Data Sources

Is it possible to create data object lookup fields that point to data objects that are External Data Sources rather than Internal Data Objects.
Thanks,
Mark.

Thanks for you reply Matt.
Yes I did mean creating lookup fields to External Data Objects. I believe our issue is actually that we were trying to create a lookup from an External Data Object to another External Data Object - which doesn't seem to work.
We have confirmed that we can lookup from an Internal Data Object to an External Data Object which will cater for the majority of the use cases. For any other cases (external looking up external) we will produce a new Internal Data Object and flatten out the lookup levels.
Mark.

Calculation Field to be mapped to different data object's column name in Oracle BAM 12c

Hi,
I am having a challenge to enable drill down to 2nd level report by passing calculation field as parameter.
As an alternative, I am thinking to point calculation field to another data object’s column name and generate report so that I would be able to pass that as parameter to drilling report view.
Is there any way to map calculation field to different Data object’s column name? Thanks in advance.
Regards
Amik Basu

1. Yes, you can.
SQL> create table ÜÝÞ( ßàá number(10));
Table created.
SQL> insert into ÜÝÞ values (10);
1 row created.1.1 and 1.2 and 2. You can choose UTF as your default character set. It allows the user of non-English characters in VARCHAR columns in your whole database. It is not per tablespace.
SQL> create table ÜÝÞ( ßàá varchar2(100));
Table created.
SQL> insert into ÜÝÞ values ('âãäçìé');
1 row created.

BAM 11g Moving External Object Data to Internal Data Object

Hi
I'm working with external data objects in our dashboards, this objects are updated every 30 minutes.
It's posible to update Internal Data objects at same time using triggers in BAM schema for use Active Data?
I need to autorefresh the Dashboard every 15 minutes.
Thanks for your comments
Ricardo
Edited by: rzegarrape on Jun 26, 2010 10:06 AM

Hi
What is the use case. Are you trying to automate a refresh of the report view based on an External data object? Or is there another use case - i am confused about 'moving external dataobject to internal data object' comment.
Some basic questions:
Version of BAM in use
Version of IE in use
Do you see updates in the browser for the internal DOs. For example, run call center sample with the scripts in [soa_home]/bam/samples/bam/callcenter/bin and verify that you can see the updates on the call center dashboard in Active Viewer.
Can you describe the setup a little - where is the data you want to view & refresh in the dashboard?
Regards
Payal

Differences between DATA TYPE and DATA OBJECTS

I am new to ABAP,I want to know the differences between DATA TYPE and DATA OBJECTS with some examples.
please help me regarding this.

Hi Ashish,
Data Types:       Are pure descriptions.
               No memory is associated with data types.
               Describes the technical properties of data objects.
EX.
1.     C-CHARACTER
2.     D-DATE
3.     F-FLOAT
4.     I-INTEGER
5.     N-NUMERIC TEXT
6.     T-TIME
7.     P-PACKED NUMBER
8.     X-HEXADECIMAL
9.     STRING-Variable length string.
10.     XSTRING-Variable length byte string.
Data Objects: Are created during runtime.
                They cannot exist without the data Types.
                Occupies memory space.
EX:
1.     INTERNAL DATA OBJECT- Internal Data objects
     LITEERAL- A literal has a fixed value.Ex: WRITE:u201DWORK HARDu201D.
     VARIABLES: Data statement is used to create variables.
EX.DATA: NUM TYPE I.
NUM: VARIABLE defined by data statement.
EX: DATA: PRICE LIKE NUM.
     CONSTANT-It is a data object, which contains a constant value throughout the program.
Can be declared in program by using CONSTANT statement.
EX:CONSTANT: INT TYPE I VALUE 15.
2.     EXTERNAL DATA OBJECT: Are defined in tables i.e In ABAP/4 dictionary you can access this data from table.
         EX: TABLES: SFLIGHT
          DATA: SEATS LIKE SFLIGHT-SEATSMAX.
3.     SYSTEM DEFINED DATA OBJECTS:Space & system variables like SY-UNAME,SY-DATUM, SY-REPID.
4.     SPECIAL DATA OBJECTS:
     PARAMETERS: Are Variables ,which can accept value from user.
      SELECTION SCREEN : Are special internal tables to accept value ranges from user.
3 APPROACHES TO DEFINE DATA OBJECTS.
1.     ELEMENTARY TYPES
DATA: Customer _Name (25) TYPE C,
               Vendor_Name (25) TYPE C.
2.     REFRENCE TO AN EXISTING FIELD:
DATA: Customer _Name2 (25) TYPE C,
              Vendor_Name2 (25) LIKE Customer_Name2
3.     REFRENCE TO NON-ELEMENTARY TYPE:
TYPES: T_NAME (25) TYPE C
DATA: CUSTOMER_NAME TYPE T_NAME
               VENDOR_NAME TYPE T_NAME
4.     RECORD-Information in rows & columns.
DATA: BEGIN OF BOOKING,
                                ID (4) TYPE C,
                                FLIGHT_DATE TYPE D,
                                NAME LIKE CUSTOMER_NAME,
                                END OF BOOKING.
You can also look into SAP help for more information.
Regards,
Indu.

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Data types and Data object

Can Any one give me Clear definition of Data type and Data objects.
Concept i know clearly.. but unable to explain it..
Regards,
Prasanna

Data consists of strings of bytes in the memory area of the program. A string of related bytes is called a field. Each field has an identity (a name) and a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
         In the ABAP type concept, fields are called data objects. Each data object is an instance of an abstract data type. Data types in ABAP are not just attributes of fields, but can be defined in their own right. There are separate name spaces for data objects and data types. This means that a name can at the same time be the name of a data   object as well as the name of a data type.
<b>Data Types:</b>
                 As well as occurring as attributes of a data object, data types can also be defined independently. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program (using the TYPES statement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
         Data types can be divided into elementary, reference, and complex types
<b>Data objects:</b>
                  Data objects are the physical units with which ABAP statements work at runtime. Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running. The technical attributes of a data object are its length, number of decimal places, and data type. ABAP statements work with the contents of data objects and interpret them according to their data type. You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
ABAP contains the following kinds of data objects
Literals
   Named Data Objects
Predefined Data Objects
Dynamic Data Objects

Data types and data objects

diff b/w data types and data objects

hi prasanth,
Data Types and Data Objects
Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
Data types are templates for creating data objects. Data types can be defined independently in the ABAP program or in the ABAP Dictionary. As attributes of a data object, data types can also exist in a non-independent state. Data types do not use any memory space for work data, but may require memory for administration information.
As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
A data object is an instance of a data type and occupies as much memory space as its type specifies. An ABAP program only works with data that is available as content of data objects. Data objects are either created implicitly as named data objects, or exanonymous data objects using CREATEDATA.
Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
regards,
sravanthi

Calculated fields based on data in multiple rows

Hi,
I am using SOA Suite 11.1.1.4 for BAM.
Can someone please help explain to me if and how we can use calculated fields in BAM data objects where the calculations are not only based on the data for that row, but on multiple rows ?
Like for example, this case can easily be constructed -->
TestDataObject Layout
Column1 integer
Column2 integer
Column3 calculated = Column1 + Column2
But if I want to create something like this -->
TestDataObject Layout
Column1 integer
Column2 integer
Column3 calculated = max(Column1) + avg(Column2)
Is it possible to do the above ?
Is it possible to check multiple rows of the other columns while calculating a value ?
Thanks & Regards,
Karan.
Edited by: user8890668 on Mar 9, 2011 3:58 AM

Hi, Karan.
Do you know you can do that in reports with calculated fields?
I guess it is not possible using calculating functions offered in data objects to do that.
If you, or anybody, discover how do that, please tell us. I would like to know that.
Luciano Gomes
user8890668 wrote:
Hi,
I am using SOA Suite 11.1.1.4 for BAM.
Can someone please help explain to me if and how we can use calculated fields in BAM data objects where the calculations are not only based on the data for that row, but on multiple rows ?
Like for example, this case can easily be constructed -->
TestDataObject Layout
Column1 integer
Column2 integer
Column3 calculated = Column1 + Column2
But if I want to create something like this -->
TestDataObject Layout
Column1 integer
Column2 integer
Column3 calculated = max(Column1) + avg(Column2)
Is it possible to do the above ?
Is it possible to check multiple rows of the other columns while calculating a value ?
Thanks & Regards,
Karan.
Edited by: user8890668 on Mar 9, 2011 3:58 AM

Unable to create Model from DOE Data Object

Hi,
I created a Mobile Laptop WebDynpro DC in NWDS 7.1, the build and deploy work fine.
The problem is that when I attempt to create a Model based on a Data Object from the
Mobile Middleware 7.1 DOE, I always get an exception when the Data Object metadata is
imported (the last step of the Model Creation Wizard).
Here's the exception :
Status ERROR
Plugin : com.sap.ide.cmi.core
code=0
Internal error
   Plugin name: Common Model Tools Core
   Internal error : com.sap.ide.cmi.core
   Class      : com.sap.tc.mobile.dt.metaimp.ModelImportWizard
   Method     : run(IProgressMonitor)
   Message    : Failed to create model
   Exception : com.sap.ide.metamodel.general.exception.ObjectRequiredException: ModelClassPropertySetting "//WebDynpro/ModelClass:ca.test.sandbox.mitest1.test3.ZTESTDATAOBJ/Property:ACTUAL/Setting:backendKey", Role "SettingDefinition": A minimum of 1 object(s) is required
ObjectRequiredException: ModelClassPropertySetting "//WebDynpro/ModelClass:ca.test.sandbox.mitest1.test3.ZTESTDATAOBJ/Property:ACTUAL/Setting:backendKey", Role "SettingDefinition": A minimum of 1 object(s) is required
at com.sap.ide.metamodel.webdynpro.implementation.ModelClassPropertySettingProxy._validate(ModelClassPropertySettingProxy.java:358)
at com.sap.ide.metamodel.core.DevelopmentObjectProxy.validate(DevelopmentObjectProxy.java:825)
at com.sap.tc.mobile.dt.metaimp.MBOModelImporter.doImport(MBOModelImporter.java:170)
at com.sap.tc.mobile.dt.metaimp.ModelImportWizard.createModel(ModelImportWizard.java:200)
at com.sap.ide.cmi.core.model.importer.CMIWizard$2.run(CMIWizard.java:197)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
I know this is not related to Middleware authorization, I tested with a userid with full DOE authorization.
When I display the Data Object metadata from the Middleware, it shows as status 'active'.
The exception seems to complain about the backend key, but there is a backend key field in
the Data Object.
I have the same exception even with any SAP delivered Data Objects (MAM30_001, etc..).
any thoughts on what the problem is ?
thanks,
Yanick.

Hi Yannick,
This type of error can occur with local non-dc Mobile App when some jars required for the model generation are missing.
The easiest way to fix this is to create a DC for your Mobile app from the
Mobile App Offline perspective.
Let me know if it works
Genevieve

Question about performance (entities & data object)

Hello:
I know that this can be, maybe, a silly question, but I've got the doubt
I get a local reference to a entity ( myEntityLocal ) and I'm going to get many values from it.
For example
myEntityLocal.getId();
myEntityLocal getName();
myEntityLocal.getAddr();
etc etc
My question is
Would be better, in performance terms, to fill all fields into a data object myEntityData ) and retrieve them from it ?
I mean
myEntityData = myEntityLocal.getData() // where getData() calls getter methods on myEntityLocal
myEntityData.getId();
myEntityData.getName();
myEntityData.getAddr();
I think the result is the same because is a local reference, but I've got that doubt
Thanks and regards

This will be san=me if you are considering the Local interfaces.
For remote interface(like accessing EJB from Servlets resides in diffferent Apps Server) use the DTO(data Transfer Object) patterns.
Regards
Sushil

Cannot add hub-managed content type with external list lookup columns to a list -- Error:Id field is not set on the external data field

This is a variation on the issue mentioned in this
post
We are using SP 2010 Content Hub to manage our content types. On the content hub we've created a couple of exteranl lists, and then created some site columns as lookups against these lists. We then added the columns to one of our content types
and set it to publish.
After the publishing job executed, I tried adding the content type (which now appears on the subscriber sites) to one of the document libraries on one of the subscriber sites. When I did that it threw the following error:
Microsoft.SharePoint.WebControls.BusinessDataListConfigurationException: Id field is not set on the external data field
at Microsoft.SharePoint.SPBusinessDataField.CreateIdField(SPAddFieldOptions op)
at Microsoft.SharePoint.SPBusinessDataField.OnAdded(SPAddFieldOptions op)
at Microsoft.SharePoint.SPFieldCollection.AddFieldAsXmlInternal(String schemaXml, Boolean addToDefaultView, SPAddFieldOptions op, Boolean isMigration, Boolean fResetCTCol)
at Microsoft.SharePoint.SPContentType.ProvisionFieldOnList(SPField field, Boolean bRecurAllowed)
at Microsoft.SharePoint.SPContentType.ProvisionFieldsOnList()
at Microsoft.SharePoint.SPContentType.DeriveContentType(SPContentTypeCollection cts, SPContentType& ctNew)
at Microsoft.SharePoint.SPContentTypeCollection.AddContentTypeToList(SPContentType contentType)
at Microsoft.SharePoint.SPContentTypeCollection.AddContentType(SPContentType contentType, Boolean updateResourceFileProperty, Boolean checkName, Boolean setNextChildByte)
at Microsoft.SharePoint.SPContentTypeCollection.Add(SPContentType contentType)
at Microsoft.SharePoint.ApplicationPages.AddContentTypeToListPage.Update(Object o, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)   b55297ed-717f-466d-8bdc-297b20344d3f
I checked the external content type configuration and it did specify an "id column". Anyone know if what I am attempting to do is possible and if so, what special configurations are required?
Thanks

The issue is not External Content type or external list but the look up column.
It's not possible to publish a look up column via the Content Type Hub.
If you need to do this then an alternate way is to use a Managed Metadata column instead, otherwise you will have to implement this via a feature.
Varun Malhotra
=================
If my post solves your problem could you mark the post as Answered or Vote As Helpful if my post has been helpful for you.

Lookup field in external data-object????

Similar Messages

Maybe you are looking for