Problems with ALV - Excel after changing from 640 to 710

Hi all,
first i have to say, that i have tried to set this thread in the SAPGUI-Forum,
but i didn't get any answers, therefore i try it here.
I have changed our SAPGUI from 640 to 710. Now i get problems
with ALV-GRID display.
When i change the output to EXCEL-Inplace i get the Error-Message:
0K000
View cannot be switched: Product is not installed or integration is not active.
In 640 i don't have any problems. We have ECC6.
When i use GUI710 and SAP 4.6C i don't have any problems.
Simple Test is possible with SE16N and change ALV output to excel-inplace.
Can anybody help?
Thanks.
Regards, Dieter

Hi Dieter,
we had a similar problem who we resolved installing path the GUI710_1-10002995.EXE.
Have you tried to install the patch?
Bye
Giovanni Mortati

Similar Messages

Problems with ALV - Excel after changin from 640 to 710

Hi all,
i have changed our SAPGUI from 640 to 710. Now i get problems
with ALV-GRID display.
When i change to EXCEL-Inplace i get the Error-Message:
0K000
View cannot be switched: Product is not installed or integration is not active.
in 640 i don't have any problems.
Can anybody help?
Thanks.
Regards, Dieter

Hi Roman,
in Service.sap.com there is the first patch-level of the new GUI7.10.
i have install it without any problems.
The problem i had with excal-inplace is solved.
Regards, Dieter

Problem with Push Notifications after change from 3GS to 4S

After I changed from my 3GS to my 4S I have a Problem with the Push Notifications.
I only receive them on my old device, not on my new 4S.
They both have different Phone Numbers, and i set the 4S up with a Backup from the 3GS.
How can I fix this problem?

I have the same phone, and have just had it replaced with an identical model and am having the same issue. I am going to go through Apple Care again and see what seems to be the problem. I never had any push issues with my 3G, except at the initial launch.

Problems with IMAQ Vision after upgrading from Labview 6i to Labview 6.1

Hi,
We just upgraded from Labview 6i to 6.1.To do this,we uninstalled the 6i version as was suggested by NI and then installed the 6.1 version.Later when we tried to run the old vi's written using Imaq vision, we ran into different problems.Has anyone experienced any similar problems with IMaq vision after upgrading?If so please help me solve this issue.
Thanx
deepak

What kind of problems?
I would strongly suggest that you uninstall IMAQ (all elements) and reinstall them. They register with Windows, probably docked to 6i, and also must be recompiled, which I believe is done in installation.
This is your best bet.
If you still have problems, contact NI and ni.com/ask and start a support inquiry.

How do I investigate and solve Pages, Notes, Mail intermittent 'offline' and failure to synchronise problems with Mountain Lion after waking from Sleep

When I wake up my iMac after sleep, i get a variety of intermittent - but mostly FREQUENT and FRUSTRATING problems including:
Notes app is offline - as stated by a message in the window bar. If I close Notes and reopen, the app appears to be online. However, Notes does NOT update with items I know are on my iPad or in the web iCloud. Furthermore, if I create a new note on my iMac, the new Note does not upload to iCloud. This is IRRITATING!
Pages and Numbers - similar situation. I can edit a Pages or Numbers document on my iMac (stored on the iCloud). But then the Pages doc doesn't ALWAYS get uploaded to the iCloud. Then I end up with conflicted versions of the file in the cloud, my iPad, and the two iMacs I use. Then I get CONFUSED and FRUSTRATED. For example, consider these steps:
Open Pages on my iMac, edit an iCloud file, then save and close file
Pages/File/Open/iCloud - I note in the iCloud file list the edited file has a little 'cloud' icon against its name. From experience this warns me of TROUBLE - namely that the file has NOT yet been uploaded to the iCloud. However, I just checked the new Beta iCloud on the web, and to my surprise, the file edited on my iMac is apparently in the icloud. But now, I edit the iCloud version, and the changes DO NOT appear on my iMac pages version. OK I realise its in Beta version...
So now, I open my iPad, open Pages. I note the iCloud version of my edited document updates to my iPad, as indicated by a blue download line. 'It just works' as Steve Jobs claimed at Apple Developers Conference a couple of years back. Again, the edited version form my iPad is now 'up in the cloud' correctly....
Oh - and now mysteriously the Pages version on my Imac has become synchronised with my iPad/iCloud version! Luck ... but that's about all I can say. It doesn't always happen. I'm LUCKY today.
Meanwhile, the Note I created on my iMac (Item 1 above) has still not yet appeared on my iPad or iCloud... even though I HOPE it would be given that Pages on my iMac, iPad and iCloud are chatting nicely now! The Note says it's in my iCloud - but NOT. Similarly, notes updated or added on my iPad, which appear in iCloud, are NOT on my iMac.
Mail - last but NOT LEAST! and MOST INFURIATING!!! My Gmail, Vodafone NZ and Orcon accounts (in Mail) are all active and receiving after the night's sleep. However, my iCloud mail account has the dreaded offline.
The message on Mail is "There may be a problem with the mail server or network. Verify the settings for account “ICloud - [email protected]” or try again. The server returned the error: The server “p03-imap.mail.me.com” cannot be contacted on port 993." Despite the message, mail was received this morning at 8:59 am ... some time before I woke-up my computer (a late start this morning).
If I sent an email FROM my .me iCloud account TO my Vodafone account, the message whooshes away, it's in my SENT box. But it doesn't get delivered to my Vodafone account on my iMac Mail, or anywhere else, Despite the message being listed in my 'Sent' mailbox!!!
In contrast, a message sent from my Gmail account to my Vodafone account (in Mail) gets sent and received almost instantly on my iMac and iPad.
All of the above mishaps are extremely frustrating, as I rush off from working on my iMac at home, get to my iMac at work and find documents I have been updating on my home iMac not available correctly on my work iMac ... or even my iPad. I expect these things from Apple to 'just work'. Furthermore, emails I THINK I have sent (as indicated by them appearing in the Sent folder on my home iMac) ... have not actually been despatched.
Frankly, I can no longer rely or recommend the Apple iCloud stuff, so I am converting more and more to relying on DropBox and Google.
These problems only became apparent since I updated to one of the Mountain Lion versions... I can't say when.
Oh - if I shutdown and restart the computer my Mail works OK. Guess what, I don't want to do that each time I want to use Mail!
Technicals:
My iMac is connected by Ethernet cable to my Apple TimeCapsule. The TimeCapsule is connected by Ethernet cable to my Orcon Genius Modem.
Obviously, my internet connection is A-OK, as I am able to use Firefox to make this posting!
Mountain Lion 10.8.4
iMac 27 inch, mid 2010, Intel Core i5 16 Gb

I've returned to my sleeping iMac after a few days away. Tis time, ALL MAIL accoiunts are offline. I will follow you next set of instructions. In the meantime, here is the DETAIL from MAIL CONNECTION DOCTOR:
LevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
19.10827 STATUS [Gmail]/Trash (UIDNEXT UNSEEN HIGHESTMODSEQ)
WROTE Sep 30 08:35:11.179 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
20.10827 STATUS INBOX (UIDNEXT UNSEEN HIGHESTMODSEQ)
WROTE Sep 30 08:35:11.202 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
21.10827 STATUS "Sent Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
WROTE Sep 30 08:35:11.226 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
22.10827 STATUS "Deleted Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
READ Sep 30 08:35:11.254 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
* STATUS "[Gmail]/All Mail" (HIGHESTMODSEQ 561701 UIDNEXT 1666 UNSEEN 105)
13.10827 OK Success
READ Sep 30 08:35:11.494 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
* STATUS "[Gmail]/Drafts" (HIGHESTMODSEQ 561701 UIDNEXT 1 UNSEEN 0)
14.10827 OK Success
READ Sep 30 08:35:11.514 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
* STATUS "[Gmail]/Important" (HIGHESTMODSEQ 561701 UIDNEXT 731 UNSEEN 8)
15.10827 OK Success
* STATUS "[Gmail]/Sent Mail" (HIGHESTMODSEQ 561701 UIDNEXT 532 UNSEEN 2)
16.10827 OK Success
* STATUS "[Gmail]/Spam" (HIGHESTMODSEQ 561701 UIDNEXT 16 UNSEEN 2)
17.10827 OK Success
* STATUS "[Gmail]/Starred" (HIGHESTMODSEQ 561701 UIDNEXT 19 UNSEEN 0)
18.10827 OK Success
* STATUS "[Gmail]/Trash" (HIGHESTMODSEQ 561701 UIDNEXT 546 UNSEEN 0)
19.10827 OK Success
* STATUS "INBOX" (HIGHESTMODSEQ 561701 UIDNEXT 603 UNSEEN 64)
20.10827 OK Success
* STATUS "Sent Messages" (HIGHESTMODSEQ 561701 UIDNEXT 138 UNSEEN 0)
21.10827 OK Success
* STATUS "Deleted Messages" (HIGHESTMODSEQ 561701 UIDNEXT 89 UNSEEN 0)
22.10827 OK Success
WROTE Sep 30 08:35:11.537 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
23.10827 IDLE
READ Sep 30 08:35:11.927 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
+ idling
READ Sep 30 08:35:15.472 [kCFStreamSocketSecurityLevelNone] -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
220 st11p00mm-asmtp002.mac.com -- Server ESMTP (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013))
WROTE Sep 30 08:35:24.784 [kCFStreamSocketSecurityLevelNone] -- host:mail.orcon.net.nz -- port:25 -- socket:0x7fc3161a1b00 -- thread:0x7fc315d05050
EHLO [10.1.1.4]
WROTE Sep 30 08:35:24.822 [kCFStreamSocketSecurityLevelNone] -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x7fc316e72a70 -- thread:0x7fc31850bec0
EHLO [10.1.1.4]
WROTE Sep 30 08:35:34.080 [kCFStreamSocketSecurityLevelNone] -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
EHLO [10.1.1.4]
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316fc30e0
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc31a6fa8a0
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316197890
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316e813d0
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0350
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3185c0410
INITIATING CONNECTION Sep 30 08:35:47.175 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315ded870
INITIATING CONNECTION Sep 30 08:35:47.193 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e729b0
INITIATING CONNECTION Sep 30 08:35:47.198 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
INITIATING CONNECTION Sep 30 08:35:47.377 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
INITIATING CONNECTION Sep 30 08:36:40.352 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.352 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc312c8dbc0
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31617f290
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316e729b0
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31615a390
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e3bbc0
INITIATING CONNECTION Sep 30 08:36:40.353 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e0cfa0
INITIATING CONNECTION Sep 30 08:36:40.368 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31829f120
INITIATING CONNECTION Sep 30 08:36:40.403 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
INITIATING CONNECTION Sep 30 08:36:40.412 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.565 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
INITIATING CONNECTION Sep 30 08:36:40.595 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.633 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.687 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.708 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:36:40.729 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3183339e0
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3186f07e0
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315a9b630
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3163e7dd0
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172f6e70
INITIATING CONNECTION Sep 30 08:37:33.322 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31616b9d0
INITIATING CONNECTION Sep 30 08:37:33.323 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.336 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e03950
INITIATING CONNECTION Sep 30 08:37:33.462 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.463 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
INITIATING CONNECTION Sep 30 08:37:33.509 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.528 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
INITIATING CONNECTION Sep 30 08:37:33.557 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.598 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.624 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:37:33.646 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
INITIATING CONNECTION Sep 30 08:38:26.315 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31686fa30
INITIATING CONNECTION Sep 30 08:38:26.316 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316fcc7d0
INITIATING CONNECTION Sep 30 08:38:26.316 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3170d8a90
INITIATING CONNECTION Sep 30 08:38:26.317 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc318521490
INITIATING CONNECTION Sep 30 08:38:26.317 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e81b30
INITIATING CONNECTION Sep 30 08:38:26.317 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316fdf410
INITIATING CONNECTION Sep 30 08:38:26.318 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d3a890
INITIATING CONNECTION Sep 30 08:38:26.320 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
INITIATING CONNECTION Sep 30 08:38:26.350 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316728a90
INITIATING CONNECTION Sep 30 08:38:26.350 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.495 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
INITIATING CONNECTION Sep 30 08:38:26.538 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.591 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.619 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.642 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:38:26.666 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
INITIATING CONNECTION Sep 30 08:39:19.257 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31662a980
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3182e6150
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31605c330
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3184b79c0
INITIATING CONNECTION Sep 30 08:39:19.258 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31658f5b0
INITIATING CONNECTION Sep 30 08:39:19.259 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316e03950
INITIATING CONNECTION Sep 30 08:39:19.259 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3160d8c80
INITIATING CONNECTION Sep 30 08:39:19.265 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
INITIATING CONNECTION Sep 30 08:39:19.287 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316073530
INITIATING CONNECTION Sep 30 08:39:19.287 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.420 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
INITIATING CONNECTION Sep 30 08:39:19.457 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.505 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.531 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.552 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:39:19.573 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
INITIATING CONNECTION Sep 30 08:40:11.346 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3161c6e50
INITIATING CONNECTION Sep 30 08:40:11.347 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316becee0
INITIATING CONNECTION Sep 30 08:40:11.348 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31679c620
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3144ad030
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc3158e5b50
INITIATING CONNECTION Sep 30 08:40:11.349 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316728a90
INITIATING CONNECTION Sep 30 08:40:11.363 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315c576d0
INITIATING CONNECTION Sep 30 08:40:11.518 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.518 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
INITIATING CONNECTION Sep 30 08:40:11.548 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.568 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
INITIATING CONNECTION Sep 30 08:40:11.597 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.638 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.660 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:40:11.683 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
INITIATING CONNECTION Sep 30 08:41:06.173 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318297540
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc314144080
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d435e0
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3167306a0
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31680f3e0
INITIATING CONNECTION Sep 30 08:41:06.175 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3170d8a90
INITIATING CONNECTION Sep 30 08:41:06.197 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31671e630
INITIATING CONNECTION Sep 30 08:41:06.223 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.223 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
INITIATING CONNECTION Sep 30 08:41:06.376 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.396 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
INITIATING CONNECTION Sep 30 08:41:06.431 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.475 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.503 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:06.527 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
INITIATING CONNECTION Sep 30 08:41:59.159 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.160 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e16c90
INITIATING CONNECTION Sep 30 08:41:59.160 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3161e71f0
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc315f45120
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3170d94c0
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3174bc990
INITIATING CONNECTION Sep 30 08:41:59.161 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31820b7d0
INITIATING CONNECTION Sep 30 08:41:59.174 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162884e0
INITIATING CONNECTION Sep 30 08:41:59.189 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:41:59.189 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.344 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:41:59.363 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.409 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.430 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.450 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:41:59.471 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
INITIATING CONNECTION Sep 30 08:42:51.209 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31a613830
INITIATING CONNECTION Sep 30 08:42:51.210 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3168ae8d0
INITIATING CONNECTION Sep 30 08:42:51.210 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3161d6110
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315de6190
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316482400
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.211 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31829f120
INITIATING CONNECTION Sep 30 08:42:51.224 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3159e76e0
INITIATING CONNECTION Sep 30 08:42:51.372 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:42:51.372 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.402 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
INITIATING CONNECTION Sep 30 08:42:51.421 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.466 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.492 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.514 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 08:42:51.536 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc315d40d90
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc315ad1930
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc316c27e30
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315adf230
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d49010
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159a1ea0
INITIATING CONNECTION Sep 30 09:43:23.246 -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc318691eb0
INITIATING CONNECTION Sep 30 09:43:23.250 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
INITIATING CONNECTION Sep 30 09:43:23.311 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e1b2d0
INITIATING CONNECTION Sep 30 09:43:23.311 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.427 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
INITIATING CONNECTION Sep 30 09:43:23.471 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.524 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.547 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.574 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 09:43:23.598 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
INITIATING CONNECTION Sep 30 10:06:17.592 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
INITIATING CONNECTION Sep 30 10:06:17.596 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3174e7bd0
INITIATING CONNECTION Sep 30 10:06:17.598 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315e08640
INITIATING CONNECTION Sep 30 10:06:18.674 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.483 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318462600
INITIATING CONNECTION Sep 30 10:06:19.539 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162d4270
INITIATING CONNECTION Sep 30 10:06:19.564 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
INITIATING CONNECTION Sep 30 10:06:19.582 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.653 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.674 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.725 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:06:19.747 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
INITIATING CONNECTION Sep 30 10:07:19.496 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
INITIATING CONNECTION Sep 30 10:07:19.523 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3144bad30
INITIATING CONNECTION Sep 30 10:07:19.531 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.534 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172b7640
INITIATING CONNECTION Sep 30 10:07:19.550 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315cbb960
INITIATING CONNECTION Sep 30 10:07:19.626 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315842910
INITIATING CONNECTION Sep 30 10:07:19.665 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
INITIATING CONNECTION Sep 30 10:07:19.715 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.805 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.854 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.892 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:07:19.915 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
INITIATING CONNECTION Sep 30 10:08:19.527 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
INITIATING CONNECTION Sep 30 10:08:19.553 -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3162e8510
INITIATING CONNECTION Sep 30 10:08:19.555 -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315ac9950
INITIATING CONNECTION Sep 30 10:08:19.564 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.582 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3146b1020
INITIATING CONNECTION Sep 30 10:08:19.685 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3163d82c0
INITIATING CONNECTION Sep 30 10:08:19.705 -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
INITIATING CONNECTION Sep 30 10:08:19.756 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.800 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.852 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.876 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
INITIATING CONNECTION Sep 30 10:08:19.898 -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0

Problem with Java Script after upgrade from BW 3.5 to BI7

Dear Colleagues,
We're facing the issue with Java Script after upgrade of BW 3.5 to BI7.
Just after update we checked the basic functionality and it occured that some of web templates that use Java Script don't work. They generate seelction screen, but after selection the screen becomes blank without any error messages.
We're currently stucked since web templates weren't converted to BI7 version so they should work exactly as before the upgrade.
We compared the Java code with other environment that was not upgraded - it's perfectly the same.
The only explanation that comes to my mind is that some Java Script settings on the server level were changed during the upgrade but I have no idea where I can check that.
Thanks in advance for any suggestions,
Andrzej Bobula

Hi Deepu,
Thanks, it was great to read your reply and then few minutes later talk to you live on SDN Day!
Unfortunately, http cache clean-up did not help. But there is another funny thing I found - for exactly the same 3.5 webtemplate html code returned from WebAS 3.5 was different then from 7.0.
Unfortunately, this editor does not allow to paste complete code, even in CODE brackets, but here are main differences:
<b>3.5</b>
if (navigator.appName == "Microsoft Internet Explorer")
<frame src="/sap/bw/BEx?SAP-LANGUAGE=E&PAGENO=1&REQUEST_NO=1&CMD=GET_TEMPLATE"
name="Content">
and
<b>7.0</b>
if (navigator.appName.indexOf("Microsoft Internet Explorer")!=-1)
<frame src="/sap/bw/BEx?SAP-LANGUAGE=E&PAGENO=8&REQUEST_NO=0&CMD=GET_TEMPLATE"
name="Content" 0nLoad="javascript:loadTitle()">
(I intentionaly put 0 i/o o in 0nLoad, otherwise Forum's editor does not accept the text.
How about SAP's claim that technical upgrade from 3.x to 7.0 changes nothing?
Regards,
Vitaliy

Problem with field catalog after upgrade from 4.0

Hi experts,
We have recently upgraded from CRM 4.0 to 5.2.
I am now experiencing a problem with generation of a transport request for field catalog in transaction CTFC_CRM. I can generate the field catalog without errors.
The problem is that when I want to create the transport request in our dev system a pop up appears saying "Create object directory entry". Here I have to enter a package for some of the fields in the field catalog. The special thing is that the fields are not custom fields but rather SAP standard fields (using standard data elements). For example field BZIRK.
These are SAP standard fields but they are not standard in the field catalog. In 4.0 I did not get this prompt but this has apparently changed from 5.0.
What do I do? I guess if I need to create the objects I will need to use an SAP standard package. But how do I know what package to use?
Any comments or suggestions will be highly appreciated.
Best regards,
Anders

Hi,
If you did just install database, then you use Embed PL/SQL Gateway.
See this guide
Upgrading Oracle Application Express in Oracle Database Express Edition
I think you have not run step 5 script apxldimg.sql
Regards,
Jari

Problem with workflow manager after restore from dump

Hi,
I updated my development environment from my dump production (restore full from dump). I restore my applicative schemas and aslo the schema owf_mgr which is used by my application.
I've got a problem with three views that I cannot recompile....
WF_USERS, WF_ROLES, WF_USER_ROLES
The errore message is ORA-00942 : Table or view doesn't exist.
How can I solve my issue ? Do I miss something
Thanks for your help !

Which version of Oracle Workflow Standalone do you use?
The views are based on workflow tables such as WF_LOCAL_USERS, WF_LOCAL_ROLES, WF_LOCAL_USER_ROLES and DBA dictionary DBA_USERS. Please check if these are available in OWF_MGR schema.
Hope this helps.
Vijay

Problems with SCXI-1000 after update from Labview 5.1 to LabView 6

I'm using a SCXI-1000 board to readout temperatures from some Pt-100 sensors. The analog signal going into the SCXI-1000 is correct. The reading by LabView program is not. The SCXI-1000 is connected to the PC via a PCI-1200 bus. I've used this setup for some time with LabView 5.1. Here it worked nicely. Recently I upgraded to LabView 6. Now the readout is not giving the proper values. When I reinstalled Labview 5.1 it was all OK again. When using LabView6 do I need to calibrate of configure the SCXI-1000 for my temperature readout? Are there any known problems with upgrading from LabView5 to Labview6? How can I see which analog values are being read by the SCXI-1000 and to which values they are converte
d? Hopefully you can help me.

Upgrading from different versions of LabVIEW shouldn't be a problem; I would suspect different versions of NI-DAQ first. Make sure you use the Measurement and Automation Explorer (MAX) to configure your card.
To see if it's a driver update issue, when you use the LabVIEW 6 installation CD, choose custom install and don't upgrade your drivers. You may have to browse into your LabVIEW 5 directory and use copies of the VIs from there.

Problem with Billing Engine after upgrade from CRM 5.0 to CRM 7.0

Hello together,
The system of our customer has been upgraded from CRM 5.0 to CRM 7.0. After that some problems occurred regarded the billing.
In the Billing Due List a dump occurs when clicking on an item and then on conditions
Dump message: No function module can be found named "/1BEA/CRMB_DL_PAR_O_DERIVE" however.
(Other classes are new generated after the upgrade)
During the Analysis we looked to the billing engine navigator:
In the Billing Engine Navigator (Transaction: BEFN_F1) the Generation Log shows the following:
We have re-generated the Object PAR in CRMB->DL->Feature->PAR. But this shows the above displayed error message. How can we add value to the Placeholder?
Another question is which impacts does it have if we regenerate the complete billing engine for CRMB with transaction BEA_CONFIG_F1 (Configure Application)?
BR, Anne

Hi Nawanit,
we checked the key figure settings and categories. Everything is maintained correctly.
Since we work with MRP areas we also checked the "Global Parameters and Default Values for MRP Areas" in APO Customizing: The "Default values for Stock Transfer Documents" is set to "1" = Stock Transport Requisitions for MRP Areas.
BUT: When I try ot change this indicator I get the following message no. /SAPAPO/MRPA000:
"Process. w. stock transp. requisitions is not supported in standard sys. The process with stock transport requisitions will be supported as of SAP R/3 Enterprise Core Release 4.70 with SAP R/3 Enterprise Extension Set 2.0. ".
As far as we work with ECC 6.0, EHP4 this message makes no sense.
Does anyone have another idea?
Thanks
Jan

Problem with method action after migrating from TP2 to TP4

Hi,
we are migrating our application (ADF Faces, ADF BC) from TP2 to TP4. We have encountered several problems.
The biggest that we could not solve is as following:
In our View Object's RowImpl.java classes we have method void refreshLOVAccessorQueries(). In a number of View Objects that method is placed in client interface. In pageDefs of jspx pages that are bound to that View Objects we have method action like
<methodAction IterBinding="TeeCronTtVOIterator"
id="refreshLOVAccessorQueriesCron"
InstanceName="bindings.TeeCronTtVOIterator.currentRow"
DataControl="TradingAppModuleDataControl"
RequiresUpdateModel="true" Action="invokeMethod"
MethodName="refreshLOVAccessorQueries"
IsViewObjectMethod="false" IsLocalObjectReference="true"/>
and invoke action like
<invokeAction id="refreshCronLOVs" Binds="refreshLOVAccessorQueriesCron"
Refresh="prepareModel"
RefreshCondition="#{!requestContext.postback and empty bindings.exceptionList}"/>
When we are accessing such a jspx page the application rases error:
"Method bindings.TeeCronTtVOIterator.currentRow.refreshLOVAccessorQueries() not supported "
In TP2 everything worked fine. Now in TP4 for some VO that refresh is OK and for others just mentioned error is thrown. Confusing is that all View Objects and their java classes are created in the same manner and they are almost identical, and this counts for pageDefs too.
What could be the reason of all this?
Second thing is that in adfc-config.xml in backing bean defs we have managed-property like:
<managed-bean>
<managed-bean-name>regionBacking</managed-bean-name>
<managed-bean-class>app.view.backing.RegionBacking</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>bindings</property-name>
<value>#{bindings}</value>
</managed-property>
</managed-bean>
JDeveloper warn us about that with: ' EL token bindings" is unknown '. Why is that? It looks that everything connected with that managed property works fine.
Another problem is not severe but unpleasant
After migration to TP4 nothing (not one element) is visible (shown) in the design view.
The structure of the pages is similar as in the StoreFrontDemo and it shows just fine in TP2.
Thanks!!!

Thanks Frank,
but working from beginning is to much work so, we have solved it in another way.
Regard to first problem we discovered that it is happening only when there is no Rows in iterator for which we are invoking action. In invoke action we have changed refresh property to default value and the problem is solved.
Second thing is warning that has no other effect so we will ignore it.
About third problem, when we create new working copy of application in JDeveloper without system11.1..... directory, JDev works fine and all jspx pages are shown in design view. After some work, due to undiscovered reason design view is lost... What could cause this?
Maxa

Problems with wifi network after waking from sleep

I have recently started using a new wifi network and have had some problems connecting to it. When i first tried to connect it gave a message that said "An error occured while trying to join". After some trial and error, I found that I could connect by going to network preferences, clicking "Assist me...", then "Diagnositcs...", clicking the AirPort dot then continue, then clicking on the network name and continue, then it prompts for a password, but there isnt one so i just pushed continue and all of a sudden it connected. I figured it was functional now, but after waking it from sleep mode, the error message popped back up. The only way I know to connect is through that annoying diagnostics path... What is the Problem, is it the computer or the router or the settings on the admin computer? (by the way, I don't know what kind of router it is, but its definantly not an apple airport)

Sorry to drag this back up, but I may have found the source of the problem, I just need the solution. When I first created settings for the network, it automatically "detected" that the security was WPA2 Enterprise, and knowing there was no password, I just pushed join and it saved it that way. When I go through diagnositics as described before, it lists WEP as the encryption. I had a friend with almost the same problem, but in tiger. They were able to fix it by changing the encryption on the login screen that comes up when you click on the network name from the menu bar. But that screen no longer exists in Leopard, it only goes by previous settings. How do I change the encryption in settings, I'm sure it will fix the problem...

Problem with some features after changing memory c...

My N2690 cannot work with 2GB. Right now most of the functions like; Ovi, Life tools, Web browser is refusing to open.
Community Manager note: this post has been removed from an unrelated thread and the subject line changed to reflect the nature of the question.

Problem Solved!
I discovered how to locate earlier versions - I my case had to go back 3 versions of HotKey fix. For my laptop, T60 2007-49U, the latest version is 3.86.0000 - I found that 3.84.2000 restored both audio & brightness levels on screen display.
One point though, my previous display was a series of green bars - the new display is a black bar with white characters... no real problem - at least the On Screen Display is back!
Thanks for your help in suggesting I try previous versions.

Problems with Canon ip4200 after upgrading from panther to tiger.

Hello
I have recently purchased a lovely new imac 24", everything is great apart from my my printer which is now printing pictures with a lovely magenta cast over all my photos.
From googling around I think it might something to do with having a double printer profile on? But the actually printer doesn't seem to have much options to play around with.
If anyone has any idea of what's happening or how to sort this out I would really appreciate it as after MANY hours of googling I am now totally perplexed!
Thanks
Rosie

Hello Rosie,
For starters, please ensure you have the latest driver for the iP4200 installed. You can get this from the Canon Europa web site. The version is 4.8.3. With the new driver available, follow this procedure to remove any previous version before installing this later version.
1. Open Printer Setup Utility, delete the iP4200 queue and then click on Printer Setup Utility and select Reset Printing System.
2. Close the Printer Setup Utility.
3. Go to Library > Printers > Canon and delete the contents of the BJPrinters folder.
4. Go to Library > Receipts and delete the file Canon iP4200 xxx.pkg
5. Empty the Trash
6. Restart the Mac
7. Install the latest version of the Canon driver (4.8.3)
8. Once the driver installation is complete, go to Applications > Utilities and open Disk Utility. Run the Repair Disk Permissions option.
9. Open Printer Setup Utility and click Add.
10. Select the Default Browser view and select the Canon printer connected via the USB port. The Print Using menu should automatically change to Canon IJ Printer.
11. Click Add to add the printer.
With this latest driver installed, print your photo and check your output. If there is still a magenta tinge, open the driver settings and select Quality & Media. Try a different media type, such as Photo Paper Pro, and also set the Print Mode to the photo setting. If you are printing from iPhoto, then open Color Options and ensure you have the Color Correction set to BJStandard.
If you are printing from PhotoShop, then open Color Options and ensure that Color Correction is set to ColorSync so that the ICC profile associated with the paper type selected above is used.
If you want to check the gamut of the respective paper types/profiles available to the printer, you can open the ColorSync utility and expand Others > /Library/Printers/Canon/BJPrinter/...Here you will see the available profiles for the respective Canon paper stocks and their colour gamuts. The MP settings are Matt Paper, PR is Photo Paper Pro and SP is Photo Paper Plus Glossy.

Problem with some queries after migration from MS Access

Hi everyone!
We've just finished a migration from a MS Access database and we notice some errors when running some queries like :
Query1:
SELECT A.field1, A.field2, B.field1 as FieldTmp
FROM A,B
where (B.field1 <=10);
Query2:
SELECT Query1.field1, Query1.field2, Query1.FieldTmp
FROM Query1 LEFT JOIN Table3
ON (Table3.field1 = Query1.Field2) AND
(Table3.field5 = Query1.FieldTmp)
WHERE ((Table3.field5) Is Null)
ORDER BY Query1.field1, Query1.FieldTmp;
The Query1 runs as expected, but when I try to run the Query2 I got a ORA-00904 error message. If I remove the (Table3.field5 = Query1.FieldTmp) statement or modify to compare with another field (as instance, field2) everything goes fine.
If I modify the first query to a make-table query, the Query2 request runs as desired too.
Is there anything that we can do to keep the queries statement as it is when using the MS Access DB?
Thanks in advance,
Elaine Viel Denadai

Hi Turloch! Thanks for your help!
Those SQL Statements were extracted from the MS Access application that we will continue to use to access the data , now on an Oracle Database.
I don't know what I can do to make this kind of statements works as it is on Access database. The first query, that I called Query1 works fine on Oracle, I just mentioned it because the 2nd Query , named Query2, use it.
I'm not able to understand why when I change the 1st. query to a "make-table" query the Query2 works as desired, but if I keep the Query1 and Query2 as it is on the MS Access Application I got the ODBC error message and the ORA-00904 error message , related (I think!) to the FieldTmp field used on the LEFT JOIN statement (AND).
As I told before, if I change the AND clause to compare to another field, as instance, field1 :
FROM Query1 LEFT JOIN Table3
ON (Table3.field1=Query1.Field2) AND
(Table3.field5 = Query1.Field1)
it works.
Please, is there anything that I can do to keep the MS Access Application unchanged?
Oracle = 8.1.6
Oracle ODBC Driver = 8.1.6.4
Oracle Migration Workbench = 1.3.1
Thanks in advance,
Elaine Viel Denadai

Problems with ALV - Excel after changing from 640 to 710

Similar Messages

Maybe you are looking for