DNL_CUST_PROD0 & SYSFAIL in backend

Hello,
I've got a problem when I want to replicate material group from my backend.
In fact our SRM is linked to 3 backend, I can replicate material group for 2 of them but for the third one I got an error message on SMQ1 in the backend with a SYSFAIL.I've checked all the customizing table CRM*...and everything is OK and the same as the 2 others backend.
Maybe the problem came from a custo specific in the backend...do you have any idea?
Thanks a lot,

Hello,
Thanks for the answer but I run the program BBP_PRODUCT_SETTINGS_MW but it doesn't work better.
For information we are on SRM Server 5 (Version with SRM consumer), classic scenario.
The problem seems that in SMQ1 in our backend, it look likes if the the system try to call it himself...

Similar Messages

Material Replication from Backend: DNL_CUST_PROD0 is stuck in SMQ2

Hi Experts,
I am getting this error while running R3AS for DNL_CUST_PROD0 adapter and checking the SMQ2 is getting into SYSFAIL status. The detail error says "Incorrect parameter with CALL FUNCTION" for Function Module BAPI_CRM_SAVE
Even, adapter DNL_CUST_PROD1, is getting SYSFAIL error in SMQ1. The detail error is Filter criteria Invalid on function module CRS_FIRST_DOWNLOAD_TRIGGER
Please suggest
Thanks
Rakesh

Hi
Here is the possible solution. Ii was facing this issue however was able to do.
First goto SMOEAC and check wheather CRM is connected with correct site attribute or not.
Then check all the RFC connection.
delete all the existing queues and R3AM1
now goto R3ac3
refresh all the Load and try again i Hope it should work and also maintain
system landscape in technical basic setting in SRM GUI(SPRO)
Regards
saurabh

Service replication Dump SYSFAIL Invalid subfield access: Offset too large.

Hello,
I am working with SRM 7.0, Backend: SAP ERP 6.0 EHP4
My problem is that I have replicated the SERVICE MASTER from R/3.But in
tcode SMQ1 for Queue: R3AI_SERVICE_MASTER the system shows the following
error message:SYSFAIL Invalid subfield access: Offset too large.
In SRM the Range are SRM external match with R/3 internal.
I have already replicated OK the following:
DNL_CUST_PROD0
DNL_CUST_PROD1
DNL_CUST_SRVMAS
Could anybody please advise, it would be well appreciated.
Kind regards,

Hello,
the problem was the table CRMSUBTAB for the Service line had a field ticked as inactive.

Switching Backend System

Hello everybody
We've setup SRM 4.0 with SRM Server 5.0 SP08 and CCM 2.0 SP03 on a development/customizing machine called DIM. We connected it to temporary devel./customizing SAP R/3 4.7 backend system called RIS.
Why a temporary devel./customizing backend system? Well, that's a complete other story...
However, we now have to change this connection to the definitive devel./customizing SAP R/3 4.7 backend system.
The problem / question is: after having changed all customizing settings (changed logical and/or RFC destinations everywhere) we are able to replicate DNL_CUST_BASIS3, DNL_CUST_PROD0 but not DNL_CUST_PROD1 from the new backend system.
In R3AM1 it hangs with a yellow status, in SMQ2 it stays in the inbound queue with an error message ":COM_PRODUCT_CUSTMSG:028 R3PRODHIER RISCLNT200".
RISCLNT200 is the logical system name of the old backend system.
Is this error message araising because we already replicated from this (old) backend system? Does anybody out there know this issue? Anyone having a solution to it?
Other question:
Is it somehow possible to wipe out all repliacated data (hierarchies, categories, material, ...) from an SRM server instance without having to reinstall everything from scratch? We're still on development/customizing level and not in production yet!
Thanks in advance for some help. Would be happy to reward with points!
Renaud
EDIT: looking at COMM_HIERARCHY I can see that the product categories were replicated. Any ideas, why I get above error in the inbound queue SMQ2 then?
Message was edited by: Renaud Desarzens

Hi Christophe
Thanks for the tip. Just tried it out, went to COMM_PRAPPLCAT and deleted the entry with application 01 and its assigned hierarchy id (R3PRODHIER). Then went to the pending queue entry in SMQ2 and restarted it.
Now the system returns another error in the inbound queue (SMQ2). It tells me that the hierarchy id R3PRODHIER already exists.
Tried to delete it in COMM_HIERARCHY but of course the system says it may only be maintained in the backend system. This backend system is no more of interest for us. We want to replace it by another one.
What else can I do? Is there a way to wipe out all replicated hierarchies and all products just to be able to redo an initial replication from a new (NOT additional!!!) backend system?
BTW: In the actual R3MATCLASS hierarchy I have some categories from our old backend system and some additional new ones from the new backend system. How can I make sure to have only categories from 1, the new one, backend system?
I'm kind of lost here...
Best regards,
Renaud

Error 'sysfail' in outbound que of SRM :Initial download - DNL_CUST_BASIS3

Dear Consultants,
                               We are trying to replicate the product categories and material master from ECC system to SRM system for the first time.
Performed all the middleware settings as per note 720819. When running the initial load - DNL_CUST_BASIS3 the prog keeps on running. We are getting a entry in SRM outbound que - Sysfail - trigerred a dump in the source system. When we get into ST22 in ECC system we see there is a dump. While analysing the dump in st22 we get that table CRMATAB is empty, the same issue we get when we debug the que in outbound que in SRM.
We are planning to apply note 1501685 to address the issue. But there are some entries which are there in Inbound que of SRM system. All have the status of sysfail. Some refer to analyse the error in SMW01 and some say refer note 490748. In the Note 490748 all entries are maintained . Other entries says the category for material group xxx does not exist - import the Customizing object DNL_CUST_PROD1.
I am a bit confused now, will the application of the Note will solve the issue or is there something else that may need to be done.
Any specific inputs will be valuable for me.
regards
Arindam.

Hello All,
                            I am getting the following error in SMW01a re as follows
Category for material type MAT_KMAT does not exist
Category for material group CM14 does not exist
Please note I am running the following initial load in sequence
DNL_CUST_BASIS3
DNL_CUST_PROD1
DNL_CUST_PROD0
We are also getting a dump in SRM system -
ST22 -
Runtime Errors         CALL_FUNCTION_PARM_MISSING
ABAP Program           SAPLSMOUTIL
any specific inputs will be welcome
regards
Arindam

Materials replication and R3PRODSTYP - SYSFAIL in inbound queues

Hi,
We are using SRM 7.0 and we have a problem in materials replication. In inbound queues we have the status SYSFAIL and the following error:
R3A* Error in Mapping (Details: transaction SMW01)
In SW01 the error messages are: u201CDownload inicial material: Table not supported by functionu201D and u201CCategory for material type MAT_Z001 does not existu201D
We did the initial download of DNL_CUST_PROD1 and the materialu2019s group corresponding to R3MATCLASS were replicated successfully. However 2 product subtype, corresponding to R3PRODSTYP, were not replicated.
Thus, the materials are not being replicated.
Do you have any ideas?
Thanks in advance,
Best regards,
AN

We already did the initial download of DNL_CUST_PROD0, DNL_CUST_PROD1, MATERIAL...
The problem is that there are two material types that at this time donu2019t exist in R/3 and when we do the material download those material types are trying to be replicated...
Any help?
Thanks!
Best Regards,
AN

Backend is sending CRM stuff to SRM

Hello,
we have landscape with backend 4.7, CRM and SRM.
The problem is that backend system is sending SD information not only to CRM but also to SRM. This is causing short dumps in SRM because functions necessary for that call are inactive. It will not be a problem but this information is comming every minute or so. We have more than 2000 shortdumps in SRM just last day. Also outbound queue of the backend system is full of SYSFAIL
Is it possible to somehow filter that those queues are going only to CRM?
I think that this is in connection with table CRMPAROLTP in the backend system, but do not know what to put in Parameter Value field for Parameter Name2 = SALESDOCUMENT. Now in Parameter Value is X in Parameter Value2 is nothing.
TIA
GOrdna

Hi,
Check the entries in all the CRM tables in the backend related to middleware...specially the CRMCONSUM table..here check the entry for EBP...Also check all the middleware settings and esp the RFC destination....May be in your case ,for the CRM consumer/entry(in CRMCONSUM table),the RFC destination is of SRM system....
HTH.
BR,
Disha.
Pls reward points for useful answers.

Error message in trans code SMQ1(backend) for material replication

Hi All,
I am wandering if someone can help me with this query. I have basically followed all the customisation steps requried to replicate replicate material masters from R/3 to SRM. I had infact closley followed the advise posted on the blog: How to replicate material master from R/3 to SRM
However, once I start the initial load in SRM with trans code R3AS and thebn goto trans code SMQ1(in R/3 backend), the load has failed with the 'status' or SYSFAIL. When I double click on this message, I get the error:
"Exception condition" EBCDIC_PROBLEM__OSSNOTE_33300 8" raised.
I have looked at note 333008 but cannot find any clues as to what is causing the load to fail. In trans code R3AM1, the job's status only remains as 'Running' and does not change.
Any pointers as to the cause and required workaound would be appreciated!
Thanks
SW.

Hi Muthu,
Thank you for your feedback. I have just this moment implemented the note you recommended, but this does not appear to have resolved the error message, even though the consumer has been changed from CRM to SRM in r/3 and srm.
I basically undertook the initial load for object 'dnl_cust_basis3' only with trans code R3AS, but the system still shows the following error message in the outbound que list (trans code SMQ1) in the sender R/3 backend system:
""Exception condition "EBCDIC_PROBLEM__OSSNOTE_33300
8" raised""
I am reluctant to implement the note number (333008) within the error message as the note heavily describes the CRM 2.0 component only and shows little relevance to SRM 5.0.
Any feedback would be appreciated. I have pasted the note contents below.
Thanks
SW.
Note 333008 - XML in R/3 Adapter
Summary
Symptom
For the Plugin PI 2000.1 (R/3 OLTP) and the CRM 2.0B Support Package 08, the R/3 Adapter was enhanced by an XML support.As of CRM 2.0B Support Package 7, SAP recommends to use R3A XML as a standardAs of CRM 2.0C, XML is automatically the standard setting in the server, only in the OLTP PlugIn, you have to maintain a setting.
Additional key words
CRM, R/3 Adapter, XML, CRM_SEND_XML, BAPIMTCS, IBM, AS/400 OS/400 S/390, DBIF_RSQL_SQL_ERROR, SQL error -302 accessing table SMOAUSP
Cause and prerequisites
System requirement:Plugin PI 2000.1 with at least PlugIn patch 03 or higher and CRM 2.0B Support Package 08 or CRM 2.0C on the server.(XML is possible with CRM 2.0B Support Package 07, however, Support Package 08 is recommended:if you only use Support Package 07, parameter CRM_CONVERT_ENDIAN has to be maintained even if this has no effect - see Note 207264.)
Solution
Introduction
To eliminate or minimize problems that occur during the data transfer between different operating and computer systems, an XML interface was implemented in the R/3 Adapter in addition to the binary transport, which has been used so far.
This XML interface consists of an XML generating program on the OLTP-Plugin and an XML parser on the CRM.
The generating program generates an XML document from the data stream to be sent to the CRM System and the XML parser converts this back into the original data stream. Except for the initial configuration, the mechanism is transparent and does not require further user activities.
Activation
To use XML in CRM 2.0B in the initial download, you have to enter the following new parameter in table SMOFPARSFA (Transaction SM30 or R3AC6) on the CRM server:
             Key:             R3A_COMMON
             Parameter name: CRM_SEND_XML
             Parameter value: 'X'
In CRM 2.0C, table SMOFPARSFA does not have to be maintained since XML is automatically the standard setting.
For the data transfer with XML in delta download you must do the following
Maintain parameter table CRMPAROLTP in PlugIn Release PI 2000.1, patch 03:Newly enter parameter name CRM_SEND_XML_FOR_DEFAULT_DEST with parameter value 'X'.
Maintain parameter table CRMRFCPAR as of PlugIn Release PI 2000.2:Transaction SM30, set field SEND_XML of CRMRFCPAR to value 'X' for the corresponding entries
Advantage
The data transport in the XML format solves both the endian problem (see Note 207264) and the code page problem which existed during a data transport from or to an IBM mainframe (AS/400, S/390) to or from an ASCII-based system (NT, UNIX).
Deactivation
Regarding the performance, the XML format has the disadvantage that the XML parser needs CPU time (which can be processed in parallel because no database access is made).If you want to do without the XML conversion in a specially defined system landscape, then set parameter CRM_SEND_XML to blank in the CRM System, and set table CRMPAROLTP (PI 2000.1) or CRMRFCPAR (PI 2000.2) without XML in the R/3 OLTP.In addition, parameter CRM_CONVERT_ENDIAN must be maintained correctly in the CRM System (see Note 0207264).
You can do without the XML conversion under the following conditions.
1. The OLTP system infrastructure and the CRM system infrastructure mustbe homogeneous. Example: all OLTP application servers UNIX and all CRMapplication servers NT.
2. You must also make sure that no application servers with different operating systems are used in future.
3. The OLTP system infrastructure must be homogeneous.In the CRM System it is possible to limit the application servers permitted for the processing of the queues by setting a specific server group.The application servers of these group servers must be homogeneous.However, the setting is valid for all inbound queues and cannot be restricted to specific queue names.
              You can set up a server group with Transaction RZ12, and in Transaction SMQR you can set up the server group used for the processing via menu option 'Edit' -> 'Change AS group'. For details on this, see Note 369007.
As SAP cannot check the customer's system landscape,this option is to be classified on project basis where the responsibility is the customer's and not SAP's.
If homogeneous system infrastructures do not exist, the time required for saving data and documents can nevertheless be significantly reduced by carrying out the XML conversion in one asynchronous step.For this, you must maintain parameter CRM_XML_BACKGROUND_PROCESSING_ON in table CRMPAROLTP. For this purpose, refer to Note 350176.
Notice
Since the IPC is currently not able to process the XML document of the R/3 Adapter, XML must not be activated for IPC targets in CRMRFCPAR!
Since, in addition to the existing data mapping and data transport, the XML generation and the XML parsing is included in the sequence of operations, you must expect a download runtime which might be twice as long as usual!
Due to performance reasons, only the '&', '<' and '>' characters are converted into XML escape sequences at present.Therefore, other special characters in text fields might cause problems and might not be output correctly on the target system.
The XML conversion does not solve problems with multi-byte texts, for example the data exchange between a Japanese and an English codepage is not supported.
Source code corrections
Header Data
Release Status: Released for Customer
Released on: 25.07.2001 22:00:00
Priority: Recommendations/additional info
Category: Special development
Primary Component: CRM-MW-ADP Middleware Adapter
Secondary Components: CRM-MW Middleware
Affected Releases
Software
Component Release From
Release To
Release And
subsequent
MDM 200 200 200
COM_CRMMDM 40 4.0 4.0
UIFRW 40 4.0 4.0
CGVMIC 10 100 100
BBPCRM 2.0 20B 20C X
BBPCRM 3.0 300 300 X
BBPCRM 3.1 310 310 X
BBPCRM 3.5 350 350 X
BBPCRM 4.0 400 400 X
Correction delivered in Support Package
Support
Packages Release Package
Name
BBPCRM 20C

SYSFAIL - Queue problem

Hello,
I have an integration scenario wherein I am sending a xml message to XI and in XI the message is mapped to 2 idocs and sent to 2 different R/3 systems.
When I run the test in the Runtime Workbench and give the payload with the Quality of Service as Exactly Once(EO) it runs perfectly and creates the idocs in the backend systems. --- Scenario 1
But when I send the xml message from the sender system the Quality of Service I get is Exactly Once In Order (EOIO) and eventually after the mapping and branching the message gets stuck in the outbound queue with status SYSFAIL. --- Scenario 2
The difference I see in the SXMB_MONI is that the queue id after branching for the scenario 1 is that the is changed to XBTOC and XBTOD but in scenario 2 the queue ids after branching have the prefix as SAP_ALE_ which in my opinion is not a valid queue id prefix.
Could you please tell me how to rectify this? This is very crucial and urgent.
Thank you.
Regards,
Vivek

Hello Vijaya,
Unfortunately the xml message is created by a framework and I cannot change the QOS. Is there any way that I can make XI believe that the QOS is EO rather than EOIO.
Thank you.
Regards,
Vivek

BBP_EXTREQ_TRANSFER - SYSFAIL

Hi everyone,
I've been having problems when I try to synchronize PR's from ECC to SRM 4.0 using BBP_EXTREQ_TRANSFER. The queue status is SYSFAIL and the message is Exception condition "OBJECT_ID_NOT_FOUND" raised.
I've checked SLG1 in SRM and there's nothing there.
In transaction ST22 there is a RAISE_EXCEPTION in program SAPLBBP_ATTR_PDORG - form "map_object" (line 34).
PPOMA settings seem to be ok (I've done all settings that were recomended in other threads).
I've had no problems in transaction R3AS with:
DNL_CUST_BASIS3
DNL_CUST_PROD0
DNL_CUST_PROD1
DNL_CUST_SRVMAS
MATERIAL
SERVICE_MASTER
Our Production SRM content was copied into QA, which demanded some re-configuring. There could be something missing related to that...
Any hints?
Thanks in advance,
Henrique

Hi,
The PR is in EPRTRANS table, with field TRANSSTAT = 2 and EPROFILE = 01. The RFC user has profiles SAP_ALL and SAP_NEW.
SMQ1 (in ECC) is always emptied before the attempt to synchronize and so is SMQ2 (in SRM).
Local Purchasing Organization as well as local Purchasing Group are properly defined in PPOMA, with the tab Function pointing these groups to the SRM logical system (since they are local). The groups also have required attributes set.
The RFC user is correctly integrated into the Org. Model.
I've checked transaction 'comm_hierarchy' in SRM and there are 3 categories (under R3MATCLASS):
- R3MATCLASSQRM200
- R3MATCLASSQAS-100
- R3MATCLASSQAS-200.
I want to delete the last one but it says I can only do it in ECC QAS. I went to the same transaction in ECC but there was nothing there.
Could this be the problem? What should I do about it?
Regards,
Henrique
Message was edited by:
Henrique Hermont

SMQ1 - SYSFAIL - Middleware

Dear Gurus,
I'm working on CRM 5.0 and I'm creating a BP. After create, when i check transaction SWM01 the BDOC is wating(yellow) then I check transaction SMQ1 and the is an error in the outbound queue. The status is assigned as SYSFAIL and when I check the details there is an error in FM CRM_UPLOAD_TRIGGER - Field symbol has not yet been assigned.
Can anyone help me?
Regards,
Caíque Escaler

Dear All----
I am also facing the same issue----
I am trying to replicate BP from CRM to ECC. I have already succeeded in replicating customer from ECC to CRM. I have maintained all settings in PIDE in ECC. On CRM side I am creating BP in role Sold-to-party and I have mapped it to a Z-Account Group created by copying from standard Acc Group 0001 Sold-to-party. When creating the BP, a Bdoc is generated in yellow status. The queue is stuck in smq1 outbound queue with SYS FAIL.
I can also see errors in SMWP dashboard.----
I am facing some errors under Runtime Information in SMWP.----
1. Runtime InfoData Exchange using qRFC QueuesqRFC Queues in CRM ServerData exchange with R/3 BackendR3A* Load Queues R/3 OLTP -> CRM --Blocked queues: Client 201 Blocked inbound queue: Client 201 Q name R3AD_CUSTOME status SYSFAIL dest carnation3_DEV_00 -
2. Runtime InfoData Exchange using qRFC QueuesqRFC Queues in CRM ServerData exchange with R/3 BackendR3AU* Load Queues CRM -> R/3 OLTP--Blocked queues: Client 201 Blocked outbound queue: Client 201 Q name R3AUBUPA0001100004 status SYSFAIL dest DEVCLNT100 -
3. Runtime InfoData Exchange using qRFC QueuesqRFC Queues in R/3 Backend(s)ECC SiteLoads for CRM Server--Blocked queues 6 entries. -
4. Runtime InformationCRM Middleware BDoc-Msg. in the FlowStatus of BDoc Messages--BDoc Messages in error status (201) BDoc Type TG_MSG: 1 Entries in Error Status Please suggest a way out. Any help will surely be appreciated and rewarded. -
Thanks and Regards-----
Varun Taneja

Erro de SYSFAIL e Queda do Ambiente JAVA (PI)

Bom Dia
Estou num projeto de NFe e atualmente esta acontecendo o seguinte cenário de Erros:
    Na SMQ2 , quando apresenta um aumento nas filas de Mensagens , aparece SYSFAIL em determinadas Filas , todas as outras travam , aumenta o numero de Filas.
   Com essa mensagem de SYSFAIL nas filas , o serve0 (Parte JAVA do PI) cai e após isso estou tendo que efetuar manualmente um STOP/START em todos os canais de comunnicação para que os R/3 voltem a emitir NFe.
    Isso esta ocorrendo com mais frequência após inserir uma nova empresa para emissão de NFe.
    Alguem poderia me ajudar a entender por que ocorre o SYSFAIL as mensagens travam e derruba o ambiente JAVA ?
Sérgio.

1º) Erro: Commit Fault: com.sap.aii.af.rfc.afcommunication.RfcAFWException:SenderA
2º) Foi alterado o numero de Filas O numero de Filas foi alterado , mas não consigo ver esse parametros na RZ10 , tem 3 entradas : X32_DVEBMGS32_NFISAP ; DEFAULT ; START_DVEBMGS32_NFISAP nessa transação ...onde eu vejo isso
3º) Esse parametro não tem nessa transação (/usr/sap//DVEBMGS00/j2ee/cluster/server0/log/). em qual desses diretórios abaixo eu encontro esse parametro ?
Existe esses:
DIR_ATRA      /usr/sap/X32/DVEBMGS32/data
DIR_BINARY      /usr/sap/X32/DVEBMGS32/exe
DIR_CCMS      /usr/sap/ccms
DIR_CT_LOGGIN    /usr/sap/X32/SYS/global
DIR_CT_RUN              /usr/sap/X32/SYS/exe/run
DIR_DATA              /usr/sap/X32/DVEBMGS32/data
DIR_DBMS              /usr/sap/X32/SYS/SAPDB
DIR_EXECUTABLE /usr/sap/X32/DVEBMGS32/exe
DIR_EXE_ROOT     /usr/sap/X32/SYS/exe
DIR_GEN              /usr/sap/X32/SYS/gen/dbg
DIR_GEN_ROOT    /usr/sap/X32/SYS/gen
DIR_GLOBAL        /usr/sap/X32/SYS/global
DIR_GRAPH_EXE /usr/sap/X32/DVEBMGS32/exe
DIR_GRAPH_LIB   /usr/sap/X32/DVEBMGS32/exe
DIR_HOME             /usr/sap/X32/DVEBMGS32/work
DIR_INSTALL        /usr/sap/X32/SYS
DIR_INSTANCE     /usr/sap/X32/DVEBMGS32
DIR_LIBRARY      /usr/sap/X32/DVEBMGS32/exe
DIR_LOGGING     /usr/sap/X32/DVEBMGS32/log
DIR_MEMORY_INSPECTOR   /usr/sap/X32/DVEBMGS32/data
DIR_ORAHOME       /oracle/X32/102_64
DIR_PAGING                            /usr/sap/X32/DVEBMGS32/data
DIR_PUT                            /usr/sap/X32/put
DIR_PERF                            /usr/sap/tmp
DIR_PROFILE      /usr/sap/X32/SYS/profile
DIR_PROTOKOLLS     /usr/sap/X32/DVEBMGS32/log
DIR_REORG                          /usr/sap/X32/DVEBMGS32/data
DIR_ROLL                          /usr/sap/X32/DVEBMGS32/data
DIR_RSYN                            /usr/sap/X32/DVEBMGS32/exe
DIR_SAPHOSTAGENT     /usr/sap/hostctrl
DIR_SAPUSERS     ./
DIR_SETUPS                           /usr/sap/X32/SYS/profile
DIR_SORTTMP     /usr/sap/X32/DVEBMGS32/data
DIR_SOURCE     /usr/sap/X32/SYS/src
DIR_TEMP                           /tmp
DIR_TRANS                           /usr/sap/trans
DIR_TRFILES                          /usr/sap/trans
DIR_TRSUB                          /usr/sap/trans

SSO between a Java EE application (Running on CE) and r/3 backend

Hi All,
Over the past few days I have been trying to implement a SSO mechanism between NW CE Java Apps and R/3 backend without any success. I have been trying to use SAP logon tickets for implementing SSO.
Below is what I need:
I have a Java EE application which draws data from R/3 backend and does some processing before showing data to the users. As of now the only way the Java App on CE authenticates to r/3 backend is by passing the userid and pwds explicitly. See sample authentication code below:
BindingProvider bp = (BindingProvider) myService;
Map<String,Object> context = bp.getRequestContext();
context.put(BindingProvider.USERNAME_PROPERTY, userID);
context.put(BindingProvider.PASSWORD_PROPERTY, userPwd);
Now this is not the way we want to implement it. What we need is when the user authenticates to CE ( using CE's UME) CE issues a SAP logon ticket to the user. This ticket should be used to subsequently login to other system without having to pass the credentials. We have configured the CE and Backend to use SAP logon tickets as per SAP help.
What I am not able to figure out is: How to authenticate to SAP r/3 service from the java APP using SAP logon tickets. I couldnt find any sample Java code on SAP help to do this. (For example the above sample code authenticates the user by explicitly passing userid and pwd, I need something similar to pass a token to the backend)
Any help/pointers on this would be great.
Thanks,
Dhananjay

Hi,
Have you imported the java certificate into R/3 backend system ? if so.
Then just go to backend system and check on sm50 for each applicaion instance of any error eg.
SM50-> Display files (ICON) as DB symbol with spect.(cntrlshiftF8)
You will get logon ticket details.
with thanks,
Rajat

Error while uploading Backend Role

Hi All,
I was trying to upload a backend role in Portal, but while uploading, got the following error:
com.sap.portal.pcd.rolemigration.RoleMigrationException: Nested Exception. Failure to execute native function. Nested Exception. NOT_AUTHORIZED - message at com.sap.portal.pcd.rolemigration.util.Connector.callFunction(SAP_ECC_HumanResources,en_US,qpi019,MENU_AGR_TREE_READ_HIERARCHY,{ACTIVITY_GROUP=Z_QPI_AGU}): Check parameters. Nested Exception. Failure to execute native function. Nested Exception. NOT_AUTHORIZED at com.sap.portal.pcd.rolemigration.RoleMigrationObject.getIconsDescriptions(RoleMigrationObject.java:2154) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1843) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:782) at com.sap.portal.pcd.rolemigration.RoleMigrationThread.run(RoleMigrationThread.java:523) Original exception: com.sapportals.connector.execution.ExecutionException: Nested Exception. Failure to execute native function. Nested Exception. NOT_AUTHORIZED at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewExecutionException(SAPConnectorException.java:116) at com.sapportals.connectors.SAPCFConnector.execution.functions.SAPCFConnectorInteraction.execute(SAPCFConnectorInteraction.java:531) at com.sap.portal.pcd.rolemigration.util.Connector.callFunction(Connector.java:426) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.getIconsDescriptions(RoleMigrationObject.java:1940) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:1843) at com.sap.portal.pcd.rolemigration.RoleMigrationObject.migrate(RoleMigrationObject.java:782) at com.sap.portal.pcd.rolemigration.RoleMigrationThread.run(RoleMigrationThread.java:523) Caused by: com.sapportals.connector.ConnectorException: Nested Exception. NOT_AUTHORIZED at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionException(SAPConnectorException.java:37) at com.sapportals.connectors.SAPCFConnector.execution.functions.SAPCFConnectorInteraction.execute(SAPCFConnectorInteraction.java:406) at com.sapportals.connectors.SAPCFConnector.execution.functions.SAPCFConnectorInteraction.execute(SAPCFConnectorInteraction.java:496) at com.sapportals.connectors.SAPCFConnector.execution.functions.SAPCFConnectorInteraction.execute(SAPCFConnectorInteraction.java:520) ... 5 more Caused by: com.sap.mw.jco.JCO$AbapException: (126) NOT_AUTHORIZED: NOT_AUTHORIZED at com.sap.mw.jco.JCO$Client.execute(JCO.java:3429) at com.sapportals.connectors.SAPCFConnector.execution.functions.SAPCFConnectorInteraction.execute(SAPCFConnectorInteraction.java:398) ... 7 more
Can you please suggest, how to go ahead to overcome the issue.
Cheers!!!
Umang Mathur

Hi,
The backend user, mapped to Portal, was given SAP_ALL authorization. Once that was done, the role was uploaded easily into Portal. But now, the issue is, which role is specifically required to perform the task. The role, s_rfc was already given to the user, but still I was facing the error.
As of now, I am keeping the post open, for discussion and points. Please post your valuable comments.
Cheers!!!!
Umang

Error while reading the PO in the Backend system. Inform system admin

Hi All,
We are having a peculiar issue of 'Error while reading the PO in the Backend system. Inform system admin'.
The P.O is in ordered status in SRM but the same is not getting transferred to backend ECC system.
No error messages or logs in RZ20, SLG1 any where.
All programmes like BBP_GET_STATUS_2 and CLEAN_REQREQ_UP are running fine.
Tried pushing the P.Os manually using function module (BBP_PD_PO_TRANSFER_EXEC_V2) to backend ECC.
It was working fine till a week ago and suddenly this problem is coming.
We had implemented few OSS notes suggested by SAP for the issue of 'shopping carts appearing in sourcing cockpit even after P.O creation' in both development and test system.
Now this issue is coming up in test system where as development system is working fine.
Please let us know where to look and how to resolve this issue.
A quick response would be highly appreciated.
Regards,
Teja

I am facing the same issue with one PO in the Production system.
SRM 5.0 , R/3 4.6C Extended classic scenario.
I checked the status of other PO's created today. I see them in R/3. There is one PO which was created a week back which shows up as "ordered" in SRM but the PO is missing in R/3. When clicked on the details on the web, system throws the error
Error while reading the PO in the Backend system. Inform system admin.
Message no. BBP_CF010
I checked RZ20, SLG1 no errors were found. I checked RFC connection, it was working fine too.
I tried pushing the PO using the FM BBP_PD_PO_TRANSFER_EXEC, it did not solve the problem.
In SRM WEBGUI Process PO - Item data -->follow on documents --> PO status is shown as Archived.
Any inputs would be greatly appreciated. Please throw some light on this issue.
Krishna

DNL_CUST_PROD0 & SYSFAIL in backend

Similar Messages

Maybe you are looking for