IS M/AM 4.72 - Impact evaluation in upgrade from R/3 4.7 to ECC6.0

[Former Member]

Hi everybody,

I need to evaluate how the IS M/AM 4.72 version (running on an R/3 4.7) could be affected by an upgrade to ECC 6.0.

I have found documentation about new functionality/impact on Netweaver (es. SOA architecture) or in SD but nothinh specific on IS M/AM.

Thank you in advance

Emanuele

[former_member1052317 · Accepted solution]

There is no particular document which will impact the IS MAM module when upgraded from 4.7 to ECC 6. However there are a few additional functions in ECC 6 like series creation and improvised upselling  etc. These functions are also based on the EHP version. But the actual impact analysis should focus on the following

• Effects on any integrated systems for ad pagination
• The modified standard objects
• If you are not using the business partner functionality, then you may have to migrate your customers to business partners.
• Cut-over is the most important thing as getting downtime for the upgrade is very tough if you have a daily publication.

These conditions vary with each client as the implementation is specific to a publishing house and there can be a lot of objects that you 'll find in SPAU and SPDD list.

[Former Member]

Thank you for the answer.

Could you give me some example on what you mean about "Effects on any integrated systems for ad pagination"?

Is it a technical warning about tha way the system is integrated with technical system or something affected the process itself?

Thanks

Emanuele

[former_member1052317]

I mean if any technical interface exists with the IS-M/AM module for ad booking and pagination, it should be thoroughly tested and checked from the quality or development environment before upgrading the production. If any user exits are active for the technical interface, the flow from SAP - technical system and technical system - SAP, these should be not be effected after the upgrade.