Shadow Processing Version-1.0 9NT1399
Contents
1. meme mem 0000000 Y cesta Gers reme eese eso Srs nn Y ESE YY esca ccoo rn Y EE escort YY E E usum lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt DNI RN CN EI ET woes esoo omaras E E son snos E E RN soem eomas CTI TT NN E E eerie 0 OT esmee reos con NN ETE weas somma veen ot censors tretago _ RN 2 14 ORACLE lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt CNN CT fasmo CE CO _ CO E _ Y EOI Y CONC CNN E _ woo esee na COMET _ CO _ Womem 0000 LN CO RN CNN LENIN 22. smowo CET a Y _ sewn meruere semen _ sen nta CNN CEC 2 18 ORACLE lt lt lt lt lt lt gt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt rem Pa o Smoon Eo soe pecora atm lt lt lt lt lt Er A CT O CS eee is Foro enn Y CNN 2 8 2 Online Operations gt lt lt The online operations that replayed shadow system listed below 2 20 ORACLE Authorization of disbursement 2 8 3 Accounting Entries The events for which accounting entries will be handed off to the shadow system are given below Ronson Prerio hr Saneren 2 8 4 Batches Transaction Rejection events that will be replayed of batch processing in shadow system Module Code Process Name Process Description Process Name Event Event Name In SHADOW ALIQ Auto Liquidation SLIQ BLIQ Bulk Liquidation SBLQ
3. C ROLL Auto Rollover SROL C TLIQ Tank Liquidation TLIQ Tank Booking TBOK TROL Tank Rollover TROL CL L L L L L O O O O O Module Code Process Process Description Process Name Name Event Name In SHADOW TROL Tank Rollover TROL INIT Forward INIT liquidation SNIT LIQD Liquidation of drafts SLIQ The following events need to have been completed successfully in the main system for them to be processed in the shadow system Module Code Process name Event Name Process Description Auto Disbursement GONSOL ROLLOVER ROSL SPLIT ROLLOVER DSBR Auto Disbursement Liquidation ORACLE Shadow Processing December 2010 Version 1 0 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 650 506 7000 Fax 1 650 506 7200 www oracle com financial_services Copyright O 2010 Oracle Financial Services Software Limited All rights reserved No part of this work may be reproduced stored in a retrieval system adopted or transmitted in any form or by any means electronic mechanical photographic graphic optic recording or otherwise translated in any language or computer language without the prior written permission of Oracle Financial Services Software Limited Due care has been taken to make this document and accompanying software package as accurate as possible However Oracle
4. This User Manual may refer to all or some of the following icons s p ORACLE Refer the Procedures User Manual for further details about icons 15 Related Documents For further information on terms discussed in the manual refer to the Oracle FLEXCUBE manuals on Funds Transfer Payments and Collections Retail Teller Data Entry Mortgage Core Entities Consumer Lending Interest and Charges ORACLE 2 Shadow Processing 2 1 Introduction Oracle FLEXCUBE supports accounting based on different GAAPs for certain retail transactions This is done through shadow processing wherein two FLEXCUBE systems main system and a shadow system each with a different GAAP The actual processing is a combination of replaying maintenances transactions and batches for specific modules and transferring accounting data for other modules that do not require replaying from the main system to the shadow system The replaying can be done manually or through a scheduler and involves the following Replaying of maintenances pertaining to Core FT CL MO and IC modules e Replaying of transactions for the CL TD MO and FT modules Replaying of events through batches for the CL TD MO and FT modules e Handing off of accounting entries for other modules like PC RT DE This is because for these modules there is no difference in processin
5. Entry Number Event e For Batch Processing Status 2 4 ORACLE Processing Date Status Key ID Module Event Code Event Sequence Number Click the Refresh button to view latest details 2 5 Replay Processing You can initiate the replaying of maintenances transactions and batches that are eligible for replaying in the shadow schema in the Replay Operations screen To invoke this screen type STDSHUPD in field at the top right corner of the Application tool bar and click on the adjoining arrow button Replay Operations Webpage Dialog Replay Process Replay Click the Replay button In the shadow system data for the current branch pertaining to maintenances and online transactions will be moved from the staging data store for further processing This replay 15 required to be done before 15 run in the main system and replay of batches can be done only after has been posted in the main system 2 5 1 Processing Maintenances Whenever a maintenance record is saved a check is done in the main system to see if a shadow system exists and if the function ID which is being processed requires replaying replaying is allowed only for first time maintenance then on successful authorization of a new maintenance the details of the maintenance will be stored staging data store to be processed replaying is allowed for diff
6. 15 ORACLE lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt INL TIT CNN WII NN Weser CO _ wes ewm IE TO _ TO AS E _ powan Dewemas 0 CA omen i I MITT RN e E TNT seus _ sewn 2 16 ORACLE lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt gt lt lt lt lt lt lt E CNN A rr LEUTEN CO sro Eo _ A CET _ scu sess CN sewn mee 2 17 ORACLE lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt gt lt lt lt lt lt gt O _ O CNN Er smoww oce sroceu CNN CS sw
7. Financial Services Software Limited makes no representation or warranties with respect to the contents hereof and shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this document and the accompanying Software System Furthermore Oracle Financial Services Software Limited reserves the right to alter modify or otherwise change in any manner the content hereof without obligation of Oracle Financial Services Software Limited to notify any person of such revision or changes All company and product names are trademarks of the respective companies with which they are associated ORACLE
8. OCESSING 8 2 7 2 1 PROCESSING EOD OPERATIONS IN MAIN AND SHADOW 5 5 5 2 8 Lro S12 TOD aia 2 8 PN A Processing BOD 1 Shadow SNS CM AAA 2 9 2 8 PII race cae ac 2 9 2 6 1 IV 2 9 2 8 2 One TC dc 2 19 2 8 3 ECON EROS iaa 2 21 2 8 4 o 2 22 ORACLE 1 1 1 2 1 3 1 4 1 About this Manual Introduction This manual is essentially designed to help you get acquainted with the shadow processing feature in Oracle FLEXCUBE Among other things it provides details on the maintenances that need to be in place and the operations that are impacted in different modules You can obtain information specific to a particular field by placing the cursor on the relevant field and striking lt F1 gt on the keyboard Audience This manual is intended for the following User User Roles Back office clerk Input functions for contracts Back office managers officers Authorization functions Product Managers Product definition and authorization End of day operators Processing during end of day beginning of day Financial Controller Product Managers Conventions Used in this Manual Important information is preceded with the symbol Glossary of Icons
9. Shadow Processing Version 1 0 INT1399 ORACLE FCUBSV UM 11 0 RU 1 0 0 0 December 2010 Oracle Part Number 51712 01 ORACLE FINANCIAL SERVICES ORACLE Document Control Author Documentation Team Group UBPG BEEN Created on November 29 2010 Revision Updated by Documentation Team Reviewed by Development Approved by Software Quality Testing teams Assurance Team Updated on December 23 2010 Reviewed on December 23 Approved on December 23 2010 2010 Shadow Processing Table of Contents L ABOUT THIS MANUA Lonas nio 1 1 1 1 ENTRODUCTI N 1 1 1 2 1 1 1 3 THIS MANTA Laird 1 1 1 4 done 1 1 1 5 HEN _ _____________ __ 1 2 2 SHADOW PROCESSING 2 1 2 1 INTRODUCTION 2 1 222 MAINTENANCES FOR SHADOW 561 0 0001110 2 1 2 3 HANDOFF PROCE SING scada 2 2 2 4 VIEWING HANDOFF PROCESSING DETAILS cccccesecceseccesecccscccenccceneceeeeceseececeneceeeceeueceeeeceseeceeeceeeeceees 2 3 2 5 la A 2 5 23d Processing Maintenances 2 5 2 942 Processing Online 2 6 2 3 3 Processing Batch 1 2 2 2 4 Processing Accounting 2 6 2 6 VIEWING REPLAY PR
10. ata store at the time of authorization of the account entry When transactions are handed off the accounting entries are also populated in the shadow system where they are processed as single entry transactions Accounting maintenances and online transactions will need to be handed off prior to EOD processing in the main system Batch handoff will be done as part of EOD Refer the Annexure for a list of accounting entries that will be handed off to the shadow system 2 4 Viewing Handoff Processing Details You can view the data that is pending for handoff in the Handoff Monitor screen You can invoke this screen by typing STDHDMTR in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button 2 3 ORACLE 2 Handoff Monitor Webpage Dialog Branch Code Branch Maintenance Transaction Processing Status Processing Date Status Key ID Accounting Processing Status sequence Number Status Reference Number Period Code Financial Cycle Account Entry Number Event Batch Processing Status Processing Date Status Key ID Event Code Event Sequence Number The system will display the following details Branch Code Branch Name For Maintenance Transaction Processing Status gt Processing Date gt Process Status gt KeyID For Accounting Processing Status Sequence Number Status Reference Number Period Code Financial Cycle Acoount
11. ations events for batches and accounting entries that replayed from the main system into the shadow system are listed in this section 2 8 1 Maintenances The following are the maintenances that are replayed in the shadow system FUNCTION 1D REPLAY_REOD 2 9 ORACLE mower mower mee ends 0 mower momen CS worst Y menn como pmen Y CEE YY vom eme _ omen Por o or roy e Y CT oe o emm oem nt vave Tag Co ns conce non Prora too ooo Y cn too tag sius retos Y E 2 10 ORACLE lt lt lt lt gt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt lt FUNCTION ID DESCRIPTION CODUDEMT Relationship Pricing User Data Elements Maintenance Y Detailed coc usos temere not cr trato Y EE YY 2 11 ORACLE lt lt lt 2 12 ORACLE mer YY mere omms ET CAC _
12. d Code Batch No Current Number Upload Status Currency Amount Account Value Date Node Serial Number For Batch Processing Status Processing Date Status Key ID Module Event Code Event Sequence Number Click the Refresh button to view the latest details 2 7 Processing EOD Operations in Main and Shadow Systems EOD operations need to be run in both the main as well as the shadow systems The process involves checks in both systems and co ordination between the two systems For instance EOD processing in the shadow schema can start only after is completed in the main system Similarly before each stage of EOD can be run in the shadow system only after the same stage or a later stage in EOD has been completed in the main system This is explained in detail below 2 7 1 Processing EOD in Main System As part of the EOD process in the main system checks are carried out which include ensuring that handoff to the shadow system has been completed After this when 15 marked the following takes place e Running of batch processes Populating of staging tables for batch and accounting entries e Handing off of batch and accounting data to the shadow system Subsequently is marked and a check is carried out as part of post EOFI process to ensure that the handoff to the shadow schema has been done Then EOD and date change ta
13. erent operations for the function ID and a shadow system exists then the details of the modified record are stored in the staging data store in the main system during authorization 2 5 ORACLE 2 5 2 2 5 3 2 5 4 Subsequently during handoff these details will be made available in the staging data store in the shadow system the shadow system these details will be processed further and the status of the processing updated in the staging data store the shadow system Refer the Annexure for a list of maintenances that can be replayed in the shadow system Processing Online Operations Whenever a new contract is authorized or any other operation is performed on an existing contract a check will be done in the main system to see if replaying is allowed for both the function ID and the Service Operation for the function ID replaying is allowed then the contract and operation details of the contract are stored in the staging data store in the main system This will be moved to the staging data store in the shadow system to be processed further The processing however will be with regard only to the main contract and will not include any linkage maintained for the contract Subsequently the shadow system will log the status of the processing in its staging data store Refer the Annexure for a list of online operations that can be replayed in the shadow system Processing Batch Replays As part of batch processing during EOD i
14. f a shadow system exists events for which replay 15 required are populated in the staging data store in the main system and moved to the shadow system in the form of request xmls when replay is triggered In the shadow system for modules requiring different GAAP accounting like FT CL and TD events like accrual provisioning status change revaluation will be processed differently For other events like liquidation rollover value dated amendmenis for these modules the shadow system will pick up the request xmls from the staging data store for further processing If a certain event has been unsuccessful in the main system the event can be replayed in the shadow system only if the data for the event is not available in the staging store in the shadow system You can configure the order in which the various batches are to be run in the shadow system Based on the order specified the system will process as a normal batch process or replay the request xml or replay the accounting entries for the module Processing Accounting Entries For the PC RT and DE module accounting entries replay instead of transactions replay is done This is because there is no difference in the GAAP requirements for these modules The replay is essentially to keep the account balances the same in both the systems When the accounting entry for a contract is authorized in the main system if the Replay Required flag is selected then the accounting entry will be l
15. g for different GAAPs The accounting entries handoff is primarily to ensure that the account balances in both systems are the same After the processing the shadow system will handoff the accounting to FGL for further processing as is depicted below Systems FCUBS MAIN SYSTEM Accounting Maintenances Online Batch events GAAP wise Chart accounts Accounting GAAP wise Balances FCUBS SHADOW SYSTEM 2 2 Maintenances for Shadow Processing The following backend maintenances are required for shadow processing e Defining different GAAPs for the main and shadow system in the GAAP INDICATOR field The GAAP indicator for each system will be displayed in the title bar for the system 2 1 ORACLE e Defining shadow system in the main and shadow systems you need to indicate that a shadow system exists by configuring the value of the backend parameter SHADOW_SYSTEM EXISTS to Y e Identifying the shadow system You need to indicate which system is the main system and which represents the shadow system This is done by configuring the value of the backend parameter SHADOW SYSTEM N in the main system and in the shadow system e Identifying maintenances requiring replay in the shadow system you can do this by configuring the backend parameter Required the corresponding function 10 to any of the following gt Y to replay fi
16. kes place When the next stage marking of BOD takes place the following is carried out Running of batch processes Populating of staging tables for batch and accounting entries Handing off of batch and accounting data to the shadow system T ORACLE Again in the next stage Pre Checks check 15 carried out to see if the handoff process to the shadow system is completed On successful completion of the above steps Tl is marked in the main system 2 7 2 Processing EOD in Shadow System As part of the EOD process in the shadow system checks are carried out which include ensuring that the branch in the main system is in the EOFI stage or any stage later than If the check is successful batch process in the shadow system is executed and batch and handoff data that was handed off to the shadow system is replayed Subsequently will be marked and pre EOD checks carried out in which the EOD stage in the main system is checked it should be EOD or a stage later than EOD Then EOD 15 marked and date change 15 done in the shadow system After this during pre BOD check again the stage for the branch in the main system is checked This should be TI stage If it is then in the shadow system BOD is marked during which batch process is run and the data handed off for batch and accounting replayed After this Tl is marked in the shadow system as well 2 8 Annexure The maintenances online oper
17. ogged into the staging data store to be replayed in the shadow system These would be populated in the data store of the shadow system when transactions are replayed at the main system Subsequently these accounting entries will be processed as single entry transactions in the shadow system You can replay batches only for those events for which accounting handoff has not been done 2 6 ORACLE Refer Annexure for a list of events that can be replayed in the shadow system 2 6 Viewing Replay Processing Details You can view the data that is pending replay in the Shadow Monitor screen You can invoke this screen by typing STDSHMTR in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button Shadow Monitor Webpage Dialog a Branch Code Branch Name Maintenance Tranzaction Processing Status Processing Date Process Status Accounting Processing Status Financial wear Period Batch Current Number Upload Status Currency Amount Account WEC Value Date E Batch Processing Status Processing Date Status iD Module EventCode Event Sequence Number The system will display the following details e Branch Code e Branch Name e For Maintenance Transaction Processing Status gt Processing Date gt Process Status gt e For Accounting Processing Status 2 7 ORACLE Financial Year Perio
18. rst time maintenances only gt A to replay maintenances for all operations gt not replay the maintenance e Identifying the transactions to be replayed you can do this by configuring the backend parameter Replay Required for the corresponding function ID to any of the following gt Y to replay the transaction gt not replay the transaction e Identifying the events for which batches need to be replayed e Identifying the events for which accounting entries that need to be replayed you can do this by configuring the backend parameter Replay Required in the events data store 2 3 Handoff Processing You can trigger the handoff of entries for maintenances online batch and accounting from the main to the shadow schema in the Handoff Operations screen To invoke this screen type STDHDOFF in field at the top right corner of the Application tool bar and click on the adjoining arrow button 2 2 ORACLE Operations Webpage Dialog In this screen click Handoff to begin the handoff operation The main system hands off accounting entries for modules for which differential GAAP treatment is not required The handoff is done to keep account balances in both systems the same and ensure proper accounting in the shadow system When a contract is authorized if replay of accounting entries is allowed for an event then the accounting entry will be logged in the staging d
Download Pdf Manuals
Related Search