Inbound Idocs: Queue Processing (non-stop queue?)

Hi everyone!
I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
I'm using PI 7.0 SP30.
Thank you in advance!

First, this is not serialization, it's the queuing design EOIO... they are not the same.
So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
Basically the serialization is not a good fit for these requirements.
Here is one solution:
1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
4- There is standard report that you have to schedule and restart the queues
5- Reprocess the IDOCs from steps 2
The enemy of EOIO design is the user locks in the target system...
Cheers,
Fouad

Similar Messages

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

Inbound IDOC Mass processing - No status message

Hi Friends,
I am updating a database table using inbound IDOC. But in batch job when XI passes multiple IDOCS,
for some IDOCs there is no status message even though i coded for status message.
If i rerun IDOC in BD87 then it work fine.
please help.
regards,
madan

Hi Madan,
Since you are loading multiple idoc to the system due to high load in the production system data is not commiting properly. So use external commit work statement in you code. this will reduce the performance but logic will work.
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the current SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
The sequence is based on the order of registration or according to the priority specified using the LEVEL addition. Execution of the following statements is not permitted in a subroutine of this type:
PERFORM ... ON COMMIT|ROLLBACK
COMMIT WORK
ROLLBACK WORK
The statement CALL FUNCTION ... IN UPDATE TASK can be executed.
Triggering an internal event for the Persistence Service of the Object Services.
If event handlers are registered by the Persistence Service, these collect the changes to the objects managed by the Persistence Service and transfer them via CALL FUNCTION ... IN UPDATE TASK to a specific update function module that is registered as the last update module.
This executes all high-priority (VB1) update function modules in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating), but instead is resumed immediately after COMMIT WORK. However, if the addition AND WAIT is specified, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
When all high-priority update function modules are completed successfully, the statement executes the low-priority (VB2) update function modules in the order of registration together in a common database LUW.
After the execution of high-priority update function modules, the individual function modules registered using CALL FUNCTION ...IN BACKGROUND TASK|UNIT are executed in a separate database LUW for each destination.
Within an update function module started using COMMIT WORK, the execution of statements that lead to a database commit is not permitted. In particular, the following are forbidden:
Thanks,
Raghav

HRMD_A Inbound Idoc with process Code:HRMD not updated in SAP

Dear friends,
I'm facing a problem with Personnel data creation in SAP (this is not a SAP HR system).
I have a data file with Personnel data, in WE19, I use idoc_input_hrmd to process the data (with basic type: hrmd_a06). Idoc has been created with status '53'. However, when I check in SAP, t-code PA30 with the Personnel number, the record does not exist. Checked infotype tables PA0000, PA0001, PA0002 and PA0003 as well, no luck.
I wonder where does the data go? Is it sitting somewhere in the system and waiting to be processed?
Please help!!!!!

Hi
Authorizations might be one of the reason.
So IDOC transfered but no records to be writeen to DB.
regards
vijay

Aperture 3.3 continues to process non-stop

So I finally broke down and purchased A3 after using the demo... I installed on a 2.4 MBP, 4 gigs of RAM. I imported nearly 200 gigs off an external drive that contained my iphoto library onto a new external fw800 drive. THe entire import ran fine, everything seems to be there, however I noticed that whenever I launch A3 it never ceases to stop "processing". I even let the machine run A3 all day today to see if it would ever finish "processing".. negatory. Is this normal? I am not editing anything... I am simply launching the app and it continues to process.... Anybody out experience the same thing? Is this normal? Is this connected to the fact that my library is pretty huge?

Thanks Eric!
Apparently it was a faces issue... it is tracking through all my photos looking for faces I've marked.

Queue processing in receiver idoc adapter

hi all
i am doing file to idoc scenario and i want to use queue proceesing option can anybody tell me the entire process regarding queue processing.

Hi KUNAAL MASIH ,
U can use a Prioritized queue for urgent messages that must be processed immediately
These r the details Queues Prioritization:
Queues for Prioritized Message Processing
http://help.sap.com/saphelp_nw04/helpdata/en/04/827440c36ed562e10000000a155106/content.htm
Queue prioritization for XI processing queues uses a built in feature of qRFC. By specifying the maximum processing time for a queue, u can define how much processing time a specific queue will get(this works like a time-scheduling procedure, time slicing). U can use this feature to add queues for high-priority and low-priority messages(for inbound and outbound processing). These queues are then named, for example XBT1* or XBT9* for inbound EO processing and XBTA, XBTZ for outbound EO processing.
This function uses the message filter concept and can be configured in transaction SXMB_ADM. U can define message filters for specific message attributes such as sender/reciever service, interface and so on. A filter can also be dependent on the message size.
This function can also be useful in situations where a queue backlog needs to be processed, due to a system error or an error on the reciever side, for example. In this case, u can use a Prioritized queue for urgent messages that must be processed immediately, without having to process the whole back-log first.
How to prioritize XI messages on the integration server
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
The parameter QualityOfService specifies how the Integration Engine should process a message. The following values are permitted:
1)BE(Best Effort: synchronous processing). If QualityOfService is BE, the client is sent the final status for the processing.
2)EO(Exactly Once: asynchronous processing with guaranteed execution exactly once). If QualityOfService is EO,processing occurs asynchronously and the client only recieves a confirmation of reciept with HTTP status '200'.
3)EOIO(Exactly Once in Order: asynchronous processing using queues, that is, guaranteed execution exactly once and maintaining the sequence of successive messages). If QualityOfService is EOIO,processing occurs asynchronously and the client only recieves a confirmation of reciept with HTTP status '200'.
Since u had choosen EOIO ,You must also define a queue name for EOIO:
XI.QueueId=<QueueName>
This queue name is used in the Integration Engine to process messages in the same sequence that they arrived in.
This QueueName can consist of a maximum of 16 characters. If the first 8 characters contain 'SAP_ALE_', these r removed since this value is reserved by SAP and used internally.
If a value is not specified for QualityOfService , the default value 'BE' is used.
These r following websites which u wil find helpful:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
http://documentation.softwareag.com/crossvision/xie311/admin/config.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca52244
cheers!
gyanaraj
****Pls reward points if u find this helpful

Forward Inbound - IDOC process

Has anyone used this option WE45- forward Inbound for inbound IDOC automatic processing?
 The help says
"Specify a job as a logical address for forwarding the data from an inbound IDoc or from a status confirmation". But need more details if anyone has used. We are looking for internal invoice posting in application V3 .

INBOUND_IDOC_PROCESS is the function module to be used before release SAP R/3 4.0; since release 4.0 you should use IDOC_INBOUND_ASYNCHRONOUS instead.
Similarly as indicated by the previous posting IDOC_INBOUND_SINGLE replaces function module IDOC_INBOUND_SYNCHRONOUS for posting a single IDoc.
Best wishes, harald

Creation of FM for Inbound Idoc

Hi abap gurus,
I need to create a function module to generate an inbound idoc form a non SAP system system to SAP system .How can I send the data to the IDOC segments ? do I need to use EDIDD structure or I can do it without EDIDD structure ?
Thanks in advance .

Hi,
If u need to send data to the IDOC segments, it is better to use the EDIDD structure.
Edited by: sharin varghese on Jul 21, 2008 1:40 PM

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

Problem in Inbound Idoc

Hi friends,
I have a small problem, actually one of my inbound idoc successfuly processed. But there is one field called IBAN, its for vendor master bank details. its not populated in SAP. But the segment having the value. Its giving problem for one particular vendor. So how to find why its not populated in SAP? Where we need check. Because IDOC having proper values, one of field value only not populated in sap. Pls help this issue.
Mohana

Open include in SE38 LKD02F01 and put a break point on line 3943 or following piece of code:
IF e1lfbkm-iban <> c_nodata.
MOVE e1lfbkm-iban TO f_lfbk_iban-iban.
WRITE f_lfbk_iban-iban TO blfbk_iban-iban.
ENDIF.
and check what value is getting populated when processing IDOC for that particular vendor.

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

AEDTM + UNAME not filled via HRMD_A inbound idoc

Sorry if this is the wrong forum but I couldn't find any forum related to IDocs.
I have an inbound idoc:
message type: HRMD_A
basic type: ZHRMD_A0701
Processing the idoc is working, however, AEDTM and UNAME isn't filled (the fileds are empty). I would assume that those fields are filled automatically with sy-datum and sy-uname. I did some debugging and found the corresponding INSERT:
IDOC_INPUT_HRMD
- IDOC_PROCESS_HRMD
- RH_IDOC_OBJECTS_SAVE
 - inbound_objects_block
 - RH_CREATE_INFTY_PA_PB
 - SAVE_PA_PB_INFTY
 - insert_pa_pb_objects
 INSERT (dbname) FROM <f_prel_db>.
AEDTM and UNAME are emtpy in <f_prel_db>. Any idea why? Is this a known issue?

HR inbound idocs actually do not override change date / time (aedtm, uname) with date/ user id of the user who processes the inbound idoc. These info should automatically be populated in the oubound idocs as is from sending SAP system.
I guess the reason being is this is meant to replicate data (with all original info from sending system) to receiving system. If you notice in the receiving system, when HR inbound idocs are processed, change pointers are not recorded.
Therefore, if the inbound idcocs are not senf from SAP, these info would need to be populated when outbound idocs are created. Otherwise, you may have to look at inbound user-exit to see if these fields can be populated in the idocs segments.

Inbound IDOC commit

Dear all,
I need to clarify scneario below:
INBOUND process
Receive an Idoc, and inbound FM Z_TEST_IN will be executed. In inbound FM Z_TEST_IN, i have to update both Table ZHEADER and ZITEM. Since they are Header and item table, so if one of the table updating failed I've to perform rollback.
This is what i plan to do. Create 2 update task FM, one for ZHEADER update and one for ZITEM update. It will look like this:
Function Z_TEST_IN
CALL FUNCTION 'Z_UPDATE_HEADER'
IN UPDATE TASK
CALL FUNCTION 'Z_UPDATE_ITEM'
IN UPDATE TASK
ENDFUNCTION
My question would be:
1. Is there a system COMMIT WORK predefined in ALE layer? Or should i code an explicit COMMIT WORK in Inbound FM Z_TEST_IN?
2. Let's say update fail on one of the table, then ROLLBACK WORK will be triggered. So i'm aspecting data will not update to both tables, but how about the Inbound Idoc creation? Will the idoc still be created and shown in WE05?
Your comment is highly appreciated. Thanks in advance.

Hi,
1.You are using the Zfunction module,So you need to commit explicitly.
2.For standard ,implicitly done.
3.There is no need to create inbound IDoc.While processing only the Inbound idoc created.
4.Suppose if u want to create just go for We30.
5.We05 for just gives the list of idocs created.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Regards,
Shiva.

Receiving IDocs in XI from a system with Queue Processing option

I am trying to use the Queue Processing option that can be set in a partner profile for IDoc sending, so that qRFC is used.
I have set up the Rule Name as one of the defaults that come with the system, but when I execute the sending of the IDoc, it gets stuck with status 30 (ready for dispatch). I have configured the Output Mode of the IDoc as "Transfer IDoc Immediately".
SAP Documentation states that:
"When you send by qRFC, the IDocs are first put in an outbound queue in the sending system, and then in an inbound queue in the recipient system. You can assign IDocs to various queues and specify queue name rules. "
Is there something I also have to do in the XI system that is receiving the IDoc?
Kind Regards,
Tony.

Hi Anthony,
Now I have the same problem in between ECC6.0 and PI7.11.
If you solving the problem,
Please let us know how you did.
Best Regards,

Queue processing of messages (files / idocs)

Hi,
We have 4 communication channels:
INT A
1 filesender (file)
1 filereceiver (idoc)
INT B
1 filesender (file)
1 filereceiver (idoc)
So, the issue is we need to process the messages in order. First, 2 files from INT A, next 1 file from INT B. The correlationship is the key.
Is any configuration possible for queue processing with no using of BPM?
Regards,

hi,
yes you can set queue (EOIO) processing in both filesenders
and if you hava ERP (IDOC) on WAS 6.40 it can be processed
in this one queue
how to (IDOC queue processing part) described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Inbound Idocs: Queue Processing (non-stop queue?)

Similar Messages

Maybe you are looking for