RESÚMENES COMPILADOS

8/7/2019 RESMENES COMPILADOS

1/52

TFIN50I PART 1

UNIT 1: BASIC SETTINGSLesson 1: Organizational Units

Client: Highest level: independent unit: separate MRs and set of tables/data.

Important Organization Units in FI: 1. Company Code (CC): Independent

balancing/legal @ing entity (Minimum structure of FI). 2. Business Area (BA):Separate areas of operation (can create own set of Financial Statements (FS) andcan be used across CCs.

Creating a CC: Copying an existing CC copies: 1. Definition, 2. GlobalParameters, 3. Customizing Tables, 4. GL @s, and 5. @ Determination.

Editing CC data (defining a CC): 1. Four-character CC key (identifies CC), 2.Name, 3. City, 4. Country, 5. Currency, 6. Local Currency, 7. Address.

Define BA: 1. Four-digit alphanumeric key, 2. Description. To create FSs for BAs,the field for BA in line item must be ready for input. In activity Enable BA FSs, set indicator for the

BA field for each CC. Once done, the BA field is always ready for input when you post docs regardless of

field controls for the PK and @s.

Country Templates (CC 001): A template for a general CC with CA INT and nocountry specifications. What does country template contain?1. Cross-Application: Calendarsettings, factory calendar, public holidays, etc. 2. FI: Tax on sales and purchases calculation procedures,

withholding tax, @ determination, charts of @s, FS versions, Customizing settings for the PYMT

program, PYMT methods and sample house banks, formats for the electronic @ statement, valuation

approaches, etc. 3. CO: Cost elements, standard hierarchies for cost centers, profit centers, etc. 4. Other

country-specific templates for other areas.

Lesson 2: Variant (V) Principle.Three step method used to assign particular properties to one or more objects.Steps: 1. Define V, 2. Determine Values for V, 3. Assign V to objects. V is used for:a. Fields Status, b. PP, c. FY. The advantage of the V principle is the low level of maintenancerequired in the sys.

Lesson 3: Fiscal Year (FY).

FY defined as a period of 12 months for which a company regularly creates an inventory and FSs. 1.Year-Independent: number and start dates for the period are the same for everyyear: a. calendar year, b. Non calendar year. 2. Year-Specific: Periods can varyfrom year to year. Conditions: 1. Start and end dates of the posting periods forsame FY are different to the dates to other FYs. 2. If all the FYs of FY variant havethe same number of posting periods, only the dates have to be defined. 3. If oneFY variant has less posting periods than others, is a shortened FY (closing inadvance). Special Periods: Used for postings not assigned to time periods but tothe business process of year-end closing. Max. 16 periods. How do I post in a specialperiod? 4 conditions: 1. Posting date must be in last PP (irrespective of whether this last PP is open). 2.

Special periods must be open for posting. 3. Special period must be entered manually when posting. 5.

Authorization to post in special periods must be given (optional).

Lesson 4: Currencies.

Currencies and exchange rate (T) types: Currency key: assigned to everycurrency used. T type: diff. T for every combination of two currencies.Translation ratios: to maintain the relationship between two currencies per Tand currency.

Maintaining T: Tools: 1. Inversion2. Base currency: choose one currencyand maintain the rest currencies only to that one 3. T spreads: between the bankbuying/selling rate and average rate usually remains constant.

Direct Quotation of T: 1 unit of foreign currency is quoted for the localcurrency. Indirect quotation: one unit of local currency is quoted for the foreigncurrency.

Work lists for maintaining T: 1. Only the relevant T can be maintain and

assign authorizations. 2. Only the relevant quotation can be maintain. 3. The

1


2/52

worklist is smaller and therefore clearer. 4. Parallel processing of diff worklists ispossible.

Design of T in diff. quotations: 3 scenarios: 1. Mostly work with directquotations (blank for direct and / for indirect). 2. Increasingly use ofindirect quotation (* for direct and / for indirect). 3. Mostly use of indirectquotation (* for direct and blank for indirect).

UNIT 2: MASTER DATALesson 1: GL Accounts

Chart ofAccounts (CA): Variant with structure and basic info about GL @s.Steps: 1. Define the CA (assign a 4-character ID). 2. Define properties (language,length of the @ number, CA group, status). 3. Assign the CA to CC.

Define CA: 1. CA key, 2. Description. General info: Language and length (1-10 digits). Controlling integration: Manual or automatic creation of costelements. Consolidation: Group of CA (used for cross-company reporting ifcompanies use diff CA. Status: blocked indicator if CA is not yet completed.

Assigning the CA to every CC: Using V principle, one CA can assign to severalCCs. Controlling uses the same CA than FI. If CCs intend to use cross-company code

controlling they must have the same CA.

CA segment: contains basic info about @s: 1.@ Number. 2. Name. 3.Control fields. 4. Consolidation fields.

Fields in the CA segment: applies to all CCs. Groups of fields (tab pages):A. Type/Description: 1. Control in CA. 2. Description. 3. Consolidation data in CA.B. Keyword/Translation: 1. keyword in CA 2. Translation. C. Information: 1. Infoin CA. 2. GL texts in CA. Tab pages can be defined on: # of tab pages, title, fieldgroups and their position on the tab pages and select layout for central processing.

CC segment: Must be created for the @ to use this @ from the CCs CA. CCsegment + CA segment form the @.

Fields in the CC segment: 1. Currency. 2. Taxes. 3. Reconciliation @. 4. Lineitem display. 5. Sort Key. 6. FST group. 7. House Bank/ interest calculation info.Groups of fields:A. Control/Data: 1. @ control. 2. @ Management. 3. Jointventure. B. Bank/interests: 1. Doc creation. 2. Bank/fin. Details. 3. Int. calculation.C. Information: 1. info. 2. GL @ texts.

One CA, Several CCs: A CA segment can be assigned to several CC segments. Ex: 2 CCs use

the same CA. Therefore, both CCs use same CA segment of a G/L @, but each have a different CC

segment. The entries in the CC segment are CC-specific and can be diff. for diff. CCs (for example,

different currencies).

Balance sheet (BS) and P&L statement @s: CA segments ask if @ is BS(balance is carried forward to same @) or P&L statement @ (balance is carriedforward to a retained earnings @ and the P&L @ is set to 0.

Retained Earnings @: is part of the FSs. Use field P&L Statement @ Type to define retainedearnings @ to which balance is carried forward. Define the key in Customizing. If user has only defined

one retained earnings @ in Customizing, the P&L Statement @ Type field is hidden in the G/L @ MR.

User can use different retained earnings @ to reflect different FS standards within the sys.

@ groups for GL @s: Assign range # to an @ group to ensure similar @s aregrouped together. In CA segment, enter @ group to control appearance of CCsegment of a GL @.

FST: Enables to control the display and maintenance of an @s master data.What is the purpose of the FST?: 1. Superfluous field groups or fields are hidden. 2. Input errors are

avoided. Priority: 1. HIDE (not used fields). 2. DISPLAY(values that must not bechanged). 3. REQUIRED (required value enter). 4. OPTIONAL (can contain entrybut are not required). Fields @ currency and FST group are always required. Two

options for controlling the FST: @ group-specific and Transaction-specific.

2


3/52

FST for master data: Not only @ group controls the field, also the transactionused to edit master data. Change master data transaction is used when aftercreating a MR, its data is not intended to be changed. By choosing OPTIONAL, @group specific control is used when not wanting to use transaction-specific control.

Reconciliation Accounts: GL @s assigned to the business partner MRs to

record all transactions in the Sub-ledger (SL). All postings to SL @s areautomatically posted to the assigned reconciliation @s. You cannot post directly tothose @s. The reconciliation @ connects a SL to the GL realtime. The following SLs are connected tothe GL via reconciliation @s: 1. @s Receivable. 2. @s Payable. 3. Assets. 4. Contract @s Receivable

and Payable. A report carries out reconciliation between GL and SLs through consistency checks as part

of the monthly GL closing: 1. Debit and credit transaction figures of the C/V, and G/L @s with the debit

and credit totals of the posted docs. 2. Debit and credit transaction figures of C/V, and G/L @s with the

debit and credit totals of the application indexes (secondary index).

Line Item display: Transaction figures are total of line item postings on thedebit or credit side. Balance=D-C. Line Item display field is control field in the CCsegment of an @. @s without line item display: Transaction figures updatedwhen docs are posted (user can only view balance). @s with line item display:Data stored in special index table and user can see balance and line items. NOTUSE LID FOR: 1. Recon. @s (line items are managed in SLs). 2. Revenue @s(managed by sales application). 3. Material stocks @s (managed by purchasingapplication). 4. Tax @s. Line items are items posted to a specific @. In contrast to a doc item, a lineitem only contains information relevant from the @ view. User can display the following line items in a

G/L @: 1. Open items. 2. Cleared items. 3. Noted items. 4. Parked items. User defines whether an @ is

managed with line items in the MR of the G/L @. User can activate line item display for an @ later (@

has already been posted to). Prerequisites: 1.Line item display is active in the G/L @. 2. @ is blocked for

posting during the changeover.

Open Item Management: line item display should be activated for the @.Open Item Management is necessary to see if theres any offset posting for a BT.USE OIM FOR: 1. Bank clearing @s. 2. Clearing @s for goods receipt/invoicereceipt. 3. Salary clearing @s. Cleared Items: already closed with an offsetting

doc. OIM can only be activated or deactivated if @ has 0 balance. If indicatorOIMt is set in MR for a G/L @, items belonging to this @ are either open items or cleared items. The

balance of an @ with OIM is always the balance of the open items. G/L @s are always managed with

OIM if user wants to see if an offsetting posting exists for a BT

Accounts in local currency: If @ currency is local, that @ can be posted inany currency.

Only Balances in local currency: (Checkbox), if activated in MR, transactionfigures are only managed for amount converted to local currency. USE IT FOR:clearing accounts that use same local currency amount without necessitating Tdifference postings.

@s in foreign currency: only posted in chosen currency and not in local

currency. Creating a GL @:A. Manually: 1. Centrally 2. Two steps: CA segment andCC segment. B. Copying: 1. An individual GL @. 2. Entire CA segment. 3. Entire CCsegment. C. Data transfer: transfer a new CA from an external system.

Collective Processing: change simultaneously: 1. CA data. 2. CC data 3.Description.

Group CA: Possible to have internal reporting (FS) that contains items fromseveral CCs that share the same CA. When thats not possible because of legalconstrains, use Group CA assigned to each operational CA. Disadvantage: not crossCC controlling because of diff. CAs.

Country CA: alternative to Group CA to fulfill the country-specific requirements for

external reporting and simultaneously carry out uniform internal reporting. All CCs use the sameoperational CA but if a CC requires a special CA, use the country CA. Enter it in

3


4/52

every CC segment. Cross CC controlling because of the same CAs is possible. The linkbetween an @ in country CA and in operational CA is always a 1:1 relationship.

Lesson 2: Customer/Vendor (C/V) Accounts

Accounting View of the C/V @: C/V @s have 2 segments: 1. At clientlevel with general data and 2. At CC level with CC specific data. Any CC thatis to do business with a C/V has to create a CC segment for the C/V (creating aC/V@).

Sales Area and Purchasing Organization Segments can be crated foreach C/V.

The complete Customer @: 3 segments: 1. Gral Data at clientlevel. 2. CC segment. 3. Sales area segment. @ Number is assigned tothe customer at client level so it applies for all CCs and sales areas.

The complete Vendor @: 3 segments: 1. Gral Data at client level.2. CC segment. 3. Purchasing organization segment. @ Number isassigned to the customer at client level so it applies for all CCs and salesareas.

Centralized Maintenance: to FI, MM and SD. Decentralized Maint.:from FI, MM and SD separately. Compare Master Data is possible to avoidduplicated or incomplete MRs. Two ways: 1. Use match code before creating anew @. 2. activate automatic duplication check.

Pages of the C/V @: Groups of fields in every @ segment. 1. Graldata: address, control data, payment tranasactions + texts. 2. Companydata: accounting info, payment transactions, correspondence, insurance,withholding tax + texts.IMPORTANT FIELDS: 1. SEARCH TERMS(abbreviation of C/V name to find quickly) 2.CORPORATE GROUP (C/Vsgrouped together by group key if belong to a corp. group. 3. ACCOUNTINGCLERK(ID of responsible). You can create a new C/V with reference toan existing another.

Avoiding Master Data Duplication: Two ways when creating a new customer: 1.Before creating a new MR, use matchcode to check whether C/V already exists. 2. The message

control should create a message when creating a C/V again.

@ Groups for C/Vs: useful to control: 1. Number ranges for @s so that all@s in an @ group are in one @ number interval . 2. FST in the MRs so that all @s in an @group have same screen layout. 3. If @ is a one-time C/V. In contrast to GL @s, where userenters @ group in CA segment of MR, for C/V @s enter @ group before maintaining individual

MR segments. Reason: For C/V @s, the @ group controls the internal or external # assignment.

For G/L @s, the # assignment is always external. In addition to CC segment, sales segment, and

purchasing segment, the @ group also controls screen layout at client level.

# ranges for C/V: separate for C/V and divided into smaller # ranges(int. and ext).

FST of the MRs: @ Group is used to control the fields in the MR.Factors that affect the C/V data screen: 1. @ group-specific control: Onegroup controls the FST of all its @s. 2. Transaction-specific control: FSTcan be dependant on the master data transaction (create, change, display). 3.CC-specific control: in CC segment of the C/V MRs via the CC-specific screenlayout. Applies FST priority.

Dual Control Principle: one user makes changes to a C/V and anotherconfirms them. Dual control is defined in the MR and can apply for asingle CV or a list restricted by C/V CC - @s not yet confirmed - @ rejected -@accounts to be confirmed by me.

C/V clearing: if a person is both vendor and customer, payment anddunning programs clear open items against each other. Steps: 1. Enter V @number in the Customer @ and vice versa. 2. Select field clearing with V/C inthe C/V @ correspondent.

4


5/52

Alternative payer/payee: Can be entered at client and CC levels.individual entries indicator makes this possible. Payer/payee may be a C/Valready created in the sys (entering C/V @ number as permitted payer/payeein the MRs) or been entered when creating the invoice. Definition options foralternative payer/alternative payee:

Priority Type Basic Setting at...

1 At doc level: 1.Individually (no MR exists), 2. Selection list (MRs exist) Client level

2 At CC level CC level

3 At client level Client level

Head Office/Branch: Items posted to a branch @ are automaticallyposted to the head office @.

Lesson 3: Bank Accounts

Bank Master Data: for house banks or C/V banks. Every bank is ID bythe bank country and bank key. Bank MRs contain data as SWIFT code, bankgroup and postal giro data. House Bank: Bank Master Data, electronicpayment info, Bank @s, GL @s per Bank @s. 4 ways of creating BankMaster Data: 1. Entering bank info in C/V MRs or in customizing for House

Banks. 2. Create Bank transaction in the @R and @P MD menu. 3.Imported. 4. Lockbox function. Bank Type: To distinguish between diff.banks. Partner Bank field: when processing invoices and the C/V hasmore than one Bank.

Bank Accounts: each bank @is reflected in sys as combination ofHouse bank ID + @ ID that is entered in a GL @ that represents the Bank@ in the GL. Bank @s can be ID by and @ ID unique per House Bank. Bank@ data contains: 1. @ number at the bank. 2. @ currency. 3. GL @. OneBank @= one GL @= ID @= same currency.

UNIT 3: DOCUMENT CONTROLLesson 1: Document Structure

Doc principle: a doc is saved for every BT posting and remains as complete

unit in sys until archived. Every doc is uniquely ID by: 1. Doc number. 2. CC. 3.FY. Parts of Doc: 1. Header (info applies to entire doc). 2. Doc items (info applies toline item). 3. Detailed Data for 1 and 2. Control Keys: 1. Doc type for doc header.2. PK for line item. Doc # can be assigned int. or ext. A BT can create 1 or moredocs linked to each other to have overview of every BT.

Doc types: ctrls doc header and is used to differentiate BTs to be posted.Doc types are defined at client level so valid for all CCs. Doc types define:1. ranges for doc #s. 2. @ type permitted for posting. 3. FST of doc header fieldsdoc header text and ref. #. 4. Whether invoices are posted with the netprocedure. If doc has ext. #: 1. Use ext. # in field reference # in header. 2. Notethe # of the sys # in the original doc. Options for int. doc # assignment: 1. Up to afuture FY. 2. For each FY. One # range can be assigned to several doc types.

Intervals of doc # ranges can be copied from one FY/CC to another.

Functions of the PKs: within the line items: 1. Types of @ line item can beposted to (D, K, S, A, M). 2. If item is posted as Debit or Credit. 3. FST of additionaldetails (layout of entry screens). PKs are defined at client level. PKs alsospecifies: 1. if line item is connected to a payment transaction. 2. If the PK is salesrelevant and if the sales figure if the @ is to be updated by transaction. PKs areposted D or C. PKs default values: 1. GL @ posting: D=40 C=50. 2. CustomerInvoices: D=01 C=50. 3. Vendor invoices: D=40 C=31.

Doc FST:defines whether fields are to be hidden, required or optional fields. However, this does

not apply for fields: 1. .Amount. 2. PK. 3. @ which are required entry fields, you cannot influence their

FST. FST for posting an accounting doc is determined by three factors: 1. @ type (for example, G/L @,

SL @). 2. FST of the PK. 3. FST of the @. Sys determines the FST dependent on the @ type. It cannot

be influenced by Customizing. The PK-specific and @-specific FST both control the field layout of theadditional @ assignments in the line item.

5


6/52

FST Groups: for each group of GL @s define the status of every doc entryfields. Info is divided into FST groups for each group of GL @s and summarized inone FST variant assigned to the CC. This is so that the FST groups can be used in the @s ofthese CCs. Different CCs can use one FST V.

Standard PKs: Since SL @s dont have FST group, differentiation via PKs. In

GL postings, differentiation is via FST groups (only 2 PKs are needed for GLpostings: 40 and 50).Lesson 2: Posting Periods (PP)

PPs: defined in the FY variant. PP can be closed to prevent docs from beingposted to the incorrect period. OPEN a PP by entering a range in the PP variant.Special periods can be opened furing period closing for closing postings. Duringclosing, two period intervals must be open at the same time. PP Variant: can beused by several CCs.

Period checks by @ type: PP variant must contain at least @ type +. PPscan be handled differently for diff. @ types (K, D, S, M). At line item level, syschecks if PP assigned is open to permit postings. Determination of PP duringposting: When entering a doc posting date, sys determines PP and FY based on that

date. PP is entered in doc overview and transaction figures for this posting areupdated.Lesson 3: Posting Authorizations

Maximum amounts: defined per CC in tolerance groups. This is also wherethe processing of PDs is controlled. Upper limits for posting transactions in: 1. Totalamount x doc. 2. Amount x C/V item. 3. Cash discount granted.Lesson 4: Simple Documents in Financial Accounting

Simple Posting in FI: FI uses one posting transaction for several differentpostings: GL @s, Customer invoice posting, Customer credit memo posting, Vendorinvoice posting, Vendor credit memo posting.

ENJOY Posting Screen:in the GL, C/V area are single screen transactions. Header and

first line item: Enter Gral data for posting doc: invoice, posting date, text, etc.Define a doc type for each transaction. Additional Line items: Once made andconfirm entries, @ name appears. Once balance is 0, select PARK, POST or HOLD tocomplete doc entry transaction.

UNIT 4: POSTING CONTROLLesson 1: Default Values

Default values for user settings: Configure screens for areas: 1. Doc entry. 2.Doc display (using list view). 3. Open Items (layout display and posting options).

Sys. and Accounting defaults: Sys provides defaults for doc entry. DocPrinciple: Balance of doc must be 0 before posted . Doc types, PKs, FYs all canbe proposed by sys.

Lesson 2: Change Control

Changing Docs: that have been posted is possible only in certain fields.(based on rules). 1. Doc Header: a. Ref #. b. Text fields. 2. Line Item: Notchanges in a. amount. b. PK. c. @ d. any field that would affect the reconciliationof a posting.

Doc change rules: based on: 1. @ type: AR, AP or GL @ (M,K,D,S,A). 2. TransactionClass: for SGLTs (bills of exchange and down payment). 3. CC: if field is blank, rulesapply to every CC. Change conditions for changing a field (line item) if: 1. PPis still open (also applies for doc header). 2. Line item is not yet cleared. 3. Line itemis either a debit in a customer @ or a credit in vendor @. 4. Doc is not credit memofor an invoice. 5. doc is not credit memo from a down payment.

Lesson 3: Document Reversal

6


7/52

Reverse Docs: 2 ways of reversing: 1. Normal (standard) reversalposting: causes sys to post the incorrect debit as credit and the incorrect creditas debit. The normal reversal posting causes an additional increase in thetransaction figures. 2. Negative posting: also posts the incorrect debit as creditand the incorrect credit as debit. This time the posted amount is not added to thetransaction figures of the other side of the @, setting transaction figures back toas they were before the incorrect posting took place. Prerequisites to enablenegative postings: 1. CC permits negative postings. 2. Reversal reason must bedefined (explains the reversal and allows to use or not the same posting date).Negative postings are also to perform transfer postings of incorrect lineitems. During the reversal, a reversal doc is created. The reversal doc and the reversed doc are thencleared items. In the doc header of the reversed doc you can see the number of the reversal doc and

the reversal reason. The doc header of the reversal doc contains the number of the reversed doc but

not the reversal reason. Mass reversal: With recurring entries or with the PYMT program, a large

number of docs are created automatically. Using the mass reversal function, these can be reversed

simultaneously.

Lesson 4: Payment Terms and Cash Discounts

Terms of Payment (TofP): conditions agreed between business partners forthe payment of invoices. TofP are used to define: 1. Baseline date for due datecalculation. 2. Cash discount periods/terms. 3. Cash discount % rate. TofP areassigned to C/V MRs, defaulted in sys or entered by user, and used intransaction line item to determine payment conditions.

TofP in Invoices: TofP can be entered in the C/V MR: 1.CC segment (defaultedif invoice created in FI). 2. Sales area segment (defaulted if invoice created in SD).3. Purchasing organization segment (defaulted if invoice created in PM). Whenentering an invoice its possible to enter a fixed cash amount or adiscount % rate. (entry in cash discount field).

TofP in credit memos:Linked from original invoice by entering invoice # ininvoice ref. field in doc entry. TofP are copied from invoice, so invoice and credit

memo have same due date. In Non-Invoice related credit memos TofP are invalid.

TofP basic data: 1. Day limit: Calendar day to which the TofP are valid.Store a single or multi-part TofP in a TofP Key. 2. Description (1. Sales ordermanagement text for printing on invoices, 2. An explanation if necessary, 3. An explanation generated

by the sys) 3. @ Type: Subledger in which TofP can be used.

TofP controls:1. Block Keys (line item, @, or payment terms) to blockpayment or collection (enter block key and the PYMT method: 1. During posting. 2. In the C/V MR(CC segment). 3. In the TofP). 2. Payment Method: (for country): line item, @, orpayment terms. The PYMT method is generally entered in the C/V MR and not in the doc.

Baseline date:Starting date sys uses to calculate invoice due date. Rules ofcalculation: 1. default values: No default, doc date, posting date, entry date. 2.

Specifications for calculating the baseline date: Fixed date (use to overwrite thecalendar day of the baseline date). 3. # of months to be added to the calendarmonth of the same baseline month. Fixed day = fixed calendar day to which the first or secondcash discount terms apply or when net due date is reached. Additional months = Number of months to

be added to the baseline date to determine the end of the 1. or 2. cash discount terms or the net due date.

Cash discount: calculate: enter % rate in TofP and the 3 of days the % isvalid for the same line (possible to add fixed days and months). Days and Monthsin TofP+ Baseline date+ %= cash discount amount.

Day Limit: enables day-specific TofP in one TofP key. Several versions of TofPhaving each version a diff day limit. Day limit is the baseline date to whichthe term version applies. Two-part TofP under the same TofP key is possiblewhen the TofP are dependant on whether the baseline is before or after an

specific day of the month. TofP that require day limit: 1. Doc with invoice date up

7


8/52

to 15th of the month are payable on the last day of the following month. 2. Docswith later invoice date are payable 15th of the month after.

Installment Payments: Invoice paid over several months. One due date perpartial amount. If installment payment is defined, sys splits automatically (do notdefine cash discount periods or %). Elements: 1. installment #. 2. % rate. 3.TofP for each installment (line item per each installment).

Cash discount base amount: 1. Gross (tax): when open items are cleared,cash discount goes to an @ for cash discount expense/received(expense/revenue @s are not reduced). 2. Net (no tax): Expense/revenue @s arereduced. Theres a cash discount clearing @ and also a lost cash discount ifpayment done after cash discount deadline.

Lesson 5: Taxes

Taxes are levied in invoice amount as: 1. Tax on sales/purchases. 2. US salestax. 3. Additional Taxes (country-specific). 4. Withholding tax. Taxation types: 1.Fed/country level. 2. State/jurisdiction level.

Tax support: 1. Calculate tax amount. 2. Posting amount to define tax @s. 3.

Performing tax adjustments for discounts and deductions. 4. Tax reporting. Baseamount: expense or revenue amount (with or without discount). Gross tax base =Includes cash discount, Net tax base = Does not include cash discount. Tax code: required toperform tax functions. 1+2=tax amount (which can be gross or net depending onthe CC or jurisdiction code).

Tax on sales and purchases: Balance of output tax (to net value of goods andbilled to customer. Liability of company to tax authorities) and input tax (to netinvoice amount and billed to vendor. Receivable company claims to tax authorities).

US tax on sales and purchases: Collected by vendor on a sale and remittedto jurisdiction of the customer. Use tax: on customer if previous condition didntoccur.

Tax calculation procedure:Assigned to every country: 1. Steps. 2. Taxtypes (condition types) that apply for the country (rules for calculating tax). 3. @

key/transaction key: This is used for posting to the correct tax @s (automatic @ determination). The@ keys also create the tax items during posting. The calculation procedures are defined in sys and user

does not have to maintain them. Tax rates are assigned to the tax types that are used in the tax calculation

procedure.

Jurisd. code: State, County, City, District. 2 steps: 1. define length ofindividual elements of the code for the format jurisdiction code. 2. define it forevery level.

Tax code: enterede when posting the doc and main connection to taxcalculation. Tax code is linked with: 1. Country key. 2. Combination of country keyand tax jurisdiction code. Tax code is used for: 1. Verify amount of tax. 2. Calculate

amount of tax. 3. Calculate additional tax portion. 4. Verify tax type. 5. DetermineGL @. 6. Show tax correctly on tax forms.

Tax rates: Contained in tax codes. Assigned to the tax types used in taxcalculation procedure. 1. Tax code may have several tax rates for diff. tax types.Tax rate 0 applies. Tax type definition determines if the base amount is percentageincluded or percentage separate.

Tax postings: 2 cases: 1. As separate line item (standard) to a special tax @.2. tax with certain transaction/@ keys are distributed to relevant expense/revenueitem (non deductible input taxes).

Tax @ determination:can be automatic by assigning data to theaccount/transaction keys: 1. Posting key (40-50) 2. Rules determining fields

the @ determination is based on (e.g. tax code or account key). 3. Tax @s.

8


9/52

Tax @s:to which tax items are posted. Defined in the tax category byentering: 1. < for input tax. 2. > for output tax. (tax code can define it).

Other GL @s:blank for non tax-relevant postings. - postings that requirean input tax code. +postings that require an output tax code. * any tax code.xx with a xx predefined tax code. If posting without tax allowed field is

selected, GL @s can be posted without any tax code.

Lesson 6: Cross-Company Code Transactions (CCCT)

1 or more CCs in one BT (1 pays, buys or sells for/to another).Process flow:1. A CCCT posts to @s in several CCs (1 doc for each CC). 2. Sys createsseveral offsetting docs to balance C and D in the doc. Sys generates automatic lineitems which are posted to Clearing @s for payables and receivables. 3. All docs arelinked by a common CCCT number. Taxes are not distributed among CCs.

Clearing @s: defined in every CC before a CCCT. @ may be GL or C/V @.Assign clearing @ to every possible combination of CCs. Use one CC as theclearing CC so every CC assign clearing @ to that one. PKs must be assigned tothe Clearing @s to identify account types. CCCT doc #: CC doc that links all docs

together: combination of doc # of the first CC, the first CC # and the FY. Can bereversed.

UNIT 5: CLEARINGLesson 1: Clearing Open Items.

Open Items are incomplete transactions such as invoices not paid. For atransaction to be completed, it must me cleared (clearing postings have beencarried out for item or group of items so balance = 0). Docs with open items cantbe archived. A clearing transaction always creates a clearing doc.There are twoways to clear open items: 1. @ clearing (subsequent). 2. Posting with clearing (during posting).

Posting with Clearing (PWC): invoice is posted to a customer @, customer

pays and payment is assigned to an open item, the invoice is cleared with thepayment and balance=0. Procedure: 1. enter the clearing doc amount. 2. selectopen items to be cleared. 3. clearing amount is assigned automatically. 4. If total

9


10/52

amount of selected items = total amount of clearing doc, sys clears open items bycreating clearing items. If total amount of selected items total amount ofclearing doc, sys allows to post the difference. PWC can be done for several @s, @types and any currency simultaneously. It can be manual or automatic. Account Clearing: e.g.: clearing an open invoice with a related credit memo andpayment on @. Procedure: choose open items from an @ that balance=0. Sys

marks them as cleared and creates a clearing doc which number and date areentered in the clearing item. Date can be current or determined by user. Accountclearing works for any @ managed with open items in GL or SL. To Clear itemswithin an @ not always is necessary to carry out postings. It can be manual orautomatic. Manual clearing takes place, for example, in the following cases: 1.For bank sub@sand clearing @s, 2. For debit memo procedures. 3. If a vendor makes a rePYMT.

Automatic Payment Program (to clear open items for GL and SL @s): Itgroups items for an @ together when they have the same entries in: 1Reconciliation @ #. 2. Currency. 3. SGL indicator. 4. Five free defined criteria fromdoc header or line item. If balance in local currency=0 sys clears automatically andcreates clearing docs. Prerequisites: Customizing defines: 1. @ to be cleared. 2.define user criteria. Steps: 1. Groups items. 2. If balance=0, clears. Program does

not clear: 1. noted items. 2. statistical postings, bills of exchange postings. 3.items with withholding tax entries.

Assignment field as sort field: Sort+ field entry in MR when posting(combination of up to 4 fields max 18 characters). Can be used to trace docsbetween FI and other components.

Lesson 2: Incoming and Outgoing payments

Manual Payment Process: transaction that clears an open item (typically andinvoice), by manually assigning a clearing doc. INCOMING PAYMENT (AR): clearsan open debit @. OUTGOING PAYMENT (AP): clears an open credit @. Threesteps:

1. Data is entered in doc header: a. Payment header: 1. doc date. 2. Doc

type. 3. CC. 4. Posting date and PP. 5. Currency code, T, date of currencytranslation 6. Ref. doc #, doc header text, clearing text. b. Bank Data: 1. @ (GLfor incoming or outgoing payments). 2. Payment amount. 3. Bank charges. 4. Valuedate (date on which the actual cash movement takes place -to evaluate position incash management). 5. Text (description). 6. Assignment #. c. Select Open Items:1. @ and @ type. 2. Normal open items and/or SGLTs. 3. Payment advice note #. 4.Other @s (to process their open items at the same time).

2. Process Open Items:a. Activate line items to assign a payment:amount entered is assigned to the line item and their cash discount. Options: 1.Selection of editing options for open items. 2. Double click on the amount. 3.Selection form action menus and function keys. If amount entered=amountassigned posting the doc is possible. b. Activate cash discount: determined by

TofP of line item. Discount is used to calculate assigned amount and is can bechanged (tolerances).

3. Post: a. Display overview. b. Simulate to reveal automaticgenerated items. C. Correct mistakes. d. Post (if D and C agree).

Automatic Postings for clearing open items: Can be carried out for: 1. Cashdiscount expense or revenue. 2. Cash discount clearing (net procedure) 3. Taxadjustments. 4. T differences. 5. Bank charges. 6. Clearing fro CCC payments. 7.Over or under payments with tolerances.

Resetting Clearing: for individual docs when line items cleared in error.

Lesson 3: Payment Differences (PD)

If PYMT differences occur they may be handled either automatically or manually. 1. Automaticclearing: If the PYMT difference is small, it can be dealt with automatically: 1.By adjusting the cash

10


11/52

discount. 2. By writing off the difference to a special @. The limits up to which a difference is considered

to be immaterial are defined in tolerance groups. 2. Manual clearing: If the PYMT difference is too high

to be immaterial, it must be processed manually: 1. By manually adjusting the cash discount. 2. By

posting the PYMT as a partial PYMT. 3. By posting the PYMT difference as a residual item. 3. By

posting the PYMT difference as a difference posting.

Tolerance Groups (TG): 3 types: 1. Employee (assign to

user Mater data): type of employee hierarchy (a. upper limits. b.permitted PDs). 2. GL @s (assign to MRs): clearing @s for externalprocurement or for in-house production (permitted PDs). 3. C/V @s(assign to MRs): good, not so good, cash only (a. Default values forclearing transactions. b. Permitted PDs. c. Specification for postingresidual items from PDs. d. Tolerance for payment advice notices).Two steps to use TGs: 1. Group definition: a. TG is defined by agroup key, CC and currency code. b. Group key 4-characteralphanumeric key. C. blank is standard TG: minimum. 2. GroupAssignment: a. Employees. b. GL MRs. c. C/V MRs. d. default blankvalue.

Permitted PD: can be found in both types of TGs. Control de

automatic posting ofcash discount adjustments andunauthorized customer deductions.

PD: Normally during clearing of an open item. Diff. is compareto TGs and handled accordingly: Within tolerances: automaticallyposted as either cash discount or unauthorized deduction. Outsidetolerances: processed manually.

Processing PDs: If diff. is immaterial (limit defined in TG),processed automatically by allowing sys to adjust cash discount up tocertain amounts or to write it off to a special @. If diff is too high to beimmaterial, processed manually. Payment can be posted as follows: 1.Partial payment (all docs remain open). 2. PD may be posted as aresidual item (only residual items remain in the @ and open). 3. PD

can be posted to an account assigned to a reason code or written offby manually entering a new posting item. 4. Payment on account(write off the diff.).

Partial and residual payment: C/V TGs contain entries tocontrol residual items that specify: 1. TofP for residual items are thesame as the cleared items or are fixed. 2. Cash discount is grantedpartially or not for the whole amount. 3. By using a dunning key, ifresidual item has a max. dunning level or is printed separately.

Reason codes: to describe reason for the PD. distribute diff.can be used to assign more than one reason code to a PD. Reasoncodes can be assigned to: 1. Difference postings. 2. Partial payments.3. Residual items. Optional functions: 1. Ctrl type of payment noticesent to customer. 2. Ctrl @ where a residual item is posted. 3.Automatic posting of a residual item to a specified GL @. 4. Exclusionof residual items from credit limits checks because they are disputed.

Lesson 4: Exchange Rate (T) Differences (TDs)

Realized TDs: due to fluctuations, when claring open items inforeign currency. Sys posts TDs automatically and realizes gainsor losses to revenue/expenses @s. the realized TDs is stored inthe cleared line item. TDs are also posted when open items arevaluated for FS to another TDs @ and to a FS adjustment @.

@ Determination: All Recon. and GL @s with open item

transactions in foreign currency must be assignedrevenue/expense @s for realized losses or gains. One gain/losscan be assigned to: 1. All currencies and currency types. 2.

11


12/52

Per currency and currency type. 3. Per currency. 4. Percurrency type.

UNIT 6: CASH JOURNALLesson 1: Cash Journal (CJ) Configuration

What is the cash journal and what can you do with it? 1. Tool for managing cash. 2. Supports

posting cash receipts and expenses. 3. Create a separate cash journal for each currency. 4. Make postings

to G/L, customer, and vendor @s. 5. A CC can have several cash journals. 6. A cash journal has a 4 digit

alphanumeric key

CJ Assignment:CJ is tool for managing cash, which supports cash receiptsand payments. Functions: 1. Create a separate CJ for each currency. 2. Post to C/Vand GL @s. 3. Run several CJs in each CC. 4. Choose a number for CJ ID (4.-digitalphanumeric key).

Setting up the CJ:enter values in: 1. CC. 2. 4-digit CJ ID code. 3. GL @s towhich you want to post the CJ BTs. 4. Currency. 5. Doc types for: a. GL @spostings. b. Outgoing payments to Vs. c. Outgoing payments to Cs. d. Incomingpayments from Vs. Incoming payments from Cs.

BT types:1. Expense (E): Expense/cash desk. 2. Revenue (R): Cash deskrevenue. 3. Cash Transfer from CJ to Bank (B): Bank/cash desk. 4. CashTransfer from Bank to CJ (C): Cash/Desk Bank. 5. AR (D): Customer paymentreceipt cash office/customer and Customer outgoing payment customer/cash office.6. AP (K): Vendor payment issue Vendor/cash office and Vendor incoming paymentCJ/Vendor.

Creating BTs: can define them in two places: 1. CJ itself2. IMG. Settings tocreate a BT:1. CC in which BT should be created. 2. Type of BT. 3. Tax codes forthe BT E and R. 4. For BTs E, R, B and C: set indicator to enable the GL @ for the BTto be changed when the doc in entered. GL @ is only a default value in this case. 5.For BTs E and R: indicator to enable tax code to be changed when doc is entered. 6.Once saved, BT is assigned a code automatically. 7. Set and block indicator for

further postings.

Lesson 2: Cash Journal (CJ) Transactions

Posting BTs in the CJ: CJ is one of the ENJOY BTs that can be processed in asingle screen (enter, display and change CJ entries). CJ entries can be saved locallyin the CJ SL and can be copied or deleted. Saved CJ entries are posted to the GL atthe end of working day for example.

CJ doc with doc split: A CJ can contain several items with diff. tax codesand/or @ assignments relevant to cost @s. When the CJ doc is forwarded to FI, onlyone accounting doc is therefore created.

CJ docs with One-Time account: In CJ you can create a BT linked to a one-

time @. If you use a one time @ in the CJ, the dialog box for entering the one timedata is called automatically and the entries saved in the CJ.

12


13/52

UNIT 7: SPECIAL G/L ACCOUNTS

Lesson 1: Application Area for SGL Transactions What are Reconciliation @s (R@)?: Transactions in the SLs (e.g. AR-AP) arealso posted in R@s in GL to have the values available in form of totals as well as inthe GL to quickly create a financial/income statement. To determinepayables/receivables, the balance of the R@ can be directly displayed instead ofsearching for the values in the SL. R@ to be posted is entered in the C/V MR. R@field: CC segment of C/V MR.

Posting in the SL: @ # of the R@ posted can be seen on the FI doc.Transaction figures are updated on the R@ in concern.

SGLTs-Alternative R@: are @s in the AR and AP that are displayed separatelyin the GL and the SLs. Transactions in the SL are linked to the GL by RA defined in

the SL MR. If SL @ assignments are made using a SGLindicator, postings areperformed on alternative RA (SGL@s) to display these transactions separately.

3 SGLclasses: 1. Down Payment (DP): requested, received and used. DPprocess is integrated to the dunning and payment programs. Bills of Exchange(BofE): In order to deal with country-specific particularities. 3. Other transactions:other option in doc entry menu in AR and AP.

3 SGLtypes: or ways of transferring SGL entries to sys. Configured in the SGLindicators.

1. Automatic offsetting entries (statistical): transactions always posted onthe same offsetting @. Usually included in the notes of FS. The @# is defined incustomizing and entries are made automatically to the @. Clear the open items inthe respective @ makes the sys clear the open items in the offsetting @. These

transactions are called statistical postings since are not displayed in FS but innotes.

2. Noted items: individual @ assignments only used to remind the respectivedepartment of due payments of payments to be made and are not intended to bedisplayed in GL. Only one line item is updated if a noted item is created and nooffsetting entry is made. No zero balance check is made. Payment and dunningprograms can access noted items for further processing. Noted items areadministrated as open items in the AP/AR and the SGL@. Line item display must beactivated. No transaction figures are updated when entering noted items.Items can be found on the line item list but do not affect the displayedbalance of the customer. SGL@s posted to also always display balancezero.

3. Free offsetting entries: Postings are part of the FS with freely definableoffsetting entries.

DP in the Customer area: Procedure: 1. DP request: are noted items. Do notchange any account balance. Its possible to automatically issue dunning noticesand make payments. 2. DP received: displayed as payable in accounts. They maynot change the balance of the receivables RA. Received DPs are administrated inthe DP received alternative R@ in the payables area on the FS. 3. Customerinvoice: Customer receives an invoice whenever good or services are supplied. 4.Posting a DP clearing with invoice: at this point, DO is not longer a DP. Amount mustbe displayed as payment on the normal RA. 5. Clearing: of items during payment ofcustomers balance. 6. Individual Value Adjustment (IVA): another SGLT. Disputed ordoubtful receivables are entered as IVA when preparing the balance statements for

year-end closing. The transaction is entered in the customer @ and in the SGL@.

13


14/52

IVA for receivables: Procedure: 1. Receivable is entered in the customer @.2. IVA without tax is entered. Expenses are now in the right place in the expensesfor IVA @ for the income statement reporting. 3. IVA is cleared after the key datefor the balance sheet, meaning it is reversed. 4. Final value adjustment is madeafter asserting that the receivable in uncollectible. In this case, the expenses foruncollectible receivables @ is posted to. No SGLaccount is used sinceadjustment postings must be made on regular C RA.

Guarantees of Payment-customer (guarantees of payment made): Companytakes over a guarantee of payment for certain amount. Transaction is displayed inon the @of the customer and on a SGL@. Guarantees made are displayed in the FSnotes. Guarantees of payment are stored in SAP as transactions with automaticoffsetting entries.

Guarantees of Payment-vendor (received guarantees of payment): vendormakes the guarantee for company.

Bills of exchange (optional): a type of short-term financing treated as a SGLT.Transactions are automatically recorded in the SL separately from othertransactions and posted to a SGL@. BofE can be seen at any time. Receivable and

payable BofEs can be posted as well as incoming and outgoing checks. Procedure:1. Receivable is enetered in the customer @. 2. Customer initiates payment with aBofE. @ balance is now registered as a receivable BofE and not as a normal balanceof AR. 3. Bank collects money from @ of the customer on a fixed date. 4. Collectedamount is transferred to the companys @. 5. Amount is posted to the @ of thecustomer and the respective accounts cleared.

Lesson 2: Configuration of SGLTs

Basic settings for SGLT:1. PKs: SGLT are posted from the application sideby means of special PKs (09,19,29,39) and using SGL indicators that indicate PK isbeing used to enter SGLTs. 2. Outsorting of the alternative R@. SGLT areposted to an @stored in customizing and not to the R@ stored in the MR. These @s

must be created in FI and outsorted according to requirements. SGL @s are definedas R@s for the D and K @ types (always line item display activated).

Configuration of SGLT:Properties and @ determination: in SGLT possibleto make changes in: 1. Diff. @ # for R@ or SGL @s. 2. Other PKs or GL indicators forindividual transactions. 3. Other settings for automatic postings (accounts to beposted to, PKs, rules of @ assignment). SGL indicator: determines the type oftransaction and the @ type. In properties determine the characteristics of SGL @sin connection with the @ type: a. Noted Items: can determine that the SGLT doesnot update any @ balance. b. Relevance to credit limit check: can include SGLTinthe credit limit check for customers. c. Warning against commitments: candetermine that the user get a warning about SGLT existence when posting to C/V@s. d. Target SGL indicator: for noted items. For line items, set which SGL indicatorsare allowed to be added as target SGL indicators when entering (applying) apayment request. The target SGL indicator is used in the standard sys for DPrequests. e. SGLT class: determines types of transaction. F. PK. The alternative SGL@ is stored separately in the account determination according to the CA. sysproceeds form the R@ found in the C/V MR and assigns it when posting the SGL @assigned to this R@ in the account determination.

Automatic Statistical offsetting entries: statistical postings are always madeon the same offsetting @. The @ is stored in the basis of a combination of the @type (C/V) and the SGL indicator used.

Setting up the SGLT:1. Noted Items: No transaction figures updated. Nooffsetting @. Only a reminder on the C/V @. 2. statistical items with automaticoffsetting entries: a. stores an alternative SGL @ (alternative RA) and a clearing

@. 3. Transactions with manual offsetting entry: Alternative GL @ should bestored for the selected SGL indicator. The offsetting @ is entered manually duringtransaction.

14


15/52

UNIT 8: PARKING DOCUMENTSLesson 1: Basics of Document Parking vs Hold Document

Holding/parking docs: docs cannot be saved or posted if they arentcomplete.

Scenarios for entering docs: 2 ways of saving docs without posting:

1. Holding: entered data can be saved temporarily to continue the entries atlater time. Held docs dont have to be complete. 1. No @ balances are updated(no update of transaction figures). 2. Doc data is not available forevaluation. 3. No doc # is assigned. Doc is named to be found later. 4. Freeassignment of the designation/ID. 5. No used in evaluations/reports. Helddocs can be completed and posted or deleted later.

2. Parking: 1. Enter complete doc # via doc type as normal. User mustpass on # if assigned externally.2. Park docs can be supplemented, checkedand post by diff. operator(principle of dual control)3. Displaying

authorizations/approval. 4. No data updated when parking docs (trans.figures). 5. Data is available for evaluations/reports. 6. Responsibility. 7.Acceleration of work procedures. Park doc function is available for conventionalposting and ENJOY posting mask. Park docs can be completed, changed,posted or deleted. NoSubstitutions only until the park doc is turned into anaccounting doc.

Lesson 2: Parking Documents and Processing Park Documents

Enter and store incomplete docs without having to check entries.

Alternatively its possible to check park docs for their completeness.

@ assignment templates can be used but not reference docs.

CCCT can also be parked.

Transaction figures, asset values, are not updated.

No automatic postings are created.

Balance is not checked.

Areas of application of doc parking: 1. Temporary storage of input values. 2.Displaying multi-level models. 3. Work assignment by means of work lists.

Ways of using doc parking: 1. Customer @ (invoices and credit memos). 2.Vendor @ (invoices and credit memos). 3. GL @s (GL @ postings).

Processing: further processing of park docs by: 1. editing park doc andposting them (deleted in exceptions). 2. Displaying parked docs in the sys.(individually or list).

15


16/52

Editing parked docs:Header and line items can be edited, includingamounts. Doc change rules for normal docs do not apply for parking docs. NOTCHANGE: currency, CC and doc type/number. MAY CHANGE: Dates, amounts, @sand @ assignment objects. Changes can be displayed before or after posting.

Posting Parked Docs: as standard transaction individually or by list: direct

posting or batch input. When a park doc is turn into a proper doc: 1. Usualinspections are performed when posting a doc. 2. A normal complete FI doc iscreated. 3. History is documented. 4. Doc number remains the same. 5. Transactionfigures are updated. 6. Park doc is deleted after creating a FI doc.

Doc parking reporting and overview: Doc parking is linked to @ display andreporting FI functions. Can be included in doc journal and be viewed in line itemdisplay.

Lesson 3: Doc Parking and Workflow

Workflow: providing employees with right tasks and respective info atright time.

SAP Business Workflow: four process dimensions: 1. Organizationalstructure (who). 2. Process structure (when, in what order, under whatcircumstances?). 3. Function (what). 4. Information (with which data).Using a graphic definition tool, process to be display as a workflow can bestored in the sys. SAP BW: 1. tool for the automation of business processesin SAP sys and between sys. 2. Not tied to a particular application and canbe adapted to customer requirements. 3. Works the same way in allapplications. 4. Coordinates all integrated tasks. 5. Supports user actively.

Workflow management architecture: 3 layers (flexibility): 1. the rightwork. 2. at the right point of time. 3. to the right processor. Workflow areusually initiated by a triggering event.

Tasks related to the workflow: 1. Posting invoices. 2. Changing

material masters. 3. Realizing purchase requisitions. 4. Approving leave. 5.Creating customer @s. 6. Deleting purchase order. 7. Creating requirementrequest via internet.

Workflow and FI: workflow variants: can be crated for doc parking in customizingand assigned to CCs and no doc is released until this task is performed. The workflowV and the corresponding CCs must have the same currency.

Assigning workflow variants to CC: its possible to apply diff. releaseprocedures to diff. AR and AP. The Release Group field in these @scontrols it. Release group is required to determine Release ApprovalPath at the time of processing. The path is determined by the workflowvariant in connection with doc type and release group.

Calculation of Release Approval Path:Release procedure is

represented by Subwork flows. For doc parking, workflow variant +release approval paths are assigned amounts, which determine the releaseprocedure to be initiated and performed. Subwork flows control theindividual release procedures.

16


17/52

TFIN50I PART 2

UNIT 1: FUNDAMENTALSLesson 1: Customer/Vendor (C/V) Accounts

Master data: C/V data that remains unchanged and that is often referred toanother data.

FI view of the C/V @: C/V @s have two segments in the FI view: 1. At clientlevel: General data. Can be accessed throughout the whole organization. Data: a.address. b. Ctrl data. c. PYMT transactions. + texts. 2. At CC level: CC specificdata. Any CC, to do business with a certain C/V, has to create a CC segment for theC/V (a C/V @ is created). Data: a. @ management. b. PYMT transactions. c.Correspondence. d. Insurance. e. Withholding tax. + texts.

Pages of the C/V @.Important fields: 1. search term: abbreviation of C/Vname. 2. Corporate group. 3. Clerk/accounting: name and ID. 4. Explanatory texts: Anew C/V can be created with ref. to an existing MR.

AP/AR @ groups: when creating a C/V MR, enter @ group in initial screen. @group ctrls: 1. # of ranges of the @. 2. If @ is one-time C/V. 3. FST of in MRs.

Controlling the FST: Factors affect the C/V layout: 1. @ group-specific control:

FST is only control by @ group. 2. Transaction-specific ctrl: FST can be dependanton the master data transaction (create, change, display). 3. CC-specific ctrl: FST forfields in the CC segment for C/V MR can also be controlled by the CC dependentscreen layout.

Clearing C/V: if a customer is also a vendor, PYMT and dunning programs canclear open items against each other. Steps: 1. V @ must be entered in the C @and vice versa. 2. Each CC can decide separately if wants to do clearing.

Alternative Payer/payee: at CC level (1) and a client level (2). 1>2. Individualspecifications indicator: if alternative Pyr/Pye has not been created in SAP. If italready exists, enter C/V @ as permiteed Pyr/Pye in MRs.

Head/office branch: C place orders locally but pays centrally. Items posted to

branch are automatically transferred to head office @. Dunning can be an exceptionusing function descentral processing.

17


18/52

Lesson 2: Simple Docs in FI

FI docs in SAP: According to Doc principle: a doc is saved for every postingand each doc is uniquely ID by: 1. Number (int or ext). 2. CC. 3. FY.

Doc consists of: 1. Header: info applies to entire doc. 2. Line Item: Specificinfo

Doc ctrl keys: 1. Doc type: for the doc header. 2. PK: for line items.

Simple posting in FI: can be: 1. GL @ posting. 2. C/invoice posting 3. C/creditmemo posting. 4. V/invoice posting. 5. V/credit memo posting.

Header and first line item: Grl data for the posting doc (invoice, PK, postingdate, text).

Additional line items: table in the lower part of screen (@ name) select park,post, hold. If balance=0.

UNIT 2: AUTOMATIC PAYMENTSLesson 1: Payment Run- Overview

The PYMT process:Nat and Intl PYMT transactions with C/Vs and for

outgoing and incoming PYMTs. PYMT program allows: 1. select open invoices tobe paid or collected. 2. post PYMT docs. 3. print PYMT media.

4 steps:1. Setting parameters: a. what is to be paid. b. PYMT method. c.when. d. CC considered. e. How are they going to be paid? 2. Generating aproposal: list of open invoices and business partners that are due for PYMT.Invoices can be blocked for PYMT. 3. Scheduling the PYMT run: PYMT doc iscreated and GL and SL @s are updated. 4. Printing PYMT media.

Settings for the PYMT prog. are defined in 3 places: 1. In the MR for the business partner,

i.e.: bank details and PYMT methods. 2. In the items, i.e.: PYMT methods in the doc and terms of

PYMT. 3. In Customizing for the PYMT program.

Lesson 2: PYMT Program Configuration

Structure: Most settings can be accessed directly from USER. Categories(configuration areas): A. For all CCs define: 1. Inter-company PYMT relationship.2. CC that process PYMTs (paying CC that records Bank postings) on behalf ofsending CC (records SL postings). 3. Tolerance days for PYMT (grace days). 4. C/VSGLT to be made. 5. PYMT method supplements (to print sort PYMTs). 6. Cashdiscounts. B. For Paying CC define: 1. Minimum amounts for incoming andoutgoing PYMTs. 2. Forms of PYMT advice and EDI. 3. BofE specifications. C. ForPYMT method/ country define: 1. Methods of PYMT and for each method: 2.create a check, bank transfer, BofE, etc. 3. MRs requirements. 4. Doc types forposting and clearing. 5. Print program. 6. Permitted currencies. D. PYMT methodfor CC define: 1. Min. and Max. amounts. 2. Allowing or not foreign currecies,foreign C/V, PYMTs via C/Vs bank abroad. 3. Bank optimization (PYMT program paysfrom a bank within the same clearing house sys. 4. Postal Code optimization (PYMT

from a bank based on the C/V city of residence). 5. Forms of PYMT media in the formdata area. E. Bank selection define: 1. Ranking order: a. PYMT method. b. Housebank to be considered for PYMT. c. Currencies. d. BofE @ e. House bank identifier. 2.

18


19/52

Accounts and Amounts: a. Bank and Bank @. b. Days until de value date andclearing @ (for BofE). c. Currencies. d. Amount available in house bank for outgoingPYMTs. e. offset @ to the SL posting for each house bank and PYMT method. 3.Value date: for each combination of house bank and PYMT method: a. Used withcash management and forecast to track outflow of funds. b. # of days until valuedate plus posting date (value date= PYMT run posting date+ days until value date).

4. Bank Charges: a. Assess additional bank charges for incoming and outgoingPYMTs. b. Used with BofE. c. Additional automatic posting configuration: syssubtracts bank charges from clearing amounts for incoming PYMTs. For outgoingPYMTs, sys adds charges to clearing amount. Sys also posts bank charges to anexpense @ (requiring PK and @ assignment).Lesson 3: Running the PYMT Program- Individual Steps

Parameters: Define: 1. Whats to be paid. 2. PYMT method. 3. Date of PYMT.4. CCs considered. 5. How are they going to be paid. PYMT program is ID by twofields: 1. Run date: recommended as actual date when program is executed. IDs theprogram run. 2. ID field: to differentiate between programs with same date.

Open Item Selection: 1. docs to be included in the PYMT run. 2. CCs listed. 3.PYMT method (order important due to priorities).

Proposal run: Selects docs and @s with items pending for PYMT. Oncecomplete, two reports: 1. PYMT proposal list: business partners and amounts tobe paid or received with parameters, TofP and discounts. 2. Exception List: Itemsthat cant be paid (invoice blocked, invalid data in MR, invalid PYMT record or housebank, amount is


20/52

Forms of PYMT media: in configuration setting of the PYMT prog. assignPYMT medium forms either to each CC or to each PYMT method in a CC.

EDI (Electronic Data Interchange) and PYMT advice noted: EDI: sys choosesall PYMTs selected for EDI, creates a SAP doc for them and forward the to EDIsubsys converting docs into data to be sent to Bank. PYMT advice noted can be sent

by email or EDI. DME (Data Media Exchange): File with relevant PYMT info is createdaccording to bank rules. DME file is stored in data medium adm. DME can be usedin all PYMT methods in which medium is handled to bank for further process.Lesson 4: PYMT Medium Workbench

PMW is used to create PYMT media. Avantages: 1. Uniformity. 2. Formatscan be changed without modifications. 3. New formats can be created. 4. Alladvice notes output in one print file. 5. Better sort of options for advicenotes. Each PYMT method can be converted individually to PYMTmedia formats.

Lesson 5: Debit Balance Check

PYMT run could result in PYMTs made even if the @ has a debitbalance.

Lesson 6: Automating the PYMT Process

UNIT 3: AUTOMATIC DUNNINGLesson 1: Dunning (D)-Run Overview

D Overview: Parameters to specify how D program runs can use aprevious one and update dates for a new one. During D run, sys chooses @and checks them for overdue items, whether D notes have to be sent andwhich D should be assigned. All data is stored in a D proposal that can beedited, deleted or recreated. D notices are printed and D data updated in theMR associated docs.

Lesson 2: D Program Configuration D procedure: Every @ to be included in the automatic D has to have aD procedure (also one-time @s). Any # of D procedures can be defined forstandard or SGL @s.

Structure of the D program configuration:

A. Procedures: 1. Key for D procedure. 2. Description. 3. D intervals indays. 4. Minimum days in arreas (@) after which a D notice will be sent. 5.Grace periods per line item. 6. Interest calculation.

B. Levels: 1. Minumum # of days, referring to due date of netpayment, to reach a certain D level. 2. If Int is to be calculated. 3. Printparameters. 4. If D notice is printed although no further @ movements have

occurred.

20


21/52

C. Expenses/charges: defined for each currency and dependant on thelevel. Fixed amount or %. Set a minimum amount for D charges.

D. D texts: Name of form used in every level (payment advice notes,D notices, payment forms).

E. Environment: 1. CC data. 2. Sort fields. 3. Sender details. 4. D areas

(organizational entity). 5. D keys that determine if line item can be dunnedwith restrictions or display separately. 6. D block. 7. Interest. 8. D groupingto use separate D notice with a different text for each D level in an @.

Lesson 3: Parameters for the D Run.

Maintain Parameters: D program is ID by two fields: 1. Run date. 2.Identification (to ID between programs with same date). Parameters provide the Dprogram with info on the D run. Copying parameters is possible.

Open Item selection: For overdue items: 1. which CCs. 2. Which @s (range ofC/V @ or free selection). 3. Which Docs (docs posted to date or free selection)

Lesson 4: The D Run

Creates a D proposal that can be edited, deleted or recreated.

Steps: 1. @ selection. Criteria: D procedure entered in Master Data; Date oflast D run entered must be earlier than D interval of the D procedure. 2. D lineitems (levels). 3. D @s (checks whether payments have to be dunned for an @ andD level). D procedure entered as master data.

Due Dates for Receivables and Credit Memos:Receivables are due at thedue date for net payment. Usually Payment terms of a credit memo do not apply.Rules instead: if a CM refers to an invoice it has the same due date as the invoice.All other credit memos are due at the baseline date.

Clearing with Credit Memos and Vendor items: Due net credit items on the @

are cleared with the due net credit items. Applies also for vendor @ if clearingbetween C and V is chosen.

D dates: Due date: Day after which the liabilities must be paid. D date:Day when the overdue items are dunned. Every dunned item must be overduebut not all overdue items are due.

D blocks in item @:If item is overdue but @ has a D block in item, sys addsitem to blocked items list. Also a list of blocked @s.

Payment method in line item or @:If payment method for incomingpayments has been identified for an item, item is usually not dunned becausepayment program is responsible for collecting. Only dunned if has payment block.

D levels for line item (up to 9 levels): define content of D notice (formulation

in D text). Level is assigned to item according to the D arrears and no D levels canbe skipped. D procedures with 1 D level are Payment reminders.

D keys: by assigning them to certain items, prevent those items fromexceeding certain D level.

Minimum amounts per D level: Total amount of all items in an @ with certainD level must be > than a defined Minimum amount. The relationship between thetotal amount and the total open items must be >than a minimum %. If not, itemsare set to a lower D level.

D level in @: @ is assigned the highest D level of all items to be dunned andalso dunning text is worded according to highest level.

D requirements: @ is only dunned if conditions fulfilled: 1. Data has

changed since last D run. 2. Always Dun checkbox has been selected for the Dlevel. (last level and payment reminders). Different rule for @s in a legal dunningprocedure: if the start date of the legal procedure is entered in the @ master data,

21


22/52

the @ is always dunned if conditions are fulfilled: 1. Postings have been madesince last run. 2. The always dun in legal procedure indicator is selected. Inthis case no dun notices are sent.

Lesson 5: Editing the D Proposal

Editing the D proposal: list that can be printed: 1. D statistics. 2. D list. 3.

Blocked @s. 4. blocked line items. 5. D history.

Edit D data: possible to: 1. Block @ and remove block. 2. Block line item andremove. 3. Lower D level. 4. Change D correspondence date of an @ in MR. 5.Change Doc. 1, 2 and 3 apply for the current D proposal. 4 and 5 dont apply for thecurrent D proposal.ONLY CHANGES IN D PORPOSAL APPLY FOR THECURRENT D RUN.

Lesson 6: Printing D Notices

Scheduling Printing: Print Program does: 1. group items to be dunned with dnotice according to rules. 2. Generates a D notice for each group. 3. Enters the Ddate and level in the dunned items and @s.

Group Items in D notices: possible if items have same CC, D area and @.(Also possible one-time items if they have same address.

Special Grouping: 1. D by D level: separate D notice for each D level. 2.Grouping key: in C/V @ to group items in D notices with same values in the fieldsassigned. 3. Decentralized processing: head/office branch: items are posted tocentral @, Head office receives one D notice with all due items from its branchoffices. Or select decentralized process. CCC D is also possible to combineoverdue items from diff. companies in one D run.

D text ctrl: D recipient, D clerk or accounting clerk, D interest, paymentdeadline, standard texts available, all items, D charges, attach payment form.

UNIT 4: CORRESPONDENCELesson 1: Overview

Opportunities to create correspondence:1. Ad Hoc: 1. Doc creation. 2.Display/change line items. 3. Balance display. 4. Line Item processing. 5. Payment.2. Automatically: 1. Periodic Bank @ statements.2. BC.Correspondence can bedone periodically specifying interval in the C/V MR. Processing payments manuallyand from line item display creates correspondence online. ItsPossible toconfigure correspondence creation for certain postings.

Steps of creation:1. Request required correspondence. 2. Requesteedcorrespondence types are printed.

Lesson 2: Correspondence Types

User can generate correspondence directly from many screens in the sys (manual individual

request): 1. Doc creation. 2. Display/change line items. 3. Balance display. 4. Line item processing. 5.

PYMT. User can generate this correspondence automatically (collective request with selection program):

1. Periodic bank @ statements. 2. Balance confirmations.

22


23/52

How can user define correspondence in the sys? 1. Define periodic correspondence (for example,

bank @ statements) in the MR. 2. Request individual correspondence directly in the application (such as

for processing PYMTs manually or displaying line items). 3. In Customizing, for example, attach

correspondence to PYMT differences using reason codes.

Types represent a type of letter in the sys (one for each correspondence

type). Types can be selected by user when processing a BT or automatically. Standard Correspondence types: 1. Payment notice. 2. @ statement. 3.Individual correspondence. 4. Open item list. 5. User-defined.

Correspondence type components: Following data is necessary for eachtype: 1. Payment notice=Doc #. 2. Bank statement= @ # and date. 3. BofEstatement= doc #. 4. Internal docs=doc #. 5. Individual letters= @ #. 6. Docextracts= Doc #. Components: required data (doc #, @ #), Additional text, Inter-company relationship and the # of date fields required. Data from several CCs canbe combined in a letter.

Printing Correspondence: print program and selection variant can be used foreach correspondence type.

Linking correspondence type to transactions: Specify which correspondencetype can be used in conjunction with various online functions. This selectioninfluences the choice of forms available. Specifications per CC.

Linking Correspondence types and reason codes: For different tolerancegroups, for business partners, specify the default correspondence type in cases ofpayment differences. Use different types depending on the reason code. A paymentnotice is only created according to reason code if all the reason codes carry thesame correspondence type, otherwise the type of payment notice define intolerance group is sent.

UNIT 5: INTEREST CALCULATIONLesson 1: Fundamentals of Interest (I) Calculation.

Types of I calculation: 2 kinds:

1. Account Balance I calculation: applied to the entire balance of GL orcustomer @ using a specific I% over a specific period of time.

2. Interest on Arrears: appliedto individual items in AR or AP. A certain I%is applied to those items that are still open or unpaid at specified date.

Lesson 2: Configuring I Calculation.

Configuring I calculation: involves settings in 5 areas:

1. I calculation indicator: Basic parameters to use when calculating I.Each indicator must be assigned to and I type which specifies whether it isused for an @ balance I calculation or item calculation.

23


24/52

2. General terms: Set financial parameters for each I calculationindicator. E.g.: Frequency, settlement day, calendar type, other settings, max/minlimits on I posting, block on outgoing payments, payment terms, forms.

3. Time-based (dependant) I terms: they have validity dates which isdifferent from General Terms (e.g. a reference I% used in calculation-LIBOR).

4. Reference I rates: e.g. LIBOR. For each reference I, a value andvalidity are entered periodically.

5. @ determination: predefined BTs which are accessed when user runsthe I calculation program. When BT is combined with optional modifiers such as CCand I calculation indicator, sys determines PK and @ symbols. @ symbols, combinedwith modifiers such as currency and CA, refer to GL -C/V @s where the Itransactions are posted.

Running the I calculation: ways to calculate I:1. Account Balance: Limit the # of @s included in the I calculation by enteringintervals or individual values for the CA, @#, CC, I indicator, and business area.Generally, only @s with I calculation indicator and line item display in the MR areincluded.2. Item I calculation (on arreas): I on cleared items only and post the I; I onopen and cleared items and post the I; I on open and/or cleared items withoutposting the I.

UNIT 6: COUNTRY SPECIFICSLesson 1: Check Management

Checks are only printable if sys contains a payable, such as an invoice. PYMTprocess creates a PYMT doc that clears the open invoice. Check and payment docsare created in 2 separate steps. When check is created, check #, bank info andrecipient are printed in both PYMT doc and open invoice. 3 docs involved in PYMTprocess: 1. Vendor invoice (entered in AP or PO cycle). 2. PYMT doc (records thePYMT of the invoice and clears the open invoice). 3. Checks (pre-printed or #generated by sys).

PYMT docs: 3 ways to pay an invoice: 1. Automatic PYMT program: createsPYMT docs and checks automatically. 2. Post and Print forms: create individual PYMTdocs and checks. 3. Post: Creates individual PYMT docs using pre-printed checks.

24


25/52

Check info: Info entered in a PYMT doc and the invoice when a check iscreated: 1. Bank details: a. House bank and bank key. b. @ ID and #. c. bank nameand city. 2. Check Recipient: a. name. b. city. c. country. d. region. 3. Check Info: a.check #. b. PYMT date. c. Currency and amount paid. d. cash discount amount. e.encashment date.

Voiding checks and reversing PYMTs: checks can be voided before printingif they are: 1. accidentally damaged. 2. stolen. 3. destroyed. After printing: 1. notrequired because cash PYMT is made instead. 2. Torn during printing. 3. used for atest print. If PYMT doc needs to be reversed, sys allows to: 1. reverse the check. 2.reverse check then reverse PYMT doc separately. 3. simultaneously.

Reasons for voiding checks: standard or own. A reason can be defined foreach type of void. Sys-generated codes are used by the printing program. Voidinga check updates the PYMT doc, original invoice, and check register.Reversing a doc creates a new reversal doc.

Check register: ABAP program with reports. 1. All checks. 2. outstandingchecks. 3. checks paid. 4. voided checks.

Checks cashed online: cashed checks program used to manually recordchecks that have been cashed by the bank. Process can be automatic with datasupplied by bank. Sys transfers check amount from check clearing @ to the cash @.

Lesson 2: LockBox

Service by banks to facilitate collection and processing on incoming PYMTs.PYMT dont go to office but to bank. Information contained in lockbox: 1. Customername and # in SAP. 2. Customer MICR # (routing # and @ #). 3. check amount. 4.Invoice #. 5. Payment date. 6. payment amount/deductions per notice. 7. reasonsfro deductions. Advantages of lockbox: 1. less processing time in accounting dept.2. increases cash flow. 3. cutting processing costs.

Capital Flow: Lockbox import programs post a GL entry to update the CCs

cash position and create a PYMT advice file from the bank input. PYMT advice noteis compared with Customers open items in AR. Matching items are cleared. Notprocessed checks will be manually processed.

Lockbox file formats: BA1, BA2, MICR number.

Lockbox posting entries: posts a cash receipt to an incoming PYMT @ and an@ for unassigned cash receipts. When PYMT advice info is offset against opencustomer items, open item and posting to the @ for unassigned cash receipts arecleared.

Processing of PYMT advice notes: PYMT advice notes contain info on theincoming PYMT. The more complete the better chances of efficient automaticclearing. Info contained: 1. customers MICR, 2. check amount, 3. invoice #. 4. PYMTdate. 5. PYMT amount/deductions per invoice. 6. reasons for deductions. LOCKBOXsearches data and clears open items. When check is assigned, PYMT advice note isdeleted, If not, PYMT advice note is kept for further processing.

Post processing: check status: checks the status of checks that wereassigned in the lockbox function. Every check that do not balance open items orthat was not assigned to a customers @ has to be manually cleared.

4 status of checks: 1. Applied (assigned): a. customer identified. b. doccleared. 2. Partially applied (assigned): a. customer identified. b. doc cleared. c.further processing. 3. On account: a. customer identified. c. further processing. 4.Unprocessed: c. further processing.

Posting data: in the posting data for autocash with lockbox screen, specifythe owner of the lockbox and the types of postings generated. 1. Lockbox format

(BA1, BA2). 2. Types of posting generated (GL, SL). 3. Amounts posted per check orgrand total. 4. Create a batch input session to insert new/missing bank details into

25


26/52

the Customer MR. 5. Additional posting parameters (PK, doc types used to createposting docs).

Lockbox import program: in the main lockbox program screen you specifywhere the lockbox data is stored and how it is to be processed. Also: file name,format of the input records, and how PYMT amounts are to be cleared against openitems.

UNIT 7: STANDARD REPORTS IN GL ACCOUNTING AND AR/APACCOUNTING

Lesson 1: Information Systems

Where are the reports? 1. Info sys for each area. 2. Gral report selectionscreen. 3. role-based user menu. 3. generally>sys>services>reporting.

Report Names: most reports in GL, AR, AP start with RF. RFK_=vendors.RFD_=customers. RFS_=GL @s. RFB_=doc reports.

AP info sys is split into reports for: 1. vendor balances. 2. vendor items. 3.

master data. 4. PYMT transactions. In Dynamic selections options can be chosenfor industry, @ group, country, city, etc.

AR info sys: GL @ balance list displays selected total figures by reportingperiod. Its possible to see: 1. Carryforward balance at the start of the FY. 2. Total ofthe carryforward balance period. 3. D&C total for the reporting period. 4. D&Cbalances at the end of each reporting period. At the end of the list: total for eachCC, al CCs and each local currency.

Lesson 2: Report Variants and Variables

Report Variants: selection criteria: variant enable to execute a reportrepeatedly with a diff. selection criteria in diff. variants. Define multiple reportvariants for one report. The report variants contain diff. selection criteria. A

report can have diff. report variants that provide info based on the selection criteriadefined.

Report Variants Attributes: One variant can have: 1. Name. 2. description.

Report Variant selection variables: instead of entering values for selectioncriteria each time a report is started, enter values only once and save them in avariant Use selection variables if call up the report and use a variant but still wantto display certain values up to the current date. Types of selection variables:1.Table Variables from TVARV: use them when storing statistical info that canbe used in diff. reports. When saving attributes for the variant, can maintainparameters in the table with the selection options, single values, intervals, etc. 2.Dynamic date calculation: e.g. current date, from month start to today, currentdate +/- days (working days), first day of the month (current, previous, next), 1st,

2nd, 3rd, 4th, quarter, previous/current month etc.

UNIT 8: LIST VIEWERLesson 1: SAP List Viewer Design

26


27/52

LV: Line item list: Creates standard ergonomic list fro predefined data. LVstandardizes and simplifies use of lists in SAP by providing uniform interface listpreparation function.

LV: Display/change viewers: Functions for displaying and changing docs: 1.Select detail: eyeglasses to display, pencil to change. 2. Select item: select an item

on the left side of the list. Mass change is possible. Change errors logs. LV: Generic functions: 1. Select columns (sorting, filters). 2. Summation (totaland subtotal for specific values).

LV: Display variants and fields: Possible create new display variants inaddition to the provided. Select fields in column set, hide and sort fields and addspecific fields.

Classic List and grid ctrl in line item list: When display the list choose: 1. ALVclassic list. Displayed list when no specific settings are made. Useful for multiple@s. (essentially the print screen and offers a better overview of the sorted list). ALVgrid control: has proportionate text. Useful for individual @s.

User parameters for list: enter user-default values where value is constant.

Lesson 2: Selections

Line Item list: use specific selection criteria to choose line item to evaluate.Criteria: 1. GL @ -C/V@:simple and multiple selection to include or exclude @sand @ intervals. 2. Selection using search help: A. input for the GL @ line itemlist: i) GL @# in CA. ii) GL@ name. iii) GL@ with deletion and block indicators. iv)Keywords. v) Alternative @ #s. B. Input for V line item list: i) Gral V data. ii) Vcountry/CC. iii) V by personnel #. iv) V by purchase, material or plant ref. C. inputhelp for C line item list: i) Gral C data. ii) C country/CC/@group. iii) C with rentalagreement. iv) C for each sales group or with plant ref. v) head office C. 3. Itemselection: A. Item status: i) Open items (operational key date). ii) Cleared items(Clearing date, open at key date). iii) All items (posting date). B. Item Type

(category): i) standard items. ii) SGLT (C/V). iii) Noted items. iv) Parked items. v) C/Vitems.

Selection by net due date:net due date is calculated from the TofP baselinedate and the highest # of days within the TofP.

Key for icons:In the header of the AVL classic list: 1. item status: a. open. b.cleared. c. parked. 2. Net due date: a. overdue. b. due. c. nor due.

Assignment field as sort field:in addition to selection columns, when creatingor changing the layout, its possible to define sort criteria for sorting and createsubtotals.

Lesson 3: Changing the Screen Layout

Layout: choose between diff. layouts when displaying a list: standard layoutstarts with / and can be chosen as default layout. If indicator for display variant isset as initial variant, this variant is always used unless otherwise specified. Alsopossible is to use a user-specific layout.1. Standard layout: default andinitial layout: its possible to save the last layout used as default layout. If nochoice is made, the list layout from the default selection screen is selected fromuser parameters. Default the input field for each @ type. By default, sys uses ALVinitial layout. Then choose display variant management, if not, sys uses 1SAPlayout. 2. User-specific layout: which only user can use. Select in editingoptions of the user parameters.

27


28/52

UNIT 9: DRILLDOWN REPORTING IN FILesson 1: Architecture of Drilldown Reporting (DR)

DR is a dialog-oriented info sys for evaluating data from FI, GL, AR and AP

databases. Contains helpful functions for navigating in the database and forprocessing a report interactively. Using the Report Painter: Graphic interface foractivities such as: 1. report writer reports. 2. DR forms. 3. Planning layouts.

Form types: DR in FI: can be used for GL@s evaluation: 1. Reports for FSanalysis: based on FS versions defined in FI. 2. Key figure reports: takes only the FSitems in the FS version needed for calculation of specific key figures. 3. Balancedisplay: for C/V DR its possible to use a. Balance display report. b. Line itemanalysis.

Architecture of DR: a report is a number of interactive, controllable reportlists and graphics that are displayed on the screen and contains characteristics, keyfigures and forms. 1. Provides functions for navigating within dataset. 2. Containsadditional functions to process a report interactively. 3. Its possible to send, display

on the internet, or transfer reports. 4. Contains functions for printing reports. Aform describes basic content and formal structure of report list. Can be seen assemi-finished product for a report.Lesson 2: Characteristics and Key Figures

A. Characteristics: specify classification options for the data set. E.g. CC,business area, Plan/actual indicator, time reference (FY, period). B. Characteristicvalues: Concrete forms of a characteristic. A combination of a+b=object in DR.Key figures: are not just values (balance sheet value, debit total, sales/purchases)or quantities (# of employees, sales quantity) but also calculations (formulas).

Drilldown list/detailed list: Two types of list for displaying info: 1. Drilldownlist: several objects are formatted using a selection of key figures. 2. Detail list: anindividual object is formatted for all key figures according to the form.Lesson 3: Form Types

Single-axis (one) form without key figure:make selection only incharacteristic columns which define the column content. Select key figures andDrilldown characteristics when defining the report. Single-axis (one) from with keyfigure: key figures are integrated with characteristics in rows of form. Two-axis(matrix) dual anis form with key figure: define rows and columns with key figuresand characteristics.Lesson 4: Navigation in Reports

From drilldown list to detail list:Choose detail list symbol.

From detail list to drilldown list:Choose drilldown symbol.Lesson 5: Form and Report Definition

Form definition: Balance sheet analysis example: can define characteristicsfor all columns individually (gral selections). Also possible to define characteristicvalues (fixed values or variable). Formula can be used to compare two year balancesheet.

Report definition: Balance sheet analysis example: characteristics: select allto be used fro the evaluation in report. These are drilldown characteristics usedto navigate. Sorting and organizing is possible. once one characteristic is selected,all values of this characteristic are included in the report. Options to r

RESÚMENES COMPILADOS

Documents

Transcript of RESÚMENES COMPILADOS