Connect BI 7.0 with ECC 5.0

Hello all,
I don't seem to succeed when trying to connect my BI system with my ECC system. I have followed the best practices document "BI Connectivity" step by step, but I still get errors.
When performing a connection test from BI - SM59 (one of the two "test" buttons in SM59) I succeed. However, when trying to logon remotely (the other test button) to the ECC, nothing at ll happens.
When performing a connection test from ECC - SM59 I fail ("Error opening an RFC connection"). Also, when attemting to logon remotely to the BI system, I fail ("error opening an RFC connection").
What should be done here? Any ideas?
Thanks,
F C

Please don't post the same question at multiple fourms:
connection BI 7.0 - ECC 5.0
Close any one of them.

Similar Messages

BI connection with ECC

Hello BI experts,
Iam BASIS guy and working on SAP R/3 4.72 to ECC6 upgrade project.I have few tasks which is related to BI7.0 & source systems
Let me put like this current landscape
SAP R/3 4.72 - DVE QAS PRD
SAP BI7.0 BD1 BQ1 BWP
Now we are upgrading SAP R/3 4.72 to ECC6 in seperate hardware in parallel ladscape.Copy DVE to another system and different SID ( EC1 ), QAS to (EQ1) and PRD upgrading on same hardware.
So we will have to maintain two landscape parallely till live.And then we will break old source system SAP 4.72 and continue with new systems ECC.
I know as per SAP best practice we need sepearte BI landscape for upgrade landscape instead of same hardware.But customer can not spend money for new hardware and they wanted to go with same hardware.
I will Integrate BD1 to new source system EC1 and similar to QA, but after creating this source system I can see duplicate two source systems , one old and another new. And again 2 info packakeges and 2 process chains and etc..
How we can handle such type of landscapes? Do we need any BI manual activites? and how much effort we have to put?
Your expert solutions greatly appriacted?
- Jim

Hi,
Creating Source System (SALE): This step creates source systems which are to be connected.
1.
Assigning Source System to Client (SALE): This step gives a logical name to a SAP Client from which the communication is to be established.
2.
Setting up RFC Destination (SM59): This step is required to establish remote connection to the partner with which Source system is trying to communicate. Here one has to maintain the logon and IP details of the target system.
3.
Distributing Data Model (BD64): A distribution model is used to model a distributed environment in which you specify messages exchanged between sending and receiving systems. Here one has to define the message protocols with which the two systems will communicate.
4.
Generating Partner Profile (BD82): This process generates a partner profile for each system with which your system communicates. Outbound records are created in the partner profile for each outgoing message, and inbound records are created for each incoming message.
Note: If one distributes Data Model before generating partner profile then one has to redefine partner profile in other system also (repeat step in both system). In this document we are generating partner profile after Distribution of data model so as to demonstrate how to maintain inbound and outbound message types in WE20.
5.
Maintaining Message Types (WE20): This process is optional. Generally while generating partner profiles we automatically get the respective Outbound and Inbound messages, which can be checked in T-Code WE20. If the message types are not defined then one can manually do it by following this process.
These steps will ensure that the BW and other source systems are in sync and will communicate as expected.
SAP COMMUNITY
Step 1: Define Logical System in R/3
Step 2: Assigning Logical System to Client
Step 3: Setting Up an RFC Destination
Step 4: Distributing Data Model
Message Types Involved in Process of Data Loading
Step 5: Generating Partner Profile
Step 6: Maintaining Message types in T-Code WE20
Regards,
Suman

SAP Lumira 1.17 Connectivity with ECC 6 giving error

Hi Expert,
We're on SAP Lumira 1.17 and I'm getting attached error when I'm connecting with EC 6 via Query with SQL. I've attached the error log. Can you someone please look into this , how can I resolve this error to connect with ECC.
I'm trying

Hi Antoine,
Thanks for response.
Are you able to connect to this ECC system using either:
- a SAP tool like SAP logon
Yes, I can.
- a BI tool like information design tool (if you have access to it)
Yes, I can access. I can also connect UNX universe which is built on ECC with Webi as well. It's only in Lumira which is not working.
-Can you try from SAP Lumira changing the language used?
Yes, I tried to change different language (US and UK both) but not working.
-As the base error from your log file raised from ECC is
This error log is generated from Lumira only.
Thanks,
Pawan

EP 70 connectivity with ECC 6.0 (SAP NW2004s)

Hi,
I have recently upgrade r3 4.7 (32 bit) to ecc 60 (64bit)
We also install EP 70 (NW2004s SR3)
I am not able to connect Enerprise Portal 70 to ECC 60 system
Also how to put ESS business package in EP
regards
vikas nagar

Hi Vikas,
Just go through this thread it will help you
[/message/998346#998346 [original link is broken]|/message/998346#998346 [original link is broken]]
Also check this link in help.sap.com
[http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm|http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm]
Regards,

EP6 SP2 [WAS620] Can Connect with ECC 6 [WAS700] ?

Here portal is EP6 SP2 [WAS620]
And Backend Server Upgrading to ECC6.0.
Is it possible to continue with Portal 6 with ECC 6 ?
Any specific SAP Note for this compatibility ?

Hi Sumanta,
that depends on what you are doing. If you have for example "only" some SAP transaction iView that should still work.
Also other JCo based iViews will work -- you will however not be able to run the latest business packages for ESS (for example) because they require a EP7.
Regards,
Holger.

Can SAP GRC AC 5.3 connect without any problem with SAP R/3 4.7 Enterprise?

hello,
I went to the PAM in the SAP Marketplace to see if SAP GRC AC 5.3 could connect to SAP R/3 4.7 Enterprise but I can't see all the "Add-On Product Version for...", it's cut off.
Can SAP GRC AC 5.3 connect without any problem with SAP R/3 4.7 Enterprise?
If I can't is there any proof about it? I have to show it to a client.
Best Regards,
Pablo Mortera,

Pablo,
GRC AC 5.3 works perfectly fine with SAP's R/3 4.6c, mySAP ERP 4.7 and ECC systems. In fact we have two 4.7 Enterprise systems connected to GRC AC 5.3 system.
You can get the details of supported SAP ERP systems under prerequisite section of Info page of GRC AC 5.3 , it can be accessed on marketplace at -
Downloads-->Installations and Upgrades - Entry by Application Group > SAP Solutions for Governance, Risk, and Compliance>SAP GRC Access Control>SAP GRC ACCESS CONTROL>SAP GRC ACCESS CONTROL 5.3
Just ensure to have proper BASIS and ABAP support pack level as mentioned in prerequisites.
Regards,
Amol

RFC & Excel VBA with ECC 6.0

I use a routine like this to post movements in R/3 (This is an example for MB1A Transaction) based on information posted on a excel spreadsheet + VBA and seudo-code created with SM35 transaction
Public Sub updateRFC_BDC()
'Set sheet specific variables / constants
j = 0
startRow = 3
colStatus = 1
colMsg = 1
' Cell information on the excel spreadsheet
colMKPF_BLDAT = 2
colMKPF_BUDAT = 3
colMKPF_OIB_BLTIME = 4
colRM07M_BWARTWA = 5
colRM07M_WERKS = 6
colRM07M_LGORT = 7
colXFULL = 8
colRM07M_WVERS3 = 9
colMSEG_MATNR = 10
colMSEG_ERFMG = 11
colMSEG_ERFME = 12
colMSEG_WERKS = 13
colMSEG_LGORT = 14
colMSEG_CHARG = 15
colMSEG_OIHANTYP = 16
colOIB_A08_TDICH = 17
colOIB_A08_TDICHEH = 18
colOIB_A08_MTTMP = 19
colOIB_A08_MTTEH = 20
colOIB_A08_TSTMP = 21
colOIB_A08_TSTEH = 22
colOIB_A08_MCF = 23
colDKACB_FMORE = 24
colCOBL_PRCTR = 25
i = 0
'Set debug mode
If CheckBox1.Value = True Then
   DEBUG_MODE = True
Else
   DEBUG_MODE = False
End If
'Reset status column
Range(Cells(startRow, colMsg), Cells(60000, colMsg)).Value = ""
'Login to SAP, if it fails, notify user and exit sub
updateStatus "Logging into SAP...", colStatus, 1
If Not login2SAP Then
   MsgBox "Login to SAP failed. Remote Function Call NOT performed.", vbInformation, "Login Failed"
   updateStatus "", colStatus, 1
   Exit Sub
End If
'While the next row is not empty loop through BDC
While Trim(Cells(startRow + i, 2).Value) <> ""
   firstTime = True
   updateStatus "Processing Row " & (startRow + i), colStatus, 1
   ' Retrieve the Function object (the Connection object must be set up before Function objects can be created):
   Set RfcCallTransaction = Functions.Add("RFC_CALL_TRANSACTION")
   'Set the export parameters
   RfcCallTransaction.exports("TRANCODE") = "MB1A                                                                                "
   RfcCallTransaction.exports("UPDMODE") = "S"
   Set BdcTable = RfcCallTransaction.Tables("BDCTABLE")
   'Highlight current row so user knows what is happening
   Cells(startRow + i, 2).Select
   'Screen SAPMM07M BDC code
   add_BDCData BdcTable, "SAPMM07M", "0400", "X", "", ""
   add_BDCData BdcTable, "", "", "", "BDC_CURSOR", "RM07M-LGORT"
   testForBlank_AddToBDC "MKPF-BLDAT", Cells(startRow + i, colMKPF_BLDAT).Value
   testForBlank_AddToBDC "MKPF-BUDAT", Cells(startRow + i, colMKPF_BUDAT).Value
   testForBlank_AddToBDC "MKPF-OIB_BLTIME", Cells(startRow + i, colMKPF_OIB_BLTIME).Value
   testForBlank_AddToBDC "RM07M-BWARTWA", Cells(startRow + i, colRM07M_BWARTWA).Value
   testForBlank_AddToBDC "RM07M-WERKS", Cells(startRow + i, colRM07M_WERKS).Value
   testForBlank_AddToBDC "RM07M-LGORT", Cells(startRow + i, colRM07M_LGORT).Value
   testForBlank_AddToBDC "XFULL", Cells(startRow + i, colXFULL).Value
   testForBlank_AddToBDC "RM07M-WVERS3", Cells(startRow + i, colRM07M_WVERS3).Value
   add_BDCData BdcTable, "", "", "", "BDC_OKCODE", "=NPE"
   'Screen SAPMM07M BDC code
   add_BDCData BdcTable, "SAPMM07M", "0410", "X", "", ""
   add_BDCData BdcTable, "", "", "", "BDC_CURSOR", "MSEG-OIHANTYP"
   testForBlank_AddToBDC "MSEG-MATNR", Cells(startRow + i, colMSEG_MATNR).Value
   testForBlank_AddToBDC "MSEG-ERFMG", Cells(startRow + i, colMSEG_ERFMG).Value
   testForBlank_AddToBDC "MSEG-ERFME", Cells(startRow + i, colMSEG_ERFME).Value
   testForBlank_AddToBDC "MSEG-WERKS", Cells(startRow + i, colMSEG_WERKS).Value
   testForBlank_AddToBDC "MSEG-LGORT", Cells(startRow + i, colMSEG_LGORT).Value
   testForBlank_AddToBDC "MSEG-CHARG", Cells(startRow + i, colMSEG_CHARG).Value
   testForBlank_AddToBDC "MSEG-OIHANTYP", Cells(startRow + i, colMSEG_OIHANTYP).Value
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPMM07M                                2400BLOCK1"
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPMM07M                                2400BLOCK2"
   add_BDCData BdcTable, "", "", "", "BDC_OKCODE", "/00"
   'Screen SAPLOIB_QCI BDC code
   add_BDCData BdcTable, "SAPLOIB_QCI", "0500", "X", "", ""
   add_BDCData BdcTable, "", "", "", "BDC_CURSOR", "OIB_A08-TDICH"
   testForBlank_AddToBDC "OIB_A08-TDICH", Cells(startRow + i, colOIB_A08_TDICH).Value
   testForBlank_AddToBDC "OIB_A08-TDICHEH", Cells(startRow + i, colOIB_A08_TDICHEH).Value
   testForBlank_AddToBDC "OIB_A08-MTTMP", Cells(startRow + i, colOIB_A08_MTTMP).Value
   testForBlank_AddToBDC "OIB_A08-MTTEH", Cells(startRow + i, colOIB_A08_MTTEH).Value
   testForBlank_AddToBDC "OIB_A08-TSTMP", Cells(startRow + i, colOIB_A08_TSTMP).Value
   testForBlank_AddToBDC "OIB_A08-TSTEH", Cells(startRow + i, colOIB_A08_TSTEH).Value
   testForBlank_AddToBDC "OIB_A08-MCF", Cells(startRow + i, colOIB_A08_MCF).Value
   add_BDCData BdcTable, "", "", "", "BDC_OKCODE", "=CONT"
   'Screen SAPMM07M BDC code
   add_BDCData BdcTable, "SAPMM07M", "0410", "X", "", ""
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPLKACB                                0001BLOCK"
   testForBlank_AddToBDC "DKACB-FMORE", Cells(startRow + i, colDKACB_FMORE).Value
   'Screen SAPLKACB BDC code
   add_BDCData BdcTable, "SAPLKACB", "0002", "X", "", ""
   add_BDCData BdcTable, "", "", "", "BDC_CURSOR", "COBL-AUFNR"
   testForBlank_AddToBDC "COBL-PRCTR", Cells(startRow + i, colCOBL_PRCTR).Value
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPLKACB                                9999BLOCK1"
   add_BDCData BdcTable, "", "", "", "BDC_OKCODE", "=ENTE"
   'Screen SAPMM07M BDC code
   add_BDCData BdcTable, "SAPMM07M", "0410", "X", "", ""
   add_BDCData BdcTable, "", "", "", "BDC_CURSOR", "MSEG-ERFMG"
   testForBlank_AddToBDC "MSEG-ERFMG", Cells(startRow + i, colMSEG_ERFMG).Value
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPMM07M                                2400BLOCK1"
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPMM07M                                2400BLOCK2"
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPLKACB                                0001BLOCK"
   testForBlank_AddToBDC "DKACB-FMORE", Cells(startRow + i, colDKACB_FMORE).Value
   add_BDCData BdcTable, "", "", "", "BDC_OKCODE", "=BU"
   'Screen SAPLKACB BDC code
   add_BDCData BdcTable, "SAPLKACB", "0002", "X", "", ""
   add_BDCData BdcTable, "", "", "", "BDC_CURSOR", "COBL-AUFNR"
   testForBlank_AddToBDC "COBL-PRCTR", Cells(startRow + i, colCOBL_PRCTR).Value
   add_BDCData BdcTable, "", "", "", "BDC_SUBSCR", "SAPLKACB                                9999BLOCK1"
   add_BDCData BdcTable, "", "", "", "BDC_OKCODE", "=ENTE"
   add_BDCData BdcTable, "TCDEMB1A                                                                                ", "", "", "", ""
   firstTime = False
   ' Call the function (if the result is false, then display a message):
   If RfcCallTransaction.CALL = True Then
       Set Messages = RfcCallTransaction.imports("MESSG")
       If DEBUG_MODE Then
           printBDCTable (startRow + i)
       End If
       Cells(startRow + i, colMsg).Value = Messages.Value("MSGTX")
   Else
       MsgBox " Call Failed! error: " + RfcCallTransaction.Exception
       updateStatus "Error!", colStatus, 1
   End If
   i = i + 1
   j = 0
   Messages.Value("MSGTX") = ""
Wend
logOffSAP
If DEBUG_MODE Then
    MsgBox "BDC file written to : " & DEBUG_FILE
End If
updateStatus "Processing Done. Logged off of SAP", colStatus, 1
End Sub
Now I'm trying to use this routine for ECC 6.0, but it looks like the export parameter changed and it is not working.
Could you please help me to debug this routine to make it work with ECC 6.0
Thanks

Dear Javier Cantini,
Welcome to SCN.
Post your queries in relevant forum. Your query is technical in nature and should be posted in ABAP forums. Moving your thread to ABAP, General forum.
Regards,
Naveen

Connection between webdynpro java and ECC.

Hi experts,
I am very new to webdynpro java, I want to learn webdynpro java since I know little bit of java.
So here is my question,
I want to connect my webdynpro java to ECC to get data from ECC and display it on front end and as well i want to send data to ECC, can anyone help me to resolve this one.
Thanks and Regards,
Santoshkumar.

Hi Santosh,
This is pretty basic stuff in the world of Web Dynpro Java - I'd suggest you search SCN, read content on help.sap.com and then come back here with more specific questions. All anyone can do to answer your current question is search for you and post links to documents that you could find for yourself.
Cheers,
G.

Connect one Business system with two Integration Server

Hello,
Can we able to connect one Business System with two Integration Server?
I have one Business system (ECC 6.0 with the client 900) and it is already connected with PI 7.0 system.Can I able to connect the same sytem (with same client) with PI7.1?
I want to do the HTTP Connection for ABAP Proxy for this two XI system with one business Sytem ?
Is this possible ?Is there any work around solution there?
Thanks.

Hello ,
This document describes about connecting with Two PI7.1 system using Application Server 7.1 and Application Server 7.0 SP14 .
I want to connect same ECC system via abap proxy with two different PI system .One is PI7.0 and another one is PI7.1 system.
Is this possible if i use Application Server 7.1 or Application Server 7.0 SP14 ?
Thanks.
Lakshmi
Edited by: Muthulakshmi Pandi on Apr 16, 2009 11:48 PM
Edited by: Muthulakshmi Pandi on Apr 17, 2009 12:21 AM

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.

CRM 2007 integration with ECC 6.0

Hi Friends,
I am currently working on the CRM 2007 Web UI
I have created the copy of existing standalone CRM client which is already having products, organization, BP created in it.
Now I am planning to connect the CRM client with the ECC client.
Is there any special care i need to take while connecting both the systems?
Also while doing replication any extra care do I need to take?
Help will be definately rewarded?
Cheers,
Raj

Hi!
Check the SAP Best Practices documents
http://help.sap.com/bp_crmv12007/CRM_DE/HTML/index.htm
There have a look at
C71: CRM Connectivity
B09: CRM Customizing Replication
regarding the connection and replication
rollo

Is it possible to use XSS 2005 on EP7 with ECC 5.0 ?

Hi all,
I have an ECC5.0 and I want to upgrade my EP6 to EP7. I'm using XSS 2004 on EP6 and I want to use XSS 2005 on that EP7. I've seen on different notes that it is not possible to use XSS 2005 with ECC 5.0 as a back end.
Is there any solution to connect XSS 2005 to ECC 5.0 ??? Please I really need a positive answer
Thanks,

Hi Joseph,
I have gone thru same problem in my last project but my situation was little different.
Actually Business Package of ESS/MSS has two components:
1. Portal Objects (iView, Roles, Pages etc )
2. XSS - The Java WebDynpro Code (which in turn contain 3 component SAP_ESS, SAP_MSS, PUSIC_GP)
Also the prerequisite is that we should have SAP_HR (will give HR functionalities in ECC) and EA_HR (contains RFC, structure required for XSS).
Now the restriction imposed by SAP is that SAP_HR, EA_HR and XSS should be on same version and patch level. Make sense also. However there are situation where you can deviate from above restriction. (I will explain the same below).
So what you can do is to install the Portal objects(iView, Roles, Pages etc ) on EP 7.0 (can be installed on EP 6.0 and federated to EP 7.0), install XSS 2004 on EP6.0 (having JAVA 640) and connect the same with ECC 5.0.
You are looking to install Portal Objects, XSS 2005 on EP 7.0 and connect with ECC 5.0. This is possible but NOT recommended. Actually XSS 2005 WebDynpro will look for enhanced structures, RFC in ECC, which XSS will not find and will throw dumps (sometime java and sometime SAP dumps). You can fix the problem by manually installing the new functionality but believe me it is VERY cumbersome task and will make your system highly unstable.
What I would advise you is to look into your requirement once again and educate your end client with the problem and take appropriate action accordingly.
Do let me know if you need any further help.
Cheers,
AB

Enterprise Services - Architecture - Interaction with ECC

Can someone please link to architectural docuementation for Enterprise Services which explains how NW PI interacts with ECC?

Hi Jesse,
> I've already searched and not found what I was looking for
Which means you haven't used proper keywords. PI and ECC integration (using proxy, RFC, Idoc etc) is well documented and I am surprized to know that you weren't able to find it.
>So you should assume that the poster has already searched.
Nope. This is very common for people to do "Crowd-sourcing" and "do-my-job" and post question without searching (or rather lazy search) and that's why moderators are there
Let me give you few keywords for search.
ECC Proxy PI = Proxy connection between PI and ECC (provider as well consumer)
ABAP Proxy PI = same as above
SWF_BAM = Business Event triggering outbound services
Still you won't be able to find then read following:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0e7ae66-be6d-2a10-d385-92e6e67dee10
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50d69314-1be0-2b10-11ab-8045021f0c3a
>If you have links, please do share, but please do not again reply to anyone's post with, "Go search."
Sorry if you are looking for spoon-feeding then you are asking at wrong place. I can only help you with some basics and then you need to figure things out by yourself and "one-liner" question won't help either.
Regards,
Gourav

SRM 7 ehp1 with ECC 6 ehp5?

Gurus,
Is it mandatory to use SRM 7 ehp1 with ECC 6 ehp5? Our client has ECC 6 ehp 4 and is now upgrading from SRM 4 to SRM 7 ehp1. Can you share some links where I can confirm if SRM 7 ehp1 with ECC 6 ehp5 is mandatory?
Also pl let me know what is the difference between shopping cart creation in SRM 4.0 and SRM 7.0 ehp1. SAP says they have changed something and made it more user friendly. Is it different from normal SRM 7 (without the ehp component?)
Regards,
John

Hi,
There are 3 ways of sending PO from SRM to ECC
1.Via - RFC ( by setting the system landscape to a lesser version ) it will not have any side effects just that it used RFC connections instead of ESOA
2.Via PI - by setting the landscape to the current version and configure the relevant XML services in the SOAMANGER
3. via Non PI Web Services- by setting the landscape to current version . This time the webservices are configured in SRM system itself.
I have configured transfer of Contracts from SRM 7.01 to ECC 6.5 EHP5 as Contract/ Scheduling Agreement to the backend with Non PI Web Services(via XML). This way we didnt have to install PI at the client place which saved them a lot.
I have written a blog on how to transfer central contracts from srm to ecc using web services but without PI , please find the link below and hope it is helpful.
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/13/transfer-of-central-contract-from-srm-to-ecc-using-web-services-without-pi
Regards,
Naveen

I tried to connect SAP BW7.0 with use Jco2.1.7...

I tried to connect SAP BW7.0 with Jco2.1.7(64bit Itanium) in Microsoft Windows 2003 on IA64 and x86_64 with SUN JSE 1.4.2 (64-bit VM).
But I got error as followings.
java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.
path [C:\fds2\jrun4\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\oracle\product\10.2.0\client_1\bin;C:\WINDOWS\system32;C:\WI
NDOWS;C:\WI
what's wrong?
one more question
What is the "Microsoft C runtime libraries version 7"?
Message was edited by: kooknam han

Hi,
I think it's not possible to create a Universe directly on ECC 6.0.
You need to use a Data Federator for this to work. A Data Federator view is created on top of the ECC source using the connector then you can create Universe on top of Data Federator.
Check the below for more info on the same.
SAP BusinessObjects Web Intelligence Reporting for SAP ERP
Data Federator Installation Guide:
http://help.sap.com/businessobject/product_guides/boexi3SP1/en/xi3_sp1_df_install_en.pdf
User Guide on Data Federator:
http://help.sap.com/businessobject/product_guides/boexi3SP2/en/xi3_sp2_df_userguide_en.pdf
Hope it helps.
Regards,
Raghu

Connect BI 7.0 with ECC 5.0

Similar Messages

Maybe you are looking for