SAP ABAP IMG Activity SIMG_CFMENUOHP3OOET (Create Business Event Type)
Hierarchy
☛ SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR
   ⤷ PE (Application Component) Training and Event Management
     ⤷ PP9C (Package) Training and Event Management - Customizing
IMG Activity
ID SIMG_CFMENUOHP3OOET Create Business Event Type  
Transaction Code S_AHR_61011888   IMG Activity: SIMG_CFMENUOHP3OOET 
Created on 19981221    
Customizing Attributes SIMG_CFMENUOHP3OOET   Create Business Event Type 
Customizing Activity SIMG_CFMENUOHP3OOET   Create Business Event Type 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOHP3OOET    

In this step, you create business event types. A business event type is a general description of a business event or event date. It serves as the blueprint or model from which individual event dates can be created. In contrast to a business event date, a business event type cannot be scheduled to take place at a particular time.

Business event groups, types, and dates together make up the business event catalog.

The data you store for the event type is proposed as default values when you create or plan event dates. You may overwrite these proposals.

When you create a new business event type, you can use an existing one as a reference to copy from. Here, too, you may overwrite the default values that are proposed.

You can maintain the following infotypes for business event types:

  • Description

    This infotype consists of an extended business event type text, event contents, and notes. The texts you store here can be included in the business event brochure.

  • Prices

    You can store an internal and an external price for the event type. The internal price is used for internal activity allocation purposes, while the external price is used for billing purposes.

    You can determine a price proposal for an event by choosing Proposal. This requires that you have already maintained the following data: internal currency (under "Costs"), costs, capacity, and time schedule. If you want to use the price proposal function, you must first maintain the above- mentioned data and then the Prices infotype.

  • Main schedule model

    Here, you create a subtype of the Schedule Model infotype that defines the time schedule of a business event type. You have the option of creating a schedule with pattern (in the step Define Time Schedule), a schedule without a pattern, or a user-defined schedule.

  • Capacity

    You can store a minimum, optimum, and a maximum number of attendees for the event type.

    Capacity information plays a role in the following functions:

    • Bookings: the capacity defines the borderlines between normal, essential, and waiting list bookings.
    • Resource selection: the system uses the capacity specified for the event type when proposing suitable resources for the event. It assigns a suitability value to resources based on this.
      • The closer the capacity of the resource is to the event capacity, the better suited the resource is for the event, and the higher the suitability value assigned to the resource as a result.
    • Price proposal: when determining a price proposal for an event type, the system uses the optimum capacity defined.

      The capacity stored for the event type is automatically read if no capacity is stored for the event itself.

  • Business event type info

    You can specify whether the event type is a convention or a normal event.

    In addition, you can specify whether the event type is to be included in the brochure. When you create the event brochure, you have the option of including "only selected event types" in it. You make this specification when you set this indicator for the event type.

    The No Intranet indicator lets you specify that a business event type is not published in the ESS applications of Training and Event Management.

    In this infotype, you also make specifications for internal attendees and instructors with respect to the Time Management component.

    • No integration: You select this indicator to deactivate integration with Time Management (PT) so that no attendance records are written to PT for attendees or instructors and no availability checks are performed.
    • Allowed in time off: You select this indicator to allow a person to be booked as attendee or instructor regardless of whether time off records exist for the person in PT.
    • Minimum percentage (for attendees): You use this option to specify a minimum percentage attendance required at an event. The percentage you enter is the minimum time an attendee must be present at an event to prevent the booking being considered invalid and automatically canceled as a consequence.
      • The value you enter here overrides the setting for this event type made in the SEMIN TIMEP entry in Define Attendance Types.
      Note
      The Time Management (PT) settings (No integration, Allowed in time off and minimum percentage), which you can specify here, are only displayed when integration with PT is active.
  • Validity period (Depreciation meter/Validity infotype)

    You can specify here the period of time during which attendance of a business event is valid as a prerequisite for attendance of a follow-up event.

  • Relationships

    In Training and Event Management, information and attributes of objects are stored in infotypes and relationships. You can store the following relationships for business event types in the Relationships infotype:

    • "Belongs to business event group":
      • Here you specify the superior business event group.
    • "Requires resource type":
      • Here you specify the resource types that are needed to carry out an event of this type.
      CAUTION!
      You must maintain this relationship if you want to use resources in Training and Event Management.
      If you want to use the resource types Instructor and Material, you must also maintain the following relationships:
      "Is held by" (for the resource type Instructor) and "uses for attendee/business event Material" (for the resource type Material).
    • "Is held by person"/"... user"/"... external person"/ "... contact person":
      • You specify the instructor(s) to be proposed for the event type as a rule.
    • "Imparts qualification":
      • Here you specify the qualification attained by attending an event of this type. This relationship is used for the check the system carries out for attendance prerequisites and when transferring qualifications to attendees during follow-up processing. This information is stored in the Procedure infotype, which you also maintain for the event type.
    • "Presupposes business event type":
      • Here you specify the event type defined as prerequisite for attendance. In the Procedure infotype and under Attendee Checks you can specify whether a check is carried out for this prerequisite during booking transactions.
    • "Presupposes qualification":
      • Here you specify the qualification defined as prerequisite for attendance. In the Procedure infotype, and under Attendee Checks you can specify whether a check is carried out for this prerequisite during booking.
    • "Is planned for job":
      • This relationship lets you define the target group (represented by the object type 'Job') of an event type. Target group information can be included in the event brochure.
    • "Is organized by organizational unit"/"... company":
      • Here you specify the organizer. The information stored here as to whether the organizer is internal (organizational unit) or external (company) is used for billing and cost allocation purposes and for the Correspondence function.
    • "Uses material (for attendee)":
      • Here you specify the material that is required per attendee. You specify object types, not concrete materials. For example, you can specify that the event type requires the material type 'Course book' per attendee.
    • "Uses material (for business event)":
      • Here you specify the material that is required per business event. For example, you can specify that the event type requires the material type 'Overhead projector'.
    • "Cost center assignment":
      • Here you relate a cost center with the master cost center (for accounting purposes for the cost items of a business event).
    • "Has attendee appraisal model"/ "has business event appraisal model".
      • You can specify what forms of appraisal you want to use for business events of this type as attendee appraisals and as event appraisals. The entries you make here override the settings made under Set Up Control Parameters.
  • Further information
    • On this tab strip, you can maintain the following infotypes for the event type:

  • Business event demand
    • Here you can specify the demand that exists for event dates of this type per quarter, per location, and per language.
    However, we recommend that you determine demand in the dynamic Planning menu instead.
  • Billing/Allocation Info
    • Here, you assign business event types to sales areas. You need sales areas when you carry out billing for business events. You also specify the controlling area and the activity type for internal activity allocation.
  • Costs
    • Here you assign costs to business event types. The&#x
Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional 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_CFMENUOHP3OOET 0 PH40000002 Training and Event Preparation 
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
PDST T - Individual transaction object OOET 0000000020 Create Business Event Type 
History
Last changed by/on SAP  20020503 
SAP Release Created in