2.12 Maintain Gateway Amendment Details

This topic explains systematic instructions to maintain gateway amendment details.

The user needs to identify the fields that can be amended by an external system, such as the Siebel CRM application. Every amendment request coming from a system has the following data:

• Service Name - This is a broad-level grouping of similar operations within a module in Oracle FLEXCUBE Universal Banking. The service names are published by Oracle FLEXCUBE Universal Banking. For example, FCUBSCustomerAccountService. This service is exposed by the FCUBS Interface Gateway to do a permissible operation on a customer account.
• Operation Name - This is the name of the operation that the external system wishes to perform within the service. These operations names are published by Oracle FLEXCUBE Universal Banking. For example, ModifyCustomer is for the modification of a customer.
• External Operation Name - This is the specific area of operation that an external system is performing on its side within the broad context of the Oracle FLEXCUBE Universal Banking’s amendment. In an external system, if the personal details of a customer are changed, this has a unique name by which it is identified within Oracle FLEXCUBE Universal Banking. Similarly, if the limits related details of a customer are modified, it also has a unique name.

Through the Gateway Amendment Maintenance screen, maintain a set of amendable fields, which can amend in Oracle FLEXCUBE Universal Banking whenever a request for the same is sent from an external system. Based on this maintenance, the amendment request is addressed by Oracle FLEXCUBE Universal Banking.

Note:

The fields which are marked in asterisk are mandatory.

1. On Homescreen, type GWDAMDMT in the text box, and click Next.
   The Gateway Amendment Maintenance screen displays.

   Figure 2-12 Gateway Amendment Maintenance

   
   

   
   Description of "Figure 2-12 Gateway Amendment Maintenance"

   
   
2. On the Gateway Amendment Maintenance screen, specify the fields.

   Note:

   The fields, which are marked with an asterisk, are mandatory.

   For more information on fields, refer to the field description table.

   Table 2-12 Gateway Amendment Maintenance - Field Description

   Field	Description
   External System	Specify the External System. Based on the maintenance here, only the fields that are selected as amendable can be modified if a request comes from the chosen external system. Note: The maintenance pertaining to external systems is factory shipped for the bank.
   Origin System	Specify the origin system for which the amendment details are applicable. For Example, if there is a record that is created by a specific external system CRM, and the requirement is that, for records created by this specific external system, only a set of fields are modifiable then, specify Origin System as CRM and Oracle FLEXCUBE Universal Banking as the External System. This Origin System field is used to identify such requirements wherein the amendable fields can be different if the Origination and Modification of the record are of different external sources. Specify the Origin System with the same value as the External System for Non FP services. For FP module services, provide the value as Oracle FLEXCUBE Universal Banking and the respective External system can be specified in the External System field. This feature is made available only for the FP modules with source operation as PMDTRONL_MODIFY.
   Source Operation	Specify the free format text (without spaces) which identifies the amendment. Note: The Source Operation is defaulted as (FUNCTIONID)_MODIFY. If the Source Operation is not sent from an external system, the function Id is derived from the Service and Operation combination.
   Service Name	Specify the Service Name, this is a broad-level grouping of similar operations within a module in Oracle FLEXCUBE Universal Banking. The service names are published by Oracle FLEXCUBE Universal Banking. Note: The maintenance pertaining to service names is factory shipped for the bank.
   Operation Code	Specify the Operation Code. This is the operation that the external system wishes to perform within the selected service. The operation names are published by Oracle FLEXCUBE Universal Banking. As an example, take Modify Customer, which is for the modification of a customer record. Each operation under different service names is identified by a unique code. Note: The maintenance pertaining to operation codes is factory shipped for the bank.
   Node Name	Click Search and specify the node name from the list of values. The list displays all valid nodes maintained in the system.
   New Allowed	Check this box if New Allowed is applicable.
   Delete Allowed	Check this box if Delete Allowed is applicable.
   All Records	Check this box if all records are applicable.
   Field Name	Specify the Field Name.

3. Click Exit to end the transaction.