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

Similar Messages

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.

User exit overlooked when Inbound ORDERS is triggered immediately

If I set the ORDERS Idoc for 'Trigger Immediately' in WE20, the user exit EXIT_SAPLVEDA_011 is overlooked but when I set it up for 'Trigger by background process', the user exit is passed through.
does anyone have an idea why this could be happening?
I cannot put the stop sign and debug, since the Idoc comes via RFC, and thus it is impossible to debug in case of 'Trigger Immediately'.

Hi,
the exit function is called at the end of processing FM 'IDOC_INPUT_ORDERS'. There is definitely no difference between immediate or delayed background processing. Your question could be answered if we know the coding of include ZXVEDU13. If it is used for the designed purpose, it should do nothing if the error table DERRTAB is empty.
You can code an endless loop in the include:
data wait type c value 'X'.
while wait is not initial.
endwhile.
Then process your Idoc. In SM50 you can send the process to debug mode. Clear field WAIT in debugger and step through to see whats happening and why.
Reards,
Clemens

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

Out bound idocs not triggered

When ever the employee is terminated the comm idocs should be sent to basis ,CRM and SRM systems
But in our case when ever the employees are terminated
equal number of comm idocs are not being triggered for all the systems
For instance
If 10 users are teminated today
10 users,10 communication idocs to basis ,7 to CRm and 7 to SRm systems
For a few users communication idocs are not triggered to CRm and SRM
Please help
Thanks in advance

Hi,
Check in transaction SU01D if the users for which IDocs were not generated are maintained for the respective SRM and CRM systems.
~ Bineah.

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

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

How to post an Inbound IDOC .... I am new to IDOCs

I am working on an inbound idoc for creating a goods receipt based on PO.
I dont know how to post the idoc.... Some body pls help me..
Thanks in advance

Hi Raja,
Check this out.
Inbound IDocs are triggered by either external systems (edi, wms etc) or can be triggered by inhouse applications in SAP to post a application document.
1. EDI_DATA_INCOMING can create a IDoc from a file on the OS layer. It just needs a IDoc flat file containing control and data records, it will create an Idoc from it if the control record successfully matches a inbound partner profile parameters.
2. IDOC_INBOUND_ASYNCHRONOUS can be triggered by external/internal programs to creae IDoc withing SAP, whereas IDOC_INBOUND_SYNCHRONOUS can be used by inhouse SAP programs to create inbound Idoc.
3. WE19 can create and post an existing inbound Idoc to application
Hope this resolves your query.
Reward all the helpful answers.
Regards

Inbound Idocs are not Processing

Hi,
Inbound IDOCS queue is not processing if any one IDOC is showing amber(error) . Please let me know the resolution to avoid this issue or let me know the BASIS setting to avoid it.
Regards,
PVK.

Hello,
Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
Help on RBDAPP01
Regards,
Sameer

Workitem is not generating for an Inbound Idoc

Hi All,
The problem I am facing, when inbound idoc is processing in SAP, if there are any errors occurred, it would generate a work item and that will be sent to user Inbox (SBWP) as per the workflow. Here it is not generating a work item for an inbound idoc where is there is an error. So user is not receiving work item mail to inbox, to check about the idoc error. This idoc has been processed through the function module.
Could you please let us know your input on this issue.

Hi Hitu,
The problem could be at multiple places.
To debug check the workflow which sends the workitem to the user when an error occurs.
Check if this workflow is getting triggered when the error occurs. If yes, then check the step whre this workflow fails.
Else, check the event linkage of this workflow and check if the associated event is getting triggered or not. If yes, check if the event linakge is active for the workflow.
There could be other places as well to diagnose the error.
Check if these inputs gives you some direction.
Regards,
Saumya

Inbound IDOC error - status code 52- application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

Inbound IDOC not Triggering Immediately

Similar Messages

Maybe you are looking for