Types of fixes

Type	Description
Feature pack	A feature pack contains all updates since the previously delivered feature pack, or in case of the first feature pack version, the updates made since the base delivery of M3 BE. Ensure that all market modifications installed on your environment are on the same feature pack version as the standard M3 BE. The feature packs are uploaded to the LifeCycle Manager Server using the Upload M3 BE Package task and applied using the Apply Feature Pack task. See Uploading an M3 Business Engine package and Applying a feature pack.
Fix	A fix can be a single correction or a bundle of individual corrections to the M3 Business Engine. The fix can either be a Hot Fix (HFix) or a Verified Fix (VFix). This fix is uploaded to the LifeCycle Manager Server using the Upload M3 BE Package task and applied using the Manage Fixes task or handled by MAK if it is a development environment. See Uploading an M3 Business Engine package and Managing fixes.
MCE	An MCE is an individual solution made to solve a reported issue for a particular version of M3 Business Engine. This can be downloaded from a central server at Infor as part of the CCSS initiative and is packaged as a zip file in the Temporary Fix (TFix) format. The naming standard for the zip file is `TFix_<solution no>_<component>.zip` where the component name can be any of these options: MVX for standard (M3 BE) M`xx` for a market modification where `xx` stands for market, such as SE for the Swedish market An MCE applied for an Additional Component needs to have its corresponding fix level activated in the Environment Configurator to become active. This fix is uploaded to the LifeCycle Manager Server using the Retrieve MCE task and applied using the Manage Fixes task. See Retrieving Maintenance Correction Entities and Managing fixes.
Maintenance Correction Package (MCP)	MCP is the preferred method for installing fixes. An MCP is a manually packaged MCE which has relations to a number of MCEs. Each MCP also contains accumulated delivery units for Language components and API metadata for the related MCEs. Individual MCPs are delivered for each country (Mxx) and the standard component (MVX). Installing an MCP will install all related MCEs. The MCP is created at a certain point in time and includes references to all MCEs available for the component at that time. Each MCP is cumulative, therefore it is only necessary to download and install the latest. An MCP (and all related MCEs) cannot be deactivated. The MCP is packaged as a zip file in the TFix format, and the naming standard for the zip file is `TFix_MCP<mm>-<BE version>- <nn>_<component>.zip` `<mm>` is a sequence number, `<BE version>` is the M3 BE version, and `<nn>` is a build number starting with 01. In the Manage fix view, all included MCEs are listed as Fix details.
M3 Installation fix	An M3 Installation fix is a Product Package fix. This is a correction to the LifeCycle Manager wizards and scripts used to manage and maintain M3 BE. This package also contains the M3 Foundation (including tools). This fix is uploaded to the LifeCycle Manager Server, and if no change exists to the M3 Foundation package, it is also installed using the Retrieve Fixes task. See Retrieve Fixes in LifeCycle Manager User Guide. If changes to M3 Foundation are included, you must upgrade your M3 Business Engine environment with this new version.

Type

Description

Feature pack

A feature pack contains all updates since the previously delivered feature pack, or in case of the first feature pack version, the updates made since the base delivery of M3 BE. Ensure that all market modifications installed on your environment are on the same feature pack version as the standard M3 BE.

The feature packs are uploaded to the LifeCycle Manager Server using the Upload M3 BE Package task and applied using the Apply Feature Pack task. See Uploading an M3 Business Engine package and Applying a feature pack.

Fix

A fix can be a single correction or a bundle of individual corrections to the M3 Business Engine. The fix can either be a Hot Fix (HFix) or a Verified Fix (VFix).

This fix is uploaded to the LifeCycle Manager Server using the Upload M3 BE Package task and applied using the Manage Fixes task or handled by MAK if it is a development environment. See Uploading an M3 Business Engine package and Managing fixes.

MCE

An MCE is an individual solution made to solve a reported issue for a particular version of M3 Business Engine. This can be downloaded from a central server at Infor as part of the CCSS initiative and is packaged as a zip file in the Temporary Fix (TFix) format. The naming standard for the zip file is

TFix_<solution
                    no>_<component>.zip

where the component name can be any of these options:

MVX for standard (M3 BE)
Mxx for a market modification where xx stands for market, such as SE for the Swedish market

An MCE applied for an Additional Component needs to have its corresponding fix level activated in the Environment Configurator to become active.

This fix is uploaded to the LifeCycle Manager Server using the Retrieve MCE task and applied using the Manage Fixes task. See Retrieving Maintenance Correction Entities and Managing fixes.

Maintenance Correction Package (MCP)

MCP is the preferred method for installing fixes.

An MCP is a manually packaged MCE which has relations to a number of MCEs. Each MCP also contains accumulated delivery units for Language components and API metadata for the related MCEs. Individual MCPs are delivered for each country (Mxx) and the standard component (MVX). Installing an MCP will install all related MCEs.

The MCP is created at a certain point in time and includes references to all MCEs available for the component at that time. Each MCP is cumulative, therefore it is only necessary to download and install the latest. An MCP (and all related MCEs) cannot be deactivated.

The MCP is packaged as a zip file in the TFix format, and the naming standard for the zip file is TFix_MCP<mm>-<BE version>- <nn>_<component>.zip

<mm> is a sequence number, <BE version> is the M3 BE version, and <nn> is a build number starting with 01.

In the Manage fix view, all included MCEs are listed as Fix details.

M3 Installation fix

An M3 Installation fix is a Product Package fix. This is a correction to the LifeCycle Manager wizards and scripts used to manage and maintain M3 BE. This package also contains the M3 Foundation (including tools).

This fix is uploaded to the LifeCycle Manager Server, and if no change exists to the M3 Foundation package, it is also installed using the Retrieve Fixes task. See Retrieve Fixes in LifeCycle Manager User Guide. If changes to M3 Foundation are included, you must upgrade your M3 Business Engine environment with this new version.