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.

Similar Messages

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

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

Shared Services - Your system already has the instance with name epmsystem1

Hi,
I'm installing EPM System 11.1.2.1 in a new development enviropment. I thought I could connect to a previously configured database Shared Services database and configure the new instance to epmsystem1 (the default) but it is complaining with the error message "Your system already has the instance with name epmsystem1".
Is it really necessary to create a new name for the instance?

In 11.1.2.1 each EPM instance name needs to be unique, so if you have already configured an instance in an environment and you want to add a new instance it needs to be unique.
Cheers
John
http://john-goodwin.blogspot.com/

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.

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

HT1918 how do I check what birth date Apple ID has under my account name

how do I check what my birth date is on Apple ID / it appears to be incorrect. Thanks

Your wife should set up her own Apple ID. In order to do this, on her phone, go to Settings > iTunes & App Store to sign out of your Apple ID and sign in with your wife's new Apple ID. You shouldn't get her texts on your phone after setting up the new ID. This is the best and easiest way to solve the issue.
Hope this helped!

'PT_VBRK' has no component 'OIRIPBLNR' in prog.LOIRI_REPORTINGF01when VL01N

Hi
Issue: Update termination occured when creating a delivery with Order rederence from VL01N in ECC 6.0.
Created a delivery from VL01N and press 'pack' button and saved. I received a message 'Delivery XXXXXXXX is created' and then when i ran VL03N it gave a update termination. Log says 'RV_MESSAGE_UPDATE' MC 601: Object requested is currently locked by user AYEDLAPALLI
I went to where used list for this function module and tried to activate the program 'LOIRI_REPORTINGF01' and it gave an error message "Data object 'PT_VBRK' has no component 'OIRIPBLNR' in prog 'LOIRI_REPORTINGF01' .
Could you please let me solution if anyone come across this issue?
Thanks,
Anil

I think this will be problem with locking. please check your lock entries after VL01N in thru SM12
a®

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

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.
Data Types:
 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
Data objects:
 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 type and Data object

Hi Friends,
        What is the difference between Data type and Data object?
Best Regards,
VRV Singh

hi
good
Each ABAP program define its own data types using the statement.
TYPES dtype TYPE type ...
and declare its own variables or instance attributes of classes using the statement
DATA var {TYPE type} ...
Within the program or a class, you can also define local data types and variables within procedures. Local variables in procedures obscure identically-named variables in the main program or class.
When creating data types and data objects, there are a number of naming convention that also apply for other local program definitions, such as procedures. These are described in detail in the keyword documentation.
The Additions TYPE and LIKE
The additions TYPE type and LIKE dobj are used in various ABAP statements. The additions can have various meanings, depending on the syntax and context.
·        Definition of local types in a program
·        Declaration of data objects
·        Dynamic creation of data objects
·        Specification of the type of formal parameters in subroutines
·        Specification of the type of formal parameters in methods
·        Specification of the type of field symbols
Constructing New Data Types
The TYPE addition allows you to construct new data types in the TYPES, DATA; CONSTANTS; and STATICSstatements. In the TYPES statement, these are local data types in the program. In the other statements, they are attributes of new data objects, meaning that the newly defined data types are not free-standing. Rather, they are linked to database objects.This means that you can refer to them using the LIKEaddition, but not using TYPE.
To construct new data types, the addition TYPE can be used with the following type constructors:
·        Construction of reference types
REF TO type|dobj
·        Construction of structured data types
BEGIN OF struc_type.
END OF struc_type.
·        Construction of table types
tabkind OF linetype
These data types only exist during the runtime of the ABAP program.
Referring to Known Data Types or Data Objects
Using the additions TYPE or LIKE in the TYPESstatement, local data types in a program can be referred to known data types or data objects. This is mainly the case with user-defined elementary data types. If you declare variables using the additions TYPE type or LIKE dobj with statement DATA, the data type of var is already fully defined before the declaration is made.
The known types or data that are referred to must be visible at the point where the data type or variable is declared.
A known data type can be any of the following:
·        A predefined ABAP type to which you refer using the TYPE addition
·        An existing local data type in the program to which you refer using the TYPE addition
·        The data type of a local data object in the program to which you refer using the LIKE addition
·        A data type in the ABAP Dictionary to which you refer using the TYPE addition. To ensure compatibility with earlier releases, it is still possible to use the LIKE addition to refer to database tables and flat structures in the ABAP Dictionary. However, you should use the TYPE addition in new programs.
The LIKE addition takes its technical attributes from a visible data object. As a rule, you can use LIKE to refer to any object that has been declared using DATA or a similar statement, and is visible in the current context. The data object only has to have been declared. It is irrelevant whether the data object already exists in memory when you make the LIKE reference.
·        In principle, the local data objects in the same program are visible. As with local data types, there is a difference between local data objects in procedures and global data objects. Data objects defined in a procedure obscure other objects with the same name that are declared in the global declarations of the program.
·        You can also refer to the data objects of other visible ABAP programs. These might be, for example, the visible attributes of global classes in class pools. If a global class cl_lobal has a public instance attribute or static attribute attr, you can refer to it as follows in any ABAP program:
DATA dref TYPE REF TO cl_global.
DATA: f1 LIKE cl_global=>attr,
       f2 LIKE dref->attr.
You can access the technical properties of an instance attribute using the class name and a reference variable without first having to create an object. The properties of the attributes of a class are not instance-specific and belong to the static properties of the class.
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2ff3358411d1829f0000e829fbfe/content.htm
thanks
mrutyun^

Using Date objects in SQL statements

Hi, I am wondering if it is possible to use Date objects while trying to retrieve entries from an access database with fields set as "Date/Time" fields, as opposed to "Text"? If so, do I need to reformat it before inserting it into the SQL statement, or can I just leave it as a Date object, and call up the variable name?
For example - "SELECT * FROM database WHERE startDate = ' " + dateObject + ' ". And do i need quotes round this value?
Thanks in advance.

I had some problems by just fetching a date and pushing it back to a MS SQL Database.
I used the following reformating step to fix it:
if (o instanceof Timestamp)
String time = o.toString().substring(8,10)+"."+o.toString().substring(5,7)+"."+o.toString().substring(0,4)+" "+o.toString().substring(11,19);
ht.put(columnName, time);
o is the object i receve from the select statement and ht is a Hashtable where i put my data.
To write the data back i now can use:
UPDATE table SET columnname = 'valueOfColumn'
This means i use the value i created above in Quotes to write it back.
Format of Timestamp.toString() is something like yyyy-mm-dd hh:mm:ss.xx
Format used by MS SQL (and i think by Access to) 'dd.mm.yyyy hh:mm:ss'

Export with expdp tables with name like 'name1%' or like 'name2%'

How can I export data and metadata only from tables with name like 'name1%' or like 'name2%'
what value must have INCLUDE parameter ?
from one match it is
INCLUDE=TABLE:"LIKE 'REF%' "
this exports tables witch name begins with REF, but I need tables REF and REF1
if I write like this:
INCLUDE=TABLE:"LIKE 'REF%' ",TABLE:"LIKE 'REF1%' "
or
INCLUDE=TABLE:"LIKE 'REF%' "
INCLUDE=TABLE:"LIKE 'REF1%' "
it says that
Total estimation using BLOCKS method: 0 KB
ORA-39168: Object path TABLE was not found.
ORA-31655: no data or metadata objects selected for job
I supose such constructions work like between them is logical AND.
I need an OR construction.

C:\>EXPDP SCOTT/TIGER DIRECTORY=DATA_DIR DUMPFILE=EXPDATA.DMP INCLUDE=TABLE:"LIK
E'REF%'"
Export: Release 10.1.0.2.0 - Production on Saturday, 07 October, 2006 9:38
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
FLASHBACK automatically enabled to preserve database integrity.
Starting "SCOTT"."SYS_EXPORT_SCHEMA_01": SCOTT/******** DIRECTORY=DATA_DIR DUMP
FILE=EXPDATA.DMP INCLUDE=TABLE:LIKE'REF%'Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 192 KB
Processing object type SCHEMA_EXPORT/TABLE/TABLE
. . exported "SCOTT"."REF123" 9.406 KB 10 rows
. . exported "SCOTT"."REF12345" 9.414 KB 10 rows
. . exported "SCOTT"."REF1ABC" 9.406 KB 10 rowsMaster table "SCOTT"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
Dump file set for SCOTT.SYS_EXPORT_SCHEMA_01 is:
C:\EXPDATA.DMP
Job "SCOTT"."SYS_EXPORT_SCHEMA_01" successfully completed at 09:38
C:\>
INCLUDE=TABLE:"LIKE 'REF1%'
no need to specify "ref1%" bcoz if u specify "ref%" it means all tables after "ref" will be export.

Ora-01466 unable to read data table definition has changed oracle.

hi all,
i truncated a table before 10 min. now i want the data's so i used this query ;
select *
from ( select *
from sometable where some_condition )
as of timestamp sysdate-1;
but it shows:
""" ora-01466 unable to read data table definition has changed oracle"""";
how to get the deleted records from database????????????
Edited by: 887268 on Oct 24, 2011 4:02 AM

Error: ORA 1466
Text:   unable to read data -- object definition has changed
Cause: This is a time-based read consistency error for a database object,
        such as a table or index.
        Either of the following may have happened:
        The query was parsed and executed with a snapshot older than the time
        the object was changed.
        The creation time-stamp of the object is greater than the current
        system time.
        This happens, for example, when the system time is set to a time
        earlier than the creation time of the object.
Action: If the cause is
        an old snapshot, then commit or rollback the transaction and resume
        work.
        a creation time-stamp in the future, ensure the system time is set
        correctly.
        If the object creation time-stamp is still greater than the system
        time, then export the object's data, drop the object, recreate the
        object so it has a new creation time-stamp, import the object's data,
        and resume work.

Data object MY_ITEM has no component with name ABSKZ

Similar Messages

Maybe you are looking for