EHP4 ECC 6.0 VS SRM 700 - Business Function activation list

[former_member183819]

What are the business functions available like

business function "Procurement-SRM Integration - LOG_MM_P2PSE_1

I know in ECC spro node these functions are available. can some one share the list of Business function in EHP4?

Procure-to-pay: Support of integrated scenarios for sourcing, contract usage, and service

procurement

􀂄 Procure-to-pay: Down-payment creation, clearing, and retentions integrated with logistics

processes

􀂄 Manage serialized materials and components in your procurement process

􀂄 Procure-to-Pay: Multiple account assignment

􀂄 Beverage empties management in purchasingProcure-to-pay: Support of integrated scenarios for sourcing, contract usage, and service

procurement

􀂄 Procure-to-pay: Down-payment creation, clearing, and retentions integrated with logistics

processes

􀂄 Manage serialized materials and components in your procurement process

􀂄 Procure-to-Pay: Multiple account assignment

􀂄 Beverage empties management in purchasing

SRM 7.0 on one client in SAP ERP is available with SAP ERP 6.0 EhP4 with SAP NetWeaver 7.01.

SRM 7.1 on one client in SAP ERP is available with SAP ERP 6.0 EhP5 with SAP NetWeaver 7.01

What is new on EHP5 - bUSINESS FUNCTION RELATED TO SRM

MUTHU

[Former Member · Accepted solution]

Hi Muthu,

First of all the release of SRM EHP1 seems to go together with the release of ECC EHP5. Allthough some of these features only require an ECC EHP4 back-end most will require an ECC EHP5 back-end.

New SRM features that require an ECC EHP5 back-end:

- BW-independent analytics

- SRM one client for SRM 7 EHP1 requires an ECC EHP5 back-end. It includes features like:

􀂄 Simplified User Interface with Extensive Personalization

􀂄 Highly Flexible Workflow

􀂄 Unrestricted Catalog Connectivity

􀂄 Internal SRM-MDM Catalog Included

􀂄 Run SRM One Client without Portal, PI and BI (more details below)

􀂄 Extension of supported scenarios for SRM One Client in SRM7.01/ERP6.0 EhP5

(note: SRM one client for SRM 7.00 already requires an ECC EHP4 back-end system)

Note: We want/need/will have SRM 7.0 EHP1 for PI independent services functionality (supporting both synchronous and a-synchronous services via txn SOAMANAGER (client-side pi?)).

Kind regards,

Tim

Edited by: T. Schuffelen on Jul 5, 2010 8:52 PM