Error sending IDOC to PI

Hi experts,
I´ve configured an IDOC to IDOC scenario.
The source system sends an IDOC to PI. The problem is this IDOC doesn´t arrive to PI (no message in SXI_MONITOR).
I´ve checked in the source system the transaction SM58, and I have the following error message:
Kein Service für System SAPVTQ Mandant 699 im Integration Directory
Any idea of how can I solved it?
Thanks,
Javier

Hi Pragathi,
You were right, it was because of the partner profile. I didn´t select the option Individual Processing.
Thanks for your answers,
Javier

Similar Messages

Error sending IDOC from external Java application to Sap ERP system

Hi Experts!
When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
Please help. I read all threads about this error, but non of those can help me.
My relevant java sourcecode:
doc.setSenderPort("CLNTJAVA");
The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
Both case(third party business sytem and erp business system) I have configured the ID i think correctly. I made a business systems,I configured the adapter specific identifies,I made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
My configurations if it can help for you.
Hostname:sapsp5
System name: NE2
Clients:
000 ERP
001 Integration Server
SLD configurations:
Third Party Technical system name: Java_sytem
Business System:CLNTJAVA
Logical system name: CLNTJAVA
ID configurations:
Business System:CLNTJAVA
adapter-specific identifiers:logical system:CLNTJAVA, the rest is initial,because I cant change it.
IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
I think the IDX1 port and the adapter specific identifiers are wrong. is it?
my java source if the sender is the JCO
doc.setSenderPort("INTSERV");
My configurations if the sender is the JCO.
SLD configurations:
Technical system name: NE2
Business System:INTEGRATION_SERVER_NE2
Logical system name: INTSERV
ID configurations:
Business System:INTEGRATION_SERVER_NE2
adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
Thank very much.

Hi!
My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
Check this configuration please(posted here:
No service for system ... in Integration Directory)
doc.setMessageType("ACC_DOCUMENT");
doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
doc.setRecipientPartnerType("LS");
doc.setRecipientPartnerNumber("SE1CLNT500");
doc.setSenderPort("SAP3MA");
doc.setSenderPartnerType("LS");
doc.setSenderPartnerNumber("TREMACLNT");
doc.setClient("100");
Inside XI configuration integration builder
Business Service: Service: TREMACLNT
Under the menu Service - Adapter specific identifiers
Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
Client: 100
In IDX1 trans
Port: SAP3MA (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
(a not so well documented feature)
Client: 100
RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
My idx1 port is the same as my SNDPOR value in Java,but still came the error.

Error sending Idoc's to SAP

Hi,
I'm getting error in file-XI-SAP scenario. File is read and transformed to Idoc ok, but then I get this kind of error message in SXMB_MONI:
<SAP:Stack>Error: Basic type 'HRMD_A01' is unknown</SAP:Stack>
What I'm I missing in the scenario?

Hi Tapio,
Take a look at this link:
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Error: No IDocs could be sent to the SAP BW using RFC.
Hope it helps you.
Cheers,
Chandra

Error sending IDOC from JCO Client to PI AEX 7.3.1

Hi All
We have a requirement to send an IDOC from a non SAP System to our ECC via PI AEX :
JCO.Client --> PI AEX --> SAP ECC
At this time, we are testing this scenario with a JAVA Client with JCO Library (3.0.10).
Destination to PI is OK
Destination to our SAP ECC (for IDocRepository) is OK
But by sending the IDOC to PI we are getting the following error, Exception is raised on the PI System and sent back to the JCO Client :
com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key' (raised by system <extern>|PiSystem)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:670)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:1881)
 at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1120)
 at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:953)
 at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1465)
 at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:319)
 at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:323)
 at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:353)
 at sap_connector_examples.IDocClientExampleToJavaPO_pbs.main(IDocClientExampleToJavaPO_pbs.java:97)
Caused by: RfcException: [<extern>|PiSystem]
 message: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key'
 Return code: RFC_SYS_EXCEPTION(3)
 error group: 104
 key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by <extern>|PiSystem
PI Destination:
jco.destination.repository_destination=ABAP_AS_WITHOUT_POOL
jco.client.gwhost=PiSystem
jco.client.gwserv=sapgw01
jco.client.tpname=XI_IDOC_DEFAULT_PID
jco.client.type=E
ECC Destination: (ABAP_AS_WITHOUT_POOL)
jco.client.lang=en
jco.client.client=100
jco.client.passwd=****
jco.client.user=User
jco.client.sysnr=00
jco.client.ashost=ECCSystem
We have already set the PI VM System parameter jco.allow_non_abap_partner to 1
ECC User has S_RFC Rolle
I will be thankful for any advise.
Thank You
Regards
Stéphane

Hi
InboundRA (Resource Adapter) is green (Fully available).
What do you mean by maintaining JCO RFC Destination in PI ?
We have set the inboundRA Properties has follow :
ProgramID : XI_IDOC_DEFAULT_PID
DestinationName : XI_IDOC_DEFAULT_DESTINATION
Local: true
mutliRepository : ED1=XI_IDOC_DEFAULT_DESTINATION_ED1;ES4=XI_IDOC_DEFAULT_DESTINATION_ES4;MD1=XI_IDOC_DEFAULT_DESTINATION_MD1;ES1=XI_IDOC_DEFAULT_DESTINATION_ES1;PD1=XI_IDOC_DEFAULT_DESTINATION_PD1;
GatewayServer and Service are pointing to our PI System
BindingKey : PI_AAE_IDOC
And for each Repository we created a destination in NWA pointing to the corresponding ECC System.
(target host pointing to the ECC System and the Gateway host pointing to the PI System)
Our Installation isn't new but it is the first time we are configuring the System for this scenario:
JCO.client --> PI AEX
Regards
Stéphane

Error sending IDoc from ERP to PI 7.4 Java Only (stuck in SM58)

Hi specialists
I'm trying to send an IDoc to our new PI 7.4 Java Only.
Because of some authorization issues I changed the RFC Destination <blabla> on PI (nwa) pointing to the ERP system.
Now the IDoc is stuck in SM58 (tRFC queue) and I get this error message:
The IDoc Destination <blabla> was changed. Refresh the destination instance with
Meldungsnr. SR053
Anyone able to tell me where to do this refresh? I'm new to PI 7.4 Java Only and could not find useful answers on SCN and other internet sources.
Thanks a lot in advance for any hints.
Renaud

Hi Iñaki
Great document btw... didn't stumble uppon this before. Thanks.
I carefully went through it but nothing I tried helped.
The RFC destination (PI -> ERP) is working fine.
The resource adapter (inboundRA) is configured correctly. I can confirm, that the connection test of the RFC-Destination inside ERP (ERP -> PI) is successful.
BUT still: sending an IDoc from ERP to PI fails with this message in SM58:
The IDoc Destination <destinationName> was changed. Refresh the destination instance with
Meldungsnr. SR053
This seems to happen every time after one changes some settings in the destination specified in the inboundRA property "destinationName".
So my question still is: how / where do I refresh this destination instance on a PI 7.4 Java Stack Only??? I mean without having to restart the whole PI instance...
Best regards
Renaud

Getting error code 37 while sending IDOC via WE19

Hello experts,
I am facing a very unlikely error which is preventing me from testing my scenario.
I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
In quality R/3 i have done the following:
1) Created RFC for my XI dev server
2) Created port for this RFC
3) Created partner profile adding all required IDOCS in the outbound parameters
4) Created distribution channel for all the idocs
In XI dev system i have done the following:
1) Created RFC for both dev and quality of R/3
2) Created port for both the RFCs
3) Maintained the IDOC metadata for both the ports
Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
Its really urgent hence your help will be highly apreciated.
Thanks,
Yash

hi yash,
where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
actually we are getting confused.
i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
In error it says sender port SAPQTY_510 is invalid mean port of Source not XI DEV(receiver).
just try to use some other name say SAPXXX_QUA and confirm the error.
when IDOC is sent to XI DEV ,port of XIDEV SAPQTY_510 has nothing to play any role .
just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
so please check at which port error is coming.
Thanks & Regards,
Rama Krishna
Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

Idoc- can we sent already sended idoc if status is showing error message

hi
Idoc- can we sent already sended idoc if status is showing error message
without making any changes.
Thanks in advance.

Hi raja,
IN BD87.
give the idoc number,its status,messagetype and partner system and resend it.
Regards,
nagaraj

Error in sending Idoc :: Urgent

HI
we are trying to send Idoc DELINS and ORDERS to SUS system. when sending the idoc the following error occurs in SUS
StandaredMessageFault
An error occured within XI interface: An exception with the type CX_GDT_CONVERSION occured but was neithered handled locally nor declared in a RAISING clause Program: SAPLBBP_BD_MAPPING_SAPXML1; Include : ; Line
How ever the same works fine in Dev and QAS servers
Regards,
Anand

Hi
Please provide SRM-SUS and XI Version details.
Please go through the SAP OSS Notes, which will help ->
Note 782755 - Control indicator is not transferred from MM to SUS
Related Notes
Note 1062864 - Control indicator is not transferred from MM to SUS
Note 313925 - Example exit for EDI outbound processing (e.g. purchase order
Other OSS Notes ->
Note 885825 XML inbound: Dump in QuoteItemReferenceVersionID
Note 825169 XML: Bid currency in bid invitation
Note 819953 SRM 4.0 of SAP XML output of partner address data
Note 723680 Corrections in the mapping of SAP XML messages
Note 723594 - SRM 4.0 XML confirmation mapping error
Do let me know.
Regards
- Atul

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

Error by sending IDOC-acknowledgements

Hello,
we have the following scenario:
R/3 IDOC -> XI -> Mail-Adapter
We want to receive acknowledgements from the adapter.
But we get the error "Sender XI Party http://sap.com/xi/XI / XIParty / xyz couldn't be transformed to an IDoc Partner".
Does anyone know how to solve this problem?
Regards,
Thorsten

Hi,
Ok then,
Only the IDOC-acknowledgements couldn't be sent back to the R/3.
1.By any chance, did you check the
IDXNOALE table: and see if the port, the
client of the sender, and the message type id there.If yes then that table lists and block your acknowledgement.
2. Check this, "Use transaction SXMB_ADM ( Integration
Engine - Configuration) to obtain system
error acknowledgments from pipeline
services of the Integration Server and
maintain the specific configuration
parameter ACK_SYSTEM_FAILURE of the
RUNTIME category.Whenever a system error occurs within the Integration Server, a system error
acknowledgment is sent back to the sender.But this is for system error acknowledgements.
3. Did you refer the guide: "How To Handle Acknowledgments for IDoc"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
OR
https://websmp106.sap-ag.de/nw-howtoguides
Then go to exchange Infrastructure.
Regards,
Anirban.

Sending IDOC from R/3 to MII error

Hi,
We are trying to send IDOC from R/3 4.7 to MII 12.1 (SP8 patch 9 on NW CE 7.11).
We followed the guide below:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
Connection of message listener to R/3 works fine.
RFC connection test from R/3 to message listener was successful.
But when we try to do model distribution we get this error " - Communication error occured. Server repository could not create function template for 'MODEL_VIEW_REPLICATE'.
Maybe someone encountered this error and can help to resolve it.
Thanks in advance.

Hi Michael,
What do you mean by "manually registered the ProgID"? The message listener configuration property is as below:
ProgramID: MII_IDOC_CONNECT_5
MaxReaderThreadCount: 1
SAPClient: 800
UserName: GAOMX
Password: xxxxxxxx
Language: EN
ServerName: blade01a.memc.com
PortNumber: 00
BindingKey: XMIIIDOC
And also, following is error message found from LOG VIEWER of the MII server:
here is one
Message: not supported FunctionModule MODEL_VIEW_REPLICATE for IDocActivationSpec
Date: 2011-07-21
Time: 15:30:18:060
Category: /System/Server/Connector/Rfc
Location: com.sap.mw.jco.jra
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
and another one
Message: Server repository could not create function template for 'MODEL_VIEW_REPLICATE' caused by: java.lang.RuntimeException: not supported FunctionModule MODEL_VIEW_REPLICATE used with IDocActivationSpec registered for MII_IDOC_CONNECT_5 on system blade04a_MIT_00
Date: 2011-07-21
Time: 15:30:18:061
Category: /System/Server/Connector/Rfc
Location: com.sap.conn.jco
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
Thanks,
Mike

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
 Field name RFC_TYPE value FUGR
 Field name RFC_NAME value EDIMEXT, SDTX
 Field name ACTVT value 16
Authorization object S_IDOCDEFT
 Field name ACTVT value 03
 Field name EDI_CIM value ' '
 Field name EDI_DOC value TXTRAW01
 Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
 Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
 Field name ACTVT value 03
 Field name DICBERCLS value
from the note mentioned above.
Regards
Bhavesh

Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

Hello All,
I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
Br,
Sri

Hi !
Becaus alle this happens in beckgound, things are a bit difficult but solvable....
What you should do is a "Authority trace" ... as follows....:
- Go to the ST01
- Mark "Authorisation Check"
- Swich the trace on for your Workflow user
- Execute the Workflow until the error uccurs
- Go back to the ST01
- Press the "Analyze" button and see what error occurs
Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
Regards
rainer
Some Reward poins would be nice if that helped....

Error in sending IDOC for PO

Hi,
I am facing a problem in PO for sending IDOC. The error message is "Error transferring Extension data for enhancement CI_EKKODB"
Message type is PORDCR1
Idoc type: PORDCR101
Diagonosis given:
THE UNDERLYING CUSTOMER ENHANCEMENT CONTAINS DATA REFERENCES THAT ARE NOT CHARACTER-LIKE. FOR THIS REASON THE SYSTEM WILL NOT TRANSFER DATA.
Could anybody please give any suggestion to resolve rhis.
Waiting for quick response.
Best Regards
Bapi

It seems you must change all elements in structure CI_EKKODB as charter type.

Error sending IDOC to PI

Similar Messages

Maybe you are looking for