Professional Documents
Culture Documents
AMBIT
TABLE OF CONTENTS
1 INTRODUCTION..................................................................................................................3
1.1 PURPOSE.................................................................................................................................................. 3
1.2 SCOPE...................................................................................................................................................... 3
1.3 ABBREVIATIONS......................................................................................................................................... 3
1.4 REFERENCES............................................................................................................................................ 3
2 FUNCTIONAL SPECIFICATION...........................................................................................4
2.1 FUNCTIONAL SUMMARY.............................................................................................................................. 4
2.2 FSAPISGNUPD – SIGN ATTACH - UPDATE...............................................................................................5
2.2.1 Purpose.............................................................................................................................................. 5
2.2.2 Menu Modification............................................................................................................................... 5
2.2.3 Screen Layout and Data Sheet...........................................................................................................5
2.2.4 Processing.......................................................................................................................................... 6
2.2.5 Report Layout and Data Sheet.........................................................................................................11
Steven Wee
(Product Manager)
ACCEPTED: DATE:
AUTHORIZED: DATE:
TKMS
(Head, EOC)
BUILD STATUS
Current
Section Release Date of Release Prepared by Comments
All 1.0 16 October 2009 Marek Michalovic Initial version
1 INTRODUCTION
1.1 Purpose
This document provides an identification and summarises the main functionalities of the software product.
1.2 Scope
This API is responsible for sending the request to delete the signature attachment of the client at the backend
system.
1.3 Abbreviations
CBS Core Banking System
1.4 References
SignAttachDelete.xls
sym_rb_sign_attach_in.xsd 1.1
sym_rb_sign_attach_out.xsd 1.0
2 FUNCTIONAL SPECIFICATION
ID Title/Summary References
FSAPISGNDE Sign Attach - Delete SignAttachDelete.xls
L
ID Estimation
FS Design Dev Testing Docum. Total
Total
Note: Estimation for testing covers only estimation for Unit and Module Test. It does not cover estimation for FAT
and UAT activities, which will be added during the final price negation for particular release.
474499237.doc Release ()
FUNCTIONAL SPECIFICATIONS 5
2.1.1 Purpose
This API is responsible for sending the request to delete the signature attachment of the client at the backend
system. Deletes the signature attachment of the client for the given account number, customer ID and signatory
number. If there is any error during processing, the error(s) should be returned, otherwise the status should be
SUCCESS.
Every API procedure described in this FS will contain main messages (for details about this header common part
see document “SYMADM API and Event Concept.pdf”):
The API procedure described in this FS will contain main messages:
Request
Request message is sent to Ambit CBS.
Every request message consists of 2 parts:
- Message header - contains basic information about the message type, AMBIT user, correlation ID. It is
mandatory part of the message.
- Message Data - contains user-entered data for particular object.
Response
Pertains to the system's response in relation to the request. Error messages will be returned if request is
unsuccessful.
Every response message consists of 2 parts.
- Message Header - contains information whether the upload is successful or with errors. It is mandatory
part of the message.
- Message Data – contains output data if the API has to return some data.
2.1.1.1 Background
Not applicable
474499237.doc Release ()
FUNCTIONAL SPECIFICATIONS 6
2.1.4 Processing
Request
The following parameters comprise the Request message:
Item Description Data Type / Mapping in Ambit Defaults Remarks
Format (table.column)
Validations
Dependencies
ACCT_NO Unique Alphanumeric codes VARCHAR2(20) Rb_acct_info.Acct_no Defaults:
identifying the account to be
opened in Retail Banking for a N/A
particular customer Validations:
Mandatory
CERTIFICATE_NO Certificate Number attached on the VARCHAR2(8) Rb_acct_info.Certificate Defaults:
Term Account. The certificate _no
number will change every time the N/A
account is rolled-over. Validations:
Optional
DELETE_DETAILS (Multiple Collection)
POSITION Position of record in the collection NUMBER, 0
VERSION Version NUMBER Version$
CLIENT_NO Unique Id of the customer VARCHAR2(12) Rb_acct_info.Client_no Defaults:
N/A
Validations:
Mandatory
SIGNATORY_NO No. that has been given to this NUMBER(2) Rb_acct_info.Signatory Defaults:
signature out of the total number of _no
signatories within the account N/A
Validations:
474499237.doc Release ()
FUNCTIONAL SPECIFICATIONS 7
Mandatory
Once the request message is delivered to Ambit CBS, the system will validate all the input data.
474499237.doc Release ()
FUNCTIONAL SPECIFICATIONS 8
Response
The following parameters comprise the Response message:
Item Description Data Type / Mapping in Ambit Defaults Remarks
Format (table.column)
Validations
Dependencies
POSITION Order number in query (start from 1 NUMBER, O
and increase)
VERSION The Actual version of the record, NUMBER Rb_acct_info..version$
used to ensure data integrity.
474499237.doc Release ()
FUNCTIONAL SPECIFICATIONS 9
474499237.doc Release ()
FUNCTIONAL SPECIFICATIONS 10
474499237.doc Release ()