CPPEMIG - Migration of BOM and Routing to iPPE

The following messages are stored in message class CPPEMIG: Migration of BOM and Routing to iPPE.
 It is part of development package CPPEMIG in software component LO-MD-PPE. This development package consists of objects that can be grouped under "Migration of BOM and Routing to iPPE".
Message Nr ▲
Message Text
000******************** General messages for migration ********************
001************************ iPPE migration run *****************
002Objects selected:
003BOM (groups) & (&)
004Routings: &
005Component assignments: &
006BOM data could not be read
007Application log could not be opened
008User &1 is not assigned to an iPPE profile
009Internal error: &1 &2 &3 &4
020**************************Migration tables****************************
021Migration is locked by user &
022Internal error; incorrect parameters for function module
023Mapping entry could not be found
024Number assignment failed: Check the setting for the number range object
025Object has already been migrated
040******************************Customizing*******************************
041Customizing for migration has been read
042Error in Customizing for migration
043Error in Customizing: Object type & must not be used here
044Customizing: General settings are not maintained
045Customizing: Enter representation for use &
080***************************Business Add-Ins******************************
081Active BADI implementations:
082Do(es) not exist
083&
100************************* BOM-specific ***************************
101-------------------------------------------------------------------------
102BOM & &
103BOM data could not be read
104Long text of the BOM text is not migrated
105Create access level:
106Assembly node & created
107You cannot migrate configurable multiple or variant BOMs
108BOM & & could not be migrated
109Difficulties reading long text & & &
110Long text exists (int. type &)
111Access node & has been created
112Alternative has been created at the node
113BOM &1/&2 not yet migrated
120***********************Read BOM data****************************
140********************************Analysis*********************************
141Simple BOM
142Variant bill of material
143Multiple bill of material
144Configurable BOM
145Material assignments:
146& & & &
147Lot sizes are not migrated
148BOM status & at header & & & is not migrated
149BOM could not be locked
150BOM group &
151Alternative item exists (item & &)
152Alternative item group &1: Item &2 is not transferred
160*************************************************************************
161Class for configurable material could not be determined
162Internal class number for configurable material could not be determined
180*******************************Items*************************************
181Item deletion (E) V=& L=& �=&
182Item &1, status &2 (&3) could not be migrated
183Item deletion V=& L=& �=&
184Variant &1 created (L=&2 �=&3)
185Relationship V=& L=& �=& for A=&
186Structure node &1 has been created
187Object dependencies available (&1):
188Classification as AWB
189>> &
190Object dependencies could not be read
191Object dependencies could not be created
192Object dependencies created &1
195Class nodes:
196Header deletion record for &1 has been created
199Start migration of BOM & &
200************************* Routing-specific ***************************
201Migration of routing & & has started
300************************* Routing-Specific ***************************
301Start of migration of routings
302Read routing &1 &2 &3 &4
303Read sequence &1 &2 &3 &4
304Read operation: &1 &2 &3 &4
305Generation of activity header &
306Generation of activity view &
307Generation of operation &
308Generation of activity &
309Generation of resource &
310Generation of mode &
311Activity header &1 could not be created
312Activity view & could not be created
313Operation & could not be created
314Activity & could not be created
315Resource & could not be created
316Mode & could not be created
317All (&) subordinate operations were not migrated
318Routing is locked by user &
319Internal error: &1 &2 &3 &4
320&1 &2 &3 &4
321Exceptions processed
322iPPE node assignment according to default implementation from BADI &
323iPPE node assignment according to customer implementation from BADI &
324& routings selected by Engineering Workbench
325& sequences selected by Engineering Workbench
326& operations selected by Engineering Workbench
327Selected routing headers with history
328Selected sequences with history
329Selected historical operations
330PVS node created
331Internal error; PVS nodes could not be created
332Internal error; sequence relationship could not be created
333Part-of relationship created
334Sequence relationship created
335Internal error; part-of relationship could not be created
336Internal error when writing a message in the application log
337Internal error on opening the application log
338Internal error on closing the application log
339Internal error in the Engineering Workbench: function module &
340Internal error: function module(s) &1 &2 &3 &4
341Migration of routings has been stopped
342End of the migration of routings
343Work center is not maintained in this operation
344Routing &1 &2 &3 &4 has already been migrated
345Internal error when writing mapping in the migration table
346Internal error when assigning ERP fields to iPPE fields
347Logical system could not be determined
348Mode was not created
349Routing &1/&2 was not migrated, as it has already been migrated
350Resource was not created
351Material component could not be assigned to processing activity
352Session &1-record &2 was created. Change no.='&3'.
353Session C-record &1 (ECN='&2') not created, as D-record does not exist
354Material component &1/&2/&3 assigned to processing activity
400*************************Access Object*********************************
401iPPE access &1 / &2 / &3 could not be created
800************************Engineering Workbench****************************
801Save changes before migrating
Privacy Policy