CP_INTEGRATION - Create BOM, Routing, Prod Version Integration
The following messages are stored in message class CP_INTEGRATION: Create BOM, Routing, Prod Version Integration.
It is part of development package CP_INTEGRATION in software component PP-BD-RTG. This development package consists of objects that can be grouped under "PP Task List - Integration".
It is part of development package CP_INTEGRATION in software component PP-BD-RTG. This development package consists of objects that can be grouped under "PP Task List - Integration".
Message Nr ▲ | Message Text |
---|---|
000 | ------------------------------------------------------------------------- |
001 | Production version does not exist. Inbound processing terminated. |
002 | BOM already exists for material &1, plant &2, alternative &3. |
003 | Routing already exists for group number &1, group counter &2. |
004 | Production version already exists for material &1, plant &2, version &3. |
005 | Production version created for material &1, plant &2, version &3. |
006 | Production version creation failed for material &1, plant &2, version &3. |
007 | Unknown error occured while parsing IDoc data |
008 | Issue while updating application log object &1 and subobject &2. |
009 | Production version data could not be read. |
010 | BOM &1 created for material &2, plant &3, alternative &4. |
011 | Failed to save task list/routing to the database. Re-process the IDoc. |
012 | Messages from IDoc processing can be found in the application log. |
013 | Effectivity &1 was not created. |
014 | Date effectivity change number &1 created successfully. |
015 | No changes made to BOM. |
016 | BOM &1 updated for material &2, plant &3, alternative &4. |
017 | ECM processor initialization error |
018 | Error while creating UUID and table CPD_VERSN_MAPPNG update fails |
019 | No data found. |
020 | A more recent routing version was replicated. Use repair procedure. |
021 | No relevant mapping data found for TL type &1, group &2, grp counter &3. |
022 | Update of production version failed for matl &1, plant &2, version &3. |
023 | Production version updated successfully for matl &1, plant &2, version &3 |
024 | Production version &1 does not exist for material &2, plant &3. |
025 | Validity of change number &1 adjusted successfully. |
026 | You're not authorized to change production version &1 in plant &2. |
027 | Production version cannot be locked. Try again later. |
028 | No display authorization for production versions in plant &1 |
029 | No change authorization for production versions in plant &1 |
030 | Ambiguous production versions cannot be integrated or reconciled |
101 | Mapping already exists |
102 | Unknown logical system |
103 | The validity period for routing &1 &2 version &3 does not exist. |
106 | The validity period for routing &1 &2 version &3 already exists. |
107 | The validity date must be before December 31, 9999. |
110 | Validity start date of routing &1/&2/&3 is later than the validity end. |
111 | In routing &1/&2, versions &3 and &4 have overlapping date effectivity. |
112 | Routing &1/&2 has a date effectivity gap between versions &3 and &4. |
113 | Change numbers could not be saved. |
114 | Production master data could not be saved. |
115 | Unknown bill of material |
116 | Unknown routing |
117 | Error while saving BOM and routing |
118 | Production version already exists. |
119 | Production version could not be retrieved. |
120 | BOM's root node could not be created. |
121 | BOM item could not be created. |
122 | Deletion of BOM item failed. |
123 | BOM could not be retrieved. |
124 | BOM material assignment could not be retrieved. |
125 | BOM items could not be retrieved. |
126 | BOM change state could not be retrieved. |
127 | BOM header could not be updated. |
128 | BOM header could not be updated. |
129 | BOM item is unknown. |
130 | Change to BOM item failed. |
131 | BOM could not be loaded. |
132 | BOM could not be locked. |
133 | BOM item could not be locked. |
134 | BOM items could not be retrieved. |
135 | Routing component assignment could not be created. |
136 | Routing operation could not be created. |
137 | Routing root node could not be created. |
138 | Routing material assignment could not be created. |
139 | Deletion of routing component assignment failed. |
140 | Deletion of routing operation failed. |
141 | Routing component assignments could not be retrieved. |
142 | Routing operations could not be retrieved. |
143 | Change to routing component assignment failed. |
144 | Routing material assignment could not be retrieved. |
145 | Routing component assignment is unknown. |
146 | Routing operation is unknown. |
147 | Change to routing operation failed. |
148 | Routing change state could not be retrieved. |
149 | Routing header could not be updated. |
150 | Routing could not be loaded. |
151 | Routing operation could not be locked. |
152 | Routing could not be locked. |
153 | Routing component assignments could not be retrieved. |
154 | Routing operation could not be retrieved. |
155 | Cannot determine local change number for &1. |
156 | Cannot determine local operation for &1. |
157 | Cannot determine local BOM item for &1 &2 &3. |
158 | Cannot determine remote BOM item for &1 &2 &3. |
159 | Routing component assignment path is incomplete. |
160 | Routing material assignment counter overflow |
161 | Routing material assignment path is incomplete. |
162 | Routing material assignment segment is inconsistent. |
163 | Routing material assignment strategy is different. |
164 | Routing operation path is incomplete. |
165 | Routing operation type is incorrect. |
166 | Routing header error |
167 | BOM error |
168 | You're not authorized to create items in this BOM. |
169 | You're not authorized to change items in this BOM. |
170 | You're not authorized to delete items in this BOM. |
171 | BOM item error |
172 | Cannot find the working environment; loading not possible |
173 | Incorrect working environment type; loading not possible |
174 | Incorrect class type in the working environment; loading not possible |
175 | Working environment not specified; loading not possible |
176 | Error while loading the working environment |
178 | BOM is not active. |