Connect NW 2004s with ECC 5.0

Hello gurus,
I have a problem, I'm trying to connect the SAP DEV BI System (Netweaver 2004s) to the SAP DEV R3 (ECC 5.0), both RFC are created. All tests are fine between SAP BI System and SAP R3 system, means that my BI system can connect to R3. Anyway, the RFC that connects SAP R3 with SAP BI doesn't work cause an authorization issue.
The user data used is the followin:
User: rfcuser
Type: system
Profiles: S_BI-WHM_RFC, SAP_ALL, SAP_NEW (as suggested in best practices)
While trying to test the RFC connection, the connectivity test is ok, anyway it fails on the authorization test.
Any ideas?
Best regards,
Pilar Infantas.

Dear gurus,
Is it possible that this happens due to the version of SAP_BW in SAP R3 server?. There the SAP_BW 350 0016 SAPKW35016 Business Information Warehouse, while on SAP BI server it is SAP_BW 700 0012 SAPKW70012 SAP NetWeaver BI 7.0.
Best regards,
Pilar Infantas.

Similar Messages

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

Older CUA version connectivity and functionality with ECC 6.0

Our current Solution manager box, which is used for CUA, is on Netweaver 04 (sap basis 640 patch 16). We are in the process of upgrading to ECC 6.0.
Generally speaking I would recommend having a CUA box at the same level or higher than the child systems. However I'm would like to know if anyone has experience with a similar version scenario as described above. If so what issues did you run into and or other items should I be aware.
Also, ECC has several new system parameters and other password related changes. Can any of the newer password functionality be used if CUA is still on the older version?
--B

have a look at this thread
Technical upgrade to ERP2005 6.0 and CRM2007 with CUA on 640?
it should answer both your questions.

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

Problem connecting SAP IS-U (ECC 6.0) with Business Objects Edge 3.1

Dear all,
I'm trying to connect to a SAP ECC 6.0 System (SAP IS-U) with Business Objects 3.1 (for example with Crystal Reports). I have installed the SAP RFC SDK on the ECC server and have imported these transport files:
Open SQL reporting objects
InfoSet reporting objects
Row Level Security Tool
Security functions
Cluster Definition Editor
But CR keeps returning this error "You do not have the necessary rights to design reports against the SAP System". I've read a few threads about that problem here. I couldn't find a specific "ABAP transport" - did I miss to import anything else?
Is there any way to check whether the transport files work as they are supposed to? Like the MDX parser connection test for SAP Business Warehouse.
Any other suggestions?
thanks in advance!

Hi,
I read about these authorization tasks in some other thread, but didn't know what to do.
But now I found the auth. object in the transaction SU21.
Since I cannot edit SAP_ALL I created another profile in transaction PFCG (just in case someone else is still messing with that problem) and added all activities of ZSEGREPORT ans S_RFC.
After that I added the profile to the users in question.
Now everything works like a charm.
Thanks alot!

Connecting Enterprise Portal with SAP ECC 6.0 for ESS/MSS

Hi,
I am trying to connect my Portal with the ECC backend but getting the error "SAP_R3_SelfServiceGenerics_MetaData". However when I tried to set the configuration in the JCo destination, I am not able to locate the message server for my ECC instance in the configuration page.
Any idea on this?

Hi,
Do the following steps.
1. Login to your SLD URL
http://hostname of sld:5<NN>00/sld
give the input as administrator username and password.
Once you are IN.
click on administrator TAB
Click on Profile TAB
In section TAB select DATASUPPLIER
Fil the detail in GATEWAY HOST and GATEWAY SERVICE ( SAPGW<NN>)
Gateway information should be on newly install gateway instance.
Then click on save.
Again click on Administrator TAB and click on STOP SERVER and then click on START SERVER.
Once above actvity done on SLD syste,.
Then go back to your ABAP stack in RZ70 and mainain the neccesary detatils and start the job, it should work now.
Thanks
Anil

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.

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

Error Connecting to SLD, while CC integration with ECC 6.0

Dear All,
I am using the CC v and from ECC IDES. I cannot connect to the SLD. It is giving an Error.
When I try to register the Server Programs in Vis Admin and click the SET button I am getting an error "Error Adding Bundles". In the ABAP part I am getting the same error of RFC connection.
Now from ECC when I do a SM59, and then goto TCP/IP connections, on creating this connections I cannot make them UNICODE as the R3 system is Non-Unicode. So these dont work.
What am I supposed to do.
Please let me know. This is very urgent and useful replies will be awarded full points.
Thanks and Best Regards
Chakra and Somnath

Replying to this old post hoping for some answers.
We had researched this and converted to Integrated ITS using our ZCATW over a year ago. The notes read that while integrated ITS is a suppoted platform, ESS scenarios for which newer technology exists are no longer supported. We tested ZCATW under ECC5 and decided to move forward because of a pending technical upgrade. We are now in the middle of the technical upgrade and wishing to keep it technical we are trying to keep ZCATW going and then look at the newer components as a seperate project. Has anyone found a way to overcome the above issue in CATW/ECC6?
Thanks,
Doug

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.

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

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.

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.

ESS Configuration with ECC 5.0

Hi
I am trying to configure ESS with ECC 5.0 as the HR server
My J2EE system is WAS 7.0 with EP 7.0 and patch level 12.
I am getting the following error when I am trying to get the ESS pages in EP
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcXssMenu.AreaConfig.AreaConfig_Output.Serviceinfo): structure field Helperservice not found
I was successfull in configuring ESS with ECC 6.0. I did the same configuration for ECC 5.0 also.
Can anybody help me
Thanks

Hi Jeevan,
Please check your land scape is as per the notes:
1007341     SAP ERP 2004/2005 - supported ESS/MSS system landscapes
824757      Dependencies between SAP ERP component lists
1034385     BP ESS/MSS ERP2004 and ERP2005 on EPNW04s
1004528     SAP Self Services: Business packages and components
BR, Abdul

Installed Netweaver 2004s with Rapid Installer , can not connet to BI7.0!!!

Hi,
I installed Netweaver 2004s with rapid installer but i can not connect to BI7.0 with SapLogon 710. SapLogon waiting for response forever. What are the post actions after I installed the Netweaver 2004s. I can connect to portal by IE.
I am new to this so any help will be greatly appreciated.
thanks,
Jenni

OS is Windows Server. SAPID is IKI. I am the only one trying to connect to BI so DPMON is not the issue. I wanted to stop and start the SAPIKI_03 service but I can not stop it, maybe it is related to that.
What are the post steps after installing rapid installer?
How can I make sure that I installed Java+Abap stack or only Java?
Thank you for your help.
jenn

Connect NW 2004s with ECC 5.0

Similar Messages

Maybe you are looking for