ECA Basics - PowerPoint PPT Presentation

1 / 39
About This Presentation
Title:

ECA Basics

Description:

November 2001 ECA Basics & More Manage 2000 6.5C SP6 presented by Don Luoto Powerwave Technologies dluoto_at_pwav.com THE POWER IN WIRELESS Agenda ECA what is it? – PowerPoint PPT presentation

Number of Views:79
Avg rating:3.0/5.0
Slides: 40
Provided by: DonaldL157
Category:
Tags: eca | basics

less

Transcript and Presenter's Notes

Title: ECA Basics


1
ROI Systems, Western Region User Group November
2001 ECA Basics More Manage 2000 6.5C
SP6 presented by Don Luoto Powerwave
Technologies dluoto_at_pwav.com
THE POWER IN WIRELESS
2
Agenda
  • ECA what is it?
  • Setup
  • Workshop ECA.BUILD
  • How does it work?
  • Tables for referencing contacts
  • ECA.SCAN - demo
  • Reports Debugging
  • Advanced stuff
  • QA

3
ECA What It Is, What It Does
  • What it is.
  • . The slickest thing from ROI since CTO on
    release 6.2.
  • . A great tool for management and users.
  • Event
  • Condition
  • Action
  • What it does.
  • Monitors data activity in Manage 2000.
  • Create, delete, change, read.
  • Notifies someone based on a triggered event.
  • Email, FAX, pop UP message, action.1 record.

4
ECA Setup
  • ECA.AGENT.CTLS
  • Phantom process that looks for unprocessed ECAT
    (transaction) records.
  • One phantom process per account (MAIN,TRAIN,etc).
  • Uses, 1 M2K license and 0 IBM/U2 (Unidata)
    license per phantom.
  • MONITOR.CONTROLS (optional)
  • Add for each user so that ECA processing can be
    monitored. Standard MONITOR.OPTIONS.
  • ECA.ALERT.01 INBOX
  • ECA.ALERT.01 STOPPED
  • ECA.ALERT.03 ERROR
  • ECA.SUM.01 AGENT SUMMARY STATUS

5
ECA Setup ECA.AGENT.CTLS
6
ECA Setup CONTACTS
  • CONTACTS
  • All ECAs require the setup of a contact in order
    to send an email of any kind.
  • M2K email
  • Intranet email
  • External internet email
  • Required fields for email
  • Screen 1 - Record ID, Name, File
  • Screen 2 - Type EMAIL
  • Screen 2 - E-Mail somebody_at_somewhere.com
  • Screen 2 - Auto Notify Y

7
ECA Setup CONTACTS, Screen 1
8
ECA Setup CONTACTS, Screen 2
Manage 2000 email address
9
ECA Workshop Starting Simple!!!!
  • Objective
  • Create an ECA to notify via email when a new part
    is added to the item master.
  • ECA.BUILD
  • Screen 1 Define the ECA and related files and
    functions
  • Screen 2 Create and format the output
    notification
  • Screen 3 Define the EVENT ACTION

10
ECA Workshop ECA.BUILD screen 1
11
ECA Workshop ECA.BUILD screen 2
12
ECA Workshop ECA.BUILD screen 2
Screen 2, Prompt 12 Body, in full screen edit
mode \EDP
13
ECA Workshop ECA.BUILD screen 3
14
ECA Workshop Test it with ITEMS
Test the ECA by entering a new part in ITEMS.
15
ECA Workshop Resulting Email
Resulting Manage 2000 Email (The body of an
Outlook email should be identical)
16
How does it work? Notes on Basic Function
  • Most M2K transactional functions have code in the
    controlling program that call the ECA.UPDATE
    program. i.e. SO.ENTRY is run by program SOP111.
  • If function is a data update such as ITEMS, then
    the controlling program MT500 calls ECA.UPDATE
    program.
  • The ECA.AGENT.CTLS does NOT have to be running to
    have records written to the ECAT file.
  • The ECAT (transaction) file creates 1 record for
    every notification that is attempted.
  • A single ECA triggered event that is sent to 5
    people will create 5 ECAT records.

17
How does it work? (basic functionality)
hooks in program trigger ECA test
ITEMS (function)
SOURCE USER Create Part Number EVENT
MT500 (program)
IM IPL
ECA.UPDATE (program)
ECAT (transactions)
Processed set to Purge
Unprocessed
ECAD (ECA.BUILD)
ECA.AGENT.CTLS (phantom process)
?
CONTACT.MASTER
email VSI Fax M2K Alarm Action.1
RECIPIENT Receives notification ACTION
Source User Pop-Up
18
Tables for Referencing Contacts
  • Everything must end with a contact
  • ECA.KEYWORDS groupings of contacts
  • Attach ECA.KEYWORDS to CONTACTS screen 1 and
    ECA.BUILD screen 3
  • ECA.SYSTEM.REFS links record data to contacts
  • Planners
  • Buyers
  • Sales Reps
  • Custom Fields

19
Tables ECA.KEYWORDS
20
Tables ECA.SYSTEM.REFS
21
Tables ECA.SYSTEM.REFS
22
ECA Workshop Add Conditions
  • Add an EVENT condition that excludes parts with
    the Inventory Type Code CO
  • CO non inventory items used for CTO development
  • Add an ACTION condition so that the planner
    only receives manufactured parts.
  • NOTE The condition must be TRUE to allow
    processing of the EVENT and/or ACTION
  • Read the prompt help for entering multiple
    conditions with and/or logic.

23
ECA Workshop Add Conditions
24
ECA Workshop Test Conditions
  • Test 1 Add a part with the inventory type CO
    and Lead Time Code P
  • Expected result no emails sent
  • Test 2 Add a part with the inventory type CM
    and Lead Time Code M
  • Expected result email sent to the CONTACT and
    to all CONTACTS with ECA.KEYWORD NEWITEM
  • Test 3 Add a part with the inventory type FA
    and Lead Time Code M
  • Expected result same as test 2 plus the PLANNER
    on record for the part

25
ECA Workshop Simple Pop UP
A pop up browser of the notification can be sent
to the source user.
26
ECA Workshop Simple Pop UP
The user entering the part number will get this
upon ENDing.
27
ECA Workshop Simple Pop UP
NOTES All Manage 2000 logins must be setup in
CONTACTS for Pop Up ECAs to work. The CONTACT
record key must match the SYS.USER record key.
28
ECA.SCAN
  • Use to periodically scan files for specific
    existing data and send a notification if
    conditions are met.
  • Can be run manually or perhaps launched by DJS
    (delayed job stream) or BATCH.MASTER.

29
ECA.BUILD for ECA.SCAN
SCREEN 1
30
ECA.BUILD for ECA.SCAN
SCREEN 2
31
ECA.BUILD for ECA.SCAN
SCREEN 3
32
Reports Debugging Methods
  • Key Reports
  • ECA.TXN.DTL.RPT
  • Prompt.Update.Truth.Results
  • Produces a browser report to the source user that
    traces and displays the entire ECA logic.
  • USE TCL to analyze the ECAT file
  • LIST ECAT WITH Src_Eca_Key DEMO_1

33
Advanced Stuff
  • I descriptors
  • Can be used in all cases where a dictionary item
    is used.
  • Prompts 8 9 in screen 2 of ECA.BUILD work like
    a TRANS I - descriptor
  • Email formatting
  • /INCLUDE.SENT.TO.LIST
  • List other users notified of the ECA
  • /FORM.FIELDS
  • Used to format columns of multivalued data
  • Add a hyperlink that takes the email recipient to
    a help document
  • Complex conditional statements

34
Advanced Stuff, I-Descriptors
Works like a TRANS I-Descriptor
35
Advanced Stuff, Formatting
36
Advanced Stuff, Complex Cond
37
General Notes
  • Advise users to NOT to use MS Word as their
    email editor. ECAs are best viewed in plain
    text.
  • Watch your ECAT file size, it will increase
    dramatically! Use FILE.STAT RESIZE.
  • For testing purposes, change your SYS.USER for
    Screen 6, Pmt 8, Delete Self in Sent Mail to N.
    Otherwise you cannot send and an ECA email to
    yourself.
  • wSendmail for NT or sendmail UNIX will need to be
    installed and configured before emails can be
    forwarded to MS Exchange.
  • There are treasures where some transactional
    functions do not trigger the ECA for certain
    files. i.e. PO.RECEIPTS for the IT file.

38
General Notes
  • Create the ECA as simply as possible at first to
    confirm that the ECA will trigger and send the
    notice. Then add the gravy.

39
Q A
  • Thank you!
  • Questions?
Write a Comment
User Comments (0)
About PowerShow.com