Kontakt

Ansicht
Dokumentation

/SCMTMS/TM_SAG_PLANNING_SYNC - Synchronization of TM Planning Results with MM Scheduling Agreements

/SCMTMS/TM_SAG_PLANNING_SYNC - Synchronization of TM Planning Results with MM Scheduling Agreements

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this report to synchronize the transportation planning date of freight unit items with the delivery date of the corresponding MM scheduling agreement schedule line. Once a freight unit is planned in TM, and a transportation date is fixed, the delivery date of the schedule line in MM is updated accordingly. This ensures that delivery dates specified in the scheduling agreement scheduling line are more accurate as they are based on the TM transportation planning process.

Integration

Prerequisites

The report includes only scheduling agreement schedule lines that are fixed against updates of a potential MRP run. In Customizing, you can use a planning time fence to define a fixing horizon to specify the period that the MRP result is to be protected from any automatic changes. In this period, depending on the firming type maintained in the MRP type, no order proposals are changed or created automatically. For more information see Customizing for Production under Production Planning > Master Production Scheduling> Master Data> Define Planning Time Fence and Roll Forward Period.

You can define the fixing horizon in the scheduling agreement item using the firm zone and trade-off zone settings.

Features

You can define a planning time fence in the report itself. If this parameter is maintained, the system uses this as the fixing horizon. No planning time fence settings from Customizing or the scheduling agreement items are considered.

If you do not specify a planning time fence when running the report, the report checks whether there is a fixing horizon defined in Customizing and the schedule agreement item. The fixing horizon depends on the MRP binding setting in the scheduling agreement item and is determined as follows:

  • If no binding is selected, the system uses the largest number of days from fields Firm Zone, Trade-Off Zone and Planning Time Fence as the fixing horizon.
  • If the field Binding on MRP is set to 1 (Schedule lines within trade-off zone can be changed by MRP)the largest number of days from fields Firm Zoneand Planning Time Fenceis used as the fixing horizon.
  • If the field Binding on MRP is set to 2 (Schedule lines can always be changed by MRP), the fixing horizon is 0 if there is nothing defined for the material type.

Example 1:

The delivery date of a schedule agreement schedule line is today +10 days. The determined fixing horizon is today + 5 days.

In this case, the schedule line is not relevant for the report since the MRP run could potentially change the delivery date. This is because the delivery date is beyond the fixing horizon.

Example 2:

The delivery date of a schedule agreement schedule line is today +10 days. The determined fixing horizon is today + 15 days.

In this case, the schedule line is relevant for the report since the MRP run does not change the delivery date. This is because the delivery date is within the fixing horizon.

Selection

There are several selection options to select schedule agreements for the synchronization of the delivery date:

  • Select Scheduling Agreements

You can enter selection criteria to specify the scheduling agreement for which the delivery date is synchronized from related freight units. You need to fill at least one of the selection criteria.

The following options are available for scheduling agreement selection:

  • Material

  • Plant

  • Supplier

  • Scheduling Agreement

  • Purchasing Doc. Type

  • MRP Area

  • MRP Controller

  • Additional Settings
  • Planning Time Fence

You can define a planning time fence to set the fixing horizon which is used to determine relevant scheduling agreement schedule lines.

  • Parallel Processing Profile

You can define a parallel processing profile to execute the report in parallel mode.

Standard Variants

Output

The report creates an application log. The created messages can be found with transaction SLG1. Use the report name /SCMTMS/TM_SAG_PLANNING_SYNC as external ID to filter possible results.

Activities

Example






General Data in Customer Master   General Material Data  
This documentation is copyright by SAP AG.

Length: 5575 Date: 20240420 Time: 082349     sap01-206 ( 58 ms )