MDM compatibility with ECC 6.0

Hi Gurus
Need to know whether MDM catalog functionality is available with ECC 6.0 and above versions?
Regards
harsh

Hi,
Yes, MDM catalog functionality is available with ECC 6.0 and above versions.
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6075d293-291b-2a10-7fbb-b827b28fd9b0]
Regards
Krishna

Similar Messages

ITS 6.1 compatability with ECC 6.0

Hi,
can you say me whether ITS 6.1 is compatable with ECC 6.0?
Thanks,
Architha

Hi,
latest ITS standalone version was 6.20.
But this can not be used with systems based on 7.0 kernel. Here you should use the integrated ITS.
You can also have look at Notes 905135 and 197746.
Regards
Guido

Crm compatibility with ECC 5.0

Could you please confirm that CRM 2007 can be ran together with ECC 5.0 and where I could find these kind of "compatibility" informations?

Hi Edwin
see similar post with this topic ....
Such information normally found in the Master Guide for SAP CRM (service.sap.com/instguides). This you should check first.
As an integration of a complete application does not exist, but an integration on product instances ("systems") level, the following approach is possible as well
-identify the required product instance for your scenarios in the Scenario and Process Component List viewer (service.sap.com/scl)
- check the dependency matrix (see http://www.sap.com/community/flash/KW22_08_Story_1.epx)
Keep in mind: As integration topics depend on customer specific system designs, you should test the situation in your own system landscape (Above sources concentrate on general recommendations)
regards,
Andreas R

BC compatibility with ECC

Hi,
Could any one get me the SAP document for compatibility of Business Connector with ECC.
Their help is highly appreciated.
Regards,
Gopinath Addepalli.

hi,
there's no new version/update of BC for ECC
so you can only use the same interfaces
as with R/3 (idoc, RFC)
Regards,
michal

PI 7.0 compatibility with ECC 6.0

We are upgrading our ECC environment from 5.0 to 6.0 EHP4 wehre as our PI is version is 7.0. Please let me know if there would be any compatibility implication on interfaces between new ECC env and PI7.0. we have IDOC, RFC and proxy connectivity netween ECC and PI system. Is there any official SAP statement on this?
Thanks.

Ethan,
All we did was
importing SLD objects for EhP4.
reimport 6.04 version for SAP APPL ( this s std SWC provided by SAP)
Imported latest BASIS ( had to do this to fix a issue after upgrade to Ehp4)
And yes we have many scenarios on client/server proxies. They are all working fine.
Venkat.

SRM 7.01 with ECC 6.0 EHP 7.0

Hi Guys,
Does anyone have an idea on SRM 7.01 compatibility with ECC 6.0 EHP 7.0. Any things needs to be taken care from SRM side after an upgrade to EHP 7 in ECC side.
Please share your experience.
Thanks for your reply in advance.

Hi Imran,
It is compatible, But still for confirmation please see the product availability matrix.
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/support/pam/pam.html?smpsrv=https%3A%2F%2Fwebsmp203.sap-ag.de#pvnr=01200615320900003495&ts=4&pt=t%7Co
Best regards,
Rohit

Is ECC 5.0 and EP 6.0 Compatibility with Oracle 10g (10.2.0.2)?

Hi,
Is ECC 5.0 and EP 6.0 are Compatibility with Oracle 10g (10.2.0.2)?
Is there any blog or link to get the details on SAP Compatibility?
Regards,
Vamshi.

Yes, both versions are compatable with oracle 10.2.0.2.
https://websmp210.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=RELEASE&00200682500000002804=01200314690900000171&00200682500000003818=PLTFRM
Regards,
Jazz

Supplier Registration in ESourcing ( Vendor integration with ECC or MDM )

Hi All,
SAP ESourcing has the functionality of Supplier Registration. As per the functionality, Supplier will provide all the required information in the registration form. The Supplier form will go for approval to the Buyer / Purchaser. Once approved, the supplier will considered for RFx event. My questions are :
1 :Is there OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with ECC so that system will automatically create new vendor in ECC.
2 : Is there OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with MDM (Master Data Management system ) .
Please through some pointer on this ?
Regards,
Kalandi

Hi Kalandi
For your first question, if you deploy standard integration package provided by SAP for e sourcing-ECC integration, you can replicate approved e sourcing vendor to ECC using standard script (I think script name is "Publish to ECC" ).
In case you prefer a custom option,you can write a customized script to get a flat file (.CSV) download of e sourcing vendor whcih can be used to update ECC
As far as OUT OF BOX standard solution provided by SAP for integration of newly Approved supplier / vendor of ESourcing system with MDM (Master Data Management system ) is concerned, there is no standard solution provided by SAP but again since it is possible to get a CSV export of vendor field, it can be used to update MDM as well
Hope this helps!
Regards
Mudit Saini
Edited by: Mudit_UCB on Jun 28, 2011 1:20 PM

Compatability of ESS/MSS ERP 2004 with ECC 6.0

Hi,
I was using ERP 2004 ESS/MSS on EP 7.0 SP 8. My backend was ECC 5.0.
Recently we upgraded our backend to ECC 6.0. But after the upgradation the ESS/MSS packege is not working on the portal. Its showing the below error.
<b>com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.appdesigner.api_framework
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java(Compiled Code))
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java(Compiled Code))
    at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:180)
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:232)
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.start(SAPJ2EEApplicationItem.java:192)
    ... 8 more</b>
Is ERP 2004 ESS/MSS comapatbile with ECC 6.0 or there are any steps to be performed after upgradation from ECC 5.0 to ECC 6.0?
Any suggestions??
Regards
Debasish

The new Business Packages meant for ECC 6.0 are based on Webdynpro for Java ....which have a different and better look and feel ....these are based on a RoadMap(Floor Plan Manager) which let the employees/managers to go from Overview(dislay the data),edit (to change) ,Review(to review) and Confirmation (To Confirm)....
Hope it helps.
Shikhil

SAP R/3 4.7e compatable with Netweaver foundation ?

Hi,
could you please suggest me for below Queries .
1. Does IS-Media is very much compatable with 4.7e?
2. Will this present problems for us in any of the functionality we've
been expecting? Does 4.7
have the same Netweaver foundation, integration with XI and
Portals, etc?
3. Can i integrate 4.7e with other new dimentional products like
Solman3.2,XI,BW3.5,Portals , etc ?
4. Which SAP release is recomandable for IS-Media to work? 4.7e or ECC ?
I appriciate if you could suggest me for this.
Thanks,
Ahmed

Even in Sandbox landscape having R/3 & XI on the samebox is not recommended.
Moreover SAP R/3E & XI 7.0 don't have the same WebAs version(R/3 WebAS- 6.40 & XI WebAs -7.00). Hence they cannot be installed due to product compatibility. It should be atleast ECC 6.0.
-SM

List of modules with ECC 6.0

I am looking for information on different module and engine in SAP from licensing perspective , like Netweaver comes wih ECC 6.0. What about Open Hub ? Can anyone kindly provide list of module and what comes with what and how it is set up?

Licensing is what your contract states. Just because Netweaver comes with ECC 6.0 that does not mean you are licensed to use netweaver components like enterprise portal, MDM, BI etc. ECC 6.0 requires only web application server to run and perhaps other basis components, but other pieces of Netweaver are not automatically available to you. Look at something like this to help you with modules of SAP ECC 6 http://help.sap.com/saphelp_erp60_sp/helpdata/en/80/ea89395eb58c4f9d0c3e837cf0909d/frameset.htm
Click on logistics and modules are listed
Mike

SAP MDM == PI== SAP ECC, IDOC posting

Hi,
We are integrating SAP ECC 6.0 with SAp MDM 7.1 SP04 using PI 7.1 as a interface. Scenario is SAP MDM ==>PI==> SAp ECC. I would be creating record in ECC and will be posted in SAp ECC through PI. We will be creating Basic Data (MARA), Plant level data (MARC), Sales Level data (MVKE), and Valuation level Data (MBEW) in MDM. IDOC used is MATMAS05.
Plant level data (MARC) will activate various views in Material master like Purchasing, Sales plant general data, MRP views and accounting views...right
I donu2019t want to activate MRP view but need plant level data i.e. Plant and profit center to populate in MARC table. Means same Material Type but some Materials donu2019t have MRP view activated and some may have alongwith other plant related views.
I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory. (Which means it is activating MRP view)
Do we have separate IDOC for MDM integration?? Do I need to enhance IDOC??
Warm regards,
Rc
NOTE - This is possible while manual creation as will as through BAPI.

Hi,
Have you checked MDM71_Material_Content.pdf page no 20.
3.3.2 Business Scenario: MDM710_Outbound.
You also need MDM PI content to install and run this Scenario..
Hope it helps if you go through MDM71_Material_Content.pdf
As you said, I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory
Try passing any constant through PI Message Mapping to inbound IDOC (Receiving System, ECC)
Thanks and Regards,
Mandeep Saini

Compatible versions with ECC 6.0

Hi,
We are planning the upgrade of our SAP installations:
- R3 4.6C, 4.7 --> ECC 6.0
- BW 3.1, 3.5 --> BI 7.0 (NW2004s)
- SRM 2.0 --> SRM 5.0
- CRM 4.0 --> CRM 5.0
Of course we can't do all the upgrades at the same time, so, in order to decide in which order we make the upgrades, we must be sure that the new versions will be compatible with the old ones.
In the quicklink "service.sap.com/r3-plug-in", menu option "SAP R/3 plugin --> Integration of SAP R/3 / Enterprise, ERP and SAP Components" there are some tables where we can analyze the compatibility between all the BW, SRM and CRM versions and R3 versions prior to ECC 6.0 (4.6C, 4.7, ECC 5.0), according to the plug-in version. From 2005 there seems to be a strategy change in the integration interfaces:
"SAP ECC 6.0 and subsequent releases will automatically contain all integration interfaces that so far have been contained in the SAP R/3 Plug-In and that ensured the technical integration with other SAP Components."
As I understand, ECC 6.0 will automatically contain all the integration interfaces and there will be no more R/3 Plug-In versions. How can I check the compatibility between ECC 6.0 and the other BW, SRM and CRM versions? In the quicklink there are integration matrix available for R3 Enterprise and ECC 5.0 but there is no information for ECC 6.0. Are the versions compatible with ECC 5.0 too compatible with ECC 6.0? As ECC 6.0 seems to "automatically contain all integration interfaces that so far have been contained in the SAP R/3 Plug-In", does it mean that the integration matrix available for ECC 5.0 is too valid for ECC 6.0?
We have found a specific note (931020 "SRM connection to an ERP 2005 (ECC 600) backend") for the integration between ECC 6.0 and SRM but we didn't find any note regarding BW or CRM.
How can we check wich versions (BW, SRM, CRM) are compatible with ECC 6.0? Can we use the integration matrix available for ECC 5.0 in the quicklink "service.sap.com/r3-plug-in", are there specific notes like the one available form SRM (931020)?
We need to be sure as soon as possible that after the upgrade of our R3 4.6C and 4.7 versions to ECC 6.0 they will be compatible with our actual BW (3.1, 3.5), SRM (2.0) and CRM (4.0) versions.
Thanks in advance!!

to followed unicode rules.
ABAP Development under Unicode
Prior to Unicode the length of a character was exactly one byte, allowing implicit typecasts or memory-layout oriented programming. With Unicode this situation has changed: One character is no longer one byte, so that additional specifications have to be added to define the unit of measure for implicit or explicit references to (the length of) characters.
Character-like data in ABAP are always represented with the UTF-16 - standard (also used in Java or other development tools like Microsoft's Visual Basic); but this format is not related to the encoding of the underlying database.
A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or a NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.
If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.
As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.
Other Changes
1.     Bit Statements
2.     Adding Field Sequences
3.     Loops with VARY and VARYING
4.     Creating Subroutines
5.     Saving Programs
6.     Assigning Types for GET/SET PARAMETER
7.     Unreachable Statements
8.     Function Modules with Incorrect Parameter Names
1. Bit Statements
Previously, the system checked for the bit statements SET BIT i OF f [TO g] and GET BIT i OF f [INTO g]whether the field f is character-type; X fields, X strings, and flat structures are usually regarded as character-type. For Unicode programs this is no longer useful, because the types X and XSTRING no longer count as character-type and the bit by bit access to character-type fields or structures is no longer platform-independent. Therefore, with these operations in Unicode programs, the field f must be type X or XSTRING.
For the bit mask operations f O x, f Z x, and f M x you could previously use all number-type and hence all character-type types for the left operand f. In Unicode programs, the f operand must now be type X or XSTRING.
2. Adding Field Sequences
When adding field sequences, restrictions apply to the following statements in Unicode:
ADD n1 THEN n2 UNTIL nz [ ACCORDING TO sel ] GIVING m ...
ADD n1 THEN n2 UNTIL nz TO m [ RANGE str ].
1.     The operands n1, n2, and nz must be type-compatible with one another.
2.     The distance between nz and n1 must be an integral multiple of the distance between n2 and n1.
3.     A syntax or runtime error occurs if the fields n1, n2, and nz are not in a structure. This structure must be recognizable statically or its valid area must be marked explicitly using the RANGE addition.
4.     At runtime, the system ensures that the RANGE area is not left.
ADD n1 FROM i1 GIVING m [ RANGE str ].
1.     Field n1 must be within the structure. The structure must be explicitly defined using the RANGE addition if it is not recognizable statically.
2.     For this variant, the system also checks at runtime whether n1 and the addressed values are within the structure.
3. Loops
Loops with the VARY or VARYING addition are also problematic in Unicode, since a type-a access to memory contents cannot be ensured and memory can be overwritten inadvertently.
DO ... VARYING f FROM f1 NEXT f2.
For this statement, the fields f, f1, and f2 must be type-compatible with each other. To prevent memory contents being overwritten, a RANGE for valid accesses is introduced implicitly or explicitly for the following statements:
DO ... TIMES VARYING f FROM f1 NEXT f2 [ RANGE f3 ].
WHILE ... VARY f FROM f1 NEXT f2       [ RANGE f3 ].
A syntax or runtime error is caused if f1 or f2 are not included in f3. If the RANGE addition is missing, it is defined implicitly from FROM f1 NEXT f2 as follows:
1.     If both f1 and f2 are statically recognizable components of the same structure, the valid RANGE area is defined from the smallest structure that comprises f1 and f2.
2.     A syntax error is triggered if it is recognizable statically that f1 and f2 are not part of the same structure.
3.     A valid area must be defined explicitly using the RANGE addition if the connection between f1 and f2 is not recognizable statically.
If you specify a deep structure as the RANGE addition, the system checks for every loop pass that there are no field references, object references, tables, or strings in the area read.
4. Creating Subroutines
When automatically generating subroutines using the statement GENERATE SUBROUTINE POOL itab NAME name, the generated program inherits the content of the Unicode flag of the generating program.
5. Saving Programs
When automatically generating programs using the statement INSERT REPORT prog FROM itab, default values are set for the TRDIR entry as before. Amongst other things, this statement has the new addition UNICODE ENABLING uc, with which the Unicode flag of the inserted report receives the value of uc. If this addition is missing, the following applies:
1.     A Unicode program creates a Unicode program.
2.     A non-Unicode program in turn creates a non-Unicode program.
3.     A non-Unicode program becomes a Unicode program if it is overwritten by a Unicode program.
4.     A Unicode program remains a Unicode program if it is overwritten by a non-Unicode program.
6. Assigning Types for GET/SET PARAMETER
For the statements GET PARAMETER ID pid FIELD f and GET PARAMETER ID pid FIELD f, f must be character-type. You can use the EXPORT and IMPORT statements for storing non-character-type fields and structures.
7. Unreachable Statements
In Unicode programs, unreachable statements cause a syntax error. In non-Unicode programs, there was previously only a syntax warning.
8. Function Modules with Incorrect Parameter Names
In Unicode programs, calling a function module, whose parameter names are specified statically as a literal or constant, causes an exception that can be handled if an incorrect parameter name was specified. This only applies to function modules that are not called via Remote Function Call. In non-Unicode programs, an incorrect name was previously ignored.

ITS version compatabiity with ECC 6.0

Hi Experts,
I have to install ITS (server components) at one of my client side to some transaction on web, earlier they were using R/3 4.6 and they switched to ECC 6.0
Please tel me which ITS version is comatable with ECC 6.0
I installed server components (ITS) from R/3 4.7 cd pack but i was unable to publich internet services from se80, (published successfully message on status bar but no service in the c:\program files\SAP\ITS\6.20\service folder)
Then I tried to install ITS from ECC 6.0 cd pack but i was unable to install it. the setup.bat file ask for sapinst.exe file but its not in the CD(i also checked in another ECC6.0 pack )
I dont no which one is compatable with ECC6.0, i have to generate web services for some customised transactions, can anyone tel me how to solve this pproblem of installation or if any other way to generate web services please tel me the procedure...
Regards
Manish

Instead of PZM3, use the Homepage Framework to launch your ESS offering (HF is configured in the IMG and tied to the XSS Java components that will need to be installed as well). You can run ESS standalone in this manner although SAP frowns on it (hey, they want to sale the portal! haha).

ESS implementation posibility with ECC 6.0 and EP 6.0

Hi ,
To implement ESS with ECC 6.0 and EP 6.0
Any body can suggest for this implementation feasibility and possibility.
What are the Business packages has to down load and where can we get those BPs.?
After importing into EP 6.0 , what are the configurations and settings required to get SAP HR screens/ivews (preview when we create after systems in EP),
What are the prerequisites and hardware and software requirements for 8000 users (apprx) ?
Any version upgradations are required for implementing this or
can we use this ECC 6.0 as backend and EP 6.0
and please help required for all those things.
Thanks
Kumar.

For ESS/MSS based on ECC 6.0 (ERP 2005), you can download the XSS business packages from
service.sap.com/download --> Support patches and packages --> Entry By application Group --> SAP Application Components --> SAP ERP -->
SAP ERP 2005 --> Entry By Component --> SAP XSS --> (SAP ESS 600, SAP MSS 600 and SAP PCUI_GP 600).
You can use JSPM to apply these business packages on to the portal. To use JSPM, you have to login to the portal server using <SID>adm to be able to use the JSPM tool.
Business Packages and components in it: you BP consists of the 2 following parts
1) BP_ERP5ESS / BP_ERP5MSS is Portal Business package which consist of iview, pages and roles.. while SAP_ESS / SAP_MSS. is WebDynpro part of it.
These iviews will direct to some WD application which are part of SAP_ESS / SAP_MSS. and they are deployed on server.
2) you have to simple go to
service.sap.com/downloadSupport patches and packagesEntry By application GroupSAP Application ComponentsSAP ERPSAP ERP 2004/2005--Entry By ComponentSAP XSS
pick the correct version and download. You get full package not incremental. Old ones will be overwritten when you deploy them. try to download them again if it failed first time.
3) Refer note 761266 for package compatibility.

MDM compatibility with ECC 6.0

Similar Messages

Maybe you are looking for