SAP Business ByDesign Reference Systems. Scenario Outline. SAP ERP Integration Scenarios

(1)

SAP Business ByDesign Reference Systems

SAP ERP Integration Scenarios

(2)

Content

Scenario Overview

Business Scenarios in a Reference System

Introduction

Typical Usage

Process Illustration

Usage Example 1: Procure-to-Pay (Stock) with SAP ERP Integration

Usage Example 2: Order-to-Cash (Third-Party Order Processing – Material)

with SAP ERP Integration

Usage Example 3: Basic Master Data Integration with SAP ERP

(3)

Scenario Overview

Business Scenarios in a Reference System

Introduction

(4)

Business Scenarios in a Reference System

In a Reference System, you can experience

how a business scenario meets specific

requirements of a typical midsize company.

The following slides outline and illustrate

the individual process steps of a business

scenario as it has been realized in the

model company Almika.

For hands-on experience, you can take

advantage of the business scenario document,

which guides you through the process with

(5)

Introduction

Order-to-Cash (Third-Party Order Processing – Material)

Scenario Introduction

In the SAP Business ByDesign scenarios for subsidiaries of large

enterprises, a large enterprise (using SAP ERP) runs subsidiaries

(using SAP Business ByDesign) that act as sales offices or local

distribution centers. The subsidiaries sell products to customers

and buy them from the parent company. The products are stored

at and shipped from the subsidiary or the products are shipped

directly from the headquarters to customers.

The supported processes support a series of process steps

(6)

Typical Usage

SAP ERP Integration Scenarios

Procure-to-Pay (Stock) with SAP ERP Integration

The Procure-to-Pay (Stock) business scenario covers all aspects of procuring

items to stock. This includes SAP Business ByDesign activities from purchasing

based on a list price, automatic purchase request and order creation, inbound

logistics and journal entries. Sales orders in SAP ERP are created automatically,

outbound processing and the invoicing trigger are performed manually.

All available business documents are transferred and processed using the

Application Link Enabling (ALE) integration technology.

Third-Party Order Processing – Material with SAP ERP Integration

The sales representative enters a sales order into the system. In this case, the

sales representative decides to fulfill the delivery externally to save delivery time.

When the sales order is released, the SAP Business ByDesign system sends an

automatically created purchase order to SAP ERP. The subsequent activities are

similar to the first usage example.

The customer is billed via customer invoice processing and the supplier invoice is

posted (based on the terms) automatically.

(7)

Typical Usage

SAP ERP Integration Scenarios

Basic Master Data Integration with SAP ERP

In this usage example, the systems communication supports both the transfer of

a new product from SAP ERP to SAP Business ByDesign and the replication of

the account contact update from SAP Business By Design to SAP ERP.

Consolidation Preparation

(8)

Process Illustration

Usage Example 1: Procure-to-Pay (Stock) with SAP ERP Integration

Usage Example 2: Order-to-Cash (Third-Party Order Processing – Material)

with SAP ERP Integration

Usage Example 3: Basic Master Data Integration with SAP ERP

(9)

2

4 SAP ERP Integration Scenarios

Procure-to-Pay (Stock) with SAP ERP Integration (1 of 2)

Purchaser Logistics Employee ByD Demo

Create Outbound Delivery with Order Reference

Process

Role

Work center / ERP

View

Form

Financial

Posting

Optional: Check Purchase Order Acknowledgement in

SAP Business ByDesign

Post Goods Issue in SAP ERP

1

Create Purchase Order

The purchaser creates a purchase order for some office material.

Purchase Requests and Orders Purchaser

3

Sales Employee ByD Demo

Check Created Sales Order in SAP ERP

Accounting employee ByD Demo

Create Billing Document

Create an Invoice Document in SAP ERP

5

Purchase Requests and Orders

Display Sales Order: Initial Screen

Purchase order

The user responsible for processing the company’s internal sales orders logs on to SAP ERP and checks their worklist. The worklist view allows you to check the

automatically created SAP ERP sales order details.

Once saved in SAP ERP, the invoicing document is automatically sent to the SAP Business ByDesign system for further processing. In the current scenario, the invoicing document is automatically posted when the goods receipt has been posted in SAP Business ByDesign.

This process step is executed

in SAP ERP

The supply planner posts the goods receipt at the receiving site.

Goods transfer

Warehouse Manager

Inbound Logistics Post Goods Receipt

6

The supply planner posts the goods issue in SAP ERP on the sending site and releases it to create an outbound delivery. The supply planner reviews the outbound delivery including the advanced shipping notification created by SAP ERP.

In the Purchase Orders view, the Purchase makes sure, the status changed to

Acknowledgement Received.

(10)

SAP ERP Integration Scenarios

Procure-to-Pay (Stock) with SAP ERP Integration (1 of 2)

7

The supplier invoice has been created automatically. The financial accountant checks the supplier invoice.

Customer Invoice

Financial Accountant

Supplier Invoicing

Check automatically Posted Supplier Invoice

This is an optional step

Process

Role

Work center / ERP

View

(11)

SAP ERP Integration Scenarios

Order-to-Cash (Third-Party Order Processing – Material)

with SAP ERP Integration (1/2)

1

2

The sales

representative enters sales order.

As the ordered product is an item delivered by a third party supplier, the system generates purchase order automatically.

This step is optional for a real business scenario environment. But for the process demo scenario, you need to know the generated purchase order ID for the follow-up process steps in SAP ERP.

Sales Order

Sales representative Sales Representative

Sales Orders Sales Orders Create Sales Order Optional: Check Sales

Order Document Flow

4

Logistics Employee ByD Demo

Create Outbound Delivery with Order Reference

Post Goods Issue in SAP ERP

3

Sales Employee ByD Demo

Check Created Sales Order in SAP ERP

Accounting employee ByD Demo

Create Billing Document

Create an Invoice Document in SAP ERP

5

Display Sales Order: Initial Screen

The user responsible for processing the company’s internal sales orders logs on to SAP ERP and checks their worklist. The worklist view allows you to check the

automatically created SAP ERP sales order details.

Once saved in SAP ERP, the invoicing document is automatically sent to the SAP Business ByDesign system for further processing. In the current scenario, the invoicing document is automatically posted when the goods receipt has been posted in SAP Business ByDesign. The supply planner

posts the goods issue in SAP ERP on the sending site and releases it to create an outbound delivery. The supply planner reviews the outbound delivery including the advanced shipping notification created by SAP ERP.

This process step is executed

in SAP ERP

6

The Third-Party Order fulfillment confirmation triggers the customer invoice request generation . The sales representative can review the invoice request and post the customer invoice.

Customer Invoice

Sales Representative

Customer Invoicing Post Customer Invoice

Customer Invoice Delivery Note

Sales Order

Process

Role

Work center / ERP

View

(12)

7

8 SAP ERP Integration Scenarios

Order-to-Cash (Third-Party Order Processing – Material)

with SAP ERP Integration (2/2)

Review Automatically Created Third-Party

Order Fulfillment

The system-integrated business process is finished once the billing document from SAP ERP has been posted. The Sales Representative can now review the

automatically created corresponding business documents Supplier Invoicing Supplier Invoice General Accountant Check Automatically Created Supplier Invoice

Supplier Invoice

This is an optional step

Journal Entries

The supplier invoice has been created automatically. The financial accountant checks the supplier invoice.

Customer Invoice

Supplier Invoicing

Process

Role

Work center / ERP

View

(13)

1

2 SAP ERP Integration Scenarios

Basic Master Data Integration with SAP ERP

Send new Product from SAP ERP to SAP

Business ByDesign

Account Management

System Administrator Sales Representative

Product and Service Portfolio

Check Sent Product in SAP Business ByDesign (optional)

This is an optional step

3

Sales Representative Update a Customer Account Contact Person Customer Display: Initial Screen

4

System Administrator

Check Update of Customer Account Contact in SAP

ERP (optional)

Create Material (Initial Screen)

Process

Role

Work center / ERP

View

Form

Financial

Posting

The System Administrator creates a new material in SAP ERP.

SAP ERP sends the update of the master data record to SAP Business ByDesign.

The Sales Representative reviews now if the Product and Service Portfolio in SAP ByDesign has been updated

The Sales Representative updates account information in SAP ByDesign. SAP Business ByDesign sends the update of the master data record to SAP ERP.

The System Administrator reviews the updated customer account information in SAP ERP.

(14)

2 SAP ERP Integration Scenarios

Consolidation Preparation

Financial Accountant General Ledger Check Partner Company Setting in General Ledger

This is an optional step

3

Execute Intercompany Transactions General Ledger

4

Financial Accountant Reporting for Consolidation Preparation

1

Check Business Partner Master Data

The accountant prepares the reports including “Trial Balance”, “Balance Sheet”, “Income Statement” and “Cash Flow Statement” for consolidation purposes. The intercompany

transactions are executed. For example customer invoices. For details, please refer to the related business process documents.

Process

Role

Work center / ERP

View

Form

Financial

Posting

Payables Suppliers The accountant reviews the proper account

determination groups for partner

companies within the master data.

(15)

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, POW ER6+, POW ER6, POW ER5+, POW ER5, POW ER, 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, SAP BusinessObjects Explorer, StreamWork, 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 Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of

merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.