Business Blueprint

Global Business Blueprint

Project: TARABUT
Created by: Created on: RAVIPRAKASH 12/27/2011

____________________ Signed on

____________________ Signature: Customer

____________________ Signature: Consultant

Business Blueprint

Revision History
Document Version # 1.0 1.1 Date 27-Dec-2011 21-Jan-2012 Author Ravi Prakash Ravi Prakash Description of Change Initial document Changed the document Recommendations as Per E&Y

12/27/2011 2

Business Blueprint

Contents

12/27/2011 3

Business Blueprint Acronyms

S.No 1. 2. 3. 4. 5. 6. 7. 8. 9. 10

Abbreviation AKMS FI CO SAP TRM SAR CLM FSCM Dr Cr

Description Abdul Kader Al Muhaidib & Sons Co Finance Module Controlling Module Systems Application & Product In Data Processing Treasury and Risk Management Saudi Riyal Cash and Liquidity Management Financial Supply Chain Management Debit Credit

12/27/2011 4

Business Blueprint

SAP Implementation for AMG_TARABUT

1 Business Scenarios
1.1 Treasury and Risk Management
Treasury and Risk Management (TRM) This document is a result of workshop study and requirement analysis carried out at Al-Muhaidib, Dammam. The purpose of this document is to map the Abdul Kader Al Muhaidib & Sons Cos Treasury and Investment requirements on to SAP standard functionality of the Treasury and Risk Management based on the requirements narrated in the standard templates. This document is to be studied by core users, Business process owners and executive management team. The preparation of this document is an essential precursor to prototyping and testing. Scope of Treasury and Risk Management Module The Scope of SAP Treasury and Risk Management is to monitor Treasury flows including Investments and Borrowings. All the functions under Treasury and Risk Management will be depend on Product types, flow types and transaction types. The implementation of Treasury and Risk Management is confined to the following company codes Company code 1000 1100 1200 Company Name Abdul kader Al Muhaidib & Sons Co. Al Muhaidib Holding Co. Al Muhaidib Development Co.

1.1.1 Organizational Units

1.1.1.1 Organizational Structure Organisational Structure This Blueprint has been developed based on the discussions with Subject Matter Experts nominated by Abdul Kader Al Muhaidib & Sons Co, Al Muhaidib Holding Co and Al Muhaidib Development Co from Treasury and Investment departments. Organisational Basic Settings Requirements / expectations The following company codes desires that the activities performed by the Treasury and Investment teams should be mapped to SAP Treasury and Risk Management within SAP FSCM Module. Company code Company Name 1000 1100 Abdul kader Al Muhaidib & Sons Co. Al Muhaidib Holding Co.

1200 Al Muhaidib Development Co. Using SAP TRM the Treasury and Investment departments should be able to view real time Treasury positions, calculations and reports. The information should be accurate in terms of inflows and outflows and integrates with Finance and Cash and Liquidity modules. General explanations

12/27/2011 5

Business Blueprint Treasury and Risk Management (TRM) component, Transaction Manager fulfils the requirements of Treasury and Investment management by providing a comprehensive view of all business transactions related to it. Transaction Manager The Transaction Manager is a powerful instrument that executes efficient liquidity, portfolio and risk management and consists of sub components of Money Market, Foreign Exchange, Securities and Derivatives to facilitate different types of transactions in Treasury and transfer to Financial Accounting. All the functions under treasury will be depend on Product types, flow types and transaction types. Product Type- Helps to differentiate between different financial instruments. Differentiation is necessary when the individual instruments are subject to different processing rules. The product/category for example Medium Term Loan and Short Term Loan. Transaction Type- Determines the transaction posting of a product type. For ex: Borrowing of Term Loans/repayment of Term Loans.. Flow type- The flow type/category allows the system to interpret the calculation category and determines the representation in the cash flow. Flow types also control the effective interest rate calculation and Valuation of the financial instrument. For ex: Forex valuation. All the expenses such as Commission, Management charges will be captured by using flow types Business Partner- It is a prerequisite for making transactions. Business partner will be our Banker, Issuer or Broker. The following Treasury and Risk Management functions would be used for the following company codes Company code Company Name 1000 Abdul kader Al Muhaidib & Sons Co. 1100 Al Muhaidib Holding Co. 1200 Al Muhaidib Development Co. Money Market All Fixed Deposits and Borrowings will be covered under this function. Each type of borrowing/Investment is denoted by Product Type. Foreign Exchange All forward agreements/contracts of foreign exchange will be covered under this function. Securities The Investments in Various Shares (Listed/others), Funds will be covered under this function. Each type of Investment is denoted by a Product Type. Derivatives The Investments in Various types of derivatives such as Interest rate Swap(IRS),Forward Rate Agreement (FRA) and Options will be covered under this function. Naming convention The following company codes Company code Company Name 1000 Abdul kader Al Muhaidib & Sons Co. 1100 Al Muhaidib Holding Co. 1200 Al Muhaidib Development Co. intends use the following document type TR (Treasury Posting )for posting of Treasury transactions to Financial accounting. Treasury Number Range Number 14 12/27/2011 6 From Number 140000001 To Number 150000000 Int/Ext Internal

Business Blueprint

Flow Chart The TRM Organizational Structure for the following Company codes is defined below Company code Company Name 1000 Abdul Kader Al Muhaidib & Sons Co 1100 Al Muhaidib Holding Co 1200 Al Muhaidib Development Co

Business Process flow Job Description Transaction Process in Treasury Transactions in various areas of the transaction manager (Money market, Foreign exchange, securities) generally follow the same procedure. They are first entered in the front-office component and then checked in the back-office component before being transferred to accounting.

Trading / Front office The front-office component contains functions for creating and displaying financial transactions. The software supports a range of practical auxiliary and control functions that can be used to optimize trading. These include functions for entering and evaluating offers, fast entry functions for common transactions, limit checks, date checks, expiration, and other support evaluations. Decision-making tools such as the cross-rate calculator, the option-price calculator, and the net present value (NPV) calculator are also 12/27/2011 7

Business Blueprint available. Back office In the back-office component, the complete transaction data such as account assignment information and payment details and transfer it to accounting using the settlement function. Correspondence functions, such as automatic confirmations and counter confirmations, can also be used. Other typical back-office tasks include interest-rate adjustments based on variable interest rates, and payment netting arising from financial transactions. Accounting SAP Treasury and Risk Management also has automatic-posting functions to update the general ledger in real time. The system provides the process of valuation, accrual, and deferral procedure of financial instruments and flexible functions for processing payment transactions. The application also provides with reporting functions such as the posting journal and posting overview. Changes to existing organization Currently the following Company codes Company code 1000 1100 1200

Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

are using Microsoft office for maintaining Treasury and Investment transactions. Using SAP TRM Treasury and Investment departments would be able to view real time Treasury positions, calculations and reports. Description of improvements Using the SAP Best adopted Practice the following Company codes. Company code 1000 1100 1200 above organizational structure is defined and adopted for the Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development C

Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit None System configuration considerations 1. Financials Extension (business function EA-FIN) within the SAP ECC Extension needs to be activated. 2. Saudi Riyal Currency (SAR) would be used as default currency. 3. Company code defined in Finance and controlling area, objects defined in CO, will be used in TRM module 4. Company code additional data has to be extended in Treasury and Risk Management. Integration Considerations Sr. No. Module Description of integration Description Gap resolution

12/27/2011 8

Business Blueprint None Reporting Considerations None Authorization and user roles Creation (FTR_CREATE) and Settlement (FTR_EDIT) and posting to FI (TBB1) will be given access and should be approved by change control board. 1.1.1.2 Organizational Structure of CLM Cash and Liquidity Management This document is a result of workshop study and requirement analysis carried out at Al-Muhaidib, Dammam. The purpose of this document is to map the Abdul Kader Al Muhaidib & Sons Cos Cash Management on to SAP standard functionality of the Cash and Liquidity Management based on the requirements narrated in the standard templates. This document is to be studied by core users, Business process owners and executive management team. The preparation of this document is an essential precursor to prototyping and testing. Organisational Units This Blueprint has been developed based on the discussions with Subject Matter Experts nominated by Al Muhaidib Group from Treasury department Scope of Cash and Liquidity Management Module The Scope of SAP Cash and Liquidity Management is to monitor Cash flows and Liquidity forecast including Treasury, Accounts payable and Accounts receivables. The implementation of Cash and Liquidity Management is confined to the following company codes Company code Company Name 1000 Abdul Kader Al Muhaidib & Sons Co 1100 Al Muhaidib Holding Co 1200 Al Muhaidib Development Co Organisation Basic Settings Requirements / expectations The following Company codes Company code 1000 1100 1200

Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

desires that the activities performed by the Treasury team should be mapped to SAP Cash and Liquidity Management within SAP FSCM Module. The Treasury department is able to view real time cash positions and forecasting reports. The information should be accurate based on the actual data from other modules (SAP FI, MM, SD and Treasury) effecting the inflows/outflows. In addition any short term planning effecting inflow/outflows (not flowing from other SAP modules) should also get reflected in cash positioning & cash forecasting General explanations

12/27/2011 9

Business Blueprint SAP Cash Management is used to monitor cash flows and to ensure that an entity has sufficient liquidity to cover various obligations. The SAP system provides the opportunity to determine bank status and liquidity forecast on different levels of the group. The liquidity decisions are taken centrally on a corporate level. The actual and detailed information from SAP Cash Management provides a good basis to net liquidity gaps and surpluses of subsidiaries and establish a centralized process. As a result of the high degree of automation within SAP Cash Management, only exception processing needs to be done manually. This principle treats with care the alertness of all involved parties who can fully concentrate on the exceptions and special cases that arise during the post processing procedure. In addition, daily automatic processing implicates a better operational control, because unexpected transactions are promptly visible and mistakes can be removed straight away. Naming Convention None Flow Chart None Business Process flow Job Description The following Cash Management functions would be used for the following Company codes Company code 1000 1100 1200 Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

Data Transfer from Operative Systems Commitments for forecasting purpose from Sales Order and Purchase Order. Open items (receivables and payables) from Customer Billing and Vendor Invoicing etc. Cash Position & Monitoring - The cash position supplies information on the current financial situation of bank accounts and bank clearing accounts. Integration with single records means that the cash position can give an overview over short-term liquidity trends. Liquidity Forecast & Monitoring - The liquidity forecast shows changes in liquidity in the sub-ledger accounts and helps to obtain information regarding expected payment flows. The liquidity forecast is based on incoming and outgoing payments from accounts receivable and payable, and also on open items and manually entered planned items. Changes to existing organization

12/27/2011 10

Business Blueprint Currently the following company codes Company code Company Name 1000 Abdul Kader Al Muhaidib & Sons Co 1100 Al Muhaidib Holding Co 1200 Al Muhaidib Development Co are using Microsoft office for monitoring Cash Position & Liquidity forecast. Using CLM, the above mentioned company codes would be able to view its real time cash positions and forecasting reports. The information should be accurate based on the actual data from other modules (SAP FI, MM, SD and Treasury) effecting the inflows/outflows. In addition any short term planning effecting inflow/outflows (not flowing from other SAP modules) should also get reflected in cash positioning & cash forecasting. Description of improvements Using the SAP Best Practices the above organizational structure is defined and adopted for the following Company codes. Company code Company Name 1000 Abdul Kader Al Muhaidib & Sons Co 1100 Al Muhaidib Holding Co 1200 Al Muhaidib Development Co Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit None System configuration considerations Financials Extension (business function EA-FIN) within the SAP ECC Extension needs to be activated. Saudi Riyal Currency (SAR) would be used as default currency Company code defined in FI and controlling area, objects defined in CO, and TRM module will be used in Cash and Liquidity Management. Description Gap resolution

Integration Considerations Sr. No. Module Description FI Reporting Considerations None Authorization and user roles Authorization for Planning Memo records (FF63), Cash Position (FF7A) and Liquidity forecast (FF7B) will be provided to Fund Manager. Integration to FI will be established through General ledger accounts and Sub ledger accounts.

1.1.2 Master Data

12/27/2011 11

Business Blueprint 1.1.2.1 Business Partner Master Data for TRM Requirements / expectations The following Company codes Company code 1000 1100 1200

Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

are intends to design a business process to handle Treasury and Risk Management activities associated with the Master Data. Business Partner will be used as Master Data for Treasury and Risk Management General explanations Business Partner: Business partner is a natural or legal person with whom business relationships are maintained. Business partners are divided into different categories, which have different attributes assigned to them. The functions of the business partner in the contract are determined using business partner roles, for example Counter Party, Issuer and Depository Bank. Naming Convention Business Partners are divided into different categories based on their roles as Counter party, Issuer and Depository bank. The following would be the number ranges for Business Partner for the following Company codes Company code 1000 1100 1200 Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

Business Partner Number Range Number ranges for the Business Partner Number Range for Business Partner Number 01 From Number 1001 To Number 9999 Int/Ext Internal

12/27/2011 12

Business Blueprint Flow Chart None

Business Process flow Job Description The event provides the details/process to create the Business Partner in Treasury and Risk Management and also highlight the key fields which are required for Creation of Business Partner. Business Partner The data process for a Business Partner is divided in to three areas, i. General Data This data is held centrally for all business partner roles. Access to the data can vary according to the role category, depending on the system settings in the Implementation Guide (IMG) for the Business Partner. ii. Company Code-Dependent Data This is data that only applies for a particular role in the relevant company code. iii. Differentiated Data In the standard version this is data from Additional Information, Ratings, and Customer Segments that can be defined differently by means of a differentiation criterion. The following are Business Partner Roles defined for the above mentioned Company codes. Business Partner Roles Business Partner Roles Counter Party Issuer Depository Bank

Changes to existing organization In the current system there is no concept of Business Partner. Using SAP TRM and the concept of Business partner, Treasury department can identify and monitor the financial transactions in detail.

Description of improvements Using the object of Business partner, the identification and monitoring the financial instrument will be made easy. Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit None Description Gap resolution

System configuration considerations 12/27/2011 13

Business Blueprint Creation of number ranges for Business partner and Creation of Business Partner using Transaction code BP Integration Considerations Sr. No. Module 1

Description of integration

Bloomberg Integration Interface with external software called "Bloomberg" for stock market price updation.

Reporting Considerations N None Authorizations and User Roles Treasury Managers will provide access for executing the Transaction Manager for different product types.

1.1.2.2 Transaction Manager Requirements / expectations The following Company codes Company code 1000 1100 1200

Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

intends to design a business process to handle Treasury and Risk Management activities associated with the Master Data. General explanations Transaction Manager The Transaction Manager follows the straight-through processing principle for entering different transaction types through to transfers to Financial Accounting. To achieve this goal, the front-end area has been regularly enhanced and functions and basic structures have been standardized for financial transactions through its Subcomponents of Money Market, Foreign Exchange, Securities and Derivatives. Naming Convention SAP standards have been followed for naming convention of Customized products for Money Market and 12/27/2011 14

Business Blueprint Securities. Money Market Product Type ZML for Mid-term loans Product Type ZSL for Short-term loans Product Type - ZPL for Promissory notes Payable Product Type ZIL for Inter company Loans Securities Product Type 01A- Stocks for Shares(Listed) Product Type ZPE for Public Equity Product Type ZNP Non-Public Equity(Private Equity cost method) Product Type ZNE Non-Public Equity(Private Equity Equity method) Product Type ZPF Fund Product Type ZTP Trading Portfolio Product Type ZDP Discretionary Portfolio Product Type - ZAM Application Money/ Advance towards Investment

Flow Chart None

Business Process flow Job Description Transaction Manager As per the business process of the following Company codes Company code 1000 1100 1200 Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

and after discussions with the subject matter experts from Treasury and Investment departments, the following standard product types have been finalized in SAP TRM. a. Money Market I. Standard Products Product Type 51A for Fixed Deposits Product Type 56A for Facility b. Foreign Exchange 12/27/2011 15

Business Blueprint I. Standard Products Product Type 60A for Foreign Exchange Forward contracts c. Securities I. Standard Products Product Type 01A- Stocks for Shares(Listed / non listed equity) d. Derivatives I. Standard Products Product Type 62A Interest Rate Swap. The business process of Transaction Manager will be discussed separately under different subcomponents as Money Market, Foreign Exchange, Securities and Derivatives individually Changes to existing organization Currently the following Company codes Company code 1000 1100 1200

Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

are using Microsoft office to monitor Treasury transactions using SAP TRM, entity can monitor Investments and borrowings.

Description of improvements Using the object of Transaction Manager, the identification and monitoring the financial instrument will be made easy from its sub components like Money market, Foreign Exchange, Securities and Derivatives for different types of financial instruments. Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit None Description Gap resolution

System configuration considerations Transaction Manager discussed separately under different subcomponents as Money Market, Foreign Exchange, Securities and Derivatives individually. Integration Considerations Sr. No. Module 12/27/2011 16

Description of integration

Business Blueprint FI Integration to FI will be established through Account determination in TRM by assigning respective General Ledger accounts.

Reporting Considerations N None Authorizations and User Roles Treasury Managers will provide access for executing the Transaction Manager for different product types. 1.1.2.3 Master Data of CLM Requirements / expectations The following company codes Company code 1000 1100 1200 Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

wants to view its cash positions at various levels to enable them to interpret their cash positions and forecasting easily thus enabling them to take timely and accurate decisions. Cash and Liquidity Management flows depend on Planning levels and planning groups. General explanations Planning levels include outgoing checks, outgoing bank transfers, check receipts, FI postings, purchase orders, Sales orders, and confirmed or unconfirmed payment advices. For structuring purposes, planning levels are divided by where they came from, and assigned to either the cash position or liquidity forecast. A planning level is defined in the Company Code specific part of the General Ledger Master Data. The planning level reflects the nature of the financial transaction: FI posting to a bank account FI posting to a clearing account Confirmed or unconfirmed notes The following types of levels are possible in SAP: Noted items in cash position & liquidity forecasting Purchase Orders Sales Orders Financial payment transactions settlements (incoming payments and outgoing payments) Postings with payment blockings Financial bank transactions (Bank statement postings) Planning levels for Treasury transactions Planning Groups select and structure the required dataset and are responsible for compiling the liquidity 12/27/2011 17

Business Blueprint forecast. A planning group represents particular characteristics, behaviours or risks of the customer or vendor group. Planning groups helps in breaking down incoming and outgoing payments according to the amount, the probability of the cash inflow or outflow, and the type of business relationship. Naming Convention None Flow Chart None

Business Process flow Job Description The event provides the details on the various master data used for Cash & Liquidity Management. The event will also highlight the key fields within each these master data which affect the cash positioning and liquidity forecast and also list the possible values for each of these important fields in the master data. Planning Levels The planning levels makes the display of the cash position and of the cash forecast more transparent explaining the origin of the data For all the Bank Accounts (Main, Issued and Collection A/c) would be assigned to a planning level. All the ledgers for which planning level would be assigned should also be checked as relevant to cash flow. This check also forms part of the company code specific data of GL Maser Following Planning levels would be used by the following Company codes Company code Company Name 1000 1100 1200 Planning Levels Planning Levels B0 B1 B2 C1 T1 T2 T3 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

Description Bank Main Bank outgoing Bank Incoming Cash Account Treasury Borrowings Treasury Investments Treasury Forex

Planning Groups Planning groups for Cash Management are assigned to customer and vendor master records for the 12/27/2011 18

Business Blueprint liquidity forecast. The field is part of the Accounting information tab of the Company Code specific data of the customer/vendor. The planning group reflects certain characteristics, behaviours and risks of the customer or vendor group Cash management groups are supplied data from the relevant postings within MM (Purchase Orders), SD (Sales Orders) and actual FI Postings. Planning groups for the above mentioned Company codes would be as under: Planning groups for Vendors Cash Management Description groups for Vendors V1 Domestic Vendors V2 V3 V4 V5 V6 V7 Foreign Vendors Petty Cash Vendors Employee Vendors Inter Company Vendors RE- Vendors One time Vendors

Planning groups for Customers Cash Management Description groups for Customers F1 Whole sale customers F2 F3 F4 F5 F6 F7 F8 Key Account customers Super Market customers Mini Market customers Restaurant Customers Catering customers Export customers RE- Customers

Changes to existing organization Currently the following Company codes Company code 1000 1100 12/27/2011 19

Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co

Business Blueprint

1200

Al Muhaidib Development Co

are using Microsoft office for forecasting Cash Position & Liquidity forecast. The above mentioned company codes would be able to view its real time cash positions and forecasting reports. The information should be accurate based on the actual data from other modules (SAP FI, MM, SD and Treasury) effecting the inflows/outflows. In addition any short term planning effecting inflow/outflows (not flowing from other SAP modules) should also get reflected in cash positioning & cash forecasting.

Description of improvements Using the SAP Best Practices the above Master data is defined and adopted for the Company codes Company code Company Name 1000 1100 1200 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit None Description Gap resolution

System configuration considerations 1. Creation of Planning Levels 2. Creation of Planning group Integration Considerations Sr. No. Module None FI

Description of integration Integration to FI will be established through General ledger accounts and Sub ledger accounts.

Reporting Considerations N None Authorization and user Roles Authorization for Planning Memo records (FF63), Cash Position (FF7A) and Liquidity forecast (FF7B) will be provided to Fund Manager.

12/27/2011 20

Business Blueprint 1.1.3 Business Processes 1.1.3.1 Money Market Money Market Requirements / expectations The following are the financial instruments, the Company codes Company code Company Name 1000 1100 1200 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

intends to capture under Money Market in SAP Treasury and Risk Management. a. Fixed Deposits b. Term Loans (Medium term, Short term and Notes Payable ) c. Facility

General explanations Money Market is a subcomponent of Transaction Manager which consists of different Product Types to capture different types of Financial instruments. All Fixed Deposits and Borrowings will be covered under this function. Each type of Borrowing/Investment is denoted by Product Type and the transactions of product type depend on transaction types and flow types. Product Type- Helps to differentiate between different financial instruments. Differentiation is necessary when the individual instruments are subject to different processing rules. The product/category for example Fixed Deposits and Term Loans Transaction Type- Determines the transaction posting of a product type. For ex: Borrowing of Term Loans/repayment of Term Loan Flow type- The flow type/category allows the system to interpret the calculation category and determines the representation in the cash flow. Flow types also control the effective interest rate calculation and Valuation of the financial instrument. For ex: Forex valuation. All the expenses such as Commission, Management charges will be captured by using flow types Naming Convention SAP Standard procedure has been adopted for the customizing product types ZML, ZSL, ZPL and ZIL The following would be the number range for Money Market transactions for the following Company Codes Company code Company Name 1000 1100 1200 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

12/27/2011 21

Business Blueprint Number Ranges for Money Market transactions Product Type 51A ZML ZSL ZPL ZIL 56A Flow Chart a. Fixed Deposit Number Range 01 02 03 04 05 06 From Number 100001 200001 300001 400001 500001 600001 To Number 200000 300000 400000 500000 600000 700000 Int/Ext Internal Internal Internal Internal Internal Internal

12/27/2011 22

Business Blueprint

b. Term Loans

12/27/2011 23

Business Blueprint

c. Facility

12/27/2011 24

Business Blueprint

Business Process flow Job Description The event provides the details/process to capture the Financial Transactions in Treasury and Risk Management and also highlight the key fields which are required for entering Financial transactions. The following are the financial instruments applicable for the below mentioned Company codes Company code Company Name 1000 1100 1200 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

Under Money Market in SAP Treasury and Risk Management. a. Fixed Deposit The Fixed deposit will be captured in Treasury and Risk Management by using Product Type, Transaction Type and Business Partner Product Type 51A Transaction Type determines the transaction whether it is investment or maturity including premature Withdrawals. Transaction Type - 100 (Investment) Business Partner Where the Fixed deposit has to be made (ex: Banker) Financial Entries for Fixed Deposit Fixed Deposit A/c Dr XXXX To Bank Account Cr XXXX (When Fixed Deposit is Made) Bank Account Dr XXXX To Fixed Deposit A/c XXXX To Interest Received A/c XXXX ( At the time of Maturity of Fixed Deposit) b. Term Loans Term loans are classified into 3 categories for the following Company codes Company code Company Name 1000 1100 12/27/2011 25 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co

Business Blueprint 1200 Al Muhaidib Development Co

as Medium term loans, short term and Notes Payable and will be captured by using product type. Transaction Type and Business Partner. Product Type ZML for Medium term loans Product Type ZSL for Short term loans Product Type ZPL for Notes Payable Transaction Type 200 Borrowings Business Partner- where the Borrowings has to be made.(for ex- Banker) Financial Entries for Term Loans Bank Account Dr XXXX To Term Loan a/c Cr XXXX (When Term Loan is Taken from Bank) Interest on Term Loan A/c Dr XXX To Bank Account Cr XXX (When interest on Term Loan paid) Term Loan A/c Dr XXXX To Bank Account XXXX ( At the time of Closure of Term Loan) c. Facility The Facility will be captured in Treasury and Risk Management by using Product Type, Transaction Type and Business Partner Product Type 56 A Transaction Type 100 Facility assigned 200 Facility obtained Business Partner - where the Facility has to be made.(for ex- Banker) There will not be any financial entries for facility. Facility can be viewed/monitored against each borrowings made against each facility in TRM. a. Business Process flow for Money Market Fixed Deposit Step No. Step Name 10 Process step description Delivered By TM01 (or ) FTR_CREATE FTR_EDIT

Fixed depositFixed deposits would be created in SAP by the Treasury Creations department Fixed Deposit transaction Settlement Fixed deposit would be settled in SAP Treasury before posting to finance. The purpose of settlement is to check the accuracy of the transaction and to authorize it in SAP Treasury

20

30

40 50

Fixed Deposit Fixed deposit will be posted to Finance from SAP Treasury transaction posting to Finance Fixed Deposit Reversal Fixed deposit will be carried out in SAP TRM Reversal Fixed DepositThe system will take care of Accrual interest calculations by Accrual Entry running transaction. The system will post the values of accrual/deferral on the date on which the transaction is executed and reverse on the next day automatically

TBB1

FTR_EDIT TBB4 (Accrual/deferral)

12/27/2011 26

Business Blueprint 60 Fixed Deposit Maturity / premature Closures Fixed Deposit Rollover Fixed Deposit maturity or premature will be carried out in Treasury FTR_EDIT

70

Maturity date/period of existing Fixed deposit term can be extended by using Rollover in SAP.

FTR_EDIT

b. Business Process flow for Money Market Term Loans Step No. Step Name 10 ZML/ZSL/ZPL creation Process step description ZML/ZSL/ZPL would be created in SAP by the Treasury department. Delivered By TM01 (or ) FTR_CREATE

20

ZML/ZSL/ZPL transaction Settlement

ZML/ZSL/ZPL would be settled in SAP Treasury before posting to finance. The purpose of settlement is to check the accuracy of the transaction and to authorize it in SAP Treasury

FTR_EDIT

30

ZML/ZSL/ZPL ZML/ZSL/ZPL will be posted to Finance from SAP TBB1 transaction postingPS Note: Transactions cannot be modified once they have to FI been posted to Finance. ZML/ZSL/ZPL Reversal ZML/ZSL/ZPL Closure FTR_EDIT

40

ZML/ZSL/ZPL can be reversed after posting to Finance in SAP Treasury first and then reverse in Finance

50

60 70

ZTL/ZSL/ZPL Accrual Interest ZTL/ZSL/ZPL Extension

ZML/ZSL/ZPL can be closed by editing the original FTR_EDIT transaction which has its unique identity (Separate number) generated by SAP Once the ZML/ZSL/ZPL has been prematurely closed the same needs to be settled again and then eventually posted to FI. The system will take care of Accrual interest calculationsTBB4 by running transaction in SAP Treasury. Extension of existing ZTL/ZSL/ZPL can be extended by FTR_EDIT using Rollover in SAP

c. Business Process flow for Money Market Facility Step. No. 10 Step Name Facility Creation Process step description Facility would be created in SAP by the Treasury department. Delivered By FTR_CREATE

20

Facility Utilisation

Facility can be viewed/monitored against each borrowings FTR_EDIT made against each facility

Changes to existing organization 12/27/2011 27

Business Blueprint There is no existing system defined in the organisation. At present the following company codes Company code Company Name 1000 1100 1200 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

are using Microsoft office to maintain the record of transactions. Treasury department should be able to view real time Treasury positions, calculations and reports through SAP TRM. Description of improvements System provides automated calculation of interest and repayment of borrowings at the time of making transaction for the entire tenure of the borrowings. This helps to monitor the interest payments and repayment of the borrowings on a periodic basis. Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit Description 1 Product types

Gap resolution

There are no standard product types for Medium Term Create new Loans (MTL), Short term loans (STL) and Promissory note product types for loans(PFL) in SAP. ZML, ZSL ZPL and ZIL for the MTL,STL,PFL and ICL loans respectively

System configuration considerations 1. Configuration of customized product types ZML, ZSL and ZPL for borrowings. 2. Number range for the transactions product wise(refer above mentioned step: Naming convention)

Integration Considerations Sr. No. Module Description of integration FI Integration to FI will be established through Account determination in TRM

Reporting Considerations Position of Financial instruments for Product Types on Periodic basis.

TPM 13 Fixed and Schedule flows for product type TPM 12 Fixed flows (Posted flows to Finance) for Product type Authorization and user roles Roles for Front office to make transaction of financial instrument (FTR_CREATE) Back office to validate and settle the transaction(FTR_EDIT) and Accounting for posting the transaction to Finance.(TBB1). 12/27/2011 28

Business Blueprint

1.1.3.2 Foreign Exchange Requirements / expectations The following are the financial instruments AKMS (company code: 1000) wants to capture under Foreign Exchange in SAP Treasury and Risk Management. The Scope of Foreign Exchange transactions are applicable for AKMS only. Product Type 60A for Forward contract Transaction Type 102 Forward Transaction General explanations The foreign exchange area covers all the business processes arising from both traditional foreign exchanges trading as well as trading with over-the-counter (OTC) currency options. The functions offered support the entire trading process starting from concluding the transaction in the front office, through to processing in the back office, and on to transferring data to financial accounting. For Premature/Rollover functionality, the system generates two single transactions that are linked by a reference unit. One transaction offsets the forward exchange transaction originally entered and the other transaction, a new one, allows the term to be adjusted using the amount data as default values. The two new transactions are linked to the original transaction. The relationship of a swap to the original forward transaction is automatically documented by the assignment of the individual transactions to a common finance project with an identical project number. This project number is in the administrative data which enables to display this referencing between related transactions in the transaction data. Naming Convention The following would be the number range for Foreign exchange transactions for AKMS. Number Range for Foreign Exchange transactions Product Number Type Range From Number To Number Int/Ext 60A 07 700001 800000 Internal Flow chart

12/27/2011 29

Business Blueprint

Business Process flow Job Description The event provides the details/process to capture the Financial Transactions of Foreign exchange in Treasury and Risk Management and also highlight the key fields which are required for entering Financial transactions. The following are the financial instruments AKMS(company code:1000) wants to capture under Foreign Exchange in SAP Treasury and Risk Management. Product Type 60A for Forward contract Transaction Type 102 Forward Transaction Financial Entries for Forward Contract When forward contract is Premature/closure Bank Account Dr XXXX To Foreign Exchange clearing A/c XXXX (When buying Foreign exchange ) Foreign Exchange Clearing A/c XXXX To Bank Account Cr XXXX (When Selling Foreign exchange) Business Process flow for Foreign Exchange Step No. Step Name 10 Forward Transaction Creation Forward Transaction Settlement Forward transaction posting to FI Process step description Delivered By

Foreign Exchange transactions would be created in SAP by TX01 (or ) the Treasury department FTR_CREATE Forward transactions would be settled in SAP Treasury before posting to finance. The purpose of settlement is to check the accuracy of the transaction and to authorize it in SAP Treasury Forward transactions will be posted to Finance from SAP Treasury FTR_EDIT

20

30

TBB1

12/27/2011 30

Business Blueprint Premature Forward transaction Premature settlement or rollover will beFTR_EDIT settlement /carried out in SAP Treasury. Rollover\ Changes to existing organization There is no existing system defined in the organisation. At present AKMS is using Microsoft office to maintain the record of transactions. Treasury department should be able to view real time Treasury positions, calculations and reports. 40

Description of improvements The functions offered support the entire trading process starting from concluding the transaction in the front office, through to processing in accounts and help to take accurate decisions. The system provides the Valuation of the positions of foreign exchange on periodic basis and generates accounting entries which reduces duplication of work. Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit Description None

Gap resolution

System configuration considerations 1. Maintenance of currency pair for forward contract. 2. Number range for Transactions.( refer above mentioned step: Naming Convention) Integration Considerations Sr. No. Module Description of integration . FI Integration to FI will be established through Account determination in TRM

Reporting Considerations Position of Financial instruments for Product Types on Periodic basis. TPM 13 Fixed and Schedule flows for product type TPM 12 Fixed flows (Posted flows to Finance) for Product type TPM1 Valuation of Financial instrument. Authorization and user roles Roles for Front office to make transaction of financial instrument (FTR_CREATE) Back office to validate and settle the transaction(FTR_EDIT) and Accounting for posting the transaction to Finance.(TBB1). 1.1.3.3 Securities Securities Requirements / expectations 12/27/2011 31

Business Blueprint The following are the financial instruments which the following Company codes Company code Company Name 1000 1100 1200 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

wants to capture under Securitas in SAP Treasury and Risk Management. Product Type 01A- Stocks for Shares(Listed) Product Type ZPE for Public Equity Product Type ZNP Non-Public Equity(Private Equity cost method) Product Type ZNE Non-Public Equity(Private Equity Equity method) Product Type ZPF Fund Product Type ZTP Trading Portfolio Product Type ZDP Discretionary Portfolio Product Type - ZAM Application Money/ Advance towards Investment The following are the Portfolios used under Securities in SAP Treasury and Risk Management. STOCK -Stocks & Shares(Listed / non listed equity) PUBEQ - Public Equity NPUBEC - Non-Public Equity(PRIVATE EQUITY- Cost) NPUBEQ - Non-Public Equity(PRIVATE EQUITY- Equity) FUND - Fund TRDPRT - Trading Portfolio DESPRT - Discretionary Portfolio The above mentioned Company codes wants to update its market data ((exchange rates, securities prices, reference interest rates, indexes etc.) through either Using a Market data file interface or Data feed and wants to analyze its position of securities by utilizing the SAP tool of Portfolio analyzer. General explanations SAP Treasury and Risk Management manage securities efficiently by helping by defining structure characteristics, conditions, and parameters for valuation and position management in security master data. This provides the basis for automating trading, back-office, and accounting processes. The current market data (exchange rates, securities prices, reference interest rates, indexes etc.)can be maintained in a number of ways: Manually Using a Market data file interface: To maintain the relevant data in an external application (such as Microsoft Excel), either manually or via a data provider, and then import the data into the system in an SAPcompatible format. By transferring the market data to the system from a spreadsheet Data feed: The data feed connection can be used to make real-time market data available in the system. Portfolio Analyzer 12/27/2011 32

Business Blueprint Portfolio Analyzer is a component to calculate and monitor the yields on financial assets. It is designed to be used to measure the profits from investments from different perspectives. The calculations are based on the structure of the portfolio maintained in the portfolio hierarchy based on the characteristics. For ex: Portfolio hierarchy can be based on sector, country or based on Product type. Portfolio Analyzer contains various methods for calculating the time-weighted rate of return (TWRR) and the money-weighted rate of return (MWRR). Time-weighted rate of return(TWRR) The time-weighted rate of return describes the returns that result from the actions of the portfolio manager. The rate of return is calculated net of the effect of the deposits into or withdrawals from the portfolio. Moneyweighted rate of return(MWRR) It is defined as rate of return, which used to calculate the interest rate of the portfolio, including all incoming and outgoing cash flows. This gives the exact market value of the portfolio at the end of the analysis period. Naming Convention The following would be the number range for Security ID and Security transactions for the following Company codes Company code 1000 1100 1200 Number Range for Security ID Number 01 From Number 100001 To Number 200000 Int/Ext Internal Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

Number Range for Securities transactions Product Type 01A ZPE ZNP ZNE ZPF ZDP ZAM ZTP Flow Chart Number Range 08 09 10 11 12 13 14 15 From Number 800001 900001 1000001 1100001 1200001 1300001 1400001 1500001 To Number 900000 1000000 1100000 1200000 1300000 1400000 1500000 1600000 Int/Ext Internal Internal Internal Internal Internal Internal Internal Internal

12/27/2011 33

Business Blueprint

Business Process flow Job Description The event provides the details/process to capture the Financial Transactions of Securities in Treasury and Risk Management and also highlight the key fields which are required for entering Financial transactions. The following are the financial instruments used to capture under Securities in SAP Treasury and Risk Management. Product Type 01A- Stocks for Shares(Listed) Product Type ZPE for Public Equity Product Type ZNP Non-Public Equity(Private Equity cost method) Product Type ZNE Non-Public Equity(Private Equity Equity method) Product Type ZPF Fund Product Type ZTP Trading Portfolio Product Type ZDP Discretionary Portfolio Product Type - ZAM Application Money/ Advance towards Investment The following are the prerequisites for recording financial transactions under securities 12/27/2011 34

Business Blueprint a. Business Partner Counter Party, Issuer and Depository Bank b. Security ID The ID number is used to uniquely identify a security or the category of Investment. c. Security Account It is a unit used for position management and valuation of financial instrument. XXXX XXXX Financial Entries for Securities Investment (Stocks/Fund) Account Dr To Cash Account Cr (When acquisition of New investment is made )

Cash Account Dr XXXX Unrealized gain Dr XXXX To Investment (Stocks/ Fund) Cr To Profit / Loss on Investment ( OR ) I/S Cr (When Sale of Investment takes place) Dividend Receivable Dr Deferred Credit Cr ( When Declaration of Cash Dividends) Cash Account Dr Dividend Receivable Cr (When Collection of Cash dividends) XXXX

XXXX XXXX

XXXX XXXX XXXX

Business Process flow for financial transactions Securities Step No. Step Name 10 Creation of Security ID Process step description Delivered By

Security ID would be created in SAP TRM by the Investment FWZZ department TRS_SEC_ACC

20

30

Creation of Security Account would be created in SAP by the Security Account Investment department . Creation of Security transactions would be created in SAP by the Security Investment department Transaction Settlement of Security Transaction Security Transaction posting to FI Security transaction would be settled in SAP TRM before posting to finance. The purpose of settlement is to check the accuracy of the transaction and to authorize it in SAP TRM. Security transaction will be posted to Finance from SAP TRM

TS01

40

FTR_EDIT

50

TBB1

PS Note: Transactions cannot be modified once they have been posted to Finance. Changes to existing organization There is no existing system defined in the organisation. At present the following Company codes Company code Company Name

12/27/2011 35

Business Blueprint 1000 1100 1200 Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

are using Microsoft office to maintain the record of transactions. Treasury department should be able to view real time Treasury positions, calculations and reports. Description of improvements System provides the facility of updating market data of securities to update the book value of the security market price and to take decision on investment Portfolio accurately. Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit Description 1 Product Types

Gap resolution

There are no standard product types to suit the requirements Create new of the following Company codes Product types ZPE, ZNP, ZNE Company code Company Name ZPF, ZTP, ZDP 1000 Abdul Kader Al Muhaidib & Sons Co and ZAM. 1100 1200 Al Muhaidib Holding Co Al Muhaidib Development Co

To meet the requirements of the above mentioned company codes the following Customized product types ZPE, ZNP, ZPF, ZTP, ZDP and ZAM are to be created.

System configuration considerations 1. 2. 3. 4. Configuration of customized product types ZPE, ZNP, ZNE,ZPF, ZTP, ZDP and ZAM Number range for the transactions product wise.( refer above mentioned step: Naming convention) Number range for Security ID.( refer above mentioned step: Explanation of events and functions) Account determination for Positions and post flows to Finance.

Integration Considerations Sr. No. Module Description of integration FI Integration to FI will be established through Account determination in TRM

Reporting Considerations Position of Financial instruments for Product Types on Periodic basis. 12/27/2011 36

Business Blueprint TPM 13 Fixed and Schedule flows for product type TPM 12 Fixed flows (Posted flows to Finance) for Product type TPM1 Valuation of Financial instrument. Authorization and user roles Roles for Front office to make transaction of financial instrument(FTR_CREATE) Back office to validate and settle the transaction(FTR_EDIT) and Accounting for posting the transaction to Finance.(TBB1).

1.1.3.4 Derivatives Requirements / expectations The following are the financial instruments AKMS wants to capture under Derivatives in SAP Treasury and Risk Management. The Scope of Foreign Exchange transactions are applicable for AKMS only. Product Type 62A for Interest Rate Swap (IRS) Transaction Type 300 Payer 301 Recipient

General explanations Derivatives play an important role in interest and currency management.Derivatives are dependent on variable financial market values (such as reference interest rates), SAP Treasury and Risk Management Gives access to a real-time data feed, which provides up-to-the-minute market price information. The counterparty paying the fixed rate of interest is called the "payer" (while receiving the floating rate), and the counterparty receiving the fixed rate is called the "receiver" (while paying the floating rate). Naming Convention The following would be the number range for Derivative transactions for AKMS. Number Range for Derivative transactions Product Type 62A Flow Chart Number 16 From Number 1600001 To Number 1700000 Int/Ext Internal

12/27/2011 37

Business Blueprint

Business Process flow Job Description The event provides the details/process to capture the Financial Transactions of Derivatives in Treasury and Risk Management and also highlight the key fields which are required for entering Financial transactions. The following are the financial instruments AKMS(company code:1000) wants to capture under Foreign Exchange in SAP Treasury and Risk Management. Product Type 62A for Interest Rate Swap (IRS) Transaction Type 300 Payer - 301 Receiver Financial Entries for Derivatives(Interest Rate Swap) Fixed Interest Dr XXXX To Bank Account Cr XXXX (When Fixed interest is paid ) Bank Account Dr XXXX To Interest Receivable Cr XXXX (When floating interest is received)

Business Process flow for Derivatives Step No. Step Name 10 Process step description Delivered By

IRS TransactionInterest Rate Instrument (IRS) transactions would be created TO01 (or ) Creation in SAP by the Treasury department FTR_CREATE IRS TransactionIRS transaction would be settled in SAP Treasury before Settlement posting to finance. The purpose of settlement is to check the accuracy of the transaction and to authorize it in SAP Treasury IRS transaction Interest Rate Swap will be posted to Finance from SAP posting to FI FTR_EDIT

20

30

TBB1

12/27/2011 38

Business Blueprint Treasury PS Note: Transactions cannot be modified once they have been posted to Finance. 40 IRS Premature Settlement /closure IRS Premature settlement/ closure will be carried out in SAP FTR_EDIT Treasury

Changes to existing organization There is no existing system defined in the organisation. At present AKMS is not using/exercising the financial instrument Interest Rate Swap. Treasury department should be able to view real time Treasury positions, calculations and reports.

Description of improvements Product Type Interest Rate swap provides the interest calculations of payer and receiver (i.e Outgoing and incoming) and helps to take timely decision on payment of interest. Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit Description

Gap resolution

None System configuration considerations 1.Creation of number ranges for Derivative transactions.( refer above mentioned step: Naming Convention) 2. Reference rate of interest which helps timely update of variable interest rates and calculation of interest accordingly. Integration Considerations Sr. No. Module Description of integration FI Integration to FI will be established through Account determination in TRM

Reporting Considerations Position of Financial instruments for Product Types on Periodic basis. TPM 13 Fixed and Schedule flows for product type TPM 12 Fixed flows (Posted flows to Finance) for Product type TPM1 Valuation of Financial instrument.

12/27/2011 39

Business Blueprint Authorization and user roles Roles for Front office to make transaction of financial instrument (FTR_CREATE) Back office to validate and settle the transaction(FTR_EDIT) and Accounting for posting the transaction to Finance.(TBB1).

1.1.3.5 Process of CLM Business Processes for CLM Requirements / expectations The following Company codes Company code 1000 1100 1200

Company Name Abdul Kader Al Muhaidib & Sons Co Al Muhaidib Holding Co Al Muhaidib Development Co

wants to view its cash positions at various levels to enable them to interpret their cash positions and forecasting easily thus enabling them to take timely and accurate decisions.

General explanations The main purpose of SAP Cash Management is to monitor cash flows and to ensure that an entity has sufficient liquidity to cover various obligations. SAP Cash Management uses the cash position to reflect movements in bank accounts, while movements in the sub-ledger accounts (AR & AP) are represented using the liquidity forecast. SAP Cash Management is integrated with a range of other SAP components. For example, the liquidity forecast in a medium to long term liquidity trend integrates expected incoming and outgoing payments in financial accounting, purchase and sales. Naming Convention None Flow Chart The process of Cash flow and Liquidity forecast of CLM is defined below :

12/27/2011 40

Business Blueprint

Business Process flow Job Description Incoming and outgoing payments that are not transferred to the SAP Cash Management System via actual posting can be entered manually in the planning through Memo record. There are two types of Memo Records: Payment Advices relevant for Cash Position - These are advices of confirmed nature and would appear in the Cash Position reports. The Planning levels for Payment Advice updation would be separately configured. Planned Items These are the items which are forecasted and appear in the liquidity forecast report. The planning levels for such planned memo records would be separately configured. Standard Planning Type MP Noted Items would be used for capturing any Memo Item. Planning group used would be ZZ Unconfirmed Inflow/Outflow Following important fields are entered while entering of Memo Records. The details would be covered during user training:Value Date Account Name Currency Amount Assignment Business Process flow for Cash and Liquidity Management. Step No. Step Name 10 20 Process step description Delivered By

Creation of Memo Memo record would be created for Cash position or LiquidityFF 63 record forecast Change MemoMemo records (entered for confirmed inflow/outflow) can be FF6A record (Confirmededited.

12/27/2011 41

Business Blueprint for inflow/outflow)The same transaction can also be used as a report for Using List viewing the list of memo records

30

Change MemoThe Memo records (entered for planned data) can be edited FF6B Records (PlannedThe same transaction can also be used as a report for Data) Using List viewing the list of memo records Report The two important reports are: Cash Position (FF7A) The memo records in nature of confirmed inflow/outflow will impact the Cash Position Reports. The listing of such records can also be viewed in FF6A report as written above in the step no. 20 Liquidity Forecasting (FF7B) - The memo records in nature of planned item will impact the Liquidity Forecast report. The listing of such records can also be viewed in FF6B report as written above in the step no. 30

40

Changes to existing organization There is no existing system defined in the organisation. At present the above mentioned Company codes would be using Microsoft office to generate reports for Cash Management. Using CLM Treasury department will be able to view the Cash position for all the banks and also able to generate Liquidity forecast at any given point of time.

Description of improvements CLM provides the option of generating the Liquidity forecast on daily, weekly and monthly at any given point of time taking into consideration of receivables and payables. Description of functional deficits and Approaches to covering functional deficits Sr. No. Gap/ Deficit Description None

Gap resolution

System configuration considerations 1. Maintenance of Planning levels for Cash position. 2. Maintenance of Planning groups for Liquidity forecast.

Integration Considerations Sr. No. Module Description of integration FI 12/27/2011 42 Integration to FI will be established through General ledger accounts and Sub ledger accounts.

Business Blueprint

Reporting Considerations Cash position (FF7A) and Liquidity forecast (FF7B). Custom report for Loan movement and LC movement will be developed as per the requirements. Authorization and user roles Authorization for Planning Memo records (FF63), Cash Position (FF7A) and Liquidity forecast (FF7B) will be provided to Fund Manager.

1.1.3.6 WRICEF During the workshops the following Gaps are identified and which are accomplished using RICEFWs

12/27/2011 43