SAP S/4 HANA新变化-MM物料管理

Co-Deployment of SAP SRM 集成SRM

The functional scope of SAPSupplier Relationship Management (SAP SRM)will gradually be made available within SAP S/4HANA. The related functions willbecome part of the procurement solution of SAP S/4HANA. In the first release ofSAP S/4HANA, on-premise edition a limited functional scope might be availablecompared to SAP SRM. The coverage will grow over time. Technically, theprocurement solution within SAP S/4HANA is not a successor to the SAP SRMcomponents. Therefore, the SAP SRM software components and SAP S/4HANA cannotbe installed on the same system. Technically, it is not a co-deployment, but inthe future the procurement solution will evolve to take over the SAP SRMfunctions.

Customers with SAP SRM and SAP BusinessSuite on one server need to re-implement the rocurement processes on the SAP S/4HANA, on-premiseedition system which have been used on SAP Business Suite sourcerelease withinthe SAP SRM installation. It is not possible to install the SAP SRM softwarecomponents within the SAP S/4HANA stack. The functional scope of the newprocurement solution available with the first release of SAP S/4HANA is notidentical with the SAP SRM functions.

SAP Note: 2216943

Co-Deployment of SAP Supplier Lifecycle Management (SAP SLC)

The goal is that - over time - thefunctional scope of SAP Supplier Lifecycle Management (SAP SLC) will be availablewithin the SAP S/4HANA stack. Customers who have deployed SAP SupplierLifecycle Management on SAP ERP and want to migrate to S/4HANA can continue touse those parts of the SAP SLC functionality that have been integrated into theS/4HANA Core and are referred to as "Supplier and CategoryManagement". For the functional differences, see simplification itemDedicated SAP Supplier Lifecycle Management (SAP SLC) business processes.Customers who have been using a standalone SAP SLC system can continue to useit, but have to use MDG-S for supplier data integration. For more information,see simplification item Dedicated SAP Supplier Lifecycle Management (SAP SLC)business processes.

The functional scope of Supplier and CategoryManagement in SAP S/4HANA is currently not identical with the SAP SLCfunctionalities.

Master categories in purchasing category are notavailable. As a successor, material groups are available in purchasingcategories.

SAP Note:Implementation 2186288 Description 2187627

Vendor evaluation based on LIS

The current vendor evaluation basedon Logistics Information System (LIS5) is still available with SAPS/4HANA,on-premise edition 1511, but is not considered the target architecture6. We recommend that you use the SAP HANA reporting capabilitiesfor vendor evaluation based on CDS views and smart business technology.

SAP Note: 2228247

Subsequent Settlement - Vendor Rebate Arrangements

In SAP S/4HANA, the Subsequent Settlement(MM-PUR-VM-SET) application is replaced by the new Contract Settlement(LO-GT-CHB) application. For this reason, the functional scope of subsequentsettlement has been restricted, that is, in SAP S/4HANA, it is no longerpossible to:

 Create new rebate arrangements usingtransaction MEB1 or

 Extend existing rebate arrangements usingtransactions MEBV / MEB7 / MEBH

Additionally, as a consequence of thematerial field length extension in the SAP S/4HANA landscape, the structure oftable S111 was adjusted. This can have some impact if the business volume datahas to be rebuilt in the SAP S/4HANA system.

In SAP S/4HANA, Contract Settlement replacesSubsequent Settlement, which means that existing rebate agreements can only beprocessed up until the end of the validity date of the agreement and must thenbe closed by a final settlement. Afterwards new agreements can only be createdbased on condition contracts.

Furthermore, if recompilation of the businessvolume data in SAP S/4HANA, on-premise edition 1511 is required, the indextable S111 has to be rebuilt as described in SAP Note 73214 (Subseq.settl.:

Retrospec.compltn/recompltn of busin.vol.data).

Transaction not available in SAPS/4HANA on-premise edition 1511

MEB1; MEB7; MEBV, MEBH

In SAP S/4HANA there are no direct activitiesrequired for continuing the business process for subsequent settlement, withthe only exception that the agreements have to be closed after the end of thevalidity period.

If a recompilation of the business volume data isrequired, the table S111 has to be rebuilt with the report RMEBEIN3 asdescribed in note 73214

Conversion Pre-Checks SAPNotes: 2194923, 2215220

Related SAP Notes SAP Note: 73214

Output Management Adoption in Purchase Order

With SAP S/4HANA a new Output Management approachis in place. By design, the new output management includes cloud qualities such as extensibility enablement, multi tenancy enablement and modification free configuration. Therefore, the complete configuration differs from the configurationthat is used when output management is based on NAST. The configuration isbased on BRF+ which is accessible for Customers. In SAP S/4HANA, the target architecture is based on Adobe Document Server and Adobe Forms only. For theform determination rules (along with other output parameters) BRF+functionality is used (in this sense in combination with the message determination).

Output management based on NAST is no longer supported for new documents in purchase order.

Purchase orders which are migrated from legacysystems and for which NAST based output has been determined, can be processedwith this technology. For all new purchase orders the new output management isused. Therefore in Procurement for purchase order there is a need to adapt the configurationsettings related to Output Management.

In purchase order it is recommended to use AdobeForms but due to compatibility the form

technologies known from Business Suite (likeSmartForms, SapScript) are supported as well. This is also true for the printreports.

In Purchase order processing it is recommended touse Adobe Forms but due to compatibility the form technologies known fromBusiness Suite (like SmartForms, SapScript) are supported as well.

This is also true for the print reports.

In contrast to the output management based onNAST the new output management supports only the Channels PRINT, EMAIL, XML(for Ariba Network Integration) and IDOC (for on premise). Other channels arenot supported by default.

Additional information to the new outputmanagement in SAP S4/HANA can be found in the general simplification itemrelated to Output Management (Cross Topic Area)

Output Management for Purchase Order has to beconfigured. In cases where there is not customerspecific configuration for thenew output management for purchase orders, it will not be possible to printpurchase orders or to send purchase orders via e-mail or XML.

Availability of Transactions in MM-IM

MB开头的物料移动的tcode不能再用了,只能使用migo

The following transactions for entering anddisplaying goods movements (material documents) - called"MB transactions" (below) are not available with SAP S/4HANA. In SAPS/4HANA the single-screen generalized transaction MIGO is available :

· MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A,MB1B, MB1C, MB31, MBNL, MBRL, MBSF, MBSL, MBST and MBSU 以上TCODE不能使用了

The transactions MMBE_OLD (Stock overview), MMBE(Stock overview), MB51 (Material Document List), MB52

(Display Warehouse Stocks of Material) and MB5B(Stock at posting date) are still available but will be not available midterm. Successor functionalities arealready available as Fiori applications and/or as Virtual Data Model (VDM) to be consumed by SAP Lumira or SAP Design Studio:

· MMBE_OLD: Fiori application Stock – SingleMaterial, VDM view C_MaterialStockActual

· MMBE: Fiori application Stock – Single Material,VDM view C_MaterialStockActual

· MB51: Fiori application Material DocumentsOverview

· MB52: Fiori application Stock – MultipleMaterials, VDM view C_MaterialStockActual

· MB5B: Fiori application Stock – MultipleMaterials, VDM view C_MaterialStockByKeyDate

原文发布于微信公众号 - SAP最佳业务实践(sztunxi)

原文发表时间:2016-12-07

本文参与腾讯云自媒体分享计划,欢迎正在阅读的你也加入,一起分享。

发表于

我来说两句

0 条评论
登录 后参与评论

相关文章

来自专栏开心的学习之路

03 Jme3和Nifty1.4.2中文显示

用JMonkey最大的问题就是中文问题,IDE不是中文没关系,反正可以迁移到Idea里,但是打包发布的项目以及Nifty做的GUI里没有中文就心塞塞了。好在找到...

39010
来自专栏Hongten

My Notepad

I have spent near more two weeks to write this Notepad application. At this mome...

1282
来自专栏CreateAMind

CAT Vehicle Testbed 自动驾驶仿真 gps 视觉 雷达

https://cps-vo.org/group/CATVehicleTestbed/wiki

1313
来自专栏SAP最佳业务实践

SAP S/4 HANA新变化-PP生产计划

1、BOM, Routing, Production Version With SAP S/4HANA, on-premise edition 1511, th...

6515
来自专栏PPV课数据科学社区

【学习】七天搞定SAS(三):基本模块调用

搞定基本的函数之后,开始鼓捣SAS里面的模型。也就是说,要开始写PROC了。说实话,越学SAS,越觉得SAS像Stata...无论是从输出的样式,还是语法。好不...

3405
来自专栏叁金大数据

EmguCV学习——视频与图片互转

其实视频转图片在上篇文章中已经有些眉目了,其实就是按帧读取视频,然后把帧保存就ok。然后自己再加个进度条美化一下。。。这代码简单易懂,还是直接上代码吧。

2581
来自专栏专知

2018年SCI期刊最新影响因子排行,最高244,人工智能TPAMI9.455

2018年6月26日,最新的SCI影响因子正式发布,涵盖1万2千篇期刊。CA-Cancer J Clin 依然拔得头筹,其影响因子今年再创新高,达244.585...

2262
来自专栏腾讯云流计算

Managing Large State in Apache Flink®: An Intro to Incremental Checkpointing

Apache Flink was purpose-built forstatefulstream processing. Let’s quickly revie...

2495
来自专栏SAP最佳业务实践

SAP S/4 HANA新变化-MM-IM物料帐:物料评估

Material Ledger Obligatory for Material Valuation 物料帐强制启用 Description This simpl...

5006
来自专栏智能计算时代

Best Bluemix Content

image.png Watson Services for Bluemix Sample Apps: Watson Films App (Video) Wats...

2854

扫码关注云+社区

领取腾讯云代金券