Automotive Consulting Solution. Monitor for outbound ASN-status

Automotive Consulting Solution Monitor for outbound ASN-status Agenda 1. Benefit for the Customer 2. Description of the Function 3. The Function in...
Author: Victor Short
8 downloads 0 Views 1MB Size
Automotive Consulting Solution Monitor for outbound ASN-status

Agenda

1. Benefit for the Customer 2. Description of the Function 3. The Function in the System 4. Technical Information

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

2

Customer Benefit

Solution  Proven solutions/services of SAP Automotive Consulting  Solutions already running productive at several customers  Solutions and documentation are available in German and English

Cost

 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  Prompt implementation possible  Defined timeframe for implementation

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

3

Agenda

1. Benefit for the Customer 2. Description of the Function 3. The Function in the System 4. Technical Information

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

4

Process Overview Supplier EDI-sub system

Customer

Supplier ERP-system

ASN

ASN

(856)

(DELVRY/SHPMNT)

Delivery/Goods Issue Monitor for outb. ASN status

Techn. Acknowledgement of receipt (997)

Check ASN content

Content acknowledgement of receipt

Techn. acknowledgement of receipt (STATUS)

(824)

Content acknowledgment of receipt (DELVRY(824))

Confirmation of goods receipt

Confirmation of goods receipt

(861)

(DELVRY(861))

Delivery status

997

824

861

Monitor for content check

Monitor for confirmation of goods receipt

Goods receipt Material delivery

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

5

Prozess description

Particularly on the american market, among other, the following ANSI messages  Code 997 – Technical acknowledgement of receipt  Code 824 – Content acknowledgement of receipt  Code 861 – Confirmation of goods receipt are used for the surveillance and status confirmation of ASN message At the shipping process from the supplier to the customer, shipping notifications (ASNs) are send to the customer. With the creation of an ASN, the SAP ACS creates for each delivery item an entry in the “Monitor for outbound ASN-status”. Some customers transmit a confirmation, that the ASN has arrived successfully. This technical acknowledgement of receipt has the ANSI-code 997 and is processed in the SAP ERP as an IDoc-status and displayed in the “Monitor for outbound ASN-status”. The next step is the check of the ASN related to contents at the customer side. As a feedback of this check, the supplier receives another message with the ANSI-code 824. As far as the customer is informing about errors, the latter need to be corrected and a new, corrected ASN has to be sent to the customer. As soon as the material arrives at the customer, the goods receipt is posted. The result of the goods receipt inspection as well as e.g. deviations of cums are transmitted to the supplier with the ANSI-code 861.

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

6

Motivation

 Prevention of penalty payments for incorrect or missing ASNs.  Prevention of a negative vendor evaluation

 Creation of a possibility for a monitoring in the ERP-system (no print outs from the EDI-sub system)  Increasing of the transparency of the EDI-processes via a direct connection to the outbound delivery  User friendly possibility for monitoring:  Consolidation of the different messages (ANSI 997, 824, 861) in one central monitor  Provision of important functionalities like e.g. the creation of cancelation- and repetition messages

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

7

Agenda

1. Benefit for the Customer 2. Description of the Function 3. The Function in the System 4. Technical Information

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

8

Overview over functionalities

 Individual maintenance of process flows per EDI-exchange partner (Extract of transactions for the maintenance)  Monitor for outbound ASN-status  Own processing logic  Monitor for incoming content acknowledgements of receipt (824)  Own processing logic  Monitor for incoming confirmations of goods receipt (861)  Own processing logic

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

9

Overview over functionalities

 Individual maintenance of process flows per EDI-exchange partner (Extract of transactions for the maintenance)  Monitor for outbound ASN-status  Own processing logic  Monitor for incoming content acknowledgements of receipt (824)  Own processing logic  Monitor for incoming confirmations of goods receipt (861)  Own processing logic

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

10

Receipt control for outbound ASNs: The function in the system

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

11

Receipt control for outbound ASNs: Possible settings

For each EDI-recipient the following settings could be done: 







Planned transmission status of an ASN: Dependant on the customers behavior, the he is transmitting technical confirmations of the rceipt of an ASN, the status of the outbound IDoc end up differently. In the settings could be maintained, which IDoc status could be reached at its’ maximum, so that a transmission is considered correctly. Expectation of a content check (824): Some customers always, only in cases of errors or never transmit 824 messages. With this set up could be determined, in what way 824 messages are expected from the customer. Furthermore, it could be adjusted, after what time the status for 824 should become automatically green, as soon as no error for an 824 message is transmitted from the customer. Expectation of a goods receipt message (861): Analog to the logic of the 824, 861 messages are always, only in cases of errors or never transmitted. For each EDI recipient could be set up, in what way the 861 message from the customer is to be expected. At the set up “In case of errors”, the status in the ASN monitor becomes automatically green, until the customer transmits an error. Notification of users: Additionally to the display in the corresponding monitors for the transmission of 824- and 861 messages, the notification (e.g. via E-mail, SMS, …) could be set up. Therewith could be controlled, that only in the case of transmitted errors a notification is sent to a user, so that he could go to the monitor for detailed analysis.

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

12

Overview over functionalities

 Individual maintenance of process flows per EDI-exchange partner (Extract of transactions for the maintenance)  Monitor for outbound ASN-status  Own processing logic  Monitor for incoming content acknowledgements of receipt (824)  Own processing logic  Monitor for incoming confirmations of goods receipt (861)  Own processing logic

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

13

Monitor for outbound ASN-status: Selection

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

14

Monitor for outbound ASN-status: Selection

In the selection, the following options may be chosen: 

IDoc number of the ASN

 

Creation date of the ASN IDocs Goods receipt date at the customer

 

Outbound delivery number Shipping point

 

Number of the ship-to Plant

 

Shipment number Number of the sold-to

 

Actual goods issue date Several status of the ASN IDocs

Furthermore, there is the possibility to branch to all the set up transactions. All these fields are displayed in the output list. It’s also possible to link to the monitors of the 824 and 861 messages. © SAP SE or an SAP affiliate company. All rights reserved.

15

Monitor for outbound ASN-status: Output list

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

16

Monitor for outbound ASN-status: Functions

In the output list, the following functions are possible: Go to change an outbound delivery Go to transaction VL09 to cancel the goods issue Post goods issue for an outbound delivery Send out the cancelation message of an ASN Send out the repetition message of an ASN Go to Monitor of Application Advice (824) Go to Monitor of Receiving Advice (861)

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

17

Overview over functionalities

 Individual maintenance of process flows per EDI-exchange partner (Extract of transactions for the maintenance)  Monitor for outbound ASN-status  Own processing logic  Monitor for incoming content acknowledgements of receipt (824)  Own processing logic  Monitor for incoming confirmations of goods receipt (861)  Own processing logic

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

18

Monitor for incoming application advice: Selection

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

19

Monitor for incoming application advice: Selection

In the selection, the following option could chosen:  IDoc number of the ASN  Reference date: Date, which is transmitted in the 824 messege  Outbound delivery number  Customer material number  Several status of the ASN IDocs by traffic lights

Furthermore, there is the possibility to go to all the set up transactions which are relevant for the 824.

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

20

Monitor for incoming application advice: Output list

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

21

Monitor for incoming application advice: Functions

In the output list, the following functions are possible: Go to change an outbound delivery Go to transaction VL09 to cancel the goods issue Post goods issue for an outbound delivery Send out the cancelation message of an ASN Send out the repetition message of an ASN Put an internal completion indicator, e.g. to signal, that a message for errors was completed Reset of the status change (internal completion indicator) Maintain notes

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

22

Overview over functionalities

 Individual maintenance of process flows per EDI-exchange partner (Extract of transactions for the maintenance)  Monitor for outbound ASN-status  Own processing logic  Monitor for incoming content acknowledgements of receipt (824)  Own processing logic  Monitor for incoming confirmations of goods receipt (861)  Own processing logic

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

23

Monitor of Receiving Advice: Selection

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

24

Monitor of Receiving Advice: Selection In the selection, the following option could chosen: 

IDoc number of the receiving advice

 

Goods receipt date Plant

 

Number of the sold-to Customer plant number

 

Supplier number Without Dunning: Return from the customer to the supplier for returnables are possibly notified with the same message, as the messages for goods receipts are transmitted. However, they contain another indicator, which classifies the transferred material number. With the selection of this characteristic, the IDocs for material numbers, which are classified as packing materials, are excluded from the selection.

 

Outbound delivery number Customer material number



Several status of the ASN IDocs by traffic lights

Furthermore, there is the possibility to go to all the set up transactions, which are relevant for the 861. © SAP SE or an SAP affiliate company. All rights reserved.

25

Monitor of Receiving Advice: Output list

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

26

Monitor of Receiving Advice: Functions In the output list, the following functions are possible: Put an internal completion indicator, e.g. for signal, that a message for errors was performed Reset of the status change (internal completion indicator) Maintain notes

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

27

Agenda

1. Benefit for the Customer 2. Description of the Function 3. The Function in the System 4. Technical Information

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

28

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

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

29

Source of Information Internet Overview-, Detail- and Customer presentations 

http://www.sap.com/acs

Email - distribution list Signing up through [email protected] OSS-System Notes (Search term: Automotive Consulting Solutions) © SAP SE or an SAP affiliate company. All rights reserved.

30

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]

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

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

32