Collect Idocs to XML

Hi experts,
I have a requirement which is as follow :
for sending materials to legacies from SAP, we need to create a file on legacy side.
Is it possible to collect in 1 XML file the data of the sent idocs during the day? Iin order to then do the mapping based on this file to create the target file? I heard that we could do that on SAP Side, which create an XML file based on the idocs data.
Thanks a lot,
Jamal

Hi Jamal,
> But if for example this maximum is not reached at the end of the day, is there a way to trigger the creation of the file anyway ?
You can specify one job in sap for the program RSEOUT00 for the maximum number of idocs so that if maximum number of idocs reached the idocs in teh xml file port would get triggered.
Also you can specify another job for the program RSEOUT00 with no. maximum number of idocs and schedule it only once for the whole day, so that if the above job where maximum number of idocs doesnot reach then this would get trigger. I think here one idoc would create one file (without colelction).
In stefans blog you can seee my question at the end which should give you an overview of your question also.
If this is not feasible then as michal suggested you can see a different option from his blog.
Regards,
---Satish

Similar Messages

Collect IDocs to Single Request message without BPM

Hi Experts,
My scenario is IDoc to SOAP.
PI receives multiple IDoc with same message type. ECC pushed bundled IDOcs to PI via HTTP port.
Ex: <CLFMAS>
 <IDOC1>
 <IDOC2>
 <IDOC3>
The receiver is SOAP channel.
I would like to achieve mentioned output structure without BPM.
Input Structure:
<CLFMAS>1..1
 <IDOC1> 1..999999
 <Employee>1..1
 <EmpID1>1..1
 <Location>0..999
 <JAPAN>0..1
 <Location>
 <FRANCE>
 <Location>
 <BRAZIL>
 </IDOC1>
 <IDOC2>
 <Employee>
 <EmpID2>
 <Location>
 <BRAZIL>
 <Location>
 <JAPAN>
 <Location>
 <USA>
 </IDOC2>
</CLFMAS>
Output structure:
<RequestMessage>1..1
 <GroupListType>1..1
 <GroupList>0..Unbounded
 <JAPAN>1..1
 <EmpID1>0..Unbounded
 <EmpID2>
 <GroupList>
 <BRAZIL>
 <EmpID1>
 <EmpID2>
 </GroupListType>
</RequestMessage>
Pointers will be very helpful.
Thanks
Ray..
Edited by: RayPIUS on Oct 16, 2011 6:21 AM

HI,
-> you go with IDOC packaging concept. we have three approaches collecting idocs,
 1. by using tRFC port
 we need create rfc destination(SM59) and port of tRFC(WE21) and ccreate partner profile(WE20), in partner profile we have to specify the packet size.
 then coming to PI in ID we need to create sender communication channel for IDOC there we have to provide packet size.
2.by using XMLFILE PORT
 Please refer this blog it will help you
 Collecting IDocs without using BPM
3.by using XML HTTP PORT
please go through this blog i hope this will help you
-> IN PI we have message packaging concept.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c?quicklink=index&overridelayout=true
regards,
ganesh.

ALE/IDOC to XML - Need to Change the xml tags

Hi Experts,
I am creating xml files from idocs via ALE and an XML Port and sending them to a third party system (no programming required, all standard functionality). The field labels or tags within these xml files are automatically generated by SAP based on the idoc segment definitions. Unfortunately, the receiving system cannot process these tags...they require very specific tag names.
Is there a way to interceed before the actual files are created and change these tag names? If so, how?
Thanks very much for useful information!
Deb

Hi Rejoice S
see following blog define tyour scenario step wise step
Collecting IDocs without using BPM
if helfull give rewrad point
thanks
Amit Shivhare

Regarding receiver determination problem in IDOC-XI-XML file scenario

Dear All ,
In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
Can anybody suggest what could be the reason behind this .
Thanks in Advance
Prabhat

Hi PRabhat,
In RCVR determination, you need to select the party & service (as appropriate) save the obeject
then refresh the configuration overview of recr det.
then you can see the partner/service
then you can open it & add the necessary objects.
Regards
Vishnu

IDOC not coming in status 30 for collecting idocs

Hi All,
We have a requirement in which we need to collect idocs and send together.
To achieve I am making Collect idocs in Partner profiles so that it goes in status 30 and hence I can run program RSEOUT00 to make it status 03 and hence write in file as a group of idocs.
Now inspite of making collect idocs in partner profile, its not coming in status 30 but directly coming in status 03.
Please let me know what may be the reason for the same.
Thanks,
Vivek

Hi vivek,
If you have set the Collect Idoc option in partner profile then the IDOC's will be collected , irrespective of kind of port you are using and the packet size doesn't matter in this case.
It seems to me that the program RSEOUT00 is already scheduled in your system.
Can you check in SM37 , by putting the program RSEOUT00 and check if any user has scheduled the program.
Hope this helps.
Harry

How can I convert IDoc in XML format w/DTD into a string?

I want to send by e-mail outbound IDoc in XML format with its document type definition (DTD).
I want to be able to get the same output result into a string than the XML file IDoc port type with DTD activated. I have created a FM (based on SAP "OWN_FUNCTION") assigned to an IDoc port of type ABAP-PI that executes the following processing steps:
1-Extract outbound IDoc information to get the sender & recipient mail addresses (EDP13 / EDIPHONE tables).
2-Convert & Transform IDoc data into XML string using FM IDX_IDOC_TO_XML.
3-Prepare and send e-mail with XML attachement using FM SO_NEW_DOCUMENT_ATT_SEND_API1.
I cand generate the e-mail with the XML file attachement but FM IDX_IDOC_TO_XML does not convert the IDoc with proper formating and DTD.
What should I use to accomplish the IDoc conversion to XML w/DTD into a string?
Should I use XSLT tools ?
How does that work?
Thank you
Carl

muks wrote:
Use decimal string to number
Specifically, you can define a constant with a different datatype on the input on the lower left if you need a different datatype (e.g. U8, I64, DBL, etc) Are all your values integers or do you also need to scan fractional numbers? In this case, you should use "fract/exp string to number" instead.
LabVIEW Champion . Do more with less code and in less time .

Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interfa

Hi
i am try do
Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface
With The help of SDN Contribution
link----
( have look on it)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4943f2b7-0a01-0010-37af-faff35b2f08c
I am getting error in
Partner system as HTTPLOG and "Execute" to check the results
Error is -- Port could not be created
RFC destination HTTPLOG Not specified for system HTTPLOG
any 1 have any idea if plzzzzzzzz...........
Thank u
Ram

Hello .
we are also in process of implementing the same
could you share the knowledge pl?
1)is it a separate add on with ALE to saphr
or using ECC ??
2)can u share the configuration part ??
we are trying it on webas as addon 3.0 .

Inbound IDOC using XML

Hi,
I need to create an Inbound IDOC using Function modules using an XML file as Input.
I am using mySAP ERP 2004(WAS 6.4).
IDOC type : HRMD_A05
Message Type : HRMD.
I am using the FM's in an ABAP report for testing, reading the data from the XML File using the FM GUI_UPLOAD .
I tried using the FM IDOC_INBOUND_XML_VIA_HTTP,with import parameters XML_STREAM, CONTENT_LENGTH, CONTENT_TYPE, REMOTE_ADDR.(ALL Type Strings)
This FM creates the IDOC successfully but i do not get the status record for the IDOC as there are no export parameters or tables where i can get the value.
I am trying using the FM IDOC_INBOUND_XML_SOAP_HTTP,with import Parameters as XML_STREAM type XSTRING,and there is the export parameter ASSIGN ,type IDOC_ASSIGN_TAB and i was wondering if this could return the status.
I used the same XML and used the FM "SCMS_STRING_TO_XSTRING", to convert the file input string into XSTRING.
On executing this i get the exception,"NO DATA RECEIVED" .
Can anybody Please Tell me
1)How to get the status of an IDOC if i use the FM IDOC_INBOUND_XML_VIA_HTTP ?
2)How to use the FM IDOC_INBOUND_XML_SOAP_HTTP ?
3)Is there any other way to create an IDOC with XML input?
Thanks,
regards,
Siddhartha Jain

HI Nagarajan,
I had checked the first link mentioned by you and activated the required service from Transacttion SICF,but still it didn't help.
The second link points to the IDOC Adaptor for XI,guess it won't help as i'm not using XI.
I want to pass XML data read from file and call a FM which creates and posts and IDOC into R/3 and returns the IDOC Number and Status.
For this i found the FM's IDOC_INBOUND_XML_SOAP_HTTP and IDOC_INBOUND_XML_VIA_HTTP.
The FM IDOC_INBOUND_XML_VIA_HTTP accepts xml as string and posts IDOC succesully,but i do not get the status and IDOC Number.
The IDOC_INBOUND_XML_SOAP_HTTP accepts xml as xstring,so i used the FM SCMS_STRING_TO_XSTRING to convert the same xml string to xstring and pass it to the FM.But it gives an error 'NO DATA RECEIVED'.
If i make few changes to the XML doc,to include SOAP envelope ,like
<?xml version="1.0" encoding="UTF-8"?><HRMD_A05>.......</HRMD_A05>
to
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><IDOC BEGIN="1">.......</IDOC></soap-env:Body></soap-env:Envelope>
I get the error,the tag <IDOC BEGIN="1"> not found ,the IDOC XML should be of format <IDOC BEGIN="1"> <IDOC>.
Can anybody please help on what to do/how to proceed.
Thanks,
Regards,
Siddhartha

Partner profile settings - Trigger Immediate or Collect Idocs ??

Hi All,
We have EDI Setup between SAP and a EDI system and Idocs flowing with port type TCP/IP connection.
we are facing issue at some times where in the Idoc is created and is in status 03 / 12 (trfc queue is cleared) but not found in the EDI system.
what I have observed is the issue has occurred for only few vendors where partner profile setting in trigger immediately
and it has not occurred t for every Idoc created, only some Idocs were missing in EDI system.
issue was not present in case where partner profile setting in collect Idocs.
So it that do we have a best practice to set partner profile to collect Idocs (packet size ~ 20) when sending to EDI subsystem?

Hi,
It seems the issue is not because of your partner profile setting since your status of the IDOC is 03 0r 12.
Output mode 'Transfer Idoc Immediate': Single Idoc is transfered immediately to the EDI system when the output triggered
'Collect Idoc': Idocs generated for the particular message type will be collected in a single file and are triggered to EDI system at a scheduled time. Here no of Idocs sent in a file will be decied based on packet size.
It may be problem with your network connectivity.If are using a EDI substem then you use file port not trfc port.
Check how the EDI sytem is reading the Idoc files which are created in R/3 OS level is it through FTP???
Regards
Praveen

IDOC-XI-XML Scenario Questions

Hi everyone,
I am actually trying to configure a scenario starting from SAP and finishing creating a XML file.
R/3 IDOC -> XI -> XML file
The XI is receiving IDOCs from SAP correctly, but when it try to send to third party system, the monitor engine (SXMB_MONI) are showing the following error: HTTP_RESP_STATUS_CODE_NOT_OK.
I am currently using the File Adapter, please take a look at the config for the communication channel:
Adapter Type: File
http://sap.com/xi/XI/System
SAP BASIS 6.4
Transport Protocol: File Protocol(FTP)
Message Protocol: File
Adapter Engine: Integration Server
Target Directory: / (root)
File Name Scheme: mptest_xi_output.dat
File Construction: Create
Overwrite File: X
File type: Binary
Adapter Status: Active
Regards,
Gabriel Santana

If you have enough authorization, then click on the last button which is change button.
Otherwise, open two windows of SAP and try to do the above step and when you get the authorization error, go to the second window and enter transaction /nSU53. Send that info to your security team.
Once you have authorization you should be fine.
One other thing, in which client you are doing this ?
Do not use DDIC user to change it.
regards
Shravan

Idoc to XML, namespace is not getting created in output XML

Hi All
My interface is idoc to XML.
I am using graphical message mapping.
In output xml , namespace is not formed
Can any one tell why namespace is not created in the XML and
How to add the namespace to the output XML .
Kindly help
Regards,
Sheela

Hi,
You can change your external definition to achieve it. just compare the structure of your xsd with some other normal data type xsd and change accordingly.
Inder

IDOC to XML file scenario with party

Hi All,
I am developing a IDOC to XML file scenario with party in which I have extended the MATMAS idoc and configured the receiver FILE communication channel.
But its giving me the error *"No receiver could be determined"* with party. If I run the same scenario without the sender party its working fine.
And sender is my R/3 system under party P_Party and receiver is my third party system under P_Party.
Thanks in advance.
Gaurang

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

IDOC to XML : error in opening the output file in iexplorer

Hi Frnds,
I have a scenario IDoc to xml where in Im getting some non ascii values in the idoc for which I used ISO-8859-1 encoding technique but still the conversion is not done. Iam unable to opend the output file in internet explorer giving the follwoing error as :
An invalid character was found in text content. Error processing resource
Please help me how to overcome this issue.
Thanks in advance,

Hi,
As i posted previously in xi UTF-8 is the default encoding if message protocal is FILE.
And UTF-8 encoding support unicodes..
Can reconfigure your receiver file adapter with file type as Binary and check once again.
go through http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
refer File Type
now i check with a japanese double byte character and i can open in iexplorer.
regards,
pradeep A.

Mapping issue for Idoc to xml

hello all,
 my scenario is idoc to xml file
E1EDKT1-------segment (1:n)
 -TDID----
ele
 -E1EDKT2----segment (1:n)
 -TDLINE-----ele
When TDID value is X then all values in TDLINE of undeline sement E1EDKT2 needs to be cocatenated and passed to target elemnt A
if TDID value is Y then all values in TDLINE of undeline sement E1EDKT2 needs to be cocatenated and passed to target elemnt B
i have written java function(for all values in context) to conctenate TDLINE elements.
also the context of TDLINE is changed to E1EDKT1.
i am getting all the concatenaed values of TDLINE for TDID=X in target element A but i am not geting any value in target element B for TDID=Y
can any one suggest what could be the problem.
Regards,
Sandip

Hi Sandip,
Map like this for target element A:
use simple if stament. and for If give TDID equals(text function) to constant X
and for then TDLINE-->concattdline(udf) --> output A
Map like this for target element B:
use simple if stament. and for If give TDID equals(text function) to constant Y
and for then TDLINE-->concattdline(udf) --> output B
concattdline udf:
Create a Context udf with one argument a and name it as concattdline.
Imports: java.*;
Add this code:
//write your code here
String value = "";
for(int j=0; j<a.length - 1; j++){
 value += a[j] + "";
value += a[a.length - 1];
result.addValue(value);
I just tested this and it should work for you.
Regards,
---Satish

Automate flat IDOC to XML IDOC using one interface

Hello all,
We are currently going through a migration process where XI will be replacing a legacy system. As part of our testing procedure, we are using historical data pairings from the legacy system and using an automated tool to compare if the interfaces we develop in XI match. The catch is we need the data that we are comparing in XML format for the automated tool to be able to do the comparison, and unfortunately the legacy data is a flat format. So now I would like to automate a way to convert this data to XML format.
Specifically for IDOCs, I would like to have an interface which picks up the flat files, transforms them to XML, and then drops them back into another file directory in the XML format. It would need to be able to pick up any kind of IDOC (given that XI has the metadata already imported), recognize what message type it is, then do the conversion.
I have been reading on SDN and found that there is a standard tool to do the conversion, but it appears it can only handle one kind of IDOC at a time, and it appears it only picks up one specifically named file at a time.
Has anybody tried to implement a scenario like this? Any help is appreciated (A walkthrough would be the best!).
Thanks in advance,
Mike

Mike,
What version of PI will you be using? PI 7.11 can now auto-convert Flat File IDocs to XML IDoc and vice versa.
Here is the documentation:
http://help.sap.com/saphelp_nwpi711/helpdata/en/b5/bd93642dd3410f90ebea702399fac4/frameset.htm (flat to XML)
http://help.sap.com/saphelp_nwpi711/helpdata/en/74/a45bc07e2043fb9b63295229178903/frameset.htm (XML to flat)
I have not tried this personally, but seems like you might be able to use a "File to File" scenario with no mapping, and use the "IDOCFlatToXmlConvertor" Module in your File Adapter Comms Channel and it may just work, giving you files that are the IDoc XML version of the flat file it is reading. It looks like it does an RFC call to the back-end SAP system where the IDocs are originally from (or could be any system as long as you know the IDocs in there are identical), and reads the IDoc metadata (which has always included flat file field offsets for each IDoc Segment Field), and applies that either to convert from flat file IDoc to XML IDoc, or XML IDoc to flat file IDoc.
It does mention that there is a limitation that there can only be one IDoc in the source flat file - could be a problem if you have many in one file, which is pretty typical.
Regards,
Brendan

Collect Idocs to XML

Similar Messages

Maybe you are looking for