Automotive Consulting Solution

Interface SAP ERP JIS - MES

Agenda

1. Benefit for the Customer

2. Description of the Function
3. The Function in the System
4. Technical Information

SAP SE or an SAP affiliate company. All rights reserved. 2

Customer Benefit

Solution
Proven solutions/services of SAP Automotive Consulting
Solutions already running productive at several customers
Solutions and documentation are available in German and English

Cost Exact calculation of implementation cost. Implementation for fixed price

6 months of free follow up care operations for bug corrections starting at
the date of installation within the development landscape. Afterwards
chargeable consulting support starts
No additional ongoing costs (i.e. maintenance cost)

Time
Prompt implementation possible
Defined timeframe for implementation

SAP SE or an SAP affiliate company. All rights reserved. 3

Agenda

1. Benefit for the Customer

2. Description of the Function
3. The Function in the System
4. Technical Information

SAP SE or an SAP affiliate company. All rights reserved. 4

Motivation

Sequenced (JIS) calls are received in the SAP ERP System

Production should be controlled by a Manufacturing Execution System (MES)
SAP is the leading ERP and master data system and transfers the relevant
master data to the MES (no double maintenance of master data necessary)
JIS calls are also transferred from the SAP ERP System to the MES
MES reports the production stage to the SAP ERP System at predefined points in
time
Based on the reported production progress, additional actions can be performed
in the SAP ERP System (e.g. backflushing via standard JIT action BFLU)

SAP SE or an SAP affiliate company. All rights reserved. 5

Concept Data from SAP ERP to MES

Master data are transferred in the respective standard format via IDoc
Examples for transferred master data:
Material master
Classification
Bill of material
Etc.
JIS calls are transferred to the MES via the new JIS action ZMES in the form of a
SEQJIT-IDoc
In the same way changes to the JIT call are transmitted
Within the action matrix the processing state (production progress), up to which
changes to the JIS call are possible, is defined
Within an additional table it can be defined, which JIS supplementary texts (from
table JITTE) are transferred into the IDoc for the MES

SAP SE or an SAP affiliate company. All rights reserved. 6

Concept Data from MES to SAP ERP

MES logs into the SAP ERP System via an RFC interface
BAPI to call JIS actions in SAP ERP
MES performs predefined actions in the SAP ERP depending on the processing
state
Examples:
ZSOP: Production started (no more changes to the JIS call allowed)
ZEOP. Production finished (as trigger for the backflush via action BFLU)
ZLIT: Load call onto truck (as trigger for the delivery)
Etc.
Z-actions can be freely defined, also Standard JIS actions can be called
Recommendation: If actions like BFLU or DELI should be performed by MES, the
corresponding authorities for the RFC-User are necessary. Thus it is advisable
that the MES only performs Z-actions without logic and that the actual posting is
done by a standard action per job

SAP SE or an SAP affiliate company. All rights reserved. 7

Agenda

1. Benefit for the Customer

2. Description of the Function
3. The Function in the System
4. Technical Information

SAP SE or an SAP affiliate company. All rights reserved. 8

SEQJIT-IDoc from SAP to MES

Position segment

Control segment

SAP SE or an SAP affiliate company. All rights reserved. 9

Definition of JIT supplementary text for SEQJIT-IDoc

For each JIT customer different fields can be selected

Assignment to header segment respectively position segment is freely selectable
For texts that are available in multiple JITTE levels, it can be defined which level
should be transferred into the SEQJIT-IDoc

SAP SE or an SAP affiliate company. All rights reserved. 10

BAPI for action performance by MES

The JIT part group is unambiguously identified by POSID

The JIT action that should be performed is transferred in field action
Additional transfer fields can be defined (in this example container and truck
number)
The information from the transfer fields are saved in the JIT call

SAP SE or an SAP affiliate company. All rights reserved. 11

Integration in JIT action matrix

ACS Z-action for transfer to MES

Freely defined ACS Z-action for

the status message MES to SAP
ERP

Any desired integration of the ACS

Z-action into the action matrix is
possible

SAP SE or an SAP affiliate company. All rights reserved. 12

Agenda

1. Benefit for the Customer

2. Description of the Function
3. The Function in the System
4. Technical Information

SAP SE or an SAP affiliate company. All rights reserved. 13

Technical Information

Available for SAP ERP ECC 6.0

Activation of automotive industrialized solution in SAP ERP System

necessary

Technical installation is possible remotely

Modification-free

Delivery in Z-namespace

SAP SE or an SAP affiliate company. All rights reserved. 14

Source of Information

Internet
Overview-, Detail- and Customer presentations
http://www.sap.com/acs

Email - distribution list

Signing up through mario.rebitzer@sap.com

OSS-System
Notes (Search term: Automotive Consulting Solutions)
SAP SE or an SAP affiliate company. All rights reserved. 15
Thank you!
Mario Rebitzer
Platinum Consultant
Industry Area Automotive

SAP Deutschland SE & Co. KG

Hasso-Plattner-Ring 7
69190 Walldorf, Germany

M +49/ 170 22 00 287

S +49/ 6227 7 44674
E mario.rebitzer@sap.com
 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://global12.sap.com/corporate-en/legal/copyright/index.epx 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 SEs 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 or an SAP affiliate company. All rights reserved. 17