University of Southern California Introduction to Enterprise Wide Information Systems Configuring...

University of Southern California

Introduction to Enterprise Wide Information Systems

Configuring SAP

Instructor: Richard W. Vawter


Objectives

The primary objective of this discussion is to show how the SAP R/3 Implementation Guide (IMG) can be used to aid the project team in configuring business transactions.

For simplicity, we will keep our focus on the Order process.

Upon completion of this topic, you should be able to:

Describe the various implementation and configuration tools available in the SAP R/3 system.

Anticipate how elements of the Customer Master are integrated and are used to control the SD processes.

Use elements in the Material Master to streamline COM.

How to configure the Billing process for data flow and price control.


Topics

The Implementation Guide

Sales Orders and the Customer Master

Customizing the Material Master

Configuring the Billing Process


Methods for Implementing & Configuring SAP

SAP R/3 includes several tools to facilitate configuring SAPand continuing support .

The R/3 Reference Model - describes the business processes included in the standard R/3 system as well as the relationship among the different application modules.

The Implementation Guide (IMG) - guides users in matching their business requirements with the SAP standard software.

The Procedural model - is used as a navigator to guide you through the whole implementation and configuration process.



A tool that leads to a step-by-step customizing of selected parts (modules) of the R/3 system.

It guides the project team in matching the business requirements with the SAP standard software.

With the IMG project management functions...

Consultants in charge of implementation first decide which parts of R/3 are to be customized.

The system then automatically generates the needed hierarchical list of the customizing steps for achieving that customization.



Basis configuration takes place.

Global settings are set as default in the SAP system.

The structure is defined to match the organization’s business function. (The Enterprise Structure)

Cross- application functions are developed.

Applications are created to meet business requirements.

Financial Accounting

Materials Management

Sales and Distribution

Human Resources


The Enterprise IMG

The Enterprise IMG is just a subset of the Reference IMG.

It is where all the customizing takes place.

PSPS

PPPP

COCO

FIFI

……..

HRHR

MMMM

SDSD

FIFI

MMMM

PPPP

COCO

FIFI

COCO

PPPP

MMMM FIFI

COCO

SAP Reference IMG Enterprise IMG

Project IMG

Project 001Project 002

Project 002Additional needs,

e.g. upgrade

Customizing Objects

As a rule, you will have more than one SAP system.

Development system

Changes made in the development system are transported to the test system, then to the production system.

Test system Production system

Development systemDevelopment system

11 2211 22 3311 22 33 4

1111 22

Sales organization

Sales documents

Implementation guide

Test systemTest system

22334

1122

Sales organization

Sales documentsVersions

TransportRequest

Workbenchorganizer


Customizing - How to Proceed

1. Define the organizational structures in the IMG and name the individual organizational elements.

2. Assign the organizational elements.

Define the organizational elements

Assign the organizational elements


Topics



Customizing the Material Master



How Master Data is Integrated in SD Processing

Master Data

CustomersMaterialsBills of MaterialsCustomer-Material InfoProduct Proposals

Master Data

CustomersMaterialsBills of MaterialsCustomer-Material InfoProduct Proposals

FIFI

PSPS

PMPM

CCCC

MMMM

PPPP

FIFI

MMMM

COCO

FIFI

Sales supportSales support

DataWarehouse

DataWarehouse

SalesSales

Materials Mgmt.Production PlanningPlant MaintenanceControllingFinancial AccountingProject System

Materials Mgmt.Financial Accounting

Financial AccountingControlling


Origins of Data in Sales Documents

When you create a sales order, the system proposes most of the data from the master records.

Sales orderCustomer master dataCustomer master data

Material master dataMaterial master data

. . . . .. . . . .

ConditionsConditions

TextsTexts

Control tablesControl tables


Business Partners (Partner Functions)

Partners - someone you have a relationship with or have to communicate with.

Functions - each partner type has specific functions.

Sold-to partySold-to party

Ship-to partyShip-to party

Bill-to partyBill-to party

PayerPayer

Contact personContact person

Forwarding agentForwarding agent

EmployeeEmployee

. . . . . . . .. . . . . . . .

PartnerPartnerFunctionsFunctions


Business Partners - Customer Master

Essential business partners for a sales transaction are the sold-to party, ship-to party, payer, and bill-to party.

They are stored in the customer master.

Sold-to partySold-to party Ship-to partyShip-to party

Bill-to partyBill-to party PayerPayer

CustomerCustomermastermaster


Customer Master - 3 Major Data Views

Sales data - data specific to sales, e.g. sales, distribution, shipping.

Company Code data - financial accounting data.

General data - data assigned directly to a client so it’s available to the other two areas.

General dataGeneral data

Sales dataSales dataCompany code dataCompany code data

FIFI SDSD


Customer Master - Account Groups

Account Group codes define what information will be needed; what fields will be required. A payer only needs address information, etc, while a sold-to

party needs an address plus delivery address, etc.

Customer : C1

Sales organization : 0001

Distribution channel : 01

Division : 01

Account group : 0001

Create sold-to partyCreate sold-to party

Field selectionNumber assignmentOne-line account: Yes/NoOutput proposal

ACCOUNT GROUP 0001ACCOUNT GROUP 0001

ACCOUNT GROUPACCOUNT GROUP

0001 Sold-to party

0002 Ship-to party

0003 Payer

0004 Bill-to party

. . .

0001

Customer Master - Selecting Fields for Data Groups Using field selection, you can define for each account group whether fields are optional or required.

You can suppress any fields which you do not require.

Data in the customer master recordData in the customer master recordAddressCommunicationControl dataPayment transactions

SalesShippingBillingPartner usageOutput

IMG for SalesIMG for Sales

General data

Company code data

Sales data

Hide Required Optional DisplaySales groupStatistics groupCustomer groupPricing procedureProduct proposal. . . .

Account groups are already set up in the R/3 system

Sold-to party

Specific fields are selected for each of these account groups

The selection of fields depends on the functionality of the partner function needed.

Customer Master - Selecting Fields for Data Groups

Bill-to party Payer Ship-to party

Account groupAccount group00010001

Sold-to partySold-to party

Sales

Shipping

Billing

Payer

Documents

Sales

Shipping

Billing

Payer

Documents


Ship-to partyShip-to party

Sales 1

Shipping

Billing 2

- - - - -

Documents

Sales 1

Shipping

Billing 2

- - - - -

Documents


Bill-to partyBill-to party

Sales 1

- - - - -

Billing

- - - - -

Documents

Sales 1

- - - - -

Billing

- - - - -

Documents


PayerPayer

Sales 1

- - - - -

- - - - -

Payer

Documents

Sales 1

- - - - -

- - - - -

Payer

Documents

1. Controlling for authorization 2. Tax information


Customer Master - Combination Rules in Field

The combination rule with the highest priority determines the respective field status.

SuppressSuppress

DisplayDisplay

RequiredRequired

OptionalOptional

SuppressSuppress

SuppressSuppress

SuppressSuppress

SuppressSuppress

SuppressSuppress

DisplayDisplay

SuppressSuppress

DisplayDisplay

DisplayDisplay

DisplayDisplay

RequiredRequired

SuppressSuppress

DisplayDisplay

RequiredRequired

RequiredRequired

OptionalOptional

SuppressSuppress

DisplayDisplay

RequiredRequired

OptionalOptional

1st priority1st priority

2nd priority2nd priority

3rd priority3rd priority

4th priority4th priority

Transaction fields marked as:

Acc

ou

nt

gro

up

ma

rke

d a

s:


Customer Hierarchies Create hierarchies to reflect the structure of the customer organization.

Use customer hierarchiesduring sales order processing and billing for determining pricing.

ACME CoACME CoACME CoACME Co

CentralCentral

47114711


SouthSouth

47124712


NorthNorth

47134713


NorthwestNorthwest

47144714


NortheastNortheast

47154715

Customer2743

Customer2743

Customer2744

Customer2744

Customer2742

Customer2742

Uniquenode number

Uniquenode number


Topics



Customizing the Material Master (next time)


University of Southern California Introduction to Enterprise Wide Information Systems Configuring...

Documents

Transcript of University of Southern California Introduction to Enterprise Wide Information Systems Configuring...