advanced scheduling agreement with handling unit management(hum), returnable packaging and evaluated...

Advanced Scheduling Agreement with Handling Unit Management(HUM) , Returnable Packaging and Evaluated Receipt Settlement (ERS)

SAP Best Practices for Automotive Package (Japan)

SAP Best Practices

Scenario Overview – 1

Purpose The business scenario is designed for the business processes in Packaging

Logistics between Automotive OEMs and suppliers, During the whole logistics process, Repetitive Manufacturing, Handling Unit Management (HUM), Automatic Packing with Packing Instructions, Returnable Packaging, and Credit Memo Processing are fully integrated. The OEM uses Evaluated Receipt Settlement (ERS) as the settlement method with the Supplier.

Benefits Various business information (delivery schedule/delivery/Invoice/Payment) is

synchronized immediately via EDI IDoc transfer between OEM and supplier . Handling Unit proposals are created automatically with packing instruction and

fully integrated with Repetitive Manufacturing. With Returnable Packaging Logistics, the quantity of returnable packaging

materials are tracked accurately. When Evaluated Receipt Settlement (ERS) procedure is adopted, invoice

variances are eliminated when OEM posts the invoice document automatically on the basis of the data in the scheduling agreement and goods receipt .

Via receipt of self-billing document per EDI, verification of transmitted data is performed automatically.

Purpose and Benefits:


Enhancement Package 4 for SAP ERP 6.0

OEM Client: Accounts Payable Manager (AUTO) Warehouse Clerk Strategic Planner Purchaser Production Planner IT Administrator (Professional User) Warehouse Clerk (AUTO) Accounts Payable Accountant (AUTO) Accounts Payable Accountant

Company Roles Involved in Process Flows:

SAP Applications Required:


Supplier Client : Warehouse Clerk Warehouse Clerk (AUTO) Sales Administrator Logistics Execution Specialist Production Planner Shop Floor Specialist (AUTO) Billing Administrator Billing Administrator (DIFM) Accounts Receivable Accountant (AUTO) IT Administrator (Professional User) Accounts Receivable Accountant

Company Roles Involved in Process Flows:


OEM Process (Basic): Planned Independent Requirements Processing OEM Process (Basic): Material Requirements Planning – Single OEM Process (Basic): Creating Forecast/JIT Delivery Schedules OEM Process (Basic): Outputting Forecast/JIT Messages OEM Process (Return): Outbound Delivery of Returnable Packaging to Supplier Supplier Process (Return): Goods Receipt of Returnable Packaging at Supplier Supplier Process (Basic): Processing Forecast Delivery Schedule for Scheduling

Agreement Supplier Process (Basic): Material Requirements Processing Supplier Process (HUM): Displaying Packing Instructions Supplier Process (HUM): Creating Packing Requirements per OEM

Order/Scheduling Agreement & Plan Handling Supplier Process (HUM): Repetitive Manufacturing; Backflushing Packed Handling

Units Supplier Process (HUM): Creating Deliveries from Backflushed Handling Units Supplier Process (HUM): Picking Supplier Process (HUM): Creating Shipment for the Delivery

Key Process Flows Covered (1):


Supplier Process (Basic): Creating Billing Documents OEM Process (Basic): Goods Receipt for Inbound Delivery on the Basis of EDI

Shipping Notifications OEM Process (Return): Checking Postings in OEM’s Returnable Packaging

Account OEM Process (Return): Creating Returnable Packaging Account Statement Supplier Process (Return): Account Matching Supplier Process (Return): Displaying Movements of Returnable Packaging

Account OEM Process (Basic): Evaluated Receipt Settlement (ERS) (Credit Memo

Procedure) Supplier Process (Basic): Credit Memo Request Processing OEM Process (Basic): Payment Supplier Process (Basic): Payment Advice Comment Supplier Process (Basic): Settlement by Posting the Incoming Payment

Key Process Flows Covered (2):


Detailed Process Description:Advanced Scheduling Agreement with Handling Unit Management(HUM) , Returnable Packaging and Evaluated Receipt Settlement (ERS)

The OEM plans his material requirements and creates delivery schedules. The Forecast delivery schedule is directly transmitted to the supplier and via EDI. Then the Supplier manufactures the finished product in repetitive manufacturing, and processing of outbound and inbound delivery with handling units and returnable packaging material.

The OEM provides the Supplier with empty (returnable) packaging. The Supplier then returns this returnable packaging complete with the required goods. The movements and quantities of returnable packaging are posted to the OEM’s and Supplier’s returnable packaging accounts. Account statements are sent at agreed regular intervals by the OEM and transmitted via EDI. On receipt of the account statement, the Supplier carries out account matching to compare the account statement transactions with the postings in his own account.

Advanced Scheduling Agreement with Handling Unit Management (HUM), Returnable Packaging Processing and Evaluated Receipt Settlement (ERS)

Supplier Client / Plant 1000OEM Client / Plant 1000

Material Requirement Planning Run

Create Forecast./JIT Delivery Schedule

Create Packing Requirement and Create Planed Handing Units

Repetitive Manufacturing ; Backflush Packed Handing Units

Create Delivery for Handing Units & check output

Goods Receipt: Returnable Packaging material

Goods Receipt

Returnable Packaging Account Statement

Planned Independent requirement

Deliver Returnable Packaging material

Material Requirement Planning Run

Billing

Returnable Packaging Account Statement

Picking & Goods Issue

Inbound Delivery

Create Shipment

DESADV

ACCSTA

Forecast./ JIT Delivery Schedule in Schedule AgreementDELFOR

DELJIT

Process Flow Diagram - 1

Supplier Client / Plant 1000OEM Client / Plant 1000

Returnable Packaging Account Matching

Self-Billing

Incoming Payment

Evaluated Receipt Settlement (ERS)

Payment Run

SBWAP

REMADV

Payment Advice

Advanced Scheduling Agreement with Handling Unit Management (HUM), Returnable Packaging Processing and Evaluated Receipt Settlement (ERS)

Process Flow Diagram - 2

A-55-1200_SUPHCU-Pump

A-55-2300_SUPECO-Steering unit type

A-55-VA1-1100_SUPEuro pallet

A-55-VA1-1200_SUPBox 4314

A-55-VA1-1300_SUPInlay for Box

A-55-VA1-1100_OEMEuro pallet

A-55-VA1-1200_OEMBox 4314

A-55-VA1-1300_OEMInlay for Box

A-55-2000_SUPABS_1_Four Wheel Unit Type

A-55-2000_OEMABS_1_Four Wheel Unit Type

A-55-1100_SUPAluminium valve block

OEM Client /Plant 1000 Supplier Client /Plant 1000

Finished Product, Material Type = FERT

Semi-finished Product, material type = HALB

Packing Material, material type = VERP

Master DataAdvanced Scheduling Agreement with Handling Unit Management(HUM) , Returnable Packaging and Evaluated Receipt Settlement (ERS)

Determination recordsDetermination records

Box 4314

A55-2000_SUP

Inlay

Packing Instruction Packing Instruction PV-A55-2000_SUP-EPAL

11

44

55

11

4040 Packing Instruction PV-A55-2000_SUP-KLT

A55-VA1-1100_SUP / Euro pallet

A55-VA1-1200_SUP / Box 4314 Returnable Packaging

A55-VA1-1300_SUP / Inlay for Box

Customer Material ... Packing Instruct. A55-2000_SUP PV-A55-2000_SUP-EPAL A55-VA1-1100_SUP (Pallet)

PV-A55-2000_SUP-KLT

A55-2000_SUP / ABS_1_ Four Wheel unit type 2

Packing InstructionAdvanced Scheduling Agreement with Handling Unit Management(HUM) , Returnable Packaging and Evaluated Receipt Settlement (ERS)

Legend

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.


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


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

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


Budget Planning: Indicates a budget planning document


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.

<Fun

ctio

n>E

xter

nal t

o S

AP

Business Activity /

Event

Unit Process

Process Reference

Sub-Process

Reference

Process

Decision

Diagram Connection

Hardcopy / Document

Financial Actuals

Budget Planning

Manual Proces

s

Existing Version /

Data

System Pass/F

ail Decisio

n