Subcontracting (External & Internal) SAP Best Practices for Chemicals (Russia) SAP Best Practices
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Subcontracting (External & Internal) SAP Best Practices for Chemicals (Russia)
SAP Best Practices
© SAP 2008 / Page 2
Purpose The purpose of to describe business processes related to internal and external
subcontracting.
Purpose and Benefits:
Scenario Overview
© SAP 2008 / Page 3
Required SAP ECC 6.00 EhP3
Company roles involved in process flows Warehouse Clerk Production Planner Shop Floor Specialist Accounts Payable Quality Specialist Sales Administration Buyer Sales Billing
SAP Applications Required:
Scenario Overview
© SAP 2008 / Page 4
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 Processing
MRP 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 / Page 5
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 validate sales order (Job
Order)
Provide material (components) to the
subcontractor
Process material
Generate material request automatically
Business View - 1
© SAP 2008 / Page 6
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 release invoice
Check and release payment
Business View - 2
© SAP 2008 / Page 7
External subcontracting
Vendor: S-1003
SAPChem AGPlant 1000
Vendor: S-9000(subcontractor)
Purchase order for components with delivery address to subcontractor
Invoice
Invoice
Delivery to subcontractor
Goods delivery
Delivery of components
Purchse order
CH-6210 (GranuSAP, 100 kg)
© SAP 2008 / Page 8
Process Flow Diagram –External Subcontracting
Bu
ye
rW
are
ho
us
e
Cle
rk
Ac
co
un
ts
P
ay
ab
le
Ev
en
tV
en
do
r
Receive Material at
Dock
Delivery Pick List
GR/IR PPV Vendor
MRP = Material Requirements Planning, PO = Purchase Order, GR/IR = Goods Receipt/Invoice Receipt, PPV = Purchase Price Variance
Incoming Vendor Invoice
Delivery Note
Invoice Receipt
Pick Confirmation
Goods ReceiptPost Goods Issue
Create Delivery Request
Create Subcontract PO
Inventory GR/IR Subcontracting
Services/Consumption
Print GR Slip
Requirement of Subcontracting
Material
Qu
ali
ty
Sp
ec
iali
st Quality
Inspection Record Results
Stock transfer for subcontractor
Th
ird
P
art
y
Create PO for Special Stock
Subcontract PO
Requirement of Material
(Component)
Approve PO
Subcontract PO
© SAP 2008 / Page 9
Internal subcontracting
Filling
Canister, 5 kgVERP
CH-4200
PowerPaint, redYQFP
CH-6800
Material providedMaterial provided
Paint, redYQNM
CH-0500 Plant 1000
Description
Mat. type
Mat Nr
WM managed
QM active batch managed
CH-6800 (PowerPaint, red)
© SAP 2008 / Page 10
Cu
sto
me
r
Sh
op
F
loo
r S
pec
iali
st
Sal
es
Ad
min
istr
atio
n
Sal
es
Bill
ing
Eve
nt
Customer Needs to Buy
Product
Inventory COGS
AR= Accounts Receivable, COGS = Cost of Goods Sold, MRP = Material Requirement Planning
Delivery NoteOrder
Confirmation
Pick List
Billing Document
War
eh
ou
se
Cle
rk
Billing
Process Flow Diagram –Internal Subcontracting
Pro
du
ctio
n
Pla
nn
er
MRP
MRP List
Planned Orders
Creating Planned Independent
Requirements
Inventory Consumption @ Standard. Cost
ConvertPlanned Order
to Process Order
Process Order Confirmation
Create Delivery Request
Post Goods Issue
Beginning of Planning
Cycle
Availability Check of Non
Provided Materials
Sales Order Entry
© SAP 2008 / Page 11
Legend
Symbol Description Usage Comments
To next / From last Diagram: Leads to the next / previous page of the Diagram
Flow chart continues on the next / previous page
Hardcopy / Document: Identifies a printed document, report, or form
Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines
Financial Actuals: Indicates a financial posting document
Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines
Budget Planning: Indicates a budget planning document
Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines
Manual Process: Covers a task that is manually done
Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.
Existing Version / Data: This block covers data that feeds in from an external process
Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines
System Pass / Fail Decision: This block covers an automatic decision made by the software
Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.
Diagram Connection
Hardcopy / Document
Financial Actuals
Budget Planning
Manual Proces
s
Existing Version /
Data
System Pass/F
ail Decisio
n
Symbol Description Usage Comments
Band: Identifies a user role, such as Accounts Payable 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 band contains 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 two tasks in a scenario process or a non-step event
Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario
Does not correspond to a task step in the document
Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario
Corresponds to a task step in the document
Process Reference: If the scenario references another scenario in total, put the scenario number and name here.
Corresponds to a task step in the document
Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here
Corresponds to a task step in the document
Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.
Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution
<F
unct
ion>
Ext
erna
l to
SA
P
Business Activity /
Event
Unit Process
Process Reference
Sub-Process
Reference
Process
Decision