7 ways to generate events for business objects.... Change Documents

When a change to a certain field in a document is made then an event is raised.

• Wizard: SWU_EWCD

                                                              i.      Choose the Business object and event that you want raised

                                                            ii.      Choose the change document object and the type of event (create / change / delete)

• Set up change docs using SCDO if required
• Transaction: SWED, define workflow properties for change docs
• Transaction: SWEC is the change document event linkage table maintenance transaction. Allows for restricting to only changes to certain fields

Logistics Information System (LIS)

When an exception is reached in LIS an event is raised.

• Wizard: SWU_EWLIS

                                                              i.      Choose the Business object and event that you want raised

                                                            ii.      Choose the LIS exception that you want to raise the above event for

• Transaction: AWUW is the maintenance transaction for the LIS exception linkages with business object events

Business Transaction Events (BTE)

If a BTE is raised then raise a business object event.

• Wizard: SWU_EWBTE

                                                              i.      Give a new function module name together with an existing function group

                                                            ii.      Supply the applicable business transaction product and event (See transaction FIBF for BTEs)

                                                          iii.      Choose the Business object and event that you want raised

Change to HR Master Data

Changes to HR master data can trigger business object events.

• Linking object type to Infotype

                                                              i.      Transaction: SWEHR1

• Event linkage

                                                              i.      Transaction: SWEHR2 (SAP), SWEHR3 (Customer)

                                                            ii.      Link the object type, infotype, subtype (as defined above) and update activity to object type and event

Status Management

Changes in statuses of business documents can trigger business object events.

• Transaction: BSVW

                                                              i.      Customer settings (for user status) and System settings (for system status)

                                                            ii.      Add your status object category, schema

                                                          iii.      Choose the Business object and event that you want raised

                                                          iv.      Select the line and add the status restrictions

1.      Add the particular user / system status

2.      Select inactive = checked if you want to raise the event if the status was turned off

3.      Select inactive = NOT checked if you want to raise the event if the status was turned on

Message Control

Output messages processed through message control can be configured to raise a business object event.

• Transaction: NACE

                                                              i.      Select the applicable application and add your output type of transmission medium 9

                                                            ii.      Make sure your access sequence and procedure are configured in conjunction with the output type

                                                          iii.      Once the output type is configured add the condition record which specifies the business object event to be raised.

Workflow start conditions

Workflows can be triggered when certain criteria is met for a particular business object

• Transaction: SWB_COND
• Need to ensure the condition is entered and that the start condition is active

Standard Events

Standard events are often raised by standard business objects. See if you can utilize them for your workflow triggering.

• Transaction SWETYPV is used to activate this event linkage with your receiver task / function module.

 

Other Event related transactions

• SWEINST/ SWE3 – Instance linkage transaction – Used for terminating event and wait for event linkages
• SWU0 – Simulate an event
• SWUE – Create an event
• SWEL – Event trace
• SWELS / SWE4 – Activation of the event trace
• SWEM – Configure event trace restrictions
• RSWELOGD – Delete event trace
• SWEQBROWSER – Event browser – For events that make use of the event queue
• SWEQADM – Event queue administration
• SWEQDEL – Delete event queue
• SWE2 – Event type linkages similar to SWETYPV
• SWE5 – Event linkage check report
• SWE_CD_TST – Test event creation via change documents