Summ2 of TFIN52 Certification PDF

Financial Accounting TFIN 52 Summary
Prepared by: Zeeshan R Haryani
Prepared By Zeeshan Raza Haryani ACA, ACCA Finalist Certified FICOBW Zeeshan.haryani@gmail.com
Page 1 of 45
Contents
Unit 1 Organizational Structure ..................................................................................................................... 4 Lesson 1 Assignment Company Code - Chart of Accounts - Chart of Depreciation ................................ 4 Lesson 2 Cost Accounting Assignment ..................................................................................................... 5 Lesson 3 Introduction to Assets Class ....................................................................................................... 5 Unit 2 Master Data ......................................................................................................................................... 7 Lesson 1 Function of Assets class ............................................................................................................. 7 Lesson 2 Assets Master Record .................................................................................................................. 9 Lesson 3 Mass Change............................................................................................................................... 9 Unit 3 Assets Transactions........................................................................................................................... 11 Lesson 1 Assets Acquisition .................................................................................................................... 11 Lesson 2 Assets Retirement ..................................................................................................................... 12 Lesson 3 Intercompany & Intracompany Assets Transfer ....................................................................... 13 Lesson 4 Assets Under Construction ........................................................................................................ 13 Lesson 5 Unplanned Depreciation ........................................................................................................... 14 Unit 4 Periodic Processing and Valuation ................................................................................................... 15 Lesson 1 Function of Assets class ........................................................................................................... 15 Lesson 2 Fiscal Year Change and Year End Closing in Assets ............................................................... 18 Unit 5 Information System........................................................................................................................... 19 Lesson 1 Report Selection ....................................................................................................................... 19 Lesson 2 Value Simulation ...................................................................................................................... 19 Lesson 3 Assets History Sheet ................................................................................................................. 19 Unit 6 Standard Reports in General Ledger Accounting, Accounts Receivable Accounting and Accounts Payable Accounting ........................................................................................................................................ 21 Lesson 1 Information System .................................................................................................................. 21 Lesson 2 Report Variant and Variables ................................................................................................... 21 Unit 7 List Viewer ....................................................................................................................................... 22 Lesson 1 SAP List Viewer Design........................................................................................................... 22 Lesson 2 Selections .................................................................................................................................. 22 Lesson 3 Changing the Screen Layout..................................................................................................... 23 Unit 8 Drilldown Reporting in Financial Accounting ................................................................................. 24 Lesson 1 Architecture of Drilldown Reporting ....................................................................................... 24 Lesson 2 Characteristics and Key Figures ............................................................................................... 24 Lesson 3 Form Types ............................................................................................................................... 25 Lesson 4 Navigation in Reports ............................................................................................................... 26 Lesson 5 Form & Report Definition ........................................................................................................ 26 Lesson 6 Report/Report Interface and Report Assignment ..................................................................... 27 Unit 9 Special GL Transactions ................................................................................................................... 29 Lesson 1 Application view for Special GL Transactions ........................................................................ 29 Lesson 2 Configuration of Special GL Transactions ............................................................................... 31 Unit 10 Parking Documents ......................................................................................................................... 32 Lesson 1 Basics of Parking Documents ................................................................................................... 32 Lesson 2 Parking Documents & Processing Parked Documents .............................................................. 32 Lesson 3 Document Parking and Workflow ............................................................................................. 33
Page 2 of 45
Unit 11 Validation & Substitution ............................................................................................................... 36 Lesson 1 Basics of Validation / Substitution ........................................................................................... 36 Lesson 2 Definition and Execution of Validation in Financial Accounting ............................................ 37 Lesson 3 Definition and Execution of Substitution in Financial Accounting ......................................... 38 Lesson 4 Additional Technique for Substitution/Validation ................................................................... 39 Lesson 5 Validation Rule for Account Assignment combination ........................................................... 39 Unit 12 FI Archiving.................................................................................................................................... 41 Lesson 1 Basics of Parking Documents ................................................................................................... 41 Lesson 2 Preparatory Activities System Settings ................................................................................. 42 Lesson 3 Executing Archiving in Financial Accounting Using example ................................................ 43
Page 3 of 45
Unit 1 Organizational Structure

Lesson 1 Assignment Company Code - Chart of Accounts - Chart of Depreciation
The client is the highest level in the SAP system hierarchy. It also denotes the specific logical system you are working on. Specifications that you make on this level apply to all company codes. Each company code is an independent accounting unit. The legally required balance sheet and profit and loss statement are created at this level. Each business area is to be regarded as a financially separate unit for which an internal balance sheet and profit and loss statement can be created. Asset Accounting (FI-AA) works with the chart of accounts assigned to the company code in Financial Accounting (FI). The chart of depreciation must be country-specific. Each depreciation area represents a specific type of valuation (for example, book depreciation or tax depreciation, and so on). Each company code uses one (operative) chart of accounts and one chart of depreciation. All or several company codes can work with the same chart of accounts and the same chart of depreciation. The depreciation areas in a chart of depreciation are defined with a two-digit numeric key. Depreciation area 01 is always what is known as the leading depreciation area. The leading area 01 (currently) reflects the local accounting principles in each sample chart of depreciation. Other depreciation areas can contain the following valuations, for example: o Tax balance sheet valuation o Costing-based valuation o Valuation approaches in other currencies and/or valuation approaches (=> such as group valuation) o Capital tax valuation o Differences between book and country-specific tax-based depreciation Asset portfolios and transactions are often valued differently for different purposes; for example, different valuation approaches should/have to be used for: o ... Book depreciation (according to local requirements) o ... Balance sheets for tax purposes (insofar as another valuation is permitted) o ... Internal accounting (=> cost accounting) o ... Parallel accounting, such as for creating a consolidated balance sheet according to IFRS and/or US GAAP. These various valuation approaches are mapped in the SAP system by means of depreciation areas. Steps in Assets Accounting o First, completely set up the company code(s) in Financial Accounting. o Then allocate a chart of depreciation to the company code (in a separate project, if possible). o * The company code is then expanded by means of various Customizing activities to include the necessary data and information. o The company code is then ready for use by Asset Accounting
Page 4 of 45
Lesson 2 Cost Accounting Assignment

In the master record, you can assign the following basic Cost Accounting objects to an asset: o Cost center o (Internal) order: the order can be real or statistical o Activity type: as purely statistical information These CO objects are assigned to a controlling area which can, in turn, include one or more company codes. It is also possible to assign objects from other applications (with controlling functions) in addition to original the CO objects. examples: o WBS element o Real estate object o Maintenance order: as purely statistical information o Objects from Public Sector Management (=> PSM) As such we can post the following (CO) objects: o A cost center o A (real) order o A cost center and a statistical order o A WBS element o A cost center and a statistical WBS element o A real estate object o Objects from Public Sector Management However, it is not possible to assign an asset to two cost centers.
Lesson 3 Introduction to Assets Class
Assets are assigned to asset classes. Examples of asset classes are the Vehicles, Fixtures and Fittings and Machines classes. Asset classes consist of a master data section and a depreciation area section. Asset classes are created at client level. They are also assigned to at least one chart of depreciation *, so you can complete the asset class with default values for the depreciation terms for each depreciation area. For each depreciation area, you can propose the depreciation attributes for the assets; you can choose that they be specified by the system. If the depreciation attributes are specified by the system, they are not changeable. There is also at least one special asset class each for assets under construction and low value assets. This will be addressed in further detail in the next chapter. The technical management of assets is d one using (logistical) Plant Maintenance or Enterprise Asset Management (=> EAM).
Page 5 of 45
The Treasury system is used to manage financial assets. It is a part of Financial Supply Chain Management (=> FSCM). With FI-AA, you can manage different valuation approaches for each asset in depreciation areas. However, financial statements are not created / required for the values of all depreciation areas. When using the Account Approach (see Periodic Processing and Depreciation unit) , you have the following options: o (0) Area does not post (no values posted to FI) o (1) Area posts in real-time (asset values are posted to FI online periodic depreciation) o (2) Area posts asset values and depreciation periodically o (3) Area only posts depreciation (of course, periodically) o (4) Area posts asset values and depreciation (depreciation is, of course, posted periodically) o The settings (5) and (6) are only required when using the Ledger Approach in the New General Ledger. With periodic asset value posting (program RAPERB2000), you can post asset values from depreciation areas other than area 01 to the general ledger. Depreciation is always posted on a periodic basis. Program RAPOST2000 is used for this. You can also define depreciation areas for reporting purposes only, which do not post any values to the general ledger. You can post both the asset values and the depreciation values from the individual depreciation areas to separate financial statement accounts or profit and loss accounts. You specify in the financial statement version the financial statement item or the profit and loss statement item in which the account values should appear. In Customizing for Asset Accounting, you enter the financial statement versions to be used for each depreciation area, if the asset report is also to create financial statements items for these areas in FIAA Reporting.
Page 6 of 45
Unit 2 Master Data

Lesson 1 Function of Assets class
The asset class definitions apply to all company codes in a client. An asset class consists of two main sections: o A master data section with control data and default values for the administrative data in the asset master record o A depreciation section with control parameters and default values for depreciation terms for each depreciation area When you create asset master records, this data is automatically adopted from the asset class you specify. By entering useful default values, you can reduce the time and effort needed to create new asset master records The asset class is the main selection criterion in all standard reports in FI-AA. If you use different company codes with different operational charts of accounts, however, you need only one account determination key to post asset values of the asset of one class to different accounts in different charts of accounts For those depreciation areas that post depreciation to the general ledger, you must assign the following additional G/L accounts: o For ordinary depreciation: o Accumulated depreciation accounts o Expense accounts o Revenue accounts for a write-up o For unplanned depreciation: o Accumulated depreciation accounts o Expense accounts o Revenue accounts for a write-up o And for revaluations of depreciation and for interest (cost accounting area), if necessary/desired. The number range controls the assignment of the number of the asset master record. You define number assignment as either internal or external. You can assign each company code its own number ranges, or specify cross-company code number assignment. The screen layout determines which input fields in the asset master records can be processed or whether these fields are to be defined as required fields or if the fields are not displayed at all. In addition to the information on the field selection (required entry, optional entry, display, suppress), the screen layout specifies the maintenance level of master data fields. It also determines whether the master data fields are allowed to be used as a reference. The maintenance level specifies at which level maintenance of each data field is permitted possible maintenance levels are: o Asset class o Main asset number o Sub number On the one hand, you can post (cost-accounting) depreciation to account assignment objects, on the other hand, account assignment objects can also be used for making APC postings, such as direct
Page 7 of 45
capitalization as part of an investment measure (when the IM component is also in use) or for (statistical) budget monitoring for asset purchases. You can specify a layout for the master data of each asset class. The layout defines: o The number of tab pages o The names of the tab pages o The logical field groups (groups / field group boxes, such as the visible logical field groups General data and Posting information in the figure above), that are to appear on the tab pages. In each asset class, you enter a screen layout rule for each depreciation area. These rules apply to the (input) fields of the in the depreciation data section / depreciation area. SAP supplies screen layout rules 1000 and 2000 in the standard system. These screen layout rules also contain a maintenance level. The maintenance level guarantees that depreciation is controlled uniformly. There are three options: o 1. Asset class: This maintenance level ensures uniform control of valuation at asset class level. o 2. Main asset number: The control of valuation is uniform at the level of the asset master record. The entries made in the asset class are adopted in the asset master record, and can be changed there. All asset sub numbers that belong to this asset master record adopt these values from the main number. o 3. Asset sub number: Valuation can be controlled more flexibly. Asset sub numbers can receive their own individual depreciation terms. Defining allowed entries for user fields and other information fields: In the asset master record the following fields are available as standard for general and user-specific structure of fixed assets: o Evaluation groups (evaluation group 1 to 5): These are asset master record fields that are used to map customer-defined / customer-specific information. o Environmental protection indicator: In this field you can save the reason for an environmental protection investment (for example, new climate-protection regulations). o Reason for investment: In this field you can enter an explanation for a capital investment (for example, replacement acquisition). o Asset super number: This can be assigned to an asset. This is useful, for example, if several assets are to be assigned to an asset super number (for example, business unit or production line). Assets under construction (AuC) require a separate asset class and corresponding G/L account, because they have to be shown separately in the financial statement. By choosing the standard depreciation key 0000 you can ensure that depreciation is not calculated for assets under construction in depreciation areas (at least for the depreciation areas in the financial statement). However, special tax depreciation and investment support are also possible for assets under construction. You can also enter down payments on assets under construction in accounts payable accounting processes. Even after an asset under construction has been fully capitalized, you can still post credit memos. For this to be possible you must permit negative (APC) values in the detail screen of the depreciation data section. Investment Management (IM) is available to help you manage more extensive asset investments. It integrates internal orders and projects with assets under construction. You can choose whether to manage low value assets (LVAs) using individual management or collective management. For each type of management, you have to set up a separate asset class. If you select collective management for low-value assets, a base unit of quantity must be specified for this asset class.
Page 8 of 45
Lesson 2 Assets Master Record

When you create an asset master record, you have two options: o Enter the company code and asset class for the new asset master record o Use an existing asset master record as a reference When creating asset master records, you can create multiple similar assets. Some information in the asset master record can be managed as time-dependent data. This is of particular significance for the assignment of assets to CO organizational units, for example, cost center or project). Shift operation and asset shutdown can have a direct effect on depreciation. Therefore you should enter them in the time-dependent data, where they can be changed on a monthly basis. Each time you change an asset master record, the system creates a change document. The change document contains a list of fields that were changed and the number of changes to a field. In addition, the name of the user and the old and new contents of fields are stored. The method for assigning equipment to an asset was to enter the asset number in the relevant master record still exists. Several pieces of equipment can be assigned to an asset, but a piece of equipment can only belong to one asset. You can set up the system so that when you create an asset master record, the system automatically creates an equipment master record while copying the values of certain master data fields (for example, the Company Code and the Inventory Number). If you change master data in the asset at a later point in time, the system then automatically updates the fields in the equipment master record and the other way around. If a fixed asset is made up of many component assets, you may want to manage these component assets as separate sub numbers. This might be useful for both technical and accounting reasons. You can divide up assets by sub numbers, if: o You want to manage the values for subsequent acquisitions in following years separately for example, buildings. o You want to manage the values for individual parts of assets separately. o You want to split the asset according to various technical aspects
Lesson 3 Mass Change

The individual steps for a mass change to asset master data can be summarized as follows: o 1. Create a substitution rule to specify which fields you want to change and how you want to change them o 2. The saved substitution rule must then be assigned to a company code o 3. Create a list of assets to be changed (=> a work list). o 4. Using the program called, select the master data to be changed and press the Create Work list pushbutton in the results screen. o 5. Enter a description and select a purpose for your work list. The purpose is a pre-defined standard task in the system (for example, change master data). o 6. In the dialog window that appears, select the defined substitution rule for the mass change and save your data. o 7. Now (only) the work list still has to be processed. o 8. Check whether your mass change was successful by displaying the assets or running an appropriate report. A substitution rule consists of two parts:
Page 9 of 45
o 1. Conditions that identify the records to be selected: You can create conditions using the Form Editor or in expert mode. To use expert mode, you have to know the (technical) field and table descriptions of the input fields involved. o 2. Substitutions (if the conditions are met) that identify the replacement values. These can be constant values, field-field assignments, or user exits
Page 10 of 45
Unit 3 Assets Transactions

Lesson 1 Assets Acquisition
Acquisition of an asset from a business partner: External acquisition: o In FI-AA with integration with accounts payable, usually if an incoming invoice is available, but without reference to a purchase order. o In FI-AA with automatic offsetting entry, but without a link to a purchase order and without integration with Accounts Payable. The offsetting account also has to be cleared. o In FI-AA with offset clearing: The first posting is usually made in FI-AP. The asset posting then also clears the clearing account. It is also possible, however, for both departments to make postings in the opposite order: An asset is entered with automatic offsetting entry, and the clearing account is cleared with the credit creation of the incoming invoice. o In Materials Management (MM): The posting/activation of the assets takes place in Logistics. Acquisition from in-house production is the capitalization of goods or services that are partially or completely produced in your own enterprise. Generally, you capitalize production costs by creating an investment measure (=> order/project) in Investment Management (IM) and settling to an asset under construction and then to the final asset. Transaction type When posting to assets, you must enter a transaction type. The transaction type identifies the different transactions in the asset history sheet. Document splitting is a functionality that is enabled by the new G/L. It is used to create (complete) balance sheets on characteristics under the company code. Standard (document splitting) characteristics are the profit center, the business area, or the segment, for example. You can display planned values, book values and transactions directly in the Asset Explorer in a print preview format, and you can print and export this information. The following information is automatically set in the asset master record at the time of the first acquisition posting: o Date of asset capitalization (derived from the asset value date). o Date of initial acquisition on the relevant master record (also derived from the asset value date). o Acquisition year and acquisition period (derived from the posting date) In Customizing for Asset Accounting, you can enter default values for the asset value date for each type of accounting transaction. The system determines the start date for ordinary depreciation using the asset value date of the acquisition posting and the period control method (see Deprecation Key for more information), and writes this date to the depreciation areas in the asset master record. When you post the acquisition integrated with FI-AP, the system automatically enters the vendor in the origin data field of the asset master record. The asset value date is the actual date the asset is updated and determines the depreciation start date along with the deprecation key (for each depreciation area). The posting date and the asset value date must always be in the same fiscal year!
Page 11 of 45
The number range interval for the assignment of FI document numbers is defined in the document type. Although the document type is defined across all clients, the FI document number range interval should be created specifically for the company-code. Transaction types must be used with every posting. Transaction types identify acquisitions, retirements, and transfers, amongst other things. If asset acquisition postings are not integrated, you would normally use a clearing account. This should be a general ledger account with open item management to guarantee that you can clear the account (later). Reasons for not making integrated postings: o The invoice arrived before the asset o The asset has already been delivered and should be used, but the invoice has not been delivered. The first process steps in case of FI-AA and MM could proceed as follows: o Create Purchase Requisition (optional) o Create Asset Master Record if required o Create Purchase Order (from PReq) with assignment category A (=> A = asset). In the purchase order, you can specify an asset master record number in the Item Detail screen area. o Goods receipt When you enter the purchase order, you determine whether the asset is posted directly to Asset Accounting when the goods receipt is posted (=> valuated goods receipt), and thereby capitalized, or whether capitalization does not take place until the invoice (=> invoice receipt) is posted (non-valuated goods receipt).
Lesson 2 Assets Retirement

There are different ways of posting retirements: o Retirement with revenue and customer (=> integrated asset retirement) o Retirement with revenue, but without customer (=> not integrated) o Retirement without revenue (=> Asset retirement by scrapping) o The first three points can each be entered either as complete or as partial retirement o Mass asset retirement (with work list) o Retirement of several assets (within the manually posted retirement transaction). The system determines the period for the asset retirement based on the asset value date of the asset retirement (= asset retirement date). Using the period control method (=> period control key of the depreciation key), the system automatically calculates how long depreciation is (allowed to be) posted for the asset. The system automatically determines the proportional value adjustments (depreciation) up to this period that apply to the part of the asset being retired, and cancels this depreciation. At the same time, the system posts the asset retirement. To carry out a mass retirement, follow these steps: o Use an asset report to create a list of the assets to be retired. o Create a work list. o Select a purpose for the work list: Retirement without revenue Retirement sale (with revenue) o Enter the revenue distribution. o Process the work list, or edit the work list before releasing it.
Page 12 of 45
Lesson 3 Intercompany & Intra-company Assets Transfer

Asset Accounting distinguishes between different types of transfers, depending on circumstances: o transactions within one company code (=> Intra-company Transfer) or o Transactions between different company codes (=> Intercompany Transfer). Possible reasons for intercompany code transfers: o A master record was created and posted to in the wrong class (in the previous year). o You would like to split up an asset or move part of an asset. Part of the asset must thus be transferred to a new asset. o You would like settle an asset under construction and transfer it to a finished asset. The system uses transfer variant 4 by default for intra-company asset transfers. One of the functions of the transfer variant is to determine the transaction types with which the transfer is recorded in the source and the target asset. The Transfer function can be used when: o an asset has been sold to another company code, The following distinction is made for transfers: o ... Whether it is a transfer within a legal unit (within a company). In the case where both company codes belong to the same company, SAP refers to a transfer of relationship type 02. o ... or whether the transfer is taking place between legally independent organizational units (=> company codes) which are each assigned to a different company. This arrangement can also be redefined using a relationship type it is a relationship type 01 transfer. The transfer method is used to control how the values are transferred from the source to the target company code. o If you select the Gross transfer method, this method transfers the historical values of the asset to the target company code. o When you use the Net method or the New Value Method, you have to enter sales revenue. o If there is no gain or loss on the asset retirement, the sales revenue equals the net book value of the asset. o Using the Net Method, the net book value (of the source company code) is capitalized on the target asset. o When you use the New Value Method, the system capitalizes the amount of the sales revenue on the target asset. The standard SAP assumption is that transfers of relationship type 02 (=> two company codes but one company (number)) are always transfers within one legal unit (=> the company within a corporate group), and are therefore always represented as intra-company transfers (=> with intracompany transfer transaction types and the gross method). The individual company code is not an independent legal entity, and does not create balance sheets for external purposes. If company codes are assigned to different charts of depreciation, the charts may contain different depreciation areas (=> different keys/different area IDs) but have the same functions. When this is the case, you must define cross-company depreciation areas before asset transfer. If a corresponding cross-company depreciation area is not defined, the system enters an asterisk (*) as a generic entry for the cross-company areas.
Lesson 4 Assets under Construction

Assets under construction have two phases that are relevant to Asset Accounting:
Page 13 of 45
o The under construction phase o The useful life phase The assets have to be shown in two different balance sheet items during these two phases. Therefore, they have to be managed using different objects or asset master records for the under-construction phase and for the completed asset(s). The transfer from the under-construction phase to completed asset is referred to here as capitalization of the asset under construction. Assets in the under construction phase in FI-AA can be managed in the following ways o As a normal asset master record (=> for summary settlement) o As an asset master record with line item management When capitalizing the asset under construction, the system automatically separates the transactions from the previous years from the transactions from the current year. This is done by using different transaction types. Proceed as follows to settle the asset under construction on a line-item basis to one or more completed assets: o First, assign a settlement profile to your company code o Select all line items that you want to settle in the same proportion to the same receiver. o Define distribution rules for these line items. o Post the settlement of line items to the specified receivers using the distribution rule. Note that this posting procedure settles all line items to which a distribution rule is assigned. When you settle, you do not have to settle all line items at once, and you do not have to distribute 100% of each line item.
Lesson 5 Unplanned Depreciation

When you enter the relevant transaction type, the system recognizes that you want to perform manual depreciation. As you have only manually scheduled the depreciation, the system does not create an FI document. This FI document is not generated until the depreciation posting program is run.
Page 14 of 45
Unit 4 Periodic Processing and Valuation

Lesson 1 Function of Assets class
If you want to plan primary costs on a cost center basis, you can periodically determine planned depreciation and interest and pass these on to primary cost planning in the CO system via a report. Investment support is a subsidy that a company receives for certain asset investments. Assets that are eligible for such a subsidy are marked in the asset master records with an investment support key. All specifications for claiming the investment support are stored in the definition of this key. You can post the claim manually or in a mass procedure. Inflation management is required in countries with high rates of inflation or deflation. You can now also use the Schedule Manager in FI-AA to define, schedule, process, and control periodically recurring activities. Depreciation areas are identified in the system by a two-character numeric key. We can define Depreciation area for following reasons: o Define how to post the asset balance sheet values and depreciation to the general ledger accounts. o For reporting reasons only. They will show values and calculate depreciation, but will not post any values to G/L accounts. o To calculate different values in a depreciation area for a specific purpose (for example, for the balance sheet, for cost accounting, or for taxes). o To define which values have to be managed (for example, APC or positive/negative net book values)? o To define how posting values and depreciation terms should or can be transferred to other areas. The system supports the following depreciation types: o Ordinary depreciation: This is the planned reduction in asset value due to normal wear and tear. o Special depreciation: This represents a purely tax-based type of depreciation for wear and tear. This form of depreciation usually allows for depreciating a percentage of the asset value, and this percentage may be staggered within a tax concession period, without taking the actual wear and tear on the asset into consideration. o Unplanned depreciation: This is concerned with unusual circumstances, such as damage to the asset, that lead to a permanent reduction in its value. o Unit-of-production depreciation: This allows you to take fluctuations in activity into account for the depreciation calculation. It makes the amount of depreciation dependent upon seasonal usage of the asset (example: Driven kilometers of a truck or produced units of a machine) Specifications and parameters that the system requires to calculate depreciation amounts are entered in calculation methods which are assigned to the depreciation key Individual calculation methods are: o The base method o The declining-balance method o The maximum amount method o The multilevel method
Page 15 of 45
o The period control method The depreciation terms are stored in the asset master record. The system determines the depreciation start date using the asset value date and the period control method. The Asset Explorer displays the values and the depreciation for every transaction and each area. Changes to the settings of the depreciation keys (=> customizing changes) do not automatically lead to a correction of depreciation amounts for already posted/active assets. For that to happen, you have to execute a recalculation of depreciation: With SAP Solution ERP 6.0, (and active Enterprise Extension EA-FIN, the calculation logic for depreciation changed from transaction based calculation to calculation on the basis of period interval Nonetheless, the new way of calculating depreciation (=> nwc also mentions the use of the Depreciation Engine) does enable in principle a more exact and precise calculation of depreciation amounts.
The logic and method for working with time-dependent depreciation terms is comparable with the procedure for time-dependent data in the master data area. Time-dependent changes can therefore also be defined by creating new intervals. Summary: Whats new in FI-AA deprecation calculation with ECC 6.0 and active Enterprise Extension EA-FIN (=> Financial Extension) : o Depreciation calculation on the basis of period intervals/use of the Depreciation Engine o Time-dependent depreciation terms o Support for an (automatic) changeover method to period/months. However, this is not a standard method, it must be implemented using the BAdI (Business Add-In) FAA_DC_CUSTOMER If time-dependent depreciation terms are not used, a change would have the effect that all open (and future) fiscal years are/were recalculated. The new logic of the depreciation calculation creates a new period interval for a mid-year changes to the term. You can define whether interest should be calculated for the cost-accounting depreciation area, and whether depreciation should continue below zero. You make these specifications when you define the depreciation areas. You can use index series for indexing the acquisition value and thus calculate a replacement value. Automatic calculation of Depreciation Indicator means: o Depreciation after planned life end: This indicates that you want the system to continue depreciation after the end of the planned useful life.
Page 16 of 45
o Depreciation below book value: Set this indicator if you want the system to continue depreciation after the book value is zero. The depreciation area must allow negative net book value (=> a changeover key may be used). o Effective life after planned end (=> with curb): The actual, not the planned life determines the rate of depreciation. For cost accounting, you might have to calculate imputed interest on the capital tied up in assets. Specify the following settings: o Allow the calculation of imputed interest for the depreciation area. o Determine that interest should be posted for the company code and the corresponding depreciation area. o Use a depreciation key to which calculation methods for the depreciation type Interest are assigned, or define such a key user-specifically. o If the calculation of the interest is based on a replacement value, the system calculates indexed interest. The system posts interest (periodically) during the periodic depreciation posting run. It posts to the accounts that are entered in the account determination for each depreciation area. Furthermore, an additional account assignment can be made to the cost center or the internal order entered in each asset master record (as is the case with depreciation). If revaluation (indexing) is used in a depreciation area, you can specify a default index series for calculating the replacement value in the asset or asset class. For each fiscal year, you should specify index figures for the index series. If they are missing, the system switches to a simulated annual rate. An indexed revaluation can also be calculated for accumulated depreciation and imputed interest (if the interest calculation key is based on replacement value). Specify in the depreciation area if you want to post to the general ledger, indicating whether you want to post revaluation of APC only, or also include depreciation/interest. The depreciation position program RAPOST2000 can be used to post (if required) o Ordinary depreciation (book depreciation and cost-accounting) o Tax depreciation, or allocation and write-off of reserves due to special tax depreciation o Unplanned depreciation (or other manually planned depreciation) o Imputed interest o Revaluation of APC or of accumulated depreciation Program RAPOST2000 posts without session directly to the G/L accounts and (if you want, also) to additional account assignment objects. Only real CO account assignment objects can be posted. However, you can make additional, statistical postings to other objects
Page 17 of 45
Carry out all essential checks during the test run, and records any errors: o Incorrect account assignment objects (for example, a cost center that is locked in CO) o Account assignment types missing in Customizing for Asset Accounting. You receive the error message Account xxxx requires an assignment to a CO object o Accounts for depreciation posting missing o Posting period was entered incorrectly (related to the posting interval entered in Customizing) on the initial screen of RAPOST2000 o Settings missing for the depreciation posting cycle in the depreciation area
Lesson 2 Fiscal Year Change and Year End Closing in Assets

The fiscal year change program opens new annual value fields for each asset. o The earliest you can start this program (in the production system) is in the last posting period of the current year. o You have to run the fiscal year change program for your whole company code. o You can only process a fiscal year change to a subsequent year if the previous year has already been closed for business Year-End Closing (in Asset Accounting) - Preparations: o After the depreciation lists and asset history sheet have been checked, depreciation is posted. o If an area posts asset balances periodically to the general ledger, you must start the report for periodic asset balance postings (=> RAPERB2000) (at least once in the update run). o If the final result is not satisfactory, you can carry out depreciation simulation or (bulk) changes, or make adjustment postings. o If you change any depreciation values, you must run depreciation posting again. The year-end closing program (=> RAJABS00) checks whether: o Depreciation and asset balances are posted in full o Assets contain errors or are incomplete If the program does not find any errors, it updates the last closed fiscal year (for each depreciation area). The report also locks all closed fiscal years against postings from the asset area. If a closed fiscal year is subsequently released for posting, it can only be closed again once the year-end closing program RAJABS00 has been run again. Settings for using program RAPERB2000: o Define(new)document type: o Create number range interval: o Now create the new document type for your company code(s):
Page 18 of 45
Unit 5 Information System

Lesson 1 Report Selection
There is a new graphical design, which makes it even simpler to process and display lists and reports using the ALV Grid Control. Important List Viewer functions: o Deleting and inserting columns o Arranging the values in columns in ascending or descending order o Calculating totals or subtotals across one or more columns within a list o Using layouts to save an individual report structure so that you can use it again later o Set filter: You can choose to have only those lines displayed that meet certain criteria. o You can add any number of asset input fields to ALV reports in FI-AA using FIAA_SALVTAB_* structure A sort variant consists of a maximum of five sort levels which are determined via ABAP Dictionary fields.
Lesson 2 Value Simulation
Use the Asset Explorer to create a preview of how the values for individual assets will develop by means of simulated transactions and/or simulated depreciation terms. Simulation, in this context, refers to an experimental change to depreciation parameters affecting the valuation of assets. This change can apply to a single asset, the entire asset portfolio, or parts of it. Simulation versions allow you to simulate a change of depreciation logic. For each area, asset class, and depreciation key, specifies which depreciation key and useful life should be chosen as alternatives for simulation. The validity interval excludes assets with a capitalization date that lies outside that range.
Lesson 3 Assets History Sheet

The asset history sheet is a very important and comprehensive year-end report or intermediate report. You can create it using various sort versions and totals at any group level, just like any other report. You can create a compact totals list that does not contain information on the individual assets. You can also define your own history sheet versions:
Page 19 of 45
o Size: No more than 10 rows and 8 columns o Store the headers of the history sheet items o Define how the values are supplied to the history sheet items
Page 20 of 45
Unit 6 Standard Reports in General Ledger Accounting, Accounts Receivable Accounting and Accounts Payable Accounting
Lesson 1 Information System
You can find the reports you require in various places in the system: o You can access important reports using the information system for each area (General Ledger, Accounts Receivable, and Accounts Payable) and on the general report selection screen. o Reports are also included in role-based user menus. o Under System, choose System Services Reporting. You must know name of that ABAP report. The reports that start with RF are differentiated by account type. Reports start with RFK_____ (for vendors), RFD_____ (for customers), RFS_____ (for G/L accounts), and RFB_____ (for document reports).
Lesson 2 Report Variant and Variables

You can define multiple report variants for one report. These report variants contain different selection criteria. A variant is a selection memory for a specific quantity of saved selection criteria. Enter variant attributes for your variant; first a Variant name, and then the Description. If you select the only for background processing field, then the variant is only permitted for background processing. If you do not select the field, the variant is permitted for background and online processing. If you select the Protect variant field, then only you can change the variant. System variants are only displayed in the catalog and not in F4 Input Help if you select the relevant indicator. If you call up the report and use a variant, but still want to display certain values up to the current date (for example, open items up to a certain key date), you can use selection variables. Currently, the following two types of selection variables are supported (but not for each selection criterion): o Table variables from TVARV o Dynamic date calculation Table variables from TVARV: You use these variables when you store statistical information that can be used in different reports. This means that when you save the attributes for the variant, you can maintain parameters in table TVARV that contain your selection options, single values, and/or intervals by choosing Maintain environment Selection variables. Once you have maintained these selection variables in table TVARV, you can use them in any other report variants and reports. Dynamic date calculations: The prerequisite for using these variables is that the corresponding selection criterion in the program is type D (date). If you change the selection variable from type T to type D, the Name of Variables field is no longer ready for input. You can only set values using input help.
Page 21 of 45
Unit 7 List Viewer

Lesson 1 SAP List Viewer Design
The SAP List Viewer is a generic display tool that creates a standard ergonomic list from predefined data. The List Viewer standardizes and simplifies the use of lists in the SAP system by providing a uniform interface and list preparation function. You can use the List Viewer to display simple and hierarchical sequential lists. The SAP List Viewer contains a number of interactive functions such as sorting, summation, filters, and so on. You can change the layout of lists without selecting data first and save the changed list layout in variants. Once you have selected multiple items, you can carry out a mass change in the corresponding documents. You can choose whether you want to branch to the document item view or the document overview of the document display. The accounting editing options contain a corresponding checkbox. Some of the functions provided by the SAP List Viewer include the following generic crossapplication functions: o You can sort the list in ascending or descending order. o You can set and delete filters the same way. o Summation: You can create totals and subtotals for specific values. Create totals by selecting the required column and then choosing the appropriate icon. In addition to the display variants provided by SAP, you can also create your own display variants. This allows you to define your own specific view of a list. You can also add special fields to the column set in addition to the fields that are already displayed. For more information, refer to SAP Notes 215798 and 420591. If you require offsetting account information, refer to SAP Note 112312. This is not a modification of the standard system, but a business transaction event. When you display the list, you can choose between the ALV classic list and the ALV grid control (grid design). The ALV classic list is the list that is displayed when no specific settings have been made. Using parameter IDs, you can enter user default values in fields where the value usually remains constant.
Lesson 2 Selections
You can use specific selection criteria to choose line items that you want to evaluate. These selection criteria refer to: o The accounts in which you want to see line items in specific company codes o Selection criteria that you can choose using search help o The selection of line items themselves, based on their status and category o In addition, you can also choose the following for the list output: Layout Maximum number of items If you select the Work lists Available field, you can activate and deactivate the input fields for work lists on the selection screen for each line item list. If the work lists exist, when you select the Work list Input Fields Active field when you call up the selection screen for the line item display, this selection screen is displayed with input fields for work lists.
Page 22 of 45
If you select items using search help, the system provides input help for the G/L account line item list: o G/L account number in chart of accounts (also in combination with the company code specification) o G/L account name (G/L account long text) in chart of accounts (also in combination with the company code specification) o G/L accounts with deletion and block indicators o Keywords o Alternative account numbers When you select items using search help, the system offers input help for the vendor line item list: o General vendor data (search term, postal code, city, name, and number of vendor) o Vendor country/company code o Vendor by personnel number o Vendor by purchase, material, or plant reference When you select items using search help, the system offers input help for the customer line item list: o General customer data (search term, postal code, city, name, and number of customer) o Customer country/company code/account group o Customers with rental agreement o Customers for each sales group or with plant reference o Head office customers When you select open items, you select items that are or were open at a specific time. The current date is proposed by default. If you choose Cleared Items, the system displays items that were cleared by the clearing date specified and that were still open on the key date. If you do not specify the clearing date and the key date, the system displays all the cleared items. If you want to see open and cleared items, choose All Items. You can restrict this selection using the posting date The system automatically fills the assignment field for a line item according to the Sort Field entry in the master record when you post items. The assignment field can be a combination of up to four fields with a maximum of 18 characters.
Lesson 3 Changing the Screen Layout

SAP provides various standard layouts that you can supplement with other (standard) layouts. Standard layouts start with a slash (/). You can choose a standard layout as your default layout. If the indicator for a display variant is set as the initial variant, this variant is always used for the list output unless you explicitly specify an alternative display variant. The following order applies: User-specific initial screen (set as default) has priority over general initial variant (set as default).
Page 23 of 45
Unit 8 Drilldown Reporting in Financial Accounting

Lesson 1 Architecture of Drilldown Reporting
Drilldown reporting is a dialog-oriented information system for evaluating data from the FI, GL, AR, and AP databases. SAP Graphics, SAPmail, and various printing functions are connected to drilldown reporting together with Microsoft Word for Windows and Microsoft Excel. The following report types can be used for G/L account evaluations: o 1. Reports for financial statement analysis: These reports are based on the financial statement versions defined in Financial Accounting. You can carry out any number of variance analyses based on actual and plan data (annual, half-year, quarterly, and monthly). o 2. Key figure reports: For key figure reports, the system takes into account only the financial statement items in the financial statement version that you need for the calculation of specific key figures. This is not the case for financial statement analysis reports. Financial statement version key figures could be for example, equity ratio (stockholders equity: total equity), debt-equity ratio (external capital: stockholders equity), and capitalization ratio (fixed assets: total assets). You can create key figures from report rows and/or columns using an integrated formula interpreter. o 3. Balance display: You can use the following report types for customer or vendor drilldown reports: o a) Balance display o b) Line item analysis A report definition can contain characteristics, key figures, and forms. A report is a number of interactive, controllable report lists and graphics that are displayed on the screen. Drilldown reporting provides useful functions for navigating within the dataset .It also contains several additional functions that can be used to process a report interactively (sorting, specification of conditions, ranked list, and so on). You can send report lists (for example, as a fax), display them on the Internet, or transfer them as files to Microsoft Word and Microsoft Excel. Drilldown reporting also contains functions for printing reports. There are various print preparation Functions for you to structure your report as you require (such as page break, headers and footers, and underlining). A form describes the basic content and formal structure of report lists. A form can be seen as a semifinished product for a report; it is later completed with characteristics and key figures when you define the report. Characteristics appear in the form as well as in the report. You can choose key figures either in the form or the report.
Lesson 2 Characteristics and Key Figures

Characteristics specify the classification options for the dataset. Examples of characteristics are company code, business area, and plan/actual indicator. The time reference (fiscal year, period) is also a characteristic. Characteristic values are concrete forms of a characteristic. A combination of characteristics and characteristic values is generally called an object in drilldown reporting.
Page 24 of 45
Key figures are not just values and quantities, but also calculations involving these values and quantities with user-defined formulas. The following are examples of key figures: o Value: Balance sheet value, debit total, sales/purchases o Quantity: Number of employees, sales quantity o Calculation: Sales per employee, plan/actual variance There are two types of list for displaying information: The detail list and the drilldown list. o In a drilldown list, several objects (for example, assets under construction, vehicles, and chemicals) are formatted using a selection of key figures. Usually, the key figures are in the columns of the list (for example, balance sheet value, total debit postings, total credit postings). The rows contain the characteristic values of all the characteristics that are drilled down. o In a detail list, an individual object (for example, business area) is formatted for all key figures according to the form. Usually, the key figures are in the rows of the detail list (for example, balance sheet value, total debit postings, total credit postings).
Lesson 3 Form Types

The following form types exist: o Single-axis form without key figure If you are using a single-axis form without key figures, you define either the form rows or columns with characteristics. When you access the initial screen, the system displays an empty list with columns. o Single-axis form with key figure If you are using a single-axis form with key figures, you define either the form rows or columns with key figures and characteristics. When you access the initial screen, the system displays an empty list with rows. o Dual-axis form with key figure If you are using a dual-axis form with key figures, you define the form rows and the columns with key figures and characteristics. When you access the initial screen, the system displays an empty list containing rows and columns. You are free to define whether the rows contain key figures and the columns contain characteristics, or vice versa. It depends on what you want to report. When you create a form, you define the name and the type of form that you want to process In a single-axis form with no key figures, you make selections only in the characteristics columns. o The drilldown list contains a two-line column heading. The key figures (for example, balance sheet value, total debit postings, total credit postings) are in the first row and the characteristics that you selected in the form (for example, fiscal year, prior year, and variance) are listed below. The values for the drilldown characteristics are in the rows (for example, assets under construction, vehicles, and chemicals for the business area). o In the detail list, the characteristics chosen in the form are contained in the columns, and the key figures are contained in the rows. The detail list displays the results of a selected characteristic value (for example, assets under construction for business area). In a single-axis form with key figures, the key figures are integrated with characteristics in the rows of the form (for example, fiscal year balance sheet value, prior year balance sheet value with variance).
Page 25 of 45
o In the report definition, only the drilldown characteristics are chosen (for example, business area, financial statement item account number, and so on). In the drilldown list, the key figures integrated with the characteristics are the columns of the form, and the values of the drilldown characteristics form the rows (for example, assets under construction, vehicles, chemicals, and so on) o The detail list has one column and contains the selected characteristic value for which you want to report (for example, assets under construction), and the key figures are in the rows. Therefore, for single-axis forms with key figures, the key figures are defined in the rows by default. In a form with two axes (matrix), both the rows and columns are defined using key figures or characteristics. The key figures have to be in either the rows or the columns of the form, but you can enter the characteristics in the rows and the columns. o When you define the report, you then choose only the drilldown characteristics (for example, business area, company code, account number, and so on).
Lesson 4 Navigation in Reports

If you want to switch from the drilldown list to the detail list, choose the Detail list symbol. All of the row selection symbols are then highlighted in a different color. If the basic list is defined as the detail list for a report, the detail list is the first screen to be displayed when you execute your report. If you want to switch from the detail list to the drilldown list, choose Drilldown list. The system then highlights all the free characteristics in the navigation block. Choose a characteristic by clicking it. The system then displays the drilldown list. The navigation area for the drilldown list contains additional characteristics that you can use. If you want to exchange the FS item with another characteristic, for example, Period, first click FS item and then Period. The two characteristics then change places: FS item is now available for selection in the navigation block, and Period is drilled down for all characteristic values.
Lesson 5 Form & Report Definition

SAP delivers standard forms, which you can use as templates to create your own forms. The names for these standard forms are 0SAPBLNCE-01 through 0SAPBLNCE-NN, and you cannot use these names for your own forms. Step for creating Form o Defining characteristics for all columns (general selections): o You first define the characteristics that you want to be valid for all columns in your form. Since you want to enter actual data in all the columns of your form, you can define this general characteristic by choosing Edit General Selections. o A dialog box appears for you to select the characteristics for the general selections. In the dialog box, add the characteristic Record type to the table of selected characteristics and define the value 0 for actual data. o Once you have defined the general characteristics, you can then define the characteristics of the individual columns. o A dialog box appears, in which you can select Key figure with characteristics. A second dialog box appears. Choose Balance sheet value (BILWERT) from the list of available key figures. In this case, the key figure reflects the values of the balance sheet that you want to evaluate for your report.
Page 26 of 45
o Then define the characteristic values for the characteristics that you have selected. o You can enter three different lengths of text. These are then used as the column headings for the elements. You can enter a short, medium, and long text. Using the text type, you can later determine which text is used for each column. If you want to enter a two-line heading, you must separate the two lines using a semicolon (;). o In the third column, you define the variance between the first and the second column. o To do this, place the cursor on the third column and choose Edit Element Define Element. o On the following screen, choose Formula. The formula editor appears, in which you define the formula that is to be used to calculate the variance. Using the formula editor, you can perform standard arithmetic operations (+, -, *, /) with any elements. o Save the form. Steps for Creating Report o Enter the name of a new report or choose the name of the report whose definition you want to change. You can choose a reference report if necessary. o On the Characteristics tab, the system displays a list containing all the available characteristics. In the characteristic list, select the characteristics that you want to use for your evaluation in the report, and use the arrow buttons to add them to the report. These characteristics are the drilldown characteristics that you use to navigate in the report. o Using the Sort characteristics function, you can determine the order of the characteristics in the navigation block of the report list for the executed report. The number of characteristics offered for selection is restricted by the selection criteria defined in the form. If you have already specified a characteristic in the form, it is no longer offered for selection. o Once you have selected a characteristic, all the values for this characteristic are included in the report. There are various ways of restricting the value quantity of a characteristic for output in the report. o On the Characteristics tab, you can restrict the characteristic values for each drilldown characteristic chosen. There are various options dependent on the report definition and the characteristic selected. You do not make an entry. If you do not make any of the restrictions described below, the system selects all the characteristic values when you run the report. You define a characteristic value for a characteristic. The characteristic and the characteristic value then appear above the navigation block on the report list and have been defined (that is, you cannot use the characteristic as a drilldown characteristic). You use a variable for characteristic values
Lesson 6 Report/Report Interface and Report Assignment

If you want to report on a number of characteristics or changing combinations of characteristics, you would have to define a very comprehensive report that might not actually be executable online due to the large volume of data. The report/report interface enables you to link several individual reports, each with a limited number of characteristics, to perform flexible data evaluations online. Recipient objects can be other drilldown reports, report portfolios, BW reports, ABAP reports, Report Writer reports, or transactions. Using the report-report interface you can, for example: o Link reports that contain different characteristics in an application. This enables you to report on a larger number of characteristics than with individual reports.
Page 27 of 45
o Link reports created in the different application classes. You assign the recipient reports in the report definition by choosing Options. Choose Report Assignment and define the report type (report portfolio, BW report, drilldown report, ABAP report, Report Writer, or transaction).
Page 28 of 45
Unit 9 Special GL Transactions

Lesson 1 Application view for Special GL Transactions
Transactions in the sub ledgers (accounts receivable and accounts payable, for example) are also posted on the reconciliation accounts in the general ledger. The reconciliation account to be posted to is entered in each customer/vendor master record. The Reconciliation Account field can be found in the company code segment of the customer/vendor master record. If, for example, a customer invoice or customer credit memo is entered on an account receivable, it is posted in the same way on the created reconciliation account. Special G/L transactions are transactions in the accounts receivable and payable, which are displayed separately in the general ledger and the sub ledgers. This may be necessary for internal reasons or for certain report purposes. Special G/L transactions can be divided roughly into three classes: o Down payments o Bills of exchange o Other transactions There are three ways (special general ledger types) of transferring special general ledger entries to the system. o Automatic offsetting entries (statistical) are transactions that are always posted on the same offsetting account. They are usually included in the notes to financial statements. Example: Posting of a guarantee of payment. To simplify the posting procedure, the number of the account for the offsetting entry is defined in Customizing. The system then makes the offsetting entries automatically. When you clear open items in the respective account, the system clears the respective items in the offsetting account automatically. These transactions are called statistical postings, since they are generally only shown in the notes to the financial statements (or not at all). o Noted items are individual account assignments that are only used to remind the respective department of due payments or payments to be made and are not intended to be displayed in the general ledger. Example: Down payment request. Noted items are special G/L transactions with informational character which only remind the user about due payments or payments to be made and are not displayed in the general ledger or added to it. Only one line item is updated if a noted item is created. No offsetting entry is Made. As a result, no zero balance check is made. The payment program and the dunning program can access noted items for further processing. o Free offsetting entries are part of the financial statements. They are postings with freely definable offsetting entries. Example: The bank posting of a received down payment. Special G/L transactions defined as free offsetting entries create proper postings in the general ledger. The alternative reconciliation account is debited or credited automatically, depending on the type of posting. The G/L account for the offsetting entry must be entered by the user
Page 29 of 45
Down Payment in the Customer Area - The procedure is as follows: o Down payment request: Down payment requests are noted items. They do not change any account balances. You can issue dunning notices and make payments automatically based on down payment requests. o Down payment received: Received down payments are displayed as payables on your accounts. They must not change the balance of the Receivables reconciliation account. Received down payments are administered in the Down Payments Received alternative reconciliation account, in the Payables area on the financial statements. o Customer invoice: The customer receives an invoice whenever goods are supplied or services performed. o Posting a down payment clearing with invoice: The down payment is no longer considered a down payment from this point. The amount should/must be displayed as payment on the normal reconciliation account. o 5. Clearing of the items during the payment of the customers balance Disputed or doubtful receivables are entered as individual value adjustments when preparing the balance statements for year-end closing. The special general ledger procedure is suitable here, since the transaction is entered in the customer account as well as posted to the special G/L account, Individual Value Adjustments for Receivables. Description of the procedure for individual value adjustments: o The receivable is entered to the customer account. o The individual value adjustment (without tax) is entered. The expenses are now at the right place on the Expense for Individual Value Adjustment account for the income statement reporting. o The individual value adjustment is cleared after the key date for the balance sheets, meaning it is reversed. o The final value adjustment is made after you ascertain that the receivable is uncollectable. In this case the Expenses for Uncollectable Receivables account are posted to. No special G/L account is used, since adjustment postings must be made on the regular customer reconciliation account. Bills of exchange are a type of short-term financing. If an invoice is paid with a bill of exchange, the payment period is extended for your customers (for example, to three months). If you wish, you can pass on the bill of exchange to a third party to refinance it. It can be discounted at a bank prior to the due date, which means the bank charges interest. Bills of exchange are treated like special G/L transactions in the SAP system. These transactions are therefore automatically recorded in the sub ledger, separately from other transactions, and posted to a special G/L account. As a result, you can obtain an overview of the activities concerning bills of exchange at any time. You can post receivable and payable bills of exchange and incoming and outgoing checks and bills of exchange. Example of a receivable bill of exchange free of charge as displayed above: o The receivable is entered to the customer account. o The customer initiates the payment with a bill of exchange. The account balance is now registered as a receivable bill of exchange and not as the normal balance of the account receivable. o The bank collects the money from the account of the customer on a fixed date. o The collected amount is transferred to your company account. o The amount is posted to the account of the customer and the respective accounts cleared.
Page 30 of 45
Lesson 2 Configuration of Special GL Transactions

Special G/L transactions are posted from the application side using special posting keys and special G/L indicators. The posting keys require a special configuration for this. The special G/L transactions in the standard system are assigned the posting keys 09, 19, 29, and 39. The special G/L accounts have been defined as reconciliation accounts for the D or K account types. In contrast to normal reconciliation accounts (customers/vendors), the line item display is generally active for special G/L accounts. This means a list of the line items can be displayed. The special G/L indicator defines the particular configuration of a special G/L transaction and the account type (customer or vendor account). Under properties of special GL, o Relevance for credit limit check: You can include special G/L transactions in the credit limit check for customers. Noted items are generally not taken into account. All other transactions can be selected accordingly as desired by the user. o Warning against commitments: You can define a warning message to notify the user of the existence of a special G/L transaction when posting to a customer or vendor account. o Target special G/L indicator: This entry is only relevant for noted items. For noted items, you can set which special G/L indicators are allowed to be added as target special G/L indicators when entering (applying) a payment request. The target special G/L indicator is used in the standard system for down payment requests. o Special G/L transaction class: The special G/L transaction class determines whether the transaction is a down payment, a bill of exchange, or any other type of transaction. o Posting key: Only these posting keys can be used with the respective special G/L indicators.
Page 31 of 45
Unit 10 Parking Documents

Lesson 1 Basics of Parking Documents
Document entry can be I interrupted for a variety of reason. The user departments looking for a way of temporarily saving the data entered up to the point of interruption, to resume entry at a later time. There are two different ways of saving documents (without performing proper Financial Accounting posting): o HOLDING documents The Hold Document function lets you save data that has been entered temporarily, to continue entry at a later time. Documents held by the system do not have to be complete. No account balances are updated and the data of the document is not available for evaluation. No document number is assigned. The person making the entries is asked to name the document after selecting the Hold Document function. The document can be found under this name at a later time. o PARKING documents Document parking enables you to enter incomplete documents in the SAP system without having to run the extensive input checks. When parking documents, the system assigns a document number via the document type in the same way as with normal Financial Accounting postings. The user must pass on the number if it has been assigned externally. Data from parked documents is available to the system for real-time evaluations. Data can be parked for accounts receivable, accounts payable, G/L accounts, and assets. Only receipts can be entered for assets, however. Postings for down payments cannot be parked. No data, such as transaction figures, can be updated when parking documents. The only exception to this is cash management. The tax amounts calculated on the basis of the parked document can be used to assert claims with regard to tax in due time at the tax authorities. Substitutions are not supported by the document parking feature. If you want to use substitutions with parked documents, you have to turn them into accounting documents first.
Lesson 2 Parking Documents & Processing Parked Documents

Areas of use for document parking o Temporary storage of input values when parking documents o Helpful for displaying multilevel models when parking documents (for example, dual-control principle, approval procedures) o Work assignment using work lists (streamlining/acceleration of workflows) Ways of using document parking o Customer accounts (invoices and credit memos) o Vendor accounts (invoices and credit memos) o G/L accounts (G/L account postings) The document change rules that are saved for documents posted in the system do not apply to parked documents. The currency, the document type/number, and the company code cannot be changed.
Page 32 of 45
Whenever a parked document is posted, the data from that parked document is deleted, a document is written to the document database, and the respective data (transaction figures and so on) is updated. The document number of the parked document becomes the number of the posted document. You can delete parked documents that you do not want to post. Note that the document number of the deleted document cannot be reused in such cases. The document has status Z: Parked document that was deleted. Document parking is linked to the account display and reporting functions in Financial Accounting. Numerous reports can evaluate parked documents.
Lesson 3 Document Parking and Workflow

In SAP Business Workflow, the four process dimensions o Organizational structure (Who?) o Process structure (When? In what order? Under what circumstances?) o Function (What?) o Information (With which data? The process to be modeled as a workflow is saved in the system as parameters, using a graphic definition tool. During the process, the workflow manager that is, the system - performs all the tasks that were conceived when the process was defined. As a result, users are relieved of any avoidable organizational tasks and can concentrate on the aspects of their actual work. Simply, workflow means: The right work at the right time for the right employee. SAP Business Workflow has three-tier architecture. This modularization of components provides the foundation for a high degree of flexibility. o The right work: Whatever you wish to do during the workflow, it must be implemented in the Business Object Repository as a method of a business object type. o At the right time: The process level describes the business process as a sequence of individual steps. The workflow definition is the total of all steps put together. Individual steps can refer to methods of the BOR (Business Object Repository), but they can also be used to control the process - for example, to enable loop-type processing, query conditions, or provide values in the interface (= container). Workflow Builder is the tool you use to maintain the process level. o For the right employee: The organizational level establishes a link to the organizational structure. The business process is stored in the workflow definition. The event-driven process chain (EPC) is used to display the process. Single-step tasks are essential elements of the workflow definition.
Page 33 of 45
Single-step tasks Represent the SAP functions from a business point of view Every single-step task uses precisely one method The SAP Business Workflow is based on an object-oriented structure. Objects are defined in the object repository provided by SAP. Object methods o Represent the SAP functions from the view of the business object (technical view - for example, create, delete, change) o Provide a uniform, transparent interface for SAP functions (transactions, function modules, reports, ...) o Are used to encapsulate the functions The processors responsible for a specific activity in the workflow are defined either by their assignment to an object of the organizational structure or by means of a rule. Rules are used to determine the responsible processors dynamically, that is, independently of information that is only available at runtime. Workflows are usually initiated by a triggering event. Events are used to display the changes in status of objects within the system. Like methods, they are defined in the object repository for each object type. Events are triggered in the respective applications. WHAT Is Carried Out? Workflow-Related Tasks o Posting invoices o Releasing purchase requisitions o Changing material masters o Approving leave o Creating customer accounts o Deleting purchase orders o Creating requirement coverage requests via the Internet Tasks represent steps of the business process. The process you want to model must be broken down into individual tasks during the definition. The definition of the workflow determines the tasks and the order in which they are to be carried in the process. The Workflow Builder is the main tool of the Web Flow Engine. It allows workflow definitions to be created, changed, tested, and displayed. Each task must be assigned possible processors. This is the group of employees at your company who come into question for carrying out the respective task. The Business Workplace consists of three screen areas: o Selection tree: You can find the selection tree on the left side of the Business Workplace. From here, you can select work items to be executed, workflows you have started, and documents. o Work list: The work list is displayed at the top right of the Business-Workplace screen in case you want to mark the Workflow folder. The system automatically puts the entries in groups in this folder. There are special folders in which you can find overdue work items or missed deadline work items. If you mark Inbox in the selection tree, you can see all work items and documents in this area of the screen. o Work item preview: The work item selected from the work list is displayed in a preview at the bottom right of the screen. Not all functions of the work item display or workflow log are available. It is possible for the user to make a decision from within the work item preview. The Web Flow Engine determines the recipients of the work item. All selected recipients can view the work item and perform it at their Business Workplace. Only one user can perform the work item, however. If, therefore, a user starts to perform the work item, the other recipients are unable to
Page 34 of 45
execute this work item. A recipient can accept a work item. An accepted work item can only be performed by the user who has accepted it. Workflow variants can be created for document parking in Customizing of FI. Whether the document release is supposed to be active is specified here together with the minimum amount for which this is necessary. The company codes can be assigned workflow variants. No documents are released if any company code is not assigned a workflow variant. The workflow variant and the corresponding company codes must have the same currency. The release group is required to determine the release approval path at the time of processing. The release approval path is determined by the workflow variant in connection with the document type and release group. The sub workflows that is initiated by releasing the amount and who is to release are determined by the release approval path and the particular amount. If no release group is defined, the initial release group is then used for access.
Page 35 of 45
Unit 11 Validation & Substitution

Lesson 1 Basics of Validation / Substitution
The validation function helps you to check the entered values and value intervals. When data is entered in the system, the Rule Manager validates the data according to the validation rules. In substitution, the values entered into the SAP system are validated according to a prerequisite defined by the user. If the prerequisite is met, the system replaces the values entered with other values. The following measures are required to execute validation/substitution: o Decide for which area of application validation/substitution should apply. o Correct call up point for the validation/substitution must be selected. o The validation/substitution must be defined. o You must assign your validation/substitution to an appropriate organizational unit o activate it The application area is where the validation, substitution, or rule is used. The following application areas use validations and substitutions: o FI Financial Accounting, o CO Cost Accounting, o AM Asset Accounting, o GL Special Purpose Ledger, o CS Consolidation (validations only), o PS Project System, o RE Real Estate, o PC Profit Center Accounting (substitutions only), o GA Allocations (FI-SL) (substitutions only) Call up points is specific places in an application that specify the exact location where a validation/substitution occurs. The combination of application area and call up point determines the Boolean class for a validation, substitution, or rule. Boolean classes establish the dimensions that can be used in the definition of validations, substitutions, and rules. They also specify which message classes can be used for validation messages. Three call up points have been provided for FI: o 1. Document header o 2. Document line o 3. Complete document The fields that are available for call up point 1 are also available here for possible cross-validations. At the Complete document call up point, you can use only those numeric fields with which you primarily execute mathematical calculations.
Page 36 of 45
The formula editor provides a user-friendly interface for entering arithmetic and logical statements. You can work in the Formula Builder using three different settings: o The default setting when you call up the Formula Builder is Short descriptions. All operands (such as table fields, sets, exits, and so on) are displayed using their respective descriptions. o If you want to enter statements using the technical names of the operands rather than the descriptions, change the setting by choosing Settings Technical names. o By setting Expert mode, the technical names of the operands are displayed. You can also enter a statement directly. In this case, the statement field is ready for input. The following elements are available to enter rules for the prerequisites (validation & substitution) and checks (validation): o Operands o Logical operators (Boolean terms) and o Comparison operators.
You must assign your validation/substitution to an appropriate organizational unit it means a validation/substitution can be valid for several company codes at the same time. Only one validation/substitution can be activated for one company code for a call up point. Furthermore, the validation/substitution for the correct call up point must be activated. o Inactive o Active for dialog and batch o Active except for batch input
Lesson 2 Definition and Execution of Validation in Financial Accounting

Validation enables the customer-specific validation of certain fields / field combinations / document types. Validation consists of several steps (up to 999 are possible), each with 3 parts: o Prerequisite o Check o Message
Page 37 of 45
If the prerequisite statement is satisfied (TRUE), a check is performed. If the result of the check is FALSE, the system posts a message. You can use a predefined message or create a new message for validation. A message can contain up to four fields. Messages can have different meanings: o I = Information o W = Warning o E = Error (requires the entry to be corrected) o A = Cancel The & character is used as a wildcard for field values to be output in the message. You can do the following in a logical statement: o 1. Compare fields with one another: This statement is TRUE if the date in the document date field is not the same as the date in the posting date field. o 2. Validate field contents for certain values: In this example, the document type must be SA. o 3. Check or compare only a part of the field. If you want to execute such a partial check, enter the following: Example: BSEG-HKONT :3: The system checks only the third digit of the Account field to determine if a condition is TRUE. Example: BSEG-HKONT :1-3: The system checks only the first three digits of the Account field to determine if a condition is TRUE. Example: BSEG-HKONT: 3-: The system checks from digit 3 to the end of Account field to determine if a condition is TRUE. o 4. Compare text patterns in your statements using the LIKE keyword. Example: BSEG-KOSTL LIKE *3*3 Within text pattern searches, you can also use the + sign to represent a single character.
Lesson 3 Definition and Execution of Substitution in Financial Accounting

Substitution permits the customer-specific enhancement (substitution) of certain field contents. Substitution consists of several steps (up to 999 are possible), each with two parts: o Prerequisite o Replacement If the prerequisite is satisfied (TRUE), substitution is performed. For each of the fields you selected, a dialog box appears in which you can define the substitution method. You can choose between: o Constant value o Exit o Field-field assignment You can then later enter a constant value, the name of an exit to be carried out at runtime or the name of a field, the content of which is to be used for the substitution. A substitution step contains the following components: o Prerequisite
Page 38 of 45
The prerequisite statement establishes which conditions must be fulfilled before the substitution can be performed. If the prerequisite statement not fulfilled (false), the transaction is continued without substitution. If the prerequisite statement is true, the transaction is continued with the substituted value(s). o Substitution value(s) The substitution value is a numerical value or a string of letters that replaces the value entered. A single substitution process can replace more than one value.
Lesson 4 Additional Technique for Substitution/Validation

A rule is a logical statement that you can use in a prerequisite statement, a check, or another rule. A rule permits complex logic to be summarized; it can be reused. Technically, a rule is nothing more than, for example, a prerequisite or check of a validation. The rule name can be a maximum of 11 characters long. A set is a flexible data structure for mapping ordered amounts and hierarchies. Sets are maintained and administrated centrally. They are used in almost every component of the FI-SL system: in Boolean logical formulas in validation, substitution and ledger selection, during allocation (assessment / distribution), in planning, in roll-ups, in currency conversion, and so on. To improve system performance, you should use basic or single-dimension sets rather than long lists of Boolean statements or user exits. You can use multisets (a combination of sets for various fields [dimensions]) to execute crossvalidation with values of different characteristics.
Lesson 5 Validation Rule for Account Assignment combination

With introduction of new validation rule for account assignment, now we can do following o The validation is not scenario-dependent.e.g you want to check / validate the presence of a segment this is performed without checking if the scenario Segmentation (FIN_SEGM) is assigned to a ledger. o In the application, the validations for account assignment combinations are checked when simulating the FI documents, not during posting. o The validation accesses the entry view and not the general ledger view (just as transaction code OB28). Invalid account assignment combinations = Non-valid combinations Valid account assignment combinations = Valid combinations The validation type specifies whether the defined rules or account assignment entries are to be checked with regard to their validity. It also specifies how the system is to interpret the rule later.
Page 39 of 45
Page 40 of 45
Unit 12 FI Archiving
Lesson 1 Basics of Parking Documents
Data archiving in SAP lets you safely remove application data that is no longer required for day-today activities from the database. This transferred data is saved to archive files that can be accessed at a later time. The result is a lean database that can be administered efficiently and inexpensively. Data archiving is the consistent transfer of data objects from SAP system database tables; all the table entries that characterize a data object are written to an archive file outside the database. Business consistency is ensured by SAP archiving programs that, based on archiving objects, store all relevant table entries together elsewhere. Data is archived in online mode, in other words, the system does not have to be shut down during archiving. Archiving is not o Reorganization because during database reorganization, data is removed from and loaded back into the database to optimize the physical distribution of data on the hard disk. o A backup means storing the contents of the database to avoid data loss in case of system failures. The goal is to restore the database as closely as possible to the condition it was in before the failure. Backups are generally made at fixed intervals and according to a fixed procedure. Reloading the saved data is called restoring. o The storage of documents is generally considered to be the electronic storage and administration of documents on storage systems outside of the SAP system. The documents are transferred to a document storage system; the SAP system then contains a link pointing to the externally stored document and permitting access. o Only data from completed business processes can be archived. Test data seldom reaches this status.
Data must be archived in such a manner that it can be called up at any time for queries. These queries can come from, for example, tax authorities. Data is archived independently of the version of the hardware and software (metadata is stored). In this way, archived data can be easily called up, even after a system upgrade. The actual data archiving process has three steps: o Generating the archive file(s): In the first step, the write program generates one (or more) archive file(s). Then the data to be archived is read from the database and written to the archive file(s). o Storing the archive file(s): After the write program has finished generating the archive files, they can be stored. o Deleting data: The deletion program first reads the data in the archive file and then deletes the corresponding records from the database.
Page 41 of 45
Lesson 2 Preparatory Activities System Settings

A central element in data archiving is the archiving object. It defines the smallest unit that can be archived in and deleted from the database in its entirety and describes how and which database objects must be accessed to completely archive a business object. An archiving object is basically made up of three components: o Data declaration part o Customizing settings o Programs The data declaration part describes all the relevant database objects that characterize an application object. The Customizing settings are used to set archiving object-specific parameters for an archiving procedure. Among other things, archiving object programs include: o A write program that writes the data objects sequentially in the archive files, o A deletion program that deletes from the database all the data objects that could be read in the archive file beforehand, and o A display program that permits archived data objects to be read.
Step 1: Basis Customizing In Basis Customizing (transaction FILE), a logical file path is defined if one does not already exist as a global path for data archiving and a physical path is assigned to it. The logical path is used merely as a bookmark for the physical path that is generated at runtime. (This is executed by Basis Support / System Administration employees.) Step 2: Cross-Archiving Object Customizing The parameters set here apply to all application and archiving objects for using all archiving objects. Therefore, these settings are executed by the Basis administrator. Information provided by the data archiving monitor includes: - Overview of all archiving objects that have run - Detailed information about the individual archiving procedures - Progress bars while processing archive files - help analyzing open alerts Step 3: Archiving Object-Specific Customizing The parameters that can be set here apply only to the corresponding archiving object. In archiving object-specific Customizing, settings for the deletion program are maintained in addition to a logical file name for the specific archiving object. Here, you can set whether the deletion program is to be executed automatically after an archive file is generated. Among other things, one variant each for the test run and the production run is created and the maximum size of an archive file is specified in this area. Basic logic is used in the programs for archiving Financial Accounting data. It should, for instance, only be possible to remove master data from the system if a deletion indicator has been set in the master record from the application side. In this way, it can be ascertained that a master record is no
Page 42 of 45
longer required by the department and is thus available for archiving or is scheduled for archiving according to the wishes of the department.
Deletion indicators can/must be set for customers/vendors not only in FI, but also in MM/SD. In the case of customers/vendors, there are also validations for: o - Customer = ?vendor o - Alternative payee You can specify the minimum runtime for accounts in days in Customizing. When documents are archived, a check is made whether this minimum runtime has been maintained. You should determine the minimum runtime of documents, depending on either the account type or the account, if all the accounts of an account type or if certain accounts are of interest. You can specify the minimum runtime in days depending on the document type in Customizing. When documents are archived, a check is made whether this minimum runtime has been maintained. If there is no entry or if a runtime value is empty, the system uses a minimum runtime of 9999 days. The data relevant for specifying the document runtime are the posting date (the clearing date in the case of open item-managed accounts) and the key date for the archiving procedure. The correspondingly longer definition of the runtime (document types / account types) determines how long the document resides in the system.
Lesson 3 Executing Archiving in Financial Accounting Using example

Generally, the documents are archived first (due to the checks executed during archiving). If these are removed from the system, the transaction figures are archived, followed by the master data. However, you can also archive only documents over the long term, for example. The specific archiving procedure is scheduled and processed as a background job. It selects the data objects from the database. The constraints that characterize a data object are considered here. Then every data object is checked whether it may be archived. If so, the data object is written to the
Page 43 of 45
archive file. If Customizing is set so the deletion program is to run automatically, the associated deletion procedure is started automatically when a file is closed. An archiving procedure is scheduled using transaction SARA by pressing the Write pushbutton. This is divided into 4 steps: o Create an archiving variant o Specify the execution user o Specify the start time o Define the spool parameters The data that are to be archived for the selected archiving object are specified in the archiving variants. As a rule, archiving variants can be reused only if the associated jobs are deleted. The definition of the variant must also include whether a test run or a productive run is involved. In FI, for example, you can archive master records, documents, and transaction figures. You can make the archived data available again using retrieval programs. During every archiving procedure, the system generates administration data with information about the archived/regenerated data. Various system administration tools are available to monitor archiving procedures: o Background processing tools Job logs Spool lists (if generated) o System monitoring tools Monitor for data archiving in the CCMS monitor sets The default log contains the number of archived data objects, the affected tables, the number of processed table entries and the file sizes. In application-specific logs, the archiving contents can be defined down to the document level. The document header must fulfill the following criteria before it can be archived: o The document type runtime must have been exceeded. o The document must have been in the system for longer than the minimum number of days (minimum duration). o Documents with a withholding tax remain in the system for at least 455 days. o Recurring, parked, or sample documents are not taken into account. The document position must fulfill the following criteria before it can be archived: o The document must no longer contain open items. The system takes into account only cleared items or those without open item management. o The account type runtime must have been exceeded. For the runtimes, a key date is used as a reference date; this can be specified for every program run. If no explicit key data is provided, it is set to the current execution date. The most important requirement for archiving user data is that this data belongs to completed transactions/periods and are thus no longer required for current business processes. However, it may happen that this data needs to be accessed even after archiving, such as in the case of a complaint, for evaluations or for internal or external revisions. The Archive Development Kit (ADK) stores the data in such a manner that read access is possible at any time. A requirement for this is the existence of suitable reading programs that are provided by the corresponding archiving object. They are used to read the archived data objects according to the selection criteria and to display them in a form suitable for the user. FI provides very user-friendly access to previously archived data. Users are asked whether they also want to view the archived data. If so, the display is as user-friendly as access to data located in the system. A transaction figure is the total number of postings on an account in debit or credit. In the SAP system, one transaction figure is usually maintained for credit and one for debit for each account. The financial statement of the company code is created according to these transaction figures.
Page 44 of 45
Transaction figures can be archived only if periods open for posting are no longer in the period to be archived. The periods for posting must be closed for the entire period to be archived. G/L accounts, customers, vendors, and bank data can be archived in Financial Accounting if the department agrees and the legal requirements have been fulfilled. If a master record is no longer required for postings by the department, a posting block is usually set as a first step. If this master record is not required for a long time, the deletion flag is set. The deletion flag shows a user who is processing the master record that this master record has been flagged for deletion. The deletion flag is one of the requirements that are checked by the system before master data are archived. This ensures that the department has no objections against archiving the master data. Therefore, it should be carefully checked which employees can receive the authorization for setting deletion flags when issuing these authorizations.
Page 45 of 45

Summ2 of TFIN52 Certification PDF

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Summ2 of TFIN52 Certification PDF

Uploaded by

Copyright:

Available Formats

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Unit 1 Organizational Structure

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Lesson 2 Cost Accounting Assignment

Lesson 3 Introduction to Assets Class

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Unit 2 Master Data

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Lesson 2 Assets Master Record

Lesson 3 Mass Change

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Unit 3 Assets Transactions

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Lesson 2 Assets Retirement

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Lesson 3 Intercompany & Intra-company Assets Transfer

Lesson 4 Assets under Construction

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Lesson 5 Unplanned Depreciation

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Unit 4 Periodic Processing and Valuation

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Lesson 2 Fiscal Year Change and Year End Closing in Assets

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Unit 5 Information System

Lesson 2 Value Simulation

Lesson 3 Assets History Sheet

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Lesson 2 Report Variant and Variables

Financial Accounting TFIN 52 Summary

Prepared by: Zeeshan R Haryani

Unit 7 List Viewer

Financial Accounting TFIN 52 Summary