918 Scen Overview en Cn

8/10/2019 918 Scen Overview en Cn

http://slidepdf.com/reader/full/918-scen-overview-en-cn 1/11



© SAP 2008 /

Purpose

The purpose is to describe business processes related to internal and externalsubcontracting.

Purpose and Benefits:

Scenario Overview



© SAP 2008 /

Scenario Overview

Business Requirement: Outsourcing of manufacturing processes.

External Subcontracting covers manufacturing steps outsourced to a toll-manufacturer,

internal subcontracting covers steps as a toll-manufacturer for a client.

Internal Subcontracting

External Subcontracting

Purchase Order

DeliveryPicking

Goods Receipt

Order

ProcessingMRP Shipping Invoicing

Accounts

Payable

Stock Transfer

without

Delivery

Stock Transfer

with Delivery

Inventory

Management

Process Order

Processing

Quality

Management

Goods Receipt

with

Warehouse

Management



© SAP 2008 /

Business BenefitsBusiness Benefits

Increased customer

satisfaction

No process time for

buyer

Increased

transperancy

Reduced purchasing

process cycle time

Buyer Sub-Contractor Third Party Vendor

Plan requirementsSupply material to the

Subcontractor

Assign source of

supply

Create purchase

order and update

contract

Create and validatesales order (Job

Order)

Provide material

(components) to the

subcontractor

Process material

Generate material

request automatically

Business View - 1



© SAP 2008 /

Business BenefitsBusiness Benefits

Increased customer

satisfaction

Reduced transaction

cost

Buyer Sub-Contractor Third Party Vendor

Send out shipping

notification

Confirm goods

receipt

Adjust under and

over consumption

Create invoice

Verify and releaseinvoice

Check and release

payment

Business View - 2


http://slidepdf.com/reader/full/918-scen-overview-en-cn 7/11© SAP 2008 /

External subcontracting

Vendor: S-1003

SAPChem AG

Plant 1000

Vendor: S-9000

(subcontractor)

Purchase order for

components with

delivery address to

subcontractor

Invoice

Invoice

Delivery tosubcontractor

Goods delivery

Delivery of

components

Purchse order

CH-6210 (GranuSAP, 100 kg)



Process Flow Diagram –

External Subcontracting

B u y e r

W a r e h o u s e

C l e r k

A c c o u n t s

P a y a b l e

E v e n t

V e n d o r

ReceiveMaterial at

Dock

Delivery PickList

GR/IR PPVVendor

MRP = Material Requirements Planning, PO = Purchase Order, GR/IR = Goods Receipt/Invoice Receipt, PPV = Purchase Price Variance

IncomingVendorInvoice

Delivery Note

Invoice Receipt

PickConfirmation

Goods ReceiptPost GoodsIssue

Create DeliveryRequest

CreateSubcontract PO

Inventory GR/IRSubcontracting

Services/Consumption

Print GR Slip

Requirement ofSubcontracting

Material

Q u a l i t y

S p e c i a l i s t

QualityInspection

Record Results

Stock transfer forsubcontractor

T h i r d

P a r t y

Create PO forSpecial Stock

PO

Requirement ofMaterial

(Component)

Approve PO

Subcontract PO



Internal subcontracting

Fil l ing

Canister, 5 kg

VERP

CH-4200

PowerPaint, red

YQFP

CH-6800

Material

providedPaint, red

YQNM

CH-0500 Plant 1000

Description

Mat. type

Mat Nr

WM managed

QM active batch managed

CH-6800 (PowerPaint, red)



C u s t o m e r

S h o p F l o o r

S p e c i a l i s t

S a l e s

A d m i n i s t r a t i o n

S a l e s

B i l l i n g

E v e n t

CustomerNeeds to Buy

Product

InventoryCOGS

AR= Accounts Receivable, COGS = Cost of Goods Sold, MRP = Material Requirement Planning

Delivery NoteOrder

Confirmation

Pick List

BillingDocument

W a r e h o u

s e C l e r k

Billing

Process Flow Diagram –

Internal Subcontracting

P r o d u c t i o n

P l a n n e r

MRP

MRP List

PlannedOrders

Creating PlannedIndependent

Requirements

InventoryConsumption@ Standard.

Cost

ConvertPlanned Order

to ProcessOrder

Process OrderConfirmation

Create DeliveryRequest

Post GoodsIssue

Beginning ofPlanning

Cycle

AvailabilityCheck of Non

ProvidedMaterials

Sales OrderEntry



Legend

Symbol Description Usage Comments

To next / From last Diagram: Leadsto the next / previous page of theDiagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a taskstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates afinancial posting document


Budget Planning: Indicates abudget planning document


Manual Process: Covers a taskthat is manually done

Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines

System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software

Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.

DiagramConnection

Hardcopy /Document

Financial

Actuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n

Symbol Description Usage

Comments

Band: Identifies a user role, such as AccountsPayable Clerk or Sales Representative. This band

can also identify an organization unit or group,

rather than a specific role.

The other process flow symbols in this table go into

these rows. You have as many rows as required to

cover all of the roles in the scenario.

Role bandcontains tasks

common to that

role.

External Events: Contains events that start or end the

scenario, or influence the course of events in the

scenario.

Flow line (solid): Line indicates the normal sequence

of steps and direction of flow in the scenario.

Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can

also lead to documents involved in the process flow.

Connects twotasks in ascenarioprocess or anon-step event

Business Activity / Event: Identifies an action thateither leads into or out of the scenario, or an outsideProcess that happens during the scenario

Does notcorrespond to atask step in thedocument

Unit Process: Identifies a task that is covered in astep-by-step manner in the scenario

Corresponds toa task step inthe document

Process Reference: If the scenario references anotherscenario in total, put the scenario number and namehere.


Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenario here


Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.

Does notusuallycorrespond to atask step in thedocument;Reflects achoice to bemade after stepexecution

< F u n c t i o n >

E x t e r n a l

t o

S A P

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

918 Scen Overview en Cn

Documents

Transcript of 918 Scen Overview en Cn