Error Handling During Specification Import
Use
A specification is not transferred if it contains errors or inconsistencies in the specification master record. If errors or inconsistencies occur, for example, if a non-existent phrase or source is used in a value assignment, only the value assignment is not transferred.
Errors are written to an error log during import. This can displayed using direct-input functions or batch job administration.
Features
|
Error |
From Table |
Reaction to Error |
|
Specification header |
ESTRH |
Specification import terminated |
|
Identifiers |
ESTRI |
Specification import terminated |
|
Regulatory list does not exist |
ESTRL |
Assignment not imported |
|
Material assignment |
ESTMJ |
Record not imported |
|
References |
ESTRR |
Assignment not transferred |
|
Value assignment (without additional information) |
Whole value assignment not imported |
|
|
User-defined text type does not exist |
User-defined text type used that was defined as standard parameter |
|
|
Assessment entered does not exist |
The default value defined in Customizing is used |
|
|
Component type does not exist |
Component type used that was defined as standard parameter |
|
|
Error in composition |
ESTVP |
Whole value assignment not imported |
|
Source does not exist |
TCG46 |
Assignment not imported |
|
Value assignment usage does not exist |
ESTDU |
Usage not imported |
|
General additional information Syntax or semantic errors (incorrect field, word too long, for example) |
Additional information not imported |