IDoc reciving problem

Hi Experts,
I want to send data one SAP server to another SAP server, At sender End IDoc is being sent successfully but at receiver end no IDOc is receive. plz suggest some solution.

Hi Ravinder,
If the IDocs have been sent successfully from the sender system and not received at receiver side, then they must be RFC queue.
Can you please tell us the status of the Outbound IDoc??
If it is '03' (Data passed to port OK), then execute T.code 'BD75' which will change the status of the IDocs to status 12.
If it is still not passed then execute 'SM58' t.code to see the Status text which will help you in analyzing the error.
Please revert back if facing some issue.
Cheers
VJ

Similar Messages

IDOC performance problem

Hi All,
Currently I come across a idoc performance problem,in we20,the idoc inbound process code invoke BDC manner.
the detail as follows:
(1)Seebeyond send the idoc to SAP side.
(2) Idoc added(Status 50)
(3)IDoc ready to be passed to application(64) 11:06:27
(4)IDoc passed to application(62) 11:21:22
My question is why the process time spend so much when idoc status from 64 to 62,what is the affect factor.whether the process time include BDC execution time.Thanks.

Hi,
I think it has taken much time to get the status 62 from 64 status.
In the partner profile WE20 transaction for this interface you have used Collect IDOC's option. If that is the case till your background runs it will get into 62 status.
If you use trigger immediately option in WE20 transaction then as soon as the IDOC is in 64 status it will be processed that is it will 62 status immediately.
I hope I have answered your question.
Thanks,
Mahesh.

Business system for idoc reciver communication channel.

hi gurus,
iam doing one file to idoc scenerio.
for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
pls guide me .
warm regards.

Hi
You can use th Buiness system as a receiver for IDOC.
Making sure
1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
2. Use the same LS name for the BS pointng to FIle in the SLD.
Complete the IDOC configuration from XI
1. Create the RFC dest from XI to ECC
2. Create the Trfc port and call this RFC dest created..
3. Use this Trfc port in the IDOC receiver
On ECC:
Make sure the Partner Profiles is created properly.
it is suggested to use always the business systems when you deal with IDOC and Proxies.
Edited by: Nisar Khan on Feb 27, 2008 1:31 PM

XI 3.0 IDoc Adapter Problem

Hello,
I have a problem to establish an Idoc communication between SAP R/3 4.70 and SAP XI 3.0.
Following systems I have defined in XI SLD:
Sending R/3: HS3CLNT100
Receiving XI: X30CLNT100
In the Idoc (type orders) the sending port is "SAPHS3".
I have configured the XI 3.0 IDoc Adapter as follows.
- IDoc Port "SAPHS3"
- I have loaded the IDoc Metadata
- ALE Distribution model in sending R/3 is defined
- In the Integration Directory I have defined a "service"
This was done by upload an existing business system
"HS3CLNT100" including the automatic generation of
communication channels.
This should "normally" be all, what I have to define.
PROBLEM
========
When SAP R/3 tries to send an IDoc into SAP XI it will fail. In SAP R/3 transaction SM58 I can see following message:
"No service for system SAPHS3 client 100 in Integration Directory"
I don't think, it's normal to configure XI business systems with the same name as the IDoc port!?
Thanks in advance
Klaus

Hi James,
yes in the IB (Configuration) I have generated a service under "services without partner". Service name is "HS3CLNT100" and he includes the generated receiver channels. Or do you mean something different?
Klaus

File to Idoc Mapping Problem

Hi all,
i'm getting an error from SXMB_MONI in a scenario File to Idoc.
I have done the mapping from source file and Idoc CREMAS03, when i try to test from Integration Repository it's all ok, but when the scenario is executed i find this error in Idoc Adapter :
<SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
The field BEGIN in idoc structure is filled with constant value 1, than i dont understand the error.
This is the xml source file :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Vendor xmlns:ns0="urn:tbit40:workshop:group01:legacy">
- <Address>
<Country>IT</Country>
<Zip>001</Zip>
<City>ROMA</City>
<Street>SATTA</Street>
</Address>
<Currency>USD</Currency>
<SearchTerm>TEST</SearchTerm>
<LastName>GUIDA</LastName>
<VendorNumber>44332</VendorNumber>
</ns0:Vendor>
Any help is really appreciated.
Thanks.

Hi all and thanks for your answer.
My problem is that for what i can see all Idoc attribute (like the attribute BEGIN) are mapped with constant value.
In taget source i can see : BEGIN = Constant([value=1])
What i dont understand is why when i execute the scenario it ends with this message :
<SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
It seem to me that the tag BEGIN is not filled with value, i also tried to copy the source xml file directly from SXMB_MONI (from payload) and test it in Integration Repository mapping section, but here is all ok and the test end succesfully.

Complex IDOC mapping problem

Hello,
I'm stuck with a complex mapping issue that I can't figure out. I'm trying to pull 0..N Variant Configuration segments from the ORDERS IDOC and map it into a 0..N XML segment.
The inbound ORDERS IDOC is structured like this:
IDOC
...E1EDP01 (Item segment 0..N)
......E1EDP19 (Product data 0..5)
...........Z1EDPIT (Configuration Data 0..N)
.................ATUE1   (Description)
.................ZCODE   (Category)
.................RTWTB (Value)
Target XML:
Order
....Item (Item segment 0..N)
.......Product (Product data 0..1)
............VariantConfig (configuration data 0..N)
....................Description
....................Category
.....................Value
I need to create a new VariantConfig segment in my XML for every Z1EDPIT segment for that PO Item. But I need to skip any Z1EDPIT segments when ATUE1 = 'OPTIONS' or when ATUE1 does not exist.
The problem I'm running into is that my mapping is capable of creating the VariantConfig segment under those conditions but the following mappings used to create the Description/Category/Value are unable to skip the Z1EDPIT segments.
For example:
IDOC
...E1EDP01
......E1EDP19
...........Z1EDPIT
.................ZCODE     = REQT
.................RTWTB     = 5644
...........Z1EDPIT
.................ATUE1     = Finish
.................ZCODE    = REQT
.................RTWTB    = 7712
The output XML should read:
Order
....Item
.......Product
............VariantConfig
....................Description   = Finish
....................Category      = REQT
.....................Value          = 7712
So I determine to create the VariantConfig segment if ATUE1 exists and does not equal 'OPTIONS'. So my mapping creates one VariantConfig segment because the second Z1EDPIT qualifies. But each element within that node is reverting back to the first Z1EDPIT segment.
I thought the top of the Node (VariantConfig) would determine the context for the following fields. Therefore, when the 2nd Z1EDPIT segment generates the VariantConfig node then the elements should refer to the current context of the root node (VariantConfig).
What tools does PI's mapping provide to resolve a situation like this?
Any suggestions?
Thanks,
Matt

Job,
Thanks, for the responses!
What do you mean by "add a context change for the fields".
Is there some mapping function to add a context change or is this a UDF I need to write to handle the context changes when ATUE1 is missing or equal to "OPTIONS".
In my example:
VariantConfig:
ATUE1 (E1EDP01) >mapWithDefault [OPTIONS] equatsS [OPTIONS] -> Not ->createIf->VariantConfig
Sub Element
Category
ATUE1 (E1EDP01) >mapWithDefault [OPTIONS] equatsS [OPTIONS] -> Not ->ifWithoutElse>ZCODE->Category
The problem is that this does not keep the ATUE1 and the ZCODE in the same Z1EDPIT segment. So I get the first ZCODE value when I only want the 2nd.   Even if I insert a context change I can't say for sure that next time I won't have 5 Z1EDPIT segments missing the ATUE1 segment before I find my first good segment that I need to map.
...confused...
Thanks,
Matt

XI IDoc adapter problem. MESSAGE.DUPLICATE_DE

I have a problem with the IDoc. When sending the IDoc from the PI to ERP - system throws an error (ta SXMB_MONI):
<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><SAP:Error><SAP:Category>XIProtocol</SAP:Category><SAP:Code>MESSAGE.DUPLICATE_DE</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation <SAP:Error><SAP:Category>XIProtocol</SAP:Category><SAP:Code>MESSAGE.DUPLICATE_DE</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What could be the problem?

The HTTP code 500 indicates internal error in your application.
Check on to the stacktrace in
<local drive>:\usr\sap\XXX\YYY\j2ee\cluster\server0\log
check note number 804124 at service.sap.com
You can also check:-
Ping the receiver host from XI server.
Have a look at the SMICM->Trace file
Test the connection of AI_RUNTIME_JCOSERVER
HTTP 500 can be any problem at receiver side. Are you sure, that the payload fits to the receiver requirements?
Also i looked up this message "MESSAGE.DUPLICATE_DE" this comes when duplication of message takes place.
Try chaning the input data.
Venkat.

IDOC Receiver problem with 7.11 and ECC6

Hello,
we have a IDOC_2_IDOC scenario on old XI system which worked fine.
We are moving now to PI7.11 and get the problem, that all IDOCs in the receiving ECC6 system
go to status 51 "No status record was passed to ALE by the application"
It seems to be a problem of processing of too many IDOCs at the same time,
because if there is enought ime between the IDOCs the the procsing in ECC6 works.
Only if too many IDOCs are sent from PI to ECC6 then I get this error.
I have checked aRFC and tRFC options in SM59 but there is no difference.
IDOC packing is not activated on sending system and on PI.
At the moment the scenario should work as is worked on 7.0......
Any ideas which setting is different or where to look?
best regards
Werner

Hello,
which ALE settings do you mean???
on PI or receiving ECC6
PI:
here we only use SM59, IDX1, IDX2.... for IDOC adapter
ECC6: only partner profile INBOUND PARAMETER
On the sending R/3 system I can not change something.....and there was no change.
best regards
Werner

IDOC Config Problem... Transaction BDFG giving error mesage..

Hi ,
Transaction BDFG, If i click on the change button i get an error as Message (Idoc Message Name) has not been generated,Furthur Processing is not problem. Reason being in Table EDBG the Generated field for Idoc Message is blank.
How can i get in generated.. Do help..

Hi ,
Could you please check the below links.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_erp2004/helpdata/en/00/a814b5d05b11d6b2ca00508b6b8b11/content.htm
Regards,
Ratheesh BS

Inbound IDoc(HRMD_A07) problem in delimiting the infotype records

Hi All,
I am using Inbound IDoc (HRMD_A07) approach to update infotypes. I found that I am able to create a record in an infotype, but there is a problem in delimiting the infotype.
Please help me out in case I am missing something.
Thanks,
ABAP_DEV

Hi,
Did you get this resolved. Even i'm facing this issue. Is it a config or do we have to do something in the IDOC.
Thanks,
Jilly

IDOC Inbound Problems

Hi there experts,
I've been through a lot of blogs, websites, google, SCN and others, but I can't find a solution for my problem.
We need to create an interface ECC > PI using IDOC.
All config were done to make it happen.
When the IDOC is sent to PI (I've used WE19 for tests), it goes to PI and when I check BD87 I always have those errors:
Error 56 : External segment name E2FIKPF007 cannot be interpreted
Error 60 : Basic type FIDCCP02 does not exist
So, as you can see, we are using IDOC FIDCCP02. It's basic data was configured on PI IDX2 and it is loaded just fine:
What could be possibly wrong?
Thank's!
Flavio

Hi Ramkumar, thank's for the fast response.
When we go to IDX2, select the IDOC and choose to show the details, we have an option to show all segment versions. And there is E2FIKPF007.

File to idoc scenario problem

I am trying to do FILE TO IDOC scenario, i am getting error called, UNABLE TO CONVERT SENDER SERVICE TO AN ALE LOGICAL SYSTEM.?
could anybody solve this problem?

Murali,
You get this error when Adapter specific attributes are missing..
Maintain Adapter Specific Attributes for business system in Integration directory.
Select your business system...Then select Service-->Adpater Specific identifiers.
from right hand window..
Set Logical System ID(of R/3 system), R/3System ID and client.
Let us know if you need more details.
Nilesh

ALE/IDOC configuration problem

Hi Gurus,
It will be nice if you please help me finding the flaws in my configuration that is not allowing me to get a desired output.
Let me make it step by step:-
1. My desired output:- To see destination partner type as "LI/LF/ vendor name" for the Inbound IDOCs when an IDOC is starts it journey from "KU/WE/customer name" or vice versa
2. Present output:- Inbound IDOC always comes to "LS/ /TS90CLNT800". It means in my case inbound IDOC always comes to Logical System LS instead of LI or KU
How to configure it properly so that I can pass the Inbound IDOCS to other partner type except LS.
Please help.
Here what I have done so far as setting:-
1. Created a Logical System TS90CLNT800 using transaction SALE
2. Assigned it with client 8003. Created one RFC named tZRFC with connection Type "3"
(R/3 connection) using trxn SM59
4. Created a port ZEDI and assiged tZRFC using trxn WE21
5. Created partner profile for Vendors in partner type LI and for Customer in partner type KU
6. Because of getting error " no partner profile for ZEDI LS found" therefore created inbound parameters in parter profile LS for each Message Type.
I am processing IDOC within same client 800 ( both inbound and Outbound)
But I want the Inbound Idocs should come into partner type LI if the the Outbound IDOC is sent from KU and vice versa.
Please help me what config I need to do.
Amit

Hi Sruthi,
Thank you very much for your time that you have spent for my problem.
So far I created these type of partner profiles and they were working in the following fashion.
Partner Profile created in WE20:
Partner Type = LI, Partner Number V001 ( Vendor Number)
Partner Type = KU, Partner Number K001( Customer Number)
Partner Type = LS, Partner Number ZEDI ( Logical System)
I created one Logical System ZEDI and assigned it to Client
tRFC created in SM59:-
Connection Type = R/3 Connection, Name tZRFC
Port created in WE21:-
Port Name ZEDI (again) and assigned with tZRFC.
BD64 not used so far
Now If I add Message type ORDERS in Inbound Parameters of Partner Type KU and Outbound Parameters on Partner type LI system fails.
If I add message type ORDERS in Inbound Parameters of Partner Type LS and Outbound Parameters on Partner type LI system works fine.
Whenever IDOCs are being processed partner profile are being shown as follows:-
Outbound IDOC : LI/LF/V001 ( Receiver)
Inbound IDOC : LS/ /ZEDI ( Sender)
My question is that can I make any setting so that I get the following:-
Sender ( LI/LF/V001)
Receiver ( KU/WE/K001)
LF and WE are respective partner functions
Regards,
Amit

IDOC Posting problem Through Billing Output Type

Dear Friends,
I have strange problem for IDOC posting through Billing Output Type.
We are using same output type for Partial / Final settlements through Billing Output type.
For Final settlements IDOC posted and generated account document is perfect, But for Partial settlement we are always getting message data is missing "No batch input data for screen SAPMF05A 0700 (Message no. 00 344)".
I tried to reprocess same IDOC in foreground then we are getting message "Posting is only possible with a zero balance; correct document"
(Message no. F5 060).
Could you please suggest me
Thanx in Advance.

solved

Idoc inbound problem

Hi Friends,
I am facing a problem in IDOC inbound processing.
My scenario in SALES PER RECEIPT - POS like this: I have to read XML (From PC) file and i have to post it.
I am using Idoc - WPUBON01. After reading XML file i used Function module to distribute - MASTER_IDOC_DSTRIBUTE.
In we02 i checked Idoc is generating but status showing 29.
So run the report RSEOUT00. But i am getting message like 'No idoc is selected for processing'.
Plz help me what i have to do. I created port also.
Regards,
P. Kumar.

hi kumar,
if u get status 29-error in ale service- check partner profile first.if it exists check ur logic where u modify control record,else create partner profile and restart again.
Reward if usful.
Thanks,
Srikanth.A

IDoc reciving problem

Similar Messages

Maybe you are looking for