Trova il tuo prossimo libro preferito

Abbonati oggi e leggi gratis per 30 giorni
SAP ECC FI Transaction Codes: Unofficial Certification and Review Guide

SAP ECC FI Transaction Codes: Unofficial Certification and Review Guide

Leggi anteprima

SAP ECC FI Transaction Codes: Unofficial Certification and Review Guide

5/5 (2 valutazioni)
269 pagine
2 ore
Dec 29, 2011


Transaction codes are the key to working in the SAP R/3 and SAP ECC Finance and Controlling environments; however, a user-friendly and thorough resource can be difficult to locate. From helping you to locate a transaction you haven’t used in a while to helping you unlock new functionality in SAP R/3 FI, this guide has what
you need to work faster. In addition to acting as a handy reference, this guide will help you set yourself apart from other SAP professionals – knowing the right TCODE is often the difference between a mid-range and senior SAP resource. This book contains comprehensive transaction code listings for FI.

Whether you are new to SAP, or a veteran SAP project manager this book will come in handy. One
of a series of SAP transaction code books, SAP FICO Transaction Codes delivers. Includes 150+
pages of transaction codes and explanations for SAP Finance. The table of contents and index are also comprehensive, making it easy to find what you need and help you save precious time.

Key topics include:

FI Transaction Codes and Tables
SAP FICO Frequently Asked Questions

Dec 29, 2011

Informazioni sull'autore

Correlato a SAP ECC FI Transaction Codes

Leggi altro di Equity Press
Libri correlati
Articoli correlati

Anteprima del libro

SAP ECC FI Transaction Codes - Equity Press

SAP ECC FI Transaction Codes

Unofficial Certification and Review Guide

Equity Press

Compiled By Terry S. Clark

ISBN 978-1-60332-299-7

Smashwords Edition

Edited By: Jamie Fisher

Copyright© 2006 Equity Press and SAP COOKBOOK all rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) without either the prior written permission of the publisher or a license permitting restricted copying in the United States or abroad.

The scanning, uploading and distribution of this book via the internet or via any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions, and do not participate in or encourage piracy of copyrighted materials.

The programs in this book have been included for

instructional value only. They have been tested with

care but are not guaranteed for any particular purpose.

The publisher does not offer any warranties or

representations nor accepts any liabilities with

respect to the programs.

Trademarks: All trademarks are the property of their respective owners. Equity Press is not associated with any product or vendor mentioned in this book.

Please visit our website at

Table of Contents



Question 01: CO Enterprise Structure

Question 02: Automatic account determination

Question 03: Primary and Secondary cost element

Question 04: Special GL and Noted Document

Question 05: Group Chart of Account

Question 06: Currencies in Company Code

Question 07: Special posting period

Question 08: Transport no ranges

Question 09: Asset class

Question 10: Account Group

Question 11: Use of Alternative Account

Question 12: Open Item Management

Question 13: Identify target cost version

Question 14: Parking of document

Question 15: Low value assets

Question 16: Alternative reconciliation account

Question 17: Posting key and Field status group

Question 18: Creating Vendor Invoice

Question 19: Bank Reconciliation Statement

Question 20: Document flow confusion

Question 21: Change reconciliation account of customer master

Question 22: Various postings to GL account

Question 23: Creating new company code

Question 24: APC

Question 25: Cost center

Question 26: Activate asset accounting in new company code

Question 27: Middle of the year Asset data transfer

Question 28: GRIR

Question 29: Error as T880

Question 30: House Banking

Question 31: Interest calculation

Question 32: Month end closing activities and post production issues in FI/CO

Question 33: Costing variants

Question 34: Using the Lock Box Files

Question 35: Electronic Bank Statement


Question 36: Currency conversion in BW

Question 37: Convert in update rules

Question 38: Start routine

Question 39: Currency conversion

Question 40: Currency conversion in a query

Question 41: Foreign currency valuation

Question 42: Currency conversion dependent on date

Question 43: Currency Conversions

Question 44: Currency exchange rate

Question 45: Foreign Exchange (forex) transactions

Question 46: Rate difference

Question 47: Currency conversion issues

Question 48: Foreign currency test scripts

Question 49: Automatic outgoing program error

Question 50: GR/IR tolerance for automatic clearing

Question 51: Valuation methods

Question 52: Currency conversions in BPS

Question 53: Currency translation type not appearing in BEX

Question 54: Exchange rate field for input in transactions


Question 55: GL accounts

Question 56: Transport GL Accounts

Question 57: Mass blocking of GL accounts

Question 58: Reconciliation & Alternate Reconciliation A/c

Question 59: Open item issue

Question 60: Alternative Reconciliation account

Question 61: Automated payments

Question 62: Vendor down payment made

Question 63: Maintain Field Status Variants

Question 64: Advance Payment to Vendors

Question 65: Assigning material and GL to cost center

Question 66: Configure FICO reconciliation

Question 67: Configuration for Special Purpose Ledger

Question 68: Cost elements not created for GL

Question 69: Calculate bank interest

Question 70: Special G/L transaction

Question 71: GL Accounts not be displayed

Question 72: Entries in particular Field in GL

Question 73: New GL Account in ECC 5.0

Question 74: Amount transfer from bank to bank


Question 75: Chart of Accounts

Question 76: Transport of chart of accounts

Question 77: Changing chart of accounts

Question 78: Copy GL account from COA

Question 79: Transporting COA, Cost Center & Profit Center Hierarchies

Question 80: Create and assign multiple FS to CC

Question 81: Operational chart of accounts issue

COPA - Controlling and Profitability Analysis

Question 82: Purpose of COPA

Question 83: More on COPA

Question 84: COPA tables

Question 85: Adding Fields to COPA Data Source

Question 86: COPA Extraction

Question 87: Extraction steps

Question 88: COPA does not reconcile between BW and R/3

Question 89: Index use

Question 90: Improve I/O

Question 91: COPA delta

Question 92: Billing issue

Question 93: COPA Init Delta

Question 94: Delete init request in COPA

Question 95: COPA extraction delta failure

Question 96: Data extraction for COPA pulling 0 records


Question 97: Credit management

Question 98: Increase/Decrease credit limit

Question 99: A/R - Credit Management for customers

Question 100: Update Customer Credit Management

Question 101: Mass update customer credit limit

Question 102: Customer report with dr. balance only

Question 103: Customer credit management change BO Required

Question 104: Credit Block

Acknowledgements and references


SAP R/3 is the former name of the main ERP software produced by SAP. Its new name is mySAP ERP.

SAP R/2 was a mainframe based business application software suite that was very successful in the 1980s and early 1990s. It was particularly popular with large multinational European companies who required soft-real-time business applications, with multi-currency and multi-language capabilities built in. With the advent of distributed client-server computing SAP AG brought out a client-server version of the software called SAP R/3 that was manageable on multiple platforms and operating systems, such as Windows or UNIX since 1999, which opened up SAP to a whole new customer base. SAP R/3 was officially launched on 6 July 1992. SAP came to dominate the large business applications market over the next 10 years.

From the late 1960s to the 1980s there was a concern that software development was too complex and liable to go wrong. One of the solutions to this proposed by many people including Fred Brooks was the development of a modular approach in order to maximize software reuse and encapsulate common business processes within internal transactions. SAP introduced the object-oriented concept of business objects; for example, a customer in the system is actually an instantiation of a customer business object, and interacts with other objects in the system in a pre-defined (although customizable) way. In some ways, SAP can be almost thought of as an operating system for a business.

SAP software comes with customizable processes which a company uses in the modelling of its business. Traditionally, software purchases had provided tools for building applications, but these tools did not provide business processes. SAP provided standardized processes, which were termed best-practice solutions of processes. The implementation of SAP software commonly required the expertise of knowledgeable external consultants, who were familiar with these best-practices.

SAP R/3 is arranged into distinct functional modules, covering the typical functions in place in an organization. The most widely used modules are Financials and Controlling (FICO), Human Resources (HR), Materials Management (MM), Sales & Distribution (SD), and Production Planning (PP). Those modules, as well as the additional components of SAP R/3, are detailed in the next section.

Each module handles specific business tasks on its own but is linked to the others where applicable. For instance, an invoice from the Billing transaction of Sales & Distribution will pass through to accounting, where it will appear in accounts receivable and cost of goods sold.

SAP has typically focused on best practice methodologies for driving its software processes, but has more recently expanded into vertical markets. In these situations, SAP produces specialized modules (referred to as IS or Industry Specific) geared toward a particular market segment, such as utilities or retail.

Using SAP often requires the payment of hefty license fees, as the customers have effectively outsourced various business software development tasks to SAP. By specializing in software development, SAP hopes to provide a better value to corporations than they could if they attempted to develop and maintain their own applications.

SAP R/3 is a client/server based application, utilizing a 3-tiered model. A presentation layer, or client, interfaces with the user. The application layer houses all the business-specific logic, and the database layer records and stores all the information about the system, including transactional and configuration data.

SAP R/3 functionality is structured using its own proprietary language called ABAP (Advanced Business Application Programming). ABAP, or ABAP/4 is a fourth generation language (4GL), geared toward the creation of simple, yet powerful programs. R/3 also offers a complete development environment where developers can either modify existing SAP code to modify existing functionality or develop their own functions, whether reports or complete transactional systems within the SAP framework.

ABAP's main interaction with the database system is via Open SQL statements. These statements allow a developer to query, update, or delete information from the database. Advanced topics include GUI development and advanced integration with other systems. With the introduction of ABAP Objects, ABAP provides the opportunity to develop applications with object-oriented programming.

The most difficult part of SAP R/3 is its implementation simply because SAP R/3 is never used the same way in any two places. For instance, Atlas Copco can have a different implementation of SAP R/3 from Procter & Gamble and so forth. Two primary issues are the root of the complexity and of the differences:

>Customization configuration - Within R/3, there are tens of thousands of database tables that may be used to control how the application behaves. For instance, each company will have its own accounting Chart of Accounts which reflects how its transactions flow together to represent its activity. That will be specific to a given company. In general, the behavior (and appearance) of virtually every screen and transaction is controlled by configuration tables. This gives the implementor great power to make the application behave differently for different environments and with that power comes considerable complexity.

>Extensions, Bolt-Ons - In any company, there will be a need to develop interface programs to communicate with other corporate information systems. This generally involves developing ABAP/4 code, and considerable systems integration effort to either determine what data is to be drawn out of R/3 or to interface into R/3 to load data into the system.

Due to the complexity of implementation, these companies recruit highly skilled SAP consultants to do the job. The implementation must consider the company's needs and resources. Some companies implement only a few modules of SAP while others may want numerous modules.

SAP has several layers. The Basis System (BC) includes the ABAP programming language, and is the heart (i.e. the base) of operations and should not be visible to higher level or managerial users. Other customizing and implementation tools exist also. The heart of the system (from a manager’s viewpoint) is the application modules. These modules may not all be implemented in a typical company but they are all related.

This book will discuss the various issues commonly encountered by FICO users. It will also give readers a better understanding of these two modules, FI (Financial Accounting) and CO (Controlling) which are defined as follows.

The SAP FI Module

Hai raggiunto la fine di questa anteprima. Registrati per continuare a leggere!
Pagina 1 di 1


Cosa pensano gli utenti di SAP ECC FI Transaction Codes

2 valutazioni / 0 Recensioni
Cosa ne pensi?
Valutazione: 0 su 5 stelle

Recensioni dei lettori