...
prevent data entry errors when allocating accounts for new staff (since the required ID will already be on file, the CAWIS manager need only assign a Role code and password ) This was a frequent issue when CAWIS was first released.
prevent conflicts with new external WSDRS Userids since they are allocated with the same logic as used by TC Directory. (Enhancement request : ALL new external WSDRS userids should be allocated with a numeric digit suffix)
...
SDR ORGANIZATION ID | TYPE | DESCRIPTION |
|---|---|---|
51171000 | TC DATA ENTRY | All of Continuing Airworthiness (AARDG) |
30000 | TC SUPS | The Suspected Unapproved parts section (AARTM) |
29986 | TC PMI | All TC users where role-cd = "WP". The PMI organization is auto-maintained by finding any TC Userid’s listed as company PMI’s on the following views V_CAWIS_AMM_ORGANIZATIONS@NNPRODC.WORLD A Userid meeting the above criteria and that is not already on organization #29986 will get auto-added to that group. Conversely, anyone in this group, not found on TC Directory is de-activated (deleted from M79, and set to inactive on A01) |
50049450 | TC FSS | Government of Canada, Department of Transport - Flight Services (AAFBA) This is a special case account, treated as both an internal and external organization with each user having role codes = "WO" (AMO SDR External submitter) and "HU" (TC internal CAWIS user)) |
ALL CAWIS users are entered onto stored on the A01_USER table with a Party_id linking to Y50_party, Y55_individual.
ALL WSDRS users are tied together into Organizations on the M79_SDR_SUBMITTER table
...