Table of Contents

1. Glossary................................................................................................................................................9

2. Solution Overview..............................................................................................................................10
2.1 Summary..................................................................................................................................10
Design Approach.................................................................................................................................10
2.2 Business Process Task Flow....................................................................................................11
2.3 Features in Scope.....................................................................................................................11
2.3.1 <Feature ID> : Funds Sufficiency Check Request from Channels.........................................................11
2.3.2 <Feature ID> : Addition of New Flag to Amount Block Input Screen (CADAMBLK)........................12
2.3.3 <Feature ID> : Processing Amount Block Requests from Channels Using Web Service......................13
2.3.4 <Feature ID> : Processing Debit Transaction.........................................................................................15
2.3.5 <Feature ID> : Processing File Upload from Channels..........................................................................17
2.3.6 <Feature ID> : Currency Rounding Off & Settlement File Balancing...................................................20
2.4 Features Out of Scope..............................................................................................................21
None 21
2.5 Solution Flow Diagram............................................................................................................21
2.6 Solution Components List........................................................................................................22
2.7 Assumptions and Constraints...................................................................................................22
2.7.1 Assumptions............................................................................................................................................22
2.7.2 Constraints...............................................................................................................................................22
2.7.3 Recommended Set Up.............................................................................................................................22

3. Artifacts to Plan and Validate User Design for <Feature ID> : Processing of Amount Block
Transactions, Debit Transactions & File Upload........................................................................................23
3.1 Detailed Solution Flow............................................................................................................23
3.2 Product Use Cases....................................................................................................................23
3.2.1 Activity – Task Name:.............................................................................................................................24
3.3 Navigation................................................................................................................................25
3.4 UI Wireframe...........................................................................................................................25
3.5 UI Prototype.............................................................................................................................25
3.5.1 Addition of New Flag in Amount Block Input Screen - CADAMBLK..................................................26
3.5.2 Addition of New Field in Journal Entry Input Screen - DEDJNLON....................................................27
3.6 Page Information......................................................................................................................28
3.7 UI Elements.............................................................................................................................28
3.7.1 Amount Block Input Screen - CADAMBLK..........................................................................................28
3.7.2 Addition of New Field in Journal Entry Input – DEDJNLON................................................................28
3.8 UI Business Rules....................................................................................................................29
3.9 UI Error Messages...................................................................................................................29
3.10 Embedded Help........................................................................................................................29
 3.11 Impact on Audit Trail...............................................................................................................29
3.12 Impact on Authorization..........................................................................................................29

4. Security Considerations.....................................................................................................................30
4.1 Privileges..................................................................................................................................30
4.1.1 Duties.......................................................................................................................................................30
4.2 Function Security Mapping......................................................................................................30
4.3 Data Security Mapping............................................................................................................30
4.3.1 Permissions..............................................................................................................................................30
4.3.2 Constraints...............................................................................................................................................30
4.4 Other Security Considerations.................................................................................................30

5. SOA Components...............................................................................................................................31
5.1 Reference to SOA Components deliverable............................................................................31

6. Task Flow Annotations for BPEL....................................................................................................32

7. Service Solution Component.............................................................................................................33

7.1.1 Service Information.................................................................................................................................33
7.1.2 Related Business Object Operations.......................................................................................................33
7.1.3 Support for Copying Data across Instances.............................................................................................33
7.2 FCUBSCustomerService.....................................................................................................33
7.2.1 Service Information.................................................................................................................................33
7.2.2 Related Business Object Operations.......................................................................................................34
7.3 FCUBSDEService.................................................................................................................34
7.3.1 Service Information.................................................................................................................................34
7.3.2 Related Business Object Operations.......................................................................................................34

8. BI Reports Solution Component......................................................................................................35

8.1 <BI Report Name>...................................................................................................................35
8.1.1 Page Information.....................................................................................................................................35
8.1.2 Screenshot................................................................................................................................................35
8.1.3 Report Attributes.....................................................................................................................................35
8.1.4 Parameters...............................................................................................................................................35
8.1.5 Field Specifications and Validations.......................................................................................................35
8.1.6 Business Rules.........................................................................................................................................35
8.1.7 Error Messages........................................................................................................................................35
8.1.8 Table Column Definitions.......................................................................................................................36
8.1.9 Report Format..........................................................................................................................................36
8.1.10 Graphs......................................................................................................................................................36
8.1.11 Drills from Table.....................................................................................................................................36
8.1.12 Reconciliation with Application Data.....................................................................................................36

9. Reporting Solution Component........................................................................................................37

9.1 <Report Name>........................................................................................................................37
9.1.1 Report Information..................................................................................................................................37
9.1.2 Data Extraction Definition......................................................................................................................37
 9.1.3 Parameters...............................................................................................................................................37
9.1.4 Business Rules.........................................................................................................................................37
9.1.5 Error Messages........................................................................................................................................37
9.1.6 Layout Templates....................................................................................................................................37
9.1.7 Table Column Definitions.......................................................................................................................38
9.1.8 Drills from Table.....................................................................................................................................38

10. External Interface..............................................................................................................................39

10.1 < External Interface Name>.....................................................................................................39
10.1.1 Interface Format Detail............................................................................................................................39
10.1.2 Header and Body Details.........................................................................................................................39
10.1.3 Error Handling.........................................................................................................................................39

11. Background Processing Solution Component.................................................................................40

11.1 <Background Process Name>..................................................................................................40
11.1.1 Background Process Information............................................................................................................40
11.1.2 Parameters...............................................................................................................................................40
11.1.3 Business Rules.........................................................................................................................................40
11.1.4 Error Messages........................................................................................................................................40
11.1.5 Output......................................................................................................................................................40
11.1.6 Log File...................................................................................................................................................40

12. Seed Data............................................................................................................................................41

12.1 <Requirement Name>..............................................................................................................41
12.1.1 Lookups...................................................................................................................................................41
12.1.2 Value Sets................................................................................................................................................41
12.1.3 FlexFields................................................................................................................................................41
12.1.4 Other Seed Data.......................................................................................................................................41

13. Impact on other modules or Operations with the Product............................................................42

13.1 <Impact Name>.......................................................................................................................42
13.1.1 Screenshot of <impacted screen>............................................................................................................42
13.1.2 Changes to <impacted screen>................................................................................................................42

14. Migration Impact...............................................................................................................................43

15. Dependencies and Impacts................................................................................................................44

15.1 Dependencies...........................................................................................................................44
15.2 Impacts.....................................................................................................................................44

16. Uptake Considerations......................................................................................................................45

17. Open and Closed Issues.....................................................................................................................46

17.1 Open Issues..............................................................................................................................46
17.1.1 Issue [Name, Number].............................................................................................................................46
17.2 Closed Issues............................................................................................................................46
17.2.1 Issue [Name, Number].............................................................................................................................46
18. Appendix: <Multi Multi Journal Entry & Amount Block Modification Amount Block Release
Files> 47
Table of Figures
Figure 1: Business Process Task Flow Diagram....................................................................................................................9
Figure 2: Solution Flow Diagram.........................................................................................................................................10
1. Glossary

Term Definition
BRD Business Requirement Document
FDD Functional Design Document
FCUBS Oracle FLEXCUBE Universal Banking
UBS Universal Banking Solution
FCPB Oracle FLEXCUBE Private Banking
FCIS Oracle FLEXCUBE Investor Services
2. Solution Overview
2.1 Summary
 Facility required for handling the following requests from channels using the web service.
1. Funds Sufficiency check in the CASA account.
2. Imposing amount block in the account for the requested amount.
3. Providing the amount block confirmation to the channel from where the request was initiated along with the
amount block reference number.
4. Processing amount block modification requests from channels & providing confirmation.
5. Processing amount block release request from channels & providing the confirmation after releasing amount
block.
6. Processing of account debit transaction based on the request received from channels & providing the confirmation
to the channel with transaction reference number.
 The below mentioned transactions need to be handled through file upload facility in UBS. The file will be received from
other channels, UBS need to process the request & send back the confirmation to the respective channel.
1. Amount block creation for CASA accounts.
2. Amount block modification for CASA accounts.
3. Release of the existing amount block in the CASA accounts.
4. Posting debit/credit transactions in the CASA account.

Design Approach
1. A new flag “Verify Available Balance” will be added in the amount block screen (CADAMBLK). When this flag
is selected amount block will be done only when the funds are available in the account. The same flag will be
added in the amount block gateway service as well.
2. A new field “Source Code” will be added in amount block screen (CADAMBLK) to capture the source from
which the amount block has been initiated. This will be added in amount block gateway service as well.
3. The existing operation QueryCustAcc in the service FCUBSAccService can be used to perform the funds
sufficiency check in a CASA account before imposing an amount block into the account.
4. The different operations under existing web service FCUBSCustomerService can be used to handle the following
amount block related requests that are coming from channels.
a. Creation of amount block.
b. Providing confirmation with amount block reference number.
c. Modification of the existing amount block & providing confirmation to channel.
d. Releasing the existing amount block & providing the confirmation to channel.
5. The existing web service FCUBSDEservice will be used for debit/credit settlement transactions in CASA/GL
accounts.
6. The existing GI facilities will be used to handle the debit/credit transactions upload file from channels. A new field
will be added to provide the “Amount Block Number” in the file upload.
7. A facility will be added in the GI to process the file based amount block creation, amount block modification &
release requests from channels.
 8. 24*7 support required for amount block creation, amount block modification, amount block release & debit/credit
settlement transactions.
RS Reference

2.2 Business Process Task Flow

None

2.3 Features in Scope

The following changes required to be done in various UBS services to handle the requests such as creation of amount block,
releasing of amount block, modification of amount block. Also using Generic Interface (GI) needs to provide new interface
format for processing debit transactions, creation of amount block, modification of amount block & release of amount block
through file upload.

2.3.1 <Feature ID> : Funds Sufficiency Check Request from Channels

Priority Must Have
Related Business FCUBS_Core_13_0011
Requirements
Enhancement Not Applicable
Request Number
Performance Considerations
High Volume
Throughput
High Concurrency Not Applicable
Transaction Flow

2.3.1.1 Business Benefits

This facility will allow the channel to check the funds availability in the CASA account before sending
an amount block request to UBS.

2.3.1.2 Description
The existing web service FCUBSAccService will be used to perform the funds sufficiency check from
channels.

Activity Existing Proposed Functionality

Funds Sufficiency Check Currently supported 1. The existing web service FCUBSAccService
from channels using web using the operation QueryCustAcc can be utilized by the external
service. QueryCustAcc in channels to perform the funds sufficiency check
FCUBSAccService. in a CASA account.
2.3.2 <Feature ID> : Addition of New Flag to Amount Block Input Screen (CADAMBLK)
Priority Must Have
Related Business FCUBS_Core_13_0011
Requirements
Enhancement Not Applicable
Request Number
Performance Considerations
High Volume
Throughput
High Concurrency Not Applicable
Transaction Flow

2.3.2.1 Business Benefits

Using this flag it will be possible for the user to define that the amount block should be executed only
when sufficient funds are available in the account.

2.3.2.2 Description
The new flag will be added in the Amount Block Input screen (CADAMBLK).

Activity Existing Proposed Functionality

Addition of new flag & Not Supported.  A new flag “Verify Available Balance” will be
new field in Amount added in the amount block input screen. This
Block Input Screen flag will be non-amendable post amount block
(CADAMBLK). creation.
 The proposed functionality of the new flag is
explained below.
 When this flag is selected, system will do the
amount block only when sufficient funds are
available.
 When this flag is not selected the existing
functionality of providing override before
processing the amount block when there is
insufficient funds in the account will continue.
 When this flag is selected & during amount
block creation if sufficient funds are not
available for blocking then an error “Sufficient
Funds are not Available for Blocking” will be
displayed to the user.
 The new field “Source Code” will be introduced
in the Amount Block Input Screen. The source
from which the amount block has been initiated
will be captured in this field.
  This source code will be a display field.
 Field addition of “Verify Available Balance”
will be done in the service
FCUBSCustomerServiceOperations
CreateAmtBlk, ModifyAmtBlk, and
QueryAmtBlk.
 The field “Source Code” will be available only
in the response XML.
 The field addition will be done in excel file
upload also.
 The field addition changes will be done in GI
files AMTBLKIN & CAOAMBLK also.

2.3.3 <Feature ID> : Processing Amount Block Requests from Channels Using Web Service
Priority Must Have
Related Business FCUBS_Core_13_0011
Requirements
Enhancement Not Applicable
Request Number
Performance Considerations
High Volume
Throughput
High Concurrency Not Applicable
Transaction Flow

2.3.3.1 Business Benefits

The channel will be able to do the transactions such as imposing amount block, modification of the
amount block & releasing of amount block.

2.3.3.2 Description
Using the existing web service FCUBSCustomerService the below mentioned actions related to amount
block can be performed from a channel.

Activity Existing Proposed Functionality

Creation of Amount Supported using the web The same service can be utilized by external
Block from external service channels.
channels using web FCUBSCustomerService  Channel needs to provide the following data to
service. Operation create the amount block into a CASA account.
CreateAmtBlk. a. Account Branch
b. Account Number
c. Amount
 The new field “Source Code” will be introduced
in the service to capture the source code of the
 channel from which the amount block is
initiated.
 The following values needs to be passed by the
external channel to create the amount block in
FCUBS.
a. Amount Block Type – Flexcube
b. Hold Code
 Once the amount block is created successfully
the amount block reference number will be
provided in response.
 Amount block created by the external channel
can be allowed to be released or the release can
be restricted from the branch. The identification
of whether the amount block has been created
by channel or branch will be done using the
“Source Code” field.
 Ex: When the branch user is trying to release the
amount block that has been created by the
channel then an error (configurable to override)
will be displayed to the user that “Amount
Block Cannot be Released in Branch”.
Modification of Amount Supported using the web The same service can be utilized by external
Block from external service channels.
channels using web FCUBSCustomerService  Modification will be done by using the existing
service. Operation Amount Block Number.
ModifyAmtBlk  Once the amount block modification is
successful the confirmation will be provided in
response.
 If the modification (increasing/decreasing the
amount of block) request has been failed for any
of the reasons then the original amount of the
block will be retained.
Release of Amount Supported using the web The same service can be utilized by external
Block from external service channels.
channels using web FCUBSCustomerService  Release of amount block will be done using the
service. Operation existing Amount Block Number.
CloseAmtBlock.  Once the release of the amount block is
successful the confirmation will be provided in
response.
2.3.4 <Feature ID> : Processing Debit Transaction
Priority Must Have
Related Business FCUBS_Core_13_0011
Requirements
Enhancement Not Applicable
Request Number
Performance Considerations
High Volume
Throughput
High Concurrency Not Applicable
Transaction Flow

2.3.4.1 Business Benefits

The channel will be able to debit the CASA account directly based on the availability of funds & the
required GL account can be credited.

2.3.4.2 Description
Using the existing web service FCUBSDEService the below mentioned debit transaction can be
completed from the channels.

Activity Existing Proposed Functionality

Debit/Credit Settlement Supported using the web  The web service
transaction from service FCUBSDEServiceOperations
channels. FCUBSDEService CreateMjrnlbook can be utilized by external
Operation channels to initiate a debit/credit settlement
CreateMjrnlbook transaction.
 Currently the online service doesn’t have auto
authorization facility. Hence auto authorization
facility will be provided for the underlying
function id & the same can be used in the web
service.
 Set of reserve batch numbers will be provided
for each external channel for online debit
transactions.
 At EOD, reserve batch numbers assigned for the
particular channels in open status need to be
manually closed by branch user.
Release of Amount Not Supported.  A new field “Amount Block Number” will be
block & debit initiation added in the following screen. This will be a
in a single request. display field in the screen.
a. DEDJNLON
 The “Amount Block Number” will be always a
display field in DEDJNLON screen. The value
to this field can be provided only through file
 upload facility.
 The following validations need to be built for
the field “Amount Block Number” in file
upload.
a. The amount block reference numbers
can be provided only for debit
transactions.
b. If the amount block reference number
has been provided for a “Credit”
transaction that particular amount
block will not be released. However the
credit transaction will be processed.
 When this field “Amount Block Number” is
“Null” then there is no action required to be
taken by the system while processing the
uploaded file.
 If the amount block reference number is
provided in this field for a CASA/GL debit
transaction during file upload then on
processing the transaction the following actions
will happen.
a. If the “Amount Block Number” is valid the
amount block will be released.
b. Transaction entries will be posted in the
respective accounts.
c. The validations that are applicable for the
amount block release will be applied during
releasing of the amount block through file
upload also.
d. If the “Amount Block Number” provided is
invalid then the all transaction legs under
that particular curr no. will be rolled back.
e. If the “Amount Block Number” provided is
not pertaining to the corresponding debit
account number then also the particular
“Amount Block Number” will be released
& processing the corresponding debit
transaction will continue.
f. If “Amount Block Number” has been
provided for a debit transaction but the
 release of amount block is failed due to any
reason, in that scenario all the transactions
under that curr no. will be rolled back.
 In case if the DE entry got saved during file
upload & subsequently it has been deleted then
following actions will be performed.
a. The transaction entries will be
reversed.
b. The amount block which was released
earlier will not get re-opened
automatically as part of “Delete”
action.
c. While deleting the DE entry system
will display a message to the user that
“The Deleted Journal Entries has
Released Amount Block Numbers
Which Needs to be Re-opened
Manually”.
d. User needs to re-open that particular
amount block numbers manually.
e.

2.3.5 <Feature ID> : Processing File Upload from Channels

Priority Must Have
Related Business FCUBS_Core_13_0011
Requirements
Enhancement Not Applicable
Request Number
Performance Considerations
High Volume
Throughput
High Concurrency Not Applicable
Transaction Flow

2.3.5.1 Business Benefits

The channel will be able to do debit/credit transactions , amount block request, amount block
modification & release of amount blocks using file upload facility.

2.3.5.2 Description
Using the file upload facility the below mentioned transactions are required to be performed from the
channels.
 Activity Existing Proposed Functionality
Debit/Credit transactions Not Supported  The GI facility will be utilized by external
using file upload channels to upload the Debit/Credit transaction
facility. file.
 New interface codes DEIJNLON (for incoming)
& DEOJNLON (outgoing) will be created for
the debit/credit transaction upload file. The
outgoing file would be linked to incoming file
and generated in the context of the incoming file
data set.
 The data will be provided by the external
channels in the standard file format.
 The incoming file from the channels will be
processed & the status of file upload
(success/failure) will be provided to the
channels using the outgoing file format.
 The file formats has been embedded in section
18 – appendix.
Handling failure Not supported  When a transaction leg in a “Current Number”
transactions. has been failed then the entire transaction
entries pertain to that “Current Number” will be
rolled back including amount block.
 Manual correction needs to be done further for
failed transactions.
 The list of failure transactions & reason for
failure will be provided to the external channels
for reconciliation.
Amount block creation Supported. (However  Amount block creation from external channels
using file upload further addition of fields can be done using the GI facility.
facility. (refer section 2.3.2.2) &  The existing interface codes AMTBLKIN
linking outgoing format (incoming) & CAOAMBLK (outgoing) will be
to incoming needs to be used for the same. The outgoing file would be
done). linked to incoming file and generated in the
context of the incoming file data set.
 The status of upload (success/failure) will be
provided to channels after processing the file.
Modification of amount Not Supported  New interface codes AMIBLKMD (incoming)
block using file upload & AMOBLKMD (outgoing) will be created for
facility. modifying the amount block record. The
outgoing file would be linked to incoming file
 and generated in the context of the incoming file
data set. The fields are embedded in section 18 –
appendix.
 Amount block reference number which needs to
be modified will be provided by the channels.
 The following fields can be modified in the
existing amount block record.
a. Amount.
b. Hold Code.
c. Expiry Date.
d. Remarks.
 The validations that are applicable for the
amount block modification will be applied
during modification of the amount block
through upload facility also.
 The status of upload (success/failure) will be
provided to channels after processing the file.
 If the modification (increasing/decreasing the
amount of block) request has been failed for any
of the reasons then the original amount of the
block will be retained.
Release of amount block Not supported  The GI facility will be utilized by external
using file upload channels to upload the amount block release
facility, file.
 New Interface codes AMIBLKCL (incoming) &
AMOBLKCL will be created to support the
amount block release file upload from external
channels. The outgoing file would be linked to
incoming file and generated in the context of the
incoming file data set. The files are embedded
in section 18 – appendix.
 Channel needs to provide the “Amount Block
Number” which is to be released..
 The validations that are applicable for the
amount block release will be applied during
releasing of the amount block through upload
facility also.
 The status of upload (success/failure) will be
provided to channels after processing the file.
2.3.6 <Feature ID> : Currency Rounding Off & Settlement File Balancing
Priority Must Have
Related Business FCUBS_Core_13_0011
Requirements
Enhancement Not Applicable
Request Number
Performance Considerations
High Volume
Throughput
High Concurrency Not Applicable
Transaction Flow

2.3.6.1 Business Benefits

From the external channels it will be possible to post settlement transactions.

2.3.6.2 Description
When the settlement file is received from external channels the same needs to be processed as described
below.

Activity Existing Proposed Functionality

Currency wise rounding NA.  The external channels need to synchronize the
off in UBS & external currency rounding off parameters with UBS
channels for Dr/Cr before sending the amounts. This will be
settlement files. achieved by logics within the external channels.
 The currency rounding unit functionality if not
matching in external channel then configuration
in UBS need to be synchronized to allow
rounding unit to that of channel.

Balancing of Settlement Supported.  External channels will send the settlement file in
file in UBS that has transaction currency.
been received from  Incase external channel does not send the local
external channels. currency equivalent amount, UBS will convert
the transaction amounts into local currency by
applying the applicable conversion rates.
 The maximum permissible tolerance limit for
balancing a curr no. can be set up in the system
internal parameter cstb_param. A new
parameter
DE_MULTI_MULTI_AMT_VARIANCE will
be introduced to achieve this functionality.
 After converting the transaction amounts into
local currency equivalent, if there is any
difference between credit & debit transaction
 totals it will be handled in the following way.
a. If the file is balanced without any
difference then the Dr/Cr transactions
will be posted into the respective
accounts.
b. If there is any difference found due to
which the curr no. is not balanced then
system will check whether the
difference is within the maximum
permissible tolerance limit. 1. If the
difference is within the maximum
permissible tolerance limit then the
transactions will be posted into
respective Dr/Cr accounts by adjusting
the local currency equivalent amount
into the last transaction leg. 2. If the
difference is beyond the maximum
permissible tolerance limit then the
entire set of transactions under the
“Current Number” will be failed.
c. If the transaction is failed, further
reconciliation needs to be done
manually.

2.3.7 Process for File Upload from Different Channels.

Priority Must Have
Related Business FCUBS_Core_13_0011
Requirements
Enhancement Not Applicable
Request Number
Performance Considerations
High Volume
Throughput
High Concurrency Not Applicable
Transaction Flow

2.3.7.1 Business Benefits

This facility will allow the channel to upload different files into FCUBS.

2.3.7.2 Description

Activity Existing Proposed Functionality

Approach for file transfer Partially Supported. 1. External channels should have the relevant
to UBS from external access on to the DB server and place the file
channels. in the available standard folder structure.
2. Folder structure of GI will have <Any
Folder> created.
3. The following sub folders will be available
under the main folder.
a. Ready
b. WIP
c. File_Processed
d. Error
e. Processed
4. An entry to be created as IN_WIP in
All_Directories table and pointing to the
location <Any Folder>/wip.
5. Channels need to place the file in<Any
Folder>/Ready.
6. As part of factory shipped data (.ADF). an
additional statement which will add an entry
into STTB_SCHEDULAR_UPLOADS
table.
7. Each interface code will have one entry
added on to the
STTB_SCHEDULED_UPLOADS table.
Basically an upload request should complete
and then should pick the next set of files.
Same upload request should not run in
parallel as it would cause conflicts. One
interface trigger can upload more than 1 file
based on the Incoming File Mask defined
during the interface definition.
8. This table is being polled by a scheduled job
 which is existing. This job has a polling
frequency & has to be controlled based on
the load requirements, volume of the request.
9. The scheduler limits the number of uploads
based on a threshold. If there are 5 interfaces
available they would get triggered at one
time. 6th one will have to wait for the first
one to complete. This again is an operational
limit to ensure that the overall application
impact is limited due to huge uploads. This
threshold can be reset but would need a
restart. This will be an one time set up.
10. As part of the scheduled job, the GI interface
would get triggered, completes the upload.
The process code for GI would be
‘AL’(Process All). Once completed, if an
outgoing interface is tagged as part of the
interface definition, a response file would be
generated based on the module specific
where condition that is defined. The response
file would have the naming as mentioned in
the File mask field of interface definition.
11. The response file would be placed in the
<Any Folder>/ready folder which can be
then consumed by external channels.

2.4 Features Out of Scope

None

2.5 Solution Flow Diagram

None

2.6 Solution Components List

Component Name Component Type Existing Owning Product

2.7 Assumptions and Constraints

2.7.1 Assumptions
1. The amount block request from the channels will be received only in account currency.

2.7.2 Constraints
None

2.7.3 Recommended Set Up

1. The web service FCUBSDEService for DE entry can be configured as auto authorized always in the integrated
scenario with FCPB/FCIS.

2. The field upload for DE (DEDJNLON) can be configured as auto authorized always in the integrated scenario with
FCPB/FCIS.
3. Artifacts to Plan and Validate User Design for <Feature ID> : Processing of
Amount Block Transactions, Debit Transactions & File Upload

3.1 Detailed Solution Flow

3.2 Product Use Cases

Scenario 1: Funds Sufficiency Check from external channel say FCPB.
FCPB is trying to do an amount block for INR 10,000 in the account no.005678345 on 30/09/2013. Hence FCPB is
doing a funds sufficiency check for INR 10,000 before sending the amount block request using the web service
FCUBSAccServiceOperation QueryCustAcc. The available balance in the account is INR 9,000, the same balance will
be provided to FCPB.

Scenario 2: Amount Block Request from external channel say FCIS.

FCIS consumes the web service “FCUBSCustomerService” & imposing the amount block with following details.
Field Name Value
Branch Code 001
Account Number 005678346
Currency of the Account INR
Amount of the Block 10,000
Effective Date 01/10/2013
Expiry Date 31/10/1013
Amount Block Reference Number AB4936
Block If Only Funds are Available Yes

On successful completion of the request amount block reference number AB4936 will be provided to FCIS.

Scenario 3: Processing Debit/Credit Transaction from extern channel say FCPB.

FCPB is posting the following online transaction in UBS using the web service FCUBSDEServiceOperation
CreateMjrnlbook.
Field Name Value Value for Entry 1 Value for Entry2
Batch No. 1111
Reference Number 000333110040002
Value Date 15/11/2013
Current Number 1
Currency USD
Branch Code 001
Serial No
User Ref No. 1 2
Dr/Cr Debit Credit
Account 000003171225 000008108011
Account Description 000003171225 000008108011
Acc or GL A A
Currency USD USD
 Branch Code 001 001
Amount 100 100
Exchange Rate 1 1
LCY Amount 100 100
Transaction Code 001 002
Instrument Number - -
Customer 000003171 000003171
Additional Text - -
Amount Block - -

Once the transaction is successfully processed successfully in UBS a confirmation will be sent back to FCPB.

3.2.1 Activity – Task Name:

Products
Trigger Event
Desired Outcome
Pre-Conditions
Post-Conditions
Job Role
Visio File

3.2.1.1 <PUC ID> : <PUC Name>

3.2.1.1.1Scenario 1 - <PUC ID>: < Scenario Name> (Primary)

Parent PUC
Scenario Type
Description
Related Business Use Case ID
Setup Assumptions
Scenario Priority

3.2.1.1.1.1 Steps – Scenario 1 - <PUC ID>

Step Job Role Step Description System Response

1-1

3.2.1.2 Event Information

3.2.1.2.1Action Event Name: NA

3.2.1.3 Performance Considerations

Not Applicable
Reference to Product Level Performance
Requirements
Scenario Duration (regardless of the number of sessions) Think Time (in Seconds)

Performance Considerations
Type (select one from options below for Description
each row)

Response Times by Use Case Step (Transaction)

Use Case Step Type of Operation KPI (sec) Override time(sec) Override Reason
(Transaction)

3.3 Navigation

3.4 UI Wireframe

3.5 UI Prototype
3.5.1 Addition of New Flag in Amount Block Input Screen - CADAMBLK

1. A new flag “Block Only If Funds are Available” will be added in the Amount Block Input Screen (CADAMBLK).

Function Path Customer AccountsCustomer Account

OperationsAmount Block Input.
Function ID CADAMBLK
3.5.2 Addition of New Field in Journal Entry Input Screen - DEDJNLON
Function Path Accounting and MISJournal Posting OperationJournal
Entry Online
Function ID DEDJNLON
=
 3.6 Page Information

3.7 UI Elements

3.7.1 Amount Block Input Screen - CADAMBLK

Display Alt Text Description Attribute Object Required/ Business Data Type/ Field Validation Default Value
Name Type Type Mandatory object Size
attribute
Verify Verify When this Manual Checkbox No NA Varchar (1) None Blank
Available Available flag is Input
Balance Balance selected
system will
block the
amount only
sufficient
funds are
avaiable
Source Source The source Display Textbox No NA Valid source None None
Code Code code from code values
which the
amount
block has
been
initiated

3.7.2 Addition of New Field in Journal Entry Input – DEDJNLON

Display Alt Text Description Attribute Object Required/ Business Data Type/ Field Validation Default Value
Name Type Type Mandatory object Size
attribute
Amount Amount Display Text box No NA Size of Valid Amount Blank
Block Block The amount existing Block reference
Number Number block amount Number. Value to
number block this field can be
provided in number in provided only
this field will CADAMBL during file upload.
be released K screen.
as part of the
DE
transaction.
3.8 UI Business Rules

3.9 UI Error Messages

3.10 Embedded Help

3.11 Impact on Audit Trail

3.12 Impact on Authorization

4. Security Considerations
4.1 Privileges

Name Description Incompatibilities

4.1.1 Duties

Duty Description List of Privileges Incompatibilities

4.2 Function Security Mapping

Role Duty Privileges

4.3 Data Security Mapping

4.3.1 Permissions

Role Operation Attribute Business Object Data Purpose

Access
(LOV)

4.3.2 Constraints

Role (LOV) Operation Attribute Business Object Data Access Purpose

4.4 Other Security Considerations

5. SOA Components
None

5.1 Reference to SOA Components deliverable

Location Comments
6. Task Flow Annotations for BPEL
Not Applicable

Task Annotation Related Business Object Related Business Event Default Approval
Process
7. Service Solution Component
7.1.1 Service Information
Related Features
Service Visibility
Business Process Task
Business Objects
Consuming Products
Consuming Technology
Related Use Cases
Extensibility Required
Industry Standard
Third Party Integration
Setup Related
Cross-Instance
Used for Replication

7.1.2 Related Business Object Operations

Business Object Operation Comments

7.1.3 Support for Copying Data across Instances

7.2 FCUBSCustomerService
1. The new fields “Block Only If Funds are Available” will be added in the following operations.

a. CreateAmtBlk.

b. ModifyAmtBlk.

c. CloseAmtBlk.

2. The operation CreateAmtBlk can be consumed by external channels for creating new amount blocks.

3. The operation ModifyAmtBlk can be utilized by the external channels for modifying amount blocks.

4. The operation CloseAmtBlk can be utilized by the external channels for releasing the existing amount blocks.

7.2.1 Service Information

Related Features
Service Visibility
Business Process Task
Business Objects
Consuming Products
Consuming Technology
Related Use Cases
Extensibility Required
Industry Standard
Third Party Integration
Setup Related
 Cross-Instance
Used for Replication

7.2.2 Related Business Object Operations

Business Object Operation Comments

7.3 FCUBSDEService
1. The operation CreateMjrnlbook can be utilized by external channels for posting debit/credit transactions online.

7.3.1 Service Information

Related Features
Service Visibility
Business Process Task
Business Objects
Consuming Products
Consuming Technology
Related Use Cases
Extensibility Required
Industry Standard
Third Party Integration
Setup Related
Cross-Instance
Used for Replication

7.3.2 Related Business Object Operations

Business Object Operation Comments

8. BI Reports Solution Component
None

8.1 <BI Report Name>

8.1.1 Page Information

Page Prototype URL
Related Features
Navigation
Related Use Cases
Rendering Options

8.1.2 Screenshot

8.1.3 Report Attributes

Column Factoring
Default Sort Order
Column Sorting
Non-Displayed Column
Number of Rows
Displayed
Parameter Display Only
Outlier Suppression
Access from Menu
Switching Labels
Subtotal
Page Total
Grand Total

8.1.4 Parameters

Parameter Description Type Default Value Required

Name
<Yes/No>

8.1.5 Field Specifications and Validations

Attribute Description Type Object Mandator Data Field Default

Type y Type/ Validation Value
Size

8.1.6 Business Rules

8.1.7 Error Messages

Sl. Validation Type Message Actionable by End
No. User

8.1.8 Table Column Definitions

Header Section

Column Description Retrieval Logic

Name

Tabular Section
Column Description Retrieval Logic
Name

8.1.9 Report Format

8.1.10 Graphs

Graph Name Definition

8.1.11 Drills from Table

Column Parameter Combinations Destination Report Related Links

8.1.12 Reconciliation with Application Data

9. Reporting Solution Component
Not Applicable

9.1 <Report Name>

9.1.1 Report Information

Related Features
Related Use Cases
Third Party Integration

9.1.2 Data Extraction Definition

Name
Code
Data
Columns
Summary Columns

9.1.3 Parameters

Parameter Name Description Type Default Value Required

<Yes/No>

9.1.4 Business Rules

9.1.5 Error Messages

Sl. Validation Type Message Actionable by End

No. User

9.1.6 Layout Templates

Name
Code
Description
Data Definition
Template Type
Sub Template
Layout Mockup URL
9.1.7 Table Column Definitions

Header Section

Column Description Retrieval Logic

Name

Tabular Section
Column Description Retrieval Logic
Name

9.1.8 Drills from Table

Column Parameter Combinations Destination Report Related Links

10. External Interface
Not Applicable

10.1 < External Interface Name>

10.1.1 Interface Format Detail

File level attributes Description

10.1.2 Header and Body Details

Header Details
No Field Name Type Length Derivation Logic Default Values

Body Details
No Field Name Type Length Derivation Logic Default Values

10.1.3 Error Handling

11. Background Processing Solution Component

11.1 <Background Process Name>

11.1.1 Background Process Information

Related Features
Related Use Cases
Third Party Integration
Performance Considerations
Reference to Product Level
Performance Requirements
Can Be Run in Parallel
Has Constraints
Requires Return ability

11.1.2 Parameters

Parameter Name Description Type Default Value Required

<Yes/No>

11.1.3 Business Rules

11.1.4 Error Messages

Sl. Validation Type Message Actionable by End

No. User

11.1.5 Output

11.1.6 Log File

12. Seed Data
Not Applicable

12.1 <Requirement Name>

12.1.1 Lookups

12.1.2 Value Sets

12.1.3 FlexFields

12.1.4 Other Seed Data

13. Impact on other modules or Operations with the Product
Not Applicable

13.1 <Impact Name>

13.1.1 Screenshot of <impacted screen>

13.1.2 Changes to <impacted screen>

14. Migration Impact
15. Dependencies and Impacts
Not Applicable.

15.1 Dependencies

Name Related Feature Product Dependent On Description

15.2 Impacts

Name Related Feature Impacted Product Description

16. Uptake Considerations
Not Applicable
17. Open and Closed Issues
17.1 Open Issues

17.1.1 Issue [Name, Number]

Related Features
Date Raised
Priority
Owner
Raised by
Interested Parties
Target Date
Date Closed
Issue Description

17.2 Closed Issues

17.2.1 Issue [Name, Number]

Related Features
Date Raised
Priority
Owner
Raised by
Interested Parties
Target Date
Date Closed
Issue Description
Resolution
18. Appendix: <Multi Multi Journal Entry & Amount Block Modification Amount
Block Release Files>