You are on page 1of 8

SAP S/4HANA

February 2016
English

Output Management MM-


Local Data (J21)
Building Block Configuration Guide

SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices Output Management - MM - Local Data (J21) : Config.Guide

Copyright

2013 SAP AG 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 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.

National product specifications may vary.

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 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. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.

SAP SE
of 8
SAP Best Practices Output Management - MM - Local Data (J21) : Config.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, buttons 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.

SAP SE
of 8
SAP Best Practices Output Management - MM - Local Data (J21) : Config.Guide

Content
Output Management MM Local Data.....................................................................................5
1 Purpose............................................................................................................................. 5
2 Preparation........................................................................................................................ 5
2.1 Prerequisites............................................................................................................ 5
2.2 Deployment Options................................................................................................ 5
2.3 Configuration........................................................................................................... 5
3 Configuration of Output Management MM Local Data (for On-premise).........................6
3.1.1 Output Condition Record: Invoice Verification.....................................................6
4 Manual Rework.................................................................................................................. 7

SAP SE
of 8
SAP Best Practices Output Management MM Local Data (J21): Configuration Guide

Output Management MM Local Data

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 do not want to configure manually and prefer an automated installation process using
BC Sets and other tools, refer to the Configuration Guide Getting Started of your SAP rapid-
deployment solution that is attached to the SAP Note.
This document supplements the existing Customizing documentation in the Implementation
Guide (IMG) and provides additional information where required.

2 Preparation

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 Deployment Options
The configuration guide provides the implementation content for the different deployment
options/SAP Products S/4HANA

Public cloud (PC) minimal scope & content

On-premise (OP) 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 chapters.

For the full scope of the on-premise scope & content PC and OP are required

For the public cloud scope & content PC 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):

SAP SE Page 5 of
SAP Best Practices Output Management MM Local Data (J21): Configuration Guide

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 <your value>.

Additional settings that need to be made, covered either by automation or manual


configuration (in the customer namespace).

1 Configuration of Output Management MM


Local Data (for On-premise)

1 Output Condition Record: Invoice Verification


The purpose of this activity is to create an output condition record for invoice verification.

Procedure
1. Access the activity using the following navigation option:
SAP ECC Menu Materials Management Logistics Invoice Verification Message
Invoice Determination Maintain Conditions Create Condition: Invoice
Verification
Transaction MRM1
Code
2. On the Create Output-Condition records: Invoice Verification screen, enter output type
EINK and choose Enter.
3. Choose Key combination and select CoCode, Blocking Reason: Price in the Key
Combination dialog box. Choose Enter.
4. On the Create Condition records (Mail to Purchasing): Fast Entry screen, enter the
following values and choose Enter:
Field Name Description User Action Comment
and Values
Company 1710
Code
BlockR Pr. Blocking reason: select
price
Funct Partner function ME
Medium Message 7
transmission
medium
Date/time Dispatch time 4
Language It is possible to insert the designated
language key in which you:

Display texts

SAP SE Page 6 of
SAP Best Practices Output Management MM Local Data (J21): Configuration Guide

Enter texts

Print documents.

Example: for English EN


5. Save your entries.

Result
The condition records are created. For the following output types, the output messages are
generated automatically: EINK.

2 Manual Rework
If you need to apply the Manual Rework procedure additional manual activities are required.
These activities are listed in the table below.

Configuration activity Manual Manual action in Remarks


transport target system /
possible client required
3.1.1 Output Condition No Yes
Records: Invoice
Verification

In case a manual transport is possible please proceed as follows:


1. Logon to the source system / client.

2. Goto the respective customizing activity as described in the respective chapter.

3. Select all relevant table entries and put them into a transport request.
Most likely this can be done by choosing Table View -> Transport. If this is not
possible please refer to the more detailed instructions given in the respective chapter
of the effected customizing activity.

4. The newly created transport request needs to be released and imported in the target
system / client.

Remark: Please also check the documentation for the related IMG activity regarding specific
information.

In case manual action in the target system / client is required please proceed as follows:
1. Logon to the target system / client.

2. Goto the respective customizing activity and make the relevant settings as described
in the respective chapter.

SAP SE Page 7 of
SAP Best Practices Output Management MM Local Data (J21): Configuration Guide

SAP SE Page 8 of