SAP ABAP IMG Activity /SAPTRX/ASC0AOAI (Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types)
Hierarchy
☛ PI_BASIS (Software Component) Basis Plug-In
   ⤷ CA (Application Component) Cross-Application Components
     ⤷ /SAPTRX/CUST_AI_A (Package) SCEM AI IMG Structure
IMG Activity
ID /SAPTRX/ASC0AOAI Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types  
Transaction Code /SAPTRX/68000161   IMG activity 
Created on 20020802    
Customizing Attributes /SAPTRX/ASC0AOAI   Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types 
Customizing Activity /SAPTRX/ASC0AOAI   Define Used Bus. Proc. Types, Appl. Obj. Types, and Evt Types 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ASC0AOAI    

Use

In this IMG activity, you specify the business process types that you want to use for your supply chain event management-relevant (SCEM-relevant) processes. The input help displays all the business process types that you have specified in transaction /SAPTRX/ASC0TO (see Define Business Process Types).

You assign the SCEM-relevant application object types to the business process types. SAP Event Management (SAP EM) only creates event handlers for these types of objects.

If you want to deactivate the application log for an individual object but continue to write it for other objects, you can deactivate it for the relevant application object type or event type.

Requirements

You have defined conditions or functions for SCEM relevance. The application system evaluates these conditions and functions to determine the SCEM relevance of an application object.

Standard settings

Activities

Recommendation

We recommend the following process for defining the used business process types and their conditions or functions:

  1. In this IMG activity, first define the business process types and the application object types with their main object table and master table.
  2. Then define the function or condition for the SCEM relevance of the application object types in transaction /SAPTRX/ASC0TF or /SAPTRX/ASCTC respectively.
  3. Assign these conditions or functions to an application object type in transaction /SAPTRX/ASC0AO.

Defining Used Business Process Types

  1. Under Define Used Business Process Types choose a business process type.
  2. Choose an update mode for updating the data of the application interface.
  3. Choose a processing mode that determines how the application interface processes the application objects for this business process type.
  4. Enter a description for the business process type.
  5. Save the entries.

Defining Application Object Types for a Business Process Type

  1. Under Define Application Object Types choose the General Data tab page.
    1. Specify a sequential number for flow control.
      2. Recommendation
      The sequential number for each application object type within a business process type should always be different and should follow in an ascending order, so that the processing order is clear.
      For performance reasons, we recommend that you give the most frequently used application object types the lowest sequential numbers. The application system checks the Event Management relevance condition or function for an application object type following the order of the sequential numbers.
      90% of your shipments are LTL shipments and only 10% are container shipments, for example. You define a business process type shipment with the two application object types LTL shipment and container shipment. You give application object type LTL shipment sequential number 1 and you give container shipment sequential number 2. When evaluating the condition or function for the SCEM relevance of an application object type, the application system only processes the application object type with sequential number 1 for 90% of the cases, as it already finds an application object type.
    2. Specify the business object reference.
    3. Specify the following for how the application system behaves when determining SCEM relevance:
      4. Whether an application object of this application object type is SCEM-relevant, so that the application system checks the SCEM relevance condition or function for this object.
      Whether an application object may be used for status queries for an event handler in SAP EM. For example, you can specify the purchase order number for a shipment as an application object and allow it to be used for queries. You do not then necessarily need the tracking ID or shipment ID for queries, but instead you can use the application object ID of the purchase order to query status information about an event handler.
      Whether the system should stop determining application object types for this application object when it finds an application object type for this application object for a business object. The system then no longer checks all other application object types for this application object.
      Whether an event handler that belongs to an application object that is no longer SCEM-relevant should be deleted in SAP EM. If the system has found an SCEM-relevant application object by evaluating the SCEM relevance condition or function, and has reported this to SAP EM, SAP EM creates a corresponding event handler. If you set the indicator, the event handler is deleted, if, when checking for SCEM relevance again, the application system determines that the application object is no longer SCEM-relevant.
    4. Specify how the application system reacts if errors occur when determining SCEM relevance.
  2. Choose the Control tables tab page.
    1. Specify a main object table for the application object.
    2. Specify a master table, if dependencies to another table exist for checking the SCEM relevance condition or function.
      3. You want to track all deliveries for a shipment, for example. The information about the deliveries (for example, the delivery note numbers) is found in the main object table VTTP. The information about the shipment (for example, the shipment number) is found in the master table VTTK . In this way, you can use the shipment number to query the corresponding deliveries in SAP EM.
    3. Specify the table for deleted objects, if the corresponding event handler or event handler sets should also be deleted in SAP EM when the application object is deleted.
    4. Specify the reference between the main object table and the master table.
  3. Choose the Object Identification tab page.

    Specify the way in which the application object ID is formed.

    • If you want to use only one or two fields from the data sources of the application object to determine the ID, choose Determine from Field as the application object ID method (AOID method) and specify the relevant fields from the main object table and the master table.
    • If you want to use more than two fields from the data sources of the application object, choose Determine by Function as the AOID method and specify the extractor (function module) that is to generate the application object IDs.

      The application object ID is the technical key between the application object and the event handler, and, together with the application object type and the application system name, it forms the unique identification between the application object and the event handler.

  4. Choose the Event management relevance tab page.

    Assign the Event Management relevance condition or function to the application object type.

    You define the condition or function in transaction /SAPTRX/ASC0TC or /SAPTRX/ASC0TF respectively.

    Recommendation

    For performance reasons, we recommend that you use functions when determining performance-critical processes. This is because the system evaluates functions quicker than it evaluates conditions.

    The input help only offers you Event Management relevant conditions or functions that match the main object table and master table that have been specified.

  5. Choose the Parameter setup tab page.
    1. Specify the data sources for the tracking ID.
      2. Specify the field directly, if the system should copy the tracking ID directly from the main object table or the master table.
      Specify the function, if the system should copy the tracking ID from several main object tables or master tables, or if it should calculate the tracking ID.
    2. In the parameter setup, specify the functions for extracting data from the application system for:

  • The control parameters
  • The info parameters
  • The application object IDs and application object types that are permitted for status queries
  • The expected events

  1. Save the entries.

Define Event Types for a Business Process Type

You assign the SCEM-relevant event types to a business process type.

The application system evaluates your defined conditions and functions. It uses the evaluation results to determine whether the change to an application object requires an event to be sent to the relevant event handler in SAP EM.

  1. Under Define Event Types choose the General Data tab page.
    1. Specify a sequential number for flow control.
      2. Recommendation
      The sequential number for each event type within a business process type should be different and should follow an ascending order, so that the processing order is clear.
      For performance reasons, we recommend that you give the most frequently used event types the lowest sequential numbers. The application system checks the event management relevance condition or function for an event type following the order of the sequential numbers.
      For example, 90% of your deliveries are incomplete and only 10% are complete. You
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 
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
/SAPTRX/VC_AOTYPE C - View cluster SM34  
History
Last changed by/on SAP  20021114 
SAP Release Created in