Beruflich Dokumente
Kultur Dokumente
71
SAP AG 10.09.2003 1
SAP for Automotive, Rel. DIMP 4.71
SAP AG 10.09.2003 2
SAP for Automotive, Rel. DIMP 4.71
...
...
...
SAP AG 10.09.2003 3
SAP for Automotive, Rel. DIMP 4.71
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
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
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.
Effects on Customizing
You make this setting in the shipment type.
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
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.
• 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
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).
SAP AG 10.09.2003 9
SAP for Automotive, Rel. DIMP 4.71
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.
• 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 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.
SAP AG 10.09.2003 11
SAP for Automotive, Rel. DIMP 4.71
Use
From DIMP 4.71, the following enhancements are available for summarized JIT calls:
SAP AG 10.09.2003 12
SAP for Automotive, Rel. DIMP 4.71
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).
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.
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.
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