Oracle银行财务管理系统解决方案2010
Oracle FLEXCUBE 银行业解决方案文档管理系统接口用户指南说明书
Document Management System Interface User Guide Oracle FLEXCUBE Universal Banking Release 14.5.0.0.0Part No. F42208-01May 2021Document Management System Interface User GuideOracle Financial Services Software LimitedOracle ParkOff Western Express HighwayGoregaon (East)Mumbai, Maharashtra 400 063IndiaWorldwide Inquiries:Phone: +91 22 6718 3000Fax: +91 22 6718 3001https:///industries/financial-services/index.htmlCopyright © 2007, 2021, 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 dangerous 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 affiliates 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 1. Preface ......................................................................................................1-11.1 Introduction.............................................................................................................. 1-11.2 Audience.................................................................................................................. 1-11.3 Documentation Accessibility.................................................................................... 1-11.4 Organization............................................................................................................ 1-11.5 Acronyms and Abbreviations................................................................................... 1-11.6 Organization............................................................................................................ 1-11.7 Glossary of Icons..................................................................................................... 1-21.8 Related Documents................................................................................................. 1-22. Oracle FLEXCUBE - DMS Integration ....................................................2-12.1 Oracle FLEXCUBE and external DMS.................................................................... 2-12.1.1 Integrating Oracle FLEXCUBE with external DMS..................................... 2-12.1.2 Adding a Document to DMS....................................................................... 2-12.1.3 Viewing the Document Indexed in the DMS............................................... 2-22.1.4 Deleting a Document Indexed in DMS....................................................... 2-31. Preface1.1 IntroductionThis manual is designed to help acquaint you with the integration of Oracle FLEXCUBE and Oracle FLEXCUBE Document Management System Interface.1.2 AudienceThis manual is intended for the following User/User Roles:1.3 Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at /pls/topic/lookup?ctx=acc&id=docacc.1.4 OrganizationThis manual is organized as follows:1.5 Acronyms and Abbreviations1.6 OrganizationThis document talks about the required maintenance and further processing of data transfer between Oracle FLEXCUBE and DMS.RoleFunction Back office data entry ClerksInput functions for maintenances Back office Managers/Officers Authorization functions ChapterDescription Chapter 1About this Manual gives information on the intended audience. Italso lists the various chapters covered in this User Manual.Chapter 2Oracle FLEXCUBE - DMS Integration explains about Oracle IPMwhich is an external Document Management System with whichOracle FLEXCUBE integrates for document processes.AbbreviationDescription DMSDocument Management System IPM Imaging and Process Management1.7 Glossary of IconsThis User Manual may refer to all or some of the following icons.1.8 Related DocumentsYou can refer to the following documents:Procedures User Manual IconsFunction ExitAdd rowDelete rowOption List2. Oracle FLEXCUBE - DMS IntegrationOracle IPM is an external Document Management System with which Oracle FLEXCUBEintegrates for document processes. Oracle IPM provides image scanning and businessprocess management capabilities for enterprise applications. Oracle IPM is integrated withOracle FLEXCUBE to support the existing Oracle FLEXCUBE DMS.The integration between Oracle FLEXCUBE and Document Management Systems occursonly in process flows. Therefore, not all modules of Oracle FLEXCUBE are utilizing theservices offered by the integration. The user interface in FLEXCUBE makes standard requestto the underlying infrastructure and Oracle FLEXCUBE infrastructure would interact with theDMS and supply the result to user interface in same manner.This chapter includes the following section:● Section 2.1, "Oracle FLEXCUBE and external DMS"2.1 Oracle FLEXCUBE and external DMSThis section contains the following topics:● Section 2.1.1, "Integrating Oracle FLEXCUBE with external DMS"● Section 2.1.2, "Adding a Document to DMS"● Section 2.1.3, "Viewing the Document Indexed in the DMS"● Section 2.1.4, "Deleting a Document Indexed in DMS"2.1.1 Integrating Oracle FLEXCUBE with external DMSYou can integrate Oracle FLEXCUBE with Oracle IPM. FLEXCUBE will intergrate/interactwith one DMS provider at a given time and currently it is integrated with Oracle IPM only.Adapters are kind of service provider which provides the operations as per the OracleFLEXCUBE infrastructure.Oracle FLEXCUBE supports a set of operations that are common to the DMS solutionssupported. The set of operations that would be supported by the integration are:● Add a document to a DMS● View a document indexed in the DMS● Delete a document indexed in the DMS2.1.2 Adding a Document to DMSIn this operation you can upload a document to a DMS. The paper documents should bescanned into a digital format, which can be uploaded to the DMS. To upload the digitaldocument, you must choose the file using the browse dialog and click upload button to indexthe document in the DMS. The DMS would register the document and provide a document IDto identify this document for later usage. This document ID can be used to locate thedocument, for other operations.Oracle FLEXCUBE stores this document ID to maintain a linkage between the documentsstored in the DMS, and the documents pertaining to any transaction. Hence, the documentsindexed in the DMS by Oracle FLEXCUBE, can be opened and viewed at a later stage.If Oracle IPM is the DMS of choice, then the document ID is stored as an attribute of thedocument.The ID can be utilized for searching and locating the document via the search features offeredby Oracle IPM.2.1.3 Viewing the Document Indexed in the DMSOracle FLEXCUBE allows you to view documents stored in a DMS that are referenced bytransactions created in Oracle FLEXCUBE. To view the document captured in DMS, selectthe document and click View button.If Oracle IPM is your DMS, you must login to Oracle IPM and you can view the document inthe ‘Oracle IPM: ImageViewerTool’ screen.Documents stored in Oracle IPM are viewed via the Oracle IPM Viewer which providesadditional functionality to annotate the document.NoteIf Oracle IPM Viewer is not installed on your machine you can use the plain Image Viewerto view the documents.2.1.4 Deleting a Document Indexed in DMSDocuments stored in the DMS can be deleted from Oracle FLEXCUBE if the transactionstores the link to the document. To delete the document captured in the DMS, select thedocument and click ‘Delete’ button to delete the record from the set of document records.After the deletion of a document the corresponding Oracle FLEXCUBE transaction would nothave references to the document. If the document does not get deleted from the DMS, therecord would still be removed from the Oracle FLEXCUBE transaction, so that a failure in theDMS would not prevent further transactions.To delete multiple documents at a time, you have to select the multiple records correspondingto the document and click the delete button. The system displays the message as” Theselected documents have been deleted from the Document Manager System.”。
Oracle银行财务管理系统发布14.4.0.0.0版本说明书
Development Workbench - Notifications Oracle Banking Treasury ManagementRelease 14.4.0.0.0[April] [2020]Contents1Preface (3)1.1Audience (3)2Introduction (3)How to use this Guide (3)3Notification – Getting started (4)3.1What is Notification (4)3.2Notification Trigger (4)4Notification Development (4)4.1Pre-request for Notification development and testing (4)4.2Notification specification (5)4.3Notification XML development (5)4.4Notification Process (5)4.5Development process in Development Workbench (5)4.6Notification Trigger (6)4.7Notifications (12)5Deploy Notification (18)5.1Notification - Workbench related deployment (18)5.2Notification Trigger deployment (18)6Test Notification (18)6.1Notification flow (19)6.2Scheduler based notification (19)6.3MDB based notification flow (20)6.4Triggering notification and testing (21)1PrefaceThis document describes the steps to develop the notification XML and notification trigger using Oracle FLEXCUBE Development Workbench for Universal Banking.1.1AudienceThe Development Workbench Notification Development book is intended for theFLEXCUBE Application Developers who perform the following tasks:▪Develop new Notification2IntroductionHow to use this GuideThe information in this guide includes:▪Chapter 3, “Introduction”▪Chapter 4, “Notification - Getting started”▪Chapter 5, “Notification Development”▪Chapt er 6, “Deploy Notification”▪Chapt er 7, “Test Notification”3 Notification – Getting started3.1 What is NotificationNotification framework in FLEXCUBE UBS is used to communicate the business event happened in FLEXCUBE UBS to external systems. Depending upon the event, the XML message is pushed to external system ’s asynchronous Queues for their consumption.3.2 Notification TriggerNotification Triggers is developed to recognize the event and then invoke the notification process. This trigger is developed using Development Workbench. 4 Notification Development4.1 Pre-request for Notification development and testingFollowing are pre-request for notification development:∙ Target FLEXCUBE Environment with Notification framework installed ∙ Development Workbench link mapped to the FLEXCUBE environment ∙ Required Query Web services developed and testedFig 5.1.1: Development of NotificationsPrepare Specification DevelopNotification XML in WorkbenchDevelopNotification Trigger in Workbench Deploy the units in Target Test Notification4.2Notification specificationIdentify the notification requirement as below∙What is the Notification function ID name for RAD XML (Third character should be N)?∙What is the Notification code?∙What is the Base table in FLEXCUBE UBS that triggers the notification?o What operation at base table triggers (insert/update/delete)?o What is the where clause for filter?∙What is the query Web service to be used?o What is the operation?o What are the tags required?Example;∙Notification function ID name –STNCUMOD∙Notification code –NOTIF_CA_CUSTACC_MOD∙Base table - STTM_CUST_ACCOUNTo Operation –DELETEo Filter –Account class type in ( S , U )∙Web service to be used –FCUBSAccServiceo Operation –QueryCustAcco Request node –Cust-Account-IO4.3Notification XML developmentNotification RAD XML development creates the following files:∙RAD XML∙SPC∙SQL∙Static Data4.4Notification ProcessThere will be one trigger for the base table of notification and in case of multiplenotifications sharing the same base table, there will be no new triggers created. Instead the same trigger created on the base table will be reused. This approach reduces the number of triggers being used for notifications.4.5Development process in Development WorkbenchThe notification development process in Workbench is split into two steps:1.Notification Triggers2.Notification Filter ProcedureThe first step is to create notification triggers for base tables. The trigger generated from Workbench will be inserting key details into a static notification log table. The following details will be captured:∙Trigger code: A unique value to for a notification trigger.∙Base Table: The base table on which, the trigger is built.∙When Clause: A simple when clause for the notification trigger.The second step is to capture details of notifications and generate the notification filter procedure. The following details are captured:∙Notification code: A unique value to identify a notification.∙Description: Meaningful description of the notification.∙Gateway Service:4.6Notification TriggerAfter successful login to Development Workbench click on Notification Trigger option in the tree as shown below:Fig 4.6.1: Notification triggerFig 4.6.2: Notification trigger optionsNotification Trigger we have two options - Add a new Trigger or Modify Existing one. New:Fig 4.6.3: Notification trigger: New optionTrigger Code: A unique value to for a notification trigger. Follow the naming conversion it should start with TRG_XXXX.This is mandatory field. This attribute signifies the trigger code created as part of trigger creation step in OTD. Each notification will be linked to a trigger code.Description : Information field. Meaningful description of Trigger is to be given.Firing Time : Specify when trigger needs to fired. We can create only BEFORE and AFTER triggers for tables. (INSTEAD OF triggers are only available for views; typically they are used to implement view updates.) (After/Before). Each Record: specify for each row required or not. If FOR EACH ROW option is specified, the trigger is row-level; otherwise, the trigger is statement-level. (Yes/No)Base Table: The base table on which, the trigger is built. This is mandatory field. Select a valid table from available LOV next to the field.Pk Cols: Enter Primary key fields of table in tilde (~) separated format. This is mandatory field.Pk Types: Enter Primary key type of the corresponding primary key field. This is mandatory field.Selected Columns and Data Types: DefunctTrigger When Clause: A simple when clause for the notification trigger. A trigger restriction can be specified in the WHEN clause, enclosed by parentheses. The trigger restriction is a SQL condition that must be satisfied in order for Oracle to fire the trigger. This condition cannot contain sub queries. Without the WHEN clause, the trigger is fired for each row.Notification Codes: If the trigger is associated with a specific notification code, then the particular notification code has to be provided in the field. If the trigger is shared across many Notifications, field can be left emptyFig 4.6.4: Notification trigger: GenerationOn successful save Notification Trigger will generate two files (gwtr#_<trg-code>.trg and GWTM_NOTIFICATION_TRIGGERS__<trg-code>.INC) user needs to compile them in FLEXCUBE schema.Modify:Fig 4.6.5: Notification trigger: ModificationFig 4.6.6: Notification trigger: Modification- Selecting Trigger nameFig 4.6.7: Notification trigger: Modification- Entering valuesFig 4.6.8: Notification trigger: Modification- Entering valuesFig 4.6.9: Notification trigger: Modification- Successful Generation4.7NotificationsNotifications Screen will be used to create new notification or modify existingnotification; here we capture notification information for notification codes. We savenotification details into xml.Fig 4.7.1: Notification ScreenAction:. We can choose either new or Load action. New to create a new notification and Load is used to modify the existing one.Save Xml Path: Specify the path to save notification xml. This would be considered only if the Save Mode is Client and Work Directory is specified as $CURRENT_DIRECTORY Notification Function: Specify the notification function-id name.Conventions:Maximum 8 chars. 3rd letter must be ‘N’.Example: FTNCONONNotification Code: Enter the notification code to which we need to capture values. This is Mandatory field.Recommended Convention for Notification Codes:NOTIF_<Module Code>_<Description>Example:NOTIF_LD_CONTRACTThis is the notification indicating that a LD contract has been created/modified Description: Information field. Meaningful description of the Notification has to be provided in the fieldModule: This attribute signifies the module on which the notification is based.Module Description: Information field. Module Description which would be defaulted from Module LOVNotification XSD: Notification XSD name will have to be provided in the corresponding Field. Naming convention to be followed while naming Notification XSD is as follows [Module Name] – [Notification Description] – Notif.xsdExample: FT-Contract-Notif.xsdNotification XSD has to be provided only if no Gateway Web Service Query Operation is configured to the NotificationBase Table: Select the base table on which trigger needs to be applied.Firing Time: Indicates the Operation on the base Table for which Notifications has to be sent. Options available are Insert, Update or BothFilter Type: This attribute can take the following values.1.Where clause2.Plsql blockPk Cols: Enter Primary key columns of the Base Table.Pk Types: Enter Primary key field Data Types.Provide details of Gateway Service, Operation, Type XSD Name and Full Screen Reply if a Query Web Service has to be mapped to the NotificationGateway Operation: The gateway operation name to execute query for the mentioned Service.Gateway Service: The gateway service to be used to get the full screen response. Gateway IO Request: The gateway IO request node to be used in querying operation.Type XSD Name: This field has to be entered if Notification is mapped to a Service and Request. Name of the Master Type XSD for the service and operation has to be provided here. This can be found in include portion of the Request Msg XSD of particular Service-OperationExample: LC-Contract-Types.xsdFull screen Reply: This attribute decides whether full screen or primary key notification response to be sent. This is applicable only if gateway Service details are providedHO only: This attribute is used to send notification only from head office.Filter Logic: The filter logic which decides whether the notification needs to be sent or not. This can be a simple where-clause on base table or a complex pl/sql block.Web service Tags: The columns selected from base table as part of web service tags, will be used to send the full screen notification response. These tags defines the elements of Notification Xml when no Query service is mapped to it:Fig 4.7.2: Notification Screen generationFig 4.7.3: Notification Screen Generation SuccessfulModifying an Existing Notification RADXMLThe process of modifying an existing Notification RADXML is illustrated in the images belowFig 4.7.4: Notification Screen LoadingFig 4.7.5: Notification Screen LoadedFig 4.7.6: Notification Screen Loaded and Modified5Deploy Notification5.1Notification - Workbench related deploymentCompile the following files in Target FLEXCUBE UBS Database schema•Notification Main Package generated from ODT•Hook Packages•GWTM_NOTIFICATION_TAG_MAP___<Notification Function ID>_.INC •GWTM_NOTIFICATIONS_MASTER___<Notification Function ID>_.INC 5.2Notification Trigger deploymentCompile the following files in Target FLEXCUBE UBS Database schema•GWTM_NOTIFICATION_TRIGGERS__TRIG_CONTRACT.INC•GWTR#_TRIG_CONTRACT.TRG6Test NotificationThis section explains the run time notification flow and testing steps.6.1Notification flowThe notification process occurs as two parts:1.Oracle JOBs created using FCJ Scheduler framework that sends data required fornotification to an internal JMS queue.2.Gateway MBD that lists on internal JMS queue, that picks the notification XMLs andprepare full web service response and send to external system queues.6.2Scheduler based notificationThe Notification Process in FLEXCUBE can be done using the jobs scheduler as follows: The trigger generated from Workbench will be inserting key details into a staticnotification log (STTB_NOTIFICATION)Once Job is triggered, a request is sent to EJB layer from job execution class and thenotification log table will be polled for unprocessed records.Each unprocessed record is locked.The record is verified against the notification maintenance and checked whethernotification is to be sent or not.If notification is to be sent, pre notification message xml is built and it is sent to internal NOTIFY_QUEUE(JMS queue) configured in Gateway layer.The job is then rescheduled to fire next time based on the previous execution.Refer Gateway Installation documents on how to setup the Queues.Flow Chart for Notification Flow in Scheduler6.3MDB based notification flowNotification processes in MDB are as follows:1.Notification MDB listens on the internal NOTIFY_QUEUE(JMS queue)2.On any message received, the MDB identifies which schema to connect using theJNDI name being present as part of the message xml.3.Gateway notification processing package is called from MDB to build notifications.4.In MDB, the notifications built is processed and sent to the destination specified incorresponding notification.5.In case of exception the transaction is rolled back.6.If all notifications are successfully processed, transaction is committed.Flow Chart for Notification Flow in MDB6.4Triggering notification and testingFollow the below steps to test notification:∙Simulate a case where base table under goes data change.∙Check record populated at STTB_NOTIFICATION table∙Check Notification messageGWTBS_NOTIFICATIONS_LOG.NOTIFICATION_MESSAGE21 Development Workbench - Notifications22Development Workbench - Notifications Development Workbench - Notifications [April ] [2020] Version 14.4.0.0.0Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon (East) Mumbai, Maharashtra 400 063 IndiaWorldwide Inquiries: Phone: +91 22 6718 3000 Fax:+91 22 6718 3001 /financialservices/Copyright © 2007, 2020, 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 dangerous 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 affiliates 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.。
Oracle财务会计系统解决方案介绍
Oracle财务会计系统解决方案介绍目录一、内容概览 (2)1.1 财务会计系统的重要性 (3)1.2 Oracle财务会计系统的优势 (4)二、Oracle财务会计系统概述 (5)2.1 系统简介 (7)2.2 主要功能模块 (8)2.3 系统架构 (9)三、Oracle财务会计系统解决方案 (12)3.1 账户管理 (12)3.1.1 用户账户创建与管理 (14)3.1.2 权限分配与控制 (15)3.2 会计科目体系 (16)3.2.1 科目创建与维护 (17)3.2.2 科目余额管理 (19)3.3 报表编制与分析 (20)3.3.1 自动报表生成 (21)3.3.2 定制报表需求 (22)3.3.3 数据分析与可视化 (23)四、实施与部署 (25)4.1 实施步骤 (26)4.1.1 项目启动与规划 (27)4.1.2 系统配置与测试 (28)4.1.3 员工培训与上线 (30)4.2 部署环境 (30)4.2.1 硬件环境要求 (33)4.2.2 软件环境配置 (34)五、案例分享 (35)5.1 案例背景 (37)5.2 解决方案应用 (38)5.3 成效评估 (39)六、客户支持与服务 (40)6.1 技术支持 (41)6.2 培训服务 (43)6.3 售后服务 (44)七、总结与展望 (45)7.1 项目总结 (46)7.2 未来发展趋势 (47)一、内容概览本文档将全面介绍Oracle财务会计系统解决方案的应用范围、主要特点以及对于企业财务会计管理带来的改变。
Oracle财务会计解决方案是基于其强大的Oracle数据库平台开发的一套全面的管理信息系统，旨在帮助企业简化财务流程、提高会计信息的准确性和处理速度、增强财务流程的可见性，以及支持组织在快速变化的会计和税务法规环境下的合规性。
本章节首先将概述Oracle财务会计系统的核心组成部分，包括其财务会计模块、财务分析模块以及与供应链、人力资源等其他业务模块的集成能力。
Oracle财务管控系统方案建议书
3 数据监控
▪按照清理原则进行清理 ▪整理问题清单
数 据 治 ▪基础设置数据 理 ▪主数据 路 ▪接口数据 线 ▪核心业务数据 图
2 数据清理 1 数据检查
4
“六统一”之财务流程体系：通过期末结账系统实时掌握期末结账状况，提升 财务管控水平
监控期末结账进度
• 实时期间状态看板，了解实际情况； • 监控结账进度，为财务管控提供有力支持。
• 通过期间管理平台，统一管理不同账套、不同应用产品的会计期间； • 通过数据监控平台，防范数据污染，降低数据管理成本，提升财务数据质量。
期末结账系统期间管理平台
期末结账系统数据监控平台
业务 实体
库存 组织
分类账
会计期间 控制主体
无控制
法人 主体
资产 账簿
▪ 设定数据检查点并定期检查 ▪ 增加数据控制和校验规则，控制数据入口
内控和系统整合，建立风险导向的统一权限控制体系。
1
“六统一”之会计科目体系：构建服务于核算会计和管理会计的多维度会计科 目体系
多维度会计科目结构，同时考虑会计核算与管理核算需求，并支持多维度财务管控分析。
会计核算关注重点
• 主要关注的核算维度：法人公 司、科目、内部往来等
• 必须遵循会计准则和法律法规 • 提供会计报表和法定披露信息
组织架构
人员信息
银行目录
会计科目结构
资产类别
…
基于对企业信息化规划和Oracle产品的理解，建议的未来财务信息化架构蓝图
管控层 职能层 基础层
企业财务管理框架
考核评价
决策与分析 Oracle BIEE
决策分析
预算管理体系
预算管理
预算编制
ORACLE商业银行解决方案
• Batch Reporting Based
on Fragmented Data
• Proactive Analysis Based on
Integrated Data
• Product Centric • Inefficient Internal Silos
Margin Pressure
Industry Transformation
Today Tomorrow
• Redundant and Discrete
Systems
• Manual, Paper-Based
Service Model
• Global, Integrated Systems • Streamlined and Intelligent
Standardize and Streamline Internal Business Operations
Foundation: Oracle Technology
Data Server
Application Server
Support World-Class, Scalable Solutions
9i / 9iAS
Benefits
Build Flexible, Customer-Centric Systems with Partners
• Scale to Meet Any Volume • Modularize Core Systems • Connect Externally Facing
Enable you to:
Provide Scalable, Flexible Technology Infrastructure Drive Customer to Personalized, Profitable Offering Improve Performance Mgmt, Reporting and Compliance
ORACLE财务功能概述
ORACLE财务功能概述引言Oracle是一家全球领先的企业应用软件提供商，其财务功能是其产品组合中的重要组成部分。
本文将对Oracle财务功能进行概述，包括其主要特点和功能模块。
Oracle财务功能主要特点1.综合性：Oracle财务功能涵盖了企业财务管理的各个方面，包括会计、税务、成本控制等。
2.灵活性：Oracle财务功能可以根据不同企业的需求进行定制和配置，以满足企业的特定业务需求。
3.多语言、多币种支持：Oracle财务功能支持多语言和多币种，适用于全球化企业的财务管理需求。
4.集成性：Oracle财务功能可以与其他Oracle产品和第三方系统进行集成，实现数据的共享和流转，提高工作效率。
Oracle财务功能模块Oracle财务功能包括以下主要模块：1. 会计模块会计模块是Oracle财务功能的核心模块，主要包括以下子模块： - 总账管理：管理企业的总账账簿和账户，记录和核算期末凭证。
- 应收应付管理：管理企业的应收账款和应付账款，跟踪客户和供应商的付款情况。
- 固定资产管理：管理企业的固定资产，包括资产购置、折旧与清理等。
- 成本核算：对企业的生产成本进行核算和分析，提供成本控制的依据。
- 预算管理：编制和管理企业的预算，监控和控制预算执行情况。
现金管理模块能够帮助企业有效管理现金流量，并提供准确的现金预测和资金管理决策支持。
主要包括以下功能： - 现金流预测：通过预测企业的现金流入流出情况，提供准确的现金流预测报告。
- 资金计划：制定和管理企业的资金计划，以确保足够的资金供应。
- 现金集中与支出管理：管理企业的现金集中和支出过程，优化资金利用效率。
3. 税务管理模块税务管理模块能够帮助企业满足税务合规要求，并提供税务计算和申报支持。
主要包括以下功能： - 税务计算：根据国家和地区的税法规定，自动计算企业的各类税款。
- 税务申报：生成税务申报表格和报表，支持自动申报和纸质申报两种方式。
Oracle Banking Accounts DDA解决方案说明书
Puts you in the Driver’s SeatOracle Banking Accounts can enable the Bank of Tomorrow to massively scale its account operations to offer services to new-age businesses that need massive volumes and responsiveness.Account transactions have boomed exponentially for the past two decades. In this age of instant gratification, the scale of accounts operations continues to increase manifold every year. The traditional DDA platforms were not built to handle the volume and responsiveness required by the new types of transactions, such as real-time, instant, and e-commerce transactions. Banks currently face many problems playing catch-up with newer, more agile players to serve their customers.In such a world, banks must fundamentally reimagine and redefine the value they can offer their customers.Leveraging a proven, market-leading, and cloud-native DDA solution, which is massively scalable and comes pre-integrated to provide banks with the flexibility to handle any workflow through highly configurable processautomation, is an efficient way to execute this transformation2“Oracle Banking Accounts Cloud Service is built for Needs of Today and Tomorrow”Micro ServicesArchitecturePersonaCentricCloudNative RestAPIs24x7ContinuousUpgradesExtensibleHighlyScalableOracle Banking AccountsOR ACLE BANKING ACCOUNTS 3HANDLE MASSIVE VOLUMES OF TR ANSACTIONS ON CLOUDOracle Banking Accounts is built on a highly scalable cloud-native architecture based on data grid architecture with the industry’s highest TPS (Transaction per second) per CPU that scales linearly. Today, this is extremely important for banks, primarily to cater to corporate clients from high-volume industries like e-commerce.DOMAIN DRIVEN DESIGN APPROACH WITH SPECIFIC FOCUS ON BANKING PROCESSESWith a domain-driven design coupled with a microservices architecture, the service comes pre-integrated with other Oracle solutions and offers streamlined integration capabilities with 3rd party solutions. Since the service is built ground up with the banking domain in mind, all the domain services align to business sub-domains and come in the form of their microservices, putting the Bank in the pilot’s seat with total control and flexibility.4OR ACLE BANKING ACCOUNTS“Global growth in banking real-time processing”Globally, more than ~61%CAGR in number of transactions expected in 2025-30-PwCOR ACLE BANKING ACCOUNTS 5FLEXIBLE AND HIGHLY CONFIGUR ABLEOracle Banking Accounts is built on a microservices-led architecture catering to a flexible service that allows for highly configurable process automation and workflow with the ability to spawn multiple business processes.With real-time insights, intuitive dashboards, and alerts with built-in manual exceptions or escalations, it is also easy to track and maintain a 360-degree view of the account operations.NEXT GENERATION USER EXPERIENCEOracle Banking Accounts is built with a focus on user experience. The service caters to the newer generation of users looking for better experiences -the service offers specific persona-based screens and dashboards. It offers complete transparency and control of accounts, including origination, tracking, and servicing, with a 360-degree view.API FIRSTWith a cloud-native solution, all integrations are on an API-first approach. A low-code routing hub allows for greateragility and faster integration between Oracle’s own as well as other third party’s’ solutions. This enables rapid & seamless connection with the banking ecosystem across the complete accounts value chain.• Suite of native cloud services• Pre-integrated• Offers streamlined integration capabilities6OR ACLE BANKING ACCOUNTSUnlock Value with Oracle Banking AccountsCloud Native Microservices ArchitectureProven Architecture at Tier 1 BanksTrue 24*7No downtime during maintenance and upgradesHigh ConcurrencyHigh single account throughput and horizontal scalingContinuous UpgradeInnovation and features are delivered as periodic patch sets, enabling the bank to stay on the latest version Functional DepthEngineered for Tier 1 banks and built to work withLiquidity Management,Virtual Accounts Management ComponentsMulti-Multi EnabledMulti-Country, Multi-Entity, Multi-Currency, etc. enabledEnables Bank to build capability in-houseBuilt-in tooling such as configurability and extensibilitywill help Bank build in-house modifications to workflows, screens and lifecycleOpen APIOBA can easily connect with banks’ other systems or external apps enabling a seamless experienceOR ACLE BANKING ACCOUNTS 7。
数据库oracle银行管理系统
风险管理：对银行的 各类风险进行评估、 监控和管理，保障银 行资产的安全和稳定 。
数据库在银行管理系统中的数据存储与处理
数据存储： Oracle银行管 理系统采用关系 型数据库，能够 高效地存储大量 的客户信息、账 户交易数据等。
数据处理：该系 统具备强大的数 据处理能力，支 持实时交易处理、 批量处理等多种 业务场景，确保 银行业务的顺利 进行。
单击此处添加副标题
Oracle银行管理系统的数
据库
汇报人：XX
目录
01 02 03 04 05 06
添加目录项标题
Oracle数据库概述
Oracle银行管理系统的数据库设 计
Oracle银行管理系统的数据库实 现
Oracle银行管理系统的数据库应 用
Oracle银行管理系统的数据库发 展趋势与展望
2000年代至今：Oracle数据库 不断推出新版本，功能越来越强 大，广泛应用于各行各业
Oracle数据库的体系结构
逻辑存储结构：表空间、段、区、块等 物理存储结构：数据文件、控制文件、重做日志文件等 内存结构：SGA（系统全局区）和PGA（进程全局区） 进程结构：后台进程和前台进程
Oracle数据库的特点和优势
数据库的备份与恢复
Oracle数据库提供了多种备份方式，如全量备份、增量备份和差异 备份，可根据需求选择合适的备份方式。
在进行数据库恢复时，Oracle提供了点恢复和时间恢复两种方式， 可根据实际情况选择合适的恢复方式。
为了保证数据的安全性，Oracle数据库还提供了数据压缩和加密等 高级功能，可有效减少备份数据的大小并保证数据的安全性。
数据库在银行管理系统中的数据挖掘与分析
添加 标题
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
可以满足公司对预算控 制各维度的需求 月度控制 定 义 不 同 期 间 的 预 算 指 标
预算编制
刚性控制 预算指 标下达
配置系统 预算额度 指定预算 控制方式
阶段控制
建议控制 弹性控制
单项控制
完全无控 制
总额控制
共享服务中心——之费用管理中心
从报销到付款流程
拒绝 拒 绝
员工提交费用 报表
• 填制费用报表 • 粘贴原始单据 • 提交报表/单据
财务总帐 利息支出
其他收入 成本、费用
大总账观点的提出
• 从业务角度看：把不同的业务分开核算、分开记账有合理性 ，而将各单独账务进行有机梳理、进行合理汇总，形成完整 的账务，并逐步完善数据治理是大总账的重要观点。 • 从IT建设看：利用健壮的技术平台，分开建立专门的应用系 统，各系统分工满足各项需求，作到各司其职、各尽其责， 也是IT建设的成熟模式。
现代企业财务管理目标
及时、可控、可测、全面、透明、正确 新的流程
决策支持 精密的分析 & 提前发现问题
事后发现问题
决策 支持
控制 内含的
人工、事后 控制
报告 集成 事务 处理 优化
复杂的技术 报告
基于手工 事务处理
传统流程
Oracle财务管理蓝图
绩效管理 计划和预算 财务合并 财务流程 信用到收入 现金和金库管理 采购到付款 差旅和费用管理 监管、风险和法规遵从 流程管理 监管架构 技术架构和工具 端到端业务流程 主数据管理 完善安全性 企业分析套件 内部洞察 财务控制 & 报表 资产生命周期 & 不动产管理 盈利分析和业务智能
经理审批
• 费用的合理性 批 准
财务审核
批 准
本地审计
• 审核原始单据 • 对应单据和报表 拒绝 批 准 • 单据和报表是否 一致 • 是否符合财务制 度
• 系统自动生成应 付款 •系统自动生成凭 证，并记入费用总 帐
银行付款
•转帐至本地银行 （中国） •付款到员工帐户
付款操作
•通过指定银行统 一转帐 •将付款明细交给 银行
会计服务
i.开放，快速实现的和产品系统的接口
基于规则 的 会计引擎 45 个接口 – Fidelity CBS, Equation, Cardpac, Bank Trade …… 192个接口 – Gloss, Mocom, Murex, 25个接口 – Silverlake CBS, Midas, Cardpac, Kondor+ ….. 120个接口 – MF CBS,Card Plus, Infinity, Murex, ICBS, Bank Trade.. 100+个接口 – ABACUS (Unisys) CBS
• 这样的思路，是应对今后快速变化的政策、现实业务发展的 成熟思路。
大总账观点是目前的主流观点国内主要的商业银行和厂商均采用此方案
什么是大总账？
• 内容：
• 是加工、汇总各业务系统核算结果所形成的完整会计 账务。它不包括交易数据，交易信息和分户账仍然存 在于各源业务系统中。
• 特点：
• 综合的、独立的账务平台
Oracle资产管理
ERP信息技术工具促进形成了统一集成的信息流，并为优化业务流程、管理水平创造必要条件
资产实物信息 资产财务信息来自资产编号 管理类别 资产地点 所属专业、部门 启用日期 单位数 是否盘点 父资产编号 员工编号 制造商 型号 补充信息
资产类别
统计需求 报表需求 查询需求 核算需求
信贷系统 。。。
按币种、机构、交易类型等 维度汇总的交易级数据
大总账帐套
各机构的支付数据
财务总账 帐套
。。。
问题： 1、核心系统中是否保留部分账务？ 2、其他外围系统是否与核心接口？ 3、准备金计提等数据是否回写到核心系统？
建立大总帐的Oracle一体化解决方案
核心系统
客户信息系统
-零售客户 -商业客户 -公司客户 -信用卡客户
2
Oracle 系统 开放的接口
Oracle系统的导 入程序
3
银行业务系统
1
业务系统 数据
开放的接口程序 Open Interface
其他特别 的规则
总帐
科目匹配
生成分录
总帐日记帐
案例分析:ERP项目的实施目标
建成全行统一完整的ERP总账 建立符合国际银行主流范式的规范统一的会计科目表 集成内部不同系统来源的财务披露信息 自动完成多币种处理和全行报表合并 生成满足国际上市要求的符合不同会计准则的财务报表、财务报表附注信息 以及分部报告 建成全行集中统一的ERP基础财务应用系统，包括费用、固定资产、预算及采 购管理等模块，其中ERP一期项目试点实施ERP费用管理和固定资产管理模块 借助国际成熟财务管理软件改造完善财务处理流程 实现全行财务建立在统一系统平台意义上的集中统一管理 实现财务事务处理和账务核算的集成和自动处理 实现基础财务应用模块和财务总账的集成
<Insert Picture Here>
驾驭风险 创造价值
Oracle银行财务管理系统解决方案
唐宏钧 甲骨文（中国）软件系统有限公司金融行业资深顾问 2010年10月28日
为什么要实现财务信息化？
关键的业务驱动力和需求 业务驱动力
• 中国加入世贸后，承诺进一步开 放，必须采用国际化战略来应对 国外同行的竞争和挑战。必须尽 快从规模上和管理水平上向行业 领导者看齐 • 通过成功的上市（IPO），快速的 融入国际市场，提高竞争力 • 适应国内和国际监管机构的需求 ，包括多会计准则、Basel II、 萨班斯-奥克斯利（SarbanesOxley）法案及行业的监管条例
Oracle 应对
• 大集中，大总帐和财务的
业务收益
• 实现一体化智能核算平台，
一本帐，从业务核算、费 用核算和支付，资产管理， 报表披露等实现标准化
• 多维信息管理，多组织架
端到端的财务解决方案， 实现银行从业务到财务， 从核算到管理的全方位提 升
• 优化业务流程，提高员工
构，多币种、多帐期、多 语言可以灵活支持对内对 外的信息披露要求
产品系统
-贷款、存款 -银行卡 -支付服务 -贸易融资 - 资金交易
交易系统
外部数据
82+个接口 –Hitachi CBS, Panorama/DEVON, WallStreet …
开放的接口表程序－快速集成外部系统
众多实际案例的验证 开放、成熟、简便
GL 接口格式 •会计日期 • 币种代码 • 科目 • 借方金额 • 贷方金额 • 行描述 •等 • 属性1 • 属性2 •等
核算主体 XX分行 业务主体
核算主体 分行 业务主体 业务主体
核算主体
核算主体
业务主体
业务主体
库存组织
库存组织
库存组织
高度的灵活性支持企业组织结构与业务流程的变革
在业务执行过程中的预算控制
在采购申请、采 购发票、记帐凭 证输入过程中， 系统自动检查可 用资金
系统提供多种标准的 预算控制方式 绝对控制
每段有独 立的值集 灵活设计 每段可长25位
结构
•财务核算的需要 •财务分析的需要 •未来业务扩展的需要，体现相对变化的管理需求
Oracle商务智能-高层领导的决策支持
银行总账的变迁
会计 处理 利息收入 会计总帐
利息支出 其他收入 资产负债 表损益表
业务 处理
业务 处理
会计处理
利息收入
成本 费用
2. 有利于提升财务管理水平，满足决策支持的需要
建立全行统一独立的总帐系统，满足集中化账务核算的要求，有利于加 强对分支机构的财务监管 摆脱传统财务核算仅仅停留在科目报告层面，建立全行统一的多维度 （分机构、业务线条、产品、渠道等）财务绩效报告体系 及时、准确、多维汇总全行所有业务信息，建立全行统一的信息平台， 从而准确、实时的把握业务经营的结果，满足现代银行财务管理对决策 支持的需要
Oracle帮助银行应对财务管理挑战
挑战
分散的财务系统造成信息 和业务流程不统一 内部管理和对外披露的要 求不断变化，很难及时获 得相关信息。 领导要求的信息不能及时 提供，影响决策流程 手工的审批流程，影响应 付款业务处理的效率 希望采用更先进的共享服 务等业务模式 财务信息需要按多种会计 准则披露
-多维绩效管理的基础
30 段 – 可以由用户按照管理需求设定
公司
广州分行 上海分行 。。。
业务条线
大客户 个人
成本中心 会计科目
财务部 信贷部 。。。 收入 成本 费用
产品
××产品 YY产品
客户群
AAAA BBBB 。。。
员工/渠道/销售模 式。。。
•不同会计结构并存 •客户完全根据自身业务及管理特点，建立自己的弹性会计科目
的业务模式，保持行业竞 争优势
搭建六大平台，提升财务管控水准
基于大总帐的满足多会计准则、集中的核算管控平台，建 立单一经营信息来源 全面预算管控平台，实现事前控制，保证预算落到实处 以共享服务为特质的费用报销及集中采购平台，落实政策， 规范费用发生，流程制度 资产全生命周期管理平台，管理企业资产的财务、运营 多维度绩效管理平台，多视角、全方位的管理业务 商务智能管理平台，及时准确全面地支持战略决策
信息整合
资产工作台
折旧费用科目 成本
残值 资产系统管理的 资产补充属性 范围 累计折旧 完整的资产信息 年初至今折旧 （实物/财务） 信息追溯 资产类型 资产信息重要程 度分类 是否折旧 公司特殊的管理 信息发布 税务信息 要求
Oracle弹性会计科目结构
银行内部系统的框架性定位