Lesson: Mastering Intercompany Master Planning

Introduction: Why Intercompany Planning Matters

In a globalized manufacturing and retail landscape, very few companies operate as a single, isolated entity. Most organizations function as a network of legal entities: one company might handle the manufacturing, another might focus on distribution, and a third might manage regional sales. Intercompany Master Planning is the process of coordinating supply and demand requirements across these disparate legal entities to ensure that products flow efficiently from the source of supply to the point of final demand.

Without a synchronized approach to intercompany planning, organizations often face the "bullwhip effect," where small fluctuations in customer demand cause massive, inefficient swings in inventory levels across the supply chain. If your distribution center doesn’t know that the manufacturing plant is undergoing maintenance, or if the manufacturing plant doesn’t see the upcoming seasonal demand spike in a foreign market, you end up with stockouts in one location and excess inventory in another. This lesson will guide you through the mechanics of setting up, executing, and refining an intercompany master planning system, ensuring that your supply chain functions as a unified whole rather than a collection of disconnected silos.

Understanding the Core Components of Intercompany Planning

At its heart, Intercompany Master Planning is about visibility and automation. It involves the propagation of demand from a demand-facing entity (the "buying company") to a supply-facing entity (the "selling company"). When a forecast is generated or a sales order is placed in the buying company, the system must recognize that this demand needs to be fulfilled by an internal supplier rather than an external vendor.

The Intercompany Supply Chain Model

To effectively model this, you must define the relationship between entities. In most Enterprise Resource Planning (ERP) systems, this is handled through "intercompany trade agreements" or "supply chain relations." These relations define:

• The Source: Which entity is responsible for fulfilling the demand?
• The Lead Time: How long does it take for the product to move between entities, including transit time and manufacturing time?
• The Pricing Mechanism: How is the cost transferred between the two legal entities?
• The Fulfillment Method: Is it a direct delivery to the customer, or does it go through a central distribution center first?

Callout: The "One-Touch" Philosophy The goal of advanced intercompany planning is to achieve a "one-touch" environment. This means that a customer order placed in Entity A automatically creates a purchase order in Entity A, which in turn triggers a corresponding sales order in Entity B, and potentially a production order in Entity B. By removing manual data entry, you eliminate the single greatest source of error in supply chain management: human transcription.

Setting Up the Intercompany Environment

Before you can run a master plan, the underlying data structure must be sound. If your master data—such as item numbers, units of measure, and lead times—is inconsistent across entities, the system will fail to link the demand and supply correctly.

Step-by-Step Configuration Guide

1. Synchronize Global Master Data: Ensure that every item used in an intercompany transaction has a consistent Item ID across all participating legal entities. If Entity A calls a product "Widget-100" and Entity B calls it "W-100-Blue," the planning engine will treat them as unrelated items.
2. Define Intercompany Relations: In your ERP settings, navigate to the Intercompany Setup module. You must explicitly define the buying company and the selling company. Establish the "Default Order Type" (e.g., Purchase Order or Transfer Order) for the relationship.
3. Establish Lead Time Profiles: Each relationship needs a lead time profile. This should account for manufacturing time in the selling company plus the transit time to the buying company. If you ignore transit time, your planning engine will consistently suggest late orders.
4. Configure Planning Parameters: In the Master Planning module, enable "Intercompany Planning" for the relevant demand items. This flag tells the system to look beyond the local entity's inventory when calculating net requirements.

Tip: Data Governance is King Before automating, perform a full audit of your item master. If your lead times are outdated or your safety stock levels haven't been reviewed in years, your intercompany plan will simply automate bad decisions at a faster rate.

Executing the Master Plan: How the Engine Works

When you run an intercompany master plan, the engine follows a hierarchical logic. It doesn't just look at the local warehouse; it travels up the supply chain tree.

The Logic Flow

1. Requirement Capture: The system identifies a shortage in the buying company.
2. Constraint Check: The system checks the local inventory and scheduled receipts.
3. Propagation: If the requirement remains, the system looks at the "Intercompany Supply Relation." It identifies the selling company and copies the requirement as a "planned intercompany demand."
4. Supply Generation: The selling company’s master plan then runs, treating the intercompany demand as if it were a direct customer sales order. It triggers production orders or procurement orders to meet that demand.

Practical Example: A Multi-Entity Scenario

Imagine Company A (USA) sells laptops. Company B (Taiwan) assembles the laptops.

• Company A receives a forecast for 1,000 units in October.
• Company A’s Master Plan runs. It sees insufficient inventory.
• The system creates an "Intercompany Planned Purchase Order" for 1,000 units from Company B.
• This creates an "Intercompany Planned Sales Order" in Company B’s system for the same 1,000 units.
• Company B’s Master Plan runs, sees the demand, and generates "Planned Production Orders" for the components required to build those 1,000 laptops.

Code Snippet: Automating Intercompany Validation

While most ERP systems handle the logic natively, you may need custom scripts to validate data consistency across entities. Below is a conceptual example of how you might verify that lead times match between two related companies using a pseudo-code approach common in C# or Python-based ERP integrations.

def validate_intercompany_lead_times(buying_entity, selling_entity, item_id):
    """
    Validates that the transit time defined in the buying entity 
    matches the lead time expectation of the selling entity.
    """
    buying_lead_time = db.query(f"SELECT transit_time FROM relations WHERE buying_company='{buying_entity}' AND item='{item_id}'")
    selling_lead_time = db.query(f"SELECT production_lead_time FROM items WHERE entity='{selling_entity}' AND item='{item_id}'")
    
    total_lead_time = buying_lead_time + selling_lead_time
    
    if total_lead_time > 30:
        return f"Warning: Total lead time for {item_id} exceeds 30 days. Current: {total_lead_time}"
    else:
        return "Lead time within acceptable range."

# Example Usage
status = validate_intercompany_lead_times("USA_Branch", "TWN_Plant", "LAPTOP-X1")
print(status)

Explanation of the Code: The function validate_intercompany_lead_times queries the database for two separate entities. It fetches the transit time from the buying entity and the manufacturing lead time from the selling entity. It then calculates the total time and provides a warning if the timeline exceeds a predefined threshold (in this case, 30 days). This type of programmatic check prevents the planning engine from creating "impossible" schedules that don't account for the reality of long-distance logistics.

Best Practices for Intercompany Planning

To maintain a healthy intercompany planning environment, you must adhere to strict operational discipline. The following best practices will help you avoid the common pitfalls that plague global supply chains.

1. Maintain Consistent Calendars

One of the most frequent causes of planning failure is a mismatch in working calendars. If the selling company in Asia observes a holiday that the buying company in Europe does not, the master plan might suggest a shipping date that is physically impossible. Ensure that all entities share a "global calendar" for intercompany movements, even if they maintain separate local calendars for internal production.

2. Implement "Firming" Rules

Do not allow the system to automatically change orders that are already in progress. Once an intercompany purchase order reaches a certain status (e.g., "In Production" or "Shipped"), the master plan should be prohibited from suggesting changes to the quantity or date. Use "firming" functionality to lock these orders so the system focuses on adjusting the remaining, uncommitted demand.

3. Regular Simulation Runs

Never run a major change to your intercompany planning parameters in a live production environment without testing it first. Use a simulation sandbox to run the master plan and review the "Planned Order" output. Check if the system is creating an excessive number of small, inefficient orders (a sign of poor "lot sizing" settings).

Callout: The "Bullwhip" Risk The Bullwhip Effect occurs when small errors in demand forecasting are amplified as they move up the supply chain. In an intercompany context, this often happens when the buying company changes their forecast frequently, causing the selling company to over-react with massive production runs. Always implement "forecast smoothing" or "demand fences" to prevent minor, day-to-day fluctuations from triggering large-scale intercompany production changes.

Common Pitfalls and How to Avoid Them

Even with the best configuration, intercompany planning can go wrong. Here are the most common mistakes and the strategies to mitigate them.

Pitfall 1: Ghost Demand

This occurs when an intercompany order is deleted in the buying company but remains active in the selling company. This leads to the selling company producing items that no one actually wants.

• The Fix: Always use integrated order management. If a purchase order is canceled, the system must trigger an automatic cancellation or a "change request" notification to the selling company. Never allow manual, unlinked deletions.

Pitfall 2: Lead Time Inflation

Over-cautious planners often add "buffer" time at every step of the supply chain. If the buying company adds 5 days and the selling company adds 5 days, you end up with a 10-day artificial lead time that makes your company less competitive.

• The Fix: Use "Safety Lead Time" fields in your ERP rather than inflating the base lead time. This allows you to report on your "true" lead time while keeping a separate, visible buffer that can be adjusted as performance improves.

Pitfall 3: Ignoring Currency Fluctuations

In intercompany planning, the cost of goods is often transferred in a specific currency. If the master plan doesn't account for currency conversion in its valuation, your inventory cost reports will be wildly inaccurate.

• The Fix: Ensure your planning engine is configured to use the latest exchange rates for calculating the "Planned Cost" of intercompany transfers.

Advanced Feature Comparison: Push vs. Pull Planning

When setting up your intercompany planning, you must decide between a "Push" and a "Pull" strategy.

For most organizations, a hybrid approach is the industry standard. You use "Push" planning for high-volume, stable components that can be stocked in advance, and "Pull" planning for specialized or finished goods where demand is volatile.

Step-by-Step: Troubleshooting a Planning Mismatch

If your intercompany master plan is not generating the expected results, follow this diagnostic checklist:

1. Check the "Pegging" Tree: Most ERPs have a "Pegging" feature. Click on the shortage in the buying company and use the "Pegging" or "Trace" function to see which demand is driving that requirement. Follow the link to the selling company.
2. Verify Status Flags: Ensure that the selling company’s items are marked as "Active" and "Purchasable" in the intercompany catalog. A common mistake is forgetting to check the "Purchasable" box for an item that is only intended for internal transfer.
3. Review Planning Groups: Check if the items in question belong to the same "Planning Group." If you have different planning groups for different regions, the system might not be allowed to cross-reference demand between them.
4. Audit the "Net Requirements" Screen: This screen is your best friend. It shows you the exact calculation of Supply vs. Demand. If you see a negative number that isn't being addressed, look for a "Planning Fence" that might be preventing the system from suggesting an order within a certain time window.

The Role of Safety Stock in Intercompany Planning

Safety stock is often misunderstood in intercompany scenarios. Should you hold safety stock in the buying company, the selling company, or both?

• Buying Company Safety Stock: Use this to protect against fluctuations in end-customer demand. It acts as the final buffer before a stockout.
• Selling Company Safety Stock: Use this to protect against production failures or manufacturing delays. It acts as a buffer for the supply side.

Warning: The "Double-Buffer" Trap Do not hold safety stock at both the buying and selling entities for the same item unless your supply chain is extremely unreliable. Holding safety stock in two places increases your working capital requirements and complicates your planning logic significantly. Instead, analyze which entity is more likely to experience a disruption and place your safety stock there.

Future-Proofing Your Planning Strategy

As your company grows, your intercompany planning will need to become more dynamic. Consider these advanced concepts for the future:

1. Multi-Tier Planning

If you have a three-level supply chain (Supplier -> Factory -> Distribution Center -> Customer), your planning must account for all three tiers simultaneously. Modern systems allow for "Multi-level Master Planning" where a demand at the bottom tier triggers a ripple effect that calculates requirements for the entire chain in one pass.

2. Scenario-Based Planning

Instead of just planning for the "expected" demand, use your system to run "What-If" scenarios. For example, what happens to our intercompany stock levels if the lead time from our primary supplier doubles? What if demand in the European market drops by 20%? Running these scenarios helps you build a resilient supply chain that can handle shocks.

3. Automated Exception Management

Rather than having planners review every single planned order, set up your system to only flag "exceptions." For example, have the system alert you only when a planned intercompany transfer is delayed by more than 48 hours. This allows your team to focus their energy on solving problems rather than clicking through routine, successful transactions.

Key Takeaways

Intercompany Master Planning is the backbone of a unified global supply chain. By mastering these concepts, you transition from reactive firefighting to proactive coordination. Remember these core principles:

• Data Integrity is the Foundation: You cannot automate a process if your master data (lead times, units of measure, calendars) is inaccurate. Clean your data before you turn on the planning engine.
• Visibility Across Borders: The goal is to make the intercompany boundary invisible to the planning engine. Ensure that demand in the buying company is automatically and accurately reflected as supply requirements in the selling company.
• Avoid the Bullwhip Effect: Use demand fences and smoothing techniques to prevent minor demand fluctuations from creating massive, inefficient production swings in your manufacturing plants.
• Standardize Processes, Not Just Software: Software is only as good as the process it supports. Ensure that all entities agree on how to handle exceptions, how to define lead times, and how to manage safety stock.
• Use Simulation for Safety: Never push major planning changes to a live system without testing them in a simulation sandbox. Use these tests to identify potential bottlenecks and refine your lot-sizing logic.
• Monitor the Exceptions: Focus your human capital on managing exceptions rather than routine planning. If the system is working correctly, the planner should only be involved when something goes wrong.
• Continuous Improvement: Review your intercompany planning parameters quarterly. As your supply chain performance improves, your lead times and safety stock levels should be adjusted to reflect the new reality.

By applying these rigorous standards, you will reduce inventory carrying costs, improve customer service levels, and create a more agile and responsive organization. Intercompany Master Planning is not just a configuration task; it is a strategic discipline that, when executed correctly, provides a significant competitive advantage in a complex, global market.