Accrual Engine & Applications

Introduction for Consultants

Preface

This presentation was created by the developers of the Accrual Engine and is regularily updated. Last update: March 22nd 2006. The authors apologize for any typing errors and probably bad English.

© SAP AG 2002, Title of Presentation, Speaker Name 2

Content
 Introduction: Accruals  Overview: Accrual Engine Architecture
    

Customizing the Accrual Engine Customizing: Customer-Defined Accrual Methods Customizing: Account-Determination Debit and Credit Indicators Periodic Accrual Run Manual Accruals
 Example with Screen Shots  Excursus: Status of Accrual (Sub-)Objects  Reversal of Accrual Subobjects  Working with Derived Accrual Types  Customer-Defined Parameters  Customer-Defined Additional Account Assignments  Populating Additional Fields in Accounting (incl. Customer-Defined Fields)  Assignment Number and Automatic Clearing  Parallel Accounting  Validation  Customer-Defined Navigation  Archiving Accrual Engine Data

 Applications that Use the Accrual Engine

 

Provisions for Awards
 Example with Screen Shots

© SAP AG 2002, Title of Presentation, Speaker Name 3

Lease Accounting (Part of Leasing Solution - Separate Course)

Introduction: Accruals

000 1000 Period 1 800 Period 2 1200 Period 3 700 Period 4 1100 Period 5 500 Period 6 1400 Period 7 1100 Period 8 800 Period 9 1100 Period 10 1100 Period 11 1200 Period 12 © SAP AG 2002.What Are Accruals? Simple Example:  Given:  Task: Value + time interval Distribute value over time interval 12. Title of Presentation. Speaker Name 5 .

Title of Presentation.Simple Posting Example Accounting: Accruals = Periodic postings D P&L C 1 000 (2) 800 (3) 1 200 (4) D Accrual C 12 000 (1) (2) 1 000 (3) 800 (4) 1 200 © SAP AG 2002. Speaker Name 6 .

Title of Presentation. Any periodic postings based on an amount or value: Provisions for Awards © SAP AG 2002.Accrual Engine: Where Are Accruals Needed? Contract business transactions: Insurance. Speaker Name 7 . Contract-like business transactions: Bonds with fixed interests. magazine subscriptions etc. leasing etc.

Overview: Accrual Engine Architecture .

Title of Presentation. Speaker Name 9 .Accrual Engine: What it does Input: Contract-like information Accrual Engine Output: Periodic postings © SAP AG 2002.

Title of Presentation. t pu In SDP Leasing Input Accrual Engine Output: Periodic postings © SAP AG 2002.. Speaker Name 10 .Accrual Engine: A Generic Tool Provisions for Awards CRM (future) IBS Media (future) I p tun In pu t In pu t Manual Accruals I n p u t ..

history!) Output (posted accruals) Accrual Engine = ‘Accrual subledger’ Mass data processing. performance optimized © SAP AG 2002.Accrual Engine: Some Features New component in MySAP Financials Highly flexible tool Storage of all relevant data Input (contract-like information incl. Speaker Name 11 . Title of Presentation.

g.Accrual Engine: Benefits Automated periodic calculation of accruals No recurring entries with fixed values! Automated periodic posting (self correcting!) Simulation tools (e. future accruals) Supports multiple GAAPs Comprehensive reporting tools Integration with BW (Business Information Warehouse) © SAP AG 2002. Title of Presentation. Speaker Name 12 .

Accrual Engine: Architecture Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Speaker Name 13 . Title of Presentation.

Accrual Engine: Processes Calling Application Process B: Calculate Trigger Calculation of and AccrualsPost Accruals Accrual Method R R Accrual Engine Process A: Create/ Change Basis Transfer DataData to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Speaker Name 14 . Title of Presentation.

Title of Presentation. Speaker Name 15 .Accrual Engine: Accrual Methods Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002.

Title of Presentation.Accrual Engine: Delta Logic Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Speaker Name 16 .

Accrual Engine: Account Determination Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Speaker Name 17 . Title of Presentation.

Accrual Engine: Structure of Basis Data Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Title of Presentation. Speaker Name 18 .

....Accrual Type (costs. profit center.) and .Accrual Engine: Structure of Basis Data Accrual Object Does not carry any information. US GAAP. © SAP AG 2002.) defines an Accrual Item: The total value to be accrued.... Title of Presentation.Accounting Principle (IAS. . Speaker Name 19 . . Customer-defined fields like ‘Product Group’. . linear/daily) can be entered at this level... Start-date and end-date of time interval for accrual Cost center.. Each combination of . the total quantity to be accrued and the Accrual Method (linear/periodically. revenues. links accrual subobjects Accrual Subobject Accrual Subobject .. Header Assignment Accrual Subobject Parameters Accrual Item Accrual Item Accrual Item ... business area.

Speaker Name 20 .Accrual Engine: Posted Values Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Title of Presentation.

Speaker Name 21 .Accrual Engine: Reporting of Posted Values Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Title of Presentation.

Technical Details: Database Tables in the Accrual Engine .

Title of Presentation.Database Tables in the Accrual Engine Accrual Engine (general) Accrual Objects Cutomizing Tables aster endent M ) p Time-De asis Data’ Data (‘B an d cuments ine Do ual Eng Values Accr Total Basis Data Customizing Tables Posted Values Customizing Tables Calculation Posting © SAP AG 2002. Speaker Name 23 .

Database Tables in the Accrual Engine Field Name MANDT COMP BUKRS OBJID REF_KEY STATUS ACEOBJ ACEDSOH Field Name MANDT COMP BUKRS OBJID SUBID DATE_TO DATE_FROM VALITY_FROM VALITY_TO UNAME CPUDT CPUTM REF_SUBKEY STATUS Key X X X X X X ACEDSOP Field Name MANDT COMP BUKRS OBJID SUBID DATE_TO PARAM_NAME CONTENT DATE_FROM Key X X X X X X X ACEDSASSGMT C M O P B K S U R O JID B SU ID B D E_T AT O D E_FR M AT O BU S_AR EA D E_FR M AT O PR OFIT T _C R C ST EN ER O C T O D ID R ER WBS_ELEM T EN X X X X X Key X X X X ACEPSOH Field Name MANDT COMP BUKRS OBJID SUBID UNAME CPUDT CPUTM DEACTDATE REF_SUBKEY STATUS FIRSTYEAR LASTYEAR Key X X X X X ACEPSOIT ACEDSOI_ACCOUNTS Field Name MANDT COMP BUKRS OBJID SUBID ACRTYPE ACCRULE DATE_TO DATE_FROM INC_START_ACCNT INC_TARGET_ACCNT PER_START_ACCNT PER_TARGET_ACCNT FIN_START_ACCNT FIN_TARGET_ACCNT Key X X X X X X X X ACEDSOI Field Name MANDT COMP BUKRS OBJID SUBID ACRTYPE ACCRULE DATE_TO DATE_FROM AMOUNT CURRENCY QUANTITY UNIT ACRMETHOD TIMESTMP Key X X X X X X X X ACEPSOI Field Name MANDT COMP BUKRS GJAHR OBJID SUBID ACRTYPE ACCRULE CUMVALCAP CUMVALACCR VALCAP VALACCR VALRETIRE LASTEFFDATE CURRENCY Key X X X X X X X X Field Name MANDT COMP BUKRS GJAHR OBJID SUBID ACRTYPE ACCRULE DOCNR VALCUM VALTBP CURRENCY TRANSTYPE EFFDATE POPER RUNID AWTYP AWKEY AWSYS TIMESTMP Key X X X X X X X X X © SAP AG 2002. Speaker Name 24 . Title of Presentation.

Customizing the Accrual Engine .

Speaker Name 26 .Customizing: IMG for the Accrual Engine © SAP AG 2002. Title of Presentation.

Speaker Name 27 .Customizing: Dependent on the Component tart S F4 © SAP AG 2002. Title of Presentation.

Customizing: Important Activities  Assign company codes to the Accrual Engine  Define accounting principles and  Assign accounting principles to company codes  Define accrual types (costs.)  Define number ranges for accrual postings (4 different number ranges!)  Define account determination. separate chapter!  Additionally: IMG activities specific for the application component of the Accrual Engine.:  Manual Accruals:  Define accrual object types (Insurance. Renting etc.). Speaker Name 28 . revenues etc.)  Define number ranges for accrual objects  Provisions for Awards:  Define RFC destination for data transfer from HR system © SAP AG 2002. Title of Presentation.g. e.)  Define accrual methods (linear etc. separate chapter!  Define posting control (summarization etc.

Title of Presentation. Speaker Name 29 .Customizing: Important Activities © SAP AG 2002.

© SAP AG 2002.  They are both defined in the customizing of the accrual engine. The account determination usually depends on the accrual type. how the accruals have to be calculated.  accrual method The accrual method defines. Title of Presentation. degressively. Their meaning is the following:  accrual type The accrual type defines. costs or revenues. which kind of postings (opening. linearly. what is to be accrued. i.Customizing: Important Entities  The most important entities in the accrual engine are  acrual type and  accrual method. Speaker Name 30 . … The customer can program his own accrual methods.e. It also determines. i. periodic and/or final posting) are done.e.

Title of Presentation.Customizing: Settings of the Accrual Type Start © SAP AG 2002. Speaker Name 31 .

 Only Periodic No opening posting is done. c) If the accrual (sub)object is terminated before it has reached the end of ist life time. © SAP AG 2002. then the remaining value which has not yet been accrued. when the accrual (sub)object is created. b) Periodic postings (proess = ‚P‘) are done by the periodic accrual run. Only during the periodic accrual run. when the accrual (sub)object is created. is posted with a final posting (process = ‚F‘). e.g. This setting can be reasonable if the accrual values are needed for display only. Title of Presentation.  None No accrual postings are done at all.Customizing: Settings of the Accrual Type  Most important setting that is done in the accrual type is the setting for the accrual postings. Speaker Name 32 .  Opening posting only Only an opening posting is done (process = ‚I‘). periodic postings with process = ‚P‘ are done. as explanation for other accrual types which are determined by a complicate algorithm. No periodic postings are done during the periodic accrual run. The following settings are possible:  ALL This means that the following three postings are done: a) An opening posting (process = ‚I‘).

2) (P. Title of Presentation.Customizing: Example for ‘All Postings’ D Clearing Account C D Accrued Revenues 18 000 (I) C (I) 18 000 (P.1) (P. Speaker Name 33 .18) 300 300 300 (F) 12 600 12 600 (F) © SAP AG 2002.18) D Revenues 300 300 … 300 C (P.2) … (P.1) (P.

Speaker Name 34 . Title of Presentation.2) … (P.2) (P.x) © SAP AG 2002.1) (P.x) (P.1) (P.Customizing: Example for ‘Periodic postings only’ D Expected Expenditure C 300 300 300 D Provisions 300 300 … 300 C (P.

Customizing: Link from Messages to IMG ng Lo © SAP AG 2002. Title of Presentation. Speaker Name 35 xt te .

Customizing: Customer-Defined Accrual Methods .

periodically daily with 365 days daily with 360 days  Accrual methods are ordinary function modules  Customer can define (develop) his own accrual methods by programming corresponding function modules with the ABAP workbench. © SAP AG 2002. Speaker Name 37 . Linear. Title of Presentation. ... Linear.Customizing: Customer-Defined Accrual Methods  SAP delivers a number of accrual methods: Linear.

Title of Presentation.Customizing: Customer-Defined Accrual Methods © SAP AG 2002. Speaker Name 38 .

Title of Presentation. Speaker Name 39 .Customizing: Customer-Defined Accrual Methods © SAP AG 2002.

Customizing: Developing Accrual Methods (1) © SAP AG 2002. Speaker Name 40 . Title of Presentation.

only the above mentioned three fields have to be filled. Speaker Name 41 . Title of Presentation.Customizing: Developing Accrual Methods (2)  Most important is the internal table CT_PERIOD_VALUE. Important: No records may be deleted or inserted into this table CT_PERIOD_VALUE. The entries in this table have to be modified (filled) by the accrual method:  The accrual method has to populate the following three fields in the internal table CT_PERIOD_VALUE:  VALACT This field has to be filled with the value that has to be accrued between the dates DATE_FROM and DATE_TO VALCUM This field has to be filled with the value that has to be accrued during the time before DATE_FROM VALREMAIN This field has to be filled with the value that remains to be accrued after DATE_TO. Other fields may not be modified!    © SAP AG 2002.

Customizing: Developing Accrual Methods (3)  In the interface of the function module contains also additional parameters which contain information for which accrual object the accrual method is currently called. Their meaning are the following: 1. since all relevant information is passed from the accrual engine to the accrual method by the other parameters like IT_GENERAL_PARAMS etc. Note: Usually you will not need to use this parameter to read data from the accrual engine database tables.  These parameters may not be changed by the accrual method. Speaker Name 42 . © SAP AG 2002. Import structure IS_ACE_KEY This structure contains the unique key of the accrual item in the database tables of the accrual engine. Title of Presentation.

the interval in time. The table contains the time dependent header and item data of the accrual subobject. i.Customizing: Developing Accrual Methods (4) 2. Needed only. FY_VARIANT Fiscal year variant. Import table IT_GENERAL_PARAMS This table is importing only: The records contained in this table may not be changed.e. VALITY_FROM and VALITY_TO Life time of the accrual subobject.e. in which the accruals have to be done.    © SAP AG 2002. Title of Presentation. Speaker Name 43 . i. the following fields:  AMOUNT (and CURRENCY) The total value which is to be accrued. QUANTITY (and UNIT) The total quantity which is to be accrued. if the periods need to be determined from the dates.

Import table IT_PARAMS This table is importing only: The records contained in this table may not be changed.Customizing: Developing Accrual Methods (5) 3. Speaker Name 44 . The table contains entries with the customer-defined parameters of the accrual subobject. See separate chapter ‘Customer-Defined Parameters’. The parameters can be used to determine the accrual values. Title of Presentation.  PARAM_NAME Name of the parameter. CONTENT The value of this parameter  © SAP AG 2002.

this table would contain a table with the entered data for these additional fields:  FIELDNAME Name of the additional input field. This possibility is not available in standard. Usually this table is empty and not used. Note: The additional fields have to be added to the selection screen using select-option-statements. Speaker Name 45 . Contact the SAP development for further information. Title of Presentation. It is intended to be used for simulation of periodic accruals: If the simulation is done with certain assumptions (technically: Additional input fields on the entry screen of the periodic accrual report). FIELDRANGE Table with the entered select-options. if needed.Customizing: Developing Accrual Methods (6) 4. Import table IT_COMP_SIMUPARAM_RANGES This table is importing only: The records contained in this table may not be changed.   © SAP AG 2002.

Customizing: Developing Accrual Methods (7) 4.) ID Message class of the message. MESSAGE_V4 Parameters for the message. NUMBER Number of the message in the message class. MESSAGE_V1. they can be put into this table. Export table ET_RETURN If messages appear in the accrual method. if a message appeares:  TYPE Type of the message (‘E’ for Error.    © SAP AG 2002. if required by the message. …. Title of Presentation. Only the following fields have to be filled. ‘W’ for warning etc. Speaker Name 46 .

e. the CT_PERIOD_VALUE table contains several entries: One entry for each period. i.  The accrual method is called during the data extraction to BW (data warehouse). In this case. Speaker Name 47 .g. DATE_FROM <= DATE_TO in each entry. The CT_PERIOD_VALUE table can contain different entries. In this entry DATE_FROM = DATE_TO = key date of the accrual run!  The accrual method is called from the display transaction for accrual objects (e. More detailed:  The accrual method is called during the periodic accrual posting run. In this case. the accrual method is called for the key date that was entered on the entry screen: The CT_PERIOD_VALUE table contains exactly one single entry.   The accrual method has to populate correctly the CT_PERIOD_VALUE table in all of these cases! All three cases should be tested thoroughly! © SAP AG 2002. Title of Presentation.Customizing: Developing Accrual Methods (8)  When developing accrual methods it is very important to note that the accrual method can called from several programs. CT_PERIOD_VALUE usually contains one entry in which DATE_FOM <= DATE_TO. In this case. the ACACTREE02 transaction).

© SAP AG 2002. ACACRTEE02 transaction): The accrual method is called and CT_PERIOD_VALUE contains several entries for the complete life time of the accrual subobject.g. Speaker Name 48 .Customizing: Developing Accrual Methods (9)  Display of the accrual object (e. Title of Presentation.

2000 31.01. Speaker Name 49 .2000 01.2000 31.2000 01.2000 01.2000 29.05.2000 01.2000 … A c r a u l M e h t o d  DATE_FROM  DATE_TO 31.03.01.03.02.01.04.01.2000 31.2000 30.2000 01. Title of Presentation.05.2000 01.2000 29.03.04.04. Example (correct): Accrual Method filles the value fields VALACT.2000 VALACT 150 150 150 150 150 VALCUM 0 150 300 450 600 VALREMAIN 8850 8700 8550 8400 8250 01.02.2000 30.2000 01.2000 … © SAP AG 2002.02.  DATE_FROM  DATE_TO 31.05.2000 VALACT 0 0 0 0 0 VALCUM 0 0 0 0 0 VALREMAIN 0 0 0 0 0 01.2000 31.Customizing: Developing Accrual Methods (10) 1.05.03.02. VALCUM and VALREMAIN in the CT_PERIOD_VALUE table.2000 01.04.

2000 30.02.01.2000 30.2000 … © SAP AG 2002.04. Speaker Name 50 .2000 29.2000 01.2000 29.04. Example (incorrect): Accrual Method filles the value fields VALACT.2000 01. but makes a mistake by popuplating the field VALCUM incorrectly:  DATE_FROM  DATE_TO 31.2000 01. DATE_FROM  DATE_TO 31.05.05.2000 31.2000 31.2000 01.04.02.01.05.Customizing: Developing Accrual Methods (11) 2.01.2000 01.03.2000 VALACT 150 150 150 150 150 VALCUM 0 100 300 450 600 VALREMAIN 8850 8750 8550 8400 8250 01.2000 01.03.2000 31. VALCUM and VALREMAIN in the CT_PERIOD_VALUE table. but should be 150.03. Title of Presentation. the cumulated value (VALCUM) is 100.02.2000 01.01.2000 31.2000 VALACT 0 0 0 0 0 VALCUM 0 0 0 0 0 VALREMAIN 0 0 0 0 0 01.02.05.03.2000 01.2000 … A c r a u l M e h t o d  In period 2/2000.04.

2000 01.05.04.04.02.03. continued): After the accrual method was called.05.02.01.05. The correction value is stored in the field VALCORR.03. VALACT and VALCUM are corrected.2000 31.2000 01.01.2000 31.2000 01. Title of Presentation.04.03.2000 29.01.05.2000 01.2000 29.2000 01. Example (incorrect.2000 … .2000 01.2000 31.2000 VALACT 150 150 150 150 150 VALCUM 0 100 300 450 600 VALREMAIN 8850 8750 8550 8400 8250 01.02.2000 31.01.2000 01.2000 01.2000 30. the system automatically corrects the wrong cumulated value in period 2/2000 by adjusting VALACT and VALCUM):  DATE_FROM  DATE_TO 31.03.2000 … A t u o m a c i r e n In period 2/2000.02. © SAP AG 2002.04.2000 30.2000 01.Customizing: Developing Accrual Methods (12) 2. Speaker Name 51  f a e t r DATE_FROM  A c r u l a M t e h d o VALACT 150 100 200 150 150 VALCUM 0 150 250 450 600 VALREMAIN VALCORR 8850 8750 8550 8400 8250 0 -50 50 0 0 DATE_TO 31.

Customizing: Developing Accrual Methods (13)  Periodic accrual run (e. © SAP AG 2002.g. ACACACT transaction): The accrual method is called and CT_PERIOD_VALUE contains exactly one entry in which DATE_FROM = DATE_TO = key date from the entry screen of the periodic accrual run. Speaker Name 52 . Title of Presentation.

This slide now shows. In case that accruals have already been posted by the periodic accrual runs at former key dates. The other field CT_PERIOD_VALUE-VALREMAIN is not important. the system would post the delta. so that after the current accrual run. how accruals are calculated by the accrual method. how the system calculates the value which is to be posted in an periodic accrual run: In the periodic accrual run. since it is not used for postings.       © SAP AG 2002. But it might be interesting for reporting purposes. the system would sum up the two values CT_PERIOD_VALUE-VALACT (Value of the current period) and CT_PERIOD_VALUE-VALCUM (Value from former periods): This sum is assumed to be the value which should be the cummulative accrual value at the key date of the periodic accrual run. Title of Presentation. the above sum is the cummulative accrual value (balance).Customizing: Developing Accrual Methods (14)  The slides before showed. Speaker Name 53 .

Customizing: Account Determination .

 When the Accrual Engine documents are transferred to Accounting (which is usually done automatically when they are posted). Accrual Engine documents are created in the Accrual Engine. Speaker Name 55 . Title of Presentation. an Accounting document with two line items is created from the Accrual Engine document.Customizing: Account Determination  When posting Accruals. the Accrual Engine account determination is executed to get the following information:  Start account account type  Target  Document © SAP AG 2002. These documents consist of only one line item without GL accounts and without CO assignments like cost center etc.  At this point in time.

the ‘Process in the Accrual Engine’ and ‘Accrual Type’ determine the start and target account customizing entries in these self-defined customizing tables!  Create © SAP AG 2002. Speaker Name 56 . Title of Presentation. which dimensions determine the accounts and document type! E.Customizing: Account Determination  The customizing of the account determination is done in two steps:  Define the customizing tables for the account determination The customer can define himself.g.

Speaker Name 57 . depending on the setting of the accrual type). depending on the setting of the accrual type). when the accrual (sub)object is created. The opening posting usually posts the total value which is to be accrued to an accrual account. the account determination will usually depend on these two criterias (see next slide). F: Final posting (This posting is optional.  As a consequence. This posting is done.g. Title of Presentation. It usually posts from the accrual account to a P&L account.Customizing: Example for Account Determination  The accounts which are used in an accrual posting depend mainly on the following criteria:  Process in the accrual engine I: Opening posting (This posting is optional. It is only executed if a) an opening posting was done and b) the accrual (sub)object is terminated before it has reached the end of ist life time. it is clear that the accounts usually depend on the accrual type. costs or revenues). P: Periodic accrual posting The periodic posting is done by the periodic accrual run.  Accrual type Since the accrual type determines the kind of accruals (e. © SAP AG 2002.

Title of Presentation.Customizing: Account Determination © SAP AG 2002. Speaker Name 58 .

Customizing: Account Determination © SAP AG 2002. Title of Presentation. Speaker Name 59 .

 In a second step of the account derivation. Speaker Name 60 .  Both of these account determinations use the same derivation tool!  Only difference: The extended account determination offers more features than the simple account determination.Customizing: Extended Account Determination  In addition to the ordinary account determination. derive the account from account symbol and chart of accounts!  This two-step logic can be done in the extended account determination. all companies. but derive only account symbols. there exists also a socalled ‘extended account determination’. the same logic is to be used to derive the accrual accounts.  Problem:  Solution: The accounts depend on the chart of accounts. © SAP AG 2002. Title of Presentation.  Basis idea of the extended account determination is explained in the following example:  Accruals  In have to be done in a lot of company codes.  Do not derive the accounts directly. but the chart of account is different in each company code.

Debit and Credit Indicators .

The account determination yields the necessary two accounts: Start and target account: Accounting document 100 EUR to target account  Accounting Accrual Engine document: 100 EUR . During this transfer from each Accrual Engine document two line items are created in the Accounting document. Speaker Name 62 .Debit and Credit Indicators in Accrual Postings  Postings which are done by the Accrual Engine create two kind of documents:  Accrual Engine documents Accrual Engine documents are stored in the Accrual Engine and each document consists of one line item only: This line item contains the information which value was accrued for which accrual object in which period. Title of Presentation.100 EUR to start account © SAP AG 2002. Documents The Accrual Engine document is automatically transferred to Accounting.

100 EUR to start account Accounting document Debit: 100 EUR to target account Credit: 100 EUR to start account © SAP AG 2002. Accounting document 100 EUR to target account Accrual Engine document: 100 EUR . Speaker Name 63 .Debit and Credit Indicators in Accrual Postings  The debit and credit indicators are determined from the sign of the Accounting line item:  If  If the value is > 0. then the credit indicator is set. Title of Presentation. then the debit indicator is set. the value is < 0.

Periodic Accrual Run .

 The periodic accrual run is started for a key date. Title of Presentation. Speaker Name 65 . Note: Not all key dates are allowed.Periodic Accrual Run  The periodic accrual postings are done by starting a periodic job. Only those key dates can be entered. which are defined by the settings of the accrual type. © SAP AG 2002. see next slide. the periodic accrual run.

Periodic Accrual Run: Customizing  The allowed dates which can be used as key date in the periodic accrual run are determined by the ‘frequency’ which is entered in the posting control of the accrual type. 01/31/2000. 02/29/2000.g. © SAP AG 2002. Possible dates are then e. Title of Presentation. Example: If the frequency is ‘Per posting period’. … But not dates like 01/01/2000 or 02/15/2000. then only the last day of a period is allowed as key date. Speaker Name 66 .

are possible. after the run on 01/31/2000. days 01/31/2000.  Example: If the frequency is ‘Per posting period’. the next run is assumed to be at 02/29/2000. 02/29/2000 etc. because  additional  the accrual objects were created after the first run was already executed or first run was executed not for all relevant accrual objects due to entered select options. After the periodic accrual run was executed for 01/31/2000.  If the run 01/31/2000 has to be repeated.  If one or several runs have to be skipped. but on 03/31/2000. © SAP AG 2002. the periodic accrual run has to be executed for all dates which are defined by the ‘frequency’ in a rising order. then the than the execution type has to be set to ‘Unplanned’.Periodic Accrual Run: Execution Type  Usually. Speaker Name 67 . the next run will be not on 02/29/2000.g. e.g. than the execution type has to be set to ‘Repeat’ instead of ‘Normal’. e. Title of Presentation.

Periodic Accrual Run: Log  The already executed periodic accrual runs are logged on company code level.  You can display the log in the entry screen of the periodic accrual run by ‘Environment -> Log of Periodic Accrual Runs’: © SAP AG 2002. Speaker Name 68 . Title of Presentation.

1!  Background for this restricted possibility to enter ‘past’ key dates: If there were already periodic accrual runs in future fiscal years. Speaker Name 69 . this is forbidden by the system: An Error message (ACEPS 054) is sent.  Solution: Enter the key date 01/31/2000 and(!) set the execution type to ‘Repeat’. The system will send error message ACEPS 055.  By default.0 / 1.Periodic Accrual Run: Key Dates in the Past  It might be necessary that an accrual run is executed with key date 01/31/2000 despite there was already an run on 02/29/2000. the values which were posted in these future years are then wrong. but this message can be switched off with the OBA5 transaction. Consequence: Accrual runs in future years have to be repeated. Support Package SAPKGPAA12 is required as prerequisite in release extensions 1. © SAP AG 2002. Title of Presentation. if key date 01/31/2000 is entered on the entry screen of the periodic accrual run.

Speaker Name 70 . Title of Presentation.  You can display this log in the entry screen of the periodic accrual run by ‘Environment -> Display Application Log’: © SAP AG 2002.Periodic Accrual Run: Message Log  Messages which occur in a periodic accrual run are looged in the socalled application log.

Applications that Use the Accrual Engine

Applications that Use the Accrual Engine

 Manual Accruals  Provisions for Awards  Lease Accounting

© SAP AG 2002, Title of Presentation, Speaker Name 72

Manual Accruals

Manual Accruals: Overview
 Purpose: Post accruals for contract-like data  Create ‘contract data’ (accrual objects) manually in the Accrual Engine  Start periodic accrual posting runs

© SAP AG 2002, Title of Presentation, Speaker Name 74

Title of Presentation. Speaker Name 75 .Manual Accruals Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Create Accrual Objects Manually Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002.

Speaker Name 76 .Manual Accruals: Interface for Creating Accrual Objects  In the application component ‘Manual Accruals’. Title of Presentation. The report would work in the following way:  Select contract-like data which is to be accrued. but SAP also delivers an interface for creating accrual objects. The data can be selected from any source!  Transform the selected data into the format that is needed by the interface.  Easier way: SAP delivers a sample report which can be  used for transferring vendor invoices into the Accrual Engine and it can be  reused for transferring data from any source to the Accrual Engine (see next slides) © SAP AG 2002.  The interface is the function module ACAC_OBJECT_MODIFY_EXT  There are two ways to use this interface:  Customer can develop a report to create accrual objects using this interface. accrual objects are created manually.  Save the transformed data as accrual objects in the Accrual Engine.

Title of Presentation. Speaker Name 77 .Manual Accruals: Automatic Datafeed (1)  The sample report SAP delivers is ACAC_DATA_TRANSFER_EXAMPLE  This report selects vendor invoices and creates the line items of the corresponding FI document in the Accrual Engine as accrual objects  There is also a detailed program documentation (red circle) which describes the meaning of the parameters © SAP AG 2002.

parameters Most important is the selection method which is described in the next slides. when the accrual object is created. according to the customizing of the accrual types. parameters Needed only. if an opening posting is done by the Accrual Engine.Manual Accruals: Automatic Datafeed (2)  The selection screen of the sample data transfer report consists of the following subscreens:  General selections These parameters are specific for the vendor invoices: They are used for selecting the vendor invoices. Speaker Name 78 . the accruals are calcuated linearly periodically). Example: If you enter the accrual method ‘LINEAR’. Parameters These Parameters are used for creating the accrual objects. Title of Presentation.  Accrual  Posting  Control © SAP AG 2002.

Manual Accruals: Automatic Datafeed (3)  Basic idea of the sample report is that all kinds of data transfers into the Accrual Engine work in a similar way:  First  The  The A the data have to be selected data have to be transformed into the format of the Accrual Engine data have to be saved in the Accrual Engine results list has to be created  In addition. Speaker Name 79 . each data transfer report must contain a lot of ‘administration overhead’:  Checking  Checking and setting locks the user input the Schedule Manager errors bevor saving(!) and error handling  Connecting  Checking  Creating  Testrun an output list feature and possibility of deleting data from the Accrual Engine  The sample report has all of these features and can even do more:  The sample report can be reused for selecting data from any source (see next slides)! © SAP AG 2002. Title of Presentation.

Title of Presentation. Speaker Name 80 . This customizing can be found in the sample report in the menue: ‘Environment -> Settings -> Selection Methods for Data Transfer’ © SAP AG 2002.Manual Accruals: Automatic Datafeed (4)  Selection Methods in the sample report enable the customer to use the sample report to select data from any source and transform the selected data into the format that is required by the Accrual Engine  The selection methods can be defined in the customizing.

Speaker Name 81 .Manual Accruals: Automatic Datafeed (5) Definition of selection methods: © SAP AG 2002. Title of Presentation.

 Please study also the F1 help for the field ‘selection method’ on the entry screen of the sample report ACAC_DATA_TRANSFER_EXAMPLE and study also the program documentation of this report. © SAP AG 2002.  SAP deliveres sample selection methods for the transfer of vendor invoices into the Accrual Engine. Speaker Name 82 .  In the source code. there’s a documentation of the function modules that are used in the sample selection methods (Function modules ACAC_DATA_TRANSFER_EXAMPLE_1 and ACAC_DATA_TRANSFER_EXAMPLE_2).  A DDIC-Structure which contains the fields which are to be displayed by the sample report as results list. This function module must also transform the data into the format that is required by the Accrual Engine.Manual Accruals: Automatic Datafeed (6)  Selection methods consist of two parts: A function module for selecting the data which shall be transferred into the Accrual Engine. Title of Presentation.

 Some includes for the program logic (e. includes ACAC_GENERIC_DATA_TRANSF_M10 and ACAC_GENERIC_DATA_TRANSF_F10). that the selection-screen of the sample report is not suitable for all selection methods: The selection screen of the sample report ACAC_DATA_TRANSFER_EXAMPLE was made for selecting vendor invoices.  Of course. the required select-options and parameters of the data transfer report depend on the source from which the data are selected.g. © SAP AG 2002.g. Title of Presentation. From this it is clear.g. SAP separated the selection screen from the program logic in the following way:  The sample report consists only of a few includes:  One include for each subscreen on the selection screen E. include ACAC_DATA_TRNSF_SELOPT_EXAMPLE. ACAC_DATA_TRANSFER_EXAMPLE_1) which data to select.Manual Accruals: Automatic Datafeed (7)  A problem for the selection methods are the select-options: The sample report must ‘tell’ the function module (e. Speaker Name 83 .  But since all the program logic of the data transfer program is identical for all data sources.

  © SAP AG 2002. the includes can be replaced by customerdefined includes. Only the main program has to be copied. Speaker Name 84 . First.Manual Accruals: Automatic Datafeed (8)  The includes marked with red lines can be replaced by customer-defined includes which contain the selectoptions that are required. not the includes! Aferwards. the report ACAC_DATA_TRANSFER_EX AMPLE has to be copied into the customer name space to avoid modifications. Title of Presentation.

Title of Presentation. © SAP AG 2002.  This works in the following way: The sample report scans the selection screen and puts all selectoptions into this table which have the addition ‘MODIF ID SEL’.  A similar logic is used for the accrual parameters: All select-options which have the addition ‘MODIF ID ACP’ are put into the table IT_ACCRUAL_PARAMS and passed to the function module of the selection method. the select options are contained in an internal table (parameter IT_GENERIC_SELOPT).Manual Accruals: Automatic Datafeed (9)  How the select-options are transferred from the selection screen to the function module that is used by the selection method:  Since the interface of the function modules (used by selection methods) are generic. This table is then passed to the function module of the selection method. Speaker Name 85 .

© SAP AG 2002. Title of Presentation.Manual Accruals: Automatic Datafeed (10) The addition ‘MODIF ID SEL’ is important in the include with the select-options for the data selection. Speaker Name 86 .

Speaker Name 87 .Manual Accruals: Automatic Datafeed (11)  Example:  Results list from transferring vendor invoices to the Accrual Engine  Double click on a line in the list of results displays the accrual engine object with the accrual data © SAP AG 2002. Title of Presentation.

Manual Accruals: Automatic Datafeed (12)  Deleting of data in the Accrual Engine n ode O pert M Ex © SAP AG 2002. Speaker Name 88 . Title of Presentation.

. Revenues.. Each combination of . linear/daily) can be entered at this level. © SAP AG 2002...Manual Accruals: Basis Data Structure Accrual Object Defined by the Accrual Object Type / Accrual Object Number combination Header 1:1 Start-date and end-date of time interval for accrual Cost center.. business area.Accrual Type (Costs.) defines an accrual item.. . profit center. Assignment Accrual Subobject Parameters Accrual Item Accrual Item Accrual Item . The total value to be accrued. US GAAP.. Title of Presentation..) and . . the total quantity to be accrued and the Accrual Method (linear/periodically...Accounting Principle (IAS.. Customer-defined fields like ‘product group’. Speaker Name 89 . .

Title of Presentation.Manual Accruals: Application Menu © SAP AG 2002. Speaker Name 90 .

Speaker Name 91 .Manual Accruals: Application Menu © SAP AG 2002. Title of Presentation.

Manual Accruals: Customizing © SAP AG 2002. Speaker Name 92 . Title of Presentation.

Manual Accruals: Examples .

600 EUR = 18. 2000 until 31 Dec.000 EUR / (5 x 12) © SAP AG 2002.000 EUR bonus Costs and revenues must be accrued over 5 years  Monthly revenues: 300 EUR = 18.Manual Accruals: Sample ‘Insurance Contract’  Contract data: Valid from 01 Jan. 2004 (5 years) Annual premium (to be paid by customer): 3.600 EUR  Revenues: Customer pays  Costs: Salesman gets 5 x 3.000 EUR 6.000 EUR / (5 x 12)  Monthly costs: 100 EUR = 6. Title of Presentation. Speaker Name 94 .

Title of Presentation. Speaker Name 95 .Manual Accruals: Create Accrual Object © SAP AG 2002.

Speaker Name 96 . Title of Presentation.Manual Accruals: Accrual Object and Subobject © SAP AG 2002.

Title of Presentation.Technical Background: Accrual Object and Subobject © SAP AG 2002. Speaker Name 97 .

Title of Presentation.Manual Accruals: Architecture Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Speaker Name 98 .

Title of Presentation.Manual Accruals: Architecture Calling Application Trigger Calculation of Accruals Accrual Method R R Accrual Engine Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Reporting Reporting © SAP AG 2002. Speaker Name 99 .

Title of Presentation. Speaker Name 100 .Manual Accruals: Create Accrual Object © SAP AG 2002.

Manual Accruals: Opening Postings © SAP AG 2002. Speaker Name 101 . Title of Presentation.

Speaker Name 102 .Manual Accruals: Navigation Place cursor in ‘COSTS’ line and double-click or press ‘Transfer Accrual Item’ button © SAP AG 2002. Title of Presentation.

Title of Presentation.Manual Accruals: Opening Postings © SAP AG 2002. Speaker Name 103 .

Speaker Name 104 .Manual Accruals: Documents in FI © SAP AG 2002. Title of Presentation.

Manual Accruals: Opening Postings D Receivables C D Accrued Revenues C (I.000 C 6. Speaker Name 105 .1) D Payables C D Accrued Costs (I.000 (I.000 (I.1) 18.2) 6.000 18.2) © SAP AG 2002. Title of Presentation.

Manual Accruals: Start Periodic Accrual Run © SAP AG 2002. Speaker Name 106 . Title of Presentation.

Speaker Name 107 . Title of Presentation.Manual Accruals: Result of Periodic Accrual Run © SAP AG 2002.

Manual Accruals: Display Accrual Object after Periodic Accrual Run

© SAP AG 2002, Title of Presentation, Speaker Name 108

Manual Accruals: Documents in FI

D

Receivables

C

(I.1) 18,000

D

Revenues

C

D

Accrued Revenues

C

18,000 (I.1) 300 (P.1) (P.1) 300

© SAP AG 2002, Title of Presentation, Speaker Name 109

Manual Accruals: Posting Deltas
 In each period, the following accruals are calculated:
 Revenues  Costs

(Accrual Type RVNUES):

300 EUR 100 EUR

(Accrual Type COSTS):

 In the first period (1/2000) these values were posted correctly.  Now let us assume that the customer forgets to carry out the accrual run in 2/2000.  The next accrual run is carried out in 3/2000.  The Accrual Engine then calculates that in 3/2000 the accrued values should be:
 Calculated  Calculated

Revenues: Costs:

3 x 300 EUR = 900 EUR 3 x 100 EUR = 300 EUR

 In 3/2000, the Accrual Engine then posts the difference between the calculated values and the values already posted:
 Posted  Posted

Revenues: Costs:

3 x 300 EUR - 300 EUR = 600 EUR 3 x 200 EUR - 100 EUR = 200 EUR

 This is displayed in the next slide
© SAP AG 2002, Title of Presentation, Speaker Name 110

Manual Accruals: Posting Deltas

© SAP AG 2002, Title of Presentation, Speaker Name 111

Manual Accruals: Changing the Accrual Object  Let us make the example more complex: Change to total costs which are to be accrued:  On 31 March 2000.000 EUR  When changing the total costs to be accrued from 6.000 EUR to 9.000 EUR is posted. the Accrual Engine posts the delta of 600 . Speaker Name 112 .300 = 300 EUR automatically. the following costs had already been accrued: 3 x 100 EUR = 300 EUR  On 15 Feb. Accrual Engine calculates the following costs: 4 x 150 EUR = 600 EUR  On 30 April 2000. © SAP AG 2002.000 EUR / (5 x 12) = 150 EUR  In the next periodic accrual run on 30 April 2000. Periodic costs are now calculated to be 9. 2000.000 EUR is reversed and a new opening posting of 9.000 EUR to 9. Title of Presentation. the opening posting of 6. the premium for the salesman is raised from 6.000 EUR.

Manual Accruals: Changing the Accrual Object © SAP AG 2002. Speaker Name 113 . Title of Presentation.

Title of Presentation.3) © SAP AG 2002.6 000 (I.2) . Speaker Name 114 .6 000 (I.1) C D Accrued Costs C (I.1) 6 000 (I.3) 9 000 .2) 9 000 (I.Manual Accruals: Changing the Accrual Object D Costs 6 000 (I.

Manual Accruals: Changing the Accrual Object © SAP AG 2002. Speaker Name 115 . Title of Presentation.

Title of Presentation. Speaker Name 116 .Manual Accruals: Display History of Accrual Object © SAP AG 2002.

Speaker Name 117 .Manual Accruals: Changing the Accrual Object © SAP AG 2002. Title of Presentation.

Speaker Name 118 . Title of Presentation.Manual Accruals: Changing the Accrual Object © SAP AG 2002.

Manual Accruals: Changing the Accrual Object © SAP AG 2002. Speaker Name 119 . Title of Presentation.

3) 300 100 (P.3) © SAP AG 2002.2) 200 (P.000 (I.1-3) 9.Manual Accruals: Changing the Accrual Object D Payables C 9. Title of Presentation.1) 200 (P.2) 300 (P.1) 100 (P. Speaker Name 120 .000 (P.1-3) D Costs C D Accrued Costs C (I.

while the previous year might also still be open for closing entries  Creating an accrual object: A total record is created for each year that is open.Manual Accruals: Totals  The Accrual Engine stores Accrual Engine documents and totals.  One total record exists for each year. Title of Presentation. only the current year is open. Speaker Name 121 . Usually. © SAP AG 2002.  Accrual Engine Customizing: Only 2 years can be open for periodic accrual postings.

Speaker Name 122 .Manual Accruals: Totals Opening posting in year 2000 Automatic carryforward to year 2001 © SAP AG 2002. Title of Presentation.

Speaker Name 123 . Of course.  This carryforward does not lead to postings in Accounting  The carryforward also increases the ‘current year’ in Accrual Engine Customizing. since a total record already exists for 2001.  In the example: The carryforward program does not have to be started at the end of fiscal year 2000. However. © SAP AG 2002. it is advisable to execute the carry forward at the end of each fiscal year. Title of Presentation. it does have to be started at the end of 2001. a fiscal year change program (carryforward) must be started in the Accrual Engine.Manual Accruals: Carryforward  At the end of the year.  This program creates total records for the new fiscal year for all accrual objects for which a corresponding record does not yet exist.

the accrual subobject is deactivated on 06/30/2001. The rest: 9.  When © SAP AG 2002. the remaining revenues of 18. Accordingly. They have two options:  Do nothing with the remaining values after deactivation.  The total costs to be accrued were 9. To stop accrual postings in 6/2001.600 EUR may not be accrued any more. Simply stop posting periodic accruals.  In Customizing for the accrual types (COSTS and RVNUES).Manual Accruals: Deactivating an Accrual Subobject  Let us assume that a customer quits an insurance contract before it ends.000 EUR .2. deactivating the accrual subobject. but customer quits in 6/2001.000 EUR. customers can determine what happens with the remaining values. Speaker Name 124 .300 EUR may not be accrued any more.300 EUR x (12 + 6) = 12.000 EUR . Title of Presentation.700 EUR had been accrued. 150 EUR x (12 + 6) = 2. perform a closing posting and post the remaining costs and revenues to a different account.700 EUR = 6. The contract was supposed to run from 1/2000 until 12/2004. At the end of 6/2001.

Speaker Name 125 . Title of Presentation.Manual Accruals: Deactivating an Accrual Subobject © SAP AG 2002.

Speaker Name 126 .Manual Accruals: Deactivating an Accrual Subobject © SAP AG 2002. Title of Presentation.

Speaker Name 127 . Title of Presentation.Manual Accruals: Deactivating an Accrual Subobject © SAP AG 2002.

Speaker Name 128 . Title of Presentation.Manual Accruals: Deactivating an Accrual Subobject © SAP AG 2002.

Speaker Name 129 .Manual Accruals: Deactivating an Accrual Subobject © SAP AG 2002. Title of Presentation.

Speaker Name 130 .Manual Accruals: Deactivating an Accrual Subobject Final posting at deactivation © SAP AG 2002. Title of Presentation.

Excursus: Status of Accrual Objects .

Speaker Name 132 .Status of Accrual Objects and Subobjects  The processing status can be set on two levels in the Accrual Engine:  on  on level of accrual object and level of accrual subobject. Te © SAP AG 2002. ch Data Disp. Title of Presentation.

Speaker Name 133 .  Please refer to the documentation in the customizing and to the F1 help for further information.  The status ‘To Be Archived’ can be set by the transaction ‘Prepare Archiving Session’: The archiving session will archive only those accrual objects which have the status ‘To Be Archived’ (see chapter ‘Archiving Accrual Engine Data’).Status of Accrual Objects  The status of an accrual object can have the following values:  ‘In Process’ Be Archived’. Title of Presentation.  ‘To  The status of the accrual object usually is ‘In Process’. © SAP AG 2002.

 The history of changes of the status of the accrual object is recorded in the basis data of the accrual engine.  The status ‘Stopped‘ means that no accrual postings are done as long as this status is active.  Please refer to the F1 help of the status for further information.Status of Accrual Subobjects  The status of an accrual object can have the following values:  ‘In Process’  ‘Completed’  ‘Stopped’  The status of the accrual object usually is ‘In Process’. Setting this status is -up to now. Speaker Name 134 .  The status ‘Completed’ is set when the user executes the function ‘Deactivate Accrual Subobject’ (see chapter before). Exception: Setting the status ‘Stopped’ is not recorded in the basis data. Title of Presentation. © SAP AG 2002.supported only by the Leasing application.

Reversal of Accrual Subobjects .

It is therefore not possible to delete accrual subobjects. Title of Presentation. © SAP AG 2002. The zero values are valid from the reversal date.  The  Features of the reversal:  It is not possible to reverse accrual subobjects that have been deactivated.Reversal of Accrual Subobjects  Let us assume that a customer wants to delete an accrual subobject. total value and quantity to be accrued are set to zero for all accrual items. since they are needed for the Audit trail. customers have the option of ‘reversing’ accrual subobjects. i. Consequence: No more accrual postings will be made for dates subsequent to the reversal date.e. for explaining the Accounting Documents. the original documents (Accrual Engine documents) cannot be deleted.  As documents are normally created in Accounting for an accrual subobject. This reversal does the following:  All Accrual Engine documents that were posted for this accrual subobject are reversed.  Instead. Speaker Name 136 .

Title of Presentation. Speaker Name 137 .Reversal of Accrual Subobjects © SAP AG 2002.

 There is no ‘true’ reversal of Accrual Engine documents: Reversals are new postings with reversed +/. Speaker Name 138 . © SAP AG 2002. new FI documents are created with reversed values.Reversal Postings in the Accrual Engine  It is possible to reverse certain Accrual Engine documents  Reversal  Reversal of periodic accrual runs of complete accrual subobjects including all corresponding Accrual Engine documents. Changes to the basis data should therefor be made for dates in the past. Instead. Title of Presentation.signs. reversal documents are always created based on the basis data for the accrual subobject that is valid at the key date of the posting.  Consequences:  The  The corresponding FI documents are not reversed.

2000. 2000. The corresponding posting in Accounting is made to this new cost center CC02 as this cost center is valid on key date 31 March 2000. 2000.  If the cost center had been changed on a different date. The reversal posting for the second posting on 31 March 2000 is posted to cost center CC02. the new cost center CC02 would be valid on 31 Jan. The cost center in the basis data of the accrual object on this date is CC01.. In Accounting. Title of Presentation. Speaker Name 139 . 2000. The next accrual posting run is carried out on 31 March 2000. © SAP AG 2002. Reason: In this case. 2000 would be posted to new cost center CC02 instead of CC01. the reversal posting on 31 Jan. the posting is made to cost center CC01.  Now reverse the two accrual postings: The reversal posting for the first posting on 31 Jan. since cost center CC01 is still valid on key date 31 Jan. 2000 is posted to cost center CC01.  The cost center is changed to CC02 on 15 March 2000 in the Basis Data.Example of Reversal Posting  Carry out accrual posting (run) on 31 Jan. say 15 Jan.

Working with Derived Accrual Types New Example .

000 EUR x 10% = 1.Manual Accruals: Derived Accrual Types  Derived accrual types can be used for calculating accruals from other accruals types. The monthly accrual value is 1.800 EUR  The discount must be treated differently according to IAS and HGB (German GAAP):  HGB:  US  Discount is posted once when the contract is created GAAP: Discount has to be accrued during the life of the contract. Title of Presentation. (New) Example:  Customer gets a discount of 10 %  Discount: 18.800 EUR / (5 x 12) = 30 EUR © SAP AG 2002. Speaker Name 141 .

Title of Presentation. Speaker Name 142 .Manual Accruals: Example of Derived Accrual Types  According to US GAAP. © SAP AG 2002.  These additional postings can be made with the help of derived accrual types using the following rule:  “In US GAAP.  The following activities have to be performed in Accrual Engine Customizing:  Create  The the new accrual type “DISCNT” above rule is entered in activity “Define Calculation rules for Derived Accrual Types”. additional accrual postings have to be made for the discount. the discount is calculated by taking 10 % of the revenues in HGB”.

Manual Accruals: Customizing Derived Accrual Types © SAP AG 2002. Speaker Name 143 . Title of Presentation.

Speaker Name 144 . Title of Presentation.Manual Accruals: Customizing Derived Accrual Types © SAP AG 2002.

Title of Presentation.Manual Accruals: Customizing Derived Accrual Types © SAP AG 2002. Speaker Name 145 .

Manual Accruals: Customizing Derived Accrual Types © SAP AG 2002. Title of Presentation. Speaker Name 146 .

Manual Accruals: Derived Accrual Types

© SAP AG 2002, Title of Presentation, Speaker Name 147

Manual Accruals: Derived Accrual Types

© SAP AG 2002, Title of Presentation, Speaker Name 148

Customer-Defined Parameters

Customer-Defined Parameters
 Customer-defined parameters are additional fields that can be entered by users when creating or changing accrual objects  Customer-defined parameters are entered at the accrual subobject level  The values entered here can be used in
 Accrual

Methods The parameters can contain additional information that can be used in customerdefined accrual methods Determination The parameters can also be used in Accrual Engine account determination Parameters can be used in BAdIs for modifying documents before they are transferred to Accounting.

 Account  BAdIs

© SAP AG 2002, Title of Presentation, Speaker Name 150

Speaker Name 151 . Title of Presentation.Where Do Customer-Defined Parameters Appear in the User Interface? © SAP AG 2002.

A popup now appears. Note that the field names must start with ‘Z’ or ‘Y’. where you have to choose ‘Structure’ radio button. © SAP AG 2002.  Save and activate your entries. For this purpose.  To create additional parameters.  Additional (customer-defined) parameters can be created by adding the corresponding fields to this DDIC-structure.How to Define Parameters  Parameters are fields in DDIC structure ACAC_PARAMETERS. named ‘EXAMPLE’. Title of Presentation. Speaker Name 152 . SAP has added the customer include CI_ACAC_PARAMETERS to this DDIC-structure. start transaction SE11 for data type CI_ACAC_PARAMETERS and choose the ‘Create’.  Enter the parameters as fields. This structure contains only one parameter.

Speaker Name 153 .How to Define Parameters © SAP AG 2002. Title of Presentation.

Title of Presentation.How to Define Parameters © SAP AG 2002. Speaker Name 154 .

How to Define Parameters

© SAP AG 2002, Title of Presentation, Speaker Name 155

F4

How to Define Parameters

© SAP AG 2002, Title of Presentation, Speaker Name 156

Entering Parameters

Choose ‘Enter Parameters’

© SAP AG 2002, Title of Presentation, Speaker Name 157

Entering Parameters

© SAP AG 2002, Title of Presentation, Speaker Name 158

Speaker Name 159 . Title of Presentation.Evaluating Parameter Values in Periodic Accrual Runs © SAP AG 2002.

Speaker Name 160 . Title of Presentation.Parameters in Account Determination © SAP AG 2002.

Speaker Name 161 . Title of Presentation.Parameters in Account Determination F4 © SAP AG 2002.

such as Provisions for Awards or Lease Accounting. the procedure for creating additional parameters is almost identical to the procedure described for Manual Accruals. you should note the following differences:  The name of the DDIC structure is different to ACAC_PARAMETERS  Assignment of parameters to accrual object types is only necessary in Manual Accruals © SAP AG 2002.  However. Title of Presentation. Speaker Name 162 .Parameters for Other Components  The preceding slides described the procedure for creating additional parameters for Manual Accruals.  For other applications of the Accrual Engine.

Title of Presentation.Parameters for Other Components: DDIC Structure © SAP AG 2002. Speaker Name 163 .

Customer-Defined Additional Account Assignments .

like  Cost center order area element Center.g. © SAP AG 2002. Speaker Name 165 .Additional Account Assignments  In the Accrual Engine some account assignments can be entered. E. it is not possible to post to a network or network activity.  Because of this it might be necessary to enable more account assignments (like network).  Internal  WBS  Business  Profit  Not all possible account assignments are supported by the accrual engine. Title of Presentation.

0) © SAP AG 2002. Title of Presentation.Additional Account Assignments (Rel. Speaker Name 166 . 1.

Title of Presentation. Speaker Name 167 . 2.Additional Account Assignments (Rel.0) © SAP AG 2002.

Additional Account Assignments (Rel. © SAP AG 2002. Speaker Name 168 . 1. are moved into line items where the GL account is a balance sheet account.0)  The assignments are stored in the database table ACEDSASSGMT. I. the fields of this structure like ‘business area’.  This table contains two substructures:  ACE_PL_ASSIGNMENTS ‘PL’ stands for ‘profit and loss’. Title of Presentation. They are not moved into line items where the GL account is a balance sheet account. are moved into line items where the GL account is a profit and loss account.  Both of these two structures contain customer includes.0 + 2.  In rel. Extensions 2.  CI_ACE_BS_ASSIGNMENTS  CI_ACE_PL_ASSIGNMENTS and where customer-defined fields can be added.e. But they are also moved into line items where the FL account is a balance sheet account. the fields of this structure like ‘cost center’.  ACE_BS_ASSIGNMENTS ‘BS’ stands for ‘balance sheet’. these fields are moved into both types of line items.0 these fields are then automatically displayed on the screen.

0 + 2.Additional Account Assignments (Rel. Speaker Name 169 . 1. Title of Presentation.0) © SAP AG 2002.

2. Title of Presentation.0) © SAP AG 2002. Speaker Name 170 .Additional Account Assignments (Rel.

Posting of Accounting Docs with the Accrual Engine .

 Other types of postings which are less important  These postings have been explained in examples in detail before. This posting is executed. usually to an accrual account. then the remaining value is posted to a certain account. This value is usually a part of full value (which is to be accrued). It is usually posted from the accrual account to a P&L account.  Periodic accrual postings These postings post a certain value which is calculated by the accrual method. Title of Presentation. when the accrual object is created. several or all of the following type of postings:  Opening postings The full amount which is to be accrued is posted. © SAP AG 2002. Speaker Name 172 .Accounting Docs: Basics Of The Accrual Engine  The accrual engine does accrual postings: If the corresponding accrual type is customized accordingly then the accrual engine executes one.  Final postings If the posting of accrual has to be terminated before the full value has been (periodically) accrued.  Each posting creates an accrual engine document and this document is transferred automatically to accounting. These postings are executed by the periodic accrual run which is usually started at the end of each period.

this document is transferred to accounting by calling the BAPI BAPI_ACC_DOCUMENT_POST. this temporary document can be modified with the BAdI ‘ACEPS_BAPIPREDOC_MOD’ (see IMG of the accrual engine). These accounting documents are saved in the corresponding database tables. This BAPI creates all the documents in accounting. too.the CO document. Speaker Name 173 . The system summarizes the two-lined documents and transforms them into another format.   © SAP AG 2002. see next step. After this step. Title of Presentation.  The transfer of accrual engine documents to accounting consists of the following steps:  The system transforms the accrual engine document into a (temporary/preliminary) two-line document.Accounting Docs: How They Are Posted  The accrual engine document consists of one line item only: This line item contains the value which is to be posted. These temporary documents are not saved. Finally. like the FI document and –if required. the summarized documents can be modified with the BAdI ‘ACEPS_BAPIDOC_MODIFY (see IMG of the accrual engine). These documents are not saved. It also contains the reference. the key date which is used as translation date and as default posting date in accounting. After this step. to which accrual object it belongs. which is required by the BAPI.

Accounting Docs: Overview Accrual Engine Accrual Engine Document Preliminary two-lined document BAdI ACEPS_BAPIPREDOC_MOD Summarized document BAdI ACEPS_BAPIDOC_MODIFY Accounting Call BAPI FI document © SAP AG 2002. Title of Presentation. Speaker Name 174 CO document .

How to Fill Special Fields in the Accounting Documents .

in the BAPIACGL09 structure) but not available in the preliminary document (e.  To fill these fields there are two BAdIs available (see next slides). Speaker Name 176 . Title of Presentation.   It might be necessary from the customers point of view that some fields have to be populated which are   available in the BAPI interface (e. Included in this structure is the DDIC structure ACEPS_BAPI_PRELINEITEM which contains all the fields which are filled in the line item of the accounting document.Special Fields in the Accounting Documents  The accrual engine only populates some of the fields which exist in the accounting document: The fields that are filled by the accrual engine are contained in the complex DDIC structure ACEPS_BAPI_PREDOC. © SAP AG 2002.e.g. i. they are not filled automatically by the accrual engine. structure ACEPS_BAPI_PRELINEITEM).g.  The complete set of fields which are available in the accounting document can be viewed in the DDIC structures BAPIACHE09 (document header)  BAPIACGL09 (line items)  BAPIACCR09 (currency information) These structures are the interface of the BAPI which is used for posting the accounting documents.

Speaker Name 177 . In this BAdI interface the accrual engine document is available which contains the link to the accrual object.e.available BAdIs in Accrual Engine BAdI ACEPS_BAPIPREDOC_MOD: is used to fill special fields in the accounting document which depend on the accrual object. BAdI ACEPS_BAPIDOC_MODIFY: is used to fill fields in the summarized document. immediately before the document is transferred to accounting with the BAPI. © SAP AG 2002. In this BAdI interface the accrual engine document which contains the link to the accrual object is not available anymore. I. Title of Presentation.

Customer-defined fields in Special Ledgers .

 The following slides visualize the problem and its solution. inhancements like BAdIs are necessary to solve this problem.e. through the accounting interface into the special ledger. through the BAPI which creates the accounting documents. Title of Presentation. i.Customer-Def. the fields cannot be populated by postings which are done by the accrual engine in standard.  The task is to transport the values of the customer-defined fields from the accrual engine. Because of this.  The problem is that the customer-defined fields do not exist in the BAPI interface (DDIC structure BAPIACGL09) and also not in the preliminary documents in the accrual engine (DDIC structure ACEPS_BAPI_PRELINEITEM). Fields in Special Ledgers  A more complex problem are customer-defined fields in a Special Ledger: It might be necessary that these fields are populated when documents are posted by the accrual engine. © SAP AG 2002. Speaker Name 179 .

SL interface CONS interf. Title of Presentation. FI interface FI CO CO-PA PrCtr SL CONS © SAP AG 2002. PrCtr interf.Excursus: Architecture of Accounting in R/3 BAPI Accounting Interface DDIC structures: ACCHD ACCIT ACCCR CO interface CO-PA intf. Speaker Name 180 .

Speaker Name 181 . Title of Presentation.Excursus: Architecture with Accrual Engine Accrual Engine Document Preliminary two-lined document Summarized document BAPI Accrual Engine Accounting Interface SL interface SL Accounting © SAP AG 2002.

PrCtr interf.Customer-Def. Speaker Name 182 . which contains a customer-defined field. BAPI Accounting Interface FI interface FI CO CO-PA PrCtr SL CONS Step 1 (precondition): A special ledger was configured. SL interface CONS interf. e. the field ZZREGION. so that it can be ‚transported‘ from the BAPI through the accounting interface to the special ledger. Title of Presentation.g. Fields in Special Ledgers: Steps 1+2 Step 2 (precondition): The customer-defined field must also be added to the accounting document line item (ACCIT structure). DDIC structures: ACCHD ACCIT ACCCR CO interface CO-PA intf. © SAP AG 2002.

In this BAdI the field ZZREGION has to be filled. Accrual Engine Document Preliminary two-lined document Summarized document BAPI Accrual Engine Accounting Interface SL interface SL Accounting © SAP AG 2002.Customer-Def. Title of Presentation. with the SE11 transaction). Fields in Special Ledgers: Step 3+4 Step 3: The customer-defined field must also be added to the line item of the preliminary two-lined document (ACEPS_BAPI_PRELINEITEM structure. Step 4: A BAdI implementation has to be defined for the BAdI ACEPS_BAPIPREDOC_MOD. Speaker Name 183 .

Customer-Def. Fields in Special Ledgers: Step 3 © SAP AG 2002. Speaker Name 184 . Title of Presentation.

Speaker Name 185 . Fields in Special Ledgers: Step 4 © SAP AG 2002. Title of Presentation.Customer-Def.

this field has to be added to the DDIC structure BAPIACGL09.Customer-Def. Preliminary two-lined document Summarized document BAPI Accrual Engine Step 6: The value for the customer-defined field has to be moved from the line item of the summarized document into the Extension table. © SAP AG 2002. Title of Presentation. This is done in a BAdI implementation for the BAdI ACEPS_BAPIDOC_MODIFY. Fields in Special Ledgers: Steps 5+6 Accrual Engine Document Step 5: To make the new field ZZREGION available in the BAdI ACEPS_BAPIDOC_MODIFY. Speaker Name 186 Accounting Interface SL interface SL Accounting . .

Title of Presentation. Fields in Special Ledgers: Steps 5 © SAP AG 2002.Customer-Def. Speaker Name 187 .

Fields in Special Ledgers: Steps 6 © SAP AG 2002. Title of Presentation. Speaker Name 188 .Customer-Def.

Speaker Name 189 . Title of Presentation. Preliminary two-lined document Summarized document BAPI Accrual Engine Accounting Interface SL interface SL Accounting © SAP AG 2002. This is done in an implementation for the BAdI ACC_DOCUMENT. Fields in Special Ledgers: Steps 7 Accrual Engine Document Step 7: The value for the customer-defined field has to be moved from the Extension table into the line item of the accounting document (ACCIT table).Customer-Def.

Title of Presentation.Customer-Def. Fields in Special Ledgers: Steps 7 © SAP AG 2002. Speaker Name 190 .

Assignment Number and Automatic Clearing .

(P.1) (P.Assignment Number: General  The assignment number in FI documents is usually needed to carry out clearing automatically.1).1) and periodic postings (P.2) 1.. .4) must contain the same assignment number.. Title of Presentation.000 clearing (report SAPF124) is run after posting (P. (P.P.4) should be cleared after the last periodic posting (P. (P.4). D Accrual Account C 3.000 Condition: All documents (I.2). © SAP AG 2002. the automatic (P.3) 1.4).000 (I.  The assignment number can be useful for clearing postings to accrual accounts if open item management is active for the accrual account.2 .4) 1. Problem: The Accrual Engine does not add the assignment number to the Accounting documents.  Open posting (I.000  For this reason. Speaker Name 192 .

but then no summarization would be possible during transfer of Accrual Engine Documents to Accounting. CS_BAPI_PREDOC-LINEITEMS contains field ALLOC_NMBR (‘Assignment Number’). This field can be filled by the customer when implementing the BAdI. Title of Presentation. the Accrual Engine does not enter the assignment number. Speaker Name 193 .  However.  As a result.  Parameter © SAP AG 2002.Assignment Number: How it can be entered  The Assignment Number is not entered in postings made by the Accrual Engine. as this number should in principle be unique for each accrual item. it is possible to fill the assignment number using the BAdI (Business Add In) ACEPS_BAPIPREDOC_MOD:  The customer has to define an implemation for this BAdI in Customizing.

but the accrual object number has 22 digits. An example would be the accrual object numbers that are used by the automatic data feed of invoices (ACACDATATRANS transaction). Speaker Name 194 . Because of this one has to be careful when using the accrual object number as assginment number.e. not as an external number range) in the customizing (ACAC_NUMOBJ transaction). then the accrual object number can in general not be used as assignment number. since the number range for accrual object numbers (ACAC_NUMOBJ transaction) has only 10 digits: The other 12 digits are filled with zeros. Title of Presentation. only the document number of the invoice (which is part of the accrual object number) should be used as assignment number. then it is ok to use the accrual object number as assignment number. The only problem is that the assignment number has 18 digits.Example: How to fill the assgmt number in postings  The assignment number can be filled in the BAdI ACEPS_BAPIPREDOC_MOD by the customer. In this case.  © SAP AG 2002.  If the accrual object number is defined as an internal number range (i.  The following slides are intended to help the customer to define an implementation for the BAdI with a source code that filles the assignment number reasonably in case of the application ‚Manual Accruals‘:  It would be natural to use the accrual object number as assignment number. If the accrual object number is defined as an external number range.

Speaker Name 195 . Number and Accrual Obj. Title of Presentation.Example: Assgmt. Number © SAP AG 2002.

Speaker Name 196 .Example: Define the BAdI Implementation © SAP AG 2002. Title of Presentation.

Title of Presentation.Example: Define the BAdI Implementation © SAP AG 2002. Speaker Name 197 .

Example: Sample Source Code in BAdI © SAP AG 2002. Title of Presentation. Speaker Name 198 .

Parallel Accounting .

 Parallel © SAP AG 2002. The corresponding posting in accounting will then be done only in this special ledger. a special ledger is assigned to one of the accounting principles.Parallel Accounting  The Accrual Engine supports parallel accounting in two ways  Parallel accounts The account determination can be customized in a way that different accounts are used depending on the accounting principle. ledgers The account determination need not yield different accounts for different accounting principles. Speaker Name 200 . but in the customizing of accounting. Title of Presentation.

Speaker Name 201 .Parallel Accounting: Create Accrual Object © SAP AG 2002. Title of Presentation.

Parallel Accounting: Parallel Accounts © SAP AG 2002. Speaker Name 202 . Title of Presentation.

Parallel Accounting: Parallel Ledgers © SAP AG 2002. Title of Presentation. Speaker Name 203 .

Validation .

Title of Presentation. Speaker Name 205 .  A validation can be created and activated to execute checks. © SAP AG 2002. when an accrual object is created or changed.Validation of Creating/Changing Accrual Objects  The validation is a tool to execute customer-defined checks.

Title of Presentation.Creating Validations © SAP AG 2002. Speaker Name 206 .

After activating the append structure. The F3 key makes the system continue. the checks fail somehow. start again the transaction for creating or changing accrual objects again.e. Title of Presentation.  If the validation does not yield the desired result. © SAP AG 2002.Validating Customer-Defined Parameters  Checking customer-defined parameters (see corresponding chapter) in the validation is possible:  Before customer defined parameters can be used in the validation. the added fields are available in the validation. In the append structure the corresponding fields have to be added. it might be usful to swith on the trace in the validation maintainance transaction (GGB0 transaction): In the menue choose the function ‘Extras -> Activate trace’. an append structure has to be created using the SE11 transaction.  Afterwards. The system will then stop in the validation. i. the corresponding fields have to be added to the DDIC structure ACEVSR_VAL_PAR  To do this. Speaker Name 207 .

Activating Validations © SAP AG 2002. Title of Presentation. Speaker Name 208 .

Customer-Defined Navigation .

 The example implemenation ACAC_UI_NAVIGATION for Manual Accruals executes a navigation to the vendor invoice. 2. SAP deliveres the implementation ACAC_UI_NAVIGATION as example. a navigation from the display transaction of accrual objects. since in this case it is assumed that a vendor invoice is accrued and the document number of the vendor invoice is contained in the accrual object number. © SAP AG 2002.0 on. Title of Presentation. The customer can define additional implemenations since multiple usage is allowed for this BAdI. Extensions 2. This way.0)  From rel. Speaker Name 210 .  This navigation is done with the BAdI ACE_UI_NAVIGATION. a vendor invoice or insurance contract) for which the accrual object was created. it is possible to execute a customer-defined navigation from the accrual object to the original object (e. the system can find the vendor invoice and display it.g.Navigation (Rel. if the accrual object type is ‘0VENDORINV’.  For the application Manual Accruals.

Navigation (Rel.0): Example Manual Accruals © SAP AG 2002. 2. Title of Presentation. Speaker Name 211 D ou bl ec lic k .

Archiving Accrual Engine Data .

ACEDSOH. ACEDSASSGMT. Remark: Accrual Engine documents are needed for the reversal of periodic accrual runs.Archiving  Archiving Accrual Engine data is done in two steps:  Archive Accrual Engine documents (archiving object FI_ACE_ITM) This archiving object contains the database table ACEPSOIT. Speaker Name 213 .  The © SAP AG 2002. ACEPSOI. Prerequisites for archiving accrual objects:  All Accrual Engine documents have been archived (archiving object FI_ACE_ITM) for this accrual object accrual object has the status ‘To Be Archived’. hence please archive only Accrual Engine documents which are not needed any more for reversals. Title of Presentation. ACEDSOI.  Archive Accrual Engine objects (archiving object FI_ACE_OBJ) This archiving object contains the database tables ACEOBJ. ACEPSOH.

Archiving: Archiving Objects ACEOBJ Field Name MANDT COMP BUKRS OBJID REF_KEY STATUS Key X X X X ACEDSOH Field Name MANDT COMP BUKRS OBJID SUBID DATE_TO DATE_FROM VALITY_FROM VALITY_TO UNAME CPUDT CPUTM REF_SUBKEY STATUS Key X X X X X X ACEDSOP Field Name MANDT COMP BUKRS OBJID SUBID DATE_TO PARAM_NAME CONTENT DATE_FROM Key X X X X X X X ACEDSASSGMT Feldnam e MA D N T C M O P B K S U R O JID B SU ID B D E_T AT O D E_FR M AT O BU S_AR EA D E_FR M AT O PR FIT T O _C R C ST EN ER O C T Key X X X X X X ACEPSOH Field Name MANDT COMP BUKRS OBJID SUBID UNAME CPUDT CPUTM DEACTDATE REF_SUBKEY STATUS FIRSTYEAR LASTYEAR Key X X X X X FI_ACE_OBJ ACEDSOI_ACCOUNTS Field Name MANDT COMP BUKRS OBJID SUBID ACRTYPE ACCRULE DATE_TO DATE_FROM INC_START_ACCNT INC_TARGET_ACCNT PER_START_ACCNT PER_TARGET_ACCNT FIN_START_ACCNT FIN_TARGET_ACCNT Key X X X X X X X X FI_ACE_ITM ACEPSOIT Key X X X X X X X X X Key X X X X X X X X ACEDSOI Field Name MANDT COMP BUKRS OBJID SUBID ACRTYPE ACCRULE DATE_TO DATE_FROM AMOUNT CURRENCY QUANTITY UNIT ACRMETHOD TIMESTMP Key X X X X X X X X ACEPSOI Field Name MANDT COMP BUKRS GJAHR OBJID SUBID ACRTYPE ACCRULE CUMVALCAP CUMVALACCR VALCAP VALACCR VALRETIRE LASTEFFDATE CURRENCY Field Name MANDT COMP BUKRS GJAHR OBJID SUBID ACRTYPE ACCRULE DOCNR VALCUM VALTBP CURRENCY TRANSTYPE EFFDATE POPER RUNID AWTYP AWKEY AWSYS TIMESTMP © SAP AG 2002. Speaker Name 214 . Title of Presentation.

Archiving: Changing the Status of Accrual Objects © SAP AG 2002. Title of Presentation. Speaker Name 215 .

Archiving: Status of Accrual Objects  The status of the accrual object is displayed in the technical data: ch Data Disp. Te © SAP AG 2002. Title of Presentation. Speaker Name 216 .

Provisions for Awards .

 To do this: Transfer information about outstanding optoins from HR system to Accounting system (Accrual Engine)  Afterwards: Calculate and post provisions using the Accrual Engine  Different calculation (=accrual) methods are possible for calculating the provisions: SAP delivers two examples as accrual methods:  APB  FAS 25 123 Provisions based on stock prices Provisions based on Black & Scholes Model © SAP AG 2002.Provisions for Awards: Overview  A company grants a number of stock options to selected employees  Purpose: Post provisions (= accruals) for the outstanding options. Speaker Name 218 . Title of Presentation.

Title of Presentation.Provisions for Awards: Architecture HR-System Provisions for Awards Trigger Calculation of Accruals Accrual Method R R Accrual Engine Read HR Data R Transfer Data to Accrual Engine R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Outstanding Awards Reporting Reporting © SAP AG 2002. Speaker Name 219 .

Title of Presentation. Speaker Name 220 .Provisions for Awards: Processes HR-System Provisions for Awards Process B: Calculate Trigger Calculation of and Post Accruals Accruals Accrual Method R R Accrual Engine Read HR Data R Process A: Process A: Create/ Transfer Data Change from HRBasis Data System R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Outstanding Awards Reporting Reporting © SAP AG 2002.

Title of Presentation.Provisions for Awards: Processes Treasury Read Stock Rates Stock Rates R HR-System Provisions for Awards Process B: Calculate Trigger Calculation of and AccrualsPost Accruals Accrual Method R R Accrual Engine Read HR Data R Process A: Process A: Create/ Transfer Data Change from HRBasis Data System R Create/ Change Basis Data Periodic: Calculate Accruals R Build Delta to already posted values R Post Document R Create Accounting Documents Basis Data (Accrual Objects) Posted Values (Accrual Engine Documents) Calculation Posting Outstanding Awards Reporting Reporting © SAP AG 2002. Speaker Name 221 .

Accounting Principle (IAS.Provisions for Awards: Structure of Basis Data Grant (=Accrual Object) Vesting (=Accrual Subobject) Vesting (=Accrual Subobject) Award... Grant Date and Cost Center (optional) Header Assignment Vesting (=Accrual Subobject) Parameters Vesting Date Default: Cost Center Basis Security ID.. The number of outstanding awards is stored together with the accrual method at this level.. ) and . Accrual Item Accrual Item Accrual Item ..) defines an Accrual Item. FAS123. Basis Value. Title of Presentation. . . Speaker Name 222 Each combination of . . © SAP AG 2002. US GAAP...Accrual Type (APB25... Exchange.

Provisions for Awards: Application Menu © SAP AG 2002. Speaker Name 223 . Title of Presentation.

Title of Presentation. Speaker Name 224 .Provisions for Awards: Application Menu © SAP AG 2002.

Speaker Name 225 . Title of Presentation.Provisions for Awards: Customizing in Accounting © SAP AG 2002.

Title of Presentation. Speaker Name 226 .Provisions for Awards: Customizing in HR © SAP AG 2002.

Provisions for Awards: Example .

provisions must be posted in good time in Accounting. 2003. and the remaining 1. 2001. meaning that these options will have an inner value if the stock price rises above 100 EUR. a further 2. the company will have to meet the corresponding costs.The company decides to make the 6. Speaker Name 228 . vesting date: 1 Jan. 2001. The division of the 6. 2000 to 1 Jan. • 1 Jan. 2000 to 1 Jan.Provisions for Awards: Example  Prereqisites:  On 1 Jan. 2002: 2. The waiting periods are also referred to as vesting periods.000 options. 2.000 options.000 stock options into vesting periods of 3.000 options.000 is referred to as a vesting rule. The security identification number of the company stock is "0000000000001". 2002: 1. 2002.These waiting periods are as follows: • 1 Jan. • 1 Jan.000. 2001: 3.000 can be exercised from 1 Jan.000 stock options that it awards available in three waiting periods. vesting date: 1 Jan. 2002. 2003. © SAP AG 2002. Title of Presentation.  The employees cannot exercise their stock options until expiry of the waiting period. vesting date: 1 Jan. 2000.  This means that 3. company code 0001 will issue 6.000 and 1. If the stock price has a value of more than 100 EUR when the stock options are exercised.000 can be exercised from 1 Jan.000 stock options can be exercised from 1 Jan. For this reason. 2000 to 1 Jan. The base price of the options is 100 EUR.000 options (award OPTN) for company stock to the employees of cost center "Executive Board".

Customizing has to be adjusted accordingly for the data transfer program.Provisions for Awards: Example  Data Transfer HR -> Accounting (Accrual Engine)  Provisions can be calculated and/or posted according to different rules.  SAP delivers two accrual methods: ACC_APB25 and ACC_FAS123 for calculating provisions according to APB 25 and FASB 123 respectively. a separate accrual item has to be created. Title of Presentation.  © SAP AG 2002. Speaker Name 229 .  For each desired rule.

Provisions for Awards: Customizing Data Transfer © SAP AG 2002. Title of Presentation. Speaker Name 230 .

Speaker Name 231 . Title of Presentation.Provisions for Awards: Customizing the Data Transfer © SAP AG 2002.

Speaker Name 232 .Provisions for Awards: Data Transfer © SAP AG 2002. Title of Presentation.

 With APB25.  Method FASB 123 calculates the provisions based on an average stock price assumed by the historical volatility of the underlying stock. Speaker Name 233 . © SAP AG 2002. Title of Presentation.  This means that the provisions do not fluctuate as they would using method APB 25. the company can choose between the two methods APB 25 and FASB 123 .Provisions for Awards: APB 25 and FAS 123  To post the provisions.  Method APB 25 uses the current stock price to calculate the inner value of the outstanding options. the provision amount fluctuates in the same way as the stock price. If the company chooses the APB 25 method. it must add an additional calculation of the provisions according to FASB 123 in the appendix of the balance sheet.

33 + 27. For the first waiting period from 1 Jan. 1/12 .612 EUR © SAP AG 2002.or 8.02 % This provides the following provision amounts for the three waiting periods:  First waiting period:  Second waiting period:  Third waiting period: 3.000 options x 10 EUR x 6.000 + 1/24 x 2.000 = 0.0602 = 6.000 options x 10 EUR x 6.204 EUR + 602 EUR = 3.17 %) and 1/36 (= 2.806 EUR + 1.000 + 1/36 x 1. 2000.3 % has expired by 31 Jan. only this fraction has to be depicted as a provision. Speaker Name 234 . the stock price is 110 EUR.78) / 6.000 + 2. the option has an inner value of 10 EUR. The system calculates the weighted vested share thus: (1/12 x 3. 2000. On this date. As the base price taken over from HR is 100 EUR.000 options x 10 EUR x 6. 2001 (vesting date). The vested share for the second and third waiting periods is worked out in the same way: 1/24 (= 4. 2000 to 1 Jan.78 %).000 + 1.02 % = 602 EUR  Total: 1.02 % = 1204 EUR 1.Provisions for Awards: APB 25  Accrual Method ACC_APB25 works as follows: The value of the provisions is to be determined for 31 Jan. Title of Presentation.02 % = 1806 EUR 2.000) = (250 + 83. Accordingly.000) / (3.

Title of Presentation.Provisions for Awards: APB 25 (II) Enter Stock Prices © SAP AG 2002. Speaker Name 235 .

the last vesting date determines the vested share.78 %.78 % = 305.00 EUR 1000 x 11 EUR x 2. Speaker Name 236 .78 % = 556. In the example: 1/36 = 2.08 EUR  © SAP AG 2002. Instead.Provisions for Awards: FASB 123  Accrual method ACC_FAS123 works as follows: In contrast to method APB 25. Title of Presentation. Instead. This results in the following provision amounts:  First waiting period:  Second waiting period:  Third waiting period: Total: 1612. values can be defined by waiting period.40 EUR 3000 x 9 EUR x 2.78 % = 750. Here. the value of an option is defined manually in IMG activity "Define Data for the Black & Scholes Model". Example:  First waiting period:  Second waiting period:  Third waiting period: 9 EUR 10 EUR 11 EUR   The vested share is not used as a weighting of the three individual waiting periods.60 EUR 2000 x 10 EUR x 2. the value of an option is not calculated using the price of the underlying stock.

Provisions for Awards: FASB 123 (II) Enter Black & Scholes Values © SAP AG 2002. Title of Presentation. Speaker Name 237 .

Speaker Name 238 .Provisions for Awards: Display Transferred Data (I) © SAP AG 2002. Title of Presentation.

Provisions for Awards: Display Transferred Data (II) © SAP AG 2002. Speaker Name 239 . Title of Presentation.

Provisions for Awards: Display Transferred Data (III) © SAP AG 2002. Title of Presentation. Speaker Name 240 .

Speaker Name 241 . Title of Presentation.Provisions for Awards: Periodic Posting Run © SAP AG 2002.

. RS/6000®. R/2.           © SAP AG 2002. The information contained herein may be changed without prior notice. 901 San Antonio Road. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. SAP EarlyWatch. California. mySAP. SAP Logo. SAPPHIRE. Massachusetts Institute of Technology. Inc. and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation. INFORMIX®-OnLine for SAP is a registered trademark of Informix Software Incorporated. OSF/1®. Microsoft®. AIX®. Management Cockpit. AS/400®. ABAP. XHTML are trademarks or registered trademarks of W3C®. JAVASCRIPT® is a registered trademark of Sun Microsystems. SAP. NT®. Word® and SQL Server® are registered trademarks of Microsoft Corporation. DB2®. Inc.com. Palo Alto. All other products mentioned are trademarks or registered trademarks of their respective companies. are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. DHTML. MVS/ESA®. mySAP. UNIX®.com Marketplace..Copyright  No part of this presentation may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. S/390®. CA 94303 USA. OS/2®. XML. USA. OS/390®. WINDOWS®. 545 Technology Square. Cambridge. SAP Business Workflow. Title of Presentation. JAVA® is a registered trademark of Sun Microsystems. HTML.com Business Scenarios. mySAP. IBM®. Laboratory for Computer Science NE43-358. EXCEL®. mySAP. X/Open®. and Motif® are registered trademarks of The Open Group. Parallel Sysplex®. SAP ArchiveLink. Speaker Name 242 . R/3.com Application Hosting. SEM. World Wide Web Consortium. BAPI.com Workplace. DB2/6000®. mySAP. RIVA. used under license for technology invented and implemented by Netscape. MA 02139. WebFlow.

Sign up to vote on this title
UsefulNot useful