Error class:Data object 'WA_CT_REPORT' dosnt have component-zz_changeanalys

Hi all,
I am across an error in class-
Error is- Data object 'WA_CT_REPORT' dosnt have component-'zz_changeanalyst'.
Method used is IF_EX_CRM_DNO_MONITOR.
Please guide to resolve the issue.
Thank you.

Hi ,
You can comment this access and debug the code to see whether
WA_CT_REPORT' has any component named zz_changeanalyst
Regards,
Uma Dave

Similar Messages

Error class:Data object 'WA_CT_REPORT' dosnt have component-'zz_changeanaly

Hi all,
I am across an error in class-
Error is- Data object 'WA_CT_REPORT' dosnt have component-'zz_changeanalyst'.
Method used is IF_EX_CRM_DNO_MONITOR.
Please guide to resolve the issue.
Thank you.

No answer.

The data object "E_S_AFTER_CHG" has no component called "DSCT_DAYS1"

Hi All,
While loading data into 0FIAR_O03 i am facing this Error.....
1. Syntax error in GP_ERR_RSDRO_UPDATE , row 1.643 (-> long text)
Long Text:
The data object "E_S_AFTER_CHG" has no component called "DSCT_DAYS1",
but there is a component ...
2. Request 0000001495 in ODS 0FIAR_O03 must have QM status green before it is activated
In Details Tab :
1. Requests (messages): Errors occurred
2. Extraction (messages): Missing messages 
3. Transfer (IDocs and TRFC): Missing messages 
4. Processing (data packet): No data 
5. Request 0000001495 in ODS 0FIAR_O03 must have QM status green before it is activated 
Please Help me in this issue....
Regards,
Kiran Telkar

Hi
Replicate the datasource and activate the Trasfer structure once.. and reload the data
Request 0000001495 i htink this request is in red ..please delete ... by making it red forcebly............ or may be this req is loaded till PSA only .. plesae check in the monitor
hope it helps
regards
AK

Data object MY_ITEM has no component with name ABSKZ

Hello all,
When I try to run ME23N I receive a short dump with the cause
Data object MY_ITEM has no component with name ABSKZ
Any ideas how this can be fixed?
Regards,
Ileana

Not sure why it is causing a short dump, but ABSKZ is a Rejection indicator.

The data object does not have a component

Prior to making change to Z program, I did syntax check and got:
The data object "WA_D003" does not have a component called "ZSHIFT".
This Z program is in the End Routine of a transformation from a PSA to DSO. I get the error when syntax checking, but when executing the DTP, there is not an error and ZSHIFT gets populated as expected.
I am hesitant to make a program change and transport up.
This is all in our BW Development box. I checked the code against what is in BWQ & BWP and the code is exactly the same as is the DSO InfoObjects. However, in BWQ and BWP, I do not receive the error when doing a syntax check.
I've searched customer messages and have had no luck. I also treid to add an attachment to this question, but it won't allow me to. Thanks for any help.

pretty hard to help you as we have no clue what you're actually doing with WA_D003 and ZSHIFT, no?
so you're calling a z-program in an end routine?
what does that program do? what are it's parameters/select options?
what are you doing with the results of that program in the end routine?
what are WA_D003 and ZSHIFT? I'm assuming the first one is a work area and the latter a field you're trying to fill in the end routine?

Data Object does not have a component called MATNR

Hi Everyone,
I am battling with a small program for 2 days as to why any output is not getting on to the list.
On CHECK, the error being shown is the
'THE DATA OBJECT "WA_ITAB" DOES NOT HAVE A COMPONENT CALLED "MATNR".
Report ZTR_REP1.
tables:mara.
select-options:s_matnr for mara-matnr.
types:begin of itab,
 matnr like mara-matnr,
 ersda like mara-ersda,
 ernam like mara-ernam,
 ekgrp like marc-ekgrp,
 end of itab.
data: wa_itab like itab,
 itab1 like itab occurs 0 .
select matnr ersda ernam
 from mara
 into wa_itab
 where matnr in s_matnr.
append wa_itab to itab1.
loop at itab1 into wa_itab.
 write:/ wa_itab-matnr,
endloop.
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 5:34 PM

Hi Ranjith,
Use this code it will work fine:
tables: mara.
select-options : s_matnr for mara-matnr.
types: begin of itab,
matnr like mara-matnr,
ersda like mara-ersda,
ernam like mara-ernam,
ekgrp like marc-ekgrp,
end of itab.
data: wa_itab type itab,
itab1 like itab occurs 0 .
select matnr ersda ernam
from mara
into corresponding fields of wa_itab
where matnr in s_matnr.
append wa_itab to itab1.
Endselect.
loop at itab1 into wa_itab.
write:/ wa_itab-matnr.
endloop.
<REMOVED BY MODERATOR>
Regards
Hemant Khemani
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 5:35 PM

Reading/Setting Process Data Objects from Java Spring Component or XSLT

I have a BPMN process that references a Spring Component service.
The Spring service has a Java class and within that class I'd like to be able to reference process data objects of the BPMN process.
Ideally, I'd like to simply read and write to those objects within the Java class.
However, if that's not possible, I don't I can set input parameters on the Java class and have it return an object.
If I go that route, how can I pass in or return an object of a type other than your standard types (string, int, boolean)?
For example, I have a data object that is a type I created based on a schema.
How would I refer to that in a Java class?
Hope that makes sense.
Thanks,
Mike

Hi Adam.
I'm a little confused on the order of operations.
Here are the steps I took:
1. In JDeveloper, I created two Java classes: one interface and one class that implements it. Initially, the one method takes parameters that are Strings. I want it to also take a data type that's defined in a schema.
2. In the composite, drag Spring Context component onto screen. This opens the XML and here I define the <bean> that points to the two Java classes I just created.
3. In the composite, I create a pointer from the Spring component to Exposed Services and I create a new service, which creates the WSDL.
4. Now I edit the WSDL to import the schema that defines the type I want.
5. In my BPMN process, I add a call to the service I just created. For Data Associations, it recognizes the changes I made to the WSDL and I can map input variables to the new type added in step 4.
Here's where I'm stuck. In the actual Java class, I don't know how to add the parameter for the data type I created. Where is this Java object created?
Thanks,
Mike

Mapping errors between data object and automated activity

Hi,
in a automated activity of a bpm process I try to call a web service method ("addBook") which exptects an object called u201CbookWrapperu201D. The object "bookWrapper" consist of three variables: u201Cbidu201D (Integer), u201Cauthoru201D (String), u201Ctitleu201D (String).
When I try to directly map, for example u201Ctitleu201D, out of an existing Data Object (Filled by an human activity: u201CDO_CreateBooku201D) I got the error:
Expected: xsd:string
Found list of u2018com.sap.dictionary.stringu2019
Severity and Description Path Resource Location Creation Time Id
The literal: "Expression for target path 'DO_BookWrapper/title' has errors." do not have type, in expression: "#erroneous=true;sources=TaskOutput/UIResponse/start/title#TaskOutput/UIResponse/start/title". LocalDevelopmentLocalDevelopmentbook_chapter_process~demo.sap.com/src/bpmn create book and chapter.bpmn Expression for target path 'DO_BookWrapper/title' has errors. [Galaxy, Rule, Literal] 1260878200220 4720
I do not know why this error occurs because both type are strings. Is it due to the fact that I do not have an object instead of variables as input parameters? I used the automatically generated data types as data objects.
May anybody help me please? Can I make casts?
Regards

Hi Martin,
From the error that you get, it is indicated that you try to map a list to a single variable.
If you want to do so, please see the documentation http://help.sap.com/saphelp_nwce711/helpdata/en/47/63604e42bf6831e10000000a421937/frameset.htm where it is said:
If you map a node, whose content is a list or a node, with one or more parents that are lists, to a single-valued node, you get an error. Depending on your needs you could provide custom expression, for example to aggregate the list to a single value, or you could do parent mapping between the multi-valued parent nodes.
So you need to create an EJB function that does the conversion between a list and single value type. Here is the help for functions: http://help.sap.com/saphelp_nwce711/helpdata/en/47/63604e42bf6831e10000000a421937/frameset.htm and especially for EJB functions http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/609c9982-39af-2b10-768b-e5bd8813c1f3.
I hope this helps you.
Best regards,
Radost

The data object "T_ACCIT" does not have a component called "XTRNDP"

I am receiving an ABAP dumb following the execution of transaction MIGO (when posting the goods
movement). Attached is a copy of the ABAP dump and below is part of a dev_w log file.
I tried to look at table T_ACCIT in SE16 and I receive the message 'Table T_ACCIT is not active in the Dictionary'.
A Tue May 20 15:19:26 2014
A *GENER* request remote generation: SAPLRWCL.
A
A Tue May 20 15:19:27 2014
A *** ERROR => Syntax error in program SAPLRWCL                                 [abgen.c      1828]
A {root-id=6431504C36361EE3B88A6D67BE3C41DE}_{conn-id=00000000000000000000000000000000}_0
A *** ERROR => > Include FICA_SAPLRWCL=================E          line 5 [abgen.c      1830]
A {root-id=6431504C36361EE3B88A6D67BE3C41DE}_{conn-id=00000000000000000000000000000000}_0
A *** ERROR => > The data object "T_ACCIT" does not have a component called "XTRNDP". [abgen.c      1832]
A {root-id=6431504C36361EE3B88A6D67BE3C41DE}_{conn-id=00000000000000000000000000000000}_0
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.
A ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
I *** ERROR => SemRel: Inv. Operation. Units 1. Key=51 [semux.c      1393]
I {root-id=6431504C36361EE3B88A6D67BE3C41DE}_{conn-id=00000000000000000000000000000000}_0

Hi,
T_ACCIT is a table parameter of a fm and is of structure ACCIT. Also ACCIT can't be found in SE16 but in SE11.
Regards,
Klaus

MI: the data objects in the SCV dont have the active DOE triggered adapter

We try to use SDOE_LOAD on MI7.1 to do the initial load.
However, we get the error:
"the data objects in the SCV dont have the active DOE triggered adapter."
We cannot find a fix anywhere.
Please help. thanks a lot!

Hi,
Assuming that you are using 7.1 in non-backward compatibility mode.
1. The client post the update/delete/insert request to DOE in bound queue.
2. The DoE post these messages to the BE.
3. Meanwhile, after posting all the message client starts reading outbound messages in DoE till the outbound queue is empty.
4. WHILE the client is reading outbound messages in 3. above the BE has validated the update/delete/insert request and posted a confirmation/rejection messages to DoE outbound queue the message will flow down to the client in the same sync cycle.
However, if it's posted to DoE after the client has finishing syncing with DoE the message will flow down to the client in the next sync.
So you see it cannot be guaranteed that the ocnfirmation/rehection message will flow down to the client in the same sync cycle.It may or may not happen.
I hope this clarifies.
Best Regards,
Amit

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 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

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

Problem with initial download of a data object

Dear All,
I have created a data object named "EQUIPMENT", which has three nodes. EQUIPMENT is the header node, DETAILS is the child node to EQUIPMENT and LOCATION is the child node to DETAILS. I have also done explicit key mapping to DETAILS and LOCATION.
I have selected the following as the BE Keys in the nodes.
SERIAL NO in EQUIPMENT header node.
TYPE in DETAILS node.
ZIPCODE in LOCATION node.
In the explicit key mapping of DETAILS node we have selected "SERIAL NO" field in this node.
In the explicit key mapping of LOCATION node we have selected "SERIAL NO" and "TYPE" fields in this node.
Data object contains no errors and i have activated the data object and it was successful.
Then i have also created back adapter which has EQUIPMENT get list and get detail. Get list returns only serial numbers (which is the BE key in EQUIPMENT node). Get detail takes "serail no" as input, returns "DETAILS" and "LOCATION" data in tables parameter. I have tested the get list and get detail interfaces, they are working fine. Then i have activated back end adapter and that was successful.
Now i have triggered an initial download for the "EQUIPMENT" data object, but there is no data downloaded into the data object. I have checked the monitoring in administration portal, it is showing status "Ended with errors", but there is no details of an error.
So can you please let me know what could be mistake i have done or how to check what is the error. Please help us to resolve the issue.
Regards,
Kiran.

Hi Kiran
Are you checking in the NWMA>>Monitoring>>Logs and Traces>>Backend Integration? The logs should have the proper error.
If not can you regenerate the DO, edit and activate your adapter and try again?
Regards
Rohith

Data objects in a Unicode program are not convertible?what does this mean?

hello,everyone,
when I execute a smartform directly in the transaction smartforms.,the result can be seen just no data.
when I execute program to transfer two internal tables from interface with data to the smartforms,and I use tcode st22,
the error is : Data objects in a Unicode program are not convertible.
the error analysis; The statement
"MOVE src TO dst"
requires the operands "dst" and "src" to be comvertible.
the source code that error occurs is :LOOP AT I_SHIP_DETAIL INTO WA_DETAIL .
and I know that the internal table have errors ,I defined the internal table refer to a structure created myself,and I set break-point in the smartforms ,can see the data in the internal table ,so why occurs such errors ,pls help me if you know .thank you in advance.

hi
good
go through this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f2dac69e-0e01-0010-e2b6-81c1e8e5ce50
thanks
mrutyun^

Error class:Data object 'WA_CT_REPORT' dosnt have component-zz_changeanalys

Similar Messages

Maybe you are looking for