SAP ABAP Message Class /SAPPO/ACR (PPO Auto Corrector - Error Symptoms)
Basic Data
Hierarchy
☛ SAP_ABA (Software Component) Cross-Application Component
   ⤷ CA-GTF-TS-PPO (Application Component) Postprocessing Office
     ⤷ /SAPPO/CUSTOMIZING (Package) Postprocessing Office - Customizing
Attributes
Message class /SAPPO/ACR
Short Description PPO Auto Corrector - Error Symptoms  
Changed On 20110908 
Last Changed At 160514 
Messages
# Message Message Short Text Documentation status Authorization check
1 029 Component &1 process &2 does not exist in Customizing/Systemcustomizing The short text describes the object sufficiently
2 030 &1 Additional data exists even though this is not indicated in the header The short text describes the object sufficiently
3 031 &1 No additional data exists although this is indicated in the header The short text describes the object sufficiently
4 032 &1: Additional data is not saved as string The short text describes the object sufficiently
5 033 &1: Data cluster F1 not found The short text describes the object sufficiently
6 034 &1: An empty string was saved as additional data The short text describes the object sufficiently
7 035 &1: Messages exist but the header MORE_MSG is initial The short text describes the object sufficiently
8 036 &1: No messages exist but the header MORE_MSG = 'X' The short text describes the object sufficiently
9 037 &1: Additional data string but ORDER_HDR-ABAP_TYPEKIND <> 'g' The short text describes the object sufficiently
10 038 &1: Worklist &2 does not exist The short text describes the object sufficiently
11 039 &1 Worklist &4 is not assigned to component &2 or &3 The short text describes the object sufficiently
12 040 Component &1/Worklist &2 do not exist in WL table The short text describes the object sufficiently
13 041 &1 No further objects exist although header MORE_OBJ = 'X' The short text describes the object sufficiently
14 042 &1 Further objects exist although header MORE_OBJ = ' ' The short text describes the object sufficiently
15 043 Initial component is not allowed in worklist table (/SAPPO/WL) The short text describes the object sufficiently
16 044 Component &1 has an initial worklist (/SAPPO/WL) The short text describes the object sufficiently
17 045 System component &1: worklist &2 has to start with '/' The short text describes the object sufficiently
18 046 Component &1 / process &2: initial worklist assigned The short text describes the object sufficiently
19 047 Component &1 does not have a standard worklist The short text describes the object sufficiently
20 048 Component &1 has more than one standard worklist The short text describes the object sufficiently
21 049 &1: PPO order does not have a worklist The short text describes the object sufficiently
22 050 &1: Software component &2 does not exist The short text describes the object sufficiently
23 051 &1: Indicator additional data is set and ABAP_TYPE is not equal to string The short text describes the object sufficiently
24 052 &1: No additional data exists but the ABAP_TYPE is STRING The short text describes the object sufficiently
25 053 Component &1 does not exist The short text describes the object sufficiently
26 055 &1: Hash value 1 is inconsistent (field HASH_1 in order header) The short text describes the object sufficiently
27 056 &1: Hash value 2 is inconsistent (field HASH_2 in the order header) The short text describes the object sufficiently
28 057 &1: The RETRY message has priority and the main message is initial The short text describes the object sufficiently
29 058 &1: The order was set manually to 'completed'. This is not permitted. The short text describes the object sufficiently
30 059 &1: PPO classic order is completed => settlement type is 01 or 02 The short text describes the object sufficiently
31 060 &1: RETRY_CLASS is set for initial error category The short text describes the object sufficiently
32 061 &1: FINISH_CLASS is set for initial error category The short text describes the object sufficiently
33 062 &1: FAIL_CLASS is set for initial error category The short text describes the object sufficiently
34 063 &1: ADD1_CLASS is set for initial error category The short text describes the object sufficiently
35 064 &1: ADD2_CLASS set for initial error category The short text describes the object sufficiently
36 065 &1: EARLIEST_RETRY set for initial error category The short text describes the object sufficiently
37 066 &1: EARLIEST_CMPLIN set for initial error category The short text describes the object sufficiently
38 067 &1: EARLIEST_MANUAL set for initial error category The short text describes the object sufficiently
39 068 &1: RETRY_GROUP set for initial error category The short text describes the object sufficiently
40 069 &1: RETRY_MODE set for initial error category The short text describes the object sufficiently
41 070 &1: Order mode does not correspond to values of RETRY_MODE and FAIL_MODE The short text describes the object sufficiently
42 071 &1: RETRY_MODE does not equal FAIL_MODE => Order mode has to be '3' The short text describes the object sufficiently
43 072 &1: Order mode has to correspond exactly to value '1', '2', or '3' The short text describes the object sufficiently
44 073 &1: Retry mode has to correspond exactly to value '1', '2', or '3' The short text describes the object sufficiently
45 074 &1: Fail mode has to correspond exactly to value '1', '2', or '3' The short text describes the object sufficiently
46 075 &1: RETRY mode is set but the RETRY class is initial The short text describes the object sufficiently
47 076 &1: FAIL mode is set but the FAIL class is initial The short text describes the object sufficiently
48 077 &1: If the error category is set, RETRY, FINISH or FAIL must be defined The short text describes the object sufficiently
49 078 &1: RETRY class &2 does not exist The short text describes the object sufficiently
50 079 &1: RETRY class &2 does not implement interface /SAPPO/IF_PPO_COMMAND The short text describes the object sufficiently
51 080 &1: FINISH class &2 does not exist The short text describes the object sufficiently
52 081 &1: FINISH class &2 does not implement interface /SAPPO/IF_PPO_COMMAND The short text describes the object sufficiently
53 082 &1: FAIL class &2 does not exist The short text describes the object sufficiently
54 083 &1: FAIL class &2 does not implement interface /SAPPO/IF_PPO_COMMAND The short text describes the object sufficiently
55 084 &1: Classic PPO order contains REDO, FINISH and FAIL system messages The short text describes the object sufficiently
56 085 &1: Order for message &2/&3/&4 no longer exists The short text describes the object sufficiently
57 086 &1: Order for object data with item &2 no longer exists The short text describes the object sufficiently
58 087 &1: Order for additional data with cluster &2 no longer exists The short text describes the object sufficiently
59 088 &1: Message &2/&3/&4 from the table ORDER_MSG no longer exists The short text describes the object sufficiently
60 089 There are initial software components in table /SAPPO/WLRANGE The short text describes the object sufficiently
61 090 &1: PROCMETH is not equal to RETRY_MODE in initial FAIL_MODE The short text describes the object sufficiently
62 091 &1: PROCMETH is not equal to FAIL_MODE in initial RETRY_MODE The short text describes the object sufficiently
63 093 &1: Main message (&2,&3) does not exist The short text describes the object sufficiently
64 094 &1: RETRY class &2 does not conform to the standard CL_ECH_PPO_RETRY The short text describes the object sufficiently
65 095 &1: FINISH class &2 does not conform to the standard CL_ECH_PPO_FINISH The short text describes the object sufficiently
66 096 &1: FAIL class &2 does not conform to the standard CL_ECH_PPO_FAIL The short text describes the object sufficiently
67 097 &1: RFC destination &2 is incompletey maintained (see transaction SM59) The short text describes the object sufficiently
68 098 &1: RFC destination &2: logical destination in remote system is initial The short text describes the object sufficiently
69 099 &1: RFC destination &2 refers to system &3, however, must refer to &4 The short text describes the object sufficiently
70 100 &1: Dialog RFC &2 is incompletey maintained (see transaction SM59) ... The short text describes the object sufficiently
71 101 &1: Dialog RFC &2: logical destination in remote system is initial The short text describes the object sufficiently
72 102 &1: RFC dialog &2 refers to system &3, however, it must refer to &4 The short text describes the object sufficiently
73 103 Component for ECH process definition is initial The short text describes the object sufficiently
74 104 Component &1: process for ECH process definition is initial The short text describes the object sufficiently
75 105 Component &1/process &2: action class for ECH process definition initial The short text describes the object sufficiently
76 106 Component &1/process &2: action class &3 does not implement &4 The short text describes the object sufficiently
77 107 Component &1/process &2 do not exist in entity table &3 The short text describes the object sufficiently
78 108 Component &1/process &2 from table &3 do not exist in entity table &4 The short text describes the object sufficiently
79 109 &1: RFC destination &2 has connection typ &3. It must be 3 or I The short text describes the object sufficiently
80 110 &1: RFC dialog &2 has connection type &3. It must be 3 or I The short text describes the object sufficiently
81 112 &1: Fail class is set but Fail mode is initial The short text describes the object sufficiently
82 113 &1: PPO classic orders must have a main object The short text describes the object sufficiently
83 114 &1: ABAP_TYPE must always be initial for PPO classic orders The short text describes the object sufficiently
84 115 &1: ECH order without a main object: the additional data is missing The short text describes the object sufficiently
85 116 &1: Component &2/Process &3 does not exist in table ECHS_PP_PROCESS The short text describes the object sufficiently
86 117 &1: ECH comp. &2/proc. &3 does not have an action class (ECHS_PROCESSES) The short text describes the object sufficiently
87 118 PPO comp. &1/proc. &2 from table &3 is not clearly assigned The short text describes the object sufficiently
88 119 &1: The user that created the PPO order is not set The short text describes the object sufficiently
89 120 &1: Error category &2 does not exist The short text describes the object sufficiently
90 121 &1: Changed by is set but change time stamp is initial The short text describes the object sufficiently
91 122 &1: Inital changed by for set time stamp The short text describes the object sufficiently
92 123 &1: GUID of the PPO order is initial The short text describes the object sufficiently
93 124 &1: Messages regarding POSNR do not ascend by 1 The short text describes the object sufficiently
94 126 &1: Main message (&2/&3/&4) occurs in the message log The short text describes the object sufficiently
95 127 &1: PPO orders possess the initial time stamp (creation) The short text describes the object sufficiently
96 128 &1: Main message (&2/&3/&4) occurs in ECH addendum (log) The short text describes the object sufficiently
97 129 &1: 'Create Time' is larger than 'Change Time' The short text describes the object sufficiently
98 130 &1: 'Create Time' must be unequal to 'Change Time' The short text describes the object sufficiently
99 137 &1: EARLIEST_COMPLIN: Time stamp &2 does not correlate w. date &3 time &4 The short text describes the object sufficiently
100 138 &1: Settlement permitted from is initial The short text describes the object sufficiently
101 139 &1: Retry group &2 does not exist The short text describes the object sufficiently
102 141 &1: ECH order is open => Settlement type must be initial The short text describes the object sufficiently
103 154 &1: No main message or other messages since CREATE/RETRY The short text describes the object sufficiently
History
Last changed on/by 20110908  SAP 
SAP Release Created in   710