Hierarchy

⤷

⤷

IMG Activity
ID | IST_OM_OP_BUSEVENT | Define Permitted Business Events |
Transaction Code | S_KK4_74002443 | IMG Activity: IST_OM_OP_BUSEVENT |
Created on | 19990817 | |
Customizing Attributes | IST_OM_OP_BUSEVENT | Define Permitted Business Events |
Customizing Activity | IST_OM_OP_BUSEVENT | Define Permitted Business Events |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | IST_OM_OP_BUSEVENT |
In the first step in this activity, you can define Business Events.
In the second step, you define the technical settings for the business events, that is, you assign the required function modules and screens.
In the third activity, you assign default business events (standard business events) to the ICOM actions.
Example
1. Maintaining the Business Events
Bus.event | Description | Button descr. | Action |Trnsactn
----------------------------------------------------------------------
NEW | Create new | Create | Create newICOM obj.|TNEW
Bus.event:
- key describing the business event
- can be freely defined
Description:
- short text that describes the business event on the user interface
- can be freely defined
Button descr.:
- short text that appears on a button on the user interface
- short meaningful text
Action (ICOM action):
- specifies how the object history is affected (how does the business event affect the object tree?)
- fixed values:
- create new ICOM object
- change existing ICOM object, do not reset
- delete existing ICOM object
- display existing ICOM object
- reset existing ICOM object to its former state
Transaction (business transaction):
- specifies the processing status of an object and thus influences the permitted transactions (which action/function can be executed?)
- you can choose the values using the possible entries function (F4)
- you maintain the entries using the TJ01 check table
2. Technical Settings
Business event - Short description of the business event
FM name event: - PBO module
FM name event: - PAI module
No. current screen: - Screen for overall display (MAIN/container)
No. current screen: - Screen for header (HEAD)
No. current screen: - Screen for content/application (BODY)
No. current screen: - Screen for chapter (CHAP)
The overall screen is composed of sub-screens:
MAIN
|
--------------------------------
| |- HEAD
--------------------------------
| | |
| | |
| | |
CHAP-| | |- BODY
| | |
| | |
--------------------------------
You must specify the first screen (MAIN). Specifying HEAD, BODY and CHAP is optional.
Requirements
Standard settings
Recommendation
Activities
You can create new entries, or copy existing entries.
- Create new entry:
- Choose New entries.
- Complete the BUS EVENT, Description and Button descr. fields.
- Assign a CA, BE header and Trnsactn to the business event using the possible entries function (F4).
- Confirm with ENTER.
- Copy an existing entry:
- Select an existing entry.
- Choose Copy as ....
- Change the entry as required.
- Confirm with ENTER.
To define the technical settings for the business events already defined, proceed as follows:
- Select a row in the BE Maintenance view.
- Choose --> technical settings.
- Choose New entries.
- Enter the abbreviation for the Business Event.
- Enter the technical name for the PBO and PAI modules.
- Enter at least the number for the MAIN screen (if required complete all fields).
- Choose Save.
Further notes
3.Default business event per ICOM action
Here you allocate a default business event to each ICOM action. This is a business event that is automatically used (without a manual entry) for an ICOM action.
Action | Bus.event
------------------------------------------
Create new ICOM object | NEW
The default business event NEW is assigned to the ICOM object Create new ICOM object.
Example of use:
If a customer adds an additional product to his shopping basket (Transfer material), this corresponds to the above ICOM action. Without further prompting the ICOM then invokes the NEW business event to process the material number entered.
Business Attributes
ASAP Roadmap ID | 105 | Define 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 | IST_OM_OP_BUSEVENT | 0 | I500000144 | Order Processing |
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 |
IST_C_EVENT_01 | C - View cluster | SM34 |
History
Last changed by/on | SAP | 19991103 |
SAP Release Created in |