Mantas Interface User Manual
Contents
1. 0 02000 0 000000000000 2 3 2 2 4 Maintaining Frequency Type 2 7 2 2 5 Maintaining Branch Parameters 2 00000000000000000000000 2 8 2 2 6 Specifying the Data Extraction Details 2 9 2 2 7 8 2 10 2 3 Capturing Country Information 2 2 10 2 31 Maintaining Customer 2222 040000000000000000000000000 2 11 2 3 2 Maintaining Ultimate Beneficiary 22 0 2 11 2 3 3 Instrument Transaction 22 0022 1 000000 0 010000000000 2 11 2 3 4 Funds Transfer Transaction Details 2 11 2 3 5 Clearing Transaction 2 2 2 11 2 36 TD Redemption Renewal 205002009990 5992 2 2 11 2 37 TransSaction 5 2 2 11 2 38 Settlement 2 12 2 4 Performing the Data 2 12 2 4 1 Reterence 2 12 2 4 2 22. screen You can invoke this screen by typing IFDMTSFU in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Mantas Response Upload Received Date You can specify the following details Received Date The system displays the global application date However you can modify it Click Upload button to upload the response of the risk details The response will be stored as two files customer and account Note The file names for upload should be as given below CustomerSupplementalAttribute txt AccountSupplementalAttribute txt The folder name should be the date for which the above files are uploaded If the file contains any invalid records then it will be moved to the error log table IFTB_ERROR_LOG and the valid records will be moved to the respective data stores maintained and this is applicable for both customer and account Viewing the Risk Score The response from Mantas pertaining to the customer number and its related account can be viewed in the Risk Score screen You can invoke this screen by typing IFDMTSRD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Se ORACLE Data Extraction Monitor Branch Code LBL_EXTRACTION_BRN_CODE 10f1 O Branch Status o Click History of Customer button to view the risk history details of the customer and
3. Needed for the Country and AccountCustomerRole files All the other files will the frequency set as Daily Extract Type Specify the type of extract for the handoff indicating whether a file is to be sent as Full or Incremental For files with frequency specified as As needed the extraction type will always be Full A Full extraction takes place only if any modification happens to the data If there are no modifications for a day no file will be handed off for that day For all other frequencies an empty file would be handed off for the day if there is no data for hand off Maintaining Branch Parameters Every branch of a bank extracts the reference and the transaction data for itself and writes the data into a data store as one of its mandatory pre EOD programs Only one branch will be designated to write the hand off file on behalf of all the other branches and itself for a particular Mantas code The Extraction and the File Write roles can be assigned to the branches using the Mantas Branch Parameters screen You can invoke the Mantas Branch Parameters screen by typing IFDMTSBR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button en ORACLE 2 2 6 Branch Parameters Maintenance Branch Code Mantas Code Description File Write Role Date Time Checker Date Time Mod No Record Status Authorization Status You can
4. click History of Accounts button to view the risk history details of the accounts SA ORACLE IFDMTSBR 2 8 IFDMTSEM 2 9 IFDMTSFH 2 7 2 3 4 Function ID Glossary ORACLE
5. extraction role once the branch is saved using the branch parameter screen Further one of the branches will be given the file write role Maintaining UDF s Specific attributes related to a Customer Account and Oracle FLEXCUBE User need to be provided to Mantas in the corresponding files The following User defined fields will be maintained for Account Customer and Oracle FLEXCUBE user e MNTS_BUS_ DOMAIN which indicates the Mantas business domain e JURISDICTION which indicates the Mantas jurisdiction The extraction will pick up these values from the Customer Account and User maintenances and provide the same in the corresponding field for the relevant file Capturing Country Information The country location involved in a transaction is crucial for Mantas to analyze the transactions The following input screens in Oracle FLEXCUBE have been modified to capture the country information 210 ORACLE 2 3 1 2 3 2 2 3 3 2 3 4 2 3 5 2 3 6 2 3 7 Note This information capture is only for Mantas handoffs and will not have any other impact Maintaining Customer Account You need to capture the country information of the customer account in the Customer Accounts Maintenance screen For more details refer to the section Maintaining Customer Accounts in the Core Entities User Manual Maintaining Ultimate Beneficiary Details You need to capture the country location of the
6. list of all the reference data files Option You can specify whether you want to include or exclude a particular data file for the data hand off 2 2 3 2 Specifying Transaction Data File Parameters Transaction data file parameterization provides the bank an option to choose the type of transactions to be included in the transaction hand off files 2 5 ORACLE 2 2 3 3 Mantas File Parameters Bank Code Source ID Reference Data Transaction Datal Change Log Transaction Data 10f1 E Transaction Type oO Maker Date Time Checker Date Time Record Status Authorization Status You can specify the following details here Transaction Type The different transaction types with the corresponding modules which qualify for hand off are listed out Option You can specify whether you want to include or exclude a particular transaction type for the hand off Specifying Change Log File Parameters Change Log file consists of modified data of specific fields relating only to Account Account Address Customer and Account to Customer entities Change Log parameterization provides the bank an option to include or exclude an entity in the Change Log hand off file 26 ORACLE 2 2 4 Mantas File Parameters Bank Code Source ID Reference Data Transaction Data Change Log 10f1 a o Page Number Maker Date Time Checker Date Time Record Status Auth
7. maintain the file parameters for the following types of data e Reference Data file parameters e Transaction Data file parameters e Change Log file parameters These parameters can be captured using the Mantas File Parameters screen You can invoke the Mantas File Parameters screen by typing IFDMTSFFP the field at the top right corner of the Application tool bar and clicking the adjoining arrow button oe ORACLE Mantas File Parameters Bank Code Source ID Reference Data Change Log Transaction Data 10f1 Transaction Type Date Time Date Time Mod No Record Status Authorization Status You can capture the following details here Bank Code The Bank Code will be defaulted from the Bank maintenance Source ID Specify the Source ID which is a unique identifier representing the Oracle FLEXCUBE instance which hands off data to Mantas Note The Source ID can be only three characters long 2 2 3 1 Specifying Reference Data File Parameters Reference data file parameterization provides the bank an option to include or exclude a particular data file in the data hand off 2 4 ORACLE Mantas file Paramei amp s Bank Code Source ID HR 2 Data Change Log Reference Data 10f1 D File Name o Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can capture the following details here File Name This provides a
8. screens e Customer Account Maintenance e Ultimate Beneficiaries e Instrument Transaction Details e Funds Transfer Contract Details e Clearing Transaction Input e TD Redemption Renewal e Transaction Input e Settlement Instructions Each of these maintenances is discussed in detail in the following sections of this Manual Maintaining Mantas Installation Parameters You can capture the details specific to the Mantas installation in the Mantas Code Parameters screen a ORACLE Mantas Code Parameters Mantas Code Description Base Currency File Write Batch Name File Write Destination Rate Code Rate Code Type Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can capture the following details in this screen Mantas Code Specify the Mantas Code which identifies the Mantas instance to which the Oracle FLEXCUBE physical instance is mapped Description Specify the description for the Mantas installation File Write Destination Specify the pre defined destination where Oracle FLEXCUBE will place the hand off file Mantas will pick up the hand off file from this destination File Write Batch Name Specify a pre defined name for the file batch which will be a part of the hand off file name Note This pre defined string should be unique across all Mantas codes to which the bank is handing off files Base Currency Select the base curr
9. 13 24 3 2 13 2 4 4 Extracting the Batch 2 2 2 2 0 0000000 0000000000000000 2 13 2 4 5 Writing the Batch Data oinarria issiran eara iaaii i 2 13 2 5 File Naming Convention and File 2 13 256 2 14 Know Your Customer 21111333 3 1 3 1 a ind 3 1 21 7 3 1 3 1 2 Maintaining Mantas RESPONSE 2 0000000 00000000004000000 3 1 3 1 3 Viewing the Summary Details of Mantas Response Maintenance 3 2 3 1 4 Uploading Mantas Response 3 3 3 1 5 Viewing the RISK 5 1 2 2 1 2 2 2 2000000000000000000 3 3 Function ID Glossary oicaces foc tcccacsceuceteedhssscccscattucccuedscescecinpaceeachearavacevaccased 4 1 1 1 1 2 1 3 1 4 Introduction 1 Preface This document is designed to help you acquaint with the enhancements and changes provided in Oracle FLEXCUBE to interact with Mantas an AML application This manual explains t
10. D format e BatchName a predefined Mantas value which will be picked from the Mantas Code maintenance and used for naming all the files generated for that Mantas Code 2 19 ORACLE e n indicates the sequence number of the data file When there are multiple instances created for a data file the sequence number would indicate the number of the data file Example The files generated on 30 March 2007 will be named as follows e AccountBalance_20070330_ lt BatchName gt _1 DAT e AccountCustomerRole_20070330_ lt BatchName gt _1 DAT e 20070330 lt gt _1 2 66 Data Types Table given below explains the various data types in the data hand off Data Type Description Text These fields would be as per the length specified for the field Numeric Amounts These fields will contain digits 0 9 and a decimal The number of digits following the decimal separator would be driven by the currency maintenance of Oracle FLEXCUBE Numbers without decimals These fields will contain only digits 0 9 Numbers with decimals These are number fields which are not amounts e g exchange rates These fields will contain only digits 0 9 and a decimal separator Date Date fields will be represented in the format YYYYMMDD For instance 3041 March 2007 would be represented as 20070330 28 ORACLE 3 Know Your Customer 3 1 Introducti
11. LE 2 3 8 2 4 2 4 1 For more details refer to the section Capturing the details of payment collection transactions in the Payments and Collections User Manual Settlement Instructions You need to capture the country location of the following parties in the Settlement Instructions screen e Intermediary e Intermediary Reimbursement Institution Receiver s Correspondent e Account with Institution e Receiving Intermediary e Beneficiary Institution e Beneficiary Institution for Cover For more details refer to the section Capturing Settlement Preferences for a Customer the Settlements User Manual Performing the Data Hand Off The extraction of the data at the various branches and the writing of the hand off file data are handled through batch processes The data files handed off to Mantas can be broadly classified as follows e Reference Data e Transaction Data e Change Log Reference Data Reference Data consists of the details related to the following entities e Account the details of all the accounts of type Nostro Savings Current and Deposits e AccountAddress the address details associated with an account e AccountToCorrespondent the details of all the accounts of type Nostro and Current related to banks only AccountBalance the account number the current available balance e AccountCustomerRole the different roles of a customer which can be prima
12. ORACLE Mantas Interface User Guide Oracle FLEXCUBE Universal Banking Release 12 0 3 0 0 Part No E53393 01 April 2014 Mantas Interface User Guide April 2014 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon East Mumbai Maharashtra 400 063 India Worldwide Inquiries Phone 91 22 6718 3000 Fax 91 22 6718 3001 www oracle com financialservices Copyright 2007 2014 Oracle and or its affiliates All rights reserved Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerou
13. ary Processing ATM POS Transactions e Liquidity Management 13 ORACLE 2 1 2 2 2 2 1 2 Oracle FLEXCUBE Mantas Integration Introduction Money Laundering is the process of moving illicit funds through the banking system so as to disguise the origin of the funds Anti money laundering applications based on the data from the banking system tracks and identifies patterns in the banking transactions to trace any possible fraud or money laundering involved AML systems also attempt to detect money laundering activities by analyzing the changes in specific customer account information and the transactions performed on an account Mantas is an AML system which monitors the money flowing into and out of the banking system to detect possible money laundering An interface between Oracle FLEXCUBE and Mantas enables data hand off from Oracle FLEXCUBE to Mantas To perform AML monitoring Mantas requires reference data relating to the customer accounts etc as well as transaction details related to customer accounts Maintaining Details for Data Hand Off to Mantas You need to maintain the following details to enable the data hand off to Mantas e Mantas Installation parameters e Mantas Data file parameters e Frequency and Hand off type parameters e Branch parameters e UDF s related to customer account and user In addition to the above maintenances you need to capture the country information in the following
14. branch of the bank This happens during pre EOD where both reference and transaction data for the branch is extracted as per the Branch parameterization and the Frequency and hand off type parameterization The extracted data is written to a common data store For data extraction IFMNTSEX batch needs to be maintained at post EOFI level in the function id EIDMANPR Note The extraction should be maintained as a mandatory program as part of the branch s End of Cycle activity Writing the Batch Data The branch designated as the File Write branch for a particular Mantas code also will extract data for itself during pre EOD and then write the hand off file to the File Write destination specified in the Mantas Code maintenance The files would be picked up by Mantas from this location For file write IFMNTFWR batch needs to be maintained at post EOFI level the function id EIDMANPR Note The File Write program should be maintained as a mandatory program as part of the file write branch s End of Cycle activity File Naming Convention and File Formats The hand off file name will be generated as lt Datafile gt _ lt FileWriteDate YYYYMMDD gt _ lt BatchName gt _ lt n gt DAT 1 Datafile indicates the name of the data file for example Customer Account AccountBalance etc e FileWriteDate indicates the date on which the data was written to the hand off file The date is specified in the YYYYMMD
15. ency into which the amount involved in a transaction has to be converted to be sent to the hand off files Note There can be only one base currency associated with a Mantas Code 22 ORACLE 2 2 2 2 2 3 Rate Code The rate codes are maintained by Oracle FLEXCUBE for a base and reporting currency pair Select the Rate Code to be used for the base and reporting currency conversions Rate Code Type Select the Rate Code Type that specifies if it is a Buy rate Sell rate or Mid rate This will also be used in the base and reporting currency conversions Viewing the Mantas Code Parameter Details You can view the Mantas code parameter details in Mantas Code Parameters Summary screen To invoke this screen type IFSMTSCDI in the field at the top right corner of the Application tool bar and click the adjoining arrow button Summary Authorization Status Record Status Mantas Code at File Write Batch Name Advanced Search Records perpage 15 1 041 Authorization Status Record Status Mantas Code Description Base Currency File Write Batch Name File Write 1 In this screen you can query based on any combination of the following fields e Authorization Status e Record Status e Mantas Code e File Write Batch Name After specifying the parameters for the query click Search The system displays all the records matching the parameters specified Maintaining Data File Parameters You can
16. es will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services Contents Preface Sones eS Sa nee es Re 1 1 pp 1 1 7 2 1 1 1 3 Documentation 1 1 TA eda reenact anette 1 1 1 5 Acronyms and 1 2 126 erat thie ae Me ene die 1 2 1 7 1 2 18 Related Documents 202 11 00 1 1 2 Oracle FLEXCUBE Mantas Integration 22 1 2 1 2141 sIMMOOUCHION tae tad teeta 2 1 22 Maintaining Details for Data Hand Off to 2 1 2 2 1 Maintaining Mantas Installation 2 1 2 2 2 Viewing the Mantas Code Parameter 2 3 2 2 3 Maintaining Data File Parameters
17. he various maintenances required for the exchange of data between Oracle FLEXCUBE and Mantas to track money laundering activities It also gives you an insight into the type of data to be transferred to Mantas to perform AML activities Besides this User Manual while maintaining the interface related details you can invoke the context sensitive help available for each field This help encapsulates the purpose of each field within screen Placing the cursor on the relevant field and striking the lt F1 gt key on the keyboard can obtain information specific to a particular field Audience This manual is intended for the following User User Roles Role Function Back office data entry Clerks Input functions for maintenance related to the interface Back office Managers Offic ers Authorization functions Documentation Accessibility For information about Oracle s commitment to accessibility visit the Oracle Accessibility Program website at http Avww oracle com pls topic lookup ctx acc amp id docacc Organization This manual is organized as follows Chapter 1 About this Manual gives information on the intended audience It also lists the various chapters covered in this User Manual Oracle FLEXCUBE Mantas Integration gives an insight about Man Chapter 2 tas integration and the type of data to be transferred to Mantas to perform AML activities KYC Know Your Customer expla
18. his screen by typing IFDMTSRWM the field at the top right corner of the Application tool bar and clicking the adjoining arrow button sl ORACLE Mantas Response Maintenance Branch Code LBL_FILERD_DEST Maker Date Time Checker Date Time Record Status Authorization Status You can specify the following details Branch Code Specify the branch code of the bank to read the Mantas response about the customer risk Read Destination Specify the location where the response file has to be placed 3 1 3 Viewing the Summary Details of Mantas Response Maintenance You can view the summary details of the Mantas response maintenance in the Mantas Response Maintenance Summary screen To invoke this screen type IFSMTSRWM the field at the top right corner of the Application tool bar and click the adjoining arrow button Summary Authorization Status Record Status v Branch Code 28 Advanced Search 1 041 Authorization Status Record Status Branch Code LBL_FILERD_DEST MakerID Maker Date Stamp Checkerld In this screen you can query based on any combination of the following fields e Authorization Status e Record Status e Branch Code 92 ORACLE 3 1 5 After specifying the parameters for the query click Search The system displays all the records matching the parameters specified Uploading Mantas Response Mantas response can be uploaded using the Mantas Response Upload
19. ins about Mantas KYC solution Chapter 3 which helps to identify customer risk in all lifecycle stages of the cus tomer Chapter 4 Function ID Glossary has alphabetical listing of Function Screen ID s used in the module with page references for quick navigation 1 1 ORACLE 1 5 1 6 1 7 1 8 Acronyms and Abbreviations Abbreviation Description System Unless and otherwise specified it shall always refer to Oracle FLEX CUBE Corporate FCC system AML Anti Money Laundering UDF User Defined Field BIC Bank Identification Code Organization This manual is organized into the following chapters Chapter 1 Oracle FLEXCUBE Mantas Integration talks about the maintenances required for exchanging data to Mantas the hand off files and batch pro cess for extracting and writing the hand off data Chapter 2 Annexure explains the file formats and the data types used in the data hand off Glossary of Icons Icons Function Exit Add row Delete row Option List Related Documents You may need to refer to any or all of the User Manuals while working on the Mantas Integration interface module e CASA e Procedures e Core Entities e Clearing e Funds Transfer e Settlements e Payments and Collections e Standing Instructions e Term Deposits e Utility Payment tg ORACLE e Sal
20. on Oracle Mantas KYC solution helps you to identify customer risk in all lifecycle stages of the customer Oracle FLEXCUBE hands off data pertaining to the customer and its accounts to Oracle Mantas The customer risks indentified can be integrated with third party source systems like Watch Lists Negative News Providers and Identity Verification Vendors The Oracle Mantas KYC solution comprehends the risk of the customer at the following stages of the lifecycle Real time account on boarding risk assessing the customer risk at the time of account opening e Default Account review assessing the risk of new customers e Periodic review reviewing the risk of the customer at regular intervals e Accelerated review assessing the risk based on i alerts received from AML ii the change in controlling role in accounts 3 1 1 File Formats The following conventions are used while generating the data files e Each file will be a text file with each field delimited by Fields with blank values will be recognized by successive delimiters e There will be a delimiter at the end of a record e Each record will be on a new line Refer Savings Account Creation and Current Account Creation Process Document User Manuals for more information on KYC process flow 3 1 2 Maintaining Mantas Response You can read the response of the customer risk from Mantas in the Mantas Response Maintenance screen You can invoke t
21. orization Status You can specify the following details here Entity The list of the entities which qualify for hand off are displayed Option You can specify whether you want to include or exclude a particular entity for the hand off Maintaining Frequency and Hand Off Type Parameters Frequency and hand off type parameterization provides the bank the option to choose the frequency and the type of hand off This option is available only for the hand off files related to Reference Data Note Frequency and or hand off type parameterization will not be available for Change Log and Transaction hand off files You can specify these details in the Mantas Handoff Parameters screen You can invoke the Mantas Handoff Parameters screen by typing IFDMTSFH in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 27 ORACLE 2 2 5 Bank Code Description Mantas Handoff parameters 101 o File Name Frequency Extract Type 0 Date Time Checker Date Time Record Status Authorization Status You can capture the following details in this screen Bank Code The Bank Code is defaulted from the Bank maintenance File Name This is the name of the hand off data file All the hand off files related to Reference data type are displayed Frequency This is the handoff frequency type The frequency value will be displayed as As
22. ry secondary partner etc associated with an account e AccountToCustomer the specific role a customer plays in an account This will be picked up from linked entities captured at account level e Country the country code and its description as maintained in Oracle FLEXCUBE e Customer the details related to the customer e MatchedEntity outcome of an SDN match e WatchList single record file which maps to Oracle FLEXCUBE s watchlist e WatchListEntry list of the Specially Designated Nationals which will be picked up from SDN maintenance e Employee the details related to the Oracle FLEXCUBE user 2 12 ORACLE 2 4 2 2 4 3 2 4 4 2 4 5 2 5 Transaction Data Transaction data consists of details related to the following e Front office transactions which involve any movement of funds into or out of the financial institution and the reversed front office transactions e Front office transaction parties e Back office transactions which involve any internal movement of funds within the financial institution and reversed back office transactions Change Log Change log consists of the details of the changes in specific fields related to Account Account Address Customer and Account to Customer entities Any modification happening to these fields needs to be sent as a part of the change log file Extracting the Batch Data The data extraction routines will run on the Oracle FLEXCUBE database for each
23. s applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate failsafe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing This software or hardware and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliat
24. specify the following details in this screen Branch Code The Branch Code will be defaulted from the logged in branch Description The description for the branch is also defaulted from the Branch maintenance File Write Role Check this option to specify that file write role should be designated to write the extracted data on behalf of all the other branches and itself Mantas Code Select the Mantas Code corresponding to the branch from the option list provided Specifying the Data Extraction Details In the Data Extraction Monitor screen you can specify details pertaining to data extraction To invoke this screen type IFDMTSEM in the field at the top right corner of the Application tool bar and click the adjoining arrow button 229 ORACLE 2 2 7 2 3 Data Extraction Monitor Branch Code LBL_EXTRACTION_BRN_CODE 104 C Branch Status o You can specify the following details Branch Code Select the branch code which has got the file write role from the list of options Click Refresh button to view the extraction status pertaining to the branch The status will be N which indicates the completed and completed status of data extraction Note Data Extraction Monitor screen is accessible only to the branch which has file write role and an error message is displayed if it is accessed from other branches By default all the branches will have
25. ultimate beneficiary in the Ultimate Beneficiaries screen For more details refer to the section Maintaining ultimate beneficiary details in the Settlements User Manual Instrument Transaction Details You need to capture the country location of the remitter in the Instrument Transaction Details screen For more details refer to the section Entering Instrument Transactions in the CASA User Manual Funds Transfer Transaction Details You need to capture the country location of the ordering customer the ultimate beneficiary and the account with institution in the Funds Transfer Contract Details screen For more details refer to the section Invoking the FT Contract Detailed Screen in the Funds Transfer User Manual Clearing Transaction Details You need to capture the country location of the remitter and the beneficiary in the Clearing Transaction Input screen For more details refer to the section Entering Clearing Transactions in the Clearing User Manual TD Redemption Renewal You need to capture the country location where a check is issued in the TD Redemption Renewal screen For more details refer to the section Maintaining details for redeeming term deposits in the Core Entities User Manual PC Transaction Input You need to capture the country location of the customer and the counterparty in the PC Transaction Input screen 211 ORAC
Download Pdf Manuals
Related Search