IDocs in sequence

Hi,
I have to send 3 idocs (ARTMAS , INFREC, COND_A) in sequence from ECC to Legacy system. Target should be in XML files.
Please help me in designing the interface. How do I proceed? All 3 IDocs will be generated in ECC by background. How do I design this interface in PI? Do needful.
Regards,
Ramesh.

HI Ramesh,
I have to send 3 idocs (ARTMAS , INFREC, COND_A) in sequence from ECC to Legacy system.
Target should be in XML files.
All 3 IDocs will be generated in ECC by background. How do I design this interface in PI? Do needful.
The batch job which is used to generate the IDOC can be sheduled in a way that IDOCs are triggered in the same sequece
as required by PI. Please check with your ABAP counterpart to help you in this.
Also i feel .if you have 3 IDOCs ,you might be having 3 mappings , so in interface mapping . you can specify these mapping in sequence and check maintian order at runtime etc. I hope this will work.
Regards,
Srinivas

Similar Messages

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

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

Hello Guys,
I am using RBDAPP01 program to post Idoc in the background, I am seeing in the spool that Idoc are processed ine jeopardized sequence. Is there a simple way to have the idoc processed in the Idoc number sequence ?
I have read about serialization but I understand that it implies both the sending and receiving system and In my case it would be hard to changes anything in the sending system. Is there smething that I can do on my side ?
Does the packet size can have any effect on that ?
Best Regards, Manuell

Hi,
Try to setup queue on XI side using delivery Modes in BPM for your scenario.
Just have a look at this blog (Case 1) :
Delivery Modes in BPM
/people/milan.thaker/blog/2008/07/04/delivery-modes-in-bpm
Regards,
Chandra

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

IDOC: Number sequence

Hi
Can anyone tell me why my idoc numbers are not generated in sequence?
0000000000215190     08:16:01
0000000000216399     08:18:28
0000000000215191     08:18:31
0000000000218015     08:37:15
0000000000216400     09:21:41
0000000000218016     09:25:52
0000000000216401     09:27:59
0000000000218017     09:50:42
0000000000218018     10:04:58
0000000000218019     10:06:37
0000000000215192     10:16:47
0000000000216402     10:19:07
0000000000216403     10:25:16
0000000000216404     10:28:42
0000000000216405     10:28:43
0000000000216406     10:28:43
0000000000216407     10:28:43
0000000000216408     10:28:43
0000000000216409     10:28:43
0000000000216410     10:28:43
0000000000216411     10:28:43
0000000000216412     10:28:43
0000000000216413     10:28:43
0000000000216414     10:28:43
0000000000216415     10:28:43
0000000000215193     10:29:05
0000000000215194     10:29:12
0000000000215195     10:29:13
0000000000215196     10:29:16
0000000000215197     10:29:18
0000000000215198     10:29:19
0000000000215199     10:29:24

Are these entries from EDIDC table or From tcode WE02/WE05.
But what about the IDOC status of these?
The sequence is okay but what is the status of the same IDocs is it 53, or 64 or 51
You need to tell us this info also .
See the conclusion is many of the idocs are not processed and at the same time <b>if more than one message type is handled</b> then sequence is definitely not in scope right.
i may generate a sequence of say some 30 idoc's with status 64 which are not processed at all but still the system allocates an Idoc number .
regards,
vijay

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

What is the serialization concept in ALE/IDOC?

what is the serialization concept in ALE/IDOC?

Hi Srinu ,
IDoc Serialization means, sending/posting the idocs in sequence.
We serialize IDocs in the following cases:
· If you want the Integration Server to process the corresponding IDoc XML messages in the same sequence that it receives them from the IDoc adapter at the inbound channel.
· If you want the receiver to receive the IDocs in the same sequence that the IDoc adapter sends them at the Integration Server outbound channel.
The sequence at the Integration Server inbound or outbound channel can only be guaranteed if only IDocs are processed, and not if different protocols (for example, IDocs and proxies) are processed together.
Do not confuse IDoc serialization using the IDoc adapter with the ALE serialization of IDocs.
Prerequisites
· The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
· The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher. If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.
Procedure
If you want the Integration Server to process the IDoc XML messages created by the IDoc adapter in the same sequence that the IDocs are sent by your application, proceed as follows:
· Enter a queue name in your application. You can use 16 alphanumeric characters. The prefix SAP_ALE_ is then added.
The IDoc adapter checks the prefix and replaces it with the prefix of the corresponding Integration Server inbound queue (for example, XBQI0000).
If you want the receiver to receive the IDocs in the same sequence that they are sent by the Integration Server using the IDoc adapter, proceed as follows:
· In the communication channel, select the check box Queue processing for the receiver.
The IDoc adapter replaces the prefix of the outbound queue (XBQO) with the prefix SAP_ALE_.
You can display the individual messages in the qRFC monitor of the outbound queue. To do this, do one of the following:
¡ Use the queue ID in the list of displayed messages in the monitor for processed XML messages.
¡ Use the transaction ID in the list of displayed XML messages in the IDoc adapter.
¡ Call the transaction qRFC Monitor (Outbound Queue)(SMQ1).
To navigate directly to the display of messages in the IDoc adapter, double click the transaction ID of a message in the outbound queue.
To do this, you must have registered the display program IDX_SHOW_MESSAGE for the outbound queue in the qRFC administration (transaction SMQE) beforehand.
In both cases, the function module IDOC_INBOUND_IN_QUEUE is called, which enables EOIO processing of the messages. The processing sequence is determined by the sequence of the function module calls.
Unlike the other function modules (interface versions from the communication channel), with this function module you have to transfer segment types rather than segment names in the data records.
Serialization of Messages
Use
Serialization plays an important role in distributing interdependent objects, especially when master data is being distributed.
IDocs can be created, sent and posted in a specified order by distributing message types serially.
Errors can then be avoided when processing inbound IDocs.
Interdependent messages can be serially distributed in the following ways:
Serialization by Object Type
Serialization by Message Type
Serialization at IDoc Level
(not for IDocs from generated BAPI-ALE interfaces)
Serialization at IDoc Level
Use
Delays in transferring IDocs may result in an IDoc containing data belonging to a specific object arriving at its destination before an "older" IDoc that contains different data belonging to the same object. Applications can use the ALE Serialization API to specify the order IDocs of the same message type are processed in and to prevent old IDocs from being posted if processing is repeated.
SAP recommends that you regularly schedule program RBDSRCLR to clean up table BDSER (old time stamp).
Prerequisites
IDocs generated by BAPI interfaces cannot be serialized at IDoc level because the function module for inbound processing does not use the ALE Serialization API.
Features
ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
· IDOC_SERIALIZATION_CHECK
checks the time stamps in the serialization field of the IDoc header.
· IDOC_SERIAL_POST
updates the serialization table.
Check the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/78/2175a751ce11d189570000e829fbbd/frameset.htm
Ex: ADRMAS, DEBMAS(customer)
ADRMAS, CREMAS(Vendor)
In this case, Before posting Customer Data or Vendor Data it requires Address Data.
Rgds
Sree m

External kanban- JIT Idoc set to vendor.

Hello
I am setting the partner profile for the JIT Call in KANBAN for External Procurement.
I have defined as follow:
Partner number 6722334
Partner type: LI
Partner function: OA
Message type: PAB_ORDERS (Quantity release from KANBAN)
Outbound option tab:
Receiver port: SAPDEV
Transfer IDOC immed:
Output mode: 2
Basic type: SEQJIT01 (JIT: IDoc for sequenced/summarized JIT calls)
Message Control Tab:
Application PA :JIT call
Message type: ZDKA-JIT Call EDI
Process code: PJN0 (Generation/export of IDOC orders03 for JIT call)
When I am checking Idoc in ME38 under messages it is showing red
the status process is in error, and the error is below:
No corresponding entry in table JITOIT Message no. JIT00017
I check the table JITOIT and it is empty.
Did I miss some in configuration? Or how that table is to be filled?
Rgs
Edited by: sudhir.R.T T on Nov 25, 2011 12:53 PM

Hi Sagar
For the Confirmation you need to do the customizing for confirmation control, like what would you like to do after the confirmation. Confirmation is an inbound process.
For Invoice you need to complete the customizing under LIV in SPRO- for Invoices received via EDI.
Please go throught the help link for further details.
http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm
Reward points if useful
Thanks & regards
Kishore

Sequencing messages in BPM

Hi All,
I have a requirment where i have to send messages sequntially to target.From source i would be receiving 5(say s1,s2,s3,s4,s5) messages.These messages have to be sequntialy sent to target 1,2,3,4,5 in order.
At one instance i would receive only 1 message.Say 1st i received s2 then i shouldnt send it to target,i should wait for s1 to occur.Next instance s1 occured i should send s1 first then s2.This should be my order.
Irrespetive of what source and target systems are i would like to know how this kind of sequencing could be implimented in BPM.
I have implimented "BpmPatternSerializeMultipleTrigger" from BASIS but its not sequncing.
Its erroring in BPM send step.When s2 is occuring,its not waiting for s1 to occur.Even when next instance is s1.
Thanks

HI,
You can use EOIO, but as processing with BPM uses the same queue. You need to control this sequence on sender side.
IDOC SCHEDULING
Sequence files to be execute for XIP
These messages are using the same BPE queue,
please apply note 1040354 BPE-TS: Unprocessed messages. Pay
particular attention also to the guidelines regarding buffering.
thanks
Swarup
Edited by: Swarup Sawant on May 29, 2008 10:59 AM

EOIO for IDOCs to XI

Hi,
My scenario is IDOC ---> xi ---> File.
Need to implement EOIO(serialization) for IDOCs coming from ECC.
Checked "Queue Processing" and assigned rule "FIRST_16_OF_MESTYP".
When I send the IDOC using WE19, I get message "IDocs are stored in the queue".
But, IDOCs are not coming to XI. Please help.
Versions: ECC 6.0 & PI 7.0 SPS 13.
Also, do I need to maintain an entry in IDXQUEUE table?

Hi
use similar thread
How to implement IDOC Serialization(EOIO) using IDOC Adapter
Re: Posting idocs in sequence in SAP from file (without BPM)

Some question on IDOC (Control Record/Data Record/Status Record)

Dear all,
I am new in this area, and would like to enquire some question on this topic.
When I view a IDOC via WE02, each of the IDOC record will consist of Control Record/Data Record/Status Record).
Questions:
I notice that the data records consists of many segment (i.e. E1EDK01, etc) which are use to store application data.
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Thanks.
Tuff

Hi Tuff,
As everything in SAP, with IDOCs too there are
1) Standard IDOCs
2) Standard IDOCs(Extending - Enhancement to an IDOC, to accomodate for custom values)
3) Custom IDOCs
And every IDOC has,
Control record - EDIDC Structure - This mostly reflects the partner profile information, along with few more details which are used for IDOC extension, Sequencing etc
Data Records - EDID4 Structure - These records contain the actual business data of the document in concern. So for ORDERS05 it would contain order details, INVOIC02 - Invoice details so on...
Status Records - These records capture the status of an IDOC from the time it is received/sent from your system and a corresponding business document is created/changed. So this will have messages like "IDOC sent to the port OK" etc which are status from the communication layer(ALE) to application specific messages like "Sales Order XXX created" or "Invalid Material" etc.
You would have noticed something called as Process code in the partner profile, this is associated with a FM(or work flow task etc) which has the business logic coded in.
So in case of an Inbound IDOC, the sending system updates the IDOC - Control and Data records, and sends it to the receiving system. On the receiving system the IDOC's control record is validated against the partner profiles set, if an entry is found then using the process code it finds the associated FM which will decode the data from the IDOC data records as per the IDOC type and then use it to post data into SAP (VIA BDC, Batch Input, BAPI etc).
And all this while the Status records are being updated accordingly.
So with the above context will try to answer your questions,
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
In case of a custom IDOC, yes you will have to.
In case of a standard IDOC, you wouldn't have you just have set up the necessary configuration (Partner Profile, Process code etc)
In case of a standard IDOC extended to accommodate for some custom values(for which there are no fields in standard IDOC - Let us say you have added some new fields on VA01) - In this case you can still use the standard Process code and Standard FM associated with it, SAP provides several Function exits in these FM's which you can leverage to add your custom logic.
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
There are several documents available on the net and on SDN detailing step by step approach for all the above three cases,
just search for step by step guide for IDOCS - sap.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Again it depends, in case of using a standard IDOC you wouldn't have to. But in case you have some customizations/enhancements then you might have to.
For Ex: updating the control record accordingly for indicating that you have extended the standard IDOC. Or append custom messages to the status record as per the business logic.
Try out the examples you find on the net and post any specific questions you might have.
Regards,
Chen

Send IDoc parallel (MATMAS & INFREC & ...)

HI,
i know that it´s possible to send "as an example" with BD10 the MATMAS and INFREC and ... IDoc parallel.
Condition = flag send complete data.
Can you show me how to configure that BD10 sends more than MATMAS IDoc ?
thx,
Gordon

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

T.code wise IDoc list

Hi,
Can we get T.code wise IDoc list...
rgds,
balu

Hi,
Plz check the sequence of trasaction codes that are required for idoc.
Sequence of transaction already done
1.BD54(Create Logical Systems on Sender & Reciever),
2.SALE(Assignment of Logical System to client on Sender & Reciever)
3.SM59(To create RFC destination on Sender only)
Outbound settings:
1.WE31(Create Segments),
2.WE30(Create IDOC types),
3.WE81(Creation of Logical Message type),
4.WE82(To attach message type and idoc type),
5.BD64(To create a distribution model),
6.WE20(To create Partner Profile).
7.WE21(To create Ports)
Write Program to Trigger Idoc from Sender Side.
Inbound settings:
1.WE31(Creation of Segments)
2.WE30(Creation of IDOC Objs)
3.WE81(Creation of Message Types)
4.WE82(TO link Message Types and Idoc Type Objs)
5.WE42(To Create Process Code)
6.BD67(To attach FM to Process Code , On saving it goes to BD51 directly)
6.1 BD51 (To Configure FM as per input)
7.WE57(Assign. of FM to Msg Type and IDOC Type)
8.WE20(To create Partner Profile)
Write code for accepting data from IDOC send by sender . This has to be written in FM source tab with appropriate inport fields
and export fields .
Tips: The name of message type , idoc type , segment type and logical systems name on both sides should be same.
Hope this helps you.
<removed_by_moderator>
thanks,
dhanashri.
Edited by: Julius Bussche on Aug 13, 2008 4:21 PM

Setting EOIO for outbound processing of idoc

Hi ,
In case of standard Idoc processing ( using ALE Services ), we are not configuring Idoc adapter and sender communication channel. I want to set the quality of service as EOIO. How can I do the same??
Please help.
Pragati.

hey
have a look at the following
Re: Posting idocs in sequence in SAP from file (without BPM)
thanx
ahmad

IDocs in sequence

Similar Messages

Maybe you are looking for