Area Menu and Activity Group Transport Procedures

The business analyst assigns a request to a developer to change an existing Area Menu or create a new menu. Often, the business analyst and developer are the same person for an Activity Group.

The developer uses the Profile Generator (PFCG) in Development (SF2) to create or change the Activity Group. To create a new Activity Group, follow these naming conventions:

Example: Z_HRBEN_CAMPUS_ADMINISTRATOR

1) Z 2) underscore 3) two- through five-character business area abbreviation, such as HRBEN for Human Resources Benefits or OSP for Office of Sponsored Programs 4) underscore 5) the rest of the name. The rest of the name should describe the main function of the role, such as CAMPUS_ADMINISTRATOR.

Note: 30 is the maximum number of characters allowed.

This naming convention is intended to offer a reasonable indication of the role's purpose and scope of included activities. The Description field of the Activity Group / Area Menu / role offers a little more room for clarification of the role's function. The extended description (on the Description tab of PFCG) provides a place to enter a detailed description of the data accessed by the Activity Group, the transactions used, the persons who would have access to the role, etc., and to log changes made to the Activity Group. (There are no Change Documents for Activity Groups.)

The developer modifies or creates the Activity Group / menu and sends email to R3 Accts (r3-accts@mit.edu) stating the Activity Group's name, the business analyst, and a request that it be generated in Development (SF2) and assigned to the developer and the business analyst.

R3 Accts generates the authorizations and assigns the Activity Group to user IDs in Development.

The developer sends email to the business analyst, stating the Activity Group and the applied change. With this information, the business analyst reviews the Activity Group and determines if the maintenance proceeds to Test.

The business analyst tests the Activity Group in Development. When the test is completed successfully, the business analyst emails r3-accts@mit.edu to create a transport request for this Activity Group.

• If this is a new Activity Group, the business analyst includes a list of the user IDs that the Activity Group should be assigned to in each environment and forwards the request to R3 Accts.
• R3 Accts uses ZUTTREQ and creates a transport request that's sent to R3-Chmgt, with a cc: to the business analyst and business process owner. After the transport is imported, R3 Accts assigns the Activity Group to user IDs in Test.
• The Activity Group is tested again to ensure that no one assigned, or can do more or less than they are supposed to. When the Activity Group is validated, the business analyst uses their copy of ZUTTREQ to follow the normal transport procedures.