Finance in SAP for non-financial consultants Finance for non-financial consultants This presentation’s purpose is to give overview of basic Financial objects and their configuration for non-financial consultants who might need to use them on the SAP implementation projects. If you feel that information in this presentation is not covering all the questions you have, please comments. You may also consider buying SAP-related Contents ● Organisational objects overview ● Basic configuration ● Enhanced configuration Organisational objects overview ● Organisational objects overview ● Basic configuration ● Enhanced configuration Organisational objects overview Finance FI Accounts Payable Accounts Receivable General Ledger Banks / Cash Management Fixed Assets CO Cost Centres Profit Centres Internal Orders Project System (WBS) Investment Management Organisational objects overview Finance FI Accounts Payable Accounts Receivable General Ledger Banks / Cash Management Fixed Assets CO Cost Centres Profit Centres Internal Orders Project System (WBS) Investment Management Organisational objects overview Chart of Accounts Chart of Accounts Controlling Area Company Code Controlling Area Company Code Controlling Area Controlling Area Company Code Organisational objects overview Vendor account group Chart of Accounts Chart of Accounts GL account group Retained Earnings account Fiscal Year Variant Controlling Area Company Code Controlling Area Company Code Controlling Area Controlling Area Field Status Variant Posting Period Variant Company Code Customer account group Contents ● Organisational objects overview ● Basic configuration ● Enhanced configuration Basic configuration Basic configuration of Finance enables usage of reference objects when they are required in other modules. Basic configuration - CoA Chart of Accounts is a list of General Ledger Accounts which can be used for financial postings. Chart of Accounts itself is a separate organisational object. Usually there is one Chart of Accounts for the company. Basic configuration - CoA Configuration of CoA is carried out in IMG node: Transaction code OB13. Basic configuration - CoA Parameters for the Chart of Accounts Basic configuration - CoCd Company Code is main organisational object in Finance. All postings belong to Company Code. Usually Company Code represents legal entity which produces statutory reporting. Basic configuration - CoCd Configuration of CoCd is carried out in IMG node: Transaction code OX02. Basic configuration - CoCd Basic parameters for creation of Company Code are: Basic configuration - COArea Controlling Area is main organisational object in Controlling. Costs accounting is fulfilled within Controlling. This includes Cost Centres, Internal Orders, WBS-elements. Even though Profit Centre accounting is not entirely part of Controlling now, it requires existence of Controlling Area. Usually Controlling Area includes all Company Codes n scope. Basic configuration - COArea Configuration of COArea is carried out in IMG node: Transaction code OX06. Basic configuration - COArea Basic parameters for creation of Controlling Area are: Basic configuration - Assignments Organisational objects are to be assigned to each other before effective usage. Slides below describe assignments of CoCd to CoA and CoCd to COArea. Basic configuration - Assignment Assignment of Company Code to Chart of Account is carried out in IMG node: Transaction code OB62. Basic configuration - Assignment Assignment of Company Code to Chart of Accounts: Basic configuration - Assignment Assignment of Company Code to Controlling Area is carried out in IMG node: Transaction code OX19. Basic configuration - Assignment Assignment of Company Code to Controlling Area: Contents ● Organisational objects overview ● Basic configuration ● Enhanced configuration Enhanced configuration Enhanced configuration is required when not only organisational objects are required for assignments, but also additional Finance elements are required for the project, like GL accounts, Customer and Vendor master data. Enhanced configuration – FY Variant Fiscal Year Variant determines assignment of calendar days to reporting periods in Finance. Fiscal Year variants determines: ● Number of normal and technical periods ● Whether the company uses periods equal to calendar months or not ● Whether Fiscal Year starts and ends on the same dates each year or not End dates for each period must be defined for non-calendar FY Variant. Enhanced configuration – FY Variant Configuration of FY Variant is carried out in IMG node: Transaction code OB29. Enhanced configuration – FY Variant Parameters for the Fiscal Year Variant: Enhanced configuration – PPV Posting Period Variant determines range of open periods in the Fiscal year. PPV is assigned to Company Code. Later you can maintain the periods and allow/block postings in them. Transaction OB52. There can be 2 ranges of open periods: one for normal activities and another (optional) for closing activities. Please note that you cannot maintain Open Periods themselves in test system. Client should have status “Development” or “Productive” in order to maintain the periods. Enhanced configuration – PPV Configuration of Posting Period Variant is carried out in IMG node: Transaction code OBBO. Enhanced configuration – PPV Parameters for the Posting Period Variant: Enhanced configuration – FSV Field Status determines rule for the opening/hiding field during the Financial document entry. There can be different settings for different types of accounts. For example, Reconciliation accounts (linked to Customers or Vendors), Cost accounts and Bank accounts are different from each other, because different fields should be available on the screen or made mandatory. Possible entries for field status are: ● Hidden ● Optional ● Mandatory Set of rules for all available fields is named “Field Status Group” (FSG). Set of FSGs is named “Field Status Variant”. This FSV is assigned to CoCd. Enhanced configuration – FSV Configuration of Field Status Variant is carried out in IMG node: Transaction code OBC4. Enhanced configuration – FSV Parameters for the Field Status Variant: Enhanced configuration – Assignment Once Fiscal Year Variant, Posting Period Variant and Field Status Variant are created and configured, they can be assigned to the Company Code. Additional parameters for the CoCd can be defined in the same transaction Enhanced configuration – Assignment Configuration of Company Code is carried out in IMG node: Transaction code OBY6. Enhanced configuration – Assignment Parameters for the Company Code: Enhanced configuration – GL account group General Ledger Account group allows to show/suppress fields on the screen of General Ledger Account master record. There should be at least one account group for the CoA before any GL account can be set up. Each field on the master record of GL account can have one of the following 4 statuses: ■ Hidden ■ Optional ■ Mandatory ■ Display only Enhanced configuration – GL account group Configuration of GL Account Group is carried out in IMG node: Transaction code OBD4. Enhanced configuration – GL account group Parameters for the GL Account Group: Enhanced configuration – Retained earnings account There are 2 types of GL accounts: Balance Sheet and Profit&Loss. Balance of BS accounts goes over the year-end without any changes while balance of P&L account is zero at the beginning of the Fiscal Year. Retained earning account is balance sheet account which gets balance of P&L accounts during the year-end closing. Retained earnings account type defines which BS account gets balance of P&L account. There should be at least one Retained earnings account type before P&L account can be created. It is recommended to create retained earning BS account before creating Retained earnings account type Enhanced configuration – Retained earnings account Configuration of GL Retained Earnings account is carried out in IMG node: Transaction code OB53. Enhanced configuration – Retained earnings account Parameters for the GL Retained Earnings account: Enhanced configuration – Vendor / Customer account group Vendor / Customer group allows to group counterparties and also show/suppress fields on the screen of master record. There should be at least one account group for the vendor / customer before any account can be set up. Each field on the master record of GL account can have one of the following 4 statuses: ■ Hidden ■ Optional ■ Mandatory ■ Display Customer and Vendor master records consist of 3 segments: Central data, Company Code data and Purchase / Sales organisation data. Each of those segments have fields specific for the purpose. They can be managed separately. Enhanced configuration – Vendor / Customer account group Configuration of Vendor / Customer Account Group in Finance is carried out in IMG node: Transaction codes OBD3 and OBD2. Enhanced configuration – Vendor / Customer Parameters for theaccount Customer Accountgroup Group:
