SAP ABAP IMG Activity ISP_IS_PL_STAMM_PARA (Set Parameters for Info Structures and Key Figures)
Hierarchy
☛ IS-M (Software Component) SAP MEDIA
   ⤷ IS-M (Application Component) SAP Media
     ⤷ JAS (Package) Application development R/3 Publishing Advertising System***
IMG Activity
ID ISP_IS_PL_STAMM_PARA Set Parameters for Info Structures and Key Figures  
Transaction Code S_KK4_74001477   IMG Activity: ISP_IS-M:L_STAMM_PARA 
Created on 19990816    
Customizing Attributes ISP_IS_PL_STAMM_PARA   Set parameters for info structures and key figures 
Customizing Activity ISP_IS_PL_STAMM_PARA   Set parameters for info structures and key figures 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISP_IS_PL_STAMM_PARA    

In this step, you set the planning parameters of information structures and their key figures for use in Sales & Operations Planning. These parameters are as follows:

Information Structures

  • Table

    This is the number of the information structure.

  • Number of rolling versions

    At any one time, the system can manage one active planning version and a number of historical versions for an information structure. You specify here the number of historical versions which you want to be stored in the system.

  • Planning method
    • Consistent planning
    • Level-by-level planning
    • Delta planning

      In consistent planning, planning levels are interdependent. The user plans at any characteristic level, and the data is then aggregated and disaggregated automatically up and down the planning hierarchy. The sum of the details always gives the planning value at the aggregate level. In contrast to level-by-level planning, the system stores the data at the most detailed hierarchy level only.

      In level-by-level planning, planning data is saved for every characteristic value of an information structure. The planning levels are independent of each other, unless they are aggregated and/or disaggregated by manual intervention from the user. In order to aggregate, you need to write a macro (see SOP: Planning Types and Macros). You perform disaggregation for a key figure using the planning table function Edit -> Disaggregate line; the system then bases disaggregation on the proportional factors in the planning hierarchy master record.

      In delta planning, aggregation is performed automatically, but not disaggregation.

  • planning plant

    The plant you enter here is used in resource leveling. Resource leveling is always carried out with reference to a plant, even if no plant has been specified in the rough-cut planning profile. For more information, see Define scheduling levels, Define routing selection, and Set planning plant for SOP.

  • storage periodicity

    The storage periodicity gives the time unit in which planning versions of the information structure are stored. The default storage periodicity is the update period defined in Customizing for the Logistics Information System.

    If the planning method is consistent planning or delta planning, this entry is mandatory.

    If the planning method is level-by-level planning, this entry is optional. If you do not define a storage periodicity, the data is saved as it is displayed in the planning table.

  • fiscal year variant

    If the storage periodicity is "posting period", you must specify a fiscal year variant.

  • factory calendar

    Make an entry here if you want to be able to disaggregate one or more key figures in this information structure with regard to time (see "time-based disaggregation" below).

  • exchange rate type

    You define here whether, for example, an average rate, a buying rate, or a selling rate is to be used for currency conversion.

  • statistics currency

    This is the currency in which you want to plan value key figures from this information structure. It will apply throughout the planning hierarchy.

  • base unit of measure

    If the planning method is consistent planning, this is the default unit in which you plan quantity key figures from this information structure. The unit can be overwritten in the planning table provided that conversion is possible either via the SI system (e.g. 1 tonne = 1000 kg) or via conversion factors defined in the material master.

    If the planning method is level-by-level planning, this is the default unit in which you plan quantity key figures from this information structure. This unit can be changed in the planning hierarchy for characteristic values above the material level provided that conversion is possible via the SI system (e.g. 1 tonne = 1000 kg). Key figure quantities are shown in the planning table in the unit of measure maintained for that characteristic value in the planning hierarchy. The unit can also be overwritten in the planning table provided that conversion is possible either via the SI system or via conversion factors defined in the material master.

    When data is transferred from SOP to Demand Management, planned independent requirements are created in Demand Management in the base units of measure of the materials. This is not necessarily the same as the base unit you maintain here. If you plan a material in SOP in a unit other than its base unit, the necessary conversion factor between the two units needs to have been defined in the material master record. Otherwise, you cannot pass on this material's data to Demand Management.

  • zero values to MRP

    You set this indicator if you want key figure values of zero to be transferred to Demand Management.

Note

When you perform this transfer, any planned independent requirements that already exist in Demand Management are overwritten with the SOP data.

  • capacity allowed

    Enter a "1" here to allow the capacity situation to be displayed for this information structure. You will then be able to carry out resource leveling for the following resources:

    • work center capacities
    • materials
    • production resources and tools
    • costs
  • capacity key figure

    If you want to carry out capacity planning in flexible planning on the basis of routings, enter here the field name of the key figure to which the capacity load is to be attached.

  • no unit conversion

    Enter an "X" here to disallow units conversion for this information structure.

  • no user exits

    Enter an "X" here to disallow the incorporation of non-SAP data into your sales and operations plans.

  • no 0 column usage

    Enter an "X" here to disallow the setting of values (for example, opening stock) in the 0 column of the planning table.

  • no event usage

    Enter an "X" here to disallow the use of events for this information structure.

Key Figures

  • forecast

    You specify whether or not it will be possible to run a forecast for this key figure in this information structure.

  • time-based disaggregation

    You specify whether or not, in the case of period splitting to a smaller period (e.g. months to weeks), you wish to disaggregate on a proportional basis.

    You use the "factory calendar" setting (see above) in conjunction with this parameter.

    Example

    The key figure is stock level and you wish to maintain a constant stock level of 100 tonnes. Therefore, you do not disaggregate (that is, you do not set this indicator); when you change the period split from months to weeks, the stock level stays at 100 tonnes.

    Example

    The key figure is planned production order quantity. You wish to view it first in months and second in weeks. In this case, you do disaggregate. The system works out the key figure values in each of the periods with reference to the factor calendar.

  • aggregation type

    This parameter is designed for use with the consistent planning method. In consistent planning, data is aggregated and disaggregated automatically to every level in the planning hierarchy. For each key figure, you choose one of three options:

  1. Average calculated

If you are in Create mode and enter or overwrite data at the aggregate level, this data is copied to the detailed level.

If you are in Change mode and overwrite data at the aggregate level, the values at the detailed level change so that each one represents the same proportion of the aggregate value as before.

If you create or change data at the detailed level, the new value at the aggregate level is calculated as the mean average of the values at the detailed level.

This option is designed for key figures that represent prices (for example, sales price) or percentages (for example, percentage of purchasing budget already released).

  1. Total created

This is the default setting for planned key figures.

The system performs aggregation by totaling the key figure values at the detailed level and writing the total to the aggregate level.

The system performs disaggregation using the proportional factors. In consistent planning, the proportional factors can be determined in four ways:

  • You can have the system calculate them on the basis of existing (normally actual) data (the menu option Master data -> Calculate proportions -> Using actual data). This calculation gives generic proportional factors that will be valid for all key figures, characteristic values, and periods unless they are overridden.
  • You can have the system calculate them on the basis of proportional factors already entered for adjacent levels in the planning
Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ISP_IS_PL_STAMM_PARA 0 I170007158 O  
SIMG ISP_IS_PL_STAMM_PARA 1 I170007159 Information System for Advertising Management 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
PLANPARAM C - View cluster MC7F ISP-IS-001 Planning parameters 
History
Last changed by/on SAP  19990816 
SAP Release Created in