|
Diagnosis
The field catalog belonging to the archive information structure &V1&is not correctly defined. System Response
The system cannot carry out the processing for the informationstructure What_to_do.
You should deactivate the info structure &V1&. Otherwise the infostructures for the same archiving object which are correctly definedwill also not be filled. For more information on this see thedocumentation on Activating and deactivatinginfo structures.
After you have corrected the info structure &V1& and its assigned fieldcatalogs, you can refill the info structures. For more information onthis see the documentation on filling andemptying info structures.
It is probable that the error is not in the info structure but in theunderlying field catalog. If there is an error in an SAP standard fieldcatalog, contact the SAP Hotline. (The names of SAP standard fieldcatalogs start with "SAP".) For your own field catalogs note thefollowing points.
a) General:
The system passes the data records to the write program in randomorder. This means that the result is undefined if, for one informationstructure key, there is more than one data record within an archivedobject.
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
Müller 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 onesource table.
All key fields which are filled from source tables must behierarchically dependent on one another. Therefore the join conditionsfor the various source tables must be defined. Technically the systemalways creates an "outer join" when building the index. However, thiscan 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 theadditional source field VBAP-VBELN is defined in the first line.Similarly this is also valid for VBEP-ETENR. The keys for all sourcetables 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 forthe source table VBEP. |