You are on page 1of 18

SAP for Automotive, Rel. DIMP 4.

71

SAP for Automotive


Release DIMP 4.71

SAP AG 10.09.2003 1
SAP for Automotive, Rel. DIMP 4.71

SAP - Copyrights and Trademarks


© Copyright 2003 SAP AG. 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 AG. The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered
trademarks of Microsoft Corporation.
IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®,
OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,
Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in
USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,
MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world. All other product and service names
mentioned are the trademarks of their respective companies.

SAP AG 10.09.2003 2
SAP for Automotive, Rel. DIMP 4.71

...
...
...

1 Structural Changes to the Implementation Guide for DIMP 4.71(New)........................................... 4


2 IS-A-GR Goods Receipt Process .................................................................................................... 6
2.1 Set Up Return Delivery with Delivery via Shipping (LE-SHP) in Quantity Difference Profile
(New) 6
2.2 Creation of Shipments with Incomplete Inbound Delivery Data (New) .................................... 7
2.3 Enhancements in the Goods Receipt Dialog (Enhanced) ........................................................ 7
2.4 Performance Improvements in the GR Dialog (Changed)........................................................ 8
2.5 Enhancements to the Registration of Inbound Deliveries (Enhanced)..................................... 8
2.6 Improvements to the Usability of the Automotive GR Dialog (Enhanced)................................ 9
3 IS-A-HUM Handling Unit Management.......................................................................................... 10
3.1 IS-A-HUM-PSP Packing and Shipping Planning.................................................................... 10
4 IS-A-JIT Just-In-Time Processing.................................................................................................. 10
4.1 JIT Inbound (Enhanced) ......................................................................................................... 10
4.2 JIT Outbound (Enhanced) ...................................................................................................... 11
4.3 4.3 IS-A-JIT-SUM Summarized JIT call.................................................................................. 12
4.3.1 Summarized JIT Calls (Enhanced).................................................................................. 12
5 IS-A-PPC Production Backflush .................................................................................................... 13
5.1 Production Backflush (Enhanced) .......................................................................................... 13
6 IS-A-SBO Outbound Self-Billing Procedure................................................................................... 13
6.1 Generate a List of Invoices and Credit Memos (New)............................................................ 13
7 IS-A-SCH Enhancements to Scheduling Agreements................................................................... 14
7.1 IS-A-SCH-EMM Enhancements to scheduling agreements MM (Outbound) ........................ 14
7.1.1 Set Up Return Delivery with Delivery via Shipping (LE-SHP) in Quantity Difference
Profile (New) .................................................................................................................................. 14
8 IS-A-S2L Production Supply .......................................................................................................... 15
8.1 Automatic Supply-to-Production (Enhanced) ......................................................................... 15
9 IS-A-VMS Vehicle Management System ....................................................................................... 16
9.1...................................................................................................................................................... 16
10 IS-A-WTY Warranty Processing................................................................................................. 16
10.1 Warranty Processing (New) ................................................................................................ 16

SAP AG 10.09.2003 3
SAP for Automotive, Rel. DIMP 4.71

1 Structural Changes to the Implementation Guide


for DIMP 4.71(New)
Use
Aerospace & Defense
• New IMG Nodes:
{ Plant Maintenance and Customer Service -> System Enhancements and Data Transfer -
> Business Add-Ins -> Maintenance and Service Planning (MSP)
{ Plant Maintenance and Customer Service -> Maintenance and Service Processing ->
Configuration Control -> Maintain General Settings for Installation/Removal
{ Configuration Control -> Business Add-Ins -> Configuration Control Workbench:
ƒ Perform Quantity Check
ƒ Define Customer-specific Within Overall Configuration Check
ƒ Adjust Message Type According to Configuration Check Types
ƒ Create Multiple Configuration Check Logs
{ Plant Maintenance and Customer Service -> Maintenance and Service Processing ->
Logbook -> Business Add-Ins -> Component List

Automotive
• New IMG Nodes:
{ Logistics Execution -> JIT Inbound -> Business Add-Ins (BAdIs)
{ Logistics Execution -> JIT Outbound -> Business Add-Ins (BAdIs)
{ Logistics Execution -> JIT Outbound -> Summarized JIT Call -> Business Add-Ins
(BAdIs) Automatic Supply-to-Production
{ Logistics Execution -> JIT Inbound -> Define Message Types
{ Production -> Repetitive Manufacturing -> Production Backflush > Business Add-Ins
(BAdIs)
{ Production -> Kanban -> Business Add-Ins Kanban
{ Materials Management -> Logistics Invoice Verification -> Revaluation -> Configure
Parallel Processing
{ Materials Management -> Logistics Invoice Verification -> Revaluation -> BAdI for
Revaluation with Collective Processing
{ Plant Maintenance and Customer Service -> Maintenance and Service Processing ->
Warranty Claim Processing
{ Logistics Execution -> Vehicle Management System (VMS) -> Business Add-Ins (BAdIs)
{ Logistics Execution -> Vehicle Management System (VMS) -> Vehicle Search -> Define
Fields for TREX Download
{ Logistics Execution -> Vehicle Management System (VMS) -> Vehicle Search -> Define
Search Views
{ Logistics Execution -> Goods Receipt Automotive -> Business Add-Ins -> BAdI:
Registration
{ iPPE Customizing is now also available under cross-application components
{ Integrated Product and Process Engineering -> General Settings -> Enhanced
Dependency Editor:

SAP AG 10.09.2003 4
SAP for Automotive, Rel. DIMP 4.71

ƒ Activate Enhanced Dependency Editor


ƒ Create Scheme for Enhanced Dependency Editor
ƒ Assign Scheme
{ Integrated Product and Process Engineering -> General Settings:
ƒ Define Settings for Access Object
{ Integrated Product and Process Engineering -> iPPE Product Structure Administration
ƒ Extract: Activate and Define Settings

• Moved IMG Nodes:


{ User Assignment: iPPE-Workbench is no longer in the SAP Reference IMG but in the
SAPEasy Access Menu under Logistics -> Production -> Master Data -> Integrated
Product and Process Engineering.

• Deleted IMG Nodes:


{ Logistics Execution -> Vehicle Management System (VMS) -> Enhancements ->
Program Actions

Engineering & Construction


• New IMG Nodes:
{ Sales and Distribution -> Bill of Services -> Service Entry Sheet
{ Sales and Distribution -> Bill of Services -> Service Entry Sheet -> Business Add-Ins
High Tech

• New IMG Nodes:


{ Production Planning for Process Industries -> IS-HT-MES (Manufacturing Execution
System) -> Serial Number -> Set Serial Number Profile
{ Production Planning for Process Industries -> IS-HT-MES (Manufacturing Execution
System) -> Batch Traceability -> Activate Documentation of Goods Movement ->
Activate Documentation of Goods Movement for Process Orders
{ Production Planning for Process Industries -> IS-HT-MES (Manufacturing Execution
System) -> Batch Traceability -> Activate Documentation of Goods Movement ->
Activate Documentation of Goods Movement for Production Orders
{ Production Planning for Process Industries -> IS-HT-MES (Manufacturing Execution
System) -> Batch Traceability -> Batch Genealogy Report Configuration Mill Products

• New IMG Nodes:


{ Logistics - General -> Reel Calculation
{ Logistics - General -> NF Metal Processing
{ Logistics - General -> Basic Setting for mySAP Mill Products -> Define Characterisitcs
for Length-Based Materials
{ Logistics - General -> Batch Management -> Weight Determination
{ Sales and Distribution -> Basic Functions -> Availability Check and Transfer of
Requirements -> Availability Check -> Rule-based Availability Check -> Copying of
Characteristic Values for Sub-Items
{ Sales and Distribution -> Sales -> Return. Packaging Processing

SAP AG 10.09.2003 5
SAP for Automotive, Rel. DIMP 4.71

{ Sales and Distribution -> Sales -> Sales Documents -> Fast Data Entry of
Characteristics in Sales Documents
{ Materials Management -> Purchasing -> Purchase Order -> Fast Entry of Characteristics
in Purchase Order
{ Materials Management -> Inventory Management and Physical Inventory -> Settings for
Enjoy Transactions -> Settings for Goods Movements (MIGO) -> Fast Entry of
Characteristics in Goods Movements
{ Materials Management -> Inventory Management and Physical Inventory -> Goods
Issue/Transfer Postings -> Set Cutting Processing and Delivery-Related Trading Unit
Change
{ Logistics Execution -> Shipping -> Deliveries -> Delivery-Related Trading Unit Change
(DTUC)
{ Logistics Execution -> Shipping -> Deliveries -> Weight Determination
{ Production -> Shop Floor Control -> Master Data -> Order -> Fast Entry of
Characteristics in Production Order
{ Production -> Shop Floor Control-> Operations -> Confirmation -> Fast Entry of
Characteristics in the Confirmation

• Moved IMG Nodes:


In Release DIMP 4.71 the industry-specific IMG activities for mySAP Mill Products have been
moved into other areas of the Implementation Guide. For more information see Structural
Changes to the IMG for mySAP Mill Products (New).

2 IS-A-GR Goods Receipt Process


2.1 Set Up Return Delivery with Delivery via Shipping (LE-
SHP) in Quantity Difference Profile (New)
Use
Previously, in the case of return deliveries in connection with Automotive goods receipts a material
document was generated, which was displayed in the PO history for the scheduling agreement
(among other places).
In addition, you were able to specify via confirmation control or the assigned quantity difference
profile whether or not the associated inbound delivery was to be MRP-relevant again on the basis
of the returned quantity.
In other words, you could specify whether you were expecting substitute deliveries for an inbound
delivery.This function remains available.

As of SAP DIMP 4.71, you can generate an outbound delivery in Shipping (LE-SHP) when posting
a return delivery in the Automotive goods receipt function.
This enables you to use the functions of Shipping (e.g. picking and packing) for the return delivery
and thus have shipping documents and delivery notes at your disposal. This also applies to items
with summarized JIT calls , handling units, and the use of Warehouse Management (WM). You
specify whether an outbound delivery is created in the background during the process of return
delivery in the quantity difference profile, which you assign to the confirmation key and thus the
scheduling agreement item.

If you use outbound deliveries, the inbound delivery to which the return delivery relates always
counts as closed. This is predefined in the quantity difference profile and cannot be changed. The
delivery quantity is not reduced by the returned quantity, so that the delivery quantity can be taken
into account in determining freight costs for instance.

SAP AG 10.09.2003 6
SAP for Automotive, Rel. DIMP 4.71

If you create a return delivery with outbound delivery via Shipping, the system creates an outbound
delivery instead of the material document. This displayed in the PO history or confirmation overview
together with the associated inbound delivery. In the confirmation overview, the external document
of the outbound delivery indicates the associated inbound delivery.
Inbound and outbound deliveries are offset in terms of MRP following goods receipt and goods
issue.

Note
If you create a return delivery without outbound delivery - as hitherto - you can specify in
the quantity difference profile whether or not the inbound delivery is to be closed. In the
case of a return delivery with outbound delivery, the inbound delivery is always closed.

See also
For more information, refer to the SAP Library under mySAP Automotive -> MM Scheduling
Agreement Enhancements.

2.2 Creation of Shipments with Incomplete Inbound


Delivery Data (New)
Use
From release 4.71 you can create a inbound shipment, regardless of whether the inbound delivery
data exist in system or not. The inbound delivery is automatically linked with the shipment as soon
as the shipping notification is received.
Such shipments can be processed directly in the Goods Receipt Automotive Dialog.

Effects on Customizing
You make this setting in the shipment type.

2.3 Enhancements in the Goods Receipt Dialog


(Enhanced)

Use
From release 4.71, the following functional enhancements have been made to the GR dialog:
• Display of the Original Supplier when the Supplier for Summerized JIT Calls is Different
Using this function, the goods receipt employee can see from the inbound delivery that the
supplier (manufacturer) is not the one that was specified. This will be displayed in the overview
of the summerized JIT calls at an inbound delivery item.
• Maintenance of Partner Rolls
Until now, the maintenance of partner rolls (for subsequent processes and by-processes) was
only possible after switching to the standard dialog. You can now do this directly in the GR
Dialog at inbound delivery header level.
• Printing of Goods Receipt Slips
You can trigger the printing of GR slips at item level and specify how many GR slips should be
printed.

SAP AG 10.09.2003 7
SAP for Automotive, Rel. DIMP 4.71

2.4 Performance Improvements in the GR Dialog


(Changed)
Use
In release 4.71, performance improvements have been made to specific functions:
• Conversion of the Posting
When registering and processing the goods receipt at the activities (activities that, in general,
do not require a subsequent activity and which have the corresponding indicator in
Customizing), the system no longer waits for the processing to be completed. The wait time is
therefore shortened when waiting for these activities. The object posted is left and has to be
selected again for further actions.
• Compile Worklist from New
As the system does not wait for the complete processing to be completed, it is possible that
objects are displayed in the tree structure, that do not correspond to the selection criteria. In
this case, a corresponding message is displayed by the system. The object is removed from the
display, and the data is updated after refreshing.

Effects on Existing Data


The posting takes place in the background. You do not have to wait for for the processes to be
completed before you continue working.

Effects on Customizing
In Customizing for the function profile for the Goods Receipt Automotive, you can set whether the
system should wait for the posting to be completed or not.

2.5 Enhancements to the Registration of Inbound


Deliveries (Enhanced)
Use
From release 4.71, the registration of goods receipts will be enhanced with the following
functions:

• Automatic posting of the goods receipt (when registering manually), without the employee in the
goods receipt office having to make a manual decision.
• Accessing a Special BAdI after Registering Inbound Deliveries
This can be used to evaluate missing part information during the registration.
• New Indicator in the Scheduling Agreement Item
There is a new indicator in the scheduling agreement item "Info when Registering", that is
evaluated in the above BAdI and can be used for other actions depending on the scheduling
agreement item (for example, for informing the MRP planner when registering an inbound
delivery for this scheduling agreement item).

Effects on Customizing

• Automatic Posting of the Goods Receipt:

SAP AG 10.09.2003 8
SAP for Automotive, Rel. DIMP 4.71

In order to use these functions, you must set the indicator in Customizing for the confirmation
control key to "Automatic GR when Registering Manually". (Customzing -> Logistics Execution -
> Goods Receipt Automotive -> Confirmations -> Set Up Confirmation Control).

Set up Confirmation Control

2.6 Improvements to the Usability of the Automotive GR


Dialog (Enhanced)
Use
In release 4.71, the following improvements have been made to the usability:
• Save Function for Search Parameters
Entries made in the search dialog box for the detail search are now saved when executing the
dialog. You can still saved save your search settings as a variant, when you are not accessing
the dialog.
• Dialog Box - Quantity Cancellation
When working with goods receipt based invoice verification, you can split the quantity to be
cancelled between the posted material documents, as it is only possible to post with reference
to a material document.
• Dialog Box - Document Cancellation
In addition to the material document, the objects that are posted with the material document are
also displayed. The cancellation is still done at material document level.
• Search Function in the Quantity Difference Dialog Boxes
As the inbound deliveries can often be complicated, that is many items handling units and/or
summerized JIT calls can be assigned, a search function is now available. You can choose
whether you want to search according to particular objects (HUs, SeqJCs), or according to a
text, and whether you want to search in all rows, or either in HU rows or SumJC rows only. The
subordinated object, which is contained within your selection, is designated for the posting.
• Expand All (Tree Structure)
You can expand the corresponding subtree for all nodes of the tree.
• Save Function for the Layout of the PO Determination
In the dialog box for the possible purchase orders from the PO determination, the
corresponding toolbar is now displayed, so that you can save your (personal) layout.
• Enhanced Search for Assignment of Summerized JIT Calls
In the summerized JIT call view for an inbound delivery item, you can now select several
summerized JIT calls from the input help simultaneously and therefore carry out the
assignments quicker.
• Tree Remains Expanded After Updating
To avoid you losing your focus, the tree structure remains expanded after you refresh the
screen (providing that the affected objects still exist in your worklist).
• Copy Function for Users in the User Assignment Profiles
When assigning users to groups for the Automotive Goods Receipt Dialog you can display all
groups for a particular user. Within this display it is possible to copy the user, and to therefore
assign all their groups to a new user.

SAP AG 10.09.2003 9
SAP for Automotive, Rel. DIMP 4.71

3 IS-A-HUM Handling Unit Management


3.1 IS-A-HUM-PSP Packing and Shipping Planning
3.1.1.1 Handling Unit Management (enhanced)

Use
As of DIMP 4.71 you can directly assign HUs to a shipment. The following cases are possible:
• If the delivery contained in the shipment matches the HUs that are to be assigned, the system
updates the delivery and increases the delivery item (transaction Selection of Handling Units
(HUMO) or RF transaction HUVTRF).
• If the delivery contained in the shipment does not match the HUs that are to be assigned, the
system creates a new delivery and increases the delivery quantity (transaction Selection of
Handling Units (HUMO) or RF transaction HUVTRF).
Due to the changes mentioned above, the function Assign HUs in the transaction Outbound
Delivery of Handling Units (VL10HU) has also been enhanced. You can now increase the
quantities of deliveries and create new delivery items/deliveries in this transaction.

4 IS-A-JIT Just-In-Time Processing


4.1 JIT Inbound (Enhanced)
Use
As of DIMP 4.71 the following enhancements are available in JIT processing:

• Process Enhancement for External Agents


JIT processing now also supports processes that distinguish between plants which concentrate
on production and plants which specialize in picking. For example, suppliers who implement the
mySAP Automotive solution can now create deliveries for a plant that specializes in picking or
for an external agent to whom JIT calls are forwarded.

• Action Log
In more complex processes it can be useful to monitor the history of a JIT call. With the new
action log (Transaction JITLOG) you have an overview of individual actions and their results for
each JIT call. A log entry, containing data such as user name, action, time of execution and
previous internal status, is created for each action In addition, the system saves a log with
actions which were not carried out successfully, allowing you to recognize critical situations in
good time.

• SAP Smart Forms


All three JIT forms (component list, pick list and swap list ) are now also available as SAP
Smart Forms . Using SAP Smart Forms you can efficiently create and process forms. Thanks to
a graphical user interface you can adapt SAP Smart Forms without programming knowledge.
• IDoc Monitor for Incoming JIT Calls
You can now also use an IDoc Monitor for incoming JIT calls. You can use this monitor to keep
track of the processing of incoming IDocs. This gives you an overview of the processing of all
current and previous JIT calls, allowing you to easily identify and process IDocs containing
errors.

SAP AG 10.09.2003 10
SAP for Automotive, Rel. DIMP 4.71

• Additional Enhancements:
{ Status Update on Goods Issue Posting
It is now possible to update the status of a JIT call when you post or cancel goods issue
in the SAP R/3 transactions.
{ Enhanced Shipment Scheduling
You can now schedule deliveries based on factory calendars or shift sequences. JIT
calls can now also be scheduled according to their components group type. You can
also take your JIT customer's factory calendar as the basis for the shipment scheduling.
In this way you can schedule JIT calls according to a status time, because some
customers do not send a requirements time. It can be useful to use this function if, for
example, you have JIT customers who work in a different time zone.
{ Additional Data on Destination or Components Group Type Level
It is now possible to save additional data for every destination or every components
group type. In this way you can define additional characteristics for assembly locations.
• Business Add-Ins (BAdIs) for JIT Inbound
The following BAdIs are available in the implementation guide:
{ Process Delivery Confirmations
{ Enhance JIT Monitoring
{ Assign Internal Number Ranges for JIT Basic Data
For more information see the documentation on the individual BAdIs.

4.2 JIT Outbound (Enhanced)


Use
As of DIMP 4.71 the following enhancements are available in JIT Processing Outbound:

• Manually Create and Change JIT Calls Outbound


You can use this new functionality to manually create and change JIT calls outbound. This can
be useful if you have to carry out emergency correction in critical situations.
• Bar Code Transactions for JIT Outbound
As in the bar code transactions in JIT Inbound, you can now use a bar code scanner to execute
an action for a JIT call outbound. With bar code scanners you can carry out actions for one or
more JIT calls cost-efficiently. Before an action is carried out the scanned JIT calls are loaded
into a work buffer. The action is carried out when the JIT calls are saved.
• Additional Enhancements
{ Scheduling for JIT Calls Outbound
You can now also schedule a JIT call outbound with a control cycle. In the control cycle
you define a time buffer which is then added when the JIT call is scheduled.
{ Delivery Confirmation Number per Supplier
For delivery confirmation numbers, SAP now offers you a number range per supplier.
You can assign a number range to each supplier. This makes it easier for your suppliers
to check whether all their delivery confirmations have arrived.
• Business Add-Ins (BAdIs) for JIT Outbound
The following BAdIs are available in the implementation guide:
{ Define Customer-specific Actions

SAP AG 10.09.2003 11
SAP for Automotive, Rel. DIMP 4.71

{ Adjust Data on Creation of an Outbound JIT Call


{ Adjust Delivery Confirmations Outbound
{ Adjust IDoc Data
{ Adjust Layout of Reports and Lists
For more information see the documentation on the individual BAdIs.

4.3 4.3 IS-A-JIT-SUM Summarized JIT call


4.3.1 Summarized JIT Calls (Enhanced)

Use
From DIMP 4.71, the following enhancements are available for summarized JIT calls:

• Enhancements for Summarized JIT Calls for Materials Managed in Batches


Until now, you could create characteristic valuations for materials managed in batches which
were procured using summarized JIT calls. The following functions have been enhanced:
{ The characteristic values for summarized JIT calls are displayed in the following
transactions:
PK23 (create summarized JIT calls)
PJ02 (change summarized JIT calls)
PJ03 (display summarized JIT calls)
JITOM (JIT monitoring for outbound calls)
JITOG (outbound JIT cockpit)
{ The characteristic values are archived if the summarized JIT calls are archived.
• Cross-Plant Stock Transfer
It is now possible to transfer stock from plant to plant for all stock transfer replenishment
strategies. In the implementation guide under Define Stock Transfer Strategies, you define that
stock is to be transferred from plant to plant. If you work with cross-plant stock transfer, you
also have to define an issuing plant when creating the control cycle.
• Changing the Control Cycle Category
You can change the category of a control cycle from manual to automatic, for example. Until
now, you first had to delete a control cycle and then create a new one with your chosen
category.
• Stock Correction: Last Goods Receipt
In production, a situation may arise where certain goods receipts have been posted in the
system but where the materials have not yet physically arrived at the supply area. It is also
possible that the materials have physically arrived at the supply area but the goods receipt has
not yet been posted in the system.
To find out whether such a situation exists, the summarized JIT call for which the last goods
receipt was posted is displayed in the stock correction transaction. This means an overview is
always available of which materials can still be expected at the supply area so that you can
take this information into account during stock correction.

SAP AG 10.09.2003 12
SAP for Automotive, Rel. DIMP 4.71

5 IS-A-PPC Production Backflush


5.1 Production Backflush (Enhanced)
Use
In release DIMP 4.71 the production backflush will be enhanced with the following functions:
• Cancel "with reference"
Using this new function you can cancel a backflush with reference to an existing one. This new
function is particularly useful if the original backflush for a component or assembly was created
with a variance. The function enables you to cancel all goods movements and activities
generated for that backflush.
• Resetting the status of a planned order
Previously, planned orders could not be changed once they had been partially backflushed.
Even if all the backflushed quantities had been reset, the status of the planned order remained
partially backflushed.
If you backflush the quantity zero at a reporting point, the status is cancelled at activity level,
but the status of the planned order remains partially backflushed. If you reset all backflushes for
a planned order and backflush quantities of zero, the overall status of the planned order is reset
to initial because of the new functionality. That is, the status is reset both at planned order level
and at activity level.
• Components for sales order stock without stock value segements
If a production backflush contains several components and/or activities that have to be
processed, the Work in Process (WIP) for the components and assemblies must also be
updated during processing, and the goods movements must be executed. Previously, the
backflush could not be executed for components/assemblies, if a component has requirements
for sales order stock, and no goods receipt has been posted.
From this release, the processing will no longer be stopped and such components/assemblies
will be saved for postprocessing (Transaction COGI), even if no stock value segments exist.
• iPPE master data
The production backflush supports product interchangeability, phantom assemblies, and by-
products in iPPE master data. For further information, see the release information for these
topics.
• Business Add-In (BAdIs) for the production backflush
You find the following Business Add-Ins in Customizing under Business Add-Ins :
{ Provision of backflush data in DB table form
{ Distribution of postprocessing records in other systems
For further information, see the documentation for the BAdIs.

6 IS-A-SBO Outbound Self-Billing Procedure


6.1 Generate a List of Invoices and Credit Memos (New)
Use
As of SAP DIMP 4.71 you can generate a list of the invoices and credit memos that you have sent
by EDI to your vendor (supplier).
You can also generate a list more than once or overwrite it, that is generate it using new selection
criteria. When you generate the list a spool request is created, which you can then output. A new

SAP AG 10.09.2003 13
SAP for Automotive, Rel. DIMP 4.71

page is created for each vendor. Message determination and output cannot be used in
conjunction with the list.

The Smart Form ISAUTO_ERS_OVERVIEW is used to select and output data. You can adjust
the list to your own requirements by copying the Smart Form to the customer name space and, for
example, adding additional data.

This list can only be generated for vendors with whom you have agreed to use evaluated receipt
settlement (ERS).

Choose Materials Management -> Logistics Invoice Verification -> Automatic Settlement ->
Generate Collective Settlement List (EDI Only).

See also
For more information see the SAP Library for the components Logistics Invoice Verification
(MM-IV-LIV) under Revaluation and mySAP Technology Components under SAP Web
Application Server -> Basis Services / Communication Interface (BC-SRV) -> SAP Smart Forms
(BC-SRV-SSF).

7 IS-A-SCH Enhancements to Scheduling


Agreements
7.1 IS-A-SCH-EMM Enhancements to scheduling
agreements MM (Outbound)
7.1.1 Set Up Return Delivery with Delivery via Shipping (LE-SHP) in
Quantity Difference Profile (New)
Use
Previously, in the case of return deliveries in connection with Automotive goods receipts a material
document was generated, which was displayed in the PO history for the scheduling agreement
(among other places).
In addition, you were able to specify via confirmation control or the assigned quantity difference
profile whether or not the associated inbound delivery was to be MRP-relevant again on the basis
of the returned quantity.
In other words, you could specify whether you were expecting substitute deliveries for an inbound
delivery.
This function remains available.

As of SAP DIMP 4.71, you can generate an outbound delivery in Shipping (LE-SHP) when posting
a return delivery in the Automotive goods receipt function.
This enables you to use the functions of Shipping (e.g. picking and packing) for the return delivery
and thus have shipping documents and delivery notes at your disposal. This also applies to items
with summarized JIT calls , handling units, and the use of Warehouse Management (WM).

You specify whether an outbound delivery is created in the background during the process of return
delivery in the quantity difference profile, which you assign to the confirmation key and thus the
scheduling agreement item.
If you use outbound deliveries, the inbound delivery to which the return delivery relates always
counts as closed. This is predefined in the quantity difference profile and cannot be changed. The
delivery quantity is not reduced by the returned quantity, so that the delivery quantity can be taken
into account in determining freight costs for instance.

If you create a return delivery with outbound delivery via Shipping, the system creates an outbound
delivery instead of the material document. This displayed in the PO history or confirmation overview

SAP AG 10.09.2003 14
SAP for Automotive, Rel. DIMP 4.71

together with the associated inbound delivery. In the confirmation overview, the external document
of the outbound delivery indicates the associated inbound delivery.
Inbound and outbound deliveries are offset in terms of MRP following goods receipt and goods
issue.
Note
If you create a return delivery without outbound delivery - as hitherto - you can specify
in the quantity difference profile whether or not the inbound delivery is to be closed. In
the case of a return delivery with outbound delivery, the inbound delivery is always
closed.
See also

For more information, refer to the SAP Library under mySAP Automotive -> MM Scheduling
Agreement Enhancements.

8 IS-A-S2L Production Supply


8.1 Automatic Supply-to-Production (Enhanced)
Use
From DIMP 4.71, the following enhancements to automatic supply-to-production are available:
• Automatic Supply-to-Production with R/3 Requirements
Until now, you could only work with requirements from SAP APO for automatic supply-to-
production. Without SAP APO, you could only calculate the replenishment using the minimum
stock level (consumption-based material staging).
With this enhancement, you can now also work with requirements from the SAP R/3 System
(dependent requirements, manual reservations, dependent reservations and summarized JIT
calls created by production orders) in the automatic supply-to-production function. Note that
sales order stocks and project stocks cannot be processed.
You can define per material whether you want to work with APO requirements or with R/3
requirements. To work with both APO and R/3 requirements simultaneously, SAP provides you
with the Business Add-In S2L_PSEG_CTR_FACTORY.
• Deleting All Replenishment Proposals for a Supply Segment
Until now, you could only delete replenishment proposals individually. Now it is possible to
select a supply segment and delete all the replenishment proposals (also firmed ones) for this
segment.
• Grouping Planning Elements
The number of planning elements within a planning horizon can be very large meaning that the
supply-to-production table may not be very clear. Therefore, you can group planning elements
that lie in a sequence and that are of the same type (such as dependent requirements or
summarized JIT calls). The individual quantities of the planning elements are added in this
process.
The planning element created by the grouping only exists on the interface and has no effect on
the missing quantities calculation which is still based on the individual planning elements.
Grouped replenishment elements are displayed with the date of the latest element included in
the grouping. Grouped requirements are displayed with the date of the earliest requirement
included in the grouping.
• Creating Replenishment Proposals for Control Cycles of the Category: Manual
Summarized JIT Call

SAP AG 10.09.2003 15
SAP for Automotive, Rel. DIMP 4.71

Until now, in the supply-to-production table, you were only able to display the current situation
for supply segments based on the control cycle category manual summarized JIT call. With this
enhancement, you can now also create summarized JIT calls manually in the supply-to-
production table.
Note that any supply segments based on the control cycle category manual summarized JIT
call are not taken into account in the automatic planning.
Note that batches are not supported in the supply-to-production table.
• Overwriting the Planning Horizon
The planning horizon defines the period in which missing quantities are calculated for
requirements-based supply-to-production. Until now, you define the planning horizon in the
control cycle as a relative period of time. The end of the planning horizon is calculated on the
basis of the shift program and a factory calendar in R/3.
With this enhancement, you can maintain a planning horizon in the supply-to-production table
(or when starting the transaction) that overwrites the planning horizon of all or individual
requirements-based control cycles. If you also use this planning horizon for consumption-based
supply segments, these segments are treated as requirements-based supply segments.
You can also reset these settings so that the calculation is again made on the basis of the
planning horizon saved in the control cycle.
• Product Interchangeability and Phantom Assemblies
The automatic supply-to-production supports product interchangeability and also phantom
assemblies in SAP APO. For more information on this topic, please refer to the corresponding
Release Information.
• Business Add-Ins (BAdIs) for the Automatic Supply-to-Production
The following BAdIs are available in the Implementation Guide:
{ Extending Output Structure for Supply Segments (already available in DI 4.6C2)
{ Extending Outut Structure for Planning Elements (already available in DI 4.6C2)
{ Grouping Planning Elements
{ Defining User-Specific Logic for Missing Quantities Calculation
{ Defining User-Specific Logic for Replenishment Proposal Creation
{ Defining Planning Control for Supply Segments
For more information, please refer to the documentation on the individual BAdIs.

9 IS-A-VMS Vehicle Management System


9.1
10 IS-A-WTY Warranty Processing
10.1 Warranty Processing (New)
Use
The component Warranty Processing is a new component aimed at the needs of manufacturers
and importers of complex products and at their suppliers.
This component enables you to process a large number of warranty claims conveniently and, as far
as possible, automatically. Only the claims for which the results of the automatic checks are

SAP AG 10.09.2003 16
SAP for Automotive, Rel. DIMP 4.71

negative become candidates for manual processing. You also have complete flexibility as regards
the warranty conditions that you define.
Warranty Processing is completely integrated in the SAP solution from master data management
(CS, PM) and pricing (SD) through the checking of master warranties and creating measurement
documents (CS, PM) to the posting of financial accounting documents (FI/CO) and the evaluation
of warranty data (SAP BW).

Possible warranty objects are equipment, functional locations, installed bases, objects with a
material and serial number. Vehicles in the Vehicle Management System (VMS) can also be
handled as warranty objects in connection with the component SAP Discrete Industries.

Delivered Functions
• Master data management.
• Interface for communicating with the claimant and the reimburser.
• One screen transaction for creating, changing and displaying warranty claims with the option of
displaying the available subscreens on tab pages according to you customer-specific needs.
• Check routines for the automatic processing of warranty claims. These routines can also be
defined to meet your own specific requirements.
• Numerous actions that cover all the most common transactions and processes in warranty
processing.
• Automatic pricing, message determination and revenue account determination
• Checking of master warranties and creating measurement documents for a warranty object.
• Postings in financial accounting.
• Online reporting and reporting in the SAP Business Information Warehouse (SAP BW).
• Mass processing of warranty claims.
• Archiving of completed warranty claims.
• Numerous business add-ins (BAdIs) for implementing your own logic and using your own data.
Supported Processes
• Warranty processing - standard case (postcrediting)
The claimant transfers a warranty claim to the person responsible for processig the claim via
IDoc, the dealer portal or a web interface. Flexible checks automatically check whether the data
is complete and consistent. Price determination functions automatically determine the prices if
they have not been set externally. The system uses the measurement data to determine
whether the claim is accepted or rejected. Claims that are accepted are forwarded
automatically to the reimburser, rejected claims are transferred to manual processing. Claims
accepted by the reimburser are then automatically returned to the claimant as accepted and the
accounting documents for the claim are created. In the optimal case, this process takes place
completely automatically.
Precrediting is also possible. In this case, the claimant receives a credit memo immediately
although the claim is not forwarded to the reimburser until later.
• Warranty processing with authorized goodwill
The person responsible for processing the claim gives the claimant the authorization to demand
a warranty for the object although, according to the master warranty, no warranty actually
exists. In other words, the claimant is entitled to an act of goodwill. The system then checks this
authorization automatically.
• Warranty processing with parts to be returned
The claimant transfers a warranty claim which includes a part that has been defined as "to be
returned" in the system of the person processing the claim. The claimant is informed of his/her
duty to return this specific part. The automatic processing procedure keeps track of the time

SAP AG 10.09.2003 17
SAP for Automotive, Rel. DIMP 4.71

limit and deadlines that have been defined for returning parts and checks, iat regular intervals,
whether the required part has been sent in.
• Warranty processing with claim split
A claim split is required if there is more than one reimburser for the items in a warranty claim
version. In this case, the system automatically splits the inbound version from the claimant into
several outbound versions to the different reimbursers and then later combines the inbound
versions from the different reimbursers to form one outbound version to the claimant.
• Warranty porcessing for recalls
During a recall campaign, products that have already been sold are recalled, either publicly or
otherwise, to production so that technical errors that have been declared as intolerable can be
corrected. The cost of the removal of the defects is borne by the reimburser or the claim
processor, even if the warranty conditions are no longer fulfilled. The reimburser transfers an
external recall number with the appropriate data (period of time in which the recall applies,
objects affected including parts and labor values that occur for the recall) to the claim processor
and the latter creates the appropriate recall in the system. Inbound warranty claims for this
recall are then checked against the data stored in the system.

SAP AG 10.09.2003 18