File to IDOC - Serialization

Hi experts,
i have been through the OSS note 152239 :
Symptom
In the ALE inbound IDocs are not processed in the same sequence as they are generated in the receiving system (IDoc number).
Additional key words
RBDAPP01, serialization, swapped, EDIDC-SERIAL
Cause and prerequisites
Cause: In the control record of the IDoc the field SERIAL is not filled.
The sequence of the IDoc numbers in the receiving system does not always correspond to the creation sequence in the sending system.
However, the processing sequence in the ALE inbound should correspond to the creation sequence in the sending system. Therefore the IDocs in the ALE inbound are sorted according to the field SERIAL during background processing.
Preconditions:
IDocs come from an external application (no R/3 System)
Background processing with program RBDAPP01 (Transaction BD87)
Solution
Check whether the field SERIAL is filled in the control record of the IDoc: Up to Release 4.5B, out from the display of IDoc the control record display; via Goto -> Serialization info the field is displayed.
If the field is empty, it must be filled in the transmission system in the control record the IDocs(structure EDIDC) are filled. For example, a time stamp like the following is suitable:+ YYYYMMDD_HHMMSS
In my mapping, I tried to insert the timestamp in the field SERIAL of the idoc, but I have a problem, there are many mandatory fields such as : TABNAM, DIRECT, IDOCTYP, CIMTYP, MESTYP, SNDPOR, SNDPRT, SNDPRN, RCVPOR, RCVPRN in which I have no idea what to put in ??
any help would be appreciated,
Kind regards,
Jamal

Hi,
For serialization find below links for more help
http://help.sap.com/saphelp_erp2004/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc1869733413
http://help.sap.com/saphelp_nw04/helpdata/en/78/2175a751ce11d189570000e829fbbd/content.htm

Similar Messages

File XI IDOC (Serialization )

Hi Experts
i have this scenario : A csv file is coming from the 3rd party and is converted into idoc at Pi and being updated in R/3 system.
i have been going through blogs, where i noticed "serialization " . what is meant by "serialization "? All the blogs were discussing the scenario as" IDOC > XI > FILE". For my scenario should we use the "serialization ".
thanx in advance

Hello...
Have you checked the replies in this thread:
When IDoc Serialization is required ?
>>All the blogs were discussing the scenario as" IDOC > XI > FILE". For my scenario should we use the "serialization ".
Your scenario is file to IDoc right? So if you are planning to create one file from one IDoc then no need of serialization (as each file will be creating only 1 idoc)
But if you want a single file to create multiple IDoc, then you may want to serialize the Entry of IDocs into ECC
Regards
Suraj

How to serialize File- XI- IDoc

Hi,
we have a scenario FILE->XI->IDoc.
The IDocs (one special idoc type) have to be send to ERP 2005 in serial order (not parallel).
I know, that I can solve this problem with queues (one queue for this interface) - but how can I manage it?
All other interfaces should still work parallel.
Regards
Wolfgang

Hi Michal,
wow - it work's ... but the idocs in ERP 2005 have now the state 75 (yellow) (in WE02; the message is: IDoc received via qRFC).
All messages a sent to ERP via exactly the same queue - called SAP_ALE....
Do you have an idea with state 75.
But you helped me a lot ... Thank you!
Before I wrote this thread, I checked your book, but you described the scenario IDOC -> XI -> ... and not opposite.
You see - I bought your book ... and now I should read it ))
Regards
Wolfgang

Help needed in a file to idoc scenario

Hi all,
The scenario is file to Idoc via XI. The problem here is the input file might contain both the PO create and PO change in the same file.
Assume the first record is PO create and When we post this via XI there could be a delay for creating the PO in the SAP.
Meanwhile even if the second record (say that's the PO change for the first PO create record) gets processed parallely there could be a possibility of error saying that PO is not created.
How do we handle this in XI??.. If we use Queue Processing in IDoc adapter it'll guarantee only the delivery order and not the processing order if I'm right?.
Please guide.

Saravanan - IDoc preocessing can be handled by serialization. This will guarantee also the order of processing.
 
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/frameset.htm" target="n">SAP Help - IDoc serialization in XI</a>
 
 
Peter

XI Problem: File to Idoc Scenario - IDOC_INBOUND_ASYNCHRONOUS

Hi,
I'm having problems with inbound IDOCS in R/3. The idocs from XI are sent as tRFC using the FM IDOC_INBOUND_ASYNCHRONOUS and this is a problem because i have like 200 or 300 idocs to be sent at the same time and each IDOC takes like 5 minutes to process, hence the system crash due the amount of simultaneous logins (error message ThISend: ThRollout ).
I need to fix this problem using some kind of serialization and the use of the function module IDOC_INBOUND_IN_QUEUE.
Does anyone know how to achieve this?.
The scenario configuration in XI and R/3 is as follows: (PI 7.0 SP15) - (R/3 SAP ECC 6.0)
File to Idoc.
Sender CC->
File content conversion
Exactly once in order
Receiver CC->
IDOC protocol
Queue Processing
R/3 Partner profile config.
Message type BOMMAT
Trigger immediately
Thanks.

Hi,
You have to split the messages in the sender file adapter, by using the parameter "Recordsets per Message".
I hope that it will solve your problem. Please see the below link, it might be useful to you.
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards,
Rajesh

File- to -IDoc scenario EXPLINATION in a INTERVIEW

Hi ,
What are the configurations done on XI, on R3, on XI's SLD, what is the protocol used for File, Content Conversion, Serialization , etc
I know how to do the step by step procedure... but plz let me know how can we explain the same thing in an interview..
plz give a small explination about all the above steps..
thanks
Babu

> Hi ,
>
hi babu,
> What are the configurations done on XI, on R3,
configuration on XI
RFC destination to R3
Loading metadata
configuration on R3
create a logical system
RFC destination to XI
create a Transaction Rfc pointing to XI RFC Destination
>>what is the protocol used for File
Here it depends on the where the file is located. If the file is in same Local network as XI is then NFS (Network File system is best suited)
Otherwise FTP
FTP protocol is used more frequently
>Content Conversion
In case of File to IDoc and suppose if the file that need to be picked up is not in XML format then we will go for Sender File Content conversion, otherwise not
>>XI's SLD
You will create a technical system for
R/3 system
Third party system (file system)
You need to create a business system for the R/3 Technical system
regards
Ramesh P

IDOC serialization

Hi Experts,
I am doing the scenario file->PI->ECC.
I would like to know how can we do the IDOC serialization (Object channel serialization) .
In my case we need to ensures that documents are processed in the receiving system in exactly the same sequence in which they were created in the sending system.
As per the note 752194 the Object channel serialization will best suite my requirement.But how can i achieve when i am sending the IDOC xml from PI--> ECC.
I want to know what are the settings we need to do in XI and ECC??
Do we need to generate channel number in XI..?? if so how??
If i want to do for orders IDOC...what we need to do BD105 and BD104 transactions.??
Where we need to call ALE_SERIAL_KEY2CHANNEL function module..??
Note: I dont want the serialization for ECC--> XI

Please post this in PI forums
Anil

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

Logical System in file 2 idoc

Hi
I am developing an scenario of file to idoc.
My problem is, when it is generating the idoc in target system, the Parner Number in control record is filling with the logical system name given when creating the business system.
I tried changing the logical system name with actual partner number which I want but giving an error ' The selected integration server already has a business system with logical name "pidclnt001". Select a different integration server or change the logical name. '
Can anybody advice me, is it not possible to create two scenarios to send same Idoc to same system ?
Regards,
Shylesh

Hi Shylesh !
You need to enable the header mapping option in your receiver agreement to overwrite the Logical System name that is sent to the R/3 destination system...which now is the Logical System name linked to your sender system (info is in SLD if is a business SYSTEM or in the Adapter Specific identifier attributes if it is a business SERVICE)
You cannot have more than 1 business service/system with the same Logical System name...but you can overwrite the sender logical system name that arrives to the destination R/3 system using the header mapping section of the receiver agreement as noted above.
Regards,
Matias.

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

File to Idoc OR File to AbapProxy

Hello,
Let me expose my problem.
In fact, I need to integrate new Goods Movements sent by a non-Sap system to ECC system.
To do that, the non-sap system sends a file.
Then, I need to generate from this file an Idoc (MBGMCR), fill this Idoc with some extra data (from Ecc tables) and then to integrate it into ECC.
The question here is to find the best solution (according to performance and feasibility) to do that using PI (7.0).
We are hesitating between two scenarios:
1- File to Abap Proxy
We get the data sent by an abap proxy, and then we complete it with the necessary extra data from ECC tables in order to create complete the Idoc segments.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Even, using PI will be a waste of performance/time (due to mappingu2026)
2- File to IDOC
This alternative looks more interesting (at least in the PI way).
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
For example, the file contains Orders headers and I need to generate Goods Movements for the materials contained in the orders. So I need to access Orders posts, to retrieve the materials data.
Is there a way to retrieve simple information in PI using ECC data?
Any other suggestion/comment is welcome.
(Any other scenario is also welcome)
Thanks you in advance.
Saber L.
SAP PI consultant.
Edited by: LMS LMS on Nov 7, 2008 10:24 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM

ABAP proxy would improve performance in terms of providing adapterless communication.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Making a direct connection would increase point to point connectivity across the organization whose reduction is one of the reason why XI is used.
If ur communication is async and u have the idoc structure ready, then u may proceed with Idocs.
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
If you want to prevent the node from getting generated, simply disable it in mapping.
I hope u have seen this
Choose the Right Adapter to integrate with SAP systems
Regards,
Prateek

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Error in file to idoc scenerio

hi
in file to idoc scenario
i got error in sxmb_moni
in status it is showing recording,
in Q.status it is showing stop symbol.
waiting for suggestions.

Hi Sandeep,
Have a look at queue problms here
/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
Some additional help
Q.Status is "Queue stopped"
queue status is stopped
Regards,
Prateek

Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

File to IDOC - Serialization

Similar Messages

Maybe you are looking for