Tuesday, February 21, 2017

RMA : Creating an Authorisation

Purpose

The procedure explains how to create an authorisation by creating an Authorisation to Receive, and to create authorisations using an existing authorisation. An Authorisation to Receive is the authorisation that you (Own BIC) send to a correspondent (Correspondent BIC) to enable that correspondent to send messages to you.
If you create an authorisation using an existing one, then the Relationship Management application uses the values of the existing authorisation as default values for the new authorisation. You can keep those values or modify them if necessary.
RMA Plus enables you to define a granular authorisation which specifies the types of messages within a service that a correspondent can send you. This capability is defined by the service and the available granularity levels for a service are defined in the application service profile. A non-granular authorisation covers all types of messages.
For more information about what happens to the authorisation after you have created it,
For more information about creating an authorisation for Test and Training,

Using an existing authorisation

When you base a new authorisation on an existing one, the New Authorisation to Receive Details window shows the same details as in the existing one. You can use those details, or modify them if necessary.
The comments from the existing authorisation are not included, so you can enter new comments for the new authorisation.

Users and permissions

You can create authorisations when the Create Auth function is assigned to you in the Relationship Mgmt application.
The following permissions restrict the business relationships that you can access:
  • Allowed/Prohibited Destination(s)
  • Allowed/Prohibited Service(s)

Before you begin

When you are creating a granular authorisation for RMA Plus, ensure that Own BICs are approved as candidates for granular authorisations.

To create an Authorisation to Receive:

  1. To create an authorisation without basing it on an existing one, select New or New (granular) from the Authorisation menu.
    To create an authorisation based on an existing authorisation, open an authorisation and view its details in the Authorisations window. Then, select New As or New As (granular) from the Authorisation menu.
    If the existing authorisation has a preparation status, then the new authorisation is based on the authorisation in preparation rather than the active authorisation. Also, if you view an Authorisation to Send or an Authorisation to Receive, then the new authorisation is based on the authorisation that is being viewed.
    The New Authorisation to Receive window appears.
    The Available list displays the BICs for which you have permission to create an authorisation.
    For granular authorisations, the list shows only the BICs that are approved as candidates for granular authorisations, and for which you have permission to create an authorisation.
  2. Select the service to which the authorisation will apply.
    The list of services contains the live services (including the associated Test and Training !p service) that require authorisations and which are specified in the application service profile. You can select another service by selecting the Other option from the Services list and then, selecting the service name and optionally, entering an environment identifier.
    Authorisations that are based on an existing one show the same service as the existing authorisation.
  3. Select the licensed BIC8s for which you want to create authorisations.
    Tip
    Selecting several BICs in this field generates an Authorisation to Receive for each BIC8. Each authorisation has the same validity period and comments, if any are specified.
  4. Type the BIC8 of the Correspondent BIC.
    This gives permission to the Correspondent BIC to send messages to the Own BICs in the Selected list.
    If the BIC and Bank file is already installed, then the first 35 characters of the Correspondent's BIC expansion appear automatically beside the Correspondent BIC.
  5. Click Continue.
  6. If an authorisation exists for the business relationship, then the New Authorisation to Receive window appears.
    In this case, select an action by clicking one of the following buttons:
    • Modify - Apply the authorisation details to all the selected Own BICs.
      (This action modifies the authorisation details of those BICs.)
    • Skip - Leave the existing authorisations for the selected BICs unchanged, and create new authorisations for the remaining BICs.
    • Cancel - Display the New Authorisation to Receive window, where you can change the list of Selected Own BICs, or cancel the task.
    If no authorisation exists for the service, Correspondent BIC, and Own BICs that you selected, then the New Authorisation to Receive Details window appears.
    Note
    When you base a new authorisation on an existing one, the New Authorisation to Receive Details window shows the same details as in the existing one. You can use those details, or modify them if necessary.
    The comments from the existing authorisation are not included, so you can enter new comments for the new authorisation.
  7. To specify a validity period for the authorisation after it becomes active, select the option box Timebound Authorisation In the New Authorisation to Receive Details window. Then, specify the date range in the Valid from and Valid until fields.
    Valid dates are between 01 January 2006 and 31 December 2037, inclusive.
    The dates are stored in Greenwich Mean Time (GMT), with their times set to 00:00:01 and 23:59:59. The format of the date is defined by the Date configuration parameter in the System Management application.
  8. For a granular authorisation, specify the types of messages that may be transmitted between both parties. The available granularity levels for a service are defined in the application service profile.
  9. Enter comments about the authorisation (optional).
  10. From the Authorisation menu, select Add.
    The Add Authorisation to Receive dialog box appears.
    Assign one of the following statuses to the authorisation:
    • Draft - Save the authorisation for future editing.
      The Relationship Management application saves the authorisation with the preparation status "Draft". If the authorisation exists and is active, then it stays active and gains the preparation status "Draft" in addition to its external status.
    • Enabled - Activate the new version of the authorisation to make it the Current version.
      This option is available if your user profile has Bypass Approval set to "Yes" for the Create Auth function.
      The Relationship Management application saves the authorisation with external status, "Enabled", and activates it so that it becomes the Current authorisation. The date on which the authorisation becomes active is the Issued Date, and it is stored and displayed in GMT.
    • Pending Approval - Request approval for the new version of the authorisation.
      The Relationship Management application saves the authorisation with the preparation status, "Pending Approval", which requires another user to approve it. If the authorisation exists and is active, then it stays active and gains the preparation status "Pending Approval" in addition to its external status.
  11. Click OK.

No comments:

Post a Comment