产险分支机构ORACLE业务对照
Oracle生命保险政策管理解决方案数据表说明书
Oracle Insurance Policy Administration Solution for Life InsuranceIn the life insurance industry, getting ahead requires perfect conditions: a constant flow of customers, effective agents, innovativeand compliant products, and much more. Cultivating those conditions is nearly impossible with legacy policy administration systems. What if you could accelerate product development for modification, new products and greenfield initiatives all with the same platform, in weeks versus months using a future ready policy administration system? What if you could use that same solution to differentiate from the competition by transforming the way you service your distribution and valued customers? You can achieve all of this and more with the insurance industry’s best-in-class policy administration system.Ultimate Flexibility for Business AgilityOracle Insurance Policy Administration (OIPA) is a rules-driven system that supports every stage of life, annuity and group insurance, including underwriting, contract changes, claims, and more. With Oracle’s solution, you make the important decisions and your system enforces them. You customize the experience you want for your business users and customers at every stage of the policy lifecycle.Unlike other insurance systems, OIPA enables you to easily define your rules, and create and modify products without changing the base code. Managing rules configuration no longer needs the technical expertise of a programmer. Other policy administration systems like code generators and parameter-based solutions offer limited options and ultimately slow things down. They either require you to program changes in the source code or pose constraints based on their defined parameters. OIPA’s browser-based functionality makes the system easy to learn for both business users and IT users.Rapidly Configure, Manage, and Bring Life Insurance Products to Market through Highly Flexible, Rules-Driven Policy Administration Top Analyst Rankings GARTNER LEADERS QUADRANTMagic Quadrant for Life Insurance Policy Administration Systems, North America, 2020 highlightsAbility to executeCompleteness of visionProven track recordDeep pockets for innovation Digital capabilityDepth of functionalityMarket understandingIndustry trendsUser communitySmart Rules ArchitectureFuel Product Innovation through a Single PlatformKey demographic groups like millennials and young couples with children are emerging as prime targets for the life insurance industry. Additionally, many aging seniors still remain unprepared without life insurance. Now is the time to create new life insurance products that appeal to each of these segments. Because Oracle Insurance Policy Administration is a single platform for life, annuity, and group products, the system enables more effective collaboration among your different users. Those involved in the product configuration process—i.e., actuaries, compliance officers, business analysts, and others—can work more effectively to combine features of existing products. They can create or change products with extremely specific features, drilling down to the most intricate levels, without worrying about system limitations.Speed Time to MarketConsider the impact of slashing three to six months off your product development cycle. How much new business could you attract before your competitors launch a similar product? How much would you save in administrative costs? On average, insurers that use Oracle Insurance Policy Administration cut their product development timeframe by one-third.Oracle Insurance Policy Administration Solution for Life Insurance comes with prebuilt product templates for common life insurance products and prebuilt components for features specific to life insurance, giving users a jumpstart in product development. You never have to start from scratch because OIPA offers many user-friendly options: share business rules across the lifecycle, clone products, and copy plans. Whether you need to manipulate detailed components or implement a blanket rule over multiple items, OIPA gives you the flexibility you need to bring your life insurance product to market faster than ever.Key BenefitsBring new products tomarket faster throughcollaborative productdevelopmentLeverage a single system to support multiple lines ofbusinessCut operational costs by configuring business ruleswithout changing yoursource codeIncrease productdevelopment flexibility using configurable business rules Support compliance through detailed audit trail of everytransactionEnhance sales channels and ability to service customersthrough real-time access topolicy dataRapidly scale up or down to support evolving businessneedsLeverage deep domain and technical expertise of OracleInsurance teamAite Life Insurance Policy Administration Systems: An EMEA View, (2017), highlights, “In the EMEA region, OIPA supports all life insurance products” In the same report, OIPA is ranked among the top two best in class platforms for Speed to Market.Conquer Life Insurance ComplexitiesThe leading insurance companies worldwide use Oracle Insurance Policy Administration across multiple lines of business. A majority of those are life insurers with specific requirements and product variations among traditional term, whole life, universal, joint products, and more.Here are a few of the most popular life insurance features:Dynamic quote capability. Customer service representatives are prepared to resolve “what if” scenarios through the system’s dynamic quotingcapability. For example, suppose a policy owner requests a face decrease, but that request would result in a release of taxable funds. The policyholder might ask, “How much can I reduce my face amount without releasing those funds?” OIPA can generate real-time quotes to accommodate the largest possible decrease that avoids the release.Multiple commutations per transaction. OIPA transactions allow more than one set of commutation functions per OIPA transaction. Users may usea special command to invoke a new set of commutation functions.Review past activities and calculations. Users can easily cycle back through earlier activities in chronological order to recalculate or simplyreview past transactions.Tax compliance. The system’s commutation functions generate and present the global DEFRA and TAMRA actuarial formulas used for basesegments and qualified additional benefits. All OIPA transactions andbusiness rules share a common DEFRA and TAMRA data set.Drag and Drop to Create Business RulesDesigning first-rate customer experiences starts by giving your customer service representatives the right tools. Oracle Insurance Policy Administration’s Rules Palette is a visual configuration tool that enables you to define and customize your rules with easy drag and drop functionality. You can add your unique requirements to your rule sets, optimize user interfaces, or simply decrease the number of user interfaces—all without knowing XML or having a programmer’s technical expertise.Key FeaturesHighly flexible, rules-based engine to supportconfiguration, separate fromsource code.Prebuilt life insurancetemplates for faster productdevelopmentUser-friendly rules palette lets you drag and drop toconfigure business rulesA task management solutionenabling users to becomemore productiveProduct cloning capabilities enable users to reuse rulesand componentsCalculation engine andintegrated debuggervalidates calculations andformulas for reuseFull traceability of data with comprehensive audit trailAble to handle large volumes up to 100 million policiesRelease management tool provides visibility and control of rules migrations andstandardsMultilanguage andmulticurrency functionalityto comply with localizationrequirementsWeb-based access to policy in real timeThe Rules PaletteThe Rules Palette comes with many built-in tools including:Data dictionary. Configure math variables and fields for your products and keep naming conventions consistent when cloning productsDebugger. Debug, fix, and retest your mathematical calculations within the Life Products and Riders in Production on Oracle Insurance Policy AdministrationTerm (Guaranteed Level, Annual Renewable) -IndividualTerm with Cash Value, Term with Return of Premium -IndividualWhole Life with Lifetime Protection – IndividualWhole Life with Flex Term Rider - IndividualGroup PensionsIndexed Universal Life -IndividualUniversal Life withSecondary GuaranteesVariable Universal Life –IndividualHybrid Indexed/Variable Universal Life – IndividualUniversal Life with Tiered Interest - IndividualEndowments - IndividualSurvivorship - IndividualUnit Linked - IndividualTerm Life Rider - Individual Spouse RiderOne Year Term RiderChild Term RiderAccidental Death andDismembermentAccelerated Death Benefit RiderUniversal Life with Cash Back Option – IndividualFlex Term Life Rider –IndividualSurrender ValueEnhancement (COLI/BOLI)Early Values Agreement(COLI/BOLI)Business Continuation Rider (for Buy-Sell Agreements)Guaranteed Insurability RiderEquipped for ComplianceA documented audit trail can be extremely useful to comply with market conduct audits. Oracle Insurance Policy Administration Solution for Life Insurance stores all transactions, including reversals, and provides full traceability of that data. Security access is both role-based and defined by configuration, automatically recording check-ins and check-outs associated with each transaction. Increased ProductivityOracle Insurance Policy Administration includes a configurable Workflow Task Management functionality enabling users to become more productive. This feature allows users to set up a workflow for creating and completing tasks associated with policies, policy activities or clients. These workflow tasks are organized into queues based on user’s role and allow for control over who works on tasks and how they work on them. With the Workflow Task Management feature, users can access the tasks and work on activities, policies, applications, clients and fulfill requirements quickly.Cost Savings All AroundOracle Insurance Policy Administration enables life insurers to reduce costs in multiple ways:Eliminate the unsustainable maintenance costs of legacy systems by consolidating multiple existing systems into one.Reserve your IT resources for more substantial technical work. Nontechnical staffers can easily make changes in OIPA without having to customize the source code.Straight-through processing eliminates errors, manual intervention, duplicative work, and delays.Go paperless and dramatically reduce your supply and postage expenses. Oracle’s Proven Track RecordOracle’s $350 million investment in core insurance applications continues to strengthen its insurance industry experience and implementation expertise. The world’s leading life insurance carriers rely on Oracle Insurance Policy Administration because it allows decision makers to adapt to changing market conditions and regulatory requirements.Equip your organization with the most flexible and comprehensive system of its kind: Oracle Insurance Policy Administration. Prove to regulators that you’re following compliance requirements. Prove to your customers that you’re putting their needs first. And prove to your competitors that your company will lead the life insurance market.“Oracle’s talent for enterprise application development and support is strongly evident in the transformation of the Oracle Insurance Policy Administration solution. Most evident is the expansion of features, particularly across the policy lifecycle category that displays Oracle’s ability to listen to the insurance market and respond effectively.”CEB TowerGroupRelated ProductsOracle Documaker Enterprise EditionOracle Business Intelligence Enterprise EditionOracle Business Process ManagementCloud AnalyticsRegulatory ReportingConnect with usCall +1.800.ORACLE1 or visit . Outside North America, find your local office at: /contact ./financialservices/showcase/oraclefs /oraclefs /insuranceCopyright © 2021, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any otherwarranties or conditions, whether expressed orally or implied in law, including impliedwarranties and conditions of merchantability or fitness for a particular purpose. Wespecifically disclaim any liability with respect to this document, and no contractualobligations are formed either directly or indirectly by this document. This documentmay not be reproduced or transmitted in any form or by any means, electronic ormechanical, for any purpose, without our prior written permission.This device has not been authorized as required by the rules of the FederalCommunications Commission. This device is not, and may not be, offered for sale or lease, or sold or leased, until authorization is obtained.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARCtrademarks are used under license and are trademarks or registered trademarks of SPARCInternational, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks orregistered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The OpenGroup. 0120Disclaimer: If you are unsure whether your data sheet needs a disclaimer, read the revenue recognition policy. If you have further questions about your content and the disclaimerrequirements, e-mail ********************.。
利用Oracle Cohereence来处理大规模的保险业规则管理
An Oracle White PaperJuly 2011Oracle Insurance Policy Administration for Life and Annuity: Leveraging Oracle Coherence for Distributed Executionof High Volume TransactionsOracle Insurance Policy Administration for Life and Annuity: Leveraging Oracle Coherence for Distributed Execution of High Volume TransactionsDisclaimerThe following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.Introduction (2)Oracle Coherence (2)Clustered Caching (3)Oracle Insurance Policy Administration for Life and Annuity (5)Rule-based Configuration (5)OIPA Cycle Processing (6)Challenges of Cycle Processing (7)Powering Cycle with Oracle Coherence (7)Distributed Computing with the Coherence Processing Pattern (8)Scalability and High Availability in the Processing Pattern (12)OIPA Cycle Execution using the Coherence Processing Pattern (13)Extending the Processing Pattern to Support Cycle (14)Using the Processing Pattern to Submit Tasks (14)Executing a Cycle Level using ResumableTask (15)Benchmark Results for Cycle Processing (17)Conclusion (18)About Oracle Insurance (18)IntroductionThis technical white paper discusses how Oracle Insurance Policy Administration for Life and Annuity (OIPA) leverages the powerful capabilities of Oracle Coherence in-memory data grid middleware to provide predictable scalability, performance for high-volume batch cycle processing, and seamless fail-over support. It includes a technical discussion of how the Coherence Processing Pattern provides the grid computing infrastructure used by the Oracle Insurance Policy Administration cycle subsystem. The first two sections of this paper provide an overview of Oracle Coherence and the Oracle Insurance Policy Administration products, respectively. The remaining sections of the paper describe how OIPA implements the Oracle Incubator Processing Pattern to enable distributed batch processing of work across a grid of interconnected Oracle Coherence powered compute nodes.Oracle CoherenceOracle Coherence is an in-memory data grid solution that enables organizations to predictably scale mission-critical applications by providing fast access to frequently used data. Data grid software is middleware that reliably manages data objects in memory across multiple servers. By automatically and dynamically partitioning data, Oracle Coherence ensures continuous data availability and transactional integrity even in the event of a server failure. It provides organizations with a robust scaled-out data abstraction layer that brokers the supply and demand of data between applications and data sources. Oracle Coherence enables the following benefits within today’s enterprise applications:•Performance – Oracle Coherence solves latency problems and drives dramatic increases in performance by moving data closer to applications for efficient access. In-memory performance alleviates bottlenecks and reduces data contention, improving application responsiveness.•Reliability – Oracle Coherence is built on a fault-tolerant mesh that provides data reliability and accuracy. Organizations can meet data availability demands in mission-critical environments with Oracle Coherence support for data tolerance and continuous operation. The reliability of the data grid minimizes the need for applications to compensate for server and network failures, streamlining the development and deployment process.•Scalability – Oracle Coherence enables applications to scale linearly and dynamically for predictable cost and improved resource utilization. For many applications, it offers a straightforward approach to increasing the effective capacity of shared data sources. Oracle Coherence handles continually growing application loads without risking data loss or interruption of service.Figure 1. Oracle Coherence OverviewThe information stored within the nodes of a data grid is evenly distributed among the cluster members. When applications access the data grid, Oracle Coherence ensures that the data is never more than one network hop away and thus allows for near in-memory latency to all data stored within the grid. This approach enables very large performance improvements in data access. Furthermore, since the data is distributed among all nodes of the data grid and each node does not have to hold all cached data, a data grid can store very large amounts of data (in the order of magnitude of hundreds of gigabytes) without a degradation in performance. In fact, the addition of nodes to a data grid leads to a linear increase in data capacity available to the clients of the grid without any degradation in performance. This latter property is what is known as a linear scalability. Finally, a data grid has the ability to store backup copies of its data objects in separate nodes and thus also provides for high availability.Clustered CachingOne of the main capabilities of Oracle Coherence, and one that is used heavily by the features discussed within the rest of this document, is clustered caching. Clustered caching refers to the ability to maintain data in the application tier in such a way that the application can fulfill some portion of its data access requirements from the cache. This mitigates the application’s load on the database without violating the application’s requirements for data correctness if that data is being changed. Oracle Coherence provides two main types of clustered caching that are used by the Oracle Insurance Policy Administration solution: Replicated Caching and Partitioned Caching.Replicated CachingThe best-known form of coherent clustered caching is the fully replicated cache. Replication is the ability to achieve guaranteed coherency of data across multiple nodes of a cluster by maintaining copies of the data within each node and synchronizing changes. If each server maintains a local copy of cached data, then the application logic running on each server can access local data without the need to communicate with any other servers. As a result, data access has no measurable latency. There are a few limitations to replicated caching. First, a change to the cache implies the need to communicate to the entire cluster. Such communication—often accomplished by use of group network protocols—cannot by its nature scale linearly. Second, the cache is severely limited in its in-memory size, because each cluster node is maintaining the entire cache within its process space.Partitioned CachingTo solve the limitations of a replicated cache model without sacrificing either the high-availability (HA) benefits of redundancy or the coherency guarantees provided by the clustered cache, Oracle invented the concept of a partitioned cache. With the data partitioned, the cache capacity grows linearly with the size of the cluster, as does the processing capacity available for managing the cache. Further, in a shared-nothing architecture, each piece of data in the cache has exactly one owner within the cluster who is responsible for managing that data. All network communication can be point-to-point in a partitioned model, allowing the cache throughput to scale linearly on a switched network. In order to recover from a possible node failure, a partitioned cache needs to store, at a minimum, one redundant copy of the cache data on a different physical node. The partitioned caching capability of Oracle Coherence provides the foundation for distributed processing in OIPA.Oracle Insurance Policy Administration for Life and AnnuityOracle Insurance Policy Administration is a highly-flexible, rules-based policy administration solution that provides full record keeping and support for all policy lifecycle transactions (e.g. policy issue, billing, collections, policy processing, and claims). With OIPA, insurers rapidly adapt to changing business needs and regulatory requirements while supporting straight-through processing throughout the policy lifecycle.OIPA is used by leading insurers to accelerate product development and speed time to market for differentiated life, health, and annuity products. The system enables insurers to provide real-time policy servicing of customers and sales channels throughout the policy lifecycle for increased retention and loyalty. It also helps insurers reduce risk and support compliance while better managing the business to optimize performance through the use of a single system for life and annuities.Insurers require the ability to quickly bring to market innovative products that stand out from the competition, capture more market share, and ultimately maximize profitability. OIPA is an industry leading, fully configurable system allowing insurance companies to outpace competitors by getting to market faster. In addition, it enables insurers to drive transactions using business rules. It also provides real-time access to policy data, enhancing self-service capabilities for customers and distribution channels.Rule-based ConfigurationFigure 2. OIPA enables insurers to accelerate the development and launch of life, health, and annuity products and update existing products with new features or riders through flexible, rules-based configuration.The rules-based architecture of OIPA enables rapid new product development, freeing insurers from the limitations of legacy policy administration systems. The rules-driven capabilities of OIPA are unmatched in the industry; almost all changes to the system—including products, fields, screens, languages, and currencies—can be made without ever touching the core code or recompiling the application. The system does the heavy lifting through pre-configured templates, rules reusability and product cloning, and a visual Rules Palette with easy to use, drag-and-drop functionality.One of the most important elements configured by business analysts within an OIPA system is the concept of a transaction. Transactions define how the system updates, modifies, or deletes data in OIPA. As an example, a premium transaction takes a payment submitted by an insured and applies that money to a policy. A premium transaction performs a number of actions including validating inputs, removing value from suspense, applying fees and charges, issuing commission, applying the money to one or more funds on the policy, and adjusting the cash value of the policy. OIPA allows insurers to configure the sequence of steps, business rules, and calculations that are performed, as well as what data is updated as a result of the transaction processing.An instance of a transaction is known as an activity. The execution of an activity involves the execution of all processing associated with its underlying transaction within a single atomic unit of work. The execution of an activity also involves the auditing of all of the changes so that they can easily be reversed or undone.In most cases, activities that are entered into the system are scheduled for execution at a later time. In a typical OIPA system, Customer Service Representatives (CSRs) may create hundreds or even thousands of pending activities during the day. These pending activities are subsequently executed during a scheduled batch process.OIPA Cycle ProcessingCycle is the component of an OIPA system that is responsible for the scheduled execution of pending activities. The activities executed by cycle are classified into different levels, where each Cycle Level determines the type of work item to be processed and the sequence of execution:•Pre-Company – process all pending company level activities that are configured to be executed before any policy activities are processed.•Pre-Plan – process all pending plan level activities that are configured to be executed before any policy activities are processed.•Pre-Client – process all pending client level activities that are configured to be executed before any policy activities are processed.•Policy – process all pending policy activities in the insurance database•Post-Client – process all pending client level activities that are configured to be executed after any policy activities are processed.•Post-Plan – process all pending plan level activities that are configured to be executed after any policy activities are processed.•Post-Company – process all company level activities that are configured to be executed after any policy activities are processed.The association of levels with activities allows business analysts to define the sequence within which policy level activities execute. An example is the importing of the latest fund unit values into the system so that policy level activities that affect cash value can be executed properly. Fund unit values wouldhave to be imported before policy level cycle can execute, because many policy level activities require the latest fund unit values in order to process successfully. Other examples are the execution of calculations for downstream reporting or exporting of data into a data warehouse. This should happen after policies are processed, as policy level processing results in the modification of a significant amount of operational data, which should be current before it is imported into a data warehouse.Challenges of Cycle ProcessingThe requirements of the OIPA Cycle system lead to inherent time and volume challenges as described in this section. The next section will describe how Oracle Coherence’s capabilities enable Cycle to meet these challenges.Time ConstraintsOIPA Cycle processing places a large demand on database and system resources and can slow down the online OIPA application. Cycle is typically scheduled to execute off business hours in order to minimize the impact to the OIPA application users. The increasing globalization of insurance companies expands the OIPA application availability and therefore shortens the time intervals that Cycle has to complete processing.High Volume ProcessingCycle activities must be able to meet varying processing volume demands with specific time constraints. There are peak periods when the volume of pending activities can be significantly greater than normal. Example peak periods include end-of-month, end-of-quarter, and end-of-year processing when many, if not all, active policies in the system have pending activities to process. During these peak periods when the number of pending activities possibly number hundreds of thousands or even millions, Cycle must still be able to meet time constraints.Powering Cycle with Oracle CoherenceA consideration of the challenges presented by Cycle requirements makes it clear that the use of a distributed computing infrastructure that allows for the parallel execution of process intensive tasks across a number of processing nodes is needed. Furthermore, the infrastructure would also need to adhere to the following additional requirements:•Fault Tolerance – The pending tasks from a failed Cycle processing node should fail over to another node and be scheduled for processing.•Scalability – The sizing requirements for the grid are different based on the customer. While some customers may be relatively small in terms of processing requirements, other customers need the ability to execute many millions of pending insurance activities in parallel.•Simplicity – The need to achieve distributed computing capability without the system being overly cumbersome and difficult to understand and setup.•Extensible – The ability to execute custom tasks•Proven – The underlying architecture must be proven at many existing production installations. After careful consideration of these requirements, the OIPA team concluded that the best approach in addressing Cycle’s demanding needs would be through the use of Oracle Coherence.Figure 3. The use of Oracle Coherence allows OIPA to achieve the challenging performance and scalability needs driven by insurers' demand for high-volume, nightly batch processing.Oracle Coherence provides a repository of projects, known as the Coherence Incubator, that represent best practices for common solutions. The Processing Pattern is a Coherence Incubator project that provides a generalized approach for the submission and asynchronous processing of work within a Coherence cluster. This makes the Processing Pattern a good fit as a foundation for a distributed computing platform. This fit, combined with OIPA’s existing and successful use of Oracle Coherence as a distributed cache, provided the basis for choosing the Processing Pattern as the foundation for the implementation for OIPA’s distributed computing needs.Distributed Computing with the Coherence Processing PatternThe Processing Pattern leverages Oracle Coherence as the connection, communication, and management mechanism to enable distribution and execution of work across a network of computers, also known as a cluster. It allows clients to submit work to the cluster, ensures that the work gets processed, and reports the results of the execution back to the client. The Processing Pattern provides aframework that allows implementers to define their own types of work to be processed and customizes how work is dispatched and processed.The Processing Pattern provides a simple interface so that clients do not have to be concerned with how work is distributed and processed. Clients of the Processing Pattern see the cluster as a single process, and are not aware of the number and types of computers that are being used.Figure 4. The Processing Pattern distributes work using a submissions cache that is partitioned across the cluster. The Processing Pattern is built on top of the clustered caching capability of Oracle Coherence. When work is submitted using the Processing Pattern, it is stored in a partitioned cache where Oracle Coherence assigns the storage for the submission to one of the nodes connected to the cluster. When the submission is stored on the node, Oracle Coherence also makes a backup copy of the submission and stores the copy on a different node in the cluster to provide failover capability in the event that one of the nodes fails. When a node fails, the submissions in the backup storage are automatically distributed among the remaining operational nodes in the cluster. This automatic failover feature of Oracle Coherence is used by the Processing Pattern to support re-dispatching of queued tasks in the event of node failure.Distributing Tasks in the Processing PatternThere are different methods of distributing work using the Processing Pattern. The method used by OIPA Cycle includes two phases: dispatching and processing. The sequence of steps for this two phase submission process is as follows:Figure 5. The Processing Pattern distributes work in two phases: dispatching and processing.•When a task is submitted to the Processing Pattern, it is bundled with a submission and stored in the submission partitioned cache. When the submission arrives at a node, an event is fired notifying registered listeners that a new submission has arrived. The Processing Pattern has a listener (the DispatchController) that is registered to receive new submission events.•The DispatchController dispatches the new submission through a set of registered Dispatchers. The registered dispatchers form a chain of dispatchers, each one capable of performing some processing on part of the incoming submission.•The DefaultTaskDispatcher is the most important type of Dispatcher used by OIPA Cycle. It consults one or more TaskDispatchPolicy instances to determine which TaskProcessors are available to process the new submission. A TaskProcessor maps to a node in the cluster that is capable of processing the Submission. One type of TaskDispatchPolicy is the attribute-matching policy, which maps a submission to a TaskProcessor based on attributes on the submission. Another type is the round robin policy, which guarantees uniform dispatching of submissions across all nodes in the cluster. OIPA Cycle uses both of these policies to route submissions to the appropriate TaskProcessors and perform round robin load balancing of work.•Once the DefaultTaskDispatcher has selected a TaskProcessor, the DefaultTaskDispatcher assigns the submission to the TaskProcessor’s work queue using a Coherence partitioned cache.•The new submission entry is received by a TaskProcessor using another registered listener on the TaskProcessor partitioned cache. The TaskProcessor can be a different node than the node thatdispatched the submission. The TaskProcessor accepts the submission and schedules it for processing by unbundling the task associated with the submission and placing the task in a thread pool.•At some point, the task is picked up by a thread from the thread pool and processed. The code that is executed is application specific, so the task can do anything that the application requires. As an example, OIPA Cycle has a type of task called the CycleTask, which is responsible for processing all pending activities on a single unit of work such as a policy.•Once the task is completed, the TaskProcessor stores the result of the task in a SubmissionResult partitioned cache. The result of processing gets transmitted to the originating client through additional event listeners.Handling Long Running Tasks with Resumable TasksA Resumable Task is a special type of task provided by the Processing Pattern that provides additional features of reporting progress, yielding, resuming, and returning a result. These capabilities make Resumable Tasks well-suited for executing long running tasks such as asynchronously executing a Web service or governing a process that takes a long time to complete like an OIPA Cycle Level. That task can then go through a sleep/wake cycle checking on the status of processing until it is complete.When a Resumable Task is executed, it can store the progress made by saving information using a checkpoint. Thus, if the Task needs to be restarted, it can start from the latest checkpoint rather than starting from the beginning. For clients that want to be informed of the progress of a Task, the progress is reported back by listening for events on that task. It can also return a special object called a Yield that indicates the task is not yet finished and needs to be re-scheduled for execution. The Yield object is used to store the intermediate state of the task, as well as specify a delay before running the task again.Figure 6. The above diagram shows the states of a Resumable Task.Scalability and High Availability in the Processing PatternThe Processing Pattern relies on the scalability and high availability capabilities provided by Oracle Coherence to scale and provide resiliency of failure to the tasks managed by the Processing Pattern. If a node crashes during execution of a task, that task is automatically restarted on another node in the cluster. Similarly, capacity can be added to the cluster without the need for stopping or reconfiguring existing nodes. As soon as a node joins the cluster, the Processing Pattern takes advantage of the additional capacity.OIPA Cycle Execution using the Coherence Processing PatternFigure 7. OIPA Cycle executes catch processing using Oracle Coherence and the Processing PatternOIPA Cycle is built on top of the Oracle Coherence Processing Pattern to enable the distributed and parallel processing of activities during the batch processing of pending activities in the OIPA system. OIPA Cycle implements the Processing Pattern framework and provides custom tasks that execute the Cycle process. There are two components to Cycle, the Cycle Client and the Cycle Agent. The Cycle Client is a simple console application that requests a Cycle Level be completed by submitting a task to the grid for processing. The Cycle Agent is a processing node that is connected to a cluster of Cycle Agents and provides the distributed computing capability for OIPA and Cycle.Cycle acts as a workload manager; the actual work of processing activities is done by the OIPA run-time. Each Cycle Agent is bundled with the same OIPA libraries that the OIPA Web Application uses and simply delegates to these libraries to process the pending activities in the OIPA system. In this sense, Cycle provides the plumbing that connects the distributed computing capability of the Coherence Processing Pattern with the activity processing capability of OIPA.Cycle uses its own queue that exists in the underlying OIPA database in order to direct the execution of a Cycle Level. The Cycle table in the database holds a record for every task that is to be processed during the execution of a single Cycle Level. For example, when running the Policy Cycle Level, each record in the table contains an identifier for a policy that has pending activities that need to be processed. Cycle maintains its own queue instead of using the Processing Pattern’s internal queue for a two reasons. First, the number of tasks that need to be executed may number in the millions; submitting millions of tasks at one time would overwhelm the grid. Second, Cycle needs to audit each task individually to support downstream reporting on the nightly batch process. Keeping the queue in the database allows Cycle to distribute manageable chunks of work to the grid for processing and persist the results of each task.Extending the Processing Pattern to Support CycleThe Processing Pattern is a purpose-built platform that enables grid computing. It leverages Oracle Coherence as the clustering technology and builds on top of it the dispatching, assignment, scheduling, execution, and management of tasks in the cluster. One of the benefits of using the Processing Pattern is the simplicity of the framework that you need to extend in order to leverage the grid computing infrastructure that it provides. The following diagram illustrates two custom task implementations:Figure 8. Cycle classes that extend the Processing Pattern are illustrated above.The only requirement to provide custom task processing for Cycle is the implementation of the ResumableTask interface. The ResumableTask interface has a single run method that passes in a TaskEnvironment and returns an Object. The TaskEnvironment object provides access to intermediate state and gives the custom task the ability to checkpoint information and report progress. The return parameter gives the ability for the custom task to return a Yield object, which moves the task into a sleep state and schedule it for future execution.The CycleProcessTask class is the Cycle task that governs the execution of an entire Cycle Level, such as Policy Level Cycle or Pre-Company Level Cycle. The CycleProcessTask class is discussed below; it is responsible for loading the Cycle queue in the database and replenishing the grid with work until the Cycle Level is complete.The CycleTask class is responsible for processing all of the pending activities on a unit of work, (for example, a single policy). When a CycleTask object completes processing, it updates a record in the Cycle table with the results.Using the Processing Pattern to Submit TasksThe Processing Pattern provides a simple service facade called the ProcessingSession that is used to submit tasks to the grid for processing. The ProcessingSession supports different ways of waiting for the results of a task to complete, including blocking for the task to be finished (synchronous) or receiving event notifications (asynchronous).。
oracleEBS中英词汇对照表
Oracle ERP 中英对照词汇表Aaccount hierarchy（帐户分层结构）Oracle 财务系统的一种特性，您可以用来执行汇总层资金检查。
采用帐户分层结构，Oracle 采购管理系统和总帐管理系统可以快速确定明细帐户累计成的汇总帐户。
Account segment（帐户段）会计弹性域多达30 个不同节中的其中一个，这些节一起构成您的总帐帐户代码。
段与段之间通过一个您所选定的符号（如-、/ 或\）分开。
每一个段通常表示业务结构的一个要素，如公司、成本中心或帐户。
Account segment value（帐户段值）定义特定值集唯一值的一系列字符和说明。
account structure（帐户结构）请参阅：会计弹性域结构accounting calendar（会计日历）Oracle 总帐管理系统中定义会计期和会计年度的日历。
您可以使用“会计日历”窗口来定义会计日历。
Oracle 财务分析程序可以使用会计日历自动创建“时间”维。
Accounting Flexfield（会计弹性域）用于标识Oracle 财务应用产品中的总帐帐户的代码。
每个会计弹性域段值与科目表中的一个汇总或累计帐户对应。
Accounting Flexfield structure（会计弹性域结构）为满足组织的特定需要而定义的帐户结构。
您可以在会计弹性域结构中选择段数及每个段的长度、名称和顺序。
Accounting Flexfield value set（会计弹性域值集）一组值以及这一组值的属性。
例如，您为帐户段指定用于标识业务特定要素的值长度和值类型（如公司、分部、区域或产品）。
ad hoc（即席）与特殊用途相关并应用于特殊用途。
例如，即席税码或即席数据库查询。
aggregate balance（汇总余额）天数范围内的日终余额总和。
有三种汇总余额类型：期初至今(PTD)、季初至今(QTD) 和年初至今(YTD)。
所有这三种类型余额均存储在每个日历日的总帐管理系统数据库中。
oracleerp全模块中英文对照完整资料
【最新整理，下载后即可编辑】Oracle ERP全模块中英文对照财务系统模块：Oracle 总帐管理（GL） General LedgerOracle 应付帐管理（AP） ACCOUNT PAYERBLEOracle 固定资产管理（FA）Fixed AssetsOracle 应收帐管理（AR）ACCOUNT RECEIVABLE Oracle 现金管理（CE）Cash EntryOracle 项目会计（PA）project accountingOracle 财务分析（。
尸人）Oracle Financial Analyzer分销系统模块：Oracle 库存管理（INV） Inventory ManagementOracle 采购管理（PUR）PurchasingOracle 销售定单管理（OE）Order EntryOracle 销售&市场管理（SM） Sales ManagementOracle 销售补偿管理（SC）Sales CompensateOacle 售后服务管理（SR）Service RequestOracle 销售分析（。
5人）Oracle Sales Analyzer制造系统模块：Oracle 计戈| 管理（ MPS/MRP ）Mster Production Schedule / Material Requirement Planning Oracle 能力计划管理（CAP） Capability planningOracle 制造数据管理（BOM）Bill of MaterialOracle 车间生产管理（WIP） Work in ProcessOracle 成本管理（CST） Cost ManagementOracle 项目制造（PJM） Project Manufacturing Management Oracle 质量管理（QM） Quality Management其他系统模块：Oracle 设备管理（EM） Equipment Management【最新整理，下载后即可编辑】Oracle 人事管理（HR） Human ResourceOracle 薪金管理（PAYROLL） PayrollOracle 系统管理（SYSTEM ADMIN） System AdminstratorOracle 预警（ALT）AlertOracle多维数据分析/商业智能系统（OLAP/BIS）Online Analytical Processing / busi ness intelligence systemOracle 桌面集成（ADI）Application desktop integrator DRP 分销资源计划Distribution Resource Planning CRP 能力需求计划I Capacity Requirement Planning\Oracle ERP全模块中英文对照财务系统模块：Oracle总帐管理（GL）Oracle应付帐管理（AP）Oracle固定资产管理（FA）Oracle应收帐管理（AR）Oracle现金管理（CE）Oracle项目会计（PA）Oracle财务分析（。
oracle11 科目明细表
一、引言在企业财务管理中，科目明细表是非常重要的财务报表之一。
它对企业的资金流动、资产负债情况等进行了详细的分析和总结，是财务决策的重要依据。
本文将针对oracle11科目明细表的内容和功能进行详细分析，为读者深入了解该财务报表提供参考。
二、oracle11科目明细表的基本概念1.1 科目明细表的定义科目明细表是企业会计报表中的重要内容之一，它主要记录了公司在特定时间段内的所有会计科目的明细数据，包括资产、负债、所有者权益、收入、成本和费用等方面的数据。
1.2 科目明细表的功能科目明细表通过对财务数据的详细分析，反映了企业在特定时间段内的经营状况和财务状况。
它不仅可以为企业管理者提供重要的经营决策依据，还可以为外部利益相关者提供了解企业财务状况的重要参考。
三、oracle11科目明细表的构成要素2.1 核算要素科目明细表的构成要素主要包括科目代码、科目名称、本期发生额、本年累计发生额、期初金额和期末金额。
通过这些要素，可以全面、清晰地了解企业在特定时期内各项财务指标的变化情况。
2.2 科目分类在科目明细表中，会计科目通常按照资产、负债、所有者权益、收入、成本和费用等方面进行分类，以便更好地进行财务数据的管理和分析。
四、oracle11科目明细表的编制流程3.1 数据采集科目明细表的编制首先需要进行数据采集工作，即收集企业在特定时间段内所有会计科目的详细数据，包括资产、负债、所有者权益、收入、成本和费用等方面的数据。
3.2 数据处理在完成数据采集后，需要进行数据处理，包括数据汇总、分类、整理和计算，在这个过程中需要保证数据的准确性和完整性，以便最终形成科目明细表。
3.3 报表编制根据数据处理的结果，编制完整的科目明细表，确保表格的格式清晰、内容完整、逻辑严谨，同时需要注明报表的编制单位、日期等信息。
五、oracle11科目明细表的应用价值科目明细表作为企业重要的财务报表之一，对于企业的经营决策和管理具有重要的应用价值。
oracle-ERP系统-中英文名词对照-po中文翻译
oracle-ERP系统-中英文名词对照-po中文翻译PO(Purchasing Order—采购管理)中文翻译Auto Create 自动产生采购或请购单Approvals 核准Approval Groups 签核群组Attachments 附带图片或文件Aliases 别名Blanket Orders 合并式采购Cross-Validation 交叉确认Category Sets 料品种类集Category Codes 种类代码Corrections 修订Contracts 合约式采购Customer Item Commodity Code 商品代码Default Category Sets 定义料品种类集Delete Constraints 删除限制Delete Items 删除料号Flexfields 弹性字段Freight Carriers 运送Forward Documents 文件移转Hazard Classes 危险产品类别IR (Internal Requisitions) 内部请购Item Relationships 料品关系Item Search 料品寻找Lookup Code 供货商查询码(维护供货商list of value) Mass Cancel 大量取消Master Items 主要料品Match Unordered Receipts 补货单Notifications Summary 需签核数据摘要PO 采购单PR (Purchasing Requisitions) 外部请购Planed Orders 计划式采购Purge 清除Quick Codes 快速码Quality Inspection Codes 质量检验码Quotations 报价单Request for Quotation 询价Requisitions (REQ) 请购单Receiving Transactions Summary 收货异动摘要Releases 释出Supply Base 供货商基本数据库Supplier 供货商Supplier Merge 供货商合并Supplier Statuses 供货商状态Sourcing Rules 各类条件规则Validation 确认。
银行管理会计系统ORACLE解决方案ppt
促进业务流程优化
Oracle解决方案支持灵活的业务 流程定制和调整，有助于银行优 化管理会计相关流程，提升整体 运营效率。
收益分析
降低成本支出
通过实施Oracle解决方案，银行可降低在硬 件、软件及人力等方面的成本支出，实现资 源的优化配置和高效利用。
提高决策准确性
该解决方案提供全面、准确的管理会计信息，有助 于银行管理层做出更科学、合理的决策，推动银行 业务发展。
06
应对措施
加强网络安全管理，采用防火墙、入侵检测等 安全措施，对数据进行加密存储和传输，确保 数据安全。
数据风险及应对措施
数据准确性风险
数据输入错误或处理不当可能导致数据不准 确，影响银行决策和业绩评估。
应对措施
建立完善的数据校验和审核机制，对数据进行 定期核查和清理，确保数据准确性。
数据一致性风险
银行管理会计系统 Oracle解决方案
目录 CONTENT
• 引言 • OБайду номын сангаасacle解决方案概述 • 银行管理会计系统现状分析 • Oracle解决方案在银行管理会计
系统中的应用
目录 CONTENT
• Oracle解决方案的实施效果与收 益分析
• Oracle解决方案的风险与应对措 施
• 总结与展望
缺乏专业的Oracle数据库管理人员可能导致系统运维困难 。
应对措施
加强人员培训和技能提升，引进具有Oracle数据库管理经 验的专业人才，确保系统运维水平。
人员流动风险
关键岗位人员流动可能影响系统的稳定性和连续性。
应对措施
建立完善的人员交接和培训制度，确保关键岗位人员流动 不会对系统造成严重影响。同时，积极培养后备人才，降 低人员流动带来的风险。
oracle-ERP系统-中英文名词对照-fa中文翻译
FA (Fixed Asset—固定资产)中文翻译Asset System 资产系统Asset Categories 资产种类Fiscal Years 会计年度Prorate Conventions 分摊惯例Asset Keys 资产键值Price Indexes 物价指数Adjusted Current Earnings 调整本期盈余Run Exception Reports 执行异常报表Populate ACE Book 更新ACE账簿Aliases 别名Assets 资产Asset Workbench 资产工作台Capitalize CIP Assets 资本化CIP资产Set Extended Life 设定延长年限Concurrent 并行处理CIP 在建工程Inquiry 查询Transaction History 交易历史记录Depreciation 折旧Bonus Rules 红利准则Ceilings 上限ITC Rates 投资扣抵率ITC Recapture Rates 投资扣抵率抵减率Depreciation 折旧Projections 规划Deferred 递延Flexfields 弹性字段Leases 租赁Distribution Sets 科目分配集Mass Transactions 整批交易Transfers 移转Revaluations 重估Retirements 报废Purge Data 资料清除Profile 前制档Physical Inventory 库存Tax 税捐Tax Workbench 税捐工作台Initial Mass Copy 初始整批复制Periodic Mass Copy 定期整批复制Mass Deprecation Adjustments 整批折旧调整Segments 节段Upload 上载UOM (Units of Measure) 单位。
Oracle词汇中英对照表
Oracle词汇对照表Bill-To 开票至Financial Options 财务选项Serial 序列号Supplier Lot 供应商批号Secondary 从属Aliases 别名Created 创建日期Currency Unit Price 外币单价Stock Locators 库位AutoCreate 自动创建View Plan 查看计划View Label Requests View Label Requests Reserved 被保留Order Organizer 订单管理器Lines/LPNs 行/LPNsNew 新建Shipment 发运Supplier 供应商Order Date 订单日期Qty Cancelled 取消数量Order Source 订单来源- Organizations - 组织- Import - 导入Source Details 来源明细GE Standard Cost Update GE Standard Cost Update Export Cycle Count Entries 导出循环盘点录入Auto-pack 自动包装+ Supply Chain Plan + 供应链计划Related Items 关联物料Notifications 通知Corrections 更改View Cost Update 查看成本更新- Kanban - KanbanSchedule Ship Date 计划发运日期- Customer Items - 客户物料Order Information 订单信息- Financials - 财务Buyer 采购员Approve 审批Requester Workbench 请购单汇总Orders and Return Menu 订单和退货Transfer Subinventory 转移子仓库Generate Serial Numbers 产生序列号Lot 批号Pending Purchase Order Changes Pending采购订单更改Line Status 行状态Reorder Point Planning 再订购点计划Reservations Interface Manager 保留接口管理Sourcing 来源Rate 汇率Details 明细+ Setup + 设置Releases 发放- Open Interface - 开放接口Miscellaneous Transaction 杂项事务处理Supplier Sourcing 供应商来源Primary 基本Orders 订单Tag Counts 标签盘点Material Transactions 物料事务处理Shipment Number 发运号码Position Hierarchy 职位层级Related PO Number 关联的PO单ABC Assignment Groups ABC分配组Ship Set 发运集Select 选择Deliveries 发运Run Requests 执行请求- Supplier User Creation - Supplier User Creation Customer Items 客户物料Change Organization 更改组织Find (J) 查找Document Type 单据类型Workflow Background Engine 工作流后台引擎Purge Cost Update History 清除成本更新历史纪录Salesperson 销售人员Move Order Line Number 物料搬运单行号码Document 单据Main 主Average Cost Update 平均成本更新Personal Profiles 个人配置文件User Item Type 物料类型Ordered Item 销售物料Destination Subinv 目标子仓库Serial Numbers 序列号Price List Setup 价目表设置Total 金额Date Ordered 订单日期Attachments 附件Imp Qty/Rate 实施数量Shipping Method 发运方式Rev 版本Line Number 行号码- Reports, Requests - 报表，请求Approved 已审核Default Category Sets 默认分类集Items 物料+ Management + 管理Warehouse 仓库On-hand 现有量Configurator 配置+ Collections + 数据收集Costing 成本Date 日期Ready to Release 准备挑库Make or Buy 制造或购买Error Code 错误代码Transaction Menu 事务处理菜单Numbers 号码- Release Sales Orders - 销售订单发放/挑库Closed 关闭Tools 工具Counts 盘点Approve Adjustments 审核调整Num 编号Purchase Order Summary 采购订单汇总WF Notifications WF通知Returns 退货Copy 拷贝Calendars 工作日历Unit Selling Price 单价P-Card P-CardNotifications Summary 通知汇总- Counting - 盘点Unit Cost 单位成本- Customers - 客户Requisitions 请购单Purchase Order 采购订单View Cost History 查看成本历史Quote Analysis 报价分析Item Name 物料名称Control 控制Automatic 自动Organizations 组织Implement Date 实施日期Requisitions 请购单Supply/Demand 需求/供应Requisition 请购单Serial Numbers Entered 序列号输入Requested Qty 需求数量Backordered Qty Backordered数量Incomplete 未完成Move Order:Transact Move Orders 物料搬运单：执行物料搬运单Serial Number 序列号Control Purchasing Periods 控制采购期间Outside Services 外协加工Display 显示Deliver to Location Deliver至Requested Dates 需求日期Build 创建Jobs 工作Freight Code 运输代码Qty Shipped 发运数量Quantity 数量Document Set 文档集Transactions:Miscellaneous Transaction 事务处理:杂项事务处理- Move Order - 物料搬运单- Costs - 成本Subinventory 子仓库Destination 目的地Purge Cost Information 清除成本信息Transaction Quantities 事务处理数量Destination Type 目标类型Notifications 通知Templates 模版+ Counting + 盘点Available 可用量Item Supply/Demand 物料供应/需求- Cost Mass Edits - 成本批量编辑Tax 税+ On-hand, Availability + 现有量, 可用量Cycle Counts 循环盘点Notification Summary 通知汇总Unit Price 单价Preparer 提交者Releases 发放Change Organization 切换组织- Transactions - 事务处理Org Code 组织代码Supplier List 供应商列表Buyer Workbench 采购单汇总Exceeded Price Tolerances 超过价格允差Org 组织Promised 承诺日期Edit 编辑Supplier Item 供应商物料Notification List 通知列表Rate Type 汇率类型Transactions 出货交易Project 工程Reason, Reference 理由，备注Transaction Open Interface 事务处理开放接口Creation Status 创建状态+ Supply Base + 供应商基础Supplier Item Catalog 供应商物料目录Account 账户Transactions Status Summary 事务处理状态汇总Tag Generation 标签生成Source 来源Description 描述Transact 执行Order Type 订单类型Copy Cost Information Copy成本信息Deviation Factor - 偏离-Bills of Material BOMClose 关闭Item Types 物料类型Lines 行Purchasing Org 采购组织Exceptions 例外- Receiving - 接收事务处理Sales Orders 销售订单Ship From 发货从Receipts 接收Created By 创建者Ship-To 发运至Contact 联系人Default Stage 默认StageSupplier List Name 供应商列表名称Open... 打开...Freight Terms 运费条件New PO 新建采购单Receiving Options 接收选项Line Qty 行数量Document Types 单据类型View Plan Options 查看计划选项Destination Account 目标科目Requisition Summary 请购单汇总Site 地点Action 动作Material Transactions (TOM) 物料事务处理（ＴＯＭ）Positions 职位Setup 设置Type 类型+ Sourcing + 来源AutoCreate 自动创建Criteria 标准Pending Status Pending Status- Planning - 计划Calendar 日历Summary Approved Supplier List 合格供应商列表汇总- Purchasing - 采购Source Supplier 来源供应商- Transactions - 事务处理Daily Rates 日汇率Payment Terms 付款条件+ Shipping + 出货+ RFQ's and Quotations + 询价和报价Cancel 取消New Date 新日期Transactions: 事务处理:On Hand 现有量Notifications Summary 通知汇总On-hand Quantity 现有量Pick and Ship 挑库和发运Others 其他- Reports - 报表Shipping Menu 发货Project and Task 项目与任务- Items - 物料Primary UOM 基本单位Catalog... 目录...Manage Shipments Manage ShipmentsImport Items Import ItemsApproval Assignments 审批分配Subtotal 子合计OK 确定Allocate 分配Work Order 工单Start Date 开始日期Options 选项Category 分类- On-hand, Availability - 现有量/可用量+ ABC Codes + ABC代码Inventory Accounting Periods 库存会计期间Line Information 行信息Names 名称RFQ's 询价Documents 文档Lots 批号+ Requisitions + 请购单Availability 可用量Miscellaneous Transaction (TOM) 杂项事务处理(TOM)Find (B) 查找Demand History 需求历史Agreement 协议PO, Rev PO单号，版本Long Description 长描述Status Codes 状态代码New Release (B) 新建发放Borrow Payback Transactions Borrow Payback Transactions Item Search 物料查询Date Ranges 日期范围Supplier Merge 供应商合并+ Orders, Returns + 订单，退货Transactions:Subinventory Transfer 事务处理:子仓库转移+ Release Sales Orders + 销售订单发放/挑库Reservations 保留Pick Release 挑库View 查看- Shipping - 出货Purchase Order 采购订单Classes 分类Purchase Orders 采购单Item Information 物料信息Find Move Order Lines (TOM) 查询物料搬运单行(TOM)Help 帮助Subinventory Transfers (TOM) 子仓库转移(TOM) Next Step 下一步Segments 截段Order Number 订单号码Lot / Serial 批号/序列号Ship To 发货至- Items - 物料Price Reference 价格参照Receiving 接收Line Items 行信息Scheduled Ship Dates 计划发运日期Supplier Statuses 供应商状态Line 行Sales Person 销售人员Reference 参考Window 窗口Shipped Qty 发运数量Allocations 分配Move Order Type 物料搬运单类型Actions 操作Purchasing 采购Both Both- Sourcing - 来源+ Items + 物料Based On Rule 基于规则Planning Transfer 计划转移Purchase Orders 采购订单- Personnel - 人员GL Date 总帐日期Material Distributions 物料分录Note to Buyer 通知采购员Transact Move Orders (TOM) 执行物料搬运单(TOM) Create 创建Reference Documents 参考文档Purge 清除From 从Category Sets 分类集Source 来源Transaction Dates 事务处理日期Run 执行Resource Supply 资源供应Quotations 报价ABC Classes ABC分类Shipping 发运Approval 审批File 文件- Item Onhand, Availability - 物料现有量，可用量+ Purchase Orders + 采购订单Category Set 分类集Safety Stocks 安全库存Requester 请购人员Shipping:Transactions 发运：事物处理Movement Statistics 移动统计Reservations Interface 保留接口Transaction Type 事务处理类型Book Order 登记订单Move Order Number 物料搬运单号码Ordered 已下单Customer Contact 客户联系人Currency 币种Reference Num 参照号码Sugg Due Date 建议日期Period Types 期间类型Returns 退货- Accounting - 帐户Request Date 需求日期Intransit 在途+ Receiving + 接收事务处理Subinventory Transfer 子仓库转移Receiving Controls... 接收控制...Inter-organization Transfer 组织间转移Units of Measure 单位Date Required 需求日期RFQ Required 询价单需要Approve Counts 审批盘点Open 打开Item Relationships 物料关系Ship to 发货至Receipts 接收Purchasing Options 采购选项- Move Order - 物料搬运单Define 定义Item Description 物料描述Order 订单Mass Edit Cost Information 批量编辑成本信息Unit of Measure 单位Late 延迟交货Manual Requests 手工请求Line Types 行类型Purge Cycle Count InterfaceData 清除循环盘点接口数据UOM 单位Results 结果Sales Order Num 销售订单号码- Manufacturers' Part Numbers - Manufacturers' Part Numbers Shipping Transactions Form 出货事务处理界面New Quote 新报价Update Costs 更新成品- Flexfields - 弹性域- Cycle Counting - 循环盘点Need-By 需要日期+ Accounting Close Cycle + 会计期间关闭Customer Number 客户编号Find... 查找...Reports 报表Urgent 紧急Category Codes 分类代码More 更多+ Planning + 计划Sales Order Number 销售订单号码Transact Move Orders 执行物料搬运单New Qty 新数量- Replenishment Counts - Replenishment CountsPO,Rev 采购单Go (B) 执行(B)Sales Order 销售订单Approval Groups 审批组Price 价格Suppliers 供应商Import Cost From Price List Import Cost From Price List Assigned 已分配Status 状态Source Types Source TypesCustomer Name 客户名称Currencies 币种Headers 头New Order 新订单Subinventories 子仓库- Set of Books - 帐套Min-Max Planning 最大最小量计划Sourcing Supplier Site 来源供应商地点Distributions 分录OM Sales Orders 订单管理Subinventory Transfer (TOM) 子仓库转移(TOM)Inquiry/Update OpenInterface 查询/更新开放接口Delete... 删除...Terms 条件Counts 盘点Release Date 发放日期Price List 价格列表Item 物料Need-By Date 需求日期Source Subinv 来源子仓库Supplier Site 供应商地点Requisition Number 请购单号码Receiving Transactions 接收事务处理Line Total 行总计Lines (B) 行(B)Currency... 币种...Number 编号Top Ten List Top Ten列表Organization Items 组织物料Shipments 发运Ship Method 发运方式- Movement Statistics - 移动统计Run Reports 执行报表Transaction Types 事务处理类型ABC and Counting ABC和计划Pick Slip Number Pick Slip号码Task 任务Transact Move Orders 执行物料搬运单View Items 查看物料Standard 标准Phone 电话Execute Now 立即执行Move Orders (TOM) 物料搬运单(TOM)Period 期间- Receiving - 接收GE Transfer Price Update Details GE转移价格更新明细- Units of Measure - 单位- Standard Cost Update - 标准成本更新Conversions 装换Import Source 导入来源Update Item Assignments 更新物料分配Clear 清除Safety Stock Update 安全库存更新Equals 等于Go 执行Requests 请求Containers 容器Choose 选择Functions 功能- Physical Inventory - 实地盘点Service Total 服务总计To Subinv 至仓库Sourcing Rules 来源规则Bill To Location 开票至- Price Lists - 价目表Release Sales Orders 销售订单发放/挑库Transaction 事务处理Physical Inventory 实际盘点Waybill/Airbill 货运单Summary 汇总Ship To Location 发运至- Currency - 币种Source Type 来源类型- RFQ's and Quotations - 询价和报价Pricing 价格Move Orders 物料搬运单Qty/Rate 数量Save 保存Order Management 订单管理Open and Close periods 打开关闭期间Customer 客户Folder 文件夹Rate Date 汇率日期Payment Terms 付款条件Resource Name 资源名称Documents DocumentsQty 数量- Requisitions - 请购单Requisition Templates 请购模版Not Shipped 未发运的Transaction Date 事物处理日期- ABC Codes - ABC代码Import Cost Information 导入成本信息Item Search 物料查询Concurrent 并行运行Asset Management 资产管理Grouping 分组Quote/Order Information 订单信息Receiving Transactions 接收事务处理From Order Number 从订单号码- Supply Base - 供应基础Item Costs 物料成本To 至Ship from 发货从- Inventory Positions - 库存PositionsRelease 发放Invoice To Location 开票至+ Transactions + 事务处理Planning 计划Manual 手工Expires On 过期- Supply Chain Plan - 供应链计划Internal Item 内部物料- Approvals - 审批Mass Edit Item Accounts Mass Edit Item Accounts Need-By Days from Today 从今天开始的需求日期Employees 员工Attribute Controls 属性控制Transact Move Orders 执行物料搬运单ABC Compiles ABC编译Freight Carrier 货运商Snapshot Complete? 快照完成Transaction Summaries 事务处理汇总Catalog Groups 目录组Pending Transactions Pending事务处理- Move Orders - 物料搬运单Related Documents 关联单据- Setup - 设置Release Properties 发放属性Defaulting 默认Assembly 装配件View Receiving Transactions 查看接收事务处理Supplier Lists 供应商列表Assign Sourcing Rules 分配来源规则Locations 地点View Collected Data 查看数据收集To Order Number 到订单号码- Collections - 数据收集Creation 创建Transaction Lines 事务处理行To Locator 至库位Approved Supplier List 合格供应商列表（ASL）Category Accounts 分类科目Charges 费用- Accounting Close Cycle - 会计期间关闭Transaction 事务处理Delivery 发运Ship Confirm 出货确认Cross References 交叉参照- Purchase Orders - 采购订单Primary Quantity 基本数量Item specific 物料明细Conversions 转换Item Status 物料状态Deviation Factor + 偏离+Shipping Transactions 出货事物处理Organization 组织- Forecasts - 预测Launch 运行Line Type 行类型Buyers 采购员Subinventory Transfer 子仓库转移- Costs - 成本Amount 金额Import Cycle Count Interface Data 导入循环盘点接口数据Item, Rev 物料+ Reports + 报表Workbench 工作台Approve... 审核...Condition 条件Requests 请求Customer PO 客户PO号Detail... 明细...Tracking 跟踪- Orders, Returns - 订单，退货- Key - 值Interface Managers 接口管理View/Update Allocations 查看/更新分配+ Costs + 成本Chargs 费用Accounts 帐户Revision 版本Receiving Org 接收组织Source Org 来源组织Location 地点Ship-to Org 发运至组织AutoCreate Documents 自动创建Physical Attributes 物理属性+ Receiving + 接收Pick From 挑库从On-hand 现有量Master Items 主物料Manage Deliverables Manage Deliverables Find 查找Inventory 库存View Potential Shortage 查看潜在的短缺量Assign Items 分配物料Physical Inventories 实地盘点- Categories - 分类Organizations 组织Default 默认Set $$ 集Launch Pick Release Form 挑库和发放Move Orders 物料搬运单Cycle Count Entries 循环盘点录入Locator 库位Operation Department 操作部门Emergency PO Number 紧急PO单号+ Kanban + KanbanReason 原因Mult-organization Quantity 多组织数量- Pricing - 价格+ Move Orders + 物料搬运单Shipped 已发运。
Oracle保险收入管理和收据系统说明书
Oracle Insurance Revenue Management and Billing The healthcare industry is in the midst of aseismic change. Increasing cost pressures,a shift towards individual plans andcoverage and the continuing uncertaintysurrounding healthcare reform is drivingpayers to lower their costs and theircompetitive position. Oracle InsuranceRevenue Management and Billing is anadaptive, flexible solution that addresseschallenges of healthcare payers - reducingadministrative overhead while improving service to plan membersOPTIMIZE MEMBER SERVICE AND PROFITABILITY Oracle Insurance Revenue Management and Billing for healthcare payers is built on adaptive, configurable business rules—letting you quickly change your billing operations as your business needs dictate. The application gives you the flexibility to help you keep pace with dynamic market shifts, support new products, and complywith new regulations as they arise. With Oracle Insurance Revenue Management and Billing, you can:•Support individual coverage and manage high-volume billing for the growing individual market segment.•Support multiple products and services for direct, small, medium, or large group payers•Provide revenue optimization through AR consolidation across coverage lines of business.•Create a single, consolidated bill showing all of member’s coverage s•Configure the system to handle ASO billing processes, as well as manage fees and adjustments associated with ASO and stop loss Key BenefitsAutomated billing for reducedprocessing costsBetter, more efficient serviceto employers, providers, andmembersImproved member andprovider satisfactionImproved revenuemanagement and cash flow Cost savings and riskoptimizationOperational ease withworkflow based ability tosetup customer policystructures•Support level funding and discounted pricing that reduces risk and provides cost savings.•Provide member reconciliation capabilities for self billed customers •Improve billing accuracy for large group bills and list bills•Gain flexibility in application of charges based on pricing rules•Define and store premium pricing for a policy plan offered to the fullyinsured group customers.•Support premium pricing methods such as – age-banded and tier-based pricing•Gain workflow-based ability to setup customer structures- billing hierarchy, invoicing accounts, policies, and plans.•Enable calculation of premium based on life change events•Generate manual invoice request for regular invoice, automatic invoice request for policy events, and manual invoice request generation forperforma invoice i.e., trial bill.•Access the Bill Information Portal to view bill details and drill down to the transaction level and calculate details for bill segments corresponding to selffunded policies or to the membership level for premium billing.•Leverage the Audit Event Portal to view and track the audit events and drill down to the repricing request and corresponding calculations.•Use the Repricing Request Portal to view and track the repricing requests and drill down to the calculations.REPLACE YOUR LEGACY SYSTEM WITH A MODERN ENTERPRISE SOLUTIONOracle Insurance Revenue Management and Billing for healthcare payers lets you choose the options to tailor the system to your needs. Configuration tables help you implement changes in hours rather than weeks or months, greatly reducing expensive and time-consuming code changes. With the majority of processes determined by business rules, rather than core code, configurations are maintained throughout the upgrade process, making updates faster and less painful.Improve Plan ManagementWith Oracle Insurance Revenue Management and Billing for healthcare payers, you can:•Automate payroll deduction•Process high-volume group bills and list bills with utmost precision•Perform speedy reconciliation and reduce manual processing•Improve member support via web-based, self-service optionsLower Your CostsOracle Insurance Revenue Management and Billing helps healthcare payers streamline and automate their back-end operations, you can:•Offer self-service options to reduce bill inquiries, back-office activity, field audits and bill adjustments•Integrate with existing policy administration, accounting, and payment systems to improve enterprise revenue management and cash flow •Minimize the costs to change premiums, products, and services•Utilize built-in business intelligence and reporting capabilities to uncover further potential for operational efficiencies Key FeaturesConfigurable business ruleshelp you quickly changebilling processes as needed Supports group billing, list billprocessing and individualbillingSupports ASO billing includingsetting complex multi-levelgroup structure, loading dailypaid claims, calculation of feesand discounts, stop losscalculation (both individualand aggregate)Scale to support high volumebilling environmentsSupports electronic billpresentment and processing Commission calculationSupports for level funding anddiscounted pricing.Calculates and storespremium pricing for fullyinsured group customers.Enables premium calculationbased on life change events.Related ProductsOracle Health InsuranceEnterprise RatingOracle Health InsuranceSolutionsOracle Documaker EnterpriseEditionCONNECT WITH USCall +1.800.ORACLE1 or visit .Outside North America, find your local office at /contact./oracle /oracleCopyright © 2023, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0120 Scale As Your Business GrowsAs your organization’s billing volume expands, Oracle Insurance Revenue Management and Billing scales with you to:• Handle all sizes of groups and membership• Support new forms of coverage/products easily•Add customers one at a time or in large groups typical of acquisitionsRAPID DEPLOYMENT AT LOWER COSTOracle has developed a ready to deploy preconfigured workflow and templates to get you live at an accelerating rate with Oracle Insurance Revenue Management and Billing, at lower costs and with less internal impacts. Oracle Insurance Revenue Management and Billing is easily scalable to handle the inevitable increases in data and transactions through acquisitions, international expansion, and/or the addition of new business models and product assortments. It can be deployed on premise or on the cloud.。
Oracle 保险收入管理与账单分析版2.7.0.0.0 许可指南（修订版1.3 E63607-01
Oracle® Insurance Revenue Management and Billing AnalyticsVersion 2.7.0.0.0Licensing GuideRevision 1.3E63607-01May, 2018Oracle Insurance Revenue Management and Billing Analytics Licensing GuideE63607-01Copyright NoticeCopyright © 2018, Oracle and/or its affiliates. All rights reserved.Trademark NoticeOracle, Java, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.License Restrictions Warranty/Consequential Damages DisclaimerThis 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 de-compilation of this software, unless required by law for interoperability, is prohibited.Warranty DisclaimerThe 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.Restricted Rights NoticeIf this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:U.S. GOVERNMENT RIGHTSOracle programs, including any operating system, integrated software, any programs installed on the hardware, documentation, and/or technical data delivered to U.S. Government end users are “commercial computer software” or “commercial technical data” 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, documentation, and/or technical data shall be subject to license terms and restrictions as mentioned in Oracle License Agreement, and to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). No other rights are granted to the U.S. Government.Hazardous Applications NoticeThis software 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 in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.Third Party Content, Products, and Services DisclaimerThis software 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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.PrefaceAbout This DocumentThe Licensing Guide provides the complete list of Oracle Insurance Revenue Management and Billing Analytics licensed products and the Third-Party licenses included with the license. It provides the product-wise licensing options and rules in terms of prerequisite licenses and the included license components. It does not cover the features and functionality of the products.If you have any question about your licensing needs, please contact your Oracle sales representative or contact the License Management Services representative listed at this URL:/us/corporate/license-management-services/index.htmlIntended AudienceThis guide is intended for all purchasers of Oracle Insurance Revenue Management and Billing Analytics. Organization of the DocumentThe information in this document is organized into the following sections:Section No. Section Name DescriptionSection 1 Oracle Insurance RevenueManagement and BillingAnalytics Licensing Describes the Oracle Insurance Revenue Management and Billing Analytics licensing details including:∙Separately licensed prerequisite products∙Components included∙Restricted use licensing∙General licensing informationAppendix A Third-Party Licenses Includes licensing and copyright information for third-party products included with the Oracle InsuranceRevenue Management and Billing Analytics application.Related DocumentsYou can refer to the following documents for more information:Document DescriptionOracle Revenue Management and Billing Analytics Installation Guide Lists the pre-requisites, supported platforms, and hardware and software requirements for installing the Oracle Revenue Management and Billing Analytics application. It also explains how to install the Oracle Revenue Management and Billing Analytics application.Document DescriptionOracle Revenue Management and Billing Analytics Security Guide Describes how to configure security for Oracle Revenue Management and Billing Extractors and Schema and Oracle Revenue Management and Billing Analytics.Oracle Revenue Management and Billing Analytics Functional Overview Guide Lists and describes the key features of Oracle Revenue Management and Billing Analytics. It also describes the features available in the Administration UI and Dashboards.Change LogRevision Last Update Updated Section Comments1.0 March 2017 Migrated for ORMBA2.3.0.0.0 1.1 June 2017 For ORMBA 2.3.1.0.01.2 December 2017 For ORMBA2.6.0.1.01.3 May 2018 For ORMBA2.7.0.0.0Contents1. Oracle Insurance Revenue Management and Billing Analytics Licensing (1)1.1 Oracle Insurance Revenue Management and Billing Extractors and Schema (1)1.1.1 Separately Licensed Prerequisite Products (1)1.1.2 Components Included (1)1.1.3 Restricted Use Licensing (1)1.1.4 General Licensing Information (2)1.2 Oracle Insurance Revenue Management and Billing Analytics (2)1.2.1 Separately Licensed Prerequisite Products (2)1.2.2 Components Included (2)1.2.3 Restricted Use Licensing (2)1.2.4 General Licensing Information (2)1.2.5 Third Party Products Used (3)Appendix A : Third-Party Licenses (4)A.1 JQuery (4)A.2 jQueryUI (4)1. Oracle Insurance Revenue Managementand Billing Analytics LicensingThis section includes licensing information for the Oracle Insurance Revenue Management and Billing Analytics application.1.1 Oracle Insurance Revenue Management andBilling Extractors and SchemaOracle Insurance Revenue Management and Billing Extractors and Schema is a ready data mart, which enables customers to slice and dice data to define reports.It is used to extract and transform the data into target ‘stars’ that can be used to drive reports and answer business questions from the data within the Oracle Revenue Management and Billing source system.1.1.1 Separately Licensed Prerequisite ProductsThe following prerequisite products require separate licenses:∙Oracle WebLogic Suite or Oracle WebLogic Suite for Oracle Applications∙Oracle Data Integrator Enterprise Edition or Oracle Data Integrator Enterprise Edition for Oracle Applications∙Oracle GoldenGate or Oracle GoldenGate for Oracle Applications∙Oracle Applications Management Pack for Oracle GoldenGate1.1.2 Components IncludedThe following table describes the components included with a license for Oracle Insurance Revenue Management and Billing Extractors and Schema:Licensed Program Product or Component Included with LicenseNot applicableOracle Insurance Revenue Management andBilling Extractors and Schema1.1.3 Restricted Use LicensingOracle Insurance Revenue Management and Billing Extractors and Schema product contains all or portions of the following Oracle products:Product or Component Available FeaturesNot applicable1.1.4 General Licensing InformationOracle Insurance Revenue Management and Billing Extractors and Schema can be licensed with the $M in Application Annual Revenue metric or with the 1K Insurance Plan Members metric.1.2 Oracle Insurance Revenue Management andBilling AnalyticsOracle Insurance Revenue Management and Billing Analytics is a pre-built set of ‘rich’ dashboards and reports that deliver intuitive, role-based intelligence for everyone in an organization – from front line employees to senior management. These dashboards and reports can be personalized by them as required.Each dashboard caters to a subject area corresponding to a physical star in the database. Each dashboard contains a number of pages that present information from the subject area through a set of visualizations to the end user.1.2.1 Separately Licensed Prerequisite ProductsThe following prerequisite products require separate licenses:∙Oracle Insurance Revenue Management and Billing Analytics∙Oracle Business Intelligence Foundation Suite OR Oracle Business Intelligence Foundation Suite for Oracle Applications OR Oracle Business Intelligence Suite Enterprise Edition Plus1.2.2 Components IncludedThe following table describes the components included with a license for Oracle Insurance Revenue Management and Billing Analytics:Licensed Program Product or Component Included with LicenseNot applicableOracle Insurance Revenue Management andBilling Analytics1.2.3 Restricted Use LicensingOracle Insurance Revenue Management and Billing Analytics product contains all or portions of the following Oracle products:Product or Component Available FeaturesNot applicable1.2.4 General Licensing InformationOracle Insurance Revenue Management and Billing Analytics can be licensed with the Application User metric.1.2.5 Third Party Products UsedOracle Insurance Revenue Management and Billing Analytics uses the following third party software for scripting.∙JQuery∙jQueryUIThe Third-Party Licenses section of this document explains the licensing information for the above software.Appendix A :Third-Party LicensesThe third-party products included with the Oracle Insurance Revenue Management and Billing Analytics licensed software are:∙JQuery∙jQueryUIA.1JQueryCopyright (c) 2011 John Resig, /Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BELIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTIONOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTIONWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.A.2jQueryUICopyright (c) 2010 Paul Bakaus, /This software consists of voluntary contributions made by many individuals (AUTHORS.txt, /about) For exact contribution history, see the revision history and logs, available at /svn/.Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sellOracle Revenue Management and Billing Analytics Licensing Guide copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.Copyright © 2018, Oracle and/or its affiliates. All rights reserved.5。
ORACLE EBS-OU,BG,INV,HR等组织架构介绍【范本模板】
ORACLE EBS—组织架构介绍（一）业务组（（一）业务组（BG）（二)法律实体（LE)（三）业务实体（OU）(四）库存组织（INV）（五）公司成本中心(Cost Center）（六)HR组织（七）多组织接入控制在企业管理实践的过程中，“组织”(Organization)一词是个经常需用到的概念，一般与“人员”与“职能”这两个要素密切相关，反映某种行政管理关系，例如“财务部、销售部、采购部、生产部、仓储部”等等。
企业内部行政组织(部门）的划分是企业基于“职能驱动”业务管理模式进行运作的基础。
目前，国内适用于小企业使用的大多数低端管理软件并不考虑系统中的“组织”设置问题，其系统应用模块的划分，例如采购模块、仓管模块、销售模块等等,实际上就已经基本反映了企业运作的“组织职能"划分问题。
但是,对于业务复杂、规模较大的企业(如所谓“集团企业"）,管理软件使用与实施的系统“组织设置”问题将是一个首要的重要问题。
一个常见的、也是错误的系统实现方式就是将企业的“行政组织设置”直接映射到系统中，以“行政组织”代替“业务组织"。
这种系统实现方式虽有理解、掌握比较容易的优势，但却完全违背了大企业运作必须基于“流程驱动"业务模式的基本管理原则。
国内有所谓高端管理软件在系统实施过程中，常常出现有几十个财务、采购组织，几百个销售组织，乃至上千个库存组织的“盛况”,导致系统几乎没法使用的困境，其症结正在于此。
与企业的“行政组织”设置与人员规模密切相关且复杂多变不同,软件系统的“组织设置”必须以业务流程运作为核心，要求尽可能简单并保持相对稳定，在公司（人员）规模扩大的过程中具有延续性与继承性。
作为ERP鼻祖的SAP将系统组织简单地分为“集团（Client）、公司代码（Company Code）、采购组织（Purchase Org）、销售组织（Sale Org)、工厂（Plant）”等类别。
保险行业大数据分析解决方案-Oracle
最具前景应用-基于车载信息的产品创新（1/2）
汽车保险费
习惯 平稳停车 急刹车
路程 最远 10 英里 11 至 50 英里 50 英里以上
位置 城市 高速公路
事故 近 18 个月
对保险费的影响
80% 5%
50% 20%
5%
75% 25%
0 (2400)
业务目标
• 让利消费者行为 • 提供在线透明度 • 备用产品实时风险分析
在短时间转型为分析人员
• 从学校或者社会招聘统计学背景的分析人才，
• 从市场方面也难以招到合适人员，受互联网
提前培养
影响，IT人才流失严重
• 通过数据探索去挖掘业务场景，通过业务场
• 因此，大数据存储和业务严重脱节，缺少两
景去挖掘数据价值
者的沟通桥梁：分析平台
起步尝试阶段，投入少， 没有将场景和数据关联起来，本质还是缺少分析
分析示例：车载数据到驾驶行为（2/2）
分析算法的广泛应用，但是很少人理解这些算法
车载数据 （外部）
历史赔付（内部， 提取样本）
主成分和主因 子分析
回归分析 贝叶斯分类 决策树分类 随机森林算法 神经网络算法 ...
客户标签 费率测算 个性化推荐 反欺诈 驾驶服务 …
数据收集和整合
降维处理
有监督的数据挖掘
自身迷茫
人才，所以找不到合适的场景，不可能有大投入
• 优先组建分析团队 • 当通过分析团队找到合适业务价值的时候，
将会有很大投入，是否Hadoop,是否开源， 是否一体机显得不再重要
Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | OracleConfidential– Internal/Restricted/HighlyRestricted8
OracleSiebelCRM解决方案保险业
可靠性：Oracle Siebel CRM解决方案经过多年的发展和完善，具有高度的可靠性和稳 定性，能够确保保险公司的业务正常运行。
安全性：该解决方案提供了一系列的安全措施，确保保险公司的客户数据和业务数 据的安全性和完整性。
人工智能和机器学习在CRM解决方案中的应用将进一步深化 云计算技术的普及将推动CRM解决方案的云端化 数据安全和隐私保护将成为CRM解决方案的重要考虑因素 定制化和行业专属性将成为CRM解决方案的重要发展方向
未来发展方向与挑战
人工智能和机器学习在Oracle Siebel CRM解决方案中的应用将进一步增强。
YOUR LOGO
Oracle Siebel CRM解决方案保险 业
XX,a click to unlimited possibilities
汇报人：XX
时间：20XX-XX-XX
目录
01
添加标题
02
03
04
05
Oracle Siebel CRM解决方案概 述
Oracle Siebel CRM 解决方案在保险 业的应用
实施效果：提高了客户满意度和 忠诚度，优化了销售流程和管理 效率，增加了业务收入和市场份 额
某外资保险公司实施效果
实施背景：公司面临客户信息分散、数据不一致等问题，需要集中管理客户信息和销售流程。
解决方案：采用Oracle Siebel CRM解决方案，整合客户信息，统一销售流程，提高客户满意 度和销售效率。
汇报时间：20XX/01/01
实施过程：项目分阶段进行，包括需求分析、系统配置、数据迁移、员工培训等环节，确保系统 顺利上线。
Oracle 保险会计分析器扩展包克隆参考指南说明书
Oracle Insurance Accounting Analyzer Extension PackCloning Reference GuideRelease 8.1.2.0.0February 2023Oracle Insurance Accounting Analyzer Extension Pack Cloning Reference GuideCopyright © 2023 Oracle and/or its affiliates. All rights reserved.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.If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: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 fail-safe, 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. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.For information on third party licenses, click here.Document ControlTable of Contents1Preface (5)1.1Background (5)1.2Assumptions (5)1.3Audience (5)1.4Conventions (5)1.5Abbreviations (5)2Set Up an OFSAA Instance Clone for the 8.1.x Release (7)1PrefaceThe purpose of this document is to serve as reference material to the OFSAA administrators. Thisdocument contains detailed steps to set up an OFSAA Instance Clone for the 8.1.x.x.x releases.1.1BackgroundThere is a consistent requirement for a faster and effective procedure to replicate an existing OFSAAinstance for further project developments. The procedure is to set up the OFSAA instances that areexact copies of the current OFSAA instance.1.2AssumptionsThe assumptions made in this document are:• A working source OFSAA 8.0.6.1.x (or above) instance exists.•An appropriate target system exists for the new OFSAA setup.1.3AudienceThis reference guide is for the administrators and implementation consultants responsible for thecloning of an OFSAA instance.1.4ConventionsThe following text conventions are used in this document.1.5AbbreviationsThe following table lists the abbreviations used in this document.S ET U P AN OFSAA I NSTANCE C LONE FOR THE 8.1.X R ELEASEA BBREVIATIONS 2Set Up an OFSAA Instance Clone for the 8.1.x ReleaseFor information about the prerequisites, cloning, and post-cloning configurations for the 8.0.x releasewhen setting up an OFSAA Instance Clone, see the OFSAA Cloning Reference Guide Release 8.1.x.OFSAA S UPPORTOFSAA SupportRaise a Service Request (SR) in My Oracle Support (MOS) for queries related to the OFSAAapplications.S END U S Y OUR C OMMENTSSend Us Your CommentsOracle welcomes your comments and suggestions on the quality and usefulness of this publication.Your input is an important part of the information used for revision.•Did you find any errors?•Is the information clearly presented?•Do you need more information? If so, where?•Are the examples correct? Do you need more examples?•What features did you like most about this manual?If you find any errors or have any other suggestions for improvement, indicate the title and partnumber of the documentation along with the chapter/section/page number (if available) and contactthe Oracle Support.Before sending us your comments, you might like to ensure that you have the latest version of thedocument wherein any of your concerns have already been addressed. You can access My OracleSupport site that has all the revised/recently released documents.。
阳光财产保险集团资金管理系统用户手册(账户管理篇)--产险
目录目录 (2)【功能描述】 (3)【使用对象】 (3)【系统通用描述】 (3)1账户管理 (5)【说明】 (5)1。
1开户管理 (6)1。
1。
1开户申请 (6)1.1。
2开户确认 (8)1。
1。
3账户启用 (9)1。
2销户管理 (10)1.2.1销户申请 (10)1。
2.2账户销户 (11)1。
2。
3销户确认 (12)1.3变更管理 (13)1。
3.1变更申请 (13)1.3.2账户变更 (15)1.3.3变更确认 (15)1.4冻结解冻 (16)1。
4。
1账户冻结 (17)1.4。
2账户解冻 (17)1.4.3冻结解冻复核 (18)1.5账户查询 (19)1。
5.1账户信息查询 (19)1。
5.2当日余额查询 (20)1.5.3历史余额查询 (20)1.5。
4当日交易查询 (21)1.5.5历史交易查询 (22)【功能描述】将作为资金管理系统中的基础信息的账户信息维护进入系统。
管理账户开户的整个流程：从开户前的意向管理:“开户申请”，到账户开立后账户具体信息在资金系统中的维护：“开户确认”，及账户在资金系统中是否容许使用的状态管理：“账户启用”.【使用对象】出纳（资金管理员）：负责本公司新开账户申请,到银行开户，将开户信息录入到系统；负责本机构账户信息变更的申请,账户变更；负责本机构销户申请,账户销户。
财务经理：负责对本公司和下级公司提交的开户、变更、销户申请进行审批.总部财务部机构资金管理岗：负责总部新开账户申请，到银行开户，将开户信息录入到系统；负责本机构账户信息变更的申请，账户变更；负责本机构销户申请，账户销户。
负责对总部、分公司、三级机构提交的开户、变更、销户申请进行审批。
总部机关资金管理岗：负责总部新开账户申请，到银行开户，将开户信息录入到系统；负责本机构账户信息变更的申请，账户变更；负责本机构销户申请,账户销户.总公司财务部资金管理处负责人:负责对总部、分公司和三级机构提交的开户、变更、销户申请进行审批。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
贷：累计折旧 日记帐－生成－分配 日记帐－生成－经常性 币种－重估 报表－请求－财务 报表－请求－标准 查询－帐户 日记帐－输入日记帐－查询 手工录入凭证同原中科软凭证 手工录入凭证同原中科软凭证
应付，资产，资金模块关账后，进行总帐关账： 总账超级用户职责－设置－打开－关闭
备注 总帐录入现金/银行存款时“说明”后弹性域选择现金流 总帐日记帐头信息中“控制合计”下弹性域输入“附件数”，凭证保存后“流水号”记在凭 证右上角，凭证排序使用 日记帐头、行记录后部“说明”处为凭证摘要显示内容 日记帐中的单据编号为最终装订凭证的真正编号 凭证借贷不平可保存，过帐时系统提示错误，注意 将发票批编号、发票编号记在报销单右上角，凭证排序使用 发票弹性域输入凭证附件、是否福利费 将票据系统生成流水号记在付款单据右上角，凭证排序使用 付款弹性域输入：现金流、支付原始银行单据编号、付款说明（摘要）
业务
模块
取现/工资发放/三金缴纳/二费计提/长期待摊费用摊消/待摊 费用摊消/销售工资计提发放/预提销售工资、费用/税金、保 险保障基金、保险监管费的缴纳/坏帐、减值损失等减值准备 总帐GL（手工） 的计提/应收利息的计提/预提费用/待处理资产损益/固定资 产等资产清理/递延收益/股本/资本公积/盈余公积/
计提税金、计提保险保障基金、创新发展基金计提、上交管 理费、 董事长奖励基金,分支机构特殊税种的计提 汇兑损益计提 资产负债表、利润表、营业费用表 分险种利润表、现金流量表、科目明细帐、科目汇总帐 科目余额、当月发生数查询 业务系统接口凭证、资金模块接口凭证、人力系统接口凭证 、投资系统接口凭证
总帐GL(成批分配凭证） 总帐GL（经常性凭证） 总帐GL 总帐 总帐 总帐 传至总帐GL
固定资产折旧运行后，复选“关闭期间”，系统讲自动关闭当前期间，进入下一区间，且不 可再回到上一区间 每月总公司统一生成凭证，各机构检查 分支机构自己生成 总公司统一生成 选择相应报表查询，可设定期间、成本中心、渠道、公司段 选择相应报表查询，可设定期间、成本中心、渠道、公司段 总公司会设定几个常用的汇总模板
建立中转发票，分配行录入“其他应付款－中转”以核销借款/押金 核销时注意选择对应预付款
红字发票，退款相当于收款
内部往来编码IC0000000029请记在原始凭证右上角，凭证排序使用 内部往来编号为全系统流水
固定资产折旧运行后，复选“关闭期间”，系统讲自动关闭当前期间，进入下一区间，且不 可再回到上一区间
日常费用报销 日常报销付款 个人借款/外部押金 个人借款/外部押金付款
应付AP 应付AP 应付AP 应付AP 应付AP 应付AP
现金(银行全额）还借款/押金
应付AP 应付AP 应付AP
报销还借款/押金
应付AP 应付AP 资产FA 总帐GIS(公司间事务往来）
固定资产采购 固定资产卡片录入
机构之间代付费用(含固定资产） 资产FA 固定资产调拨（调出方） 总帐GIS（公司间事务往来） 总帐GIS（公司间事务往来） 固定资产调拨（调入方） 资产FA 应付AP 低值易耗品报销 低值易耗品卡片录入 固定资产折旧 资产FA 资产FA
关账
总帐
业务流程对照表
路径 凭证
日记帐－输入日记帐－新建批－日记帐
手－标准发票
借：营业费用－印刷费 贷：其他应付款－员工/外部供应商（AP） 付款－录入－付款 借：其他应付款－员工/外部供应商（AP） 贷：现金/银行存款 发票－录入－发票批－预付款 借：其他应收款－员工借款/外部单位（AP) 贷：其他应付款－员工/外部供应商（AP） 付款－录入－付款 借：其他应付款－员工/外部供应商（AP） 贷：现金/银行存款 发票－录入－发票批－新建批－标准发票 借：其他应付款－中转 贷：其他应付款－员工/外部供应商（AP） 发票－录入－发票批－标准发票－活动－核销预付款 借：其他应付款－员工/外部供应商（AP） 贷：其他应收款－员工借款/外部单位（AP) 发票－录入－发票批－新建批－贷项通知单 借：其他应付款－中转 负数 贷：其他应付款－员工/外部供应商（AP） 负数 付款－录入－付款－退款 借：其他应付款－员工/外部供应商（AP） 负数 贷：现金/银行存款 负数 发票－录入－发票批－新建批－标准发票 借：营业费用 贷：其他应付款－员工/外部供应商（AP） 发票－录入－发票批－标准发票－活动－核销预付款 借：其他应付款－员工/外部供应商（AP） 贷：其他应收款－员工借款/外部单位（AP) 发票－录入－发票批－新建批－标准发票 借：固定资产中－中转 贷：其他应付款－员工/外部供应商（AP） 资产－资产工作台 借：固定资产－电器设备 贷：固定资产－中转 事务处理－输入 借：内部往来－代付 发起方 贷：现金/银行存款 借：营业费用/固定资产 接收方 贷：内部往来－代付 资产－资产工作台－查询资产－报废 借：固定资产清理 累计折旧 贷：固定资产－机器设备 事务处理－输入 借：内部往来－其他 贷：固定资产清理 事务处理－输入 借：固定资产－中转 贷：内部往来－其他 累计折旧 资产－资产工作台－查询资产－报废 借：固定资产－机器设备 贷：固定资产中转 发票－录入－发票批－新建批－标准发票 借：低值易耗品－设备 正数 借：低值易耗品－设备 负数 借：营业费用－低值易耗品摊消 正数 贷：其他应付款－员工/外部供应商（AP） 正数 资产－资产工作台 实物管理，不产生凭证 折旧－运行折旧 借：营业费用－财产使用费用－××折旧费