240 Scen Overview en CN

7/29/2019 240 Scen Overview en CN

1/6

Engineer-to-Order (ETO)

Project Assembly

(240)

SAP Best Practices forDiscrete Manufacturing V1.603(China)

SAP Best Practices


2/6

Scenario Overview 1

Purpose

This scenario describes the order processing in a standard Engineer-to-Order (ETO) environment.

SAP Project System is used to control the whole process, from the SD requirement to planning, purchasing,production and delivery.

SAP Project-Oriented Procurement (ProMan) is used as an advanced tool to control the planning/purchasingsteps in the order procedure.

Benefits

Project structuring/execution via project system is used to control the collaboration between different departments

Milestone billing is used to control the progressive payment procedure, and track back the status of the project

Use of ProMAN to control and monitor the manufacture/procurement procedures centrally

Delivery the semi-finished goods via the project

Handling the final assembly on customer site using network activity in the project

Key process flows covered

Creation of sales order with reference to the quotation

Rescheduling of project

Use of ProMan for procurement process Reporting of milestones

Confirm project activities

Subassembly for various semifinished goods

Delivery to customer

Purpose and Benefits:


3/6

Scenario Overview 2

Required

SAP ECC 6.03

Company roles involved in process flows Sales Administration

Project Manager

Sales Billing Accounts Receivable Accountant 1

Accounts Receivable Accountant 2

Buyer

Purchasing Manager

Warehouse Clerk

Production Planner

SAP Applications Required:


4/6

Scenario Overview 3

Engineer-to-Order (ETO) Project Assembly

This scenario describes a business process in a typical engineer-to-order (ETO)environment. The project system is used to control the complete process from SDrequirement to planning, purchasing, production, and delivery. Project-OrientedProcurement (ProMan) is used to control the planning/purchasing steps.

The process starts with the creation of a sales order with reference to the quotation.

Adoption of project data to the sales order (e.g. finished date, rescheduling of project)

Execution of advanced procurement for long lead-time materials using ProMan forrequirements planning

Creation of project milestones to provide a basis for a SD billing plan

The prework for the project will be done by R&D and the activities will be createdunder a WBS element and confirmed later on. The first advance payment of thecustomer should be received.

Goods receipt for long lead-time components and check of availability of stock

materials

Materials requirements planning using ProMan to create planned orders over thewhole BOM

Subassembly for various semifinished products and confirmation in WBS element. Thecustomer should pay the second advance payment.

Delivery of components to the customer

Final payment of the customer

Detailed Process Description:


5/6

Process Flow Diagram (1)Engineer-to-Order (ETO) Project Assembly

Accounts

receivable

accountant

Ware-

house

Clerk

ProjectManager

Produc-

tion

Planner

Advance

d

Procure

men

t

Sales

Admini-

stration

Sub

se-

que

nt

proc

ess

es

ProManMRP run;

Creation ofplanned

order

Transfermilestones

to SalesOrder

ProMan MRPfor project

Create Salesorder with

reference toquotation

Rescheduleproject and

release

BillingDown

payment

SettleDown

Payment

Release ofactivities inR&D WBSelement

Confirmactivities inR&D WBSelement

ConfirmR&D

activity

Goodsreceipts forcomponent

s

Conversionto

productionorder

Confirmingproductionactivities

Goodsreceipt forproduction

order

Createdelivery

fromproject

Post goodsissue

Releaseactivity for

finalassembly

Billing 2ndadvancedpayment

Settle 2ndadvancedPayment

Reporting

ETOQuotationprocessin

g (232)

Period endclosing

GeneralPlant

(181)

Accounts

receivable(157)

Sales:Period End

ClosingOperations (203)

Billing 1stadvancedpayment

Settle1stadvancedpayment

Release ofProduction

WBSelement

Release ofLong-Lead

timePurchase

Order

Post rawmaterials to

Project

Goodsissue for

productionorder

Confirmproduction

order

Confirmactivities of

finalassembly

Billing FinalSettlement

Settle FinalSettlement

CloseProject

technically


6/6

Legend

Symbol Description Usage

Comments

Band: Identifies a user role, such as AccountsPayable Clerk or Sales Representative. This bandcan also identify an organization unit or group,rather than a specific role.

The other process flow symbols in this table go intothese rows. You have as many rows as required tocover all of the roles in the scenario.

Role bandcontains taskscommon to thatrole.

External Events: Contains events that start or end thescenario, or influence the course of events in thescenario.

Flow line (solid): Line indicates the normal sequenceof steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line canalso lead to documents involved in the process flow.

Connects twotasks in ascenario

process 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 another

scenario in total, put the scenario number and namehere.

Corresponds to

a task step inthe document

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

Corresponds toa task step inthe document

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

Symbol Description Usage Comments

To next / From last Diagram: Leads

to 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.

External

to

SAP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n

240 Scen Overview en CN

Documents

Transcript of 240 Scen Overview en CN