Problem when sending IDOC from ECC to MII 12.0

Hi all,
   I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
   But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
   - 53 IDOCS were successfully outbounded (list in WE02).
   - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
   - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
   I'm wonder why some IDOCs were successful while some others were error. If the bean IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
   I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
   If some have the same problem and know how to resolve it, could you please help me?
Thank a lot in advance,
Vinh Vo

Hi Vinh,
Please read the following document:
[IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.
In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it.
I suggest that you follow the document completely and do nothing else to set up a new listener.
If you are not using ECC 6.0, you may find the paths are different, but the transactions codes are generally the same. However, you may want to check with some of the older installation instructions regarding specific modifications. Look in the Wiki for MII under Connectivity.
Good luck,
Mike

Similar Messages

Problem when pushing IDOC from SAP to XI

Hi,
I am trying to push an IDOC from SAP R/3 system to XI. When I processed the IDOC using test tool(WE19), it's showing message that IDOC sent succesfully to R/3 or External system. But in SM58 Transaction it gave error message that in Trabsaction IDX1: some RFC connection error. Then I opened the Transaction IDX1 on XI server, in that IDOC Adapter configuration I gave RFC destination, Logical system name of R/3 and saved it. Now When I tried again to push IDOC from R/3 to it's not giving any error message(in SM58), but I am not able to see any thing in SXMB_MONI. Can anybody guess what's happening? And also I am using fresh newly installed XI server. DO I need to configure something else? All RFC connections are well defined and working fine.

Hi,
It is not required to create Sender Agreement for the Idoc to XI scenario. Because it is implicitly exists.
Can u check Receiver Determination created in the XI once again. And also check for RFC destinations created in the R/3.
Hope it helps ..
-Moorthy

Problems at sending IDOC from XI to R/3

Hello everybody, I have a problem sending an IDOC (WPUUMS) from XI to R/3. Everytime the ERP system presents overflow problems at the locked table, the IDOC, send by the XI, is not created. The type of the sending message is asynchronous. I tried to use the ALE configuration but it doesn´t seem to work.
I hope anyone can help me to figure out this issue.
Thank you.

Julio
Please try this...
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
http://help.sap.com/saphelp_nw70/helpdata/en/44/a1b46c4c686341e10000000a114a6b/content.htm
Check the Queue [SMQ2] & if the message got struck in queues clear the queues
Then goto SMQR - De-register & register the queues.
I hope it helps you ...
Thanks,
Vasanth.

Why is a photo displayed sideways when emailed. When I take a picture and email it is received sideways and not like it appeared when sent. I have not had this problem when sending pictures from my IPad or Mac. Thanks for any help M

It seems when the photo is sent to someone it is received in a sideways position. I have resent after editing and rotating the picture but is still is not upright.
Any help would be great.
Thanks. M

In my case I take HD video with an Apple iPhone 4S and an iPad 2. These cameras can be just as easily oriented in any of four orientations by hand, or in various iPhone or iPad holders for mounting on a tripod. As long as I stay with Apple or Adobe products for my whole video handling process, I have no problem with software support for orientation
While there are countless software programs available today that display JPEG images, only a subset of them actually interpret the EXIF Orientation flag. Just like color management, many programs simply display the JPEG image as it is stored, and completely ignore any extra details stored in the file's metadata. The most important of these additional details is the Orientation flag, stored in the JPEG APP1 marker under EXIF IFD0.
More explanation of this is in the text below.
Briefly, Apple is doing it right, with their iPhone 4S and iPad 2, the way most High end video cameras do it. And they made sure that their apps looked at the appropriate flag to rotate the image before showing it. To understand this look at this site:
http://www.impulsead...rientation.html
This is a site that explains the whole deal. Apple and Adobe are looking at the flags for image rotation. Plex,and many others are not doing so. VLC for instance, DropBox is anpther example, Thunderbird is another example, the list is long.
Many newer digital cameras (both dSLR and Point & Shoot digicams) have a built-in orientation sensor. Virtually all Canon andNikon digital cameras have an orientation sensor. The output of this sensor is used to set the EXIF orientation flag in the image file's metatdata to reflect the positioning of the camera with respect to the ground. Canon calls their sensor the "Intelligent Orientation" sensor. It is presumably a 2-axis tilt sensor, allowing 4 possible orientations to be detected. The paragraphs below are taken from that wonderfully illustrated link.
Auto-rotation in Digital Cameras
While your digital camera may include an option to "auto-rotate images" due to the camera's orientation, this is almost always just a "virtual rotation". A flag is set to indicate to the viewing software / LCD preview which way to rotate the image before display, rather than rotating the image content itself.
As lossless image rotation is a fairly compute-intensive operation, digital cameras are not likely to include true lossless rotation after capturing the photo. The CCD/CMOS sensor hardware is designed to stream raw data in a particular direction (e.g. rows then columns), and so it may be hard to incorporate true auto-rotation in-camera without a performance impact to continuous shooting (frames per second).

Sending IDoc from ERP to PI

Hi all,
I am trying to sent IDoc's from the ERP (SAP ECC) side to PI. But the IDocs are not arriving at the PI side. In ECC tc:we05 they seem to be successfully sent.
The Partner Type in we20 is "LI". I added the IDoc to the Outbound parameters and set the PORT to the Port we use for PI. But unfortunately it is not working.
Any idea why?

When sending IDoc from ECC System to PI.
some settings needed on ECC System & PI System
On ECC System
Create Port in WE21 type LS (Logical System) use RFC Destination TYPE ABAP in that port.
Create Partner Profile using PORT in WE20.
Add the Idoc as Outbound in that Partner Profile.
Now on PI System
PI System does not have structure / matadata of IDoc.
Create Port in IDX1.
Import IDoc Matadata in IDX2 use Port created in IDX1.
Create complete scenario & send IDoc from ECC, it will reach at PI System, if successful at ECC.

Error to send a IDOC from ECC to SUS

Hi,
I am trying to connect to SAP SUS System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP SRM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP SUS on PI. I have encountered the following error after executing the scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have configured HTTP receiver with Addressing type HTTP Destination and configured the HTTP destination field with RFC destination(Connection Type H) created on PI. Here my source and target structures are same i.e DELVRY03. I have triggered DELVRY03 idoc from ECC and i am expecting same xml to be sent to SAP SUS but stuck up with the above mentioned error.
Someone know how fix this problem?
Tks,
Erik

HI,
As per my understanding to your scenario, You want to send one IDoc from ECC to SAP SUS system using SAP PI.
So i hope you must have configured on all the steps required to Send one IDoc to PI syste, Secondly, are you using any Standard interface in PI to send data to SAP SUS system? If yes, you need to create an HTTP Destination for that system and then you have to create XI Receiver Adapter with that HTTP destination to post incoming message to SAP SUS system.
Your error suggests you are using Plain HTTP adapter to post data to SAP SUS, which is in my understanding is incorrect.
Regards
Aashish Sinha
Edited by: Aashish Sinha on Feb 21, 2011 9:15 AM

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

TS2755 Hi all, I bought one iphone and 3 ipads, i set up all on one apple ID. Now i have a problem when using messages: when sending message from one device it appears again on screen from the other 3 devices. I need help of how to set up messages on each

Hi all, I bought one iphone and 3 ipads, i set up all on one apple ID. Now i have a problem when using messages: when sending message from one device it appears again on screen from the other 3 devices. I need help on how to set up messages on each device separately and to start using messages app on each device independently. Thanks

search google for "iphone remove picture from contact"

Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

Hi,
I try to send idoc from SAP r/3 4.6C to PI 7. I had made ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
Is somebody can help me ?

Hi,
In R/3 :
my RFC destination is type 3 and point to XI. The port in the partner profile point to this RFC destination. ( all seems good !).
In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038 "1 master IDocs set up for message type MATMAS" and just after
the XI logon screen appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

Problem during hierarchy load from ECC 6.0 to BW

Hello,
I encountered a problem during hierarchy loads from ECC to BW:
I get the following in BW:
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
Once I go into ERP and look at the IDocs I get the following message:
Idoc Error 26:
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment E1RSSH does not occur at the current level of the basic type (extension ).
This error can have several reasons:
The segment E1RSSH is assigned to a group whose header segment does not occur.
The segment E1RSSH does not exist in the syntax description of the basic type (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type (extension ).
Can anyone help?

The most basic setting in a BW system is its connectivity with the R/3 system (which is a basis team activity, but BI consultant can always help).
Issue: While creating source system, I am getting an error "Segment E1RSSH does not exist".
Diagnosis
Segment E1RSSH is in the syntax description, but it does not exist.
The issue was that some of the entries in the table EDISEGMENT were missing.
As this a standard table, it is recommended to restore the table from Backup or from another BI system. (Please ask your basis team to do it.)
Now, the significance of the segments: We all know that we require 3 message types in total to communicate with R/3 system. RSRQST, RSSEND and RSINFO.
Now each of the message types has some segments which help in communication.
You can see this segment types in the t-code we30. Just enter the basic idoc type and click on display.
This error is not a common error, but can be useful if at any stage of implementation or support, the table gets disturbed and you have issues with source system connectivity.
Thanks
SM

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.

Unable to import IDoc from ECC to PI 7.1(ESR)

Hi,
I am creating an IDoc to File scenario in PI7.1 . I am trying to import the MATMAS IDoc from ECC to PI 7.1.So under the SWCV -> Imported Objects - > Wizard to import IDod/RFC opens -> I enter the ECC system login details -> But when I expand the IDoc node here,I find no IDoc from ECC ,moreover it throws me an error " component should be attached to some frame or dialog"
Can you please suggest me as what is going wrong.
Thanks,
Venu

Hi all,
I am using PI 7.3
When I Import object and passing parameter like application server, system number, uid and password.
I got this error
Unable to establish connection to R/3 system servertm_TM9_06 (system=00, client=001)
Troubleshooting information:
Is the target system online?
Check the connection data; server name and group fields are case-sensitive
Tips for administrators (see configuration guide for details):
Does the user have sufficient authorization in the target system?
Is the target system configured correctly in etc/services?
See error logs for details
Please help me.

Send IDoc from External System to SAP system

Hi Folks,
I have a requirement to send IDocs from an external system to the SAp system. Basically the external system is a subsystem which is able to send & receive idocs. The external system is currently able to send idocs to SAP system through the ALE layer but now we have to replace it by PI. Now the external system has to send teh IDocs to the SAP ECC system through the SAP PI 7.0.
Kindly let me knowq how I can achieve it.
Regards,
Santosh

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Problem while sending IDOC to File Senario

Hi Experts
 I am having problem while sending the Idoc from SAP R/3 to File
 I have done all the setting in SAP as well in XI but while pushing IDOC
 I am getting error in the transaction sm58 in SAP R/3
" The service for the client 300(My SAP R/3 client) is not present in Integration
Directory"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Send IDOC from Business Connector to SAP faster

Hi Developer!
I need to send a very lot of IDOC converted from XML files from the Business Connector to SAP. The XML files are in different directories pro business partner, but they have a same type (ISU_MSCONS).
My problem, that the import take a lot of time. Only in every 3 seconds (IDOC creation time) gets (or works up?) the SAP one IDOC. I start diferent services pro partner at the same time to import the IDOCs, but I couldnt short the 3 second work time in the SAP. So you can count it easy, that in 1 minute I can import 20, in 1 hour 1200, in 1 day 28800 IDOCs instead of 100.000.
It is really parallel import? Have anybody any idea to make the import more faster. I know (asked the SAP Administrator) so, one BC - SAP connection (Program_ID) has more pools (= threads) in the SAP at the same time.
Thanks any help,
Charlie

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Problem when sending IDOC from ECC to MII 12.0

Similar Messages

Maybe you are looking for