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

Similar Messages

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 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

IDOC not displayed in billing document

Hi Experts,
I have a issue about the outbound idoc's generated from two different billing document.
I can see the idoc's from these documents though the path Goto>header>Output ---> Processing log.
But if i check the services of object button for one billing document, i can see the same idoc.but for the other document, its not displaying idoc number....in the relationships button..
What could be the cause?
What is the difference between these two documents ?

Dear Mr. Kapil and Madhurao,
Thank you for your help and quick response.
I followed your instaructions and found that the option "Relevant for Order-related billing - - Status acc. to order Qty" "B" is already maintained.
Also, i have to mention that this is not the first time we use this service material in our orders and we weren't facing any problem. This is the first time we face such issue.
so please let me know if there's any other option to check.
Thank you

Inbound IDoc not getting generated in XI System

Hi all,
I have created a scenario following the given weblog:
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
The first half of this scenario is working fine and the idoc data is getting posted into the the oracle table successfully.
The business process is successfully sending the acknowledgement IDOC 'ALEAUD' to the XI server using an HTTP Receiver Channel.
The problem is that no inbound IDOC can be seen in the XI system using tcode we05.
Next the xi system has to send the same IDoc to the R/3 system. But as no IDoc is getting generated in XI, nothing gets sent to R/3.
Can anyone suggest what could be the possible error.
Pls help.
Regards,
Neetu

Hi,
You will not see that IDOC in WE05 of the XI system. You can see that only in SXMB_MONI. XI system will not store any IDOC. When it enters XI it is a XML message and it will not post any IDOC that you can see in WE05.
If you need to send the IDOC back to R/3 system, you can use BPM and send back the IDOC to R/3. If you need few details from Oracle tables that is to be sent back to R/3 then get those values from Oracle tables and fill in the same IDOC and send it back to R/3.
Try this and let me know.
Thanks,
Prakash

INBOUND IDOC not updating the basic data field which is created newly

Hi,
i am creating an inbound IDOC for material master creation in that in basic data1 i have created 2 custom field in general data 1 is updating and another is not updating with the value in iDOC.
User exits codes are fine. but data is not updating.
can some one help hw to resolve this..
regards,
thanigai

Hi,
Are you Debug the function module in Process code of IDOC and use COMMIT WORK in that Function module.

Inbound IDOC not creating B007 relationship (HRP1001)

Hi,
I have an inbound IDOC containing object type S (Position) and object type C (Job), plus various relationships including A007 and B007 between the Job and the Position.
All of the relationships get created except the B007 i.e. the Position cannot link to the Job? This is happening for some jobs only....
We checked with all the possible testcases but could not find the clue....
Kindly let me know if anyone have answer ??
Thanks in Advance.

Glen,
Thanks for your Quick response.
Firstly I would like to tell you that the relationship is not created for only couple of Jobs which were existed in the system. But if I do same by creating new records(jobs) its flowing perfectly.
It's giving neither error message nor the Subsegment for this created Object.

Inbound Idoc not getting posted

Hi,
I am facing a problem in posting an Inbound Idoc of Baisc type INVOIC02 and Message type INVOIC.
The Idoc stays in status 51 and the error is "Function Code cannot be selected".
I have checked the Function module, it is already assigned to the process code.
Please help me.
Thanks in advance.
Regards,
Rachit.

Hello Kristine,
I'm "afraid" to make any suggestions if you say you have checked the ALE configuration more than 3 times....
However the message you are getting suggests the client specified for the partner system is not correct. If you double click on the Target system in the overview of transaction SM58 you will go into the RFC destination; is the client specified there really ok?
If all is ok you might you in the debug mode: Copy the transaction id from the overview and goto SE38. Put a break-point in program RSARFCSE (if you don't put a break-point before you execute you will have a hard job to get there because it is a system program). Then start the program using the transaction id and set 'Forced'.
Regards,
John.

Inbound IDOC:Not able to create OBJID while testing basic type HRMD_A07

Hi Friends,
I am trying to test creation of organization data (HRP1000) for inbound idoc via tcode WE19 using basic idoc type HRMD_A07.I am using inbound fm IDOC_INPUT_HRMD.After test data entry,The idoc status is showing as 53 but in the database table HRP1000 objid is blank.It is not creating objid.can any body suggest solution for this.In this case,i want to create objid internally by the system.
Thanks,
Rajesh Kumar
Edited by: rajeshvatsa2005 on Feb 17, 2011 9:03 AM

Hi Rajanidhi,
Thank you for following up!
Perhaps optomizing the choice of forum for the questions could also help somewhat, in addition to following up on them. For example [this one|Forgot username & password; would have enjoyed more knowledgable attention in the NW Admin or Security forum.
Hope that helps in future,
Julius

Inbound IDOC not Triggering Immediately

I am processing an inbound idoc using startrfc, EDI_DATA_INCOMING. It posts the idoc, but stuck with status 64. Partner profile set to Trigger immediately. Why will it not process immediately? I can execute the RBDAPP01 to handle, but prefer immediately. Is there something on the EDI_DC that needs to be set?

Oh, unfortunately not with startrfc. I overlooked the startrfc word in your post.
You can check this SAP note 168276. It talks about The event receiver linkage not activated in Customizing. (t-code OYEB)
regards,
Advait

Idoc not displaying check number

Hi Gurus
I am running f110 program to make a payment, but the idoc does not have the E1EDK12 segment that we use to carry the check number. Rest all information looks fine in the idoc. only this segment is missing. And also we have this problem only for one Account ID (CAD) of the House bank, other Account ID(USD) displays the check information correctly.
Do any one know why this is behaving so...?
Thanks
Princeoflight

Hi
May be you are using custom outbound program, check with ABAPER- if any hard coding is in relation to CAD in the program.
VVR

Inbound IDOC not getting posted in database

Hello All,
I have a similar problem below:
http://www.sapfans.com/forums/viewtopic.php?t=59840&highlight=inboundaleconfiguration
Currently, I have distributed exchange rates from my sending system to my receiving system. When I check on the IDOC status, it is set to status 03 (Data passed to port OK) but on the receiving system, I am unable to find any IDOCs received.
I have checked more than 3 times the ALE configuration and I'm really stuck now.
I have already looked in to tRFC Queue (SM58) but I don't know how to trace the errors. The message I'm getting in SM58 is "Client M88 is not available. Please choose an existing client." However, I tested the connection from the sending system to the receiving system and it works OK.
I'd appreciate any help.
Regards,
Kristine

Hello Kristine,
I'm "afraid" to make any suggestions if you say you have checked the ALE configuration more than 3 times....
However the message you are getting suggests the client specified for the partner system is not correct. If you double click on the Target system in the overview of transaction SM58 you will go into the RFC destination; is the client specified there really ok?
If all is ok you might you in the debug mode: Copy the transaction id from the overview and goto SE38. Put a break-point in program RSARFCSE (if you don't put a break-point before you execute you will have a hard job to get there because it is a system program). Then start the program using the transaction id and set 'Forced'.
Regards,
John.

I can create material using inbound Idoc of type MATMAS01, but not MATMAS05

I can create material using inbound Idoc of type MATMAS01 in WE19, but MATMAS05 failed. In fact I used same data ( different material number), and same inbound function, but got different result.
What is different between MATMAS01 and MATMAS05? Is there some configuation need for MATMAS05?
My system is ECC5.0. Thanks.

Hi, nagaraj
this is inbound IDoc, not outbound IDoc, so we can't assign Basic type in WE20, only can assign Message type.
In WE82, there are 5 records about Messagetype MATMAS:
     Message type   Basic type     Release
      MATMAS         MATMAS01        30A
      MATMAS         MATMAS02        30D
      MATMAS         MATMAS03        40A
      MATMAS         MATMAS04        46C
      MATMAS         MATMAS05        470
   I think it should be ok.
In WE57, there 2 records are exist:
   FM_name                 BasicType       MessageType
IDOC_INPUT_MATMAS01       MATMAS01         MATMAS
IDOC_INPUT_MATMAS01       MATMAS05         MATMAS
so I think all configurations should be ok.
Message was edited by:
        liu bin

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.

** Inbound IDoc - One field is missing but it is displayed in SXI_MONITOR

Hi Friends,
We have developed IDoc to IDoc scenario. Source IDoc is sent from 3rd party system. Target is an Z IDoc (Replica of VEHCLE01 IDoc).
When we test the source IDoc XML from RWB, the message processed successfully in SXI_MONITOR and target IDoc is also created in backend SAP system. But, the problem is that, in target payload there are 5 fields. But, in the physical idoc created in SAP system has only 4 fields. The last field is missing.
Since it is inbound IDoc, I deleted the IDoc meta data in IDX2 txn, and reimported again the Z IDoc. But, again the same problem is coming. i.e one field is missing in inbound IDoc. But, in the receiver payload, that field is there with value.
Kindly clarify, friends.
Kind Regards,
Jegathees P.

HI,
If that field is missing for first time in R3 means(ie Receiver system, Idoc posting in we02) , then
XI side:
1. u have check whether that field is existing in Target Interface,Target Message in Interface Mapping
2. Make sure that u have mapped that field in Message Mapping.
R3 (receiver side)
1. Plz check we30 , whether that field is there for that ZIdoc structure
2. Take the same Idoc which got posted , test in we19 whether that Idoc getting posted with that field or not?
check whether ur Idoc structure is activated in XI
Thanks
Praba

Inbound idoc not displayed in WE02

Similar Messages

Maybe you are looking for