首页 > 代码库 > 【MM ECC VS S4】MM模块中ECC与S4的区别

【MM ECC VS S4】MM模块中ECC与S4的区别

原文出自 https://blogs.sap.com/2017/04/28/comparison-of-simplification-and-functionality-in-s4-and-ecc-in-procurement-process/ 

 

Functionality/Element ECC S/4
Material Master
  • Material Number length is 18 characters
  • Service Master is used for Services.
  • Material Number length 040 characters
  • MRP fields – Quota arr. Usage, SLoc MRP indicator, spec. proc. type SLoc , reorder qty and replenishment qty are not required to be switched on.
  • A new Material type ‘SERV” for service material. However, service material type “DIEN’ is also available.
Vendor Master
  • Master data is maintained separately for Vendor and Customer.
  • Only one single address
  • No integrated classification data
  • No time – dependency
  • Supplier evaluation is only on hard facts only and supplier evaluation for soft-facts using questionnaire is not available but only in SAP Supplier Life cycle management.
  • No integration to Dun &Bradstreet Information Services

 

  • Business partner concept is used as a replacement for Vendor and Customer Master.
  • The roles available are “000000” – Business Partner (Gen), “FLVN00” – FI Vendor and “FLVN01” – Supplier.
  • Multiple addresses are possible.
  • Multiple roles
  • Time dependency object attributes and relationships
  • Purchasing Category: Suppliers can be managed according to specific categories of goods and services.
  • Classification: Assign important characteristics to suppliers. A score card for each supplier to monitor supplier’s social responsibility compliance
  • Own questionnaire can be defined directly and evaluation requests can be created and distributed directly to appraisers.
  • Support of Dun &Bradstreet Information Services  data

 

 

Purchase Requisition
  • If no source of supply is assigned automatically by the system, Buyer needs to do this manually.
  • System proposes automatically a set of available sources of supply to facilitate and accelerate assignment of source of supply.
  • Grouping, filtering and downloading capabilities of open purchase requisitions.
Purchase Order processing
  • Search for existing POs is time –consuming, no provisioning of existing documents.
  • No prefilling of other fields based on supplier.
  • No pre-filtering of value help search results.
  • Only at the end get a list of errors that need to be corrected.
  • Dynamic prefilling and provisioning of fields based on selected supplier or material type.
  • Restricted list of available value help fields to avoid subsequent errors in purchase order.
  • Draft purchase order is created automatically when session is lost or retrieved automatically upon returning.
Output Management
  • The output management configuration is based in NAST.
  • The configuration is based on BRF+ (Business Rule Framework Plus) based on Adobe server and Adobe Forms. But NAST configuration is still supported for New documents.

 

Contract Management
  • Only one-time search for contract documents is possible.
  • No action can be done directly in the contract list
  • Approval information is missing
  • Notes are missing
  • All activities can be executed in one screen
  • Contract target value or target quantity update
  • Approval details, notes, business card for supplier are provided
Invoice processing
  • Inflexible search functionalities
  • Confusing visualization of Supplier invoice to detect issues
  • Administrator has to resolve business issues in case of faulty supplier invoice
  • Flexible and dynamic search capabilities
  • Defect issues in one glance
  • Directly resolve issues finish the process
1. 物料主数据
ECC
  • 物料号长度18位
  • 服务使用服务主数据
S/4
  • 物料号长度40位
  • MRP字段 – Quota arr. Usage, SLoc MRP indicator, spec. proc. type SLoc , reorder qty and replenishment qty 不再需要被开启。
  • 新的物料类型SERV用于服务型物料。然而,服务物料类型DIEN依然可用。

 

2. 供应商主数据
ECC
  • 客户和供应商主数据分开维护。
  • 只有一个单独的地址。
  • 没有集成的分类数据。
  • 没有时间相关性。
  • 供应商评估只能基于“硬事实”,而不支持调查问卷等“软事实”方式,软事实方式仅在SAP Supplier Life cycle management中被支持。
  • 不支持到邓白氏信息服务的集成。
S/4
  • 业务伙伴被用于替代供应商和客户主数据。
  • 可用的角色是“000000” – 业务伙伴 (通用), “FLVN00” – FI供应商 和“FLVN01” – 供应商。
  • 支持多个地址。
  • 支持多个角色。
  • 时间相关的对象属性和关系。
  • 采购类别:供应商可以按照采购不同货物或服务的类别进行管理。
  • 分类:分配重要的特征给供应商。用每个供应商一个计分卡的方式来监控供应商的社会责任合规性。
  • 可以自行定义问卷调查,评估请求可以被创建并直接发给评估者。
  • 支持邓白氏信息服务。

 

3. 采购申请
ECC
  • 如果系统没有自动分配货源,采购员需要手工分配。
S/4
  • 系统自动建议一组可用货源,方便和加速货源分配。
  • 未清PR的分组,过滤和下载功能。

 

4. 采购订单处理
ECC
  • 搜索已经存在的PO是很花时间的,无法提前准备已经存在的凭证。
  • 无法用基于供应商的某些字段做提前数据准备。
  • 无法提前对值进行筛选来帮助提升搜索结果。
  • 只在最后得到一个结果,关于哪些错误需要被改正。
S/4
  • 基于选定的供应尚或物料类型的,动态的数据预载入。
  • 支持字段的有效值筛选,避免采购订单中的后续错误。
  • 当连接丢失时,自动保存草稿版的PO,待连接回复后可继续编辑。

 

5. 输出管理
ECC
  • 输出管理的配置是基于NAST。
S/4
  • 配置基于BRF+ (Business Rule Framework Plus) ,和Adobe server和Adobe Forms。但是NAST依然可用。

 

6. 合同管理
ECC
  • 对合同凭证,只可以一次性搜索。
  • 不允许直接在合同清单中进行操作。
  • 缺少审批信息。
  • 缺少注释。
S/4
  • 所有的活动可以在一个屏幕内完成。
  • 合同目标值或目标数量更新。
  • 提供了审批信息,注释,供应商名片。

 

7. 发票处理
ECC
  • 搜索功能不灵活。
  • 供应商发票界面令人困惑,问题发生时,不容易找到。
  • 当错误的供应商发票出现时,系统管理员需要解决业务问题。
S/4
    • 灵活和动态的搜索能力。
    • 一目了然就能找到问题。
    • 直接解决问题,结束流程。

【MM ECC VS S4】MM模块中ECC与S4的区别