Yesterday I tested SGAMSTU functionality to create efficiencies in changing fee assessment rate codes. Traditionally, fee assessment rate codes are updated one-by-one in SFAREGS. SGAMSTU allows for a mass update similar to our usage of SHAMDEG and SFAMREG.
Because these updates are needed for a large defined population, configuring GJRPSIM would eliminate the need to hand-type or paste in individual IDs. Once setup, we could use GJAJFLU to execute the GJRPSIM job to upload IDs via .csv.
Steph D and I posed the request to configure GJRPSIM a few weeks ago. Mary explained that rather than expend resources setting this up, we should use Appworx jobs already created. However, the Appworx job that was built to update fee assessment rate codes has not worked correctly as the date of this post.
GJRPSIM has implications beyond fee assessment rate code updates - we could update cohort and attributes in addition to supporting mass processing that occurs on SHAMDEG and SFAMREG in other areas of the office. Therefore, setting up this single utility would actually free up both IT capacity needed to create additional Appworx jobs for these other changes in addition to efficiencies in our shop. Steph D agreed to pose the request again.
After reviewing Banner security reports, I decided to add SGAMSTU to BAN_TUL_RG_RMGR_10, the class everyone in our office has, as SFAMREG maintenance access is included, so it makes sense to me to allow access for everyone in our office.
In the Results tab, the Effective Term is the latest registered term, so we want to do this before registration opens.
GTVFBPR is the business profile validation table.
GORFGBP relates business profiles to fine-grained access domains (audit table: BANSECR.GURABPR)
GORDMSK relates business profiles to masked fields (audit table: BANSECR.GURAMSK)
GORFBPI relates business profiles to PII domans (audit table: BANSECR.GURABPI)
GORFBPR relates business profiles to users (audit table: BANSECR.GURAGBP)
How do I assign a FGAC business profile (or individual) 'SELECT' only privileges?
Step 1: Make the predicate something that will never be true...e.g. where 1 = 2
Step 2: Check the update, insert, delete policy boxes on tab 2 of GOAFGAC
By doing this, the user can't insert update or delete because 1 will never = 2...!!!
Since the select policy box is unchecked on GOAFGAC it will allow them to see the data without allowing them to manipulate the data.