806_BB_ConfigGuide_EN_DE

EHP4 for SAP ERP 6.0

June 2010

English

Liquidity Forecasting (806)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Liquidity Forecasting (806): Configuration Guide

Copyright

© 2010 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 components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, 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 technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 23


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 field names, screen titles, pushbuttons as well as menu names, paths, and options.

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 key words 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 as names of installation, upgrade and database tools.

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

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

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



Content1 Purpose............................................................................................................................. 5

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

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

2.2 Information about the Technical Environment.........................................................6

2.3 Defining and Naming the Systems Involved............................................................6

2.3.1 Using ALE as Integration Technology.................................................................6

2.3.2 Using SAP PI as Integration Technology.............................................................7

2.3.3 Using B1i as Integration Technology:..................................................................7

3 Configuration.....................................................................................................................8

3.1 Prerequisites............................................................................................................8

3.2 Subsidiaries.............................................................................................................8

3.2.1 Standard Configuration........................................................................................8

3.2.2 Extended Selections............................................................................................8

3.3 Headquarters...........................................................................................................8

3.3.1 Define Mapping Rules.........................................................................................8

3.3.2 Maintain Mapping Rules....................................................................................10

3.4 Check Technical Installation..................................................................................16

4 Optional Settings for Extended Selection (Purchase Orders and Sales Orders).............17

4.1 Define Component FDIS........................................................................................17

4.2 Activate the Component FDIS...............................................................................17

4.3 Include Purchase Orders.......................................................................................18

4.4 Include Purchase Requisitions..............................................................................18

4.5 Assign Planning Levels for Logistics......................................................................19

5 Prepare Productive Startup and Data Setup....................................................................21

5.1 Activate Company Code........................................................................................21

5.2 Reconciliation Activities before Start of CM and LF...............................................21

5.2.1 Customer / Vendor Data....................................................................................22

5.2.2 Data Setup........................................................................................................22

5.2.3 Data Reconciliation............................................................................................23

5.2.4 Correct Data......................................................................................................23

5.2.5 Check Customizing............................................................................................23

6 Appendix.......................................................................................................................... 23



Liquidity Forecasting: Configuration Guide

1 PurposeThe purpose of this document is to describe the configuration steps required to enable the automated transfer of cash management data, using the existing system landscape, between a subsidiary and the central treasury system at the headquarters (parent company).

The system landscape in use at the headquarters and the subsidiaries cannot be predicted, so automated installation is not currently available. As a result, the configuration must be performed manually.

The following information assumes that SAP Best Practices Baseline package Germany has been implemented in the headquarters’ system. The content of this document is aligned with SAP Best Practices Baseline package Germany.

The configuration described in this document is not specific to any particular country. However, some of the data that appears within the document is specific to Germany, because the examples are taken from the SAP Best Practices Baseline package for Germany. In cases where this country-specific data appears, you must replace the data valid for Germany by data valid for your country.

For configuration activities in the headquarters system, only the SAP GUI steps are provided. NetWeaver Business Client navigation is shown only for activities in subsidiaries.



2 Preparation

2.1 PrerequisitesBefore you start installing this scenario, you must install prerequisite building blocks.

These include:

Technical Foundation for Business Network Integration (704)

One of:

o Business Network Integration for SAP PI (705) if you choose to use SAP Process Integration as integration technology, or

o Business Network Integration for ALE (707) if you choose to use Application Link Enabling as integration technology

o Business Network Integration for SAP B1i (706) if you choose to use SAP Business One Integration as integration technology

Building blocks specified as prerequisites for the scenario Cash Management (160). Refer to the Building Block Prerequisites Matrix for SAP Best Practices Baseline (Germany) for further information.

2.2 Information about the Technical EnvironmentBefore starting the configuration, the system landscape (logical names and addresses of the system clients involved, and the assigned company codes) must be specified, as well as the integration technology (ALE, B1i or SAP PI).

You must configure the systems involved to enable the central treasury system to request the relevant data from the subsystems at any time, and also to enable the subsystems to send their data to the treasury workstation.

2.3 Defining and Naming the Systems InvolvedSince you will create your own system IDs in your environment, generic names are used in the examples. You have to replace these generic names with the corresponding system IDs in your environment.

2.3.1 Using ALE as Integration TechnologyAll the systems involved have a defined system ID. This ID is used for the assignment of data source and target. The existing mapping tables in the headquarters’ system cover all the requirements for value mapping for values such as company code, planning level, and planning group.

Headquarters’ System Description Subsidiary’s System

Description

XYZCLNT100 Headquarters ABCCLNT100ABCCLNT200ABCCLNT300…

Subsidiary 01Subsidiary 02Subsidiary 03…



2.3.2 Using SAP PI as Integration TechnologyAll the systems involved use one SAP PI server, which distributes the data to the related physical systems. It is necessary to distinguish between the physical source systems in the existing mapping tables in the headquarters’ system. The mapping tables must be maintained in the same way as for ALE.

Headquarters’ System Description Subsidiary’s System

Description

XYZCLNT100 Headquarters ABCCLNT100ABCCLNT200…

Subsidiary 01Subsidiary 02...

2.3.3 Using B1i as Integration Technology:All the systems involved use one SAP B1i server which distributes the data to the related physical systems. In the existing mapping tables in Headquarters system it is not possible to distinguish between the physical Source Systems. Details are described in chapter “Maintain Mapping Rules” of the Technical Installation (see below).

Headquarter System Description Subsidiary System

Description

B1ISRVR01 Headquarters B1ISRVR01 Subsidiary 01



3 Configuration

3.1 PrerequisitesThe subsidiaries’ systems configured using SAP Business All-in-One have an identical configuration. Planning levels and planning groups have been preconfigured in the building block Cash Management (160). They are maintained in the related configuration tables, and are integrated into the chart of accounts. For details, refer to the documentation for this building block.

As result, YIKR is in the chart of accounts list and is assigned to the company code 1000, for example. In this chart of accounts, the planning levels are maintained in the account master data relevant for cash management.

3.2 Subsidiaries3.2.1 Standard Configuration

The standard configuration of a subsidiary’s SAP Business All-in-One system is predefined for company code, chart of accounts, planning levels, and planning groups.

The company code of a subsidiary’s SAP Business All-in-One system is set to 1000 as standard. You can decide whether the company code in the subsidiary’s SAP Business All-in-One system should remain 1000, or if it has to be changed to match a company code for that subsidiary that is already in use at headquarters. This value can be changed during the installation if required. This is described in the Baseline package documentation.

No changes are made to the other values in the subsidiaries’ systems to minimize effort.

Company code, planning level, planning group, and business area of a subsidiary can be mapped to the corresponding key values in the headquarters’ system. This mapping must be performed in the headquarters’ system. To prepare this mapping, it is necessary to identify the required target values in the headquarters.

The standard configuration includes the selection of cash position data from the bank accounts based on the value date and the open items of accounts payables and accounts receivables based on the due dates.

3.2.2 Extended SelectionsYou can decide to include also purchase requisitions, purchase orders, schedule lines, invoicing plans, and invoice verifications in Liquidity Forecasting. In this case, additional configuration activities are required. They are described below under Optional Settings for Extended Selection (Purchase and Sales Orders).

3.3 HeadquartersAll the mapping activities between headquarters and subsidiaries for company codes, planning levels, and planning groups are performed at the headquarters.

Basically, all involved Subsidiaries must be defined as Company in the Headquarters system with unique Company Codes.

3.3.1 Define Mapping Rules There are various possibilities when implementing the subsidiary systems:



The headquarters already has central cash management in its ERP system.

In this case, the headquarters must provide a mapping guide that enables the mapping of company codes, planning levels, planning groups, and possibly business areas. Particular attention must be paid to the assignment of bank accounts (and related clearing accounts) to the established planning levels at headquarters, in order to enable the mapping of the preconfigured chart of accounts and the related levels in the SAP Business All-in-One subsidiaries.

Headquarters and subsidiaries want to start the cash management solution from scratch.

In this case, it is recommendable to apply the preconfigured values from the SAP Business All-in-One system at each subsidiary in the headquarters’ system for the chart of accounts and the groupings of customers and vendors (for source symbols, planning levels, planning groups, and structure).

General Ledger (G/L) AccountsAccount IDs are not mapped between subsidiaries and headquarters.

G/L accounts in subsidiaries are linked to a company code and assigned to planning levels in their master data.

Acct ID Account Name Co. Code Group Level Src. Grouping

280000 Bank Account 1000 - F0 BNK BANKS

280002 Bank Clearing Account 1 1000 - B1 BNK BANKS

Sub-AccountsSub-accounts in subsidiaries are linked to a company code and assigned to planning groups in their master data.

Acct ID Account Name Co. Code Group Level Src. Grouping

300000 Vendor 1 1000 A1 F1 PSK PERSONS

100000 Customer 1 1000 E1 F1 PSK PERSONS

Specified groups in subledger accounts are assigned to planning levels.

Planning levels are assigned to source symbols. Source symbols are a basis for the assignment to either cash position (BANKS) or liquidity forecast (PERSONS).

This results for a subsidiary in company 1000 in:

Grouping/Structure Planning Level Planning Group Amount

BANKS F0 FI Banks DB EUR Account Amount1

B1 Outgoing Checks DB Outgoing Checks Amount2

PERSONS F1 FI/CV A1 Domestic Paymt Amount3

F1 FI/CV E1 Customer Receipt Amount4

Since only planning levels are defined in G/L accounts and not planning groups, a meaningful account name can be displayed instead of the group description for the bank accounts.

The levels and groups in the above table must be mapped to existing levels and groups at the headquarters, as described below.



3.3.2 Maintain Mapping Rules

All the central company code, level, planning group, and business area values provided below are only examples. Other values may be used as appropriate.

3.3.2.1 Company CodeFrom a technical point of view, there is no need to change the preconfigured company code 1000 in the subsidiaries, but a decision to change the code may be made. In either case, you must maintain the conversion table in the headquarters’ system as described below.

The entries in this table are mandatory, even if the company code at the subsidiary already matches the assigned company code for that subsidiary at the headquarters.

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

SAP System SAP Headquarters’ System

IMG Menu Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Tools → Distributed Cash Management → Central TR-CM System → Define TR-CM Subsystems

Transaction Code FF$A

2. Choose New Entries. 3. In the New Entries: Overview of Added Entries screen, make entries that reflect the

transition of the subsidiary’s company code to the headquarters’ company code in accordance with the integration technology you defined.

The ‘Company Code (Central)’ is the company code used in the Headquarters system for the Subsidiary and the ‘Company Code (Subsystem)’ is the Subsidiary’s Company Code delivered by the subsidiary system. The company defined for the subsidiary in the headquarters system must use with the same posting currency as the subsidiary itself.

Example for ALEHeadquarters XYZCLNT100Subsystem Company Code (Subsystem) Company Code (Central)ABCCLNT100 2000 2000

ABCCLNT300 3000 3000

… Insert entries for all company codes in use for each subsystem connected with the headquarters.

Example for SAP PIHeadquarters XYZCLNT100Subsystem Company Code (Subsystem) Company Code (Central)ABCCLNT100 2000 2000

ABCCLNT400 4000 4000

… Insert entries for all company codes in use for each subsystem connected with the headquarters.



For information on masking subsystem company codes, refer to the related IMG activity documentation.

Example for B1i:Headquarters and Subsidiaries using B1iSubsystem Company Code (subsystem) Company code (central)B1ISRVR01 2000 e.g. 2000

B1ISRVR01 4000 e.g. 4000

If the Company Codes are not unequivocal across the involved physical subsidiary systems you have to configure a value mapping on the B1i Server for the field “Z.BUKRS” that leads to an unequivocal Company Code in the column “Company Code (subsystem)”. You can follow the description in Chapter “Maintaining Value Mapping Tables” of the Technical Installation for B1i (BB-706).

4. Choose Save.

3.3.2.2 Planning LevelThe planning levels and charts of accounts (such as YIKR) delivered with the building block Cash Management (160) are integrated with each other, and changing these values during implementation at the subsidiary is not practical. As a result, the planning level values need to be mapped between the subsidiaries and the headquarters.

You must check if the number of clearing accounts assigned to a bank account is compatible between the subsidiaries and the headquarters. If you use fewer clearing accounts at the headquarters, you can map more than one subsidiary planning level into one planning level at the headquarters.

The planning levels must be unique within one client for all company codes.

The planning levels of each subsidiary must be mapped to corresponding planning levels in the headquarters. The entries in this table are mandatory, even if the planning level at the subsidiary already corresponds with the planning levels at the headquarters.

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


IMG Menu Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Tools → Distributed Cash Management → Central TR-CM System → Convert Sender Level

Transaction Code FF$C

2. Choose New Entries.



3. In the New Entries: Overview of Added Entries screen, make entries that reflect the transition of the subsidiary’s planning level to the headquarters’ planning level.Example for ALEHeadquarters XYZCLNT100 Subsystem Level (Subsystem) Level (Central)ABCCLNT100 AB AB

ABCCLNT100 AU AB

ABCCLNT100 B2 B2

ABCCLNT200 AB AB

... Insert entries for all planning levels in use for each subsystem connected with the headquarters.

For information on masking subsystem levels, refer to the related IMG activity documentation.

Example for SAP PIHeadquarters XYZCLNT100Subsystem Level (subsystem) Level (central)ABCCLNT100 AB AB

ABCCLNT100 AU AB

ABCCLNT100 B2 B2

ABCCLNT200 AB AB

... Insert entries for all planning levels in use for each subsystem connected with the headquarters.

For information on masking subsystem levels, refer to the related IMG activity documentation.

Example for B1i:Headquarters B1ISRVR01 Subsystem Level (subsystem) Level (central)B1ISRVR01 AB e.g. AB

B1ISRVR01 AU e.g. AB

B1ISRVR01 B2 e.g. B2

etc.

Masking of subsystems levels is possible. See the related IMG activity documentation.If the Planning Levels are not synchronized across the involved physical subsidiary systems you have to configure a value mapping on the B1i Server for the field “Z.EBENE” that leads to an unequivocal Key for the Planning Level in the column “Level (subsystem)”. You can follow the description in Chapter “Maintaining Value Mapping Tables” of the Technical Installation for B1i.

4. Choose Save.



3.3.2.3 Planning GroupThe planning groups delivered with the Cash Management (160) scenario have to be integrated with your business partner (customers, vendors) account master data. This can be done as part of the data migration from the legacy system.

You have to check whether the preconfigured planning groups delivered can be used in the SAP Business All-in-One system. Alternatively, the existing planning groups from the legacy system can be used to create a new system of planning groups in the SAP Business All-in-One system.

The planning groups must be unique within one client for all company codes.

The planning groups of each subsidiary can be mapped to corresponding planning groups in the headquarters. The entries in this table are optional. If no entry exists in the mapping table, the planning group of the sending system (the subsidiary) is transferred to the receiving system (the headquarters) without changes.

1. Access the activity using one of the following navigation options:SAP System SAP Headquarters’ System

IMG Menu Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Tools → Distributed Cash Management → Central TR-CM System → Convert Sender Group

Transaction Code FF$B

2. Choose New Entries. 3. In the New Entries: Overview of Added Entries screen, make entries that reflect the

transition of the subsidiary’s planning level to the headquarters’ planning level.

Example for ALEHeadquarters XYZCLNT100Subsystem Group (Subsystem) Group (Central)ABCCLNT100 A1 A1

ABCCLNT100 A1 A2

ABCCLNT100 E1 E1

ABCCLNT200 A1 A1

...



Example for PIHeadquarters XYZCLNT100Subsystem Group (Subsystem) Group (Central)ABCCLNT100 A1 A1

ABCCLNT100 A2 A2

ABCCLNT100 E1 E1

ABCCLNT200 A1 A1

...

For information on masking subsystem groups, refer to the related IMG activity documentation.

Example for B1i:Headquarters B1ISRVR01 Subsystem Group (subsystem) Level (central)B1ISRVR01 A1 e.g. A1

B1ISRVR01 A2 e.g. A2

B1ISRVR01 E1 e.g. E1

etc.

4. Choose Save.

3.3.2.4 Business Area

A mapping table is available for the mapping of business areas in a subsidiary to a corresponding business area in the headquarters. However, this mapping is not currently supported, because there is no data field available in the related IDoc CMSEND.

The entries in this table are optional.

After activation of this mapping function by SAP, you can process the following steps:

1. Access the activity using one of the following navigation options:SAP System SAP Headquarters’ System

IMG Menu Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Tools → Distributed Cash Management → Central TR-CM System → Convert Sender Business Area

Transaction Code FF$D

2. Choose New Entries.



3. In the New Entries: Overview of Added Entries screen, make entries that reflect the transition of the subsidiary’s planning level to the headquarters’ planning level.Example for ALEHeadquarters XYZCLNT100 DESubsystem Business Area (Subsystem) Business Area (Central)ABCCLNT100 01 01

ABCCLNT300 01 02

...

Example for PIHeadquarters XYZCLNT100 DESubsystem Business Area (Subsystem) Business Area (Central)ABCCLNT100 01 01

ABCCLNT200 01 02

...

Example for B1i:Headquarters B1ISRVR01 Subsystem Business Area (subsystem) Business Area (central)B1ISRVR01 01 e.g. 01

B1ISRVR01 02 e.g. 02

etc.

If the Business Areas are not synchronized across the involved physical subsidiary systems you have to configure a value mapping on the B1i Server for the field “Z.xxxxx” that leads to an unequivocal Key for the Business Area in the column “Business Area (subsystem)”. You can follow the description in Chapter “Maintaining Value Mapping Tables” of the Technical Installation for B1i.

For information on masking subsystem business areas, refer to the related IMG activity documentation.

4. Choose Save.



3.4 Check Technical InstallationOnce you have made all the technical settings for the subsidiary link, you should run a check of the settings. This check should be performed regardless of whether you have set up a headquarters system or a subsidiary subsystem.

Access the activity using one of the following navigation options:


IMG Menu Financial Supply Chain Management → Cash and Liquidity Management → Cash Management → Tools → Distributed Cash Management → Check Settings

Transaction Code FF$6

The system generates a log that informs you of the consistency of the settings for the subsidiary link.

This transaction is not currently available for the SAP PI integration technology.



4 Optional Settings for Extended Selection (Purchase Orders and Sales Orders)

In this section, the settings to be made in subsidiary and headquarters are described in parallel as they are similar in most cases.

4.1 Define Component FDISThe component FDIS must be defined in table TRWCI. This is configured in SAP Business All-in-One Baseline packages. In the headquarters’ system, you can check/maintain the component using transaction SM30.

1. Access the transaction using the following navigation option:

For subsidiaries (check)

SAP System SAP Business All-in-One Subsidiary System

Transaction Code SM30, Table TRWCI


For headquarters (add if necessary)


Transaction Code SM30, Table TRWCI

3. Choose New Entries (F5).

4. In the Component field, enter FDIS.

5. Choose Save.

4.2 Activate the Component FDISThe component FDIS has to be activated in table TRWCA.



Transaction Code SM30, Table TRWCA

2. If a To Year value is available for the component FDIS, select Active.

If the component FDIS is not listed, choose New Entries (F5) and make the following entries.

Component To Year Active

FDIS For example: 2050 Select

The To Year value must be greater than or equal to the current year. Make sure that there is only one entry in table TRWCA for component FDIS.





IMG Menu Financial Accounting (new) -> Financial Accounting Global Settings (New) -> Tax on Sales/Purchases -> Basic Settings -> India -> Activate Country Version India for Specific Fiscal Years

Transaction Code SPRO

4. If a To Year value is available for the component FDIS, select Active.

If the component FDIS is not listed, choose New Entries (F5) and make the following entries:

Component To Year Active

FDIS For example: 2050 Select

The To Year value must be greater than or equal to the current year. Make sure that there is only one entry in table TRWCA for component FDIS.

5. Choose Save.

4.3 Include Purchase OrdersFor the selection of purchase orders, certain entries are required in the table TRWPR for certain function modules. They are pre-configured in SAP Business All-in-One Baseline packages.

1. Access the activity using the following navigation option:


Transaction Code SM30, Table TRWPR

2. If the entries below are missing, choose New Entries and make the corresponding entries.

Bus.Trans.

Time No. Component Function Module

BEST AOPENIT 40 FDIS CASH_FORECAST_MM_OPEN_ITEM

BEST CHECKALL 40 FDIS CASH_FORECAST_MM_RELEVANT

BEST OIINIT 30 FDIS CASH_FORECAST_MM_INIT

BEST OINUMBER 20 FDIS CASH_FORECAST_MM_OPEN_ITEM_NBR

BEST OPENITEM 20 FDIS CASH_FORECAST_MM_OPEN_ITEM

BEST OIREFRSH 50 FDIS CASH_FORECAST_MM_OPEN_ITEM

3. Choose Save.

4.4 Include Purchase RequisitionsFor the selection of purchase requisitions, certain entries are required in the table TRWPR for certain function modules. They are pre-configured in SAP Business All-in-One Baseline packages.



1. Access the activity using the following navigation option:


Transaction Code SM30, Table TRWPR

2. If the entries below are missing, choose New Entries and make the corresponding entries.

Bus.Trans.

Time No. Component Function Module

BANF CHECKALL 50 FDIS CASH_FORECAST_MM_RELEVANT

BANF OINUMALL 20 FDIS CASH_FORECAST_MM_OPEN_ITEM_NPR

BANF OINUMBER 20 FDIS CASH_FORECAST_MM_OPEN_ITEM_NPR

BANF OIREFRSH 20 FDIS CASH_FORECAST_MM_OPEN_ITEM_PR

BANF OPENITEM 20 FDIS CASH_FORECAST_MM_OPEN_ITEM_PR

3. Choose Save.

4.5 Assign Planning Levels for LogisticsWhen data from Materials Management (MM) and Sales and Distribution (SD) transactions is updated, company code data for the customer (ordering party) or the vendor (supplier) may not yet be created, meaning that the planning group may not be stored in the master record of the business partner. You can therefore define a planning group, which the system uses as default for updating cash management.

In this step, you assign transactions from MM and SD to appropriate planning levels.

The grouping of subledger accounts is made by assigning the planning group to an appropriate level for Financials (FI) postings. However, a business transaction in Logistics is not represented by a posting in FI, but by an internal ID, predefined by SAP. You must assign these transaction IDs to different planning levels in order to distinguish them in cash management.

1. Access this activity using the following navigation option:


IMG Menu Financial Supply Chain Management -> Cash and Liquidity Management -> Cash Management -> Structuring -> Define Planning Levels for Logistics

Transaction Code SPRO

2. In the Change View ‘Allocate Levels for MM and SD Transactions’ Overview screen, make the following entries:

Int Code

Planning Level

Planning Group Long Text

1 M1 Purchase Requisition

2 M2 Purchase Order

3 M3 Delivery Schedule / Scheduling agreement

101 S1 Sales Orders

201 AG Agency Business



3. Choose Save.



5 Prepare Productive Startup and Data SetupWhen a company code is activated for Cash Management (CM) and Liquidity Forecasting (LF), the first effect is that CM and LF data can be updated when CM-related and LF-related funds movements or planning take place. To update from MM and SD, additional indicators must be set for data to get from logistics into cash management.

5.1 Activate Company CodeYou can activate company codes for the CM and LF update. Table settings are checked in the process. The management groups needed for the CM and LF update can be entered in the customer and vendor master records, and partial or total reconstruction of the total records is possible.

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


IMG Menu Financial Supply Chain Management -> Cash and Liquidity Management -> Cash Management -> Tools -> Prepare Productive Start Up and Data Setup

Transaction Code OT29

2. Select the checkboxes for the relevant company codes according to your requirements.

If accessing via IMG menu

Field Name User Action and Values Comment

Cash mgt active in company code Select Always

Update purchasing data Select If required

Update sales data Select If required

If accessing via transaction OT29 (necessary if transport is required)

Field Name User Action and Values Comment

CoCd <CompanyCode>

Activate CM Select Always

Update MM Select If required

Update SD Select If required

3. Choose Save.

5.2 Reconciliation Activities before Start of CM and LFThe transaction FDFD was developed mainly as a tool to support implementation of CM and LF. You can activate the CM and LF update for company codes. Table settings are checked in the process. The planning groups needed for the CM and LF updates can be entered in vendor and customer master records, making partial/complete reconstruction of the total records easier.

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


IMG Menu Financial Supply Chain Management -> Cash and Liquidity



Management -> Cash Management -> Tools -> Prepare Productive Start Up and Data Setup

Transaction Code FDFD

You can use the relevant buttons in the application toolbar to access the following settings, as well as to check customizing:

5.2.1 Customer / Vendor DataMaintain the planning group in the vendor and customer master records according to this customizing table. This activity has to be performed either as part of data migration or within subsequent maintenance of customer/vendor data.

You can use this function to enter planning groups in vendor and customer master records. Planning groups must be in place for open items to be updated in CM and LF. The lines in the table represent selection criteria for various groups. The logic is as follows:

Ranking is determined by the priority. Priority 1 is highest priority. This criterion is checked first. If the customer/vendor meets these criteria, the group for this record is entered in the master record.

Example for customers:

Prio. Country PT low PT high Dunning Pmnt.meths Group Rec. pymt hist.

1 DE ZB01 ZB05 0001 U E1 X

2 DE E2

3 E9

If the terms in row 1 apply to a customer, the customer is assigned to planning group 1 and the indicator Record payment history is set in the master record. All the other customers in Germany are assigned to group E2. Foreign customers are assigned group E9.

Use the F1 help and the F4 input help when completing the selection criteria.

To ensure that all master records are assigned to a planning group, you should always specify at least one structure (with lowest priority) to which a vendor/customer can be matched if no other will do.

Choose the Check button to determine the number of master records to which no group has yet been assigned.

You can download and upload to store the selection criteria locally and import them again.

5.2.2 Data SetupYou can copy the existing documents, open items, planning records, and account balances into CM and LF.



You can stipulate whether the data setup is to cover the data from the Logistics modules SD and MM, agency deals, or Treasury Management.

The transfer programs should be run as batch jobs where you can specify the date and time. We recommend that you run the job overnight as it is essential that no postings are made while the data setup is running, as this would cause data problems in CM and LF.

Ensure that all the planning data is deleted as the first step in the data setup. There is a separate query for data from manual MRP (planning items, payment notices, and so on), because this is lost irretrievably once deleted. If you want to retain this data, answer No to the query.

5.2.3 Data ReconciliationA report is available with which you can schedule data reconciliation as a batch job. For more detailed information, read the relevant report documentation.

5.2.4 Correct DataIf an inconsistency should occur between the data in CM and LF and the actual data, this option allows you to circumvent the need for a complete data reconstruction. Depending on the origin of the inconsistency, the reconstruction can be limited to particular areas. See the relevant program documentation for more information.

5.2.5 Check CustomizingThis function allows you to check the customizing of the CM and LF. For example, a check is made as to whether a level is used in several applications or whether a planning group is used in customer master records as well as vendor master records (both are not allowed and this will produce errors).

6 AppendixIf you have unexpected issues, refer to SAP Notes 9859 and 156239.


sapevent:DOCU_LINK%5CDS:RE.RFFDNA00

sapevent:DOCU_LINK%5CDS:RE.RFFDEA00

Documents

806_BB_ConfigGuide_EN_DE