j76 s4hana1709 Bb Configguide en Us
Short Description
Descripción: 4hana1709...
Description
SAP S/4HANA August 2016 English
Cash Daily Operation – Core [local] (J76) Building Block Configuration Guide
SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany
SAP Best Practices
Cash Daily Operation – Core [local] (J76): Configuration Guide
Copyright © 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 2 of 10
SAP Best Practices
Revision
Cash Daily Operation – Core [local] (J76): Configuration Guide
Change Date
Description
0
© SAP SE
Page 3 of 10
SAP Best Practices
Cash Daily Operation – Core [local] (J76): Configuration Guide
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.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP SE
Page 4 of 10
SAP Best Practices
Cash Daily Operation – Core [local] (J76): Configuration Guide
Contents Cash Daily Operation – Core [local]: Configuration Guide ........................................................ 6 1 Purpose .............................................................................................................................. 6 2 Preparation ......................................................................................................................... 6 2.1 Prerequisites ............................................................................................................ 6 2.2 Supported Deployments........................................................................................... 6 3 Configuration ...................................................................................................................... 6 3.1 Enter GL Account for Bank Account ........................................................................ 7 3.2 Activate Individual Source Application ..................................................................... 7 3.3 Memo Records ......................................................................................................... 8 3.3.1 Define Number Ranges ....................................................................................... 8 4 Manual Build Steps ............................................................................................................ 9 Cash Daily Operation – Core [local]: Configuration Guide ........................................................ 6 1 Purpose .............................................................................................................................. 6 2 Preparation ......................................................................................................................... 6 2.1 Prerequisites ............................................................................................................ 6 2.2 Supported Deployments........................................................................................... 6 3 Configuration ...................................................................................................................... 6 3.1 Enter GL Account for Bank Account ........................................................................ 7 3.2 Activate Individual Source Application ..................................................................... 7 3.3 Memo Records ......................................................................................................... 8 3.3.1 Define Number Ranges ....................................................................................... 8 4 Manual Build Steps ............................................................................................................ 9 Cash Daily Operation – Core [local]: Configuration Guide ........................................................ 6 1 Purpose .............................................................................................................................. 6 2 Preparation ......................................................................................................................... 6 2.1 Prerequisites ............................................................................................................ 6 3 Configuration ...................................................................................................................... 6 3.1 Enter GL Account for Bank Account ........................................................................ 6 3.2 Activate Individual Source Application ..................................................................... 7 3.3 Memo Records ......................................................................................................... 8 3.3.1 Define Number Ranges ....................................................................................... 8 4 Manual Build Steps ............................................................................................................ 9
Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar
© SAP SE
Page 5 of 10
SAP Best Practices
Cash Daily Operation – Core [local] (J76): Configuration Guide
Cash Daily Operation – Core [local]: Configuration Guide 1 Purpose The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation. If you want to install SAP S/4HANA locally (on-premise) and if you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, you can set up a best-practice client and activate the implementation content. For more information, see the Administration Guide for the Implementation of SAP S/4HANA, on premise edition which is linked in the content library (included in the documentation package).
2 Preparation 2.1 Prerequisites Before you start installing this scenario, you must install the prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix.
2.2 Supported Deployments The configuration guide provides the implementation content for the different SAP S/4HANA products:
SAP S/4HANA Cloud – (CE) minimal scope and content
SAP S/4HANA – (OP) installed locally (on-premise), full scope and content coverage Depending on the use case/deployment option/ S/4HANA product version, you need to implement the required scope/content starting with the Public cloud chapter and proceed with the next required sections.
For the full scope of the on premise scope & content – PC and OP are required
For the SAP S/4HANA Cloud scope & content – CE is required; OP is not required
3 Configuration The following section describes the complete settings for this building block. These settings can be divided into three main groups:
Prerequisite settings that have to be checked and which were delivered by SAP (as part of the standard delivery) The term Check refers to these prerequisite settings.
Settings defined by the customer (in the customer namespace and customer-specific): The system uses automation to request individual customer settings during the personalization process. These settings can be initial or reused from existing SAP ERP layers and are indicated in the text by .
Additional settings that must be made, covered either by automation or manual configuration (in the customer namespace). The term Create refers to these additional settings in the text.
© SAP SE
Page 6 of 10
Cash Daily Operation – Core [local] (J76): Configuration Guide
SAP Best Practices
3.1 Enter GL Account for Bank Account Use Enter the G/L account for the existing bank accounts which were created in building block J74.
Procedure 1. Access the activity using one of the following navigation options: Fiori Launchpad
Please contact system administrator to get the url of Fiori Launchpad, the user and password. The user must be assigned with business role: SAP_BR_CASH_SPECIALIST
Fiori app
Manage Bank Accounts
2. On the Bank Hierarchy: Active Accounts (XX Accounts) screen, choose the bank account 33333 in bank key 011000390 of Country US to be changed from the bank hierarchy view or account list view. 3. The Bank Account screen displays, choose Edit. 4. choose tab Connectivity Path, enter the following data: Field Name
Entry Value
G/L Account
0011001000
5. Choose Save and Submit. 6. Repeat the steps above all,using the following data: Field Name
Entry Value
Account Number
25800611
Bank Key
820800001
G/L Account
0011002000
Country
US
Field Name
Entry Value
Account Number
55555
Bank Key
011000390
G/L Account
0011001100
Country
US
3.2 Activate Individual Source Application Use You use this Customizing activity to activate source applications for cash management. Once a source application has been activated, the transactions from the application are included in reporting for cash management. Applications are activated per company code. With this activity, you enter each application/company code combination individually. To activate multiple company codes for an application simultaneously, you can use the mass activation report Activate Multiple Source Applications.
© SAP SE
Page 7 of 10
Cash Daily Operation – Core [local] (J76): Configuration Guide
SAP Best Practices
Procedure 1. Access the transaction using the following navigation path: Transaction Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management Cash Management Tools Activate Individual Source Applications
2. On the Change View "Activate Source Applications": Overview screen, choose New Entries. 3. On the New Entries: Overview of Added Entries screen, create the following settings: Field Name
Entry Value
Entry Value
Entry Value
Entry Value
Src. Appl.
FI General Ledger
BKPF Accounting
SDCM Sales And Distribution (CM)
MM Materials Management
CoCd.
1710
1010
1010
1010
Company Name
Company Code 1710
Company Code 1010
Company Code 1010
Company Code 1010
Active
1 Active
1 Active
1 Active
1 Active
4. Choose Save.
3.3 Memo Records 3.3.1
Define Number Ranges
Use In the "Number ranges" step, you specify one or more number ranges for manual planning. The system allocates a number from the appropriate interval to each memo record entered manually.
Procedure 1. Access the transaction using the following navigation path: Transaction Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management Cash Management Memo Records Define Number Ranges
2. On the Range Maintenance: Cash mgmt + forecast screen, enter company code 1710, and then choose Change intervals. 3. On the next screen, create the following entry: Field Name
Entry Value
No
01
From No.
0000000001
To Number
0999999999
© SAP SE
Page 8 of 10
Formatted Table
Cash Daily Operation – Core [local] (J76): Configuration Guide
SAP Best Practices
Field Name
Entry Value
Ext 4. Choose Save. Formatted: No bullets or numbering
Define Cash Management Account Name Use In this step, you assign a mnemonic name as the cash management account name to each bank account and bank clearing account. This mnemonic name is used with all functions and reports in Cash Management instead of the account number. The name is unique within a company code.
Procedure Access the transaction using the following navigation path:
Formatted: Numbered + Level: 1 + Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left + Aligned at: 0" + Indent at: 0.25"
Transaction Code
SPRO
IMG Menu
Financial Supply Chain Management Cash and Liquidity Management Cash Management Memo Records Define Cash Management Account Name
On the dialog box Determine Work Area: Entry, enter the company code 1710, and then choose Enter. On the Change View “Cash Management Account Name”: Overview screen, create the following entries: CM acct
G/L acct
US-BK1-AC1
11001000
CMF
HBPR
Description Sample - US Bank 1, Account 1
US-BK1-EUR
11001100
Sample - US Bank 1, EUR Acct
US-BK2-AC2
11002000
Sample - US Bank 2, Account 2
Choose Save. 4.
Formatted: No bullets or numbering
4 Manual Build Steps Some settings cannot automatically be transported between systems or clients. In these cases, you either transport the settings manually, if possible, or make the settings in the target system or client. The following table lists the configuration activities where automatic transport is not possible. Refer to the details and sequence in the sections above. Configuration activity
Manual transport possible
Manual action in target system / client required
3.1 Enter GL Account for Bank Account
No
Yes
3.3.1 Define Number Range
Yes
No
© SAP SE
Remarks
Page 9 of 10
SAP Best Practices
Cash Daily Operation – Core [local] (J76): Configuration Guide
We recommend that you plan especially for doing these manual build steps and rehearse the sequence in advance, if possible well before cut over.
© SAP SE
Page 10 of 10
View more...
Comments