SAP for Automotive Blogs
Explore blog posts by automotive thought leaders and SAP experts, paving the way for a smoother journey with SAP. Post a blog to share your own expertise.
cancel
Showing results for 
Search instead for 
Did you mean: 
SachinX
Advisor
Advisor
0 Kudos

Further to my previous blog on S/4 HANA Enterprise Management 1511 for Automotive - Simplification List Part 1


Here is the Part 2 list of Simplifications:


1. Long Material Number: Long material number was functionality to extend the material number of 18 Character to be enhanced till 40 Character.


In S/4 HANA materail number is been natively extended to 40 characters, this has been done for all kinds of materials.


Customer with business function MGV_LAMA already activated could not covert at this business functions is now been set to "Always Off"


Refer SAP Note: 2228241


2. Material Version: The material version was fully based on the long material number functionality. When material versioning has been activated, a version could be created against the original material master with version ID's


One reason is to create material versions for documentary reasons like minor changes in drawings etc. Another reason is to use material versions in logistics only in early phases of product development where changes occur often and continue in the mature phases of the lifecycle with the header material only.

iPPE could be maintained just using header materials, so new material versions do not require the maintenance of iPPE objects. During BOM explosion, a

valid material version with active logistics switch is dynamically determined and the header material replaced by its version if found.

The validity for material versions is determined via ECM (Engineering Change Management) which is obligatory for material versions to be used. All other applications do not distinguish between header material and material versions

The automotive specific material version features are not available within SAP S/4HANA.

These transactions are not available in S/4 HANA: MMLS, TCLSVERS, VTCU

Refer SAP Note: 2228242

3. Planning Regular Route Shipment:  In SAP S/4HANA, the automotive industry solution for planning inbound shipments for regular routes based on route schedules is not available.

Inbound deliveries created based on shipping notifications from suppliers could be directly linked as items to the generated inbound shipments. The inbound

shipments could then be used for goods receipt processing collectively for all inbound deliveries shipped together.

With SAP Transportation Management, a new solution for planning, executing and settling shipments is available

Following transactions are not available in S/4 HANA : VL51A, VL52A, VL53A, VL54A

Refer SAP Note: 2227568

4. SAP Automotive Dealer Portal:   The former Dealer Portal for Automotive based on Discrete Industries Web Interface (DIWI) and Business Server Pages is not available within SAP S/4HANA.

From SAP ERP 6.04, a Web Dynpro based dealer portal, which is accessible via SAP Netweaver Business Client, is available. The dealer portal for automotive allows dealers support the vehicle sales, spare parts procurement, and warranty claim processing.

It is recommended to move to the Web Dynpro based Dealer Portal.

Refer SAP Note: 2228244

For any further clarification, please comment.

Regards,

Sachin Balmiki