/SAPPO/ACR - PPO Autocorrector - Fehlersymptome
The following messages are stored in message class /SAPPO/ACR: PPO Autocorrector - Fehlersymptome.
It is part of development package /SAPPO/CUSTOMIZING in software component CA-GTF-TS-PPO. This development package consists of objects that can be grouped under "Postprocessing Office - Customizing".
It is part of development package /SAPPO/CUSTOMIZING in software component CA-GTF-TS-PPO. This development package consists of objects that can be grouped under "Postprocessing Office - Customizing".
Message Nr ▲ | Message Text |
|---|---|
| 029 | Component &1 process &2 does not exist in Customizing/Systemcustomizing |
| 030 | &1 Additional data exists even though this is not indicated in the header |
| 031 | &1 No additional data exists although this is indicated in the header |
| 032 | &1: Additional data is not saved as string |
| 033 | &1: Data cluster F1 not found |
| 034 | &1: An empty string was saved as additional data |
| 035 | &1: Messages exist but the header MORE_MSG is initial |
| 036 | &1: No messages exist but the header MORE_MSG = 'X' |
| 037 | &1: Additional data string but ORDER_HDR-ABAP_TYPEKIND <> 'g' |
| 038 | &1: Worklist &2 does not exist |
| 039 | &1 Worklist &4 is not assigned to component &2 or &3 |
| 040 | Component &1/Worklist &2 do not exist in WL table |
| 041 | &1 No further objects exist although header MORE_OBJ = 'X' |
| 042 | &1 Further objects exist although header MORE_OBJ = ' ' |
| 043 | Initial component is not allowed in worklist table (/SAPPO/WL) |
| 044 | Component &1 has an initial worklist (/SAPPO/WL) |
| 045 | System component &1: worklist &2 has to start with '/' |
| 046 | Component &1 / process &2: initial worklist assigned |
| 047 | Component &1 does not have a standard worklist |
| 048 | Component &1 has more than one standard worklist |
| 049 | &1: PPO order does not have a worklist |
| 050 | &1: Software component &2 does not exist |
| 051 | &1: Indicator additional data is set and ABAP_TYPE is not equal to string |
| 052 | &1: No additional data exists but the ABAP_TYPE is STRING |
| 053 | Component &1 does not exist |
| 055 | &1: Hash value 1 is inconsistent (field HASH_1 in order header) |
| 056 | &1: Hash value 2 is inconsistent (field HASH_2 in the order header) |
| 057 | &1: The RETRY message has priority and the main message is initial |
| 058 | &1: The order was set manually to 'completed'. This is not permitted. |
| 059 | &1: PPO classic order is completed => settlement type is 01 or 02 |
| 060 | &1: RETRY_CLASS is set for initial error category |
| 061 | &1: FINISH_CLASS is set for initial error category |
| 062 | &1: FAIL_CLASS is set for initial error category |
| 063 | &1: ADD1_CLASS is set for initial error category |
| 064 | &1: ADD2_CLASS set for initial error category |
| 065 | &1: EARLIEST_RETRY set for initial error category |
| 066 | &1: EARLIEST_CMPLIN set for initial error category |
| 067 | &1: EARLIEST_MANUAL set for initial error category |
| 068 | &1: RETRY_GROUP set for initial error category |
| 069 | &1: RETRY_MODE set for initial error category |
| 070 | &1: Order mode does not correspond to values of RETRY_MODE and FAIL_MODE |
| 071 | &1: RETRY_MODE does not equal FAIL_MODE => Order mode has to be '3' |
| 072 | &1: Order mode has to correspond exactly to value '1', '2', or '3' |
| 073 | &1: Retry mode has to correspond exactly to value '1', '2', or '3' |
| 074 | &1: Fail mode has to correspond exactly to value '1', '2', or '3' |
| 075 | &1: RETRY mode is set but the RETRY class is initial |
| 076 | &1: FAIL mode is set but the FAIL class is initial |
| 077 | &1: If the error category is set, RETRY, FINISH or FAIL must be defined |
| 078 | &1: RETRY class &2 does not exist |
| 079 | &1: RETRY class &2 does not implement interface /SAPPO/IF_PPO_COMMAND |
| 080 | &1: FINISH class &2 does not exist |
| 081 | &1: FINISH class &2 does not implement interface /SAPPO/IF_PPO_COMMAND |
| 082 | &1: FAIL class &2 does not exist |
| 083 | &1: FAIL class &2 does not implement interface /SAPPO/IF_PPO_COMMAND |
| 084 | &1: Classic PPO order contains REDO, FINISH and FAIL system messages |
| 085 | &1: Order for message &2/&3/&4 no longer exists |
| 086 | &1: Order for object data with item &2 no longer exists |
| 087 | &1: Order for additional data with cluster &2 no longer exists |
| 088 | &1: Message &2/&3/&4 from the table ORDER_MSG no longer exists |
| 089 | There are initial software components in table /SAPPO/WLRANGE |
| 090 | &1: PROCMETH is not equal to RETRY_MODE in initial FAIL_MODE |
| 091 | &1: PROCMETH is not equal to FAIL_MODE in initial RETRY_MODE |
| 093 | &1: Main message (&2,&3) does not exist |
| 094 | &1: RETRY class &2 does not conform to the standard CL_ECH_PPO_RETRY |
| 095 | &1: FINISH class &2 does not conform to the standard CL_ECH_PPO_FINISH |
| 096 | &1: FAIL class &2 does not conform to the standard CL_ECH_PPO_FAIL |
| 097 | &1: RFC destination &2 is incompletey maintained (see transaction SM59) |
| 098 | &1: RFC destination &2: logical destination in remote system is initial |
| 099 | &1: RFC destination &2 refers to system &3, however, must refer to &4 |
| 100 | &1: Dialog RFC &2 is incompletey maintained (see transaction SM59) ... |
| 101 | &1: Dialog RFC &2: logical destination in remote system is initial |
| 102 | &1: RFC dialog &2 refers to system &3, however, it must refer to &4 |
| 103 | Component for ECH process definition is initial |
| 104 | Component &1: process for ECH process definition is initial |
| 105 | Component &1/process &2: action class for ECH process definition initial |
| 106 | Component &1/process &2: action class &3 does not implement &4 |
| 107 | Component &1/process &2 do not exist in entity table &3 |
| 108 | Component &1/process &2 from table &3 do not exist in entity table &4 |
| 109 | &1: RFC destination &2 has connection typ &3. It must be 3 or I |
| 110 | &1: RFC dialog &2 has connection type &3. It must be 3 or I |
| 112 | &1: Fail class is set but Fail mode is initial |
| 113 | &1: PPO classic orders must have a main object |
| 114 | &1: ABAP_TYPE must always be initial for PPO classic orders |
| 115 | &1: ECH order without a main object: the additional data is missing |
| 116 | &1: Component &2/Process &3 does not exist in table ECHS_PP_PROCESS |
| 117 | &1: ECH comp. &2/proc. &3 does not have an action class (ECHS_PROCESSES) |
| 118 | PPO comp. &1/proc. &2 from table &3 is not clearly assigned |
| 119 | &1: The user that created the PPO order is not set |
| 120 | &1: Error category &2 does not exist |
| 121 | &1: Changed by is set but change time stamp is initial |
| 122 | &1: Initial change user in case of set change time stamp |
| 123 | &1: GUID of the PPO order is initial |
| 124 | &1: Messages regarding POSNR do not ascend by 1 |
| 126 | &1: Main message (&2/&3/&4) occurs in the message log |
| 127 | &1: PPO orders possess the initial time stamp (creation) |
| 128 | &1: Main message (&2/&3/&4) occurs in ECH addendum (log) |
| 129 | &1: 'Create Time' is greater than 'Change Time' |
| 130 | &1: 'Create Time' must be unequal to 'Change Time' |
| 137 | &1: EARLIEST_COMPLIN: Time stamp &2 does not correlate w. date &3 time &4 |
| 138 | &1: Settlement permitted from is initial |
| 139 | &1: Retry group &2 does not exist |
| 141 | &1: ECH order is open => Settlement type must be initial |
| 154 | &1: No main message or other messages since CREATE/RETRY |