Idoc sequencing

Hi All,
I am looking for solution to the following issue
The scenario is: Sender is sap hr which sends hr data of various info type based on change pointers (we have program RBDMIDOC scheduled every 20 mins to create idoc), the receiver is oracle IAM system which needs this hr data. We donu2019t have XI involved in between itu2019s just the case of sending idoc to IAM system via TRFC ports, now sometimes when system is down these idocs gets queued up and then later on when we execute LUWs(SM58) then there is no guarantee of FIFO (first in first out), now I wanted to know if there is any way to have some sequencing so that idoc goes in sequence because the receiving system doesnu2019t have capability to sequence it . It just takes the idocs as it comes. I have checked ALE/IDOC serialization but I guess for this both system should have capability of handling queues (like R3 to R3 or R3 to XI). Would be really grateful if you could help in this.
One solution that I can think of is to suspend the RBDMIDOC job so that it doesnu2019t create more idocs if connection is down but this solution is not that clean. Sequencing would have been a better approach.

Thanks for reply, i created outbound queue in partner profile, but i wanted to know if receiver(non sap system) doesn't have capability of queue(EOIO) it just takes the idoc as it comes , then will the outbound queue on the sender side guarantee that the idoc received are in sequence.
I can only repeat my advise that you really should read up on [qRFC|http://help.sap.com/saphelp_nw70ehp2/helpdata/en/47/cd32ee1e123c84e10000000a42189c/frameset.htm]. If you'd follow the link that I'd already given you in the previous posting you'll see as the first subtopic [qRFC Communication Model|http://help.sap.com/saphelp_nw70ehp2/helpdata/en/e7/555e3c0f51a830e10000000a114084/frameset.htm], which states this:
Case 2: qRFC Outbound Queue
In this scenario the sender system uses an outbound queue to serialize the data to be sent, that is, function calls that depend upon each other are put in the outbound queue of the sender system and transferred to the target system in Exactly Once In Order - EOIO. The called system (server) has no knowledge of the outbound queue in the sender system (client). This send process is intended in particular for communicating between an SAP system and a non-SAP system.
Note: The coding of an external server need not be adapted specially to use qRFC. However, it must be tRFC enabled.
I doubt that anybody can explain this more clearly, not to mention the fact that it's always better to rely on the official SAP documentation than possibly questionable advice by some stranger...

Similar Messages

File to idocs - sequence of inbound processing

Hi everybody,
we have a file to (2) idocs scenario. In XI we map the received data of vendors into two idocs (adrmas and cremas). After building the idocs we send them in that sequence to the reveiver systems (recommended). The problem is that in the receiver system very often the idoc cremas wants to be processed before adrmas is ready. This leads to the error "vendor xy is blocked by user sapale". Especially for massprocessing I get a lot of these error-messages in bd87. As workaround I processed all the error-idocs by the report rbdmani2. (First step adrmas - second step cremas) But then I face missing data in some cases in table lfa1 - which seems to me that the sequence of 1. adrmas and 2. cremas was not correct processed.
Is there a possibility for inbound processing with the rule process adrmas - wait until ready - process the associated cremas and so on?
I checked the sap-help article for seralisation - but we could not achieve a better result by queing the outgoing messages in the xi.
Thanks very much.
With kind regards
Jörg

You have to get a solution based on the following concepts
1. Do not use BPM it is not efficient
2. Understand what is the difference between an IDOC in received state and processed state. Received state mean IDOC is saved into IDOC table. Processed state mean IDOC processed into the business system.
3. You can ASK BASIS guy to turn on the immediate IDOC processing option in SAP system,so that SAP process the IDOC as soon as it arrive in IDOC table. This is not efficient, in case if your SAP system has to process SAP online client request and SAP document (inbound and outbound) same time.
4. Understand the concept of standard based integration, mean integration system provide the option to business parties to provide the successfull message transfer.
Based on all these points I recomend you to follow the steps below.
1. Extract each record from the input files into two idocs.
2. Send the first IDOC to the receiving system
3. Send the second IDOC to a ESB storage such as DATABASE, JMS Queue, MQ Series Q (if you have available) or even to another File.
4. Develop an RFC module to check the status of the IDOC being send to the receiving system. Status here mean whether the IDOC data processed into the business system. You can do this lookup using a custom RFC lookup using the attribute connecting the first IDOC record with second IDOC.
5. Process the records (second IDOC) from the intermediate storage using the RFC lookup into the business system updates its status as ready to deliver.
6. Using another process such as FILE to IDOC or JMS to IDOC or JDBC to IDOC send each record which are ready to process from intermediate storage to the receiving system.
7. Create a report using FILE or JMS, JDBC adaptor module to keep track of these three stage processing, so that in case an inconsistency happed you will have an auditing trace available.
This is the standard based integration approach.
ABAP guys, BASIS guys they may not get it when then repair a BMW in local auto workshop, cuz I had to fight with them 4 years ago to make it happen in Verizon supply chain project where I had to accomplish the same concept in SAME IDOCS you mentioned here.
BPM, turning on immediate processing of IDOCS etc will end up in buying another 16 CPU hardware and BASIS guys or ABAP guys running BAD record IDOC processing report for 350.00 hr consulting FEES.
SAP is a good company and XI is a good product, as long as it is being used as per right usage.

IDOCs sequence is mixed in processing - wrong receiver import sequence

Hello,
we are working with self defined IDOCs to send accounting data to another system.
The process is that regularly a high number of IDOCs is generated, lets say 1000 / 10 min.(but only once a day) and sent to XI.
The Idocs have a mandatory sequence from business perspective.
They are moved to XI and in SXMB_MONI we can see that they are received in the
expected sequence from the IDOC sender.
Having a look at the receiver side something is wrong.
The first IDOC coming in is sent to the receiver as one of the last of this .
So the IDOCs are sent to the receiver in a wrong sequence.
Currently we are thinking about a BPM with correlation to handle his problem.
But possibly there is an easier solution e.g. influencing the queue?
Thank you for any help!
Best regards
Dirk

Dirk,
It is possible to serialize the Idoc's when sent from your SAP system itself.
Refer this blog and also the comments section of this blog where Michal provides a few interesting comments,
<a href="/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi">How to serialize IDoc XML messages fed into XI</a>
Regards
Bhavesh

IDOC Number Sequence Disturbed and Need to Reset by Increment - HELP Reqd

Hi Readers,
I need your Help / Expert Advise. We are in the process of Upgrading our SAP R/3 System to 64 Bit R/3 System on XP Server. We did take the existing production Image to do our testing. Unfortunately, we see that the Outbound IDOC Sequence got disturbed and we see difference of 1000. Ex: 1454004 and next 1455004, 1456005 and so on.
Did anybody happened to face such problem ? And any of you know how to fix it. I did try to see that SAP Transaction OYSN but no use.
Any help is appreciated. Let me know on any solutions.
Outbound IDOCS affected with this. Inbound seems OK.
I have downloaded the WE05 IDOC results in XL Format and pasting it here for your ref.
<h6>IDoc Number     Segments     Status     StatusGrpg     Partner     Basic type     Time     Messg.Type     Direction     Port     Date
0000000001456004     000007     03     @08@     LI/LF/0000307136     DELFOR01     13:13:31     DELINS     Outbox     EMDEDIALE     01/15/2009
0000000001457004     000042     03     @08@     KU/AG/0000000067     ORDERS03     14:08:49     ORDRSP     Outbox     EMDEDIALE     01/15/2009
0000000001458004     000042     03     @08@     KU/AG/0000000067     ORDERS03     14:17:51     ORDRSP     Outbox     EMDEDIALE     01/15/2009</h6>
Thanks
Venkat

Ah yes !
Sorry.
do
shutdown normal
startup mount
recover database until cancel;
alter database open resetlogs;You have to "simulate" an Incomplete Recovery (or do a real Incomplete Recovery) before Oracle allows an OPEN RESETLOGS. A SHUTDOWN NORMAL ensures that you really really do not need the Online Redo Logs. So the RECOVER DATABASE UNTIL CANCEL simulates an Incomplete Recovery.
See http://hemantoracledba.blogspot.com/2008/11/open-resetlogs-without-really-doing.html
Hemant K Chitale
http://hemantoracledba.blogspot.com

XI Sequencing: File Receiver adapter

Hi All,
I am in a IDOC to file scenario.
Requirement is to process the IDOCS in the same sequence as they were created in SAP.
E.g: if IDOC 1001 (created at 12:00:01 hours) and 1005 (created at 12:00:06) were created in SAP, then they should create the files in XI in the sequence File 1001 and then create file 1005.
Currently both IDOCS came to XI almost at same time and somehow XI processed 1005 before 1001.
Is there a way on the File adapter on receiver side how to achieve file sequencing for above issue.
Regards
Shirin

Hi Shrin,
As per my knowledge, IDOC sequence must be strictly maintained at sender side.
Irrespective of the configuration you set in XI like maintain order runtime or serialization, how does it guarantee you that IDOC is been sent in sequence.
Also note that IDOCS are processed via TRFC and not QRFC. Moreover, can i know the reason or background of this requirement.
I have never come across such a requirement except for in BPM where we collect all IDOCS and bundle it.
OR you are just trying some prototype

Grouping idoc processing

Hello,
I may receive in SAP system, idoc sequences like this one for example :
1 - Deletion
2 - Creation
Firstly, I would like to be sure that the deletion is processed before the creation. For this I tought about serialization.
But my issue is here : If the second idoc (creation) is not processed correctly (for any reason), I would like to process none of them (ie Rollback the deletion). Is this possible ? Is there another way for that kind of need ?
Thank you in advance,

HI,
I doubt if it is posible using IDOCs.
Insead what you can try is to have an ABAP server proxy written, which calls a BAPI for deletion and then calls a BAPI for CReation .
If the BAPI for creating fails, you can rollback the first bapi also, using ROLLBACK WORK command in ABAP.
ELse you can Commit using COMMIT WORK statement in ABAP.
Regards,
Ravi Kanth Talagana

Cross-system stock transfer order (cross CC and without using APO)

Dear experts,
I want to set up a stock transfer order scenario cross two SAP systems (and cross company code).
The examples given in SAP documentation point to scenarios using a joint APO system.
At the same time the documentation reads:
The number of process variants is a result of the combination of system landscapes and organizational units:
- with or without joint SAP APO
Does anyone in here have experience in setting up this scenarion without using APO system and could help me with a process flow and the IDOC sequence used for this?
Thanks and regards
Norbert

Hi,
and thanks for looking into this.
No, I do not have an APO (company is using JDA/manugisitcs) and I want to set up cross system STO between two ECC 6.0 systems directly.
I do have a number of idocs running between the systems already and also know the place where to configure a plant for cross system goods flow.
What I would like to know is if this scenario is supported at all and if yes, what is the sequence of idocs and and what are their triggers (in other words - the technical side of the business process) .
Best regards
Norbert

Merchandise category & hierarchy upload using LSMW???

Hi
I am trying to upload Merchandise category and hierarcy using LSMW (BAPI/IDOC method only).
For merhcandise category
I used message type W_WGRP and it is helping me in changing or reclassification of articles. But I am not able to create new merchandise category with this. I used structure E1BPE1WGR01 with "function" field with value "005, LSMW is working fine idocs are created successfully but no new Merc Cat is created.
When I used same structure with "function" field with value "009" I get error message "Class XXX does not exist or or is not valid on this date".
For Merchandise Catrgory Hierarchy
I used idoc CLSMAS but getting error message "Keyword missing for class XXX"
has anybody uploded entire hierarchy structure using LSMW ?

Sorry to say, but your problem is not resolved.
In IS-Retail, a merchandise category must first be created as a class (CLSMAS) and then also as a merchandise category (W_WGRP). Yes, you must process two IDoc per merchandise category, and in that order.
To understand how to load data using LSMW, the best approach to watch what the system does naturally. In this case, use T-Code WGSE to send the merchandise category hierarchy via ALE from one system-client to another. For understanding, you needn't configure the entire ALE scenario, just the outbound portion. Then watch the outbound IDocs be created; there's your example!
For merchandise category hierarchy (including merchandise categories), there are four message types that will be sent: W_WGRP, CHRMAS, CLFMAS, and CLSMAS.
IDoc Serialization using message types (serialization groups) is used when several different message types are dependent on each other, as is the case here. For example, if a merchandise category is assigned to a merchandise category hierarchy level, the merchandise category hierarchy level must first exist. How you use LSMW and IDocs is informed by the sequence.
To understand the IDoc sequence for creating the merchandise category hierarchy (including merchandise categories), use T-Code BD44 to view the Serialization Group GRP_W_WGRP includes the 4 desired message types in sequence:
CHRMAS04 Distr. of Characteristics with Dependencies and Long Texts
CLFMAS02 Master object classification
CLSMAS04 Classes with Long Texts, Document Links, and E1UPSLINK
W_WGRP01 Distribution of material groups
CHRMAS04 is only relevant of Characteristics are being assigned to merchandise categories. Let us leave Characteristics aside for now.
Step 1: Create Merchandise Category Hierarchy Nodes
Step 2: Merchandise Categories - Create as a Class
Step 3: Merchandise Categories - Change as a Retail MC
Step 4: Merchandise Categories - Assign Category Hierarchy Nodes each other, and assign MC class to MCH node.
For this, use these messages:
Step 1: CLSMAS04
Step 2: CLSMAS04
Step 3: W_WGRP01
Step 4: CLFMAS02
- Paul
Paul R. Gendreau, Jr.
SAP Retail

Function Module MASTER_IDOC_DISTRIBUTE to be called in background task?

Hi,
We are generating outbound Idocs in a report. In this report we are using Function Module Master_Idoc_Distribute. Now we have faced some performance issues and the basis consultant is asking us to:
Call the function module using CALL FUNCTION Master_Idoc_Distribute IN BACKGROUND TASK.
1) How will calling the FM Master_IDOC_Distribute in background task help improve the performance?
2) By calling the function module in background task, will it have any impact on the sequencing of the idocs? If yes what is the way out, as the idoc sequence is very important.
Thanks in advance,
Mick

1) How will calling the FM Master_IDOC_Distribute in background task help improve the performance?
->Calling the FM in background task will help in performance as it will be called in the background process mode like a tRFC.So it will not occupy any dialog process which are limited.
2) By calling the function module in background task, will it have any impact on the sequencing of the idocs? If yes what is the way out, as the idoc sequence is very important.
->It will not have any impact on IDoc sequence.

What is meaning Changing ALE Inbound Channel Registry...

what is meaning Changing ALE Inbound Channel Registry
can any body give sample scenario.
thx.
sudhakar

Hi,
When inbound IDocs are processed, a unique serial number is generated for each object channel (field CHNUM) and communication link. The ALE layer determines whether a given IDoc can now be posted or whether other IDocs have to be posted first. The serial number for each received IDoc is exactly one whole number lower. Any gaps in the sequence will mean that IDocs are missing, either because the transfer did not work, or because earlier IDocs were not posted successfully.
In this case the IDoc is assigned status 66 and must be posted again with the program RBDAPP01.
Objects are assigned to messages and channels by the application.
Transfer errors (IDoc sequence mixed up) and inbound posting errors (IDoc cannot be posted due to Customizing errors) no longer affect the sequential order, because serialization corrects these errors.
The inbound channel registry is maintained in transaction BD103. The serial counter number should be one less than the IDoc in the queue expected to be processed. PURCHASE ORDER message types come under this category of serialization of IDocs.
~ Bineah.

Problem: Processing IDocs in sequence in XI 3.0

Hi,
I am trying to send an IDOC from XI (XI3.0 stack 11)to SAP R/3 (4.7).
From XI I have to post Purchase order and goods issue idoc.
My Business process is as follows,
Receive->Transform->Sync Send (Proxy call)->Transform->SEND PO IDOC->SEND GI IDOC
In BPM I am using two send step one for PurchaseOrder(PO) and another one for GoodsIssue(GI). But my condition is GI idoc should get posted only after posting PO idoc. As of now I have put transport acknowledgement in the first send step so that once all PO idocs are sent to R/3 then only the second send step will post the GI idocs. But transport acknowledgement works only if I keep refreshing messages in the sxmb_moni. If I drop a small file and open the sxmb_moni after say 1 Hour..it is still waiting for acknowledgement. Once I click refreshit is processing the acknowledgement and then processing the next send step which will post the GI idoc.
Is there any other way of processing these two different IDoc in sequence.
I tried also queue processing setting in the idoc adapter. But the two idoc are going to two different queues. Is there any way by which i can put the two idoc data into a single queue?
Let me know if you need any clarifications.
Thanks,
Sasi

Hi Robin,
I have created a sender and receiver id (for interface i have just put '*'). Also set an Integration Server Outbound EO filter for the sender and receiver id. Is it correct?
When I tested the interface, the two send step sending the data to two different queues ids as XBTAH0__0002 and XBTAH0__0001 (queue id got it from message monitoring). How to make sure that they are sent to the same queues?
I have changed the BPM to one send step (instead of two). In Integration directory I have configured two interface determination one for PO and another for GI. I also checked the QUEUE PROCESSING option in the idoc adapter. Now for both idocs it is showing the queue id as SAP_ALE_XI_SERIALIZE0001. But the status in sxmb_moni shows RED flag saying 'IDOC_INBOUND_IN_QUEUE' not found.
Cud you pls help me?
Thanks,
Sasikumar

How to serialize the IDoc of DEBMAS by time sequence?

Hi experts,
We want to transfer customer master data from one client to the other.
We have carried out the serialization distribution for message type DEBMAS
and actived the change point.
Scenario:
time 1 : We created one "NEW" customer 100436.
time 2 : We assigned the Head Office of "existed" customer100435 as 100436
The time of the distribution job was arrived,
the job started to run and failed to change "existed" customer 100435
even though "NEW" customer 100436 has created sucessfully.
We think the IDoc should be processed by time sequence,
but it seems not.
Did you think it is processed by customer key ascendence ?
How do we define the process sequence of the IDoc?
Any advice will be appreciated.
Regards,

But what if i want to check the format of date that my
database supports ?
Actually situation is :
I am making a form designer by which user will inset
date to a particular column. okay.
now the format of date must match with the underlying
format of database. Then only query will be
successfull. Is it not so.?No.
Basically you will be doing the following:
Browser -> java.util.Date
java.util.Date -> JDBC -> database
JDBC does the 'conversion' work for you, you just need to put it in the java.util.Date.
suppose database table-> column's format is
YYYY/DD/MM Databases don't store dates like that. They usually (probably always) store it as a signed integer value which is relative to a specific date/time.
When you use a database tool to look at the value the database tool converts it from the number to a format that looks familar to you.
and user enters date in the format
DD/MM/YYYY, then i will have show an error message to
the user that the format of date that he has entered
is wrong. No need for that.
The user does need to put the date in in a form that you understand. So you can convert it to a java.util.Date.
java.text.SimpleDateFormat can help with that.

Send Idoc to SAP in sequence and roll back if the last one fails

Hi All
I have a scenario like this.
System Ajore --> XI - > R/3
Ajore is a manufacturing system
Send material from Ajore to SAP through XI and create MATMAS idoc in SAP
Send change number from the Ajore to SAP through XI and create ECMMAS idoc in SAP
Send Bill of materials from the Ajore to SAP through XI and create BOMMAT idoc in SAP
All these will should be send in the sequence MATMAS, ECMMAS, BOMMAT to SAP. How can I achieve the sequence operation through XI?
Second challenge is when I send the BOMMAT to SAP and if it fails, then all the processed MATMAS, ECMMAS sent to SAP should be rolled back.
Is it possible to achieve using XI?
The reqmt is very urgent. Any help is really appreciated.
Thanks
Ricky

Hi Satish,
Thanks for the reply. Do I need to do event driven message processsing in XI for this? The other way is to schedule the RBDAPP01 in R/3 to post idocs in sequence based on the message type and Partner number
Does this makes sense?
And any idea bout the second question for roll back?
Thanks

IDoc - Incorrect Number Sequence

Hi,
I have created a custom IDoc and sending it to 2 different SAP boxes. This has been triggered every half an hour interval. But my problem is IDoc numbers are not in proper sequence
Below find the screen image of WE02.
Here you see the IDoc No. 42202 created on time 10.20 and IDoc number 43004 created on 10.34 and IDoc No. 42203 created on 10.50
|     IDoc Number|Segments|Status|StatusGrpg|Partner      |BasicType|Date      |Time    |Messg.Type|Direction|Port   |
|0000000000042200|      28|03    |          |US/ /TP1    |Y101     |06/01/2007|09:50:32|Y101      |Outbox   |TP1    |
|0000000000042201|      42|03    |          |LS/ /AP1    |Y101     |06/01/2007|10:20:31|Y101      |Outbox   |AP1    |
|0000000000042202|      26|03    |          |US/ /TP1    |Y101     |06/01/2007|10:20:31|Y101      |Outbox   |TP1    |
|0000000000043004|   18593|03    |          |US/ /TP1    |Y101     |06/01/2007|10:34:24|Y101      |Outbox   |TP1    |
|0000000000042203|      14|03    |          |LS/ /AP1    |Y101     |06/01/2007|10:50:31|Y101      |Outbox   |AP1    |
|0000000000042204|       8|03    |          |US/ /TP1    |Y101     |06/01/2007|10:50:31|Y101      |Outbox   |TP1    |
|0000000000042205|       7|03    |          |LS/ /AP1    |Y101     |06/01/2007|11:20:31|Y101      |Outbox   |AP1    |
I have checked the Number range object EDIDOC, "No. of numbers in buffer" is mentioned as 1000.
incorrect sequence of IDoc numbers is created due to this?
How to correct this ?
Thanks
aRs

Don't change standard settings.
1) What happen if you try small files, this happens only to huge segments.idoc:43004(18593 segments) is huge file.
2) What happen if you trigger same idocs again.If you didn't try can you please try again and check.If say thing occurs than i guess that's the standard functionality of
buffering.
Again this issue is very instresting to me. I never faced this probem.
If you get solution please update.
Thanks,
Narayan

Posting idocs in sequence in SAP from file (without BPM)

Hi,
I have a requirement of posting the TWO idocs from the single file. But I need to send the idocs in sequence. Can you anyone explain the process how we can ecomplish from XI without using BPM.

Hi,
you can ONLY do that if your <b>ERP,R3 (IDOC receiver system) system
is based on WAS 6.40</b>
the whole scenario is described step by step in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Idoc sequencing

Similar Messages

Maybe you are looking for