IDoc EOIO Processing

Hi all,
We use IDoc receiver to backend sap system and the QoS is EOIO. In case of Application Error in backend system, we want to stick the subsequent IDoc in the queue. But the problem is that from the XI perspective, once the IDoc goes to the backend system, the IDoc is regarded as being successfully delivered. So the subsequent IDoc is processed and continue to be sent to backend IDoc.
Is there anyway to set the XI message into error status in the queue in case of Application Error in backend system so that the subsequent messages wait in the queue untill the problem is solved.
Regards,
Hui

How will you process the error in the backend to clear and process subsequent documents??
What version is the backend?
You will have to look at serialisation.
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66c9507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/frameset.htm

Similar Messages

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

Delay in the Inbound Idoc Posting Process

Dear Friends,
We have an scenario in the Inbound Idoc Posting Process, when we process the Idocs through the standard Inbound Program - RBDAPP01, we face the delay of 3hrs to 12 hrs, approx.
When we try to re-process the same through the manual process, we could successfully post the Idocs, immediately.
When the same happens, through the background job - the delay is happening.
As we see, there is no problem with the program - RBDAPP01, but can't able to trace the delay in the process.
Any suggestions / advises are welcome.
Thanks in advance.

Hi Prasanna,
The update will happen only if a value already exists with the same unit of measure in the system. If the quantity is left blank in the system and if you are trying to update, the update might not happen. Even if the value is Zero in the system, provide the same unit of measure as the data used in the BAPI.
Regards,
Yogesh

#'s coming up in IDOC when IDOC flatfile processed with RSEINB00

Hi,
We have given IDOCs in flatfile structure which are needed to be loaded in backend SAP R/3 through XI and it needs some transformation,so we are using XI for mapping in between,otherwise we would have processed directly into R3.
Basically we are placing IDOC Flatfile in a folder and we are running RSEINB00 program on XI through a file port in XI and IDOCS are getting created in Backend SAP R/3.
When we place IDOC flatfile in Windows folder and process the file we are getting #s in IDOC fileds(many fields) ,but we don't see any #s when we process the IDOC flatfile when placing IDOC flatfile on UNIX .Our XI/PI is running on UNIX.
please help,what causing the problem?
Thank you,
Regards,
Sathish

Hi Ravi kanth,
I see them (#s)in IDOC fields in backend SAP R/3 once the IDOC flatfile got processed.
as we are running RSEINB00 report on XI ,we noticed that empty tags are coming (from Windows OS Folder)in SXMB_MONI even before my mapping execution ,I think they are being populated as # in IDOC.but dont see this problem when IDOC file processed from UNIX folder.
You think ,if we save file in UTF-8 format or Binary might help rather than ANSI format and process it.
Thank you,
Sathish

LSMW idoc Inbound Processing settings

Hi,
We have done LSMW with BAPI method to create Bank master.
In Idoc Inbound Processing settings -
We created partner type as 'B' i.e, for BANK
While creating Partner Number it is not allowing to create Partner Number. The error is "Enter a permissible partner number"
Please let me know what would be the problem.
Regards,
Hari
Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AM

Hi,
Use patner type as US only and LSMW as Patner number.
this will surely solve your problem .
plz do this way :
The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
Port: LSMW
Name: Legacy System Migration Workbench
Version: 3 (IDoc record types SAP Release 4.x)
Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
SAP recommends:
Port: assigned by the system
Version: 3 (IDoc record types SAP Release 4.x)
RFC destination: Name of R/3 System
Name of port: Legacy System Migration Workbench.
Then the partner type should be defined or selected. SAP recommends:
Partner type: "US" (User)
As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
Partner type: Create US
Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine: READ_USER
Short description: any.
Finally a partner number should be defined or selected. SAP recommends:
Partner number: LSMW
Partner type: US
Partner status: A (active)
Type: US
Language: DE or EN
Person in charge: Your user ID.
Activate IDoc inbound processing
reference : help.sap
thanx.
Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM

IDoc Inbound Processing for CREMDM & DEBMDM

Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.

Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh

IDOC Inboun processing success but no record posted to table

Hi,
We are performing ALE refresh in RCD221 (development system). The ALE IDOCS are extracted for HR area with Message class as HRMD_A, the IDOCS are processed successfully from the sending system (RCB) and reaches the receving system RCD221. While we process the inbound IDOCS in RCD221 records are not getting posted in the table, however the IDOC status is shown as successful (53). This is happening when we are processing the data for object type 'P'.
Regards,
Bharath Mohan B.

RFC destinations, Logical systems, and then Partner profiles needs to be maintained. and You need to create the Distribution model in sender system.
Partner profiles maintained in both the systems, soure Outbound properties
Target Inbound properties.
if you have two clients in system it will be easily you can check.

Inbound Idoc EOIO

Hi experts,
my scnenario is file to PI to idoc.
I have checked the box 'queue processing' in the PI configuration of my scenario so that the idocs get processed in ECC in the same order than they arrived.
I know that if one idoc fails, the whole queue get struck.
But is there an 'automatic way' to reprocess the queue without the failed idoc ? Instead of manually ?
Kind regards,
Jamal

hi,
there are two transactions on ECC
WEINBQUEUE and WEOUTQUEUE
that allow to do what you need
is that what you're looking for?
Regards,
Michal Krawczyk

RFC For IDoc outbound processing

I am creating an RFC for BDC for call transaction we19
input as : idoc number
and output:-.. iDoc Outbound processing done
so:-
I go to we19> give iDoc Number (say, some number for ALEREQ01), and execute> click on Outbound processing-->click enter -->enter
in this way, I can process any iDoc from SAP system to outbound.
I want to create RFC for the same.
Problem:-
when i am executing that RFC, and when I check the iDoc status in we05, that iDoc shows status as Idoc ready to dispatch( its in yellow color).. Its not showing green color and not saying that IDoc passed OK
when I try manually ,I see the status green..OK..successfully
Any idea why I am getting this problem??
Is there any problem in my BDC recording?..but when I run that recording for Process, i dont see any problem,it executes successfully.. but when I copy the Code from BDC and make a RFC using that code, its giving problem as mentioned.

Hi Ankit,
Theorotically it should work.... but I'll suggest not to use BDC here. What you can do is,
1. You have Idoc number..Right?
2. Read control record from EDIDC and data record from EDID4.
3. Then call Master_idoc_distribute.
4. This will again distribute the same IDoc with same control and data record as a new one. It will be same as WE19 , but without WE19.
Please check and confirm.
Regards,
Audy.

Idocs not processed automatically in BW

Dear Experts,
I have a scenario here where I extract data from source system via process chains.
The source system job completed and in BW, the outbound idocs resulted in the following Status (02).
02 Error passing data to port 1
In the infopackage message dialog, I got the message as
Could not find code page for receiving system
Errors have been reported in Business Information Warehouse during the IDoc update:
In order to resolve this, I'm manually processing the idoc using program RBDAGAIN.
Note: This issue occurs only when I trigger the infopackage via process chains.
How do I rectify this error so that the idocs are processed automatically in BW?
Br, Harish

Hi,
how much time your ecc job takes to finish job.
Is this process chain newly created one or old one?
if its old one, any changes were applied on this process chain recently?
is it showing any idoc numbers at below status bar.
if yes then try to pull them by using t code BD87.
Can you share info pack error message screen shot.
Thanks

Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 ,214

Hi friends,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender)., 214 (Shipment Status )
For shipement status i got trxstc01 for idoc type .. but its only before 4.6 version ..for 4.7 its not there .. please give the alternate for that ...
Thanks in Advance ....
If any one is provide exact answer i will give Max marks ..
Edited by: ajay KOLLA on Aug 6, 2009 8:04 AM

Hi,
Have you resolved this issue. If yes, can you please let me know. Im actually looking for same for EDI 867 (guess it is for summary report and need to know message type, Idoc type associated with this).
Rgds
Sudhanshu

Message type ,IDOC TYPE , PROCESS CODE for Edi 990

Hi ,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender).
Thanks in Advance.
Ajay Kolla

Hi
Pls check the below links
1. http://www.erpgenie.com/sap/sapedi/ansi.htm
2. http://www.erpgenie.com/sap-technical/ale-edi-b2b/master-data-message-types-idoc-types
Hope this may helps you.
Regards
Sirigiri

Idoc trfc processing very slow

Hello,
I am troubleshooting slow processing of idocs in an Xi test system.
idocs are being processed at a rate of betwen 40 / 60 per hour so at the current rate there will stil be another 3 days (approx) until the queue is cleared.
In SMQS on the Xi (source) system the specific idoc destination is set-up as follows: -
Clt - 10
Destination - R2RREG100
Type - R
W/o tRFC -
Max.Conn. - 10
Max. Runtime - 60
Status - WAITING
Act.Conn - 5
Host ID - ax2t003a_X2T_43
The RFC connection between the two systems has been tested successfully.
Selecting TRFC Monitor and there are still over 3000 rows similar to the following (was over 7000 when first checked)
Caller - PIAFUSER
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - R2RREG100
Date - 15.12.2011
Time - 12:38:22
Status Text - Transaction recorded
Transaction ID - 8218046C00014EC9DE911C9B
Host - ax2t003a
Tctn
Program - SAPMSSY1
Cln - 10
Rpts - 30
I am told by the application team that processing 7000+ idocs is not a large amount for this system
The Xi (source) system and the R3 destination system have both been restarted to clear memory etc but this has not improved speed of processing.
I presume the problem was caused by trying to process too many idocs at once through the Xi system as mentioned in SAP Note 1548446.
I have read SAP Note 1483757 and checked ST03n last minute load on RFC table in the R3 destination system -
Task Type Name - RFC
#Sequential Read - 4,782,264
T Seq Read - 1,157
Avg Seq Read - 0.2
#Accesses -      13,515,579
T Time - 204
Avg T - 0.0
#Changes - 54,206
T Changes - 63
Avg Changes - 1.2
Calls - 18,352,049
Avg Time - 0.1
#Reads - 1,828,651
#DB Recs- 109,376
#Records - 7,687,467
#Calls - 0
T Time - 0.0
Avg Time - 0.0
Last minute load Table Statistics for the destination system ARFCRSTATE table shows the following :
Table Name - ARFCRSTATE
Records -      1,822
Modifiable - 226
records - 0
Sequential Reads - 1,596
T Access - 1
In accordance with the note I tried setting the following on the detaination system but did not see any improvement in processing speed so have now removed the parameter and scheduling of the report.
    1. Set the profile parameter abap/arfcrstate_col_delete to 'X' on the default profile of the destination system.
    2. Periodically schedule the RSTRFCEU batch job in intervals of 5 minutes, in the destination system.
Q1 -after setting 'abap/arfcrstate_col_delete' I did not restart the R3 system. Is a restart required for this to take effect?
Q2 - What else should I check to identify why idocs are being processed so slowly ?
Q3 - Is there anything else I could change to speed up processing ?
Many thanks,

Many thanks jbagga for your reply.
My issue was resolved by SAP who suggested changing the processing mode for message type in WE20 on the receiver system from "Trigger Immediately" to "Trigger by background program".
With the processing mode set to "Trigger Immedaitely" the sender system calls the receiver, the idoc is stored on the dateabase and the application processing was carried out in the same LUW. As a result of this the send must wait until the application finishes processing the messages before it can anything else.
The processing mode was changed to "Trigger by background program" which decoupled the IDoc transfer from the IDoc application processing, performance immediately improved in the XI (sender) system and cleared the queue.
Regards,

IDOC Outbound processing using SAP BC

Hello Experts,
I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC, ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
Thanks & Regards,
Amit Naik

Hi Michal,
Following is the error which i am getting :-
2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
     at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
     at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
     at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
     at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
     at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
     at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
     at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
     at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
     at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
Thanks & Regards,
Amit

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

IDoc EOIO Processing

Similar Messages

Maybe you are looking for