multi-level third-party order ... - websmp104.sap-ag.desapidp/011000358700001067292013e/... ·...

Automotive Consulting SolutionMulti-Level Third-Party Order Processing with Scheduling

Agreements/Single Orders

2© SAP SE or an SAP affiliate company. All rights reserved.

Agenda

1. Benefit for the Customer

2. Description of the Function

3. The Function in the System

4. Technical Information


Customer Benefit

Proven solutions/services of SAP Automotive Consulting

Solutions already running productive at several customers

Solutions and documentation are available in German and English

Prompt implementation possible

Defined timeframe for implementation

Exact calculation of implementation cost. Implementation for fixed price

6 months of free follow up care operations for bug corrections starting at

the date of installation within the development landscape. Afterwards

chargeable consulting support starts

No additional ongoing costs (i.e. maintenance cost)

Time

Cost

Solution


Agenda






Process overview Single-Level Third-Party Order Processing

Single-Level Third-Party Order Processing with Scheduling Agreements

Process overview Multi-Level Third-Party Order Processing

Multi-Level Third-Party Order Processing with Scheduling Agreements

Multi-Level Third-Party Order Processing with Single Orders

Description of the function - Overview


Process overview Single-Level Third-Party Order

Processing

CustomerThird-party

vendor

Deliveries

to

customers

Physical delivery

Supplier

Invoices to

customers


Single-Level Third-Party Order Processing with

Scheduling Agreements

Monitor Third-

Party Order

Processing

Inb

ou

nd

de

live

ry

IB-d

eliv

ery

Deliv

ery

OB

-de

live

ry

InvoiceInvoice

Self Billing

Invoice

verification

InvoiceInvoiceInvoice

verificationSelf Billing

ASN Customer

Third-Party

ASN

Assembly

Goods

receipt

Delivery (OB)

SD Scheduling

agreement

Forec. del. sched./

JIT del. schedules

Forec. del. sched./

JIT del. schedulesPrel.

planning

MM SA

SD Sched.

Agreement

Demand planning

MM Sched.

Agreement

Production

Demand

planning

CustomerThird-party

vendorSupplier


Process overview Multi-Level Third-Party Order

Processing

CustomerThird-Party

Vendor

Delivers to

the

customer

Sales Unit/

Supplier

Bills to the

customer

Headquarter

Orders

always

Forwards the

order

or

Delivers itself

to the

customer


Process overview Multi-Level Third-Party Order

Processing

In contrast to the Single-Level Third-Party Order Processing so called sales units, which are the direct contacts for the end customer have to purchase their material always from the headquarter.

According to the situation:

a production location is located near the end customer

certain customers are always supplied by certain locations

certain materials are produced only in one location

it is decided or maintained if the assignment is forwarded to a Third-Party Vendor (Multi-Level Third-Party Processing) or if the headquarter itself occurs as Third-Party Vendor (Single Third-Party Order Processing). This decision is done automatically via a control table at the creation of the sales order or SD scheduling agreement.


Multi-Level Third-Party Order Processing with Scheduling

Agreements

Invoice/

Self Billing

FDS

JIT DS

FDS

JIT DS

FDS

JIT DS

CustomerThird-Party

VendorSales unit/Supplier Headquarter

Monitor Third-

Party Order

Processing

Inb

ou

nd

de

livery

GR

-in

bo

un

d

de

livery

Deli

very

GI-

de

livery

Monitor Third-

Party Order

Processing

Inb

ou

nd

de

livery

GR

-in

bo

un

d

de

livery

Deli

very

GI-

de

livery

MM-

scheduling

agreement

SD-sched. agreement

Demand planning

MM-sched.

agreement

SD-sched. agreement

Demand planning

MM-sched.

agreement

SD-sched.

agreement

Delivery /

Goods

issue

Goods

receipt

ASN to customer

InvoiceInvoice

verificationInvoice

Invoice

verificationInvoice

Third-Party

ASNThird-Party

ASN

Invoice/

Self Billing

Invoice/

Self Billing

Invoice

verification


Multi-Level Third-Party Processing with

Single Orders

Purchase

orderPurchase

orderSingle

Order

Purchase

order

Delivery/

Goods

issue

Goods

receipt

ASN to customer

InvoiceInvoice

verification

Third-Party

ASNThird-Party

ASN

Single Order

Demand planning

Purchase Order

Single Order

Demand planning

Purchase Order

Purchase

Order

CustomerThird-Party

VendorSales unit/Supplier Headquarter

Monitor Third-

Party Order

Processing

Inb

ou

nd

de

livery

GR

-in

bo

un

d

de

livery

Deli

very

GI-

de

livery

Monitor Third-

Party Order

Processing

Inb

ou

nd

de

livery

GR

-in

bo

un

d

de

livery

Deli

very

GI-

de

livery

Invoice/

Self Billing

Invoice

verificationInvoice

Invoice

verificationInvoice

Invoice/

Self BillingInvoice/

Self Billing


Motivation

In addition to the topics, which already apply for the Single-Level Third-Party Order Processing like e.g.:

Connection of „external Third-Party Vendors“, which shall not work in one‘s own system by using standardized messages/interfaces

Automated processing of the third-party process to minimize manual effort („cross-system third-party order processing“)

Concentration on alerts at the supplier („Monitor for third-party order processing“), to minimize manual effort

Support of all SAP standard functions (e.g. Self Billing/Invoice verification in sales and purchase)

Traceability/Reporting (Creation of documents, „Monitor for Third-Party Order Processing“)

Usage of synergies through shorter transportation routes, lower transport costs or tax advantages

The following criteria can be the reason for implementing a Multi-Level Third-Party Order Processing:

Central management of pricing: By specifying the procurement of all materials via the headquarter, prices for the sales units can be managed centralized.

Central buying: Achievement of better conditions in procurement of material through centralization into one corporation (Headquarter)


Cross-company selling vs. Multi-Level Third-Party Order

Processing

Decision cross-company selling vs. Multi-level Third-Party Order Processing:

If suppliers do not work in one‘s own system cross-company selling is not possible. Mixing of processes, partly cross-company selling, partly Multi-Level Third-Party Order Processing therefore should not be aimed at. process harmonization

With cross-company selling the availability can be checked in the delivering plant during order creation whereas with scheduling agreements normally no availability check is executed

With a classical customer-vendor-relationship, which is reflected by Third-Party Order Processing, e.g. all CO reports can refer directly to the standard documents. No enhancements are needed, which would be needed for classification during cross-company selling

As part of a corporate group, which consists of many corporations from an IT perspective it is much easier to „extract“ a company code if it is already bound by a customer-vendor-relationship

Partly, a considerable effort emerges to enhance further ACS like e.g. incoming orders/orders for cross-company selling


Project relevant topics I

Creation of master data (customer master, material master, pricing conditions, purchasing info records, …)

Timely transmission of changes to the Third-Party Vendors:

With scheduling agreements mainly through the forecast delivery schedule (change of unloading point).

With single orders through a separate change program, which forwards changes to the subsequent documents.

Export and foreign trade topics

Country specific Requirements: e.g. ascending invoice number without gaps, pro forma invoice

Value tax determination: Very complex handling/requirements in the Multi-Level Third-Party order processing

Consideration in reports/evaluations (double turnover in processes between single corporations of a corporation group) Classification possible e.g. through own Third-Party Plant


Project relevant topics II

Handling of returns and return deliveries

Competencies in the returnable packaging logistics, handling of packaging materials

Traceability (Batches, handling units)

Connection of Third-Party Vendors e.g. via EDI / WEB / fax

Usage/Integration of further ACS possible:

Usage of the ACS Exit-Control-Framework especially in the EDI inbound and outbound processing

Usage of the ACS Delivery Service Level

Usage of the ACS Vendor Evaluation

Usage of the ACS Orders on hand/Incoming orders


Project relevant topics III

During creation of the single order or the SD scheduling agreement for the end customer it

should be decided automatically if a single or Multi-Level Third-Party Order Processing is

existing. Two steps are to be taken into consideration here:

Determination of the right item category so that the forwarding of the demands and the information can be controlled

Recording of the information if a Single- or Multi-Level Third-Party Order Process is existing to provide the tax determination with information (e.g. country codes of the involved business partners: end customer, sales organization, headquarter, Third-Party Vendor) accordingly

Consistent prices between purchase and sales of the involved corporations/company codes. Through customizing it can be adjusted e.g. that the purchasing prices use the price determination of the sales organization of the supplier if the business partners are in one system and client

Re-referencing of the item category during creation of orders with reference to the quotation

Order confirmations of Third-Party Vendors have to be forwarded to the customer: e.g. by creating the outgoing message to the end customer as soon as the confirmed date receives a correct date value


Agenda






Cockpit

Change Monitor for Single Orders

Document Flow Monitor

Monitor for Incoming Third-party Shipping Notifications

The function in the system - Overview


Cockpit – Overview Third-Party transactions

For a better overview, the relevant Third-Party transactions are consolidated in a cockpit.

The transactions listed in the cockpit also contain parts of the additional ACS for an automatic

master data check and master data creation.


Change Monitor for Single Orders – Selection


Change Monitor for Single Orders – Output list

Output list before the changes were forwarded:

Output list after the changes were forwarded:


Change Monitor for Single Orders – Selection of functions I

After an order was created in the sales organization and forwarded automatically to the

Headquarter and the Third-Party Vendor it can happen that nevertheless changes have to be

made which therefore have to be forwarded to the corresponding documents (purchasing

order and sales order).

The program can be scheduled in a job in the background to forward changes automatically.

The following changes are currently taken into consideration:

Shipping conditions on header level

Delivery block on header level

Address changes or changes of the partner number of the ship-to party on header or item level

Change of the order quantity on item level

Change of the rejection code on header or item level

Change of the delivery date in the schedule line

These changes can be done when the order of the Third-Party Vendor is still open. Otherwise

the change cannot be saved.


Change Monitor for Single Orders – Selection of functions II

The following functions can be executed in the monitor:

If a change has already been done manually in the subsequent documents

the registered change record can be marked as completed via this button.

Via this button the selected changes are executed in the subsequent

documents.

If a change is obsolete and the no longer relevant for the subsequent

documents the registered change record can be deleted via this button.

Duplicate changes to an order can be compressed by this button.


Document Flow Monitor - Selection


Document Flow Monitor – Output list


Document Flow Monitor – Selection of functions

Colorful characterization of the content of the columns according to the belonging of the data

to the respective role in the process:

Yellow columns: data content of the Sales Unit/Supplier

Blue columns: data content of the Headquarter

Green columns: data content of the Third-Party Vendor

Starting point in the selection is only possible with the sales view of the sales organization.

Possibility to jump into the scheduling lines of individual orders and into the

view of forecast delivery schedules of scheduling agreements.

Print order confirmation: for the message type selected on the selection

screen e.g. BA00 – order confirmation the primary processing is triggered.

This function is only intended for orders not for scheduling agreements.

Refresh document flow: the output list is refreshed and the data selection

is triggered again.

+


Monitor Third-Party Shipping Notifications – Selection


Monitor Third-Party Shipping Notifications – Output list

A detailed description of the monitor‘s functions are available in the separate ACS presentation

„Third-Party Order Processing with Scheduling Agreements“.


Agenda






Technical Information

Available for SAP ERP ECC 6.0

Activation of automotive industrialized solution in SAP ERP System not

necessary

Technical installation is possible remotely

Modification-free

Delivery in Z-namespace


Source of Information

OSS-System

Notes (Search term: Automotive Consulting Solutions)

Internet

Overview-, Detail- and Customer presentations

http://www.sap.com/acs

Email - distribution list

Signing up through [email protected]

http://www.sap.com/acs

Thank you!

Mario Rebitzer

Platinum Consultant

Industry Area Automotive

SAP Deutschland SE & Co. KG

Hasso-Plattner-Ring 7

69190 Walldorf, Germany

M +49/ 170 22 00 287

S +49/ 6227 7 44674

E [email protected]

mailto:[email protected]


© SAP SE or an SAP affiliate company.

All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an

SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE

(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional

trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,

and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or

SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and

services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related

presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated

companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be

changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,

promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties

that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking

statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx

multi-level third-party order ... - websmp104.sap-ag.desapidp/011000358700001067292013e/... ·...

Documents