SAPSCMCofguten | 84 vent handler as varios components (gue 8.18 that all nod wo beimegraed for beter event reporting nposes. The appltion objet ID together with he he busiess process ype serve a tefercace between nt handle in SAP Event Manageme ‘oles nthe gppiction syste ppliation objet spe and thee nt andthe conesponding aplication [= 1h Se | Event Codes Event codes are defined fie both planned Management. The event mesige posting fi ‘contains the event code thatis mathe nt ‘nd unplanned events tn SAP Event tom the appli system (SAP ec) the SAP Event Management event code re defining the event code, we musts dein the aplication objet code and Tracing igure 8.15), wich se the event handler craton or update in SAP E dutng the event posting. for vesasakey during vent Management, In Transaction NT + BENT HANDLERS AND EVEN Dent cove sere cusromtzne, PRO, follow the menu path Eva Hanacta Next, define the expected evs Ses order, delivery invlce The nomenclature ofthe even the event mesige fom at codes forthe scenai gure 8.16: consiting of nd shipment information from appiation system, i code an be smart the event code that's posted he aplation system. tn Trasiction SPR, followExpected Event Pre An expected event profiles configured to define ty fo he senate. The event code of SAP Evem Management and ent ce (of SAP ECE (Figure 8.17) are matched to report the event Inthe eve Facing uring the event message posting. Within he ro {tv sls dened to check the proces and report overdue if the the sequence of the even acti expected event monitor ‘arent status ofthe onder toca business events se ne reported within a toler Parameter Mapping Paraetesare used to tore abies forthe event land, Tree cet te store in SAP Event Manageme ‘ypes oF pram Control parameters (Pure 8.19) pr theevents posted in SAP Event Manage. or Selection teria S3stem parameters te stored in extension bles for index purpose. “he pron SAP ven Management are mapped with the appiicton stone updated during he event ype posting fom sarees ny determine the process steps once met. Info parameters at for reporting Parameters and Status Attbutes he status atribute probe Gigure 8.19 helps provide vsibly ofthe business "oes sats toward the onde flllment,Statses ats when the tamer, ecoded nthe appiation system. Table 2 lst the(nem SIC hoe! ee Delve packed: expected Deter te: erp 8.4.2 Reaction to Evest In the ruleset we define how the system reacts toa reported and unreported ‘rent In TansactionSPRO, follow the mens path EVEVE MAMAGEM# Recon To EvENT + Dew RULE SrA rule set consis of three parts, Determine how to react to an event and defines the actvides and the Define hw the vent mesg ar process ~ single or multiple eps conditions Define which tasks need toe executed in the re set You can confgie the condition either with the condition eto or with ane tion module. create the function module, use the copy of /sietet wut. Cone PLATE, Rules Fare 8.20) are created bse onthe expected event, sd activ tes are but used on each event. A genete event £4 £C_shonit is included in the rules wo spdate se Expected Even dite asa tue ele The activites con ‘nctue the tas of updating the status ofthe event hile, creating alert natifica ton fr any unexpected event eporting (eg, delivery lt), updating paraneters 7