How To Fix Q6234 - Infostruktur &1 ist inkonsistent

SAP Error Message - Details

• Message type: E = Error

• Message class: Q6 - Archive Information System

• Message number: 234

• Message text: Infostruktur &1 ist inkonsistent

Was verursacht dieses Problem?

The field catalog belonging to the archive information structure &V1&
is not correctly defined.

Systemantwort

The system cannot carry out the processing for the information
structure
&WHAT_TO_DO&.
You should deactivate the info structure &V1&. Otherwise the info
structures for the same archiving object which are correctly defined
will also not be filled. For more information on this see the
documentation on <DS:TX.AIND_DOCU_AKTIV>Activating and deactivating</>
info structures.
After you have corrected the info structure &V1& and its assigned field
catalogs, you can refill the info structures. For more information on
this see the documentation on <DS:TX.AIND_DOCU_AUFBAU>filling and
emptying</> info structures.

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

It is probable that the error is not in the info structure but in the
underlying field catalog. If there is an error in an SAP standard field
catalog, contact the SAP Hotline. (The names of SAP standard field
catalogs start with "SAP".) For your own field catalogs note the
following points.
a) General:
The system passes the data records to the write program in random
order. This means that the result is undefined if, for one information
structure key, there is more than one data record within an archived
object.
Example:
Field catalog definition
Type|Fldname-Index|Tablename|Fldname
K CUSNO BSEG CUSNO
D CDATE BSEG CDATE
Archive: CUSNO CDATE
Object 1: ( Offset 200 )
BSEG ... Miller 1.2.97
BSEG ... Miller 1.3.97
...
Object 2: ( Offset 300)
BSEG ... Miller 1.2.97
BSEG ... Meyer 2.1.98
Records passed to the information structure.
1st Case: Offset in key.
CUSNO CDATE ARCHIVEKEY OFFSET
Miller 1.2.97 ... 200 <-- CDATE not unique
Miller 1.2.97 ... 300
Meyer 2.1.97 ... 300
2nd Case: Offset not in key.
CUSNO CDATE ARCHIVEKEY OFFSET
Mnller 1.2.97 ... 200 <-- CDATE + Offset not unique
Meier 2.1.97 ... 300
b) Conditions for a field catalog key where there is more than one
source table.
All key fields which are filled from source tables must be
hierarchically dependent on one another. Therefore the join conditions
for the various source tables must be defined. Technically the system
always creates an "outer join" when building the index. However, this
can be changed to an "inner join", given that a key field is mandatory.
Example:
valid field catalog:
||| additional source fields
Type|Fldname-Index|Tblname|Fldname|||Tblname|Fldname||Tblname|Fldname
K VBELN VBAK VBELN VBAP VBELN VBEP VBELN
K POSNR VBAP POSNR VBEP POSNR
K ETENR VBEP ETENR
The entry VBAP-VBELN in the second line is only allowed, if the
additional source field VBAP-VBELN is defined in the first line.
Similarly this is also valid for VBEP-ETENR. The keys for all source
tables must be predefined without exception.
invalid field catalog:
||| additional source fields
Type|Fldname-Index|Tblname|Fldname|||Tblname|Fldname||Tblname|Fldname
K VBELN VBAK VBELN VBAP VBELN
K POSNR VBAP POSNR VBEP POSNR
K ETENR VBEP ETENR
The entry for the first key field is missing from the first line for
the source table VBEP.

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE