Show TOC

Function documentationPredefined Workflows

 

Business Object Repository Object

SAP predefines a Business Object Repository (BOR) object FCLM_CR for Bank Account Management. In this object, the following two events are defined:

  • CREATED: This method is used to trigger the workflow by creating a change request.

  • PROCESSED: Dialog step in approval process which was processed.

Rules
  • 74300006 FCLM_CASHMGR

    The rule assigns a cash manager user as the agent.

    In Bank Account Management, a cash manager is authorized to approve or reject a change request of creating, changing, or closing bank accounts.

  • 74300007 FCLM_CASHOPER

    The rule assigns a bank accountant user as the agent.

    In Bank Account Management, a bank accountant works under cash managers’ supervision and is responsible for opening, changing, and closing bank accounts.

  • 74300008 FCLM_CASHSYSCOLL

    The rule assigns a key user as the agent. In Bank Account Management, a key user is responsible for making necessary configurations for bank accounts and house bank accounts.

  • 74300013 FCLM_REVWOR

    This is a fixed rule, therefore you cannot define responsibility for this rule.

    The rule retrieves the contact persons defined in the bank account master data from the General Contact field (on the General Data tab, under the Internal Contact Persons section).

Workflow Templates

The following predefined workflow templates are available. For detailed information, refer to the template definition in the system.

  • Workflow template 74300043 FCLM_AMD (General workflow for working with bank account master data)

    The following sub-workflows are defined for the typical business scenarios of opening, changing, and closing bank accounts:

    • 74300047 FCLM_AMD_OP (Workflow for opening a new bank account)

      The following process is defined with this template:

      1. A bank accountant creates a bank account master record in the system.

        The system triggers a change request and sends the information to a cash manager for approval.

      2. After evaluating the request, the cash manager can either approve or reject the request.

      3. If the cash manager approves the request, the bank accountant opens the bank account in bank and maintain necessary information for the bank account master record in system, for example, bank account number, IBAN number, and so on.

        If the bank account is opened in a bank that does not exist in the system, the bank accountant should create the bank first in the system.

      4. A key user finishes the necessary configuration, for example, creating house bank accounts and assigning these accounts to the newly created bank account master record.

        If the corresponding general ledger accounts are not yet available, the key user should create the general ledger accounts first.

    • 74300048 FCLM_AMD_MD (Workflow for changing a bank account)

      The following process is defined with this template:

      1. A bank accountant modifies a bank account master record in the system.

        The system triggers a change request and sends the information to a cash manager for approval.

      2. After evaluating the change request, the cash managers can either approve or reject the request.

      3. If the cash manager approves the request, the bank accountant notifies the bank to make the necessary changes. After the bank accountant confirms that the changes have taken effect from the bank side, he or she confirms the step in the system.

        The changes are updated to the bank account master data.

      4. A key user updates the configuration if necessary.

        For example, if a new currency is added, the key user needs to create a house bank account for the new currency and then assigns the house bank account to the bank account master record.

    • 74300049 FCLM_AMD_MM (Workflow for change a signatory in multiple accounts)

      The process defined with this template is the same with the 74300048 FCLM_AMD_MD.

    • 74300050 FCLM_AMD_CL (Workflow for closing a bank account)

      The following process is defined with this template:

      1. A bank accountant closes a bank account in the bank account master data.

        The system triggers a change request and sends the information to a cash manager for approval.

      2. After evaluating the change request, the cash manager can either approve or reject the request.

      3. If the cash manager approves the request, the bank accountant notifies the bank to close the bank account. After the account is closed in the bank, the bank accountant confirms the step in the system.

      4. A key user finishes the necessary configuration.

        For example, the key user can mark the related house bank accounts as closed in their descriptions to distinguish them from other functional house bank accounts.

    • 74300065 FCLM_AMD_RV (Workflow for reviewing bank account master data)

      The following process is defined with this template:

      1. A cash manager selects the bank accounts to be included into a review process.

        The system detects the responsible contact person of each selected bank account and sends out a request to each contact person respectively. Each contact person receives a request that contains all the bank accounts that he or she is responsible for and selected for review.

        The contact persons who are responsible for bank account review are defined in the General Contact field in the bank account master data (on the General Data tab, under the Internal Contact Persons section).

      2. After reviewing the bank account master data of their responsible bank accounts, account contact persons can either mark the bank account as reviewed or directly update the master data if they spot any incorrect information.

        Modifying the bank account master data may trigger another workflow, depending on the fields that are changed.

      3. The contact person completes the request after all the bank account in the request are marked as reviewed.

Standard Task

SAP predefines the standard task below. The task is used in workflow steps to approve or reject a change request.