SAP ABAP IMG Activity SIMG_CFMENUOLPKGRAF (Define graphical object type)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ PP-CRP-LVL (Application Component) Capacity Leveling
     ⤷ CY0C (Package) Customizing Capacity Planning
IMG Activity
ID SIMG_CFMENUOLPKGRAF Define graphical object type  
Transaction Code S_ALR_87004068   IMG Activity: SIMG_CFMENUOLPKGRAF 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLPKGRAF   Define graphical object type 
Customizing Activity SIMG_CFMENUOLPKGRAF   Define Graphical Object Type 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLPKGRAF    

In this section, you define the following for the graphic planning table:

1. Defining application-specific object types

In this step you define the data from the application object needed for the graphic display.

In this case the capacity requirements and the corresponding pegged requirements, such as operation, phase and work order are indicated as the application object.

You can define several graphic object types for one application object. This is useful if the data needed for the graphic display is clearly different in different situations.

Example

In the following example it is wise to define several graphics objects for one application object:

  • An operation from the "work order in pool" is displayed with
    • setup time
    • processing time
    • teardown time
    • wait time
  • An operation from the "work order in task list" is only displayed with
    • setup time
    • processing time
    • teardown time

In the SAP standard package, several graphic object types are created for objects from the work order.

Note

  • If various application objects are grouped in a planning table, such as work orders and planned orders, you also have to define the selection of the graphic object type.
  • The index 0 for every graphic object type is reserved for a text field that is displayed when the cursor is placed above the object. Select a text field which is as expressive as possible for this text field, such as the operation text.
  • You use the graphic object type selection to indirectly specify which graphic object types are used in a profile for the planning table.
  • The performance of the graphic decreases proportionately with the number of fields. So you should not use any fields that you do not need in the graphic object type.

Standard settings

Graphic object types are predefined in the standard SAP package.

Recommendation

You should use the standard SAP package without changing it.

If necessary, you should define your own graphic object types.

2. Defining the object representation

In this step you define the graphic display for a graphic object type. This display arises through the combination of graphic elements e.g. bars, lines or symbols.

You can define several object representations for each graphic object type. This is useful if you want to mark application objects which have different properties using their display.

That is why in the standard SAP package several object representations are created for different graphic object types.

Note

You can use the object representation selection indirectly to specify which object representations are used in a planning table profile.

Example

  • A "dispatched operation" is represented by green bars for setup, processing and teardown.
  • A "released operation" is represented by bars for setup, processing and teardown.

Standard settings

Object representations are predefined in the standard package.

Recommendation

Copy the standard settings without changing them.

Activities

If necessary, create your own object representations.

3. Specifying the object representation selection

In this work step you define the decision steps that lead to the selection of the object representation.

You can use the following for the selection:

  • every field of the capacity requirements
  • every field for the pegged requirements for the capacity requirements
  • a status profile that is defined for the application object

The overall decision is divided into one or more decision states. Every decision state consists of one or more decision steps that are worked through according to the decision sequence.

The decision starts with the decision status "0" and the smallest decision sequence (in the sequence "1").

In every decision step a statement is checked whether it is true or false:

  • If it is true and if an object representation has been entered then the overall decision has been successfully taken.
  • If it is true and if no object representation has been entered then the decision is continued with the smallest decision sequence in the "next decision state" given.
  • If it is false then the decision is continued in the next largest decsion sequence in the same decision state.

There are three sorts or statements:

  • Field comparison

    Here, the contents of the field in a structure is compared either with a comparison value or with the contents of a field.

    Various comparison operators are available for the field comparison, among others the operator CP ("contains pattern"), that checks whether a character string is contained in another. You can find more information on comparison operators in the documentation BC-ABAP/4 user manual.

A date field is compared with a date that is derived as follows from today's date: As a comparison value enter a positive or negative number that the system interprets as a number of days and adds to today's date. This date is the actual comparison value. In the following examples of logical relationships with a date field the statements in parentheses are the entries with which the statements on the object representation selection are defined:

  • < Date field > < GE > today date + < -10 > days
    • This statement is true if the date in the date field is at the earliest 10 days in the future.

  • Status query

    Structure and object number denote the object for which the status profile is evaluated. You enter the status profile that is to be checked as the "comparison value". The comparison operator must be "ST".

  • True statement

    This statement is always true, that means that a false statement can never arise in a decision step. The comparison operator must be "DEF".

Selected fields for comparisons

Fields ERROR_MASK in structure KBED

If an error arises with the following functions in capacity leveling then a 1 is written in the field ERROR_MASK. The place where the 1 is written depends on the function.

Function     for error 1 in

Scheduling     1st position

ATP check     2nd position

Taking setup time into A/C     3rd position

General selection function     4th position

Other     5th position

Note

You can only use pegged requirments in the field "structure" that are read by the object set in the framework of the "selection" with the capacity requirements.

Requirements

In order to be able to define the decision steps for the selection completely you must already have edited the work step "Define object representation".

Activities

Define the object representation selection.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-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 SIMG_CFMENUOLPKGRAF 0 HLA0006233 O HLA0006256  
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
VC_TCY55 C - View cluster OPG9 03 Define Graphical Object 
History
Last changed by/on SAP  19981222 
SAP Release Created in