Reapply Methodology

Use

You Reapply Methodology to update an existing role’s methodology because of a change to the methodology, role content, or conditions.

The following changes are relevant to the Reapply Methodology function:

  • The methodology has changed.

    For example, you add an approval phase or remove a phase.

  • A condition that affects the methodology has changed.

    For example, the condition for using a particular process, such as Process_01, is changed to Process_02.

  • The role content, such as a role attribute, has changed and it affects the methodology.

    For example, the subprocess attribute for a role was changed from Accounts_Payable_01 to Accounts_Receivables_01. The role must use a different methodology if you had set up different methodologies based on this attribute.

You can access the function as follows:

  • Role Maintenance

    On the role maintenance screens, choose the Reset Role Methodology button.

    The application applies the changes and resets the current phase to the definition phase (first phase).

  • Mass Role Methodology Update

    1. Select Role Methodology Update. This displays the Mass Role Methodology screen. There are two messages:
      • Roles which are locked for Approval will not be considered.

      • Default Methodology set in SPRO will be applied to all the roles.

        SPRO is the transaction for the Customizing activities in the Implementation Guide (IMG).
    2. Decide if you want to Set Role Methodology to Complete. If you do not select this checkbox, the Roles will be set to the Definition (initial) phase.
    3. Select the Roles to update by searching the attributes.
    4. Choose Submit.
    5. Go to the Background Jobs to verify the job and export or print as needed.

Conditions

The Reapply Methodology function has the following conditions:

  • Roles in the approval stage are not updated. The approval must be complete before the roles are updated.

  • Roles in the edit mode are not updated. The internal status of the role is locked.

  • If the role contains derived roles, and the new methodology does not contain the Derivation step, you must first remove the derived roles and update the roles separately.