IDOC not there in WE02

Hi Gurus,
I am doing a FILE TO IDOC scenario for taking Material Master data from the MDM system and posting the IDOC into the R/3 system..
The entry is there in MONI with the chequred flag but there is no IDOC in we02 of the R/3 system.
Also , i pasted the payload from teh MONI and checked in the mapping and the test was shown to be successful.
Can Anyone please tell me what can be the cause and its probable solution?
Thanks in advance,
Shweta.

(1) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
The problem is in Technical routing.
Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
Also check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
(2) Error Scenario - ATTRIBUTE_IDOC_METADATA
Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.
Following is further info on those two mandatory parameters.
(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.
(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.
(3) Error Scenario - IDOC not yet created in target SAP R/3 system.
Go to R/3 system and check at Tcode WE05 if the IDOC has been created successfully. If error is u2018"Partner profile not configured" check point 9.
Suppose IDOC did not get created at R/3 end and all the pipeline steps were successful in SXMB_MONI, then go to Tcode : IDX5 in XI and click on Transaction ID field and check the status description which explains the problem.
(4) Error Scenario - Partner profile not configured.
Go to Tcode WE20 in R/3 system and check if the partner profile has been configured correctly and is filled with the inbound parameters.
regards
chandra

Similar Messages

Inbound idoc not displayed in WE02

Hello All,
I have two different sending and receiving SAP system for IDocs. I am trying to learn ALE scenario. For this purpose, I created everything on my own on the sending system viz. idoc segments, idoc type, message type, rfc destination, port, logical system, ALE distribution model & partner profile and a Z program containing the function module MASTER_IDOC_DISTRIBUTE.
When I run the program on the sending side, the idoc is generated with status is 03 (data passed to port).
I am not sure what settings do I need to make it on receiving system. I created the logical system, partner profile, Z function module for inbound processing, registering of the function module & inbound process code & registered it in partner profile for the inbound message type
Please help me know, how to determine this IDoc on receiving side. In WE02, it does not show the IDoc generated by the sending system.
Thanks & Regards,
Saurabh Buksh

Hi,
You said you have used MASTER_IDOC_DISTRIBUTE. I hope you are doing a COMMIT WORK after calling this function. Reason is that this function doesn't do the COMMIT WORK and thus explicit commit work is required after the call.
regards,
Advait

IDOC not displayed in WE05

Hi Experts,
I have successfully run my scenario CSV-pi-Idoc yesterday. IN MOni XML file is Ok. In R/3side (WE05) Idoc generated successfully. But Yesterday night Basis people change R/3 password. Now my problem is in R/3 IDOC not displayed in WE02.
Iam also change password in SM59. But no result. Where can I do changes. can any one help me.
Thanks
Hari

Hi Hari,
Make sure in SXMB_MONI in your PI system the message is showing successful flag in outbound side (ie.. drag the scroll bar to ur right had side and see if you can see checkered flag). If you see any error then go to tcode sm58 (trfc queue) and filter based on dates and u will find error logs in detail and take appropriate action.
Mostly it might be authetication problem so better to check in ur R/3 destination in Sm59 in PI system if your rfc test and authentication test is successfully showing green or not.
Thanks,
Prasanthi.

IDoc not visible in target R3 system

Hello
I am working on File-to-IDoc test scenario where I am sending CREMAS IDoc to R3 system (through IDoc receiver adapter). I performed all the necessary configuration which includes
RFC Dest of type R3 in both the systems
Creating ports in both the systems with port name similar to logical sys name of business system
Creating Partner profile for the above port with Inbound message type as CREMAS
When I am viewing the message in SXMB_MONI it shows successfully processed but Outbound status is still showing as "Message Scheduled on Outbound Processing". Also when I checked on the R3 side using we02, I could'nt find any IDoc over there. I checked in the trace where it states "Async processing completed OK".
Am I missing any configuration on R3 side which is not processing an IDoc?
Thanks in advance.
Regards
Rajeev

Hello
Thanks for the replies but i did configuration exactly as shown in the weblog. My RFC Destination is working fine.Also theres nothing in SM58. Also in SMQ2 "Nothing is selected" that means the message is processed successfully.
In SXMB_MONI it shows status as "Processed Successfully" but the Outbound Status is "Scheduled for Outbound processing".
In addition to this, I tried to test run (through SE37
) the FM "IDOC_INBOUND_ASYNCHRONOUS" in the receiving system with the control paramters of XI and that is creating the IDoc.
Regards
Rajeev

Idoc not showing in R/3

Hi,
Iam Currentl running File to Idoc interface. Message is success in moni also and runtime workbecnh also. But when iam checking R/3 using WE19 tcode by giving date its not showing . It showing like no values found. Can anybody tel me what is the reason?

Hi,
Dont seach with IDOC no in R/3. Check in WE02 transaction not WE19
Search by Date only ........then go under your INBOUND IDOC type node in WE02 in ECC. Also Please check the ECC client no you are posting the IDOC.
Please be confirm in SLD your ECC business system client . And search the IDOC in ECC in same client no.
You can also chek in ID check Adapter Specific Message attributes for ECC business system & also click the Compare with SLD Option.
You can found this option after opening Business system in ID from menu.

IDOC not visible in IR but metadata successfully imported

Hi,
I have this wiered issue.
I want to import IDOC WPUSKR01 (cashier productivity) from BI.
But when I connect to BI system from IR to import Idoc structure, this IDOC is not visible.
But I can manually import the metadata from BI in idx2.
Now how to import this in IR?
I have imported other Idocs (like WPUBON) before and did the scenario successfully for BI.
Regards,
Anirudh Vyas.

Hi,
In BI Tcode we82 I have manually added the entries for WPUKSR01. Now Idoc is visible when importing in IR.
I have checked all the segments in we31, they are all released.
But it gives error:
Error: IDoc type WPUKSR01 contains errors (unable to read segments)
Then, I checked in R/3, there also WPUKSR01 was not there in we82. I manually added there and I was successfully able to import it in IR.
But the same thing is failing in BI. I have SAPALL permissions in all the systems.
Can I use Idoc imported from R/3 in scenario for BI?
regards,
Anirudh.

Idoc not found in the receiving system

Hi Experts,
In the sending system idoc status is 03 (Data passed to port OK), but in the receiving system the idoc is not there. How to rectify this error?
Thanks & Regards,
Soumya.

Hi Soumya,
Check the RFC connections, becoz in the sending system once the IDOC is sent the status becomes 03 it does not check whether the IDOC has sent to the received system, if there are any errors before sending the IDOC it will not send and the status will be 01, so check the RFC connections at sending and receiving systems.......
Reward points if this helps............
Regards,
Ravi G

IDOC not Received at XI

Hello folks ,
I need to send a idoc from r/3 to xi. i have made all the necessary configuration in r/3. iThis s a production sytem ....have checked on R/3the IDOC is succesful at we02
checked BD87- IDoc sent to SAP system or external program
SM58 no errors...
wen i checked at XI with the particular IDOC number iI dont find an entry what could be the reason .How to resolve the same.
Regards,
Robin

Thanks guys .. thanks for ur quick response
Solution : Had to run this job RBDMOIND ...(particular IDOC NO, was not sent to XI )
Edited by: Robin on Jul 30, 2010 3:22 PM
Edited by: Robin on Jul 30, 2010 4:43 PM

Idoc Not received?

Hi
During data loading , I got one Error that Idoc Not received.
What will be the cause of problem and How to resolve it?
Regards & Thanks
Durai

Hi Robert Negro !
I checked , Dump has been there.
How can I resolve?
what will be other causes apart from the Dump?
Thanks A Lot .
Regards
Durai

Outbound Delivery IDOC not updating values from MKPF for goods receipt

hi all,
I have a question say I am generating an outbound delivery IDOC. which has fields Goods Issues & Goods Receipt date retrieve from MKPF(BUDAT).
say when i post goods issues, MKPF is updated and IDOC is gernerated with issues date taken from MKPF.
and when i tried to goods receipt, MKPf is updated and IDOC is generated but no receipt date taken from MKPF. then i check in MKPF, date is there and then once again I triggered the IDOC, receipt date comes......so my doubt is the time issues say when IDOC is triggeres, no value in MKPF...but when i check the time it is 4 mins difference from the MKPF time and the IDOC time...
and also 1 more thing for doing goods receipt, we do in different transaction and for good issue we do in Vl02n.
so bit confused.
kindly help

True , but in BKPF only Issues date are stored not the receipt date say if the document type = WE.
Please let me know is there any other options to fetch rather than MKPF.
because at the time of IDOC generation, there is not entries in MKPF. I tried to do using WAIT UP TO 50 seconds , even that didnt work.
Please guide me
thanks

MATMAS01 IDOC not reaching to SAP XI via report program.

Dear Experts,
WE are facing small challenge.
I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
Problem:
MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
What could be the wrong ?
Thanks
Divyesh

When sending Idoc from R/3,
Settings at R/3
create one port at WE21,
Create Partner Profile for Outbound Message type in WE20.
settings at XI
Create one port in IDX1
Import Matadata in IDX2.
Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
Check these settings & send test idoc using WE19.

Idoc not getting transferred

Hi All,
I am trying to learn ALE,EDI and Idoc, what I did is I try to esatblish a connection between two clients using SALE and SM59 and then created the partner profile, now what I was trying to do is sending a customer information from one client to other using idoc, the tcode for this is BD12, on the sending system it's showing me that the idoc has been moved succesfully but when I logged on to the recieving client I didn't see my idoc over there. can anyone of you please tell what possible error is there in it and can also guide me through the step by step configurtaion of setting the network connection between two clients.
Thanks,
Rajeev

hi,
Go and check in receiving system whether the partner profile that u hav created is correct or not.... and in partner type LS -> inbound parameters -> double click message type -> check whether the process code is correct or not.
Thanks.
Arunprasad.P

Idoc not getting post

Hi Friends,
i am using transaction WPUK , there if i enter eann number starting from 1, for ex. 1WMDP000023 Then idoc posted but
if i enter eann number starting from 0, for ex. 0OA103403929908 , idoc not gettign post , error is eann number not exist or not maintained against the material number, but i have already maintained via MM42 in basic view.
pls suggest what i should do, i am already debugging but can't resolve it.

Hi Medha,
Give the leading zeros and check.
Regards,
madhu.

IDOC not getting genrated

Hi Experts,
Need your help.
In idoc creation, I have changed material description, its generating master idoc but communication idoc not getting generated.
Please suggest me the solution,
Regards,
Rachna

Hi,
Idoc's are generated based on the payment method and any how in the payment method we will give the required curriencies which are applicable for that payment method.
And u had mentioned as WE05 for IDOC list, but actually the T.Code for IDOC list is WE02.
Check the settings, it has to come. Reply back for more clarifications.
regards
srikanth.

IDOCS not reaching XI (IDEX-GE Content)

If I send IDOCS from I/SU to XI no IDOC is reaching XI.
IDX5 doesn't show any incoming IDOC. There is no error neither in XI nor in the log viewer of Visual Administrator.
The Sender system says in WE02: Datatransfer to port ok.
I checked the port and its RFC: The correct RFC (the one to XI) is set and RFC is working (sm59: test connection is ok, Remote Login from I/SU to XI is working).
IDOCS from a second backend are visible in IDX5. This backend is configured like the first backend (same RFC).
Did anyone have a solution?
Thanks
Ralf

Hi,
These are the complete steps for IDoc communication, check if you have missed any one...
SAP XI
1) RFC Destination (SM59)
     a) Choose create.
     b) Specify the name of the RFC destination
     c) Select connection type as 3 and save
     d) In the technical settings tab enter the details SAP SID/URL and system number#.
     e) Enter the Gateway host as same details above SID/URL.
     f) Gateway service is 3300+system number#.
     g) In the Logon /Security tab, enter the client user & Password details of Destination system.
     h) Test the connection and remote logon.
2) Create Port (IDX1)
     a) Select create new button
     b) Enter the port name as SAP+SID (The starting char should be SAP)
     c) Enter the destination client.
     d) Enter the RFC Destination created in SAP R/3 towards other system.
     e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
     b) IDOC Message Type
     c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
     a) Choose create.
     b) Specify the name of the RFC destination
     c) Select connection type as 3 and save
     d) In the technical settings tab enter the details SAP SID/URL and system number#.
     e) Enter the Gateway host as same details above SID/URL.
     f) Gateway service is 3300+system number#.
     g) In the Logon /Security tab, enter the client user & Password details of Destination system.
     h) Test the connection and remote logon.
2) Create Port (We21)
     a) First Select Transactional RFC and then click create button
     b) Enter the destination port name as SAP+SID (The starting char should be SAP)
     c) Enter the destination client.
     d) Enter the RFC Destination created in SAP R/3 towards other system.
     e) Save
3) Create Partner Profile (WE20)
     a) Create New
     b) Create the Partner no. name as same the logical system name of the destination system.
     c) Select Partner type LS
     d) Enter details for Type: US/USER, Agent, and Lang.
     e) Click on the + button to select the message type.
     f) Select Partner no. and LS which ever create above.
     g) Select Message type
     h) Select Process code related to the Message type.
     I) save.
In SLD
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system
Name.
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
Check these steps
Regards
Vikas

IDOC not there in WE02

Similar Messages

Maybe you are looking for