ProConfiguration V8.4.4

ProConfiguration new version V8.4.4 in development

Fixed bugs

Key	Summary	Description
CFM-339	Performance problems with large amounts of Memory Export / Import	When CFM dependencies to a large amount of plant or sales objects exists, then specially in update task performance problems can occur due to memory export and import calls. This has been fixed (Correction instruction).
CFM-340	Partially no alterantive date on bill of material	Using CFM object relations, it is possible to set alternative dates to bill of materials from corresponding material, plant or data package. But depending on data and DP selection in customizing, this is sometimes not executed. This has been fixed.
CFM-341	Multiple CFM status / processing scenario dialog when cloning with MSC	Initial situation: MSC V5.14.1 is installed (see fix MSC-18) CFM V8.4.0 is installed (see fix CFM-292) A material master including plant views is cloned using MSC One of the plant views has the batch management indicator set (XCHAR) More than one status and / or processing scenario are possible and must be selected In this case, the status selection dialogue is processed multiple times for eacht such material. This has been fixed.
CFM-342	Runtime Error ITAB_DUPLICATE_KEY in /PRONOVIA/SAPLPRMRELA	Since CFM 8.4.3 the runtime error ITAB_DUPLICATE_KEY can occurr in Program /PRONOVIA/SAPLPRMRELA. This has been corrected.
CFM-343	Object links on documents set to be available on a single document only, should not be copied when the document itself is copied	A material can be used as a template when creating a new material in CFM. In this process attached documents can also be copied to the new material. Object links on the relevant documents that are limited to a single document (1:n setting in TDWO) should not be copied to the new document. This error was corrected.
CFM-344	From "Exit" set version on primary document not used for synchronizing	If a "Exit" sets the version of the primary document, then this version will not be used on subsequent documents which are set for version synchronizing. This has been fixed.