1. Scheduling Agreement with Forecast Delivery Schedule, KANBAN and Invoice Processing SAP Best Practices for Automotive Package (Japan)
SAP Best Practices

2. Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
Scheduling Agreement with Forecast Delivery Schedule, KANBAN and Invoice Processing shows a complete process of OEM and Supplier collaboration, including forecasting delivery schedule, delivery , invoice and payment advice synchronization between OEM and Supplier. The scenario also show the KANBAN and Repetitive Manufacture functionalities.
Benefits
Planning information is synchronized between OEM and Supplier with Forecast Delivery schedule in order to shorten the planning cycle.
Supplier delivery information is updated in a timely manner to ensure safety of the goods sent to OEM.
Invoice payment information is synchronized in a timely manner to improve the accuracy of financial information and shorten the cash flow cycle.
Efficient manufacturing on the Supplier side is carried out with KANBAN and Repetitive Manufacturing.

3. Scenario Overview – 2 SAP Applications Required:
Enhancement Package 4 for SAP ERP 6.0
OEM client
Employee (Professional User)
Accounts Payable Manager (AUTO)
Accounts Payable Accountant
Accounts Payable Manager
Billing Administrator BR
IT Administrator (Professional User)
Production Planner
Purchaser
Warehouse Clerk
Supplier client
Accounts Receivable Accountant (AUTO)
Accounts Receivable Accountant
Sales Administrator
Shop Floor Specialist
Warehouse Clerk (AUTO)
Company Roles Involved in Process Flows:

4. Scenario Overview – 3 Key Process Flows Covered:
OEM Process: Confirming Vendor
OEM Process: Creating Independent Requirements Processing
OEM Process: Maintaining Source List
OEM Process: Material Requirements Planning
OEM Process: Maintaining Scheduling Agreement Schedule Lines
OEM Process: Creating Delivery Schedules
Supplier Process: Displaying Customer Scheduling Agreement
Supplier Process: Processing Forecast Delivery Schedule for Scheduling Agreement
Supplier Process: Material Requirements Planning
Supplier Process: Maintaining Scheduling Agreement Schedule Lines
Supplier Process: Evaluating the Stock/Requirements List
Supplier Process: Creating Delivery Schedules
Supplier Process: Production Supplying with Kanban and MRP for Materials Procured Externally
Supplier Process: Production Supplying with Kanban and MRP for Materials Procured via Stock Transfers from the Central Warehouse
Supplier Process: Production Supplying with Kanban and MRP for Materials Produced Internally
Supplier Process: Repetitive Production - Backflushing for Finished Products

5. Scenario Overview – 4 Key Process Flows Covered:
Supplier Process: Delivery Processing
Supplier Process: Displaying Shipping Notification
Supplier Process: Picking/Creating Transfer Order
Supplier Process: Posting Goods Issue for Delivery
OEM Process: Shipping Notification/Confirmation Processing
OEM Process: Goods Receipt Posting
Supplier Process: Process Billing Due List
Supplier Process: Displaying Billing Document
OEM Process: Displaying EDI Inbound Invoice
OEM Process: Processing Invoice with Reference
OEM Process: Payment Advice Comment
Supplier Process: Checking Payment Advice Comment
Supplier Process: Displaying Payment Advice Comment
Supplier Process: Displaying the Open Items
Supplier Process: Posting the Incoming Payment

6. Scenario Overview – 5 Detailed Process Description:
Scheduling Agreement with Forecast Delivery Schedule, KANBAN and Invoice Processing
The OEM transfers the long term planning information to the Supplier. Later, when the OEM receives the short term planning information based on the MRP run, it will also be transferred to the Supplier.
Based on the planning information, the Supplier will start the manufacturing. The manufacturing on the Supplier side needs to be performed with a high degree of efficiency, therefore, KANBAN is used together with Repetitive Manufacturing.
After the finished goods are produced at the Supplier, the delivery is posted. This time, the OEM receives the delivery information in advance, and prepares a goods receipt.
The OEM and Supplier will then perform the invoice/payment process, and synchronize this information through the system.
After the whole process, the supplier will develop the plan for the later procurement, based on the historic data, and long term planning information from the OEM side.

7. Scheduling Agreement with Forecast Delivery Schedule, KANBAN and Invoice Processing
OEM client / Plant 1000
Supplier Client / Plant 1000
Planned Individual requirement
MRP Run
DELFOR
Create Forecast Delivery Schedule
Forecast Delivery Schedule in SD Scheduling Agreement
MRP Run
KANBAN (External Procurement)
KANBAN (Stock Transfer)
KANBAN (In-house production with REM)
REM Backflush for Finished Product
Inbound Delivery
Create Delivery
Picking via Lean warehouse
DESADV
Post Goods Issue
Goods Receipt
INVOIC
Inbound Invoice
Billing
REMADV
Payment Run
Payment Advice
Post Incoming Payment

8. Scheduling Agreement with Forecast Delivery Schedule, KANBAN and Invoice Processing – Master Data
OEM client / Plant 1000
Supplier Client / Plant 1000
A _OEM
ABS_4_System
KB - REM
A _SUP
ABS_4_System
KB - REM
A _SUP
Aluminimum-valveblock
A _SUP
HCU-pump
KB - REM
A _SUP
ECU-Control Unit
KB - REM
KB-STr
A _SUP
Aluminium-valveblock(raw)
A _SUP
Electric motor (with wire & plug)
KB-ExP
A _SUP
ECU-control unit (purchased part)
A _SUP
Needle bearing
A _SUP
ACU-seal
A _SUP
SO-valve(drop out open)
A _SUP
Needle bearing Grease
A _SUP
Screw M4*55
A _SUP
SO-valve(drop out closed)
A _SUP
piston
A _SUP
Sealssplint
A _SUP
Springs
KB-STr
KANBAN with Stock Transfer from
Storage location 1040 to 1020
KB-ExP
KANBAN with External Procurement
A _SUP
Screw M4*55
Finished Product, Material Type = FERT
KB - REM
KANBAN with REM Production
Semi-finished Product, material type = HALB
A _SUP
Pump-seal
Raw Material, material type = ROH

9. Legend Symbol Description Usage Comments Symbol Description
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.
Diagram Connection
<Function>
Hardcopy / Document
External to SAP
Financial Actuals
Business Activity / Event
Budget Planning
Unit Process
Manual Process
Process Reference
Existing Version / Data
Sub-Process Reference
System Pass/Fail Decision
Process Decision