
This post was republished to SAP SCM Planning at 4:05:29 PM 8/31/2009
CTM Global Settings
How the CTM Global Settings Work
The CTM Global Settings in the IMG is used in conjunction with the CTM Profile.
http://www.scmfocus.com/sapplanning/2008/09/18/ctm-profile/
The difference being that the Global Settings apply to every CTM Profile, while each CTM Profile can be applied to different product locations. General Customizing Tab In the general customizing tab there are a number of fields to change. Some ones we want to focus on are the following:
- Demand Date: Both of these fields simply tell CTM when to look. (In CTM planning, the demands are aggregated weekly. You have chosen Start of period as the demand date. This means that all demands in one week are grouped together in one single demand, with the date at the start of the week.) – SAP Help
- Receipt Date:
- Message Output:
- Confirm Planning for Active Version: Simply checks to see if the planning version is 000 (i.e. the active)
- LiveCache Access: Related to performance for lifeCache.
- Plan Explosion: (Specifies which task list type (BOM and routing) CTM planning uses to create receipts for in-house production.) – SAP Help
- Maximum Planning Quantity: This allows CTM to plan larger quantities, but not smaller quantities, which greatly reduces the time of the CTM run. (The system only executes planning for demand and receipt quantities that lie over the indicated value. Smaller quantities are not planned.) – SAP Help
ATP Categories Tab
This is used to determine which categories are in and which are out.
- Substitute Categories for PP/DS with: This, along with the SNP substitution field is the most interesting. It determines which should be included. What is strange is that we did not think that CTM applied to PP/DS, but it does. It creates PP/DS orders as well as SNP orders (Determines which ATP categories the system should use for the PP/DS orders that are to be created.).
- Substitute Categories for SNP with:
Here you can see for the planning area we select our SNA planning area.
Demand Dependent Constraints
This is used to setup which demand will be fulfilled.
- Late Demand Fulfillment: This is the time period (in days) after the demand date, within which the system can still schedule receipt elements. – SAP Help
-
Strategy: Demand Fulfillment: These are the strategies that can be followed by CTM when late demand is to be fulfilled.
- Domino strategy: Late fulfillment of a demand can lead to late fulfillment of subsequent demands during demand prioritization. This may be the case if the capacity has already been exceeded.
- Airline strategy: If a demand cannot be fulfilled by the demand date, the subsequent demands are fulfilled first during demand prioritization. SAP APO does not attempt to fulfill the late demand until the end of demand prioritization. The advantage of using this strategy is that late demand fulfillment does not delay the fulfillment of subsequent demands. If all demand elements have moved to the end of demand prioritization, SAP APO switches automatically to the domino strategy. – SAP Help
- Restrict Early Demand Fulfillment (and associated fields): Period before demand date (in days), in which Capable-to-Match Planning (CTM) can create planned orders to cover a requirement.
- Allow Shortage: Indicates whether the system is allowed to only partially fulfill a demand. – SAP Help






