b29 core fi

7/27/2019 B29 Core FI

http://slidepdf.com/reader/full/b29-core-fi 1/101

SAP R/3 4.7

March 2004

English

Core FI

SAP AGNeurottstr. 1669190 Walldorf Germany

Building Block Configuration Guide

7/27/2019 B29 Core FI


SAP Best Practices Core FI: Configuration Guide

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without

the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software componentsof other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registeredtrademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®,OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USAand/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein aswell as their respective logos are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves information purposesonly. National product specifications may vary.

© SAP AG of 101

7/27/2019 B29 Core FI



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.

© SAP AG of 101

7/27/2019 B29 Core FI



Content

Core FI: Configuration Guide.......................................................................................................... 6

1 Purpose.................................................................................................................................... 6

2 Preparation...............................................................................................................................6

.2.1 Prerequisites..................................................................................................................... 6

.2.2 Upload Configuration Role................................................................................................7

3 Installation................................................................................................................................ 7

.3.1 Customizing of B29 (Core FI)................................................................................. .......... 7

3.1.1 Core FI - Organizational Structures.............................................................................7

3.1.2 Core FI - Master Data..................................................................................................9

.3.1.2.1 Master Data: General Ledger........................................................................... 9

.3.1.2.2 Master Data: Accounts Receivable.................................................................11

.3.1.2.3 Master Data: Accounts Payable......................................................................13.3.1.2.3.1 Master Data: Accounts Payable – Sensitive Fields............15

.3.1.2.4 Master Data: Bank Accounting.......................................................................16

3.1.3 Core FI - Configuration.............................................................................................. 18

.3.1.3.1 Financial Accounting – Basic Settings............................................................18

.3.1.3.1.1 Correspondence.................................................................23.3.1.3.2 General Ledger Accounting............................................................................ 25

.3.1.3.3 Financial Accounting: Accounts Payable........................................................25

.3.1.3.3.1 Down Payment Received and Other Special G/LTransactions.......................................................................................26

.3.1.3.3.2 Vendor Invoice....................................................................27

.3.1.3.3.3 Document Reversal............................................................29

.3.1.3.3.4 Vendor Line Item Analyses.................................................30

.3.1.3.3.5 Account Determination Payments......................................30

.3.1.3.3.6 Manual Payments...............................................................33

.3.1.3.3.7 Automatic Payments...........................................................34

.3.1.3.3.8 Manual Clearing..................................................................44

.3.1.3.3.9 Automatic Clearing.............................................................45.3.1.3.4 Financial Accounting: Accounts Receivable................................................ ...45

.3.1.3.4.1 Down Payment Received and Other Special G/LTransactions.......................................................................................45.3.1.3.4.2 Customer Invoice................................................................46.3.1.3.4.3 Document Reversal............................................................47.3.1.3.4.4 Customer Line Item Analysis..............................................48.3.1.3.4.5 Account Determination payments......................................49.3.1.3.4.6 Manual Payments...............................................................50.3.1.3.4.7 Automatic Payments...........................................................51.3.1.3.4.8 Manual Clearing..................................................................60.3.1.3.4.9 Automatic Clearing.............................................................61

© SAP AG of 101

7/27/2019 B29 Core FI



.3.1.3.4.10 Dunning............................................................................62

.3.1.3.4.11 Interest Calculation...........................................................65.3.1.3.5 Bank Accounting.............................................................................................66

.3.1.3.5.1 Bank Accounting: Cash Journal.........................................66

.3.1.3.5.2 Bank Accounting: Electronic Bank Statement....................69

.3.1.3.5.3 Manual Bank Statement.....................................................74

.3.1.3.5.4 Check Management...........................................................76.3.1.3.6 Closing Activities.............................................................................................78

.3.1.3.6.1 Current and other Assets....................................................79.3.1.3.6.1.1 Interest Calculation for Balance Sheet Accounts........80

.3.1.3.6.2 Receivables/Liabilities........................................................81

.3.1.3.6.3 Accrual/Deferral Postings...................................................83

.3.1.3.6.4 Period End Reporting.........................................................843.1.4 Core FI – Intercompany Settings...............................................................................85

.3.2 Import/Create Financial Statement Version.................................................................... 87

.3.3 Import/Create Tax Codes................................................................................................89

.3.4 Set Changes Without Automatic Recording....................................................................92

.3.5 Create Adress for Accounting Auditor (Balance Confirmation).......................................92

.3.6 Copy G/L Account Master Data (Company Code) - Intercompany.................................93

.3.7 Set Automatic Recording of Changes.............................................................................94

.3.8 Application modules per Event (Allow Dunning with SAPSCRIPT Forms)......................94

.3.9 Master Data.................................................................................................................... 95

3.9.1 Bank Master Data......................................................................................................95

.3.9.1.1 Create Bank Master Data............................................................................... 96

3.9.2 GL Account Master Data...........................................................................................97

.3.9.2.1 FS00: Maintain House Bank...........................................................................97

3.9.3 Customer Master Data..............................................................................................98

.3.9.3.1 Create Customer Master Data ....................................................................... 99

.3.9.3.2 Create/Change customer credit limit...............................................................99

.3.9.3.3 Create One-Time Customer Master Data (Domestic; Accounting)...............100

3.9.4 Vendor Master Data............................................................................................. ...100

.3.9.4.1 Create Vendor Master Data (Accounting).....................................................100

.3.9.4.2 FK02: Change Vendor - enter bank data to vendor......................................101

.3.9.4.3 Use............................................................................................................... 101

.3.9.4.4 Create One-Time Vendor Master Data (Accounting)....................................101

© SAP AG of 101

7/27/2019 B29 Core FI



Core FI: Configuration Guide

1 PurposeThe purpose of this document is to describe the general configuration steps required to manuallyset up the configuration within the system landscape that has already been installed using thecorresponding installation or configuration guides for installation.

The Configuration Guide describes how to set up the configuration of a Building Block manually,without the support of automated configuration tools. If you want to use BC Sets and CATTprocedures for an automated installation process, refer to the Building Block Installation Guide of the Building Block B29.

2 Preparation

Before starting the configuration of the building block, some preparation activities must beperformed. All of these activities are described in the following chapters.

.2.1 Prerequisites

System Variants for Reports Included in the Standard System

Installing R/3 Enterprise installs the following system variants which are created in thenamespace SAP&/BPFIDE/ in client 000.

PgmID Object Object Name

LIMU VARI RFFOD__LSAP&/BPFIDE/10LIMU VARI RFFOD__SSAP&/BPFIDE/10LIMU VARI RFFOD__SSAP&/BPFIDE/20LIMU VARI RFFOD__USAP&/BPFIDE/10LIMU VARI RFKORD30SAP&/BPFIDE/10

You can copy those variants (but you do not have to ) to application variants using transactionSE38.

Before starting the installation, complete the following activities:

• Read the documentation building block Essential Information, which you need for a BestPractices for mySAP All-in-One installation.

• Install all required Building Blocks and Layers for example BB B32 an J02.• Install all required notes

• Enter a printer in your user parameters otherwise you are not able to run all BusinessProcess Procedure later on.

© SAP AG of 101

7/27/2019 B29 Core FI



.2.2 Upload Configuration Role

Use

Before you start with the configuration according to the manual procedures described in thisConfiguration Guide, you need to upload the configuration role and assign it to your user.

The building block Core FI provides a configuration role for SAP R/3. The configuration roleenables you to easily access all transactions required for the configuration from the relevantsystem. The following role is available:

Technical name Description File name for upload

/SMB15/B29_01CConfiguration role B29Core FI _SMB15 _B29_01C.SAP

Procedure

For details how to upload the configuration roles to the system and how to work with the rolesplease refer to building block Essential Information.

3 Installation

.3.1 Customizing of B29 (Core FI)

3.1.1 Core FI - Organizational Structures

Overview of the organizational elements in SAP FI and their characteristics:Company Codes

The company code is an organizational unit in external accounting for which a balance sheet anda profit and loss statement can be created. The following company codes are mapped in thesystem:

Company Code Description

BP01 Company Code Germany

The company code is the smallest organizational unit in Financial Accounting for which a complete self-contained set of accounts can be drawn up for the purposes of

external reporting.

Fiscal Years

The fiscal year variant K4 has been assigned to the company code. For more information, refer tothe documentation on the global settings.

VAT Registration Numbers

The ID (registration number) DE123456789 has been defined for company code BP01 and isused to run the model reports. This ID must be adapted to customer requirements.

© SAP AG of 101

7/27/2019 B29 Core FI



Additional Specifications for Company Code

The additional information required has been entered accordingly for company code BP01. Thisdata must be adapted to customer requirements.

Additional Currencies

In addition to the local currency used for a particular company code, you can define up to two

further currencies.

The following currency types are available: Group currency (currency type 30), hard currency(currency type 40), index-based currency (currency type 50), and global company currency(currency type 60).

For company code BP01, the group currency (EUR) has been set as the additionalcurrency for the local currency (EUR).

The parameters for translating the currencies are set as follows:

Crcy Type 30 Group currency

Valuation 0 Legal valuation

Ex. Rt. Type M Standard translation at average rate

Srce Curr. 1 Translation taking transaction currency as a basis

TrsDte Type 3 Translation date

These settings have been made in such a way that you can activate the additional currencyseparately via a BC Set.

You cannot change the currency type for company codes that are already in use.

Functional Areas

The functional area is an organizational unit in Accounting that classifies the expenses of anorganization by function. Functional areas are used in cost of sales accounting. Since periodaccounting is implemented in Best Practices for Accounting Germany, no functional areas areused.

Dunning Areas

Dunning areas are used when several organizational units are responsible for dunning within acompany code (these organizational units are known as ‘dunning areas’). The dunning area canrepresent a division, a distribution channel, a sales organization, or a business area, for example.

Dunning Area Name

1000 BPAcc dunning area

Charts of Accounts

The chart of accounts is a classification scheme consisting of a group of general ledger (G/L)accounts (for more detailed information, see Section 2).

Charts of Accounts Name

IKR Chart of accounts - industry

Companies

The company is the smallest organizational unit for which individual financial statements can bedrawn up.

© SAP AG of 101

7/27/2019 B29 Core FI



A company can consist of one or more company codes.

Company Name

BP0001 BU SMB Company

Company code BP01 is assigned to company BP0001.

For consolidation purposes, a company can only be assigned to one company code.

Credit Control Areas

The credit control area is the organizational unit that contains all of a customer’s receivables. Youcan also define the credit control area on a cross-company code basis. This means that you cantrack the customer credit that has been granted outside a company code, in other words, outsidethe legally independent unit.

Credit Control Area Name

BP01 BU SMB credit control area

Company code BP01 is assigned to credit control area BP01.

Access the Customizing activity as described in the BC Set configuration data and make thesettings according to the table values listed in this documentation.

BC Set configuration data: SMB15_1000_ORG_STRUC_S002_B29.DOC

3.1.2 Core FI - Master Data

In this section, you make the Customizing settings for the master data. Please carry out the stepsas described in the following subchapters (General Ledger, Accounts Receivable, AccountsPayable, Bank Accounting).

.3.1.2.1 Master Data: General Ledger

Chart of Accounts

The system features the chart of accounts IKR (chart of accounts - industry) (from SAP AG).

You import the chart of accounts by activating BC Sets. The accounts that are used for thevarious Customizing settings are easily recognizable. If you do require further information, youcan refer to the relevant documentation.

General Ledger Account PlanThe system uses the general ledger account plan IKR.

IKR is based on the standard chart of accounts shipped with client 000. It has been extended,however, to include a set of accounts required for Best Practices in Germany.

Company Code Charts of Accounts

BP01 IKR

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_1000_ORG_STRUC_S002_B29.DOC



7/27/2019 B29 Core FI



Account Groups

The account group enables you to define

• The interval in which the account number must be located

• The fields in which entries are optional/required when master records are created andchanged

• The fields that can be suppressed when master data is created and changed. This enablesyou to set the layout of the screens.

You use the account groups to group accounts on the basis of the criteria mentioned above (P&Lstatement accounts, fixed asset accounts, material accounts, for example).

The following account groups from standard SAP system are used:

Account Group Name From Account To Account

ABST Recon. account ready for input 999999

ANL. Fixed assets accounts 999999

ERG. Income statement accounts 999999

FIN. Liquid funds accounts 999999

MAT. Materials management accounts 999999

SAKO G/L accounts (general) 999999

Retained Earnings Accounts

You assign a retained earnings account to each P&L statement account via a P&L statementaccount type, which has to be entered in the chart of accounts area in each P&L statement

account.

At the fiscal year change, the P&L statement account balance is carried forward to the retainedearnings account. You can define one or more P&L statement account types for each chart of accounts and assign them to the retained earnings accounts.

G/L account 350000 (already set in the standard SAP system) was used.

To carry out the activity, choose one of the following navigation options:

Transaction Code SPRO

IMG Menu Financial Accounting → General Ledger Accounting → G/L

Accounts → Master Records → Preparation → Define

Retained Earnings Account

Blocked Accounts

You can block specific G/L accounts to avoid unwanted postings.

The function for blocking a G/L account is available in the transaction for processing an individualG/L account master record.

In Best Practices for Germany, the following G/L accounts have been blocked:

© SAP AG of 101

7/27/2019 B29 Core FI



G/L Account Account Description Reason for the Block

753100 Discount charges Bill of exchange transactions are nothandled.

Menu Path

(Block G/L Account) Accounting

→Financial Accounting

→General Ledger

→ Master Records → Individual Processing → Centrally → G/L

Account → Block


BC Set configuration data: SMB15_2100_GL-MASTERD_S022_B29.DOC

.3.1.2.2 Master Data: Accounts Receivable

The following section refers to company code BP01, which uses the chart of accounts IKR.

Master Data

Account Groups

The following account groups are provided:

Account Group Name

0001 Sold-to party

CPDA One-time cust. (ext. no. assgnmt)

DEBI Customer (general)

DEMO Customer (ext. No – BP)

VERB Affiliated companies - BP

Some minor changes are made to the field selection of account groups. The account groupDEBI – Customer (general) has been copied to DEMO - Customer (ext.Nr – BP). DEMOsimply uses external number assignment and is used to create the CATTs.

Number RangesThe following number ranges have been assigned to the account groups:

Account Group Number Range Interval External

0001 01 10 000 – 99 999

CPDA XX A to Z X

DEBI 02 100 000 – 299 999

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_2100_GL-MASTERD_S022_B29.DOC



7/27/2019 B29 Core FI



DEMO 03 1 - 9999 X

VERB XX A to Z X

Message Control

For application area F2 (Master Data Maintenance: Customer, Vendor), message 145“Customers found with same address; check” has been created for batch and online processingto avoid customer master data being created twice.



IMG Menu Financial Accounting → Accounts Payable Accounts

Receivable → Customer Accounts → Master Data →

Preparations for Creating Customer Master Data → Change

Message Control for Customer Master Data

Business Transactions

Tolerances for Employees

The tolerance group “ ” (blank) with the standard SAP settings has been created for companycode BP01.




Receivable → Business Transactions → Incoming Payments

→ Manual incoming payments → Define Tolerance Groups for

Employees

Tolerances for Business Partners

The tolerance groups “DEB1” and (blank) with the standard settings for customers have beencreated for company code BP01.




Receivable → Business Transactions → Incoming Payments

→ Manual incoming payments → Define Tolerances(Customer)

Maintain Line Layout

To run the information reports for credit control the standard line layout D1 has been changed.Please check your system and maintain the following fields:

© SAP AG of 101

7/27/2019 B29 Core FI



Clearing Document: Offset 7

Text: Display Length 46



IMG Menu Financial Accounting → Accounts Payable AccountsReceivable → Customer accounts → Line items → Display

Line items → Display Line items without ALV → Define Line

Layout

Procedure


BC Set configuration data: SMB15_2200_AR-MASTERD_S023_B29.DOC

.3.1.2.3 Master Data: Accounts Payable

Use

The following section refers to company code BP01, which uses the chart of accounts IKR.

Master Data

Account Groups

The following account groups are provided:Account Group Name

0001 Vendor

0003 Alternative payee

AUSL Foreign vendor

CPD One-time vendor (int. no. assgnmt)

DEMO Best Practice – test data

KRED Vendor (int. no. assgnmnt)

REIS Commercial traveler

VERB Affiliated companies - BP

Some minor changes are made to the field selection of account groups. The account group AUSL– Foreign Vendor has been created. The same applies for DEMO and VERB – Affiliated Companies BP . They simply uses external number assignment and are used for CATTs.

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_2200_AR-MASTERD_S023_B29.DOC



7/27/2019 B29 Core FI



Number Ranges

The following number ranges have been assigned to the account groups:

Account Group Number Range Interval External

0001 XX A to Z X

0003 XX A to Z X

AUSL XX A to Z X

CPD 02 100000 - 199999

DEMO 03 1 - 9999 X

KRED 02 100000 - 199999

REIS 01 10000 - 19999

VERB XX A to Z X

Field Status for Change Vendor ActivityFor the change vendor activity, the field status for the reconciliation account has been set todisplay, which means that the reconciliation account can no longer be changed, even if thevendor master record is changed. This applies for transaction FK02 “Change Vendor (Accounting)” and XK02 “Change vendor (centrally)”.

1. To carry out the activity, choose one of the following navigation options:



Receivable → Vendor accounts → Master Data →

Preparations for Creating Vendor Master Data → DefineScreen Layout per Activity (Vendors)

Message Control

For application area F2 (Master Data Maintenance: Customer, Vendor), message 144 “Vendorsfound with same address; check” has been created for batch and online processing to avoidvendor master data being created twice.



IMG Menu Financial Accounting → Accounts Payable AccountsReceivable → Vendor accounts → Master Data → Preparations for Creating Vendor Master Data → Change

Message Control for Vendor Master Data

© SAP AG of 101

7/27/2019 B29 Core FI



Define Accounting Clerks

You define the names of the accounting clerks under a name identification code. You enter theidentification code in the vendor master records which the accounting clerk supervises. You canuse this information for evaluations and for correspondence.




Receivable → Vendor accounts → Master Data → Preparations for Creating Vendor Master Data → Define

Accouting Clerks

Business Transactions

Tolerances for Business Partners

The tolerance groups KRE1 and (blank) with the standard settings for vendors have been createdfor company code BP01.


BC Set configuration data: SMB15_2300_AP-MASTERD_S024_B29.DOC

.3.1.2.3.1 Master Data: Accounts Payable – Sensitive Fields

Use

In this activity you can define the fields for dual control in the customer/vendor master records.

If you define a field in the customer/vendor master record as "sensitive", the correspondingcustomer/vendor account is blocked for payment if the entry is changed. The block is removedwhen a second person with authorization checks the change and confirms or rejects it.

We recommend to define for object type K (vendor) following settings:

Field name Field label

LFA1-LNRZA Alternative payee

LFB1-LNRZB Alternative payee

LFBK-BANKL Bank Key

LFBK-BANKN Bank Account Number

The bank key, bank account, and alternative payee fields at both client and company code levelshould be defined as sensitive fields. If one of the fields is changed, the account remains blockedfor the payment run until another employee confirms the change to the master record.

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_2300_AP-MASTERD_S024_B29.DOC



7/27/2019 B29 Core FI



If only one person works in the customer’s accounting department, sensitive fieldscannot be used, since the changes must be confirmed by another user. In this case,you should not enter data in table.




Receivable → Vendor accounts → Master Data →

Preparations for Creating Vendor Master Data → Define

Sensitive Fields for Dual Control (Vendors)

For this IMG activity exists no BC Set. You have to define it by yourself.

.3.1.2.4 Master Data: Bank Accounting

Use

Country specific checks:

For all countries with which your company maintains business relationships, you must includerules for checking following data:

Bank data, Postal data, Control data

This data is then checked during master data maintenance.

For France and for US the “Bank Key” and “Length of Bank Key” is changed to:

Country Bank Key (1) Bank Key

FR 4 11

US 4 11

(1) Checking rule for bank key: Length to be kept to exactly, numerical, without gaps



IMG Menu General Settings → Set Countries → Set country-specific

check

Customizing for House Banks

The following four house banks have been created for company code XDE1:

Create House Banks

House Bank BankCtry

Bank Key Bank Name(taken from the bank master data)

BW DE 66220020 Baden-Württembergische Bank

DB DE 50070010 Deutsche Bank Filiale

© SAP AG of 101

7/27/2019 B29 Core FI



DRE DE 82080000 Dresdner Bank

PB DE 66010075 Postbank Karlsruhe

The following Customizing settings have been made for the data medium exchange (thesesettings are used by the payment program):

Instruction key 01 is the default instruction key for all banks. For more information on theinstruction key, refer to the documentation of business process procedure (Automatic paymentprogram).



IMG Menu Financial Accounting → Bank Accounting → Bank accounts → Define House Banks

Create Bank Accounts

The following bank accounts have been created in the system for company code XDE1:

House Bank AccountID

Description Bank AccountNumber

Currency G/L Account

BW GIRO Current account (BW-Bank) 1000002 EUR 282000

DB CHF DB account for CHF 5689555 CHF 280060

DB GIRO Current account (DeutscheBank)

1133698 EUR 280000

DB USD DB account for USD 5689500 USD 280050

DRE GIRO Current account (Dresdner Bank)

2580061 EUR 281000

PB GIRO Current account (Postbank) 72194758 EUR 285000



IMG Menu Financial Accounting → Bank Accounting → Bank accounts →

Define House Banks

Bank Master Data

Real-life “model banks” are imported by means of CATTs.

For Germany, Switzerland, and Great Britain, the key for the bank directory is the bank number.For the USA and France, the key is assigned externally and is the same as the SWIFT code. Appropriate settings have to be made for the relevant country under “Set Country-SpecificChecks”. These settings determine whether report RFBVALL_0 (banks are imported by banknumber) or report RFBVBIC (banks are imported by SWIFT code) is used when the bank master files are imported. No report exists for France that imports banks by bank number.

© SAP AG of 101

7/27/2019 B29 Core FI



Execute transaction SA38 to run those reports and refer to report documentation.

CATT for the Bank Master Data

The ECATT for the bank master data contains real-life “model banks” for Germany, Switzerland,the USA, Great Britain, and France. These model banks are used as house banks and in the

customer and vendor master records.


BC Set configuration data: SMB15_2400_BANK-MASTD_S025_B29.DOC

3.1.3 Core FI - Configuration

In this section, you make the Customizing settings for the configuration. Please carry out thesteps as described in the following subchapters.

.3.1.3.1 Financial Accounting – Basic Settings

Fiscal Year and Posting Periods

Fiscal Year Variants

A fiscal year comprises several posting periods and, if required, special periods to which itemscan be posted after a preliminary year-end closing. You assign this definition to the companycodes. The standard Fiscal Year Variant K4 is assigned to Company Code BP01.

Posting Periods

A correctly managed accounting system must ensure that postings can no longer be made toperiods that have already been closed. In the same way, it must ensure that postings cannot bemade to future periods that are not yet relevant. For this reason, you can open and close postingsperiods for specific company codes.

Variant 0001 is used for the posting period and the following setting has been made:

- The period 01/2000 to 16/2010 is open for postings for all accounts

The variant has been assigned to company code BP01.

To adjust the posting periods use Transaction: S_ALR_87003642.

Documents

Document Number Ranges

Only one document number interval can be defined for each document type in a company code.The document number intervals in a company code must not overlap.

Document Number Assignment

Number assignment is determined by the document type. In the R/3 System, each document typeis assigned a number range from which numbers are assigned - either by the system (internalnumber assignment) or by the user (external number assignment).

The standard number ranges from the R/3 System were used for company code BP01.

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_2400_BANK-MASTD_S025_B29.DOC



7/27/2019 B29 Core FI



Document Types

You can use the document types to classify the postings in line with the different businesstransactions (customer payment or vendor credit memo, for example). If the documents are to bestored separately according to document type, assign each document type a separate number range (for invoices or for credit memos, for example).

The document types in the SAP system are client specific, in other words, they are valid in allcompany codes. The standard document types have been used – only one additional documenttype has been created for posting of customer interest assigned to number range 16.

Additional document type defined in the system:

Type Description

DV Customer interests

The reference document number has been specified as a required entry field for the followingdocument types: DA, DG, DR, DZ

The following document type has been changed:

DocumentType

AccountTypes Allowed

Inter-CompanyPostgs

Enter TradingPartner

Adjustment

SU ADKMS X X X


SAP R/3 EnterpriseRole Menu

Installation→ Customizing of B29 Core FI → Core FI –

Configuration → Financial Accounting: Basic Settings


IMG Menu Financial Accounting → Financial Accounting Global Settings

→ Document → Document Header → Define Document Types

Posting Keys

The posting key determines the way line items are posted. It determines the layout of entryscreens and the type of posting (debit or credit).

The posting keys are defined at client level, which means that any changes made affect all of thecompany codes in this client. Only standard R/3 Posting keys are being used.

Document Change Rules

The system contains a set of fields that cannot be changed once the documents have beenposted. The standard fields that can be changed have been copied for the document header andline items. The only other deviations from the standard system apply to the recurring entrydocuments (see the documentation on closing).

© SAP AG of 101

7/27/2019 B29 Core FI



Maximum Difference Between Exchange Rates

10% has been defined as the maximum difference between exchange rates for company codeBP01.

Field Status Variants

You can combine several field status groups in a field status variant. The field status groupspecifies which fields are active when you enter documents, which are mandatory, and which aresuppressed (field status).

You can assign the field status variant to a company code. This enables you to work with thesame field status groups in as many company codes as you require.

CompanyCode

Field StatusVariant

BP01 BP01

Most of the standard field status groups have been copied without changes from Field StatusVariant 0001. In cases where additional settings or changes had to be made, new field statusgroups beginning with Z have been created additionally.

Field StatusGroup

Text

Z001 BP – General (w/text, assignment, PC)

Z008 Assets area clearing accounts

Z014 BP – MM difference accts (w/ PC, order)

Z052 BP – Accounts for fixed asset retirementZ062 Investment support accounts

The following settings and changes have been made:

G066(copiedfrom G067)

SCB / Supplying Country REQ. ENTRY Must be maintained for thereconciliation accounts of theforeign vendors

G067 Payment Currency /Payment Currency Amount

OPT. ENTRY Must be ready for input if itemsare to be paid in a differentcurrency (i.e. other than the localcurrency)

Z001 Profit Center OPT. ENTRY Profit center can be entered


Z052 Asset Retirement OPT. ENTRY Enables a sales revenue to beposted to account 540200 fromasset accounting

Z052 Asset Number/Subnumber OPT. ENTRY Enables a sales revenue to beposted to account 540200 from

© SAP AG of 101

7/27/2019 B29 Core FI



asset accounting



Z062 Business Area Suppress No business areas shipped withthe system








→ Document → Line Item → Controls → Maintain Field Status

Variants

Tolerance Groups for Employees

The tolerance group “blank” has been set up as follows:

Upper Limits for Posting Procedures:

Amount per Document 1,000,000,000,000.00

Amount per Open Item Account Item 1,000,000,000.00

Cash Discount per Line Item 5.000%

Permitted Payment Differences:

Amount Percent Cash Discnt Adj. to

Revenue 100.00 10.0% 10.00

Expense 100.00 10.0% 10.00







→ Document → Line Item → Define Tolerance Groups for

Employees

Default Values

Fiscal Year and Value Date

© SAP AG of 101

7/27/2019 B29 Core FI



Due to the settings that have been made for postings, a fiscal year or value date are currently notproposed in the system for company code BP01.

Texts for Line Items

Only the standard line items are in the system. For your company requirements, you will have to

set up additional ID’s for line item texts.To carry out the activity, choose one of the following navigation options:


Installation → Customizing of B29 Core FI→ Core FI –Configuration → Financial Accounting: Basic Settings


IMG Menu Financial Accounting →Financial Accounting Global Settings→Document → Line Item → Define Texts for Line Items

Message Control for Document Processing

The following entry has been made here for message number 671 (entry not contained in thestandard system):

671 Account & has payment block ‘&’ W W -



Installation → Customizing of B29 Core FI→ Core FI –Configuration → Financial Accounting: Basic Settings


IMG Menu Financial Accounting →Financial Accounting Global Settings→

Document→

Default Values for Document Processing→

Change Message Control for Document Processing

Accounts for Clearing Differences

The following accounts have been defined for transaction “DSA”:

Debit 710300 Credit 580300

Correspondence

The following standard correspondence types have been prepared for use:

Correspondence Type of CorrespondenceSAP01 Payment notice with line items

SAP06 Account statement

SAP08 Open item list

SAP10 Individual correspondence

SAP18 Cash document

© SAP AG of 101

7/27/2019 B29 Core FI



The individual Form names and standard text are described as additional information insubchapter.

Access the Customizing activity as described in the BC Set configuration data and make the

settings according to the table values listed in this documentation.BC Set configuration data: SMB15_3100_BASICSET_S005_B29.DOC

.3.1.3.1.1 Correspondence

The following SAP Script forms and standard texts are available in Client 000:

Forms

Forms Description

/SMB15/PAY_CONF Payment notice

/SMB15/ACC_STAT Account statement

/SMB15/INT_DOCU Internal document COURIER 12

/SMB15/IND_TEXT Individual letter

/SMB15/CASH_DOC Cash document

/SMB15/F130_CON Form set balance confirmation

/SMB15/F130_ERR Error list COURIER 12

/SMB15/F130_LIS Check list COURIER 12

/SMB15/F130_RES Results table COURIER 12

/SMB15/F130_CON Form set balance confirmation

To adjust these forms to your individual need use Transaction: SE71

Standard Texts

Standard Text Description

/SMB15/HEADER Content of HEADER window for IDES Holding AG

/SMB15/SENDER Sender in ADDRESS window for IDES Holding AG

/SMB15/SIGN Signature in document for IDES Holding AG

/SMB15/FOOTER Content of FOOTER window for IDES Holding AG

To adjust these standard text with the individual information of your company use Transaction:SO10.

Allocate Program for Automatic Correspondence

Entries are made specific for company code BP01:

CCode Corr. Program Variant Description

BP01 SAP01 RFKORD00 SAP01 Payment notice with line items

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3100_BASICSET_S005_B29.DOC



7/27/2019 B29 Core FI



BP01 SAP02 RFKORD00 SAP02 Payment notice without line items

BP01 SAP06 RFKORD10 SAP06 Account statement

BP01 SAP08 RFKORD10 SAP08 Open item list

BP01 SAP09 RFKORD30 SAP09 Internal document

BP01 SAP10 RFKORD40 SAP10 Individual correspondence / standard text

BP01 SAP18 RFKORD80 SAP18 Cash document

Define Form Names for Correspondence Print

Entries are specific for Company Code BP01:

CCode Program Program Title Fo.ID Form

BP01 RFKORD00 Print Program: Payment Notice /SMB15/PAY_CONF

BP01 RFKORD10 Print Program: Account Statement /SMB15/ACC_STAT

BP01 RFKORD30 Print Program: InternalDocuments

/SMB15/INT_DOCU

BP01 RFKORD40 Print Program: Individual Lettersand Standard Letters

/SMB15/IND_TEXT

BP01 RFKORD80 Print Program: Cash Documents /SMB15/CASH_DOC

BP01 SAPF130D Customer Balance Confirmation /SMB15/F130_CON

BP01 SAPF130D Customer Balance Confirmation ER /SMB15/F130_ERR

BP01 SAPF130D Customer Balance Confirmation LI /SMB15/F130_LIS

BP01 SAPF130D Customer Balance Confirmation RE /SMB15/F130_RES

BP01 SAPF130K Vendor Balance Confirmation /SMB15/F130_CON

BP01 SAPF130K Vendor Balance Confirmation ER /SMB15/F130_ERR

BP01 SAPF130K Vendor Balance Confirmation LI /SMB15/F130_LIS

BP01 SAPF130K Vendor Balance Confirmation RE /SMB15/F130_RES

Sender Details

Company-code-specific entries were made for all programs mentioned above.

CoCd Program Header Text Footer Text Signature Sender

BP01

RFKORD00RFKORD10

RFKORD40

RFKORD80

SAPF130D

SAPF130K

/SMB15/HEADER /SMB15/FOOTER /SMB15/SIGN /SMB15/SENDER

© SAP AG of 101

7/27/2019 B29 Core FI



Determine Call-Up Functions

No changes have been made here.

.3.1.3.2 General Ledger Accounting

Accounts for Clearing Differences

The following accounts have been defined for transaction “DSA”:

Debit 710300 Credit 580300

Reasons for Reversal / Negative Postings

Reverse postings and adjustment postings can be set as negative postings. Negative postingsdecrease the transaction figures for G/L accounts, customers, and vendors. After reversal,transaction figures can, therefore, be reset to the status they would have had before the reversed

document and corresponding reversal document were posted. In this case, the reversal is anegative posting.

Negative postings have been permitted for company code BP01.

The settings have been taken from the standard system. Additional information in Chapter Closing – Accrual/Deferrals.

Tolerance Groups

When G/L accounts are cleared, tolerance groups are used to define limits within whichdifferences are accepted and posted automatically to predefined accounts. The groups definedhere are assigned in the G/L account master record.

The following settings have been made for company code BP01:CoCd Tol.

GroupName of Tolerance Group

Debit Credit PerD PerC

BP01 Tolerance Groupfor BP01

1.00 1.00 1.0 1.0

Accounts for Exchange Rate Differences

For a detailed list of the accounts, refer to the documentation in Chapter Closing.

Automatic Clearing

The standard criteria for automatic clearing are the assignment number (ZUONR) and the tradingpartner (VBUND).


BC Set configuration data: SMB15_3200_GL_S006_B29.DOC

.3.1.3.3 Financial Accounting: Accounts Payable

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3200_GL_S006_B29.DOC



7/27/2019 B29 Core FI



.3.1.3.3.1 Down Payment Received and Other Special G/LTransactions

Use

You can post down payments and other special G/L transactions within Best Practices. The

following settings of SAP standard system for down payments paid are used (chart of accountIKR, account type K (vendor)):

Prerequisites

Down Payment Requests: special G/L indicator F Down payment request



IMG Menu Financial Accounting → Accounts Receivable and Accounts

Payable → Business Transactions → Down paymentsreceived → Define Reconciliation Accounts for Customer Down

Payments

Assigned accounts for special G/L indicator: F (Down payment request)

Recon. Acct Special G/L Account Planning Level Input Tax Clearing

440000 230100 FF --

440010 230100 FF --

445000 230100 FF --

445010 230100 FF --

Down Payment: special G/L indicator A Down payment

Assigned accounts for special G/L indicator: A (Down payment)

Recon. Acct Special G/L Account PlanningLevel

Input TaxClearing

440000 230000 A

440010 230000 A

445000 230000 A

445010 230000 A

Other Special G/L Indicator Transactions:

Except for the special G/L account and the indicator for tax clearing, the settings for the other special G/L indicators are in the same way as for indicator A:

SpecialG/L Ind.

Description of G/L Indicator Special G/LAccount

PlanningLevel

Input TaxClearing

B Financial assets down payment 170000 B

© SAP AG of 101

7/27/2019 B29 Core FI



I Intangible asset down payment 040000 I

M Tangible asset down payment 090000 M

O Amortization down payment 448000 O

V Stocks down payment 230000 V

Tax Clearing:

Transaction VVA (Input tax clearing on down payments)

Special G/L indicator Tax clearing Account

A 230290

B 170090

I 040090

M 090090

V 230090

Standard posting keys:

Posting keys 29 and 39 are used for posting vendor item with special G/L indicator.

.3.1.3.3.2 Vendor Invoice

Use

To create invoices in the system, you need to define the following tables in Customizing together with the relevant tables for document entry and master data.

Define Line Layout for Document Change/Display:

In addition to client 000, two further line layout variants have been defined ( A2 - PKey/Acct/Cost Ctr/Description and ZP - Doc. No./Ref./Amt LC/Amt Pmt Curr .)




→ Document → Line Item → Define Line Layout for Document

Change/Display

Default Line Layout:

The system contains default values for:

• Displaying and changing documents and

• Displaying and processing payment proposals

© SAP AG of 101

7/27/2019 B29 Core FI



This variant is used the first time you call up the display or change function provided you have notused any other line layout variant.

You can also assign a line layout variant to the user by entering the value as a parameter in theuser master record.

Individual transactions were changed to use line layout variant A2.



IMG Menu Financial Accounting → Financial Accounting Global Settings → Document → Line Item → Select Standard Line Layout for

Document Change/Display

Posting Keys

When you enter incoming invoices and credit memos, the posting keys for the open items andG/L account items are generated automatically by the system. You cannot change these keyswhen entering invoices and credit memos. The following posting keys have been defined in the

system for the various transactions for the group EGR “Incoming invoices”:Transaction Description Debi

tCredit

EGK Vendor item in incoming invoice 21 31

EGS G/L item in incoming invoice 40 50

EGX (1) Vendor item with special G/L indicator 29 39

(1) not SAP standard



IMG Menu Financial Accounting → Accounts Receivable / AccountsPayable → Business Transactions → Incoming Invoices/Credit

Memos → Incoming Invoices/Credit Memo – Enjoy →Define

Posting Key for Incoming Invoices/Credit Memos

Define Cash Discount Base for Incoming Invoices

In the SAP system, you can specify for each company code whether the cash discount amount isto be calculated on the basis of the gross amount (including tax) or the net amount (excludingtax). For company code BP01, the cash discount amount is calculated on the basis of the grossamount.

CoCd DiscBaseNt

BP01 --

Maintain Terms of Payment:

You can define rules with a four-character key. This enables the system to determine the requiredterms of payment automatically. You assign the specified terms of payment using the key.

The key can be

© SAP AG of 101

7/27/2019 B29 Core FI



• Stored in the master record of the customer/vendor account (in the purchasing or sales view and in the accounting view)

• Entered when the FI document is created (or changed)

• Entered when the logistics documents (in the purchase order and incoming invoice or in the order and the outgoing invoice, for example) are created (or changed)

The terms of payment include settings for the payment terms, the day limit, the baseline date for payment, and installment payments.

The standard terms are used.

.3.1.3.3.3 Document Reversal

Use

To carry out a reverse posting in the system, you have to set various tables in Customizing. Therelevant tables are described in the following section.

Permit Negative Postings

In the SAP system, a reverse posting is generally posted with offsetting posting keys; in other words, the transaction figures are increased when a document is reversed.

If the transaction figures are to be reduced when a document is reversed, note the following:

• The “Negative Postings Allowed” indicator must be set for the company code

• A reason for reversal that generates a negative posting must be used when a documentis reversed

The “Negative Postings Allowed” indicator is set for company code BP01.

CompanyCode

Negative PostingsAllowed

BP01 x



IMG Menu Financial Accounting → G/L Accounting → Business

Transactions→ Adjustment Posting/reversal → Permit

Negative Posting

Create Reasons for Reversal

To reverse an accounting document, you need to specify a reason for reversal. The reason for reversal is stored in the reversed document and determines whether

• A negative posting is generated when the document is reversed (this reduces thetransaction figures)

• An alternative posting date to the one in the original document is permitted

© SAP AG of 101

7/27/2019 B29 Core FI



The standard SAP reasons for reversal are used.

.3.1.3.3.4 Vendor Line Item Analyses

Use

To display items on accounts you need to define line layout variants. In those variants you definewhich information from the line item is displayed on the screen. To make selections when displaying lineitems you need so-called additional fields.

Prerequisites

New additional line layout variants: Z02 – Reference document number and Z03 – Affiliated company


Transaction Code SPROIMG Menu Financial Accounting → Accounts Receivable / Accounts

Payable → Vendor Accounts → Line Items → Display Line

Items → Define Line Items without ALV → Define Line Items

Additional Fields for Line Item Display: field VBUND (Trading Partner) has been included as anadditional field (not contained in the standard client (000).



IMG Menu Financial Accounting → Accounts Receivable / Accounts

Payable → Vendor Accounts → Line Items → Display Line

Items → Display Line Items without ALV → Choose Additional

Fields

.3.1.3.3.5 Account Determination Payments

Use

In the following steps, you define the global settings for automatic account determination for

vendor payments. The settings have been set for the chart of accounts IKR.

Prerequisites

Cash Discount Received

Transaction SKE (Cash discount received): G/L account 618000 is defined (standard SAP) andposting keys.

The system posts the amount to this account when clearing the open items.

© SAP AG of 101

7/27/2019 B29 Core FI



Lost Cash Discount

Transaction VSK (Lost cash discount (net procedure)): G/L account 618050 is defined (standardSAP) and posting keys.

Invoices that are posted net, the system automatically posts the difference between the originalcash discount amount determined and the actual cash discount claimed to this account.

Accounts for Overpayments/Underpayments

Transaction ZDI (Payment differences by reason): G/L account 519000 is defined (standard SAP)and posting keys.

You define the G/L account numbers for revenue accounts and expense accounts to which thesystem posts items under the following conditions:

- Payment differences that arise from underpayments or overpayments

- Payment differences within the tolerance limits for an automatic adjustment posting

- Payment differences that cannot be posted by means of cash discount adjustments

Accounts for Bank Charges

Transaction BSP (Bank charges): G/L account 675000 is defined (standard SAP) and postingkeys.

The system posts the expense amount that you specify in the bank item when you clear thepayment to this account.

Define Accounts for Payment Differences with Alternative Currency

Transaction KDW (Payment differences for altern. currency): G/L account 695400 (debit ) and572100 (credit) is defined and posting keys.

You need these accounts if you use an alternative payment currency for manual or automaticpayments.


SAP R/3 EnterpriseRole Menu Installation→

Customizing of B29 Core FI →

Core FI –Configuration→ Financial Accounting: Accounts Payable



Payable → Business Transactions → Outgoing Payments → Outgoing Payments Global Settings → Define Accounts for

Payment Differences with Altern. Currency

Define Clearing Accounts for Payment Differences with Alternative Currency

Transaction KDZ (Payment diff. for altern. curr. (offset)): no G/L account

In this step, you define clearing accounts for payment differences involving an alternativecurrency. You only have to define accounts here if the accounts for exchange rate differences(transaction KDW) have been defined as relevant for tax. Since the accounts in company codeBP01 have not been defined as relevant for tax, no accounts have been defined here.




Configuration→ Financial Accounting: Accounts Payable

© SAP AG of 101

7/27/2019 B29 Core FI





Payable → Business Transactions → Outgoing Payments →

Outgoing Payments Global Settings → Define Accounts for

Payment Differences with Altern. Currency

Accounts for Rounding Differences

Transaction RDF (Internal currencies rounding differences): G/L account 695440 and 572140 isdefined and posting keys

In this step, you can define accounts for rounding differences.

Define Accounts for Exchange Rate Differences

In this step, you define the numbers of the accounts to which the system posts realized exchangerate differences automatically when it clears open items.

When clearing open items, the system posts the realized expense/revenue (realized exchangerate differences). You define expense and revenue accounts for this purpose.

Reconciliation Account

Val. Loss Val. Gain

440000 695400 572100

440010 695400 572100

445000 695400 572100

445010 695400 572100

460000 (1) 695400 572100

470000 (1) 695400 572100

(1) not standard SAP

In this step, you can also define the accounts for valuating the open items. For more information,refer to the section on closing operations.




Configuration → Financial Accounting: Accounts Payable




Outgoing Payments Global Settings → Define Accounts for Exchange Rate Differences

Posting Keys for Clearing

In this step, you define posting keys and document types for open item clearing transactions. Thesystem uses these keys for line items to be created automatically. The payment program alsouses these posting keys.

© SAP AG of 101

7/27/2019 B29 Core FI



The standard posting keys are used.

.3.1.3.3.6 Manual Payments

Prerequisites


You predefine various amount limits for your employees with which you determine:

- the maximum document amount the employee is authorized to post

- the maximum amount the employee can enter as a line item in a customer or vendor account

- the maximum cash discount percentage the employee can grant in a line item

- the maximum acceptable tolerance for payment differences for the employee.

The tolerance group “BLANK” (SAP standard) has been set up for company code BP01.

Tolerance Groups for Vendors

The tolerance groups are used to deal with differences in payment and residual items which canoccur during payment settlement. Tolerances are specified under one or more tolerance groups. Allocate a tolerance group to each vendor via the master record. For each tolerance group,specify the following:

- Tolerances up to which differences in payment are posted automatically to expense or revenueaccounts when clearing open items

- The handling of the terms of payment for residual items, if they are to be posted during clearing.

Tolerance group “BLANK” and “KRE” have been set up for company code BP01 (same as in SAP

standard).entries have been made here.




Payable → Business Transactions → Outgoing Payments → Manual Outgoing Payments → Define Tolerances (Vendors)

Payment Block Reasons

The following settings have been made:BlockInd.

Explanation Change inPmnt Prop.

ManualPayments Block

Free for payment

* Skip account

A Blocked for payment (1) √ √

© SAP AG of 101

7/27/2019 B29 Core FI



B Blocked for payment

N Postprocess inc. pmnt √

P Payment request √

R Invoice verification (1) √ √

S Other reasons (1) √ √

V Payment clearing √

(1) not SAP standard, changed setup or new entry




Payable → Business Transactions → Incoming Payments → Incoming Payments Global Settings → Define Payment Block

Reasons

Default Values for Payment Block

You can set up an automatic payment block reason for terms of payment.

For terms of payment 0004 payment block reason A have been set up.





Outgoing Payments Global Settings → Payment Block Reasons → Define Default Values for Payment Block

Define Reason Codes

The standard reason codes (defined for Company code 0001) are used.

.3.1.3.3.7 Automatic Payments

Use

Following specifications are determined for automatic payment program for company code BP01.

- Which company codes are included in payment transactions

- Which company codes make payments

- Which payment methods can be used

© SAP AG of 101

7/27/2019 B29 Core FI



- Specifications for payment method depending on the country or on the paying companycode.

- Whether you want to use payment method supplements (e.g. grouping payments usingpayment method supplements).

- From which bank accounts payment is made.

- With which form payment is made.

Prerequisites

Set Up All Company Codes for Payment Transactions

Specify paying company code (process payment transactions centrally for several companycodes) for all company codes involved in payment transactions.

Cash discount strategy : determination of maximum cash discount for the company code

Special G/L transactions: are to be settled for customers and vendors.

Vendors - Special G/L transactions to be paid: A (Down payment), B (Financial assets down payment), F(Down payment request), I (Intangible asset down payment), M (Tangible asset down payment), V(Stocks down payment)

Customers - Special G/L transactions to be paid: A (Down payment), F (Down payment request)





Automatic Outgoing Payments→ Payment Method/Bank

Selection for Payment Program → Set Up All Company Codes

for Payment Transactions

Set Up Paying Company Codes for Payment Transactions

- minimum amount for which an incoming (€ 1,-) or outgoing payment (€ 5,-) is created.

- Forms and sender details for advice notes and EDI accompanying sheets

Form for the Payment Advice: /SMB15/D_AVIS

EDI Accompanying Sheet Form: /SMB15/EDI_01

Text Elements Letter Header: /SMB15/HEADER

Text Elements Footer Text: /SMB15/FOOTER

Text Elements Signature Text: /SMB15/SIGN

Text Elements Sender: /SMB15/SENDER

(SAP standard is used with minor changes)



© SAP AG of 101

7/27/2019 B29 Core FI




Payable → Business Transactions → Outgoing Payments → Automatic Outgoing Payments→ Payment Method/Bank

Selection for Payment Program → Set Up Paying Company

Codes for Payment Transactions

Set Up Payment Methods for Each Country for Payment Transactions

Specification for each country to setup used payment methods.

Pymt Meth.

Name PaymentMethod for

PaymentMethodClassif.

RequiredMaster RecordSpecifications

Doc.Typefor Pymt

Clea-ringDoc.Type

PaymentMediumProgram

Name of PrintDataset

A Bankabbuch(Bank directdebit)

IncomingPayments

DebitMemo

Bank Details ZP ZV RFFOD__U LIST3S

E Bankeinzug(Automatic

debit)

IncomingPayments

DebitMemo

Bank Details

Collection Authorization

ZP ZV RFFOD__U LIST3S

L Ausl.überw.(Foreign banktransfer)

OutgoingPayments

BankTransf.

Allowedfor PersonnelPayments

Street, P.O.Box or P.O.Box Pst Code

Bank Details

ZP ZV RFFOD__L LIST4S

O Orderscheck(Order check)

OutgoingPayments

Check Street, P.O.Box or P.O.Box Pst Code

ZS ZV RFFOD__S LIST1S

P Postgiro(Post office

bank transfer)

OutgoingPayments

PostOffice

Curr. AcctMethod?



R Europaüberw(EU internaltransfer)

OutgoingPayments

BankTransf.

EUInternalTransfer


Bank Details


S Scheck

(Check)

Outgoing

Payments

Check


Street, P.O.

Box or P.O.Box Pst Code


U Überweisung(Banktransfer)

OutgoingPayments

BankTransf.

Allowedfor Personnel


© SAP AG of 101

7/27/2019 B29 Core FI



Payments

All payment methods except “EU internal transfer”: all currency are allowed for payment.

Payment method R (EU internal transfer): only currency EUR is allowed for payment.


Transaction CodeSPRO



Selection for Payment Program → Set Up Payment Methods

per Country for Payment Transactions

Set Up Payment Methods for Each Company Code for Payment Transactions

Define which payment methods can be used per company code and determine the conditionsunder which a payment method should be used.

The system contains the following payment methods and settings for company code BP01:PmntMeth.

MinimumAmount/MaximumAmount (in EUR)

Foreign Payments/Foreign Currency Payments

Grouping of Items

Bank SelectionControl

A 5.00

200,000.00

Foreign Business Partner Allowed

Foreign Currency Allowed

SPACE No Optimization

E 5.00

200,000.00

Foreign Currency Allowed SPACE No Optimization

L 0

1,000,000.00


Foreign Currency AllowedCust/Vendor Bank Abroad Allowed?


O 0

100,000.00


P 5

200,000.00


R 0

5,000.00



Cust/Vendor Bank Abroad Allowed?


S 0

100,000.00





© SAP AG of 101

7/27/2019 B29 Core FI



U 0

1,000,000.00




PmntMeth.

Form DataForm for the PaymentTransfer Medium

Form DataNext Form

Pyt Adv. Ctrl Drawer

A /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2Rows;

Pymt Adv. After …Lines

Name 1

Name 2

12345 location

E /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2Rows;


Name 1

Name 2

12345 location

L /SMB15/D_Z1_98 /SMB15/D_DTA Restricted to 2Rows;


Test nameTest phonenumber

0123/456 - 789

Street 123

D-12345location

O /SMB15/D_ORDSCH As Many as Req

NoPytAdv

Name 1

Name 2

D-12345

locationP /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2

Rows;


Name 1

Name 2

D-12345location

R /SMB15/D_EURO /SMB15/D_DTA Restricted to 2Rows;


Name 1

Name 2

Street 123

D-12345location

S /SMB15/D_SCHECK As Many as Req

NoPytAdv

Name 1

Name 2

D-12345location

U /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2Rows;

Name 1

Name 2

© SAP AG of 101

7/27/2019 B29 Core FI




12345 location

Bank Determination - Ranking Order

The program selects banks or bank accounts from which payment is to be made. Thereforefollowing specifications are made:

- Ranking order of banks: specify which house banks are permitted and rank them in a list.

- Bank accounts: specify which bank account is to be used for payments for each house bank and paymentmethod (and currency, if required) and to which G/L account the payment is posted.

- Available amounts: for each account at a house bank, the amounts (incoming and outgoing payments) thatis available needs to be spedified.

- Value date: specify how many days elapse between the posting date of the payment run and the valuedate at the bank, dependent on the payment method, bank account, payment amount, and currency.

The amounts for outgoing payments are set to zero for all banks (except Deutsche Bank DB),since payments are only effected by Deutsche Bank. Only incoming payments are posted for the

other banks.Reason: If Treasury is also installed, the cash concentration function is activatedhere; in other words, all the other accounts are cleared and transferred to theDeutsche Bank accounts in the evening.






Selection for Payment Program → Set Up Bank Determinationfor Payment Transactions


Please refer to Vendor Invoice


Please refer to Manual Payments

You can use block keys to block an open item or an account for payment as follows:

© SAP AG of 101

7/27/2019 B29 Core FI



1. In automatic payments, the block becomes effective if it has been

- Defined in the master record or

- Entered in the document

If the block is entered in the master record, all the open items in this account arecontained in the exception list. The block keys '*' and '+' in the master record have

certain special features.If you set block key * in the master record, all the items in the account are skipped inautomatic payments.

If you set block key + in the master record, all the items that have not been explicitlyassigned a payment method are skipped. This block key has been deleted, sincethese items also have to be paid.

Note that block key 'A' is usually set automatically when a down payment is entered.You should, therefore, not delete 'A' or use it for other purposes.The “Change in Pmnt Prop.” indicator for the block key specifies whether a block keycan be set or removed in payment proposal processing.

2. A block key in the document only affects manual payments if the “Manual

Payments Block” indicator is set for the block key. A block key set in the master record does not affect manual payments. You can set the system to output a suitablewarning message, however. In this case, message 671 for application area F5 hasbeen set as a warning in message control.

3. The “Not Changeable” indicator must be set for the block key for payment releasein Financial Accounting. This indicator is only relevant for payment orders, however,and is, therefore, not set here.

Changed Message Control

Message 671 (Account & has payment block "&") is defined as a warning for the application areaF5.

(SAP standard)

Prepare Automatic Postings for Payment Program

For following transaction keys the posting keys and special G/L indicators are defined for automatic postings by the payment program:

Transaction ZBA (= Payment program: bank posting)

Transaction ZWO (= Payt program: bank bill liability)

Transaction ZWE (= Payt program: bill exch/bill payt reqst) (1)






Automatic Outgoing Payments→ Automatic Posting →


© SAP AG of 101

7/27/2019 B29 Core FI



Prepare Automatic Postings for Payment Requests

Transaction ZAF (= Payment requests): posting keys and special G/L indicator P are defined.

(SAP standard settings)

A payment request is not required, since the special G/L indicator for F for customer downpayment requests already exists. In Germany, no relevant business transaction exists for payment request P.

Branch Assignment for Automatic Postings

Head office/branch office processing is not supported.

Define Sender Details for Payment Forms

The following text elements are used:

Letter Header: /SMB15/HEADER

Footer Text: /SMB15/FOOTER

Signature Text: /SMB15/SIGN

Sender: /SMB15/SENDER



IMG Menu Financial Accounting →

Accounts Receivable / AccountsPayable → Business Transactions → Outgoing Payments →

Automatic Outgoing Payments→ Payment Media → Define

Sender Details for Payment Forms

Assign Payment Forms for Payment Method in Company Code

Allocate Forms to Paying Company CodeCoCd Form for the Payment Advice EDI Accompanying Sheet Form

BP01 /SMB15/D_AVIS /SMB15/EDI_01

Allocate Forms to Payment Method in Company CodePmnt

Method

Form for the Payment Transfer

Medium

Next Form

A /SMB15/D_TRNSFR /SMB15/D_DTAE /SMB15/D_TRNSFR /SMB15/D_DTAL /SMB15/D_Z1_98 /SMB15/D_DTAO /SMB15/D_ORDSCHP /SMB15/D_TRNSFR /SMB15/D_DTAR /SMB15/D_EURO /SMB15/D_DTAS /SMB15/D_SCHECKU /SMB15/D_TRNSFR /SMB15/D_DTA

© SAP AG of 101

7/27/2019 B29 Core FI







Automatic Outgoing Payments→ Payment Media → Make

Settings for classic Payment Medium Programs → Assign

Payment Forms for Payment Method in Company Code

Assign Payment Medium Program for Payment Method in Country

In this activity, for each payment method you assign the classic payment medium program(RFFO*) that is used for creating payment media in that country.

PaymentMethod

Program Name of the Print Dataset Print Dataset for B/Exch.

A RFFOD__U LIST3SE RFFOD__U LIST3S

L RFFOD__L LIST4SO RFFOD__S LIST1SP RFFOD__U LIST3SR RFFOD__L LIST4SS RFFOD__S LIST1SU RFFOD__U LIST3S

Payment Media: Define Sort Variants

In this activity you define the sort variants for payment medium forms (such as payment advicenotes, checks, bills of exchange). You can choose sorting by the payee's postal code, by thepayment method supplement, by the accounting clerk, or by a combination of these fields.

Standard settings are used: via the currency and the payee's bank details.




Payable → Business Transactions → Outgoing Payments → Automatic Outgoing Payments→ Payment Media → Sort

Variants→ Payment Media: Define Sort Variants

Payment Media: Define Sort Variants for Line Items

In this step, you define the sort variants for line items. Sorting can be set, for example, byreference document numbers or posting date.

Standard settings are used :via document date and Reference number.




© SAP AG of 101

7/27/2019 B29 Core FI




Automatic Outgoing Payments→ Payment Media → Sort

Variants→ Payment Media: Define Sort Variants for Line Items

Define Instruction Keys

Instruction Keys: controls what instructions for making a payment order are sent to participating banks. Thekey can be specified in vendor master records or in your house banks.

For payment method K (check), L (foreign bank transfer) and R (EU internal transfer) an instruction key isspecified.

No instruction key is defined for payment method U (Überweisung (Bank transfer)), since you canalso carry out bank transfers to foreign vendors that have a bank account in your country. You donot need an instruction key here, however, since a message (Z1) is not required.

You need an instruction key for payment method A because a bank direct debit isalso allowed for foreign customers and banks.

To carry out the activity, choose one of the following navigation options:Transaction Code SPRO


Payable → Business Transactions → Outgoing Payments → Automatic Outgoing Payments→ Payment Media → Data

Medium Exchange → Define instruction keys


Please refer to Account determination Payments

Lost Cash Discount






When you clear foreign currency documents in which the foreign currency and local currency arenational currencies, the differences that occur are rounding differences rather than exchange ratedifferences. For rounding differences, you have to define precisely one account in the chart of accounts so that you can post these amounts.



© SAP AG of 101

7/27/2019 B29 Core FI



Accounts must be set as being relevant to tax in order for a tax adjustment to be posted.

In this step, you can define accounts for payment differences involving an alternativecurrency. You need these accounts if you use an alternative payment currency for manual or automatic payments.

The accounts set here are accounts for exchange rate differences, which are set inthe chart of accounts as being “non tax relevant”. This explains why no taxadjustment is carried out when the open items are cleared.



Account determination is not necessary, since the accounts defined in account determination for transaction KDW are accounts for exchange rate differences (transaction: OBXO). These are set

in the chart of accounts as being “non tax relevant”. This explains why no tax adjustment iscarried out when the open items are cleared and a clearing account is not required.



.3.1.3.3.8 Manual Clearing

PrerequisitesLine Layout variants

Please refer to Vendor Line Item Analysis

Additional Fields for Line Item Display








© SAP AG of 101

7/27/2019 B29 Core FI



.3.1.3.3.9 Automatic Clearing

UseIn this step, you specify criteria that will be used to group the open items of an account for automatic clearing. The program clears open items in a group if the balance in local currency andforeign currency is zero and contents of several fields (which are defined in customizing) areidentical.

Prerequisites

Clearing Rules

Rules defined for automatic clearing for account type D (customer), V (vendor) and S (general ledger):

Criterion 1: ZUONR (Assignment)

Criterion 2: VBUND (Trading Partner)




Payable → Business Transactions → Open Item Clearing →

Prepare Automatic Clearing


BC Set configuration data: SMB15_3300_AP_S007_B29.DOC

.3.1.3.4 Financial Accounting: Accounts Receivable

.3.1.3.4.1 Down Payment Received and Other Special G/LTransactions

Use

You can post down payments and other special G/L transactions within Best Practices. Thefollowing settings of SAP standard system for down payments received are used (chart of account IKR, account type D (customer)):

Prerequisites

Down Payment Requests: special G/L indicator F Down payment request

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3300_AP_S007_B29.DOC



7/27/2019 B29 Core FI






Payable → Business Transactions → Down payments made → Define Reconciliation Accounts for Customer Down

Payments

Assigned accounts for special G/L indicator: F (Down payment request)

Recon. Acct Special G/L Account Planning Level Output Tax Clearing

240000 430100 FF --

240010 430100 FF --

241000 430100 FF --

241010 430100 FF --

Down Payment: special G/L indicator A Down payment

Assigned accounts for special G/L indicator: A (Down payment)

Recon. Acct Special G/L Account PlanningLevel

Output TaxClearing

240000 430000 A

240010 430000 A

241000 430000 A

241010 430000 A

Tax Clearing:

Transaction MVA (Output tax clearing on down payments)

Special G/L indicator Tax clearing Account

A 430010

Standard posting keys:

Posting keys 09 and 19 are used for posting transaction AGX (Customer item with special G/Lindicator.

.3.1.3.4.2 Customer Invoice

Use

To enter outgoing invoices and credit memos, the posting keys for the open items and G/Laccount items are generated automatically by the system. You need to define the following tablein Customizing.

© SAP AG of 101

7/27/2019 B29 Core FI



Prerequisites

Posting Key for open items

For more information please refer to Chapter “Financial Accounting: Accounts Payable”, under “Vendor Invoice” as well as following information.

Posting Keys

When you enter incoming invoices and credit memos, the posting keys for the open items andG/L account items are generated automatically by the system. You cannot change these keyswhen entering invoices and credit memos. The following posting keys have been defined in thesystem for the various transactions for the group EGR “Incoming invoices”:

Transaction Description Debit

Credit

AGD Customer item outgoing invoice 01 11

AGS G/L account item outgoing invoice 40 50

AGX (1) Customer item with special G/L indicator 09 19


Procedure




Payable → Business Transactions → Outgoing Invoices/Credit

Memos → Outgoing Invoices/Credit Memos- Enjoy → Define

Posting Key for outgoing Invoices/Credit Memos

.3.1.3.4.3 Document Reversal

Use

To carry out a reverse posting in the system, you have to set various tables in Customizing. Therelevant tables are described in the following section.

Permit Negative Postings

In the SAP system, a reverse posting is generally posted with offsetting posting keys; in other words, the transaction figures are increased when a document is reversed.

If the transaction figures are to be reduced when a document is reversed, note the following:• The “Negative Postings Allowed” indicator must be set for the company code

• A reason for reversal that generates a negative posting must be used when a documentis reversed

The “Negative Postings Allowed” indicator is set for company code BP01.

CompanyCode

Negative PostingsAllowed

© SAP AG of 101

7/27/2019 B29 Core FI



BP01 x



IMG Menu Financial Accounting → G/L Accounting → BusinessTransactions→ Adjustment Posting/reversal → Permit

Negative Posting

Create Reasons for Reversal

To reverse an accounting document, you need to specify a reason for reversal. The reason for reversal is stored in the reversed document and determines whether

• A negative posting is generated when the document is reversed (this reduces thetransaction figures)

• An alternative posting date to the one in the original document is permitted

The standard SAP reasons for reversal are used.

.3.1.3.4.4 Customer Line Item Analysis

Use

To display items on accounts you need to define line layout variants. In those variants you definewhich information from the line item is displayed on the screen. To make selections when displaying lineitems you need so-called additional fields.

Prerequisites

New additional line layout variants: Z02 – Reference document number and Z03 – Affiliated company




Payable → Customer Accounts → Line Items → Display Line

Items → Define Line Items without ALV → Define Line Items

Additional Fields for Line Item Display: field VBUND (Trading Partner) has been included as anadditional field (not contained in the standard client (000).




Payable → Customer Accounts → Line Items → Display Line

Items → Display Line Items without ALV → Choose Additional

© SAP AG of 101

7/27/2019 B29 Core FI



Fields

.3.1.3.4.5 Account Determination payments

Use

In the following steps, you define the global settings for automatic account determination for customer payments. The settings have been set for the chart of accounts IKR.

Prerequisites

Cash Discount Granted

Transaction SKT (Cash discount expenses): G/L account 516000 is defined (standard SAP) and

posting keys.

The system posts the amount to this account when clearing the open items.

For the following Information refer to “Financial Accounting: Accounts Payable”, subchapter “Account Determination Payments”








ReconciliationAccount

Val. Loss Val. Gain

240000 695400 572100

240010 695400 572100

241000 695400 572100

241010 695400 572100

250000 1) 695400 572100

255000 (1) 695400 572100

(1) not standard SAP

© SAP AG of 101

7/27/2019 B29 Core FI







Payable → Business Transactions → Outgoing Payments → Outgoing Payments Global Settings → Define Accounts for

Exchange Rate Differences




Reconciliation

account

Val. Loss Val. Gain

240000 695400 572100

240010 695400 572100

241000 695400 572100

241010 695400 572100

250000 695400 572100

255000 695400 572100


.3.1.3.4.6 Manual Payments

Prerequisites


For more information please refer to Chapter “Financial Accounting: Accounts Payable”,subchapter “Manual Payments”.

Tolerance Groups for Customers

The tolerance groups are used to deal with differences in payment and residual items which canoccur during payment settlement. Tolerances are specified under one or more tolerance groups. Allocate a tolerance group to each customer via the master record. For each tolerance group,specify the following:

- Tolerances up to which differences in payment are posted automatically to expense or revenueaccounts when clearing open items

- The handling of the terms of payment for residual items, if they are to be posted during clearing.

© SAP AG of 101

7/27/2019 B29 Core FI



Tolerance group “BLANK” and “DEB1” have been set up for company code BP01 (same as inSAP standard).

entries have been made here.




Payable → Business Transactions → Incoming Payments → Manual Incoming Payments → Define Tolerances (Customers)

.3.1.3.4.7 Automatic Payments

Use

Following specifications are determined for automatic payment program for company code BP01.

- Which company codes are included in payment transactions

- Which company codes make payments

- Which payment methods can be used

- Specifications for payment method depending on the country or on the paying companycode.

- Whether you want to use payment method supplements (e.g. grouping payments usingpayment method supplements).

- From which bank accounts payment is made.

- With which form payment is made.

Prerequisites

Set Up All Company Codes for Payment Transactions

Specify paying company code (process payment transactions centrally for several companycodes) for all company codes involved in payment transactions.

Cash discount strategy : determination of maximum cash discount for the company code

Special G/L transactions: are to be settled for customers and vendors.

Vendors - Special G/L transactions to be paid: A (Down payment), B (Financial assets down payment), F

(Down payment request), I (Intangible asset down payment), M (Tangible asset down payment), V(Stocks down payment)

Customers - Special G/L transactions to be paid: A (Down payment), F (Down payment request)




© SAP AG of 101

7/27/2019 B29 Core FI





Selection for Payment Program → Set Up All Company Codes


Set Up Paying Company Codes for Payment Transactions

- minimum amount for which an incoming (€ 1,-) or outgoing payment (€ 5,-) is created.

- Forms and sender details for advice notes and EDI accompanying sheets

Form for the Payment Advice: /SMB15/D_AVIS

EDI Accompanying Sheet Form: /SMB15/EDI_01

Text Elements Letter Header: /SMB15/HEADER

Text Elements Footer Text: /SMB15/FOOTER

Text Elements Signature Text: /SMB15/SIGN

Text Elements Sender: /SMB15/SENDER

(SAP standard is used with minor changes)





Selection for Payment Program → Set Up Paying Company

Codes for Payment Transactions

Set Up Payment Methods for Each Country for Payment Transactions

Specification for each country to setup used payment methods.

Pymt Meth.

Name PaymentMethod for

PaymentMethodClassif.

RequiredMaster RecordSpecifications

Doc.Typefor Pymt

Clea-ringDoc.Type

PaymentMediumProgram

Name of PrintDataset

A Bankabbuch(Bank directdebit)

IncomingPayments

DebitMemo


E Bankeinzug(Automatic

debit)

IncomingPayments

DebitMemo

Bank Details

Collection Authorization

ZP ZV RFFOD__U LIST3S

L Ausl.überw.(Foreign banktransfer)

OutgoingPayments

BankTransf.



Bank Details


O Orderscheck Outgoing Check Street, P.O. ZS ZV RFFOD__S LIST1S

© SAP AG of 101

7/27/2019 B29 Core FI



(Order check) Payments Box or P.O.Box Pst Code

P Postgiro(Post officebank transfer)

OutgoingPayments

PostOfficeCurr. AcctMethod?



R Europaüberw(EU internaltransfer)

OutgoingPayments

BankTransf.

EUInternalTransfer


Bank Details


S Scheck(Check)

OutgoingPayments

Check

Allowedfor

PersonnelPayments



U Überweisung(Banktransfer)

OutgoingPayments

BankTransf.



All payment methods except “EU internal transfer”: all currency are allowed for payment.

Payment method R (EU internal transfer): only currency EUR is allowed for payment.


Transaction Code SPROIMG Menu Financial Accounting → Accounts Receivable / Accounts


Selection for Payment Program → Set Up Payment Methods

per Country for Payment Transactions

Set Up Payment Methods for Each Company Code for Payment Transactions

Define which payment methods can be used per company code and determine the conditionsunder which a payment method should be used.

The system contains the following payment methods and settings for company code BP01:PmntMeth.

MinimumAmount/MaximumAmount (in EUR)

Foreign Payments/Foreign Currency Payments

Grouping of Items

Bank SelectionControl

A 5.00

200,000.00




E 5.00 Foreign Currency Allowed SPACE No Optimization

© SAP AG of 101

7/27/2019 B29 Core FI



200,000.00

L 0

1,000,000.00





O 0

100,000.00


P 5

200,000.00


R 0

5,000.00



Cust/Vendor Bank Abroad

Allowed?


S 0

100,000.00





U 0

1,000,000.00




PmntMeth.

Form DataForm for the PaymentTransfer Medium

Form DataNext Form

Pyt Adv. Ctrl Drawer

A /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2Rows;


Name 1

Name 2

12345 location

E /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2Rows;


Name 1

Name 2

12345 location

L /SMB15/D_Z1_98 /SMB15/D_DTA Restricted to 2Rows;


Test name

Test phonenumber

0123/456 - 789

Street 123

D-12345

© SAP AG of 101

7/27/2019 B29 Core FI



location

O /SMB15/D_ORDSCH As Many as Req

NoPytAdv

Name 1

Name 2

D-12345location

P /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2Rows;


Name 1

Name 2

D-12345location

R /SMB15/D_EURO /SMB15/D_DTA Restricted to 2Rows;


Name 1

Name 2

Street 123

D-12345location

S /SMB15/D_SCHECK As Many as Req

NoPytAdv

Name 1

Name 2

D-12345location

U /SMB15/D_TRNSFR /SMB15/D_DTA Restricted to 2Rows;


Name 1

Name 2

12345 location

Bank Determination - Ranking Order

The program selects banks or bank accounts from which payment is to be made. Thereforefollowing specifications are made:

- Ranking order of banks: specify which house banks are permitted and rank them in a list.

- Bank accounts: specify which bank account is to be used for payments for each house bank and paymentmethod (and currency, if required) and to which G/L account the payment is posted.

- Available amounts: for each account at a house bank, the amounts (incoming and outgoing payments) thatis available needs to be spedified.

- Value date: specify how many days elapse between the posting date of the payment run and the valuedate at the bank, dependent on the payment method, bank account, payment amount, and currency.

The amounts for outgoing payments are set to zero for all banks (except Deutsche Bank DB),since payments are only effected by Deutsche Bank. Only incoming payments are posted for theother banks.

Reason: If Treasury is also installed, the cash concentration function is activatedhere; in other words, all the other accounts are cleared and transferred to theDeutsche Bank accounts in the evening.


© SAP AG of 101

7/27/2019 B29 Core FI







Selection for Payment Program → Set Up Bank Determination





Please refer to Manual Payments

You can use block keys to block an open item or an account for payment as follows:

1. In automatic payments, the block becomes effective if it has been

- Defined in the master record or

- Entered in the document

If the block is entered in the master record, all the open items in this account arecontained in the exception list. The block keys '*' and '+' in the master record havecertain special features.

If you set block key * in the master record, all the items in the account are skipped inautomatic payments.

If you set block key + in the master record, all the items that have not been explicitlyassigned a payment method are skipped. This block key has been deleted, since

these items also have to be paid.Note that block key 'A' is usually set automatically when a down payment is entered.You should, therefore, not delete 'A' or use it for other purposes.The “Change in Pmnt Prop.” indicator for the block key specifies whether a block keycan be set or removed in payment proposal processing.

2. A block key in the document only affects manual payments if the “ManualPayments Block” indicator is set for the block key. A block key set in the master record does not affect manual payments. You can set the system to output a suitablewarning message, however. In this case, message 671 for application area F5 hasbeen set as a warning in message control.

3. The “Not Changeable” indicator must be set for the block key for payment releasein Financial Accounting. This indicator is only relevant for payment orders, however,

and is, therefore, not set here.

Changed Message Control

Message 671 (Account & has payment block "&") is defined as a warning for the application areaF5.

(SAP standard)

© SAP AG of 101

7/27/2019 B29 Core FI




For following transaction keys the posting keys and special G/L indicators are defined for automatic postings by the payment program:

Transaction ZBA (= Payment program: bank posting)

Transaction ZWO (= Payt program: bank bill liability)

Transaction ZWE (= Payt program: bill exch/bill payt reqst) (1)






Automatic Outgoing Payments→ Automatic Posting →


Prepare Automatic Postings for Payment Requests

Transaction ZAF (= Payment requests): posting keys and special G/L indicator P are defined.

(SAP standard settings)

A payment request is not required, since the special G/L indicator for F for customer downpayment requests already exists. In Germany, no relevant business transaction exists for payment request P.

Branch Assignment for Automatic Postings

Head office/branch office processing is not supported.

Define Sender Details for Payment Forms

The following text elements are used:

Letter Header: /SMB15/HEADER

Footer Text: /SMB15/FOOTER

Signature Text: /SMB15/SIGN

Sender: /SMB15/SENDER





Automatic Outgoing Payments→ Payment Media → Define

© SAP AG of 101

7/27/2019 B29 Core FI



Sender Details for Payment Forms

Assign Payment Forms for Payment Method in Company Code

Allocate Forms to Paying Company CodeCoCd Form for the Payment Advice EDI Accompanying Sheet Form

BP01 /SMB15/D_AVIS /SMB15/EDI_01

Allocate Forms to Payment Method in Company CodePmntMethod

Form for the Payment Transfer Medium

Next Form

A /SMB15/D_TRNSFR /SMB15/D_DTAE /SMB15/D_TRNSFR /SMB15/D_DTAL /SMB15/D_Z1_98 /SMB15/D_DTAO /SMB15/D_ORDSCHP /SMB15/D_TRNSFR /SMB15/D_DTAR /SMB15/D_EURO /SMB15/D_DTAS /SMB15/D_SCHECKU /SMB15/D_TRNSFR /SMB15/D_DTA





Automatic Outgoing Payments→ Payment Media → Make

Settings for classic Payment Medium Programs → Assign

Payment Forms for Payment Method in Company Code

Assign Payment Medium Program for Payment Method in Country

In this activity, for each payment method you assign the classic payment medium program(RFFO*) that is used for creating payment media in that country.

PaymentMethod

Program Name of the Print Dataset Print Dataset for B/Exch.

A RFFOD__U LIST3SE RFFOD__U LIST3SL RFFOD__L LIST4SO RFFOD__S LIST1SP RFFOD__U LIST3SR RFFOD__L LIST4SS RFFOD__S LIST1SU RFFOD__U LIST3S

Payment Media: Define Sort Variants

In this activity you define the sort variants for payment medium forms (such as payment advicenotes, checks, bills of exchange). You can choose sorting by the payee's postal code, by thepayment method supplement, by the accounting clerk, or by a combination of these fields.

Standard settings are used: via the currency and the payee's bank details.

© SAP AG of 101

7/27/2019 B29 Core FI







Variants→ Payment Media: Define Sort Variants

Payment Media: Define Sort Variants for Line Items

In this step, you define the sort variants for line items. Sorting can be set, for example, byreference document numbers or posting date.

Standard settings are used :via document date and Reference number.





Variants→ Payment Media: Define Sort Variants for Line Items

Define Instruction Keys

Instruction Keys: controls what instructions for making a payment order are sent to participating banks. Thekey can be specified in vendor master records or in your house banks.

For payment method K (check), L (foreign bank transfer) and R (EU internal transfer) an instruction key isspecified.

No instruction key is defined for payment method U (Überweisung (Bank transfer)), since you canalso carry out bank transfers to foreign vendors that have a bank account in your country. You donot need an instruction key here, however, since a message (Z1) is not required.

You need an instruction key for payment method A because a bank direct debit isalso allowed for foreign customers and banks.




Payable → Business Transactions → Outgoing Payments → Automatic Outgoing Payments→ Payment Media → Data

Medium Exchange → Define instruction keys



Lost Cash Discount


© SAP AG of 101

7/27/2019 B29 Core FI





Accounts for Rounding DifferencesPlease refer to Account determination Payments

When you clear foreign currency documents in which the foreign currency and local currency arenational currencies, the differences that occur are rounding differences rather than exchange ratedifferences. For rounding differences, you have to define precisely one account in the chart of accounts so that you can post these amounts.



Accounts must be set as being relevant to tax in order for a tax adjustment to be posted.

In this step, you can define accounts for payment differences involving an alternativecurrency. You need these accounts if you use an alternative payment currency for manual or automatic payments.

The accounts set here are accounts for exchange rate differences, which are set inthe chart of accounts as being “non tax relevant”. This explains why no taxadjustment is carried out when the open items are cleared.



Account determination is not necessary, since the accounts defined in account determination for transaction KDW are accounts for exchange rate differences (transaction: OBXO). These are setin the chart of accounts as being “non tax relevant”. This explains why no tax adjustment iscarried out when the open items are cleared and a clearing account is not required.



.3.1.3.4.8 Manual Clearing

Prerequisites

Line Layout variants

© SAP AG of 101

7/27/2019 B29 Core FI




Additional Fields for Line Item Display








.3.1.3.4.9 Automatic Clearing

Use

In this step, you specify criteria that will be used to group the open items of an account for automatic clearing. The program clears open items in a group if the balance in local currency andforeign currency is zero and contents of several fields (which are defined in customizing) areidentical.

PrerequisitesClearing Rules

Rules defined for automatic clearing for account type D (customer), V (vendor) and S (general ledger):

Criterion 1: ZUONR (Assignment)

Criterion 2: VBUND (Trading Partner)




Payable → Business Transactions → Open Item Clearing →

Prepare Automatic Clearing

© SAP AG of 101

7/27/2019 B29 Core FI



.3.1.3.4.10 Dunning

Use

In the following section, you make the specifications required for the dunning program.

You can use the dunning program to dun both customers and vendors.

Prerequisites

Dunning Areas

Dunning areas are not used. No dunning areas have been defined for company code BP01.

Dunning Block Reasons

You define the reasons for a dunning block under a key. The key can be entered in an item or in the accountof a business partner. Blocked items or accounts are not considered for the dunning run.

Dunning Procedures

You enter the settings that control the dunning program by:

-Specifying the company codes to include in dunning.- Setting up the dunning procedure you want to use (dunning interval, grace periods for the duedate determination and number of dunning levels)

- Setting the dunning charges.

- Specifying the net payment due date at which a particular dunning level is reached.

- Specifying the dunning notice you want to send to your customers.

The following dunning procedures have been defined for dunning customers:

0001 Four-level dunning notice, every two weeks

Z030 (1) Interest calculation after 30 days(1) Not SAP standard

Dunning Procedure 0001

The standard settings have been kept.

Dunning Procedure Z030

Dunning procedure Z030 specifies that customers who do not pay within 30 days areautomatically in arrears. The customers receive a dunning notice without interest amounts. Fromthen on, interest is calculated for the open items using the interest calculation program (see also

the section on the interest calculation program).

Dunning Interval in Days 14

Min. Days in Arrears (Acct) 0

Line Item Grace Periods 0

Sp. G/L Indicator: Customers F Down payment request

© SAP AG of 101

7/27/2019 B29 Core FI



Sp. G/L Indicator: Vendors

Standard Transaction Dunning X

Interest Indicator 01

Ref. Dun. Proced. Z030

The two dunning levels are set as follows:

Dunning Level 1 Dunning Level 2

Days in Arrears 0 Days in Arrears 14

Calculate Interest? X Calculate Interest? X

Payment Deadline 7 Payment Deadline 10

Print All Items X Print All Items X

Always Dun? Always Dun? X




Payable → Business Transactions → Dunning → Dunning

Procedure

Groupings

Dunning notices are generally created per business partner. In special cases, it can be useful togroup together the open items of a business partner according to certain aspects and dun theseitems together.

SAP standard is used.

Interest

In the dunning program, an interest rate of 7.68% has been defined for interest indicator 01 andthe currency EUR. This interest rate is the same as the rate set for the interest calculationprogram and is calculated from the discount rate (2.68%) and a surcharge of 5%.




Payable → Business Transactions → Dunning → Dunning

Procedure → Define Interest Rates

Dunning Forms

The following forms are used for dunning program:

Dunning procedure 0001:

© SAP AG of 101

7/27/2019 B29 Core FI



Dunning Level Form

1 /SMB15/DUNN_01 - Dunning form


3 /SMB15/DUNN_02 - Dunning form with interest

4 /SMB15/DUNN_02 - Dunning form with interest

Legal DunningProceedings

/SMB15/DUNN_03 - Int. dunn. notice for respondent

Dunning Procedure Z030:

Dunning Level Form



Legal Dunning

Proceedings

/SMB15/DUNN_03 - Int. dunn. notice for respondent




Payable → Business Transactions → Dunning → Printout → Assign Dunning Forms

Sender Details

The following standard texts have been created for company code BP01.

Header Text /SMB15/HEADER

Footer Text /SMB15/FOOTER

Signature Text /SMB15/SIGNATURE

Sender /SMB15/SENDER




Payable → Business Transactions → Dunning → Printout → Define Sender Details for Dunning Forms

© SAP AG of 101

7/27/2019 B29 Core FI



.3.1.3.4.11 Interest Calculation

Use

Reference Interest Rate

A new reference interest rate has been created:

Ref. Int. Rate Long Text

ZDISEUR Diskontsatz der Deutschen Bundesbank (Discount rate of German CentralBank)




Payable → Business Transactions → Interest Calculation →

Define Reference Interest Rates

Time-Dependent Interest Terms

A premium of 5% on the discount rate has been defined for calculating interest on arrears(interest calculation indicator 01).

Int. Calc.Indicator

CurrencyKey

Eff. from Term (Debit/CreditInterest)

ReferenceInterest

Premium

01 EUR 01/01/2000 Debit interest ZDISEUR 5 %

01 EUR 01/01/2000 Credit interest ZDISEUR 5 %

To carry out the activity, choose one of the following navigation options:Transaction Code SPRO


Payable → Business Transactions → Interest Calculation → Define Time-Based Terms

Values for Reference Interest Rates

An interest rate of 2.68% has been defined for the discount rate.

Reference Eff. from Int. Rate

ZDISEUR 01/01/2000 2.6800000




Payable → Business Transactions → Interest Calculation → Enter Interest Values

© SAP AG of 101

7/27/2019 B29 Core FI



Account Determination for Interest in Arrear

Following accounts are set up to post AR interests:

Interest received: 578100 Other interest and similar revenue

Interest paid: 759100 Other interest and similar expenses

Document type DV has been created for posting the interest. This enables you to exclude theinterest when performing dunning, for example.





Interest Posting → A/R: Calculation of Interest on Arrears

Printout

Int. Ind. Company Code Form

01 BP01 /SMB15/DUZI_01





Printout → Assign Forms for Interest Indicators


BC Set configuration data: SMB15_3400_AR_S053_B29.DOC

.3.1.3.5 Bank Accounting

Use

In this step, you make the Customizing settings for the configuration.

Procedure Access the Customizing activity as described in the BC Set configuration data and make thesettings according to the table values listed in this documentation.

BC Set configuration data: SMB10_3500_BANK_S008_B29.DOC

.3.1.3.5.1 Bank Accounting: Cash Journal

In the following activities settings are made for a cash journal.

© SAP AG of 101

http://c/WINNT/Temp/SAP_RM_DOC/20040219/ACC/SMB15_3400_AR_S053_B29.DOC


http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB10_3500_BANK_S008_B29.DOC




7/27/2019 B29 Core FI



Set up Cash Journal

Cash journal: 0001 - Petty Cash EUR

G/L account 288010 has been assigned to the cash journal

Assigned document types: AB – for G/L account postings

DZ – for customer receipts/paymentsKZ - for vendor receipts/payments



IMG Menu Financial Accounting → Bank Accounting → Business

Transactions → Cash Journal → Set Up Cash Journal

In the master data, account 288010 has been set to “Post Automatically Only”. In

addition, the sort key has been set to 001 (posting date) and the account text hasbeen set to “PETTY CASH EUR”. The account currency is EUR. “Only Balances inLocal Crcy” has not been set.

Set Up Number Ranges

A number range is set up for company code BP01 (same as SAP standard for company code0001)

Create, Change, and Delete Business Transactions

The following cash journal business transactions have been set up:

Transaction BusinessTransaction Type

G/Laccount

TaxCode

Cash journal businesstransaction

1 E (Expenses) 682100 V0 POSTAL COSTS W/O TELEPH.

2 E (Expenses) 682000 V1 SHIPPING COSTS

3 E (Expenses) 680000 V1 OFFICE SUPPLIES

4 D (Customer posting)

AR: PAID TO/RECEIPT FROM

5 K (Vendor posting) AP: PAID TO/RECEIPT FROM

6 B (Payment to bankaccount)

280015 PAYMENT TO DT. BANK


281015 PAYMENT TO DRESDNER BK.


282015 PAYMENT TO BW.BANK

9 C (Receipt from 280014 RECEIPT FROM DT. BANK

© SAP AG of 101

7/27/2019 B29 Core FI



bank account)

10 C (Receipt frombank account)

281014 RECEIPT FROM DRESD.BANK


282014 RECEIPT FROM BW. BANK

12 R (Revenue) 500900 A1 DOMESTIC SALES IN CASH


285015 PAYMENT TO POSTBANK


285014 RECEIPT FROM POSTBANK




Transactions→ Cash Journal → Create, Change, DeleteBusiness Transactions

Print Parameters for Cash Journal

To print the cash journal and the cash journal receipts, you have to set up the corresponding print programparameters per company code.

SAP standard is used.

Assign Print Program to Correspondence SAP18 (Cash Journal)

Print Program: RFKORD80

used variant: SAP18




Transactions→ Bill of Exchange Transactions → Bill of

Exchange Receivables → Post Bill of Exchange Receivable →

Carry Out and Check Settings for Correspondence

Assign Forms for Correspondence (Cash Journal)

Program RFKORD80: Form /SMB15/CASH_Doc



© SAP AG of 101

7/27/2019 B29 Core FI







Define Sender Details for Correspondence

The following Text IDs are used:/SMB15/HEADER, /SMB15/FOOTER, /SMB15/SIGN,/SMB15/SENDER







Access the Customizing activity as described in the BC Set configuration data and makethe settings according to the table values listed in this documentation.

BC Set configuration data: SMB15_3510_CASHJOURNAL_S026_B29.DOC

.3.1.3.5.2 Bank Accounting: Electronic Bank Statement

Global Settings for Electronic Bank Statement

Create Account Symbols and assign them to Account Symbols:You create account symbols to define the posting specifications. Before the posting rules areused, the individual account symbols are replaced by the account to which items are to beposted.In this step, you define how accounts are determined for a particular account symbol. To avoidyou having to define a separate account symbol for each individual house bank account (eachwith a different G/L account and separate bank clearing accounts), the G/L Acct field can containa masked output.

Account Text AcctMod.

Currency G/L Acct

AUSG-UEBERW-AUS Foreign out. transf. + + +++++++++3

AUSG-UEBERW-INL Domestic out. transf + + +++++++++2

BANK Bank account + + ++++++++++

BANKEINZUG Bank collection + + +++++++++4

BANKGEBUEHREN Bank cost + + 675000

BARAUSZAHLUNG Cash payment + + ++++++++14

BAREINZAHLUNG Cash deposit + + ++++++++15

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3510_CASHJOURNAL_S026_B29.DOC



7/27/2019 B29 Core FI



GELDEINGANG Cash receipt + + +++++++++9

SCHECKAUSGANG Outgoing checks + + +++++++++1

SCHECKEINGANG Incoming checks + + +++++++++8

SCHECKVERRECHNG Check clearing acct + + ++++++++13

SONSTIGE Other bank trans. + + +++++++++5

TREASURYAUSGANG Treasury outg. trans + + ++++++++16

TREASURYAUSGANG Treasury outg. trans + USD ++++++++55

TREASURYAUSGANG Treasury outg. trans + CHF ++++++++65

TREASURYEINGANG Treasury inc. trans. + + ++++++++16

TREASURYEINGANG Treasury inc. trans. + USD ++++++++55

TREASURYEINGANG Treasury inc. trans. + CHF ++++++++65

ZINSAUFWAND Interest paid + + 751000

ZINSERTRAG Interest received + + 571000

Create Keys for Posting Rules:In this step, you create the descriptions for the required posting rules. Each posting rulerepresents the business transaction on the bank statement in the SAP system, such as a checkreceived, a credit memo, or debit memo.

PostingRule

Text

001+ Cash inflow via interim account

002 + Check credit memo through bank

003- Cashed check

004- Domestic transfer

005- Foreign transfer

006- Other disbursements

007+ Other receipts

008- Cash payment

009+ Cash receipt

010+ Collection/direct debit011- Returns collection/direct debit

012- Bank fee

013+ Interest received

014- Interest paid

015+ Payment by credit card

© SAP AG of 101

7/27/2019 B29 Core FI



016- Vendor direct debit

017+ Treasury receipts

018- Treasury disbursements

Define Posting Rules/Posting Specifications:In this step, you create posting specifications for each posting rule. The posting specificationsenable you to define how a particular business transaction (such as a credit memo) is to beposted.Posting specifications comprise one or two posting records Debit → Credit. The first postingrecord is called posting area 1 and usually involves a G/L account posting (BANK ACCOUNT → CASH RECEIPT, for example). The second posting record, which is optional, is called postingarea 2 (CASH RECEIPT → CUSTOMER, for example).Depending on whether a posting transaction affects bank accounting only, or affects both bankaccounting and subledger accounting, you define posting rules either for the first posting areaonly, or for both the first and second posting areas.

PstgRule

PosAr PKey Acct (Debit) PKey Acct (Credit) Doc.Type

PstTy

Cash inflowvia interimaccount

001+ 1 40 BANK 50 GELDEINGANG SA 1

001+ 2 40 GELDEINGANG DZ 8

Check creditmemo throughbank

002+ 1 40 BANK 50 SCHECK-EINGANG

SA 1

Cashed check 003- 1 SCHECK-

AUSGANG

50 BANK SA 4

Domestictransfer

004- 1 AUSG-UEBERW-INL

50 BANK SA 4

Foreigntransfer

005- 1 AUSG-UEBERW- AUS

50 BANK SA 4

Other disbursements

006- 1 40 SONSTIGE 50 BANK SA 1

Other receipts 007+ 1 40 BANK 50 SONSTIGE SA 1

Cash payment 008- 1 BARAUS-ZAHLUNG

50 BANK SA 4

Cash receipt 009+ 1 40 BANK BAREIN-ZAHLUNG

SA 5

Collection/direct debit

010+ 1 40 BANK BANK-EINZUG

SA 5

Returnscollection/direct debit

011- 1 40 SONSTIGE 50 BANK SA 1

© SAP AG of 101

7/27/2019 B29 Core FI



Bank fee 012- 1 40 BANKGEBUEHREN 50 BANK SA 1

Interestreceived

013+ 1 40 BANK 50 ZINSERTRAG SA 1

Interest paid 014- 1 40 ZINSAUFWAND 50 BANK SA 1

Vendor directdebit

016- 1 40 AUSG-UEBERWSGINL

50 BANK SA 1

2 50 AUSG-UEBERWSGINL

KZ 7

Treasuryreceipts

017+ 1 40 BANK TREASURY-EINGANG

SA 5

Treasurydisbursements

018- 1 TREASURY- AUSGANG

50 BANK SA 4

Returns collections/direct debits are posted to the account for other interim postings, since they

need to be postprocessed.

Create Transaction Type:In this step, you create the names and descriptions for the various transaction types required.House banks that use identical lists of business transaction codes (external transactions) canlater be assigned to the same transaction type.

Trans. Type Name

MC MultiCash

Assign External Transaction Types to Posting Rules:In this step, you assign (external) business transaction codes to a posting rule (internal), whichenables you to use the same posting specifications for different business transaction codes.

Ext Trans +/- Post.Rule

IntAlgthm

001 - 003- 012 Outgoing check: check number same aspayment doc. no.

002 - 003- 012 Outgoing check: check number same aspayment doc. no.

004 - 016- 021 Reference document number search

005 - 016- 021 Reference document number search

009 - 011- 000 No interpretation

020 - 004- 019 Reference no. (DME management)

051 + 001+ 021 Reference document number search

070 + 002+ 000 No interpretation

071 + 010+ 019 Reference no. (DME management)

© SAP AG of 101

7/27/2019 B29 Core FI



082 + 009+ 001 Standard algorithm

083 - 008- 001 Standard algorithm


202 + 001+ 021 Reference document number search















814 + 013+ 000 No interpretation


833 + 017+ 001 Standard algorithm

833 - 018- 001 Standard algorithm

UNALLOCATED + 007+ 000

UNALLOCATED - 006- 000

To enable the bank statement to find the item to be cleared in the vendor direct debittransaction, the bank details must be maintained in the vendor master record. The bankstatement finds the vendor using the bank details and the item using the value (if unique).

For algorithm 012, the number interval of the document numbers must be entered in the importreport. For algorithm 026, the number interval of the reference document numbers must beentered (SD number assignment = XBLNR in the FI document). For further information onsearching for the reference document number, refer to SAP Note 0107592.

The UNALLOCATED transaction results in the bank statement being imported, even if theexternal transaction code has not been created in Customizing. The transaction is posted to theinterim account +++++5 (bank subaccount, depending on bank). Take a look at this interimaccount after the bank statement has been imported and post the items to the correct accounts

© SAP AG of 101

7/27/2019 B29 Core FI



where necessary. To ensure that the transaction is contained in the system the next time thestatement is imported, define the new external transaction code in Customizing and assign anappropriate posting rule.

Assign Bank Accounts to Transaction Types:

In this step, you assign each of your bank accounts to a transaction type.

bank key bank account Transaction Type

66220020 1000002 MC

50070010 1133698 MC

82080000 5566645 MC

50070010 5689555 MC

50070010 5689500 MC

To carry out the activities listed previously, choose one of the following navigation options:Transaction Code SPRO


Transactions→ Payment Transactions → Electronic Bank

Statement → Make Global Settings for Electronic Bank

Statement

Define Program and Variant Selection

Transaction FF.5 and FF_5 uses program RFEBKA00.

Transaction FF.6 and FF_6 uses program RFEBKAP0.Transaction FEBC has no restriction.

You can also define your own variant here so that it appears immediately on the screen when youcall up the transaction.

To carry out the activities listed previously, choose one of the following navigation options:



Transactions→ Payment Transactions → Electronic Bank

Statement → Define Program and Variant Selection


BC Set configuration data: SMB15_3520_ELEC-STAT_S027_B29.DOC

.3.1.3.5.3 Manual Bank Statement

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3520_ELEC-STAT_S027_B29.DOC



7/27/2019 B29 Core FI



Create and Assign Business Transactions

In this step, you define an indicator and assign a posting rule for each business transaction.

Tran +- Post.Rule

AcctMod

IntAlgthm

Text

001+ + 001+ + 21 Cash inflow via interim account

002+ + 002+ + Check credit memo through bank

003- - 003- + 12 Cashed check

004- - 004- + 19 Domestic transfer

005- - 005- + 19 Foreign transfer

006- - 006- + Other disbursements

007+ + 007+ + Other receipts

008- - 008- + 1 Cash payment

009+ + 009+ + 1 Cash receipt010+ + 010+ + 19 Collection/direct debit

011- - 011- + Returns collection/direct debit

012- - 012- + Bank fee

013+ + 013+ + Interest received

014- - 014- + Interest paid

016- - 016- + 21 Vendor direct debit

017+ + 017+ + 19 Treasury receipts

018- - 018- + 19 Treasury disbursements

019+ + 017+ + 1 Cash concentration - incoming

020- - 018- + 1 Cash concentration - outgoing

Define Posting Keys and Posting Rules for Manual BankStatement

The posting keys and rules have already been set up for the electronic bank statement. Theposting keys and rules for the manual bank statement are the same as those used for theelectronic bank statement.

Define Variants for Manual Bank Statement

In this step, you create your own account assignment variants for the manual bank statement inorder to adapt the assignment and/or selection of the account assignment fields to meet your company’s needs. One variant is shipped by default. This variant cannot be changed.If you do not want to use the standard variant, you can deactivate it. Any new variants you createmust be activated.

© SAP AG of 101

7/27/2019 B29 Core FI



Variant Lines Description Release

BP01 1 Acct Statement (Bank Ref.) 46C

BP02 1 Acct Statemt (Ref. doc. nr/vend) 46C

BP03 1 Acct Statement (Matchcode) 46C

SAP01 1 Standard 46C

The variants contain the following fields:

• BP01: Transaction, Value Date (sel.), Amount, Customer Number (sel.), Document Number (sel.), Bank Reference/Check (sel.)

• BP02: Transaction, Value Date (sel.), Amount, Reference Document No. (sel.), Customer Number (sel.), Vendor Number (sel.)

• BP03: Transaction, Value Date (sel.), Amount, Customer Matchcode (sel.), Vendor Matchcode (sel.), Document Number (sel.)


BC Set configuration data: SMB15_3530_MAN-STAT_S049_B29.DOC

.3.1.3.5.4 Check Management

Create and Assign Business Transactions

In this step, you define transaction codes for check deposits and assign them to a posting rule.You have to specify these transaction codes in the Tran (Transaction) field on the initial screenfor check deposits.

Tran +- Post. Rule Acct Mod Text

CD01 + CD01 + Direct check deposit

CD02 + CD02 + Check deposit via interim account

Define Posting Rules and Posting Keys for Check Deposit

Two posting rules have been created: Direct check deposit and Check deposit via interim

account. These rules represent two ways of posting checks in the system. If you only want to postthe bank accounting item in the first step and then clear the open customer items, use the Check deposit via interim account transaction. This is of particular importance when you have a lot of checks and you have to ensure that all the checks in Bank Accounting are posted by 10:30 a.m.,for example. Otherwise, you use the Direct check deposit transaction in which the customers arecleared immediately provided that clearing information is available.

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3530_MAN-STAT_S049_B29.DOC



7/27/2019 B29 Core FI



Procedure

Create Account Symbols:In this step, you create account symbols. You will need these symbols at a later stage to definethe posting specifications. Before the posting rules are used, the individual account symbols arereplaced by the account to which items are to be posted.

Symbol Description

SCHECKEINGANG Incoming checks

SCHECKVERRECHNG Check clearing acct

BANK Bank account

Assign Accounts to Account Symbol:In this step, you define how accounts are determined for a particular account symbol. To avoidyou having to define a separate account symbol for each individual house bank account (eachwith a different G/L account and separate bank clearing accounts), the G/L Acct field can containa masked output.

Act Symbol Acct Mod. Currency G/L Acct Acct Symb. Desc.(set automatically)

SCHECKEINGANG + + +++++++++8 Incoming checks

SCHECKVERRECHNG + + ++++++++13 Check clearing acct

SCHECKVERRECHNG + CHF ++++++++65 Check clearing acct

SCHECKVERRECHNG + USD ++++++++55 Check clearing acct

BANK + + ++++++++++ Bank account

Create Keys for Posting Rules:In this step, you define a posting rule for check deposits. The key determines the posting rules for general ledger and subledger accounting. The posting rule represents the typical businesstransactions involved in check deposits.

Posting Rule Text

CD01 Direct check deposit

CD02 Check deposit via interim account

Define Posting Rules:

In this step, you define the posting rules for check deposits and prepare account determination.Depending on whether a posting transaction affects general ledger accounting only, or affectsboth general ledger and subledger accounting, you define posting rules either for one or twoposting areas. You only need one posting area if you post items directly “Bank to incomingchecks” rather than using clearing accounts, for example.

PstgRule

PosAr PKey(D)

Acct (Debit) PKey(C)

Account (Credit) Doc.Type

PstTy

© SAP AG of 101

7/27/2019 B29 Core FI



CD01 2 40 SCHECKEINGANG

DZ 8

CD02 1 40 SCHECKEINGANG

50 SCHECKVER-RECHNUNG

SA 1

CD02 2 40 SCHECKVER-

RECHNUNG

DZ 8

Define Variants for Check Deposits

In this step, you can create your own account assignment variants for check deposits in order toadapt the assignment and/or selection of the account assignment fields to meet your company’sneeds. One variant is shipped by default. This variant cannot be changed.If you do not want to use the standard variant, you can deactivate it. Any new variants you createmust be activated.

Variant Lines Description Release

BP01 1 Check (Check no/Ref./Customer) 46C

BP02 1 Check (Matchcode) 46C

SAP01 1 Standard 46C

The variants contain the following fields:

• BP01: Amount, 10-Digit Check Number, Check Issuer, 8-Digit Bank Key, ReferenceDocument No. (sel.), Customer Number (sel.)

• BP02: Amount, 10-Digit Check Number, Check Issuer, 8-Digit Bank Key, ReferenceDocument No. (sel.), Customer Matchcode (sel.)

Define Value Date Rules

Not relevant. Delta Customizing. Note interaction with CM.

Define Forms

The standard form F_M40S_CHEQUE for check deposits has been copied and assigned to/SMB15/M40S_CHQ.

Access the Customizing activity as described in the BC Set configuration data and make

the settings according to the table values listed in this documentation.BC Set configuration data: SMB15_3540_CHEQ-DEP_S050_B29.DOC

.3.1.3.6 Closing Activities

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3540_CHEQ-DEP_S050_B29.DOC



7/27/2019 B29 Core FI



.3.1.3.6.1 Current and other Assets

Recurring Entries

The number range X1 (default setting) is used for the recurring entry documents.

Run schedules are not used.

Change rules for line items:The following additional entries have been made (no company code specific entries) – to allowchanges to be made for recurring entry documents:

Account Type Field Name Description

D, K, S BSEG-MWSKZ Tax code

D, K BSEG-WMWST Tax amount

D, K, S BSEG-WRBTR Amount

S COBL-AUFNR CO order

S COBL-KOSTL CO cost center

S COBL-PRCTR CO profit center




→ Document → Line Item → Document Change Rules, Line

Item

Balance Carryforward

The retained earnings account is not changed IKR = 350000.

The P&L statement account type is “X”.

Regroup GR/IR Clearing Accounts

The GR/IR clearing accounts contain the following entries:


Adjustment Account Target Account Transaction

IKR IKR IKR

204100 204199 204800 BNG

293000 204299 204800 BNG

204100 204199 204850 GNB

293000 204299 204850 GNG


BC Set configuration data: SMB15_3920_CURRASSETS_S010_B29.DOC

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3920_CURRASSETS_S010_B29.DOC



7/27/2019 B29 Core FI



.3.1.3.6.1.1 Interest Calculation for Balance Sheet Accounts

Prepare Account Balance Interest Calculation for Interest Type 02

Interest calculation frequency: 1 = monthly

Settlement day: 31 = always on the last valid day of the month

Output control = Balance plus interest




Transactions→ Bank Account Interest Calculation → Interest

Calculation Global Settings → Prepare Account Balance

Interest Calculation

Define Reference Interest Rates

UICEUR

UIDEUR

are used for the account balance interest calculation in the closing activities.

Time-Based Terms

Int. Ind. Currency Eff. from Seq. No. ReferenceInterest

02 EUR 01/01/2001 1 UIDEUR

02 EUR 01/01/2001 2 UICEUR

The customer can maintain additional currencies here in the current general ledger settings.

Interest Values

UICEUR from 01/01/2001 = 7.0000 % / UIDEUR from 01/01/2001 = 10.000 %

The customer has to enter the current interest rates manually here in the current general ledger settings.




Transactions→ Bank Account Interest Calculation → Interest

Calculation→ Enter Interest Values

Prepare G/L Account Balance Interest Calculation (Posting)

Interest paid posting:

Interest paid (account symbol 0002) to interest-bearing account (account symbol 2000)

759100 to

© SAP AG of 101

7/27/2019 B29 Core FI



interest-bearing account

Interest received posting:

Interest-bearing account (account symbol 1000) to interest received (account symbol 0001)

Interest-bearing account to

578100

.3.1.3.6.2 Receivables/Liabilities

A/R: Balance Interest Calculation

The settings are described under Interest Calculation for Balance Sheet Accounts.

Receivables: Value Adjustments

Chart of accounts = IKR Account Type = D (Customer accounts)

Customizing (Enhancement) of Doubtful Receivables

Special G/L indicator = D (Doubtful receivables)

Standard entries have not been changed.

Customizing (Enhancement) of Individual Value Adjustment

Special G/L indicator = E (Reserve for bad debt)

Additional entries made for the following accounts:

Reconciliation Account Special G/L Account

250000 254000 (Affiliated companies) NEW

255000 259000 (Investee) NEW

Foreign Currency Valuation

Valuation Methods

KTO = Standard configuration – strict lowest value principle

NWP (lowest value principle) has been created

Description: FC bal. per acct, print LIs, lowest cost principle

NWP postings are performed as follows:

Document Type = SA

Debit Bal. Exch. Rate Type = M

Credit Bal. Exch. Rate Type = M

Determine Exchange Rate Type from Account Balance.

© SAP AG of 101

7/27/2019 B29 Core FI



Open Item Valuation

You can activate the translation posting for each company code.In the following table, the Currency and Crcy Type fields are not maintained (default value = noentry).

For account determination details of loss/gain from exchange rate fluctuation and foreigncurrency valuation see BC-Set documentation.

Comment: The bank subaccounts are not valuated. Before the balance sheet is prepared,accounts are cleared upon presentation of the bank statement.

Balance Valuation

Chart of accounts IKR (Chart of accounts - industry)

Transaction KDB Exch. rate diff. in forgn. curr. balances

Exchange Rate DifferenceKey

Expense Account E/R Gains Acct

( ) 695400 572100

CHF 695400 572100

USD 695400 572100

Key KDF is entered in the account master record (bank account in CHF and USD).

An entry must be made for any additional accounts (balance sheet accounts) managed in theforeign currency.

Regroup Receivables/Payables

The following account determination entries have been made additionally to the standardcustomizing settings:

Receivables – Sort Methods – Additional Settings


Adjst Acct Targ. Acct Transaction

IKR IKR IKR

250000 250099 250020 Rec. > 1 year (V01)

255000 255099 255020 Rec. > 1 year (V01)

Payables – Sort Methods – Additional Settings


Adjst Acct Targ. Acct Transaction

IKR IKR IKR

460000 460099 460020 Paybl. 1-5 years (V03)

470000 470099 470020 Paybl. 1-5 years (V03)

© SAP AG of 101

7/27/2019 B29 Core FI



460000 460099 460030 Paybl. > 5 years (V04)

470000 470099 470030 Paybl. > 5 years (V04)

Changed Reconciliation Account – Additional Settings

Reconciliation Account Adjst Acct Transaction

IKR IKR

250000 250099 A00

255000 255099 A00

460000 460099 A00

470000 470099 A00

Balance Confirmations

Forms for Correspondence and Sender Details

The settings for Forms and Standard texts are described in Basic Setting – Correspondence.

Reply Addresses for Balance Confirmations

A dummy entry is made here. The customer has to maintain the correct information here, such asthe address of the auditing company.

The reply for company code BP01 is 0100 with dummy entry KPMG.

To carry out the activities, choose one of the following navigation options:


IMG Menu Financial Accounting → Accounts Receivable/ Accounts

Payable → Business Transactions → Closing → Count →

Balance Confirmation Correspondence → Define Reply Addresses for Balance Confirmation

Balance Carryforward

The retained earnings account in IKR is 350000.

The P&L statement account type is “X”.


BC Set configuration data: SMB15_3930_ARAPCLOSING_S011_B29.DOC

.3.1.3.6.3 Accrual/Deferral Postings

Customizing Reasons for Reversal

Table T041C-STGRD has been changed in the standard system.

Reversal reason 05 ‘Accrual’ is NOT set as a NEGATIVE POSTING.

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3930_ARAPCLOSING_S011_B29.DOC



7/27/2019 B29 Core FI



Accrual/deferral postings are inverse postings (not negative postings) with a different postingdate.


BC Set configuration data: SMB15_3940_ACCRUALS_S012_B29.DOC

.3.1.3.6.4 Period End Reporting

Financial Statement Versions

The financial statement version is a copy of the IKR version for Accounting. It has been renamedIKRB.

The version was created in accordance with the German Commercial Code §266 and §275 (2).

Returns

Customizing Advance Returns for Tax on Sales/Purchases

The Standard Tax codes of TAXD are being used. For account determination see details in theBC-Set Documentation.

- The account for automatic tax payable transfer postings is 262100.

- The vendor account is set as the tax payable account in delta Customizing.

A separate tax payable account and the posting keys for debit and credit postings to thisvendor account are assigned to the transaction key ‘UMS’ for the chart of accounts used.The tax balances are transferred to this account, provided you do not override it by enteringa different tax payable account in the selection screen. You can use either a G/L account or a vendor account as the tax payable account.

(Basic configuration) Tax payable account = G/L accountIf you use a G/L account, the posting keys assigned to the transaction key ‘UMS’ are used

for the postings to the tax payable account and the tax accounts.(Delta Customizing) Tax payable account = Vendor account

- Tax returns for tax on sales/purchases are not supported. Event. Delta Customizing.

- The taxes on sales/purchases group is not defined.

- Changes to foreign currency translation are part of delta Customizing

- The tax code for non-taxable transactions

V0 and A0 have been configured here as a table entry for company code BP01

- Foreign VAT registration number

BP01: for country FR = FR94409514692

EC Sales Lists

No Customizing activities – predefined form is provided when you call up the report.

Form name: F_ASL_DE and F_ASL_DE_LISTE for address data

German Foreign Trade Regulations (Z4 and Z5A)

Under: Global settings for company code – Additional details – Z5A. The correct entry for therelevant company must be made manually here.

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3940_ACCRUALS_S012_B29.DOC



7/27/2019 B29 Core FI



Enter Company Data: Dummy entries have already been made – a manual entry must be madefor each company.


BC Set configuration data: SMB15_3990_REPORTING_S014_B29.DOC

3.1.4 Core FI – Intercompany Settings

Use

This document describes the additional settings in the SAP R/3 component SAP FI that werecreated to enable intercompany processing. The main settings were created by copying thecompany code BP01 and using the same customizing settings. All basic settings for companycode BP0X are copied from the basic settings BP01. Below a list of the main basic settings madefor company code BP0X.

Company Codes

Use

Company code BP0X has been created for intercompany processing.

Master Data

Use

Chart of accounts IKR has also been set up for company code BP0X.

The following accounts are used for intercompany clearing (cross company postings) : 294001and 294002.

Cross-Company-Code Posting

Use

The following settings have been made:

Posted in BP01

Cleared Against BP0X

Debit Posting Key 40 Credit Posting Key 50

Account Debit 294002 Account Credit 294002

Posted in BP0X

Cleared Against BP01

Debit Posting Key 40 Credit Posting Key 50

Account Debit 294001 Account Credit 294001

Procedure

To carry out the activities, choose one of the following navigation options:

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_3990_REPORTING_S014_B29.DOC



7/27/2019 B29 Core FI




IMG Menu Financial Accounting → GL Accounting → Business

Transactions → Prepare Cross-Company Code Transactions

Global SettingsThe global settings are the same as the settings for company code BP01.

Additional Currencies

For company code BP0X, the group currency (EUR) has been set as the additionalcurrency for the local currency (EUR).

The parameters for translating the currencies are set as follows:

Crcy Type 30 Group currency

Valuation 0 Legal valuation

Ex. Rt. Type M Standard translation at average rateSrce Curr. 1 Translation taking transaction currency as a

basis

TrsDte Type 3 Translation date

These settings have been made in such a way that you can activate the additional currencyseparately via a BC Set.

The currency type must not be changed for company codes that are already in use.

Fiscal Year Variants

Settings made:

CoCd Description Fiscal Year Variant Description

BP0X Company code Germany K4 Calendar year, 4 special periods

Posting Periods

Variant 0001 is used for the posting period. The following setting has been made:

The period 01/2000 to 16/2010 is open for postings for all accounts

The variant has been assigned to company code BP0X.

Document Number Ranges

For company code BP0X, the standard number ranges were taken from the R/3 System.Maximum Difference Between Exchange Rates

10% has been defined as the maximum difference between exchange rates for company codeBP0X.

Field Status Variants

CompanyCode

Field StatusVariant

© SAP AG of 101

7/27/2019 B29 Core FI



BP0X BP01


The tolerance group “blank” has been set up as follows:

Upper Limits for Posting Procedures:

Amount per Document 1,000,000,000,000.00 Amount per Open Item Account Item 1,000,000,000.00

Cash Discount per Line Item 5.000 %

Permitted Payment Differences:

Amount Percent Cash Discount Adj. to

Revenue 100.00 10.0 % 10.00

Expense 100.00 10.0 % 10.00


BC Set configuration data: SMB15_4000_INTERCO_S051_B29.DOC

.3.2 Import/Create Financial Statement Version

Use

To create a balance sheet and profit and loss account statement you need to define a financialstatement version within R/3 Enterprise and assign all accounts to this financial statementversion.

Prerequisites

All general ledger accounts need to be created.

Procedure



IMG Menu Financial Accounting → General Ledger Accounting → Business Transaction → Closing → Documenting → Define

Financial Statement Version

2. Create the financial statement version. On the screen Display View “Financial Statement Versions” choose the button “New entries” and enter the following data.

Field name Description R/O/C User action and values Note

Fin.Stmt.vers Financialstatement version

R IKRB example

© SAP AG of 101

http://var/www/apps/conversion/tmp/scratch_1/ACC/SMB15_4000_INTERCO_S051_B29.DOC



7/27/2019 B29 Core FI




Name Name of thefinancial statementversion

R BP Acc Balance Sheet(§266) & P&L ( §275 Abs.2)

example

Maint. language Maintenance

language

R E example

Chart of accounts

Chart of accounts O IKR enter the chartof account youuse

Save the entries.

3. On the screen Choose View “Financial Statement Versions”: Details choose the button Fin. statement items.

4. For each standard item (Assets, liabilities, net result: profit, net result: loss, P+L result, Notassigned) you can change the key for the financial statement item and you need to enter adescription text. Choose the standard item and choose the button Choose. Enter the values.

5. For each standard item you can create subtimes. Choose the standard item and choose thebutton Create items.

6. On the screen Create items enter the relevant subitems. Enter the values.

7. On the lowest level you need to assign accounts to items. On the screen Change FinancialStatement Version enter choose the item to which you want to assign accounts. Choose thebutton Assign accounts. Enter single account numbers or a range of accounts. Mark if youwant to display the account under this financial statement item if it has

• a debit balance or

• a credit balance or

• not depending on the balance of the account.

8. Save the entries.

For detailed information about the values you should enter please refer to our master excel file of the general ledger accounts or refer to the download of financialstatement version IKRB (SMB15_BALANCE_IKRB.txt).

Result

You can run a daily balance sheet and profit and loss account statement.

Create Output Tax Record (MWST)

Use

The purpose of this activity is to create the output tax record. You need this output tax record tocreate a sales order in SD and post the subsequent invoice to FI.

For further detail how to create master data for condition records please refer to correspondingBPP (Business Process Procedure Pricing – Maintain Condition Records).

© SAP AG of 101

7/27/2019 B29 Core FI



.3.3 Import/Create Tax Codes

Use

You have to define a separate tax code for each country in which one of your company codes islocated.Each code contains one or more tax rates for the different tax types.

Prerequisites

SAP supplies a tax calculation procedure for each country. The procedure comprises a list of allcommon tax types with rules for tax calculation. In addition, tax codes are defined for somecountries.

Procedure

Check the standard tax codes – especially the percentage rate - for your country. Probably youhave to correct the percentage rate.




→ Tax on Sales/Purchases → Calculation→ Define Tax Codes

for Sales and Purchases

2. On the screen Country enter the country code your company is located in.


Country country key R DE example

3. Choose the button Enter.

4. In field “text code” enter or select a tax code.Following table shows you all relevant tax codes with description and relevant percentagerate.

Fieldname

Field name Fieldname

Fieldname

Fieldname

Field name Field name Field name

TaxCode

Description Outputtax(MWS)

Inputtax(VST)

TravelExpenses(%) (VST)

Non-deduct.InputTax (NAV)

Non-deduct.InputTax (NVV)

AcquisitionTax Cred(ESA)

A0 No taxprocedure

0,000

A1 7% domesticoutput tax

16,000


7,000


9,000

© SAP AG of 101

7/27/2019 B29 Core FI



Fieldname


Fieldname

Fieldname



5,000

A5 EC country

taxable/tax-exempt outputtax

0,000

A6 0% output taxon EC deliveryof goods

0,000

A7 0% output taxon ECsubcontracting

0,000

A8 Taxable/tax-exemptdomestic outputtax

0,000

A9 Taxable/tax-exempt foreignoutput tax

0,000

B9 Taxable/tax-exempt outputtax w/o inputtax dedctn

0,000

E1 16% acquisitiontax on ECdelivery of

goods

16,000-

E2 7% acquisitiontax on ECdelivery of goods

7,000-

E3 16% acquisitiontax on ECsubcontracting

16,000-

E4 7% acquisitiontax on ECsubcontracting

7,000-

E7 Acquisition taxon acquisitionwithin EC (§46)

0,000

N1 16% input tax,not deductible,assignable

16,000

© SAP AG of 101

7/27/2019 B29 Core FI



Fieldname


Fieldname

Fieldname


N2 Input tax 16%;of which 20%non-ded., nonassigble

12,800 3,200

N3 Input tax 16%non-deductible,non assignable

16,00

N4 Input tax 7%;20% non-deductible, nonassignable

5,600 1,400

R1 Input tax 7%;20% non-deductible, nonassignable

10,500

R2 8.7% trip costs,miles/kilometersallowance

8,700

R3 13.1% travelexpenses,meals/overnightstay

13,100

U1 16% import tax 16,000

U2 Sales/Purc. Tax16% (UStG §13b; fm 1.1.02)

16,000-

V0 No taxprocedure

0,000

V1 16,0%Domestic inputtax

16,000

V2 7,0% Domesticinput tax

7,000

V3 Domestic inputtax 9%

9,000

V4 5% domesticinput tax

5,000

V8 Taxable/tax-exemptdomestic inputtax

0,000

V9 Taxable/tax-exempt foreigninput tax

0,000

5. Choose the button Enter .

© SAP AG of 101

7/27/2019 B29 Core FI



6. In the screen Maintain Tax Codes: Tax Rates check the tax percentage rate and change it if itis not correct.

7. Save the entries.

.3.4 Set Changes Without Automatic Recording

Use

This step is only necessary if you want to use CATTs to maintain the address data. If you set thesettings manually, no further activities are required here.

.3.5 Create Adress for Accounting Auditor (BalanceConfirmation)

UseIn this step, you define the address to which the customers or vendors are to send their reply for the balance confirmation. Since this address is often different from the company code address,this specification is very important. You can define several addresses under one ID for everycompany code. Specify the required identification for every program run.

Prerequisites

The company code is defined.

Procedure




Payable → Business Transaction → Closing → Count →

Balance Confirmation Correspondence → Carry Out and

Check Settings for Correspondence → Define Reply Addresses

for Balance Confirmation

2. On the screen Change View “Company Code-Dependent Address Data”: Overview choosethe button “New entries” and enter the following data.


CoCd company code R BP01

AdrID addressidentification

R 0100 example

3. Choose Enter .

4. On the screen Edit address: BP01 0100 enter the following data.


Name Name R Wirtschaftsprüfung example

© SAP AG of 101

7/27/2019 B29 Core FI




GmbH

Street/Housenumber

Street/Housenumber

R Walldorfer Str. example

Postal code/City Postal code/City R 69190 Walldorf example

country country R DE example

Time zone time zone R CET example

Language Language R English example

5. Choose Enter .

6. On the screen Change View “Company Code-Dependent Address Data”: Overview chooseSave.

Result

The balance confirmation statement is printed with the address of your accounting auditor.

.3.6 Copy G/L Account Master Data (Company Code) -Intercompany

Use

In this step, you define the G/L accounts for your intercompany code. With the help of a programyou can copy all general ledger accounts of one company code to another company code.

Prerequisites

The company code with its G/L account are defined and the intercompany code is defined.

Both company codes need to use the same chart of account.

Procedure



IMG Menu Financial Accounting → General Ledger Accounting → G/L

Accounts → Master Records → G/L Account Creation and

Processing → Alternative Methods → Copy G/L Accounts →

Copy Company Code

2. On the screen Copy Company Code: G/L Accounts enter the following data.

Field name Description R/O/C User action andvalues

Note

Company code company code R BP0X example

Copy from:Company code

company code R BP01 example

Program control: Test or O ‘’(Blank) ‘x’ for a test run

© SAP AG of 101

7/27/2019 B29 Core FI



Field name Description R/O/C User action andvalues

Note

Test run productive run

‘ ‘ for productive run

3. Choose Execute.

4. You get the message “this is a productive run”. Please choose Enter .

5. You get a list of all created G/L accounts.

Result

The general ledger master data is created in the intercompany code.

.3.7 Set Automatic Recording of Changes

UseThis step is only necessary if you want to use CATTs to maintain the address data. If you set thesettings manually, no further activities are required here.

.3.8 Application modules per Event (Allow Dunning withSAPSCRIPT Forms)

Use

In R/3 Enterprise you have the possibility to use either SAPSCRIPT forms or SMARTFORMS in

the dunning procedure. In this transaction you have to specify which forms are used for dunningin this system.

This table is cross-client. Any changes you make in this table will take effect in allclients of your system.

Prerequisites

You have processed the previous mentioned steps.

Procedure

1. Access the activity using one of the following navigation options:

SAP R/3Role Menu

B29 - Core FI Germany → Installation→ BF31 – Application

modules per Event

Transaction Code BF31


→ Business Transaction Events → Settings → P/S Function

Modules → … of an SAP appl.

© SAP AG of 101

7/27/2019 B29 Core FI



or

SAP R/3Role Menu

B29 - Core FI Germany → Installation→ BF31 – Application

modules per Event

Transaction Code BF31

2. On the Change View Publish&Subscribe BTE: SAP Enhancement: Overview screen, check -and if necessary change - the following entries.

Field name Description User action and values Notes

Event Event (BusinessTransactionEvent)

00001720 this entry alreadyexists

Land Ctr (Country ISOCode)

Blank

Applk Appl.(ApplicationIndicator for

BTE)

FI-FI

Funct Function Module FI_PRINT_DUNNING_NOTICE this function moduleneeds to be entered if SAPSCRIPT formsshould be used

Save your entries.

If you want to use SMARTFORMS then you have to enter for above mentioned event 00001720function module FI_PRINT_DUNNING_NOTICE_SMARTF.Please be aware that in installation guide and configuration guide the set up for customizing isonly made for dunning with SAPSCRIPT forms and not for dunning with SMARTFORMS.

Result

You can run the BPP for dunning using Best Practices SAPSCRIPT forms.

.3.9 Master Data

3.9.1 Bank Master Data

Use

In the following subchapter you can create Bank Master Data.

© SAP AG of 101

7/27/2019 B29 Core FI



Bank Master Data is used in Business Process Procedure BPP of BB B29 (Core FI) as well as inBPP of logistics BB of Layer 0 and Layer 1.

We recommend to create bank master data. About 30 real-life “model banks” will be created.

Prerequisites

You have activated the BC Sets or set up the customizing manually.

.3.9.1.1 Create Bank Master Data

Use

If you want to run the automatic payment run program or if you want to post a bank statementautomatically you need to set up bank master data in your system.

ProcedureChoose the menu to create bank master data manually.


Transaction Code FI01

SAP Menu Accounting → Financial Accounting → Banks → Master Data

→ Bank Master Record → Create

2. On the screen “Create Bank: Initial Screen” enter the following data:

Field name Description R/O/C User actionand values

Note

Bank Country bank country R DE exampleBank Key bank key R 50070024 e.g. in Germany you use

bank number as bank key


4. On the screen Create Bank: Detail Screen enter the following data:


Note

Bank Name bank name R DeutscheBank 24

example

City city R 60254

Frankfurt,Main

town where the bank is

located


6. Save the data.

To enter all relevant bank master data which you need later on e.g. for the BPP (BusinessProcess Procedure) please refer to the file SMB15_FI01_C102_B29.TXT.

© SAP AG of 101

7/27/2019 B29 Core FI



Result

You have created some bank master data.

Procedure

Another alternative to create bank master data is the import using programs.

Appropriate settings have to be made for the relevant country under “Set Country-SpecificChecks”. These settings determine whether report RFBVALL_0 (banks are imported by banknumber) or report RFBVBIC (banks are imported by SWIFT code) is used when the bank master files are imported. No report exists for France that imports banks by bank number.

Execute transaction SA38 to run those reports and refer to report documentation.

3.9.2 GL Account Master Data

UseIn the following subchapter you can change GL accounts.

General ledger accounts are used in Business Process Procedure BPP of BB B29 (Core FI) aswell as in BPP of other BB of Layer 0 and Layer 1. We recommend to change the GL accounts.Otherwise you are not able to run further BPP.

Prerequisites

You have created the general ledger accounts automatically with BC-Sets or entered themmanually.

.3.9.2.1 FS00: Maintain House Bank

Use

If you want to run the automatic payment run program or if you want to post a bank statementautomatically you need to set up the bank identification in your corresponding general ledger master data.

Prerequisites

You have set up house bank identification and bank account identification in customizing and youhave created general ledger accounts.

Procedure

Choose the menu to change a general ledger account manually.


Transaction Code FS00

© SAP AG of 101

7/27/2019 B29 Core FI



SAP Menu Accounting → Financial Accounting → General Ledger →

Master Records → Individual Processing → In Company Code

2. On the screen “Display G/L Account Company code data” select in SAP menu → G/Laccount → Change.

3. On the screen Change G/L Account Company code data enter the following data:


Note

GL AccountNo.

general ledger accounts number

R 280000 account number for “Deutsche Bank – domestic”

CompanyCode

company code R BP01 example

4. Choose “Create/Bank/Interest”.

5. On the screen Change G/L Account Company code data enter the following data:


Note

House bank house bank O DB identification set up incustomizing

Account ID accountidentification

O GIRO identification set up incustomizing


7. Save the data.

To enter all relevant bank master data which you need later on e.g. for the BPP (BusinessProcess Procedure) please refer to the file SMB15_FS02_L006_B29.TXT.

Result

You have entered the house bank identification and bank account identification in general ledger accounts.

3.9.3 Customer Master Data

Use

In the following subchapters you can create customer master data.

Customer master data is used in Business Process Procedure BPP of

- BB B29 (Core FI)

- BB B44 (Asset Management)

- BB B46 (Cash Management).

We recommend to create customer master data if you want to run BPP of those BB.

© SAP AG of 101

7/27/2019 B29 Core FI



Prerequisites

You have activated the BC Sets or set up customizing manually.

.3.9.3.1 Create Customer Master DataUse

Create Customer Master Data in the system.

If your customer take part in the automatic payment run (you use payment method “automaticdebit” or “bank direct debt”) then you have to set up bank data for this customer.

If your customer does not take part in the automatic payment run (you do not use paymentmethod “automatic debit” or “bank direct debt”) then you do not need to set up bank data for thiscustomer.

Prerequisites

Customizing is set up correct.

Procedure

For further detail how to create customer master data please refer to corresponding BPP(Business Process Procedure).

For further detail which customer master data you need to set up to run later on through BPPplease refer in addition to file SMB15_FD01_L003_B29.TXT.

.3.9.3.2 Create/Change customer credit limit

Use

If your customer take part in the automatic credit limit check then you have to set up credit limitsfor these customer.

Prerequisites


Procedure

For further detail how to create customer master data please refer to corresponding BPP(Business Process Procedure).

For further detail which customer master data you need to set up to run later on through BPPplease refer in addition to file SMB15_FD32_L004_B29.TXT.

© SAP AG of 101

7/27/2019 B29 Core FI



.3.9.3.3 Create One-Time Customer Master Data (Domestic;Accounting)

Use

One-time customer master data are used to keep master data entries low.

Prerequisites


Procedure

For further detail how to create one-time customer master data please refer to correspondingBPP (Business Process Procedure).

For further detail which customer master data you need to set up to run later on through BPPplease refer in addition to file SMB15_FD01_C006_B29.TXT.

3.9.4 Vendor Master Data

Use

In the following subchapters you can create vendor master data.

Vendor master data is used in Business Process Procedure BPP of

- BB B29 (Core FI)

- BB B44 (Asset Management).

We recommend to create vendor master data if you want to run BPP of one of those BB.

Prerequisites

You have activated the BC Sets or set up customizing manually.

.3.9.4.1 Create Vendor Master Data (Accounting)

Use

You need to set up vendor master data in the system.

Prerequisites


Procedure

For further detail how to create vendor master data please refer to corresponding BPP (BusinessProcess Procedure).

© SAP AG of 101

7/27/2019 B29 Core FI



For further detail which vendor master data you need to set up to run later on through BPP pleaserefer in addition to file SMB15_FK01_L001_B29.TXT.

.3.9.4.2 FK02: Change Vendor - enter bank data to vendor

.3.9.4.3 Use

You need to set up additional bank accounts to your vendor master data in the system.

Prerequisites


Procedure

For further detail how to create vendor master data please refer to corresponding BPP (BusinessProcess Procedure).

For further detail which vendor master data you need to set up to run later on through BPP pleaserefer in addition to file SMB15_FK01_L002_B29.TXT.

.3.9.4.4 Create One-Time Vendor Master Data (Accounting)

Use

One-time vendor master data are used to keep master data entries low.

Prerequisites


Procedure

For further detail how to create one-time vendor master data please refer to corresponding BPP(Business Process Procedure).

For further detail which vendor master data you need to set up to run later on through BPP pleaserefer in addition to file SMB15_FK01_C003_B29.TXT.