B2B with ECC 6.0 backend error

Hi,
I receive the error "No customer found with customer number" when I try to checkout, with my shopping cart.
This is an internal POC. I've configured the UserManagement as 'R3_SU01User'. I've configured r3standardpitrex in B2B XCM configuration. I've maintained Shopadmin as well.
I know the problem has to do with "security". I've created a user on SU01, but if I add a customer number (KNA1) to the Goto>References button, I can not log onto B2B. It gives me the following error:
- A serious system error has occured
- The shoplist read from buffer if empty
-Contact the administrator
If I remove the KNA1 entry, I can log onto the shop. I am able to browse my catalog & add to the shopping basket...I just can't create a sales order because I'm not associated with a customer.
ECC 6.0 Backend
NetWeaver Java 7.0
Thanks for any help!

Please check note [1303890|http://service.sap.com/sap/support/notes/1303890]
Regards
Mark
Edited by: Mark Foley on Aug 20, 2010 4:31 PM
Edited by: Mark Foley on Aug 20, 2010 4:31 PM

Similar Messages

Clariffications in MM SUS Scenario with ECC 6.0 backend and SRM 5.0

Dear Team,
We are implementing MM SUS Scenario with ECC 6.0 backend and SRM 5.0
We need to following clarifications
1 Once we create ASN in SUS, how to cancel the ASN. We are not able to see cancel button for ASNs
2 When we create GRN in ECC against the inbound delivery and perform Return Delivery, this Return Delivery is getting updated in SUS. But the ASN status is not changing to canceled. We are not able to perform new ASN for this. Also invoice is being allowed for these ASNs. How to control the same.
Request your inputs please
Regards,
Ravi

HI can you tell me how you get it solve?
thanks in advance.

SAP SRM 7.0 with ECC EHP 4 components to execute scenario

Hi All,
I am new to SAP SRM 7.0.Could you please let me know that what are all the components needs to be in place to execute the technical scenarios and business scenarios.I had an hands on experience on SAP SRM 5.0 with ECC 6.0 backend.
Some where i read that there are lot of configuration changes when we integrate SRM 7 with ECC EHP 4.Do we need to have PI 7 for executing Centralized contract and plan driven procurement scenario?Please guide me to have some exposure towards higher version.Thank you in advance.
Best Regards,
praveen

Hello,
You can refer the INSTALLATION AND UPGRADE INFORMATION , Master guides etc maintained at the below mentioned location which will answer all your query's here.
Goto URL http://service.sap.com/srm-inst and then navigate to SAP SRM --> SAP SRM Server 7.0 .
Best Regards,
Rahul

SAP Cloud For Customer With ECC Integration Material Replication Content Error

Hi Experts,
When i replicate the Material from ECC to Cloud With Sale Org Data if getting error as shown below.
When we are replicate the Material without Sales Org Data its working but when we pass the data with Sales Org it gives error .
Errors reported by application: "Activation not permitted; cross-process category missing", "Error while processing inbound third party communication"
and the Payload for this error attached in the file
Kindly anyone have idea about this error share your inputs.
Many Thanks
Mithun

Hello Mithun,
The reason for this error is in the definition of the Material in the Cloud:
For the Sales data it is required that a product category is assigned to the Material.
This product category must belong to a product category hierarch with the category code "Cross-Process".
This is not required for the basic data i.e. without the Sales data.
Therefore you can transfer the Material data w/o Sales data and no error occurs.
HTH,
Horst

#DATA Sync & # CONTEXT error in BI 4.1 with ECC 6 environment

I am getting the #DATA Sync & # CONTEXT error in BI 4.1 with ECC 6 environment. When i am adding Excel Sheet as asecondary source for BO report am getting this error. because of below,
Ecc data
Profit center -- 000100
Fiscal Year --- 2,014
Posting Period - 1 to12
Amount 2000
Excel Data
Profit center -- 000100
Discharge Date --- Q1 2014, Q2 2014,
Discharge Port --- Excelerate or Expediate, etc
I ahve created report Using ECC Data like, Profit center,Fiscal Year,Posting Period and Amount.
Now i want to Add from Excel Discharge Date and Discharge Port am getting the #DATA Sync & # CONTEXT error or Imcompatible object.
because i am anot able to merge these objects with ECC Objects. Can anyone suggest me what i can do to achieve this?
Cheers
Murali Durairaj

Hi
Have you created two different data providers (one for ECC, another for Excel data)in
the webI report,
If yes -- check whether able to see data sample in the Excel data provider
Run the WebI Report -- Design Mode -- Edit -- Select the Excel Data Provider --
Check able to see the Data Sample data whichever there in the excel sheet.
If you are able to see the Sample data…then merge common objects (able to merge
only if both the objects have same data types.) then check the data in the
report.

Lync 2013 Error 31055 ,31059 LS Call Park Service, The database being used by Group Pickup is not the appropriate version and There was a problem communicating with the Group Pickup backend database.

Hello
I have Lync 2013 and 2010 , still i didn't finish my migration completely from 2010 to 2013 .this is coexistence environment that contains both Lync Server 2010 and Lync Server 2013 .
There was no error's in my lync 2013 front end and back end server's and every thing was fine, yesterday I installed windows updated AND CU for my lync 2013 front end and backend server's .
later on after restarting both the front end and the back end server's i start having hundred's of these error's related to "LS Call Park Service".
so any advice for these issue ? and what is the effect for these error .
below is the error I got .
The database being used by Group Pickup is not the appropriate version.
The database is not the correct version:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Expected... SchemaVersion: 1, SprocVersion: 1, UpgradeVersion: 2
Actual... SchemaVersion: 0, SprocVersion: 0, UpgradeVersion: 0
Cause: The database has not been upgraded.
Resolution:
Upgrade the database to CU1.
==============================================================
There was a problem communicating with the Group Pickup backend database.
There were problems accessing SQL server:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
Error code: -2146232060
Error number: 229
Cause: This may be caused by connectivity issues with the backend database.
Resolution:
Check if SQL backend is running and accepts connections from Group Pickup.
=============================================================================
Kind Regards
MK

Hello
thanks Holger for u r replay .
due to the Microsoft article about the cu :
I run only :
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose
Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 and in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
Install-CsDatabase -CentralManagementDatabase command to apply the changes.
here is what I get on my power shell after i run the command : "WARNING: Warning: Failed to execute batch --"
PS C:\Users\MK> Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn HQ-LYNC2013-BE.MyDomain -Verbose
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.xml".
VERBOSE: Install databases required by Lync Server role(s).
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
VERBOSE: Assigning "BackendStore:BlobStore:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:BlobStore:DbPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:DbPath" to F:\CsData
VERBOSE: Installing "BackendStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
Checking state for database rtcxds.
State of database rtcxds is DbState_RequiresMinorUpgrade.
Database rtcxds set to mode Restricted.
Dropping all procedures, functions and views from database rtcxds.
Executing RtcDb.sql...
Adding master role...
Setting owner for database rtcxds to sa.
Creating login MyDomain\RTCHSUniversalServices.
Creating user MyDomain\RTCHSUniversalServices.
Creating Schema MyDomain\RTCHSUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCHSUniversalServices to role ConsumerRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ConsumerRole.
Adding account MyDomain\RTCHSUniversalServices to role ReplicatorRole.
Adding account MyDomain\RTCHSUniversalServices to role PublisherRole.
Adding account MyDomain\RTCUniversalServerAdmins to role PublisherRole.
Setting database version: Schema Version 15, Sproc Version 13, Update Version 2.
Setting the database rtcxds to multi user mode.
Database rtcxds is set to multi user mode.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcshared.
Database created by script "RtcSharedDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-BackendStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_01].log"
VERBOSE: Installing "ABSStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
Checking state for database rtcab.
State of database rtcab is DbState_RequiresMinorUpgrade.
Database rtcab set to mode Restricted.
Dropping all procedures, functions and views from database rtcab.
Executing RtcAbTypes.sql...
WARNING: Warning: Failed to execute batch --
-- Copyright (c) Microsoft Corporation. All rights reserved.
exec sp_addrole N'ServerRole'.
Executing RtcAbDb.sql...
Setting owner for database rtcab to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 42, Update Version 3.
Setting the database rtcab to multi user mode.
Database rtcab is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ABSStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_20].log"
VERBOSE: Installing "ApplicationStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
Database created by script "RgsConfigDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
Database created by script "RgsDynDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
Checking state for database cpsdyn.
State of database cpsdyn is DbState_RequiresMinorUpgrade.
Database cpsdyn set to mode Restricted.
Dropping all procedures, functions and views from database cpsdyn.
Executing CpsDyn.sql...
Setting owner for database cpsdyn to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCComponentUniversalServices to role ReadWriteRole.
Adding account MyDomain\RTCUniversalServerAdmins to role ReadWriteRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ReadOnlyRole.
Setting database version: Schema Version 1, Sproc Version 1, Update Version 2.
Setting the database cpsdyn to multi user mode.
Database cpsdyn is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ApplicationStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_37].log"
VERBOSE: Installing "ArchivingStore" on HQ-LYNC2013-BE.MyDomain\arc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
Database created by script "ArchivingDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ArchivingStore-HQ-LYNC2013-BE.MyDomain_arc-[2014_11_13][14_35_51].log"
VERBOSE: Installing "MonitoringStore" on HQ-LYNC2013-BE.MyDomain\mon, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
State of database LcsCDR is DbState_RequiresMinorUpgrade.
WARNING: The database LcsCDR being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf. Supplied path will be ignored.
WARNING: The database LcsCDR being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf. Supplied path will be ignored.
Database LcsCDR set to mode Restricted.
Dropping all procedures, functions and views from database LcsCDR.
Executing CdrDb.sql...
Setting owner for database LcsCDR to sa.
Creating login MyDomain\CSAdministrator.
Creating user MyDomain\CSAdministrator.
Creating Schema MyDomain\CSAdministrator.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Adding account MyDomain\RTCComponentUniversalServices to role ReportsReadOnlyRole.
Adding account MyDomain\CSAdministrator to role ReportsReadOnlyRole.
Setting database version: Schema Version 39, Sproc Version 82, Update Version 2.
Setting the database LcsCDR to multi user mode.
Database LcsCDR is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing CdrJobs.sql...
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.QoEMetricsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
State of database QoEMetrics is DbState_RequiresMinorUpgrade.
WARNING: The database QoEMetrics being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf. Supplied path will be ignored.
WARNING: The database QoEMetrics being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf. Supplied path will be ignored.
Database QoEMetrics set to mode Restricted.
Dropping all procedures, functions and views from database QoEMetrics.
Executing QoEDb.sql...
Setting owner for database QoEMetrics to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 90, Update Version 1.
Setting the database QoEMetrics to multi user mode.
Database QoEMetrics is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing QoEJobs.sql...
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-MonitoringStore-HQ-LYNC2013-BE.MyDomain_mon-[2014_11_13][14_35_51].log"
VERBOSE: No changes were made to the Central Management Store.
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
WARNING: "Install-CsDatabase" processing has completed with warnings. "5" warnings were recorded during this run.
WARNING: Detailed results can be found at
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
PS C:\Users\MK>
I hope some one can confirm no issue with what I did ??
Kind Regards
MK

Test failed BAM-00553 Error when integrating B2B with BAM

Hi,
We used the following link to integrate B2B with BAM.
Oracle Fusion Middleware User’s Guide for Oracle B2B 11g.
Monitoring Instance Message Data With Oracle BAM
http://docs.oracle.com/cd/E15586_01/integration.1111/e10229/b2b_bam.htm#CFHJIBHC
server is running on linux machine..
we got the following error when we create Enterprise Message Sources and try to start it.
Name: B2B_EMS
Owner: weblogic
Created: 1/23/2012 9:02:17 AM
Last modified: 1/25/2012 8:37:43 AM
Status: Test failed - BAM-00553: Resources start operation for destination jndi/jms/bamqueue failed.
Initial Context Factory: weblogic.jndi.WLInitialContextFactory.
JNDI Service Provider URL: t3://soahost:9001.
Topic/Queue Connection Factory Name: jms/BAMAQQueueCF.
Topic/Queue Name: jndi/jms/bamqueue.
JNDI Username: .
JNDI Password: .
JMS Message Type: TextMessage.
Durable Subscriber Name (Optional): .
Message Selector (Optional): .
Data Object Name: /Samples/B2B/B2BDO.
Operation: Insert.
Batching: No.
Transaction: No.
Start when BAM Server starts: Yes.
JMS Username (Optional): .
JMS Password (Optional): .
Please suggest with the solution, also provide with any of other sample which defines B2B and BAM Integration.
Regards
Shankar

Hi,
We used the following link to integrate B2B with BAM.
Oracle Fusion Middleware User’s Guide for Oracle B2B 11g.
Monitoring Instance Message Data With Oracle BAM
http://docs.oracle.com/cd/E15586_01/integration.1111/e10229/b2b_bam.htm#CFHJIBHC
server is running on linux machine..
we got the following error when we create Enterprise Message Sources and try to start it.
Name: B2B_EMS
Owner: weblogic
Created: 1/23/2012 9:02:17 AM
Last modified: 1/25/2012 8:37:43 AM
Status: Test failed - BAM-00553: Resources start operation for destination jndi/jms/bamqueue failed.
Initial Context Factory: weblogic.jndi.WLInitialContextFactory.
JNDI Service Provider URL: t3://soahost:9001.
Topic/Queue Connection Factory Name: jms/BAMAQQueueCF.
Topic/Queue Name: jndi/jms/bamqueue.
JNDI Username: .
JNDI Password: .
JMS Message Type: TextMessage.
Durable Subscriber Name (Optional): .
Message Selector (Optional): .
Data Object Name: /Samples/B2B/B2BDO.
Operation: Insert.
Batching: No.
Transaction: No.
Start when BAM Server starts: Yes.
JMS Username (Optional): .
JMS Password (Optional): .
Please suggest with the solution, also provide with any of other sample which defines B2B and BAM Integration.
Regards
Shankar

Error Log in E-Commerce CRM B2B with SU01 user

Hi guys,
I´m configured ISAUser Admin with value "CRM_SU01UserID" for component usertype in http: //server:port/isauseradm/admin/xcm/init.do.
Also I´m configured my scenario B2B with value "CRM_SU01UserID" in component usertype.
In rute Customer Relationship Management  E-Commerce  Basic Settings for E-Commerce  Internet User Internet User Settings  Set B2B Internet User, I´m configured Only use Internet User (SU01), howewer when I access my shop in http://server:port/b2b/b2b/init.do, system display error bold " Logon is invalid; check your entries "bold
The user SU01 has assigned to a business partner in CRM.
Do you have any idea about this error?
Regards,
Lyda

Cree a new role "Internet User" for my contact person. This internet user are associated with my USER ID. Now, i access with mi userID and my pass changed (my new pass for Internet user"

Error : There was a problem communicating with the Group Pickup backend database.

Hi ,
I found this error in Event viewer for Every 2 min on lync server 2013 :
There was a problem communicating with the Group Pickup backend database.
There were problems accessing SQL server:
Connection: Data Source=(local)\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
Error code: -2146232060
Error number: 229
Cause: This may be caused by connectivity issues with the backend database.
Resolution:
Check if SQL backend is running and accepts connections from Group Pickup.
what can i do ?

Hi,
Did you solve the issue with the help of the suggest Anthony provided above?
If the issue persists, please check if you update the latest vesion of Lync Server 2013. If not, please update it, make sure after install the update for all FE Servers,
then make sure to update BE Server as well. Then rerun Step 2 Setup or remove Lync Server Components.
Here is a similar case may help you:
https://social.technet.microsoft.com/Forums/lync/en-US/3b616e51-93ad-430a-aa93-57c2fd19e0f6/call-pickup-db-issue-after-cu1-update-to-lync-2013-enterprise?forum=lyncdeploy
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

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: crm production is not sync with ecc production

Hi Middleware Experts,
I am facing one issue, "CRM Production is not sync with ECC production". I have searched alot but couldn't find any relevant material. Please let me know the steps to rectify this error.
Thanks,
Vsh

Hello,
Sorry forget the last note I suggest you,
Please check the following links might be helpful
http://help.sap.com/saphelp_crm70/helpdata/EN/28/370123814711d3ad6b0000e8a5bd28/frameset.htm
http://help.sap.com/saphelp_crm70/helpdata/EN/46/57605601a208e7e10000000a114a6b/frameset.htm
thanks
Willie
Edited by: Willie Musa on Jul 6, 2011 10:43 AM

Central contract in SRM 7.0 with ECC 6.0

Hi
We are using SRM 7.0 with ECC 6.0
When we create contract in SRM 7.0 & Trying to distribute to Backend as Contract, It is showing error in BBP_PD as below
HEADER I1015 Awaiting Approval
HEADER I1021 Created
HEADER I1038 Complete
HEADER I1141 Released
HEADER I1180 Document Completed
HEADER I1193 In Distribution
HEADER I1195 Distribution Incorrect
0000000001 I1143 Item is Active
Badi BBP_DETERMINE_LOGSY is activated to define backend system
No IDOC is also generated.
No errors in MOnitor also
Not sure what is message type needs to define & what else is needed
Regards,
NNK

HI
Need to do following
1. Keep conidtion types in ECC & SRM same for contract.
2. Also Add message types BLAORD & COND_A manually in ECC in WE20.
Then only it works
Regards,
NNK

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.

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

BPM_DATA_COLLECTION fails with (Output device "" not known) error

Hi all,
I have an issue with Output BPM_DATA_COLLECTION_1 job in the satellite system failing with 'Output device "" not known error. Since it is collecting data for Solution Manager system why does is it trying to find an output device.
It did not fail before and now I added another key figure (custom one) which is done the same way the other custom monitors are done in "Z_BPM_ECU_COLLECTOR" report and then in /SSA/EXM program, but the collector job started to fail.
Also, for some reason there are two BPM_DATA_COLLECTION jobs, one is BPM_DATA_COLLECTION_1 and the other is BPM_DATA_COLLECTION_2. _1 runs every 5 min and _2 is less frequent. They both seem to runt the same job which is /SSA/EXS. Why are there two jobs scheduled from solution manager in my satellite system?
Thank you very much for your help!

I am experiencing this same issue in our ECC 6.0 system. We currently have ST-A/PI release 01M_ECC600 level 0001 applied to our system. These jobs finish successfully in SM37, but I'm seeing the same error messages in our system logs (SM21).
When I try to update the output device that is associated with these jobs, the user ID running the jobs is not valid since it's user type is Communication Data.
Does anyone know if it ok to change the user for this job? Should it be run by DDIC? I believe the jobs were created automatically when we applied ST-A/PI release 01M_ECC600 level 0001.

B2B with ECC 6.0 backend error

Similar Messages

Maybe you are looking for