Error in Sending IDOC

Hi,
i am working with the Scenario IDOC to IDOC using middleware PI.
Done with Whole Process .
But when i Sending an IDOC through WE19 it went Succesfully(i checked it in WE05).
But when i checked in SM58. then there is an error in sending my IDOC.
Transaction IDX1: Port SAPETS, client 800, RFC destination contain error.
Please let me know where might me the problem ??
Thanks
Deepthi

Hi,
Check the RFC destination connection from PI to ECC... looks like there is connection from PI to ECC to retrieve the metadata....
HTH
Rajesh

Similar Messages

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

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

SM58 - Error while sending IDOC

Hi,
I got the following error while sending the IDoc to a XI system.
"No service for system (Idoc adapter port), client 800 in Integration Directory"
Please let me know whether this is due to an error in network or application error.
Note: remote logon is not successful in the XI system
Thanks in advance
Edited by: RPN on Jul 1, 2008 11:46 AM

Hi RPN,
Plz do check the following things :
1. Verify the logical business system in SLD.
To verify --- Go to SLD home page ---> Technical Landscape --> Select Web AS ABAP --> Select the technical system --> Clients ---> Click on the client you used as Business system --> Here look for the logical system is defined or not.
2. Open ID---> Click on Objects --> Service Without party/Party > Double click on business system>On the tright side--> Service --> Adapter specific Identifiers ---> Check IDoc Adpater, Logical System.
3. Refresh the full CPA Cache (userid must be XIDIRUSER/PIDIRUSER)
http://<hostname>:50000/CPACache/refresh?mode=full
Regards,
Vinod.

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.

Company code does not exist error while sending idoc

Hi Expert
I am trying to send idoc from one client(800) to another client(810).I have faced error Company code does not exist, searched scn ,Got solution if company code does not exist in reciever system(810 client) ,it will show this error .Then i have tried to give specific company code which is exist in 810 client also .But same issue is coming . So what exactly the issue can any one say .
More Info:FI(Finance) header items and line items are sending .
Thanks & Regards

Hi,
Your company code not activated for material management. Few pre-requisites to create material and one is to activate company code for material management
Please activate in T.code: OMSY,
[For example: For Fiscal year variant K4]
In OMSY steps, u have to enteru2026u2026u2026..
Company Code (enter your company code name 2001)u2026u2026u2026u2026u2026.
Company Name..
Fiscal Year of Current Period 2009
Current period (posting period) 03( )
Fiscal year of previous period 2008( will come automatic)
Month of previous period 02( will come automatic)
Fiscal year of last period of previous year 2008
Last month of previous year 12
Allow Posting to Previous Period (Back posting)
Disallow back posting after a change of period
Now create material with T.code; MM01
Regards,
Biju K

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.

Error during sending IDoc from XI to R/3

Hi,
I get following error (transaction: sxmb_moni), when I try to send a IDoc from XI to R/3.
Error: Transaction IDX1: Port SAPI14_921, client , RFC destination contain errors.
When I go to transaction sm 59 and start this rfc-destination so it works fine.
Can anybody help me please?
Thanks.
Regards
Stefan

Hi,
I dont now how you pushed the IDOC form R/3 to XI..
Follow this particular way ....
Go to WE19 and execute the IDOC which you want to send and clicl the tab startoutboundprocessing....
then it hits the XI after couple of minutes and then
Go to the XI in that IDX5 where you can see the IDOC messages....
Amaresh

Error during sending sales idoc

hi all,
i m getting error during sending idoc for sales.................
Error:Check value field assignment for Condition PN10.....
How to solve this...?
Regards,
Imran

friends.......argent.......

Sending IDoc from R/3 to XI -ongoing

Hi,
With reference to my previous errors while sending IDoc to XI from R/3 system. I have resolved errors with help of Seshagiri and Kummari advise and help. But now I am getting new kind of error, while sending IDoc from R/3 its getting passed from R/3, but while checking it in XI throug SXMB_MONI I am getting below error:
<?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>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_POCreateIdoc_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_POCreateIdoc_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any one advise me on this?
Thanks & Regards
Manish

Hi,
There were so many Mapping Objects under different Namespaces and under that different Message Mapping trees.
Under one tree I have tested the XML message and found the below error:
Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Kindly check if this is the correct error I am getting related to SXMB_MONI error message.
Regards,
Manish

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 sender sap idoc side

Hi Experts,
            1, When the sender post idoc to PI it shows the following
              error in sender sap system.
               Error:No service for system SAPQ01 client 118 in integration directory
            2, Is it possible to post the idoc to PI With out activating the integ directory Object in PI(Integ.repoistery activated).
            3, If possible, where can i see the idoc datas in PI before activation.
Thanks

Hi Raja,
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 Transaction SLDCHECK.
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 .
Regds,
Pinangshuk.

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

IDOC Error - Copy Sender from Payload: Sender Is Missing in Payload

Hi,
I have following scenario.
SOAP adapter ---> PI -
> IDOC Receiver -
> ECC
THe IDOC has a required node that is disabled and IDOC revicer communication channel has checkd following options.
Apply control record value from pay load
Take Sender from Payload
The soap message is mapped to IDOC structure. While testing I received following error.
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy Sender from Payload: Sender Is Missing in Payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Copy Sender from Payload: Sender Is Missing in Payload</SAP:Stack>
If you have seen similar error and please let me know how to trobleshoot. I appreciate your help.
Thank you,
Balaji

Thank you for the response. I can enable EDI_DC40 segment and map required following values.
· SNDPRN
· SNDPRT
· SNDPFC
· RCVPRN
· RCVPRT
However as we move transports to different environemnts the above values changes and I can't hard code in the mapping.
My questions is how can I map these values such that when transport moves across different environemtns the mapping valaues are still good. Please let me know.
Dont enable EDI_DC40 and dont select take sender ,receiver from pay load option,apply control record values from pay load.
this case IDoc adapter reads values from configuration time andno problem after trasporting to quality or prod.
Regards,
Raj

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML

Hello Rescue Team,
I am facing the following error :\
16.06.2014 23:22:42.164
Error
Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.166
Error
MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Exception caught by adapter framework: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
16.06.2014 23:22:42.190
Error
Transmitting the message to endpoint <local> using connection EDISeparator_http://sap.com/xi/XI/EDISeparator failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZORDERS10>: state=READING_FIELD_VALUE_TAG, charPosition=526, lineNumber=1, columnNumber=527
and the payload transferred is as attached in the attachment below.
I have refered various blogs, however I am still not able to understand how to get the exact location of the error location..According to me, the value that is giving trouble is OTH in <BSARK> however I have checked the permitted values for BSARK on ECC and OTH is maintained.
Can you please help how I can resolve this error.
Thanks
Saurabh

Hi Guys,
This is solved..I corrected the date format of the ZZTIME segment from 1157 to 115700.
Thanks
Saurabh

Error in Sending IDOC

Similar Messages

Maybe you are looking for