inter-company-reconciliation in SAP

7,016 views

Published on

inter-company-reconciliation in SAP

Published in: Education, Technology

inter-company-reconciliation in SAP

  1. 1. Inter Company Reconciliation In ECC VersionsApplies to:All the companies which requires Intercompany Reconciliation (Upto 4.7 it is F.2E, From ECC5.0 it isFBICR3.)SummaryThis guide will give you step-by-step instructions in the Inter Company Reconciliation in ECC Versions.This will be useful in reconciling the Inter Company transactions. The Intercompany Reconciliationsolution was first delivered with release ERP2004. It replaces the previously existing programsRFICRC00, RFICRC01 and RFICRC20.The Intercompany Reconciliation solution (ICR) is designed for use in Financial Accounting. It providesperiodic control of documents which describe the accounting transactions within the corporate group. ICRselects documents across SAP systems and clients. It is also possible to integrate external data into thereconciliation process. In order to avoid currency conversion differences, the documents are reconciled inthe transaction currency.Author: KRISHNA MOHAN. BOJANAPALLICompany: Intelligroup Asia Pvt. LtdCreated on: 25thMarch 2009Author BioKrishna Mohan. Bojanapalli is a Qualified Cost Accountant having a 10+ years of total experience whichincludes two years of SAP-FI/CO experience. Working as a Senior Associate Consultant with Intelligroupand has been part of the FICO Competency since April 2007.SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 1
  2. 2. Table of Contents1. Introduction.............................................................................................................................................. 32. Process ................................................................................................................................................... 33. Difference between 4.7 & ECC Versions ................................................................................................ 33.1.1 Accessing Transaction .................................................................................................................................33.1.2 Look & Feel Changes...................................................................................................................................43.1.3 Functionality Changes..................................................................................................................................64. Related Content ...................................................................................................................................... 75. Copyright................................................................................................................................................. 8SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 2
  3. 3. 1. IntroductionThe Intercompany Reconciliation solution (ICR) is designed for use in Financial Accounting. Itprovides periodic control of documents which describe the accounting transactions within thecorporate group. ICR selects documents across SAP systems and clients. It is also possible tointegrate external data into the reconciliation process. In order to avoid currency conversiondifferences, the documents are reconciled in the transaction currencyInter Company Reconciliation process will supports the below three Standard processes.1. Process 001 – GL Open ItemsThis process is intended for reconciliation of open items. You should choose this process ifmost of your intercompany receivables and payables are posted to GL accounts2. Process 002 – GL AccountsThis process is intended for reconciliation of documents which are posted to accounts whichdo not have open item management. This process is mostly used for reconciliation of profitand loss accounts.3. Process 003 – Customer / Vendor Open ItemsThis process is intended for reconciliation of open items. You should choose this process ifmost of your intercompany receivables and payables are posted to customer and vendoraccounts.2. Processa. Select Documents:Process 001 – FBICS1Process 002 – FBICS2Process 003 – FBICS3b. Assign Documents:Process 001 – FBICA1Process 002 – FBICA2Process 003 – FBICA3c. Reconcile DocumentsProcess 001 – FBICR1Process 002 – FBICR2Process 003 – FBICR33. Difference between 4.7 & ECC Versions1.1.1 Accessing TransactionBetween enterprise edition 4.7 & new ECC version, the below are the changes in accessing thetransaction & menu path.SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 3
  4. 4. The New T Code is FBICR3Earlier Version – 4.7Via Menus SAP menu Accounting Financial AccountingAccounts Receivable Periodic processing ClosingCheck/count F.2E - Reconcile affiliated companiesVia Transaction Code F.2ENew Version – ECC 6.0Via Menus SAP menu Accounting Financial AccountingAccounts Receivable Periodic Processing ClosingCheck / Count Cross-System IntercompanyReconciliation FBICR3 - Reconcile Documents ManuallyVia Transaction Code 1. FBICS1 FBICS2 FBICS32. FBICA1 FBICA2 FBICA33. FBICR1 FBICR2 FBICR31.1.2 Look & Feel ChangesBelow are the changes in the screen in ECC 6 when compared to 4.7.SAP Enterprise 4.7 SAP ECC 6.0SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 4
  5. 5. SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 5
  6. 6. 1.1.3 Functionality Changesa. In 4.7 it is a single step process, where as in ECC6.0 ICR is a 4 step process: Data selection,Data storage, Data presentation & Analysis, Communication. With EhP3, for ICR in local oneSAP system, it is a 2 step process: Data selection/Storage/presentation & analysis,communication.b. In 4.7 Reconciliation is done at a particular date for the open items. Whereas in ECC6.0Reconciliation is done for a period.c. In 4.7 we have Totals Overview also in the same screen, where as the same is available inECC6.0 through auxiliary program (Separately).d. In 4.7 there are no auxiliary programs, where as in ECC6.0 we are having some auxiliaryprograms, which can be helpful in Total records, Deletion of Transactional Data etc.SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 6
  7. 7. 4. Related ContentOSS Notes:1. sapnote_00011725912. sapnote_00011800603. sapnote_00011619934. sapnote_00008636305. sapnote_00010622926. sapnote_00011597767. sapnote_0001164059For the further info please visit: www.help.sap.comSAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 7
  8. 8. 5. Copyright© 2008 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAPAG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over theworld. All other product and service names mentioned are the trademarks of their respective companies. Data contained in thisdocument serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errorsor omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth inthe express warranty statements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials.SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within thesematerials. SAP has no control over the information that you may access through the use of hot links contained in these materialsand does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to beused in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules ofcertain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grosslynegligent.SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com© 2008 SAP AG 8

×