IDoc - SFTP (Flat File) file name

Dear Experts,
 Thanks for helping me so far, please find below my new request :
 We have IDoc - SFTP (flat file) scenario in which I have did ESR by pass scenario and used standard module to convert IDoc xml to flat file.
 But now user is asking to have the naming convention of the receiver flat file as SHPMNT05_<IDoc number>_<Reference number>.idoc.
 Could you please let me know how this can be approachable. Many thanks in advance for your valuable inputs. Awaiting your replies.
Thanks
Ravi..

Thank you very much Botha,
In the thread Idoc to file problem with DynamicConfiguration please find below my doubts.
1. I am using receiver SFTP adapter and IDoc to flat file module configuration as key 1, so how it will works.
2. What are the Parameter name and Paremeter value for the module mentioned in the blog :
Module Configurations:
1 key.0 write http://sap.com/xi/XI/System/File FileName
1 value.0 message.interface
Which is the parameter and which is the value in the above blog.
Waiting for your response.
Thanks
Ravi

Similar Messages

IDOC-- PI-- flat xml file

Hi ,
we are working on a HR IDOC>PI>flat xml file scenario.
Idoc name is HRMD_A07.
we have consolidated some 10 interfaces together.
Plan is to,
1)(master interface) get the idoc data into a flat xml file, where flat xml consists of unique fields of all 10 interfaces.
2)Later, use flat xml as input to 10 interfaces, which are FILE>PI>FILE.
we are facing problem in master interface. The data is not coming properly in flat xml.
Can you guys suggest the proper way to do this.
should we use,
1)abap mapping, with standard functionality to convert idoc to flat file?
2)write a udf to get the proper data?
pls suggest the best approach.
san.

Hi San,
you gave us nearly no details, so it is hard to give you any recommandation.
PI provides 4 general possibilities for mappings:
Graphical: Standard and for simple cases the best solution
XSL: Webstandard, in some cases much less development time compare to graphical (if the message structure changes)
ABAP: For special cases (access to ABAP tables, operations before parsing)
Java: For special cases
Regards,
Udo

Variable Substitution for IDOC-XML-Flat File

Hello
I have a scenario where I need to populate the Idoc number into my file name. the Source is an Idoc and the Target is XML but the target is then converted to an Flatfile via a module in the processing sequence. When I try to use the variable sub method it errors out as the final target structure is a flat file and not the XML structure that I hav used in the graphical mapping. Any help on how I can go abut doing this will be greatly appreciate.
Thanks
Lavanya

IF I remove my adapter that converts the XML file to Flat file from the module sequence this works perfectly. So is there a way for me to now read the xml file for the target file name in variable sub. but still have the Flat file structure derived for the processing seq.

Inbound IDOC Format (Flat File)

Hi,
I'm using SAP CRM Middleware for communication between CRM and Legacy System.
I have configured Outbound IDOCs and I see something like this:
EDI_DC40 2200000000000000023700 3012 CRMXIF_PARTNER_SAVE_M01                                     CRMXIF_PARTNER_SAVE_M
E201CRMXIF_PARTNER_COMPLEX000 220000000000000002300000100000001CRMXIF_PARTNER_COMPLEX
E201CRMXIF_PARTNER_HEADER000 220000000000000002300000200000102CRMXIF_PARTNER_HEADER         BusinessPartner                 U
E201CRMXIF_PARTNER_KEYS000    220000000000000002300000300000203CRMXIF_PARTNER_KEYS           0000000014488DDB8AD891249EE10080010A6CA883
The questions are:
I need to know how do the following information must be filled in an Inbound IDOC:
The first characters I understand that corresponds to the Structure name, IDOC Number, IDOC Line...
So I need how do fields like IDOC number must be filled in an Inbound IDOC
Thanx in advance..
BTW. I'm expecting IDOCs as flat files so I need to explain to the Legacy Technician how to fill this fields.

Hi,
Go to transaction WE30 and give the IDoc basictype name CRMXIF_PARTNER_REL_SAVE_M01 and press the view-button (or press F7 key).
This information you will need.
The records are builded using the following structure:
1st record contains control record information and follows the structure of table EDIDC.
Starting at where "220" is given (this is the CLIENT), it is followed by the IDoc number field DOCNUM (16 digits) and so on. Not all fields must be filled, only those that are used for inbound messaging. Keep here in mind: Less fields filled will probably work better (because SAP will add its own details on arrival of the IDoc).
All following records follow the structure of table EDID4 upto the field: HLEVEL (Hierarchy level, identical to the level found in WE30).
Thereafter it is followed by the name of the segment (including spaces) and after this it will follow the exact structure of the segment.
To view a sample, just generate a dummy (test) IDoc and use transaction WE19 to fill in the fields after changing to the correct IDoc type.
Hope this helps you out.
Regards,
Rob.

Multiple idoc to flat file

Hi,
i have a scenario from idoc to flat file.There is two idoc that send message in same file.Without flat file content messages come succesfully.the format should be following:
at the first row should be the first idoc,
at the second row should be the second idoc
01 1FONEX0045               FONEX0045               FONEX SIVI SABUN 400+850ML FLOWERS                    =>1.idoc
02 1FONEX0045               8691988000162           8691988000162                                                             =>2.idoc
01 1DOVE0199                DOVE0199                   DOVE SAC DOKULMELERINE COZUM SAC BAKIM M     =>1.idoc
02 1DOVE0199                8718114638348           8718114638348                                                               =>2.idoc
Thanks in Advance
Nurhan

Hi,
You have to MessageTransformBean Module.
The MessageTransformBean module enables conversion of XML files to flat files and vice versa. You can use this module in the sender and receiver communication channels.
In receiver communication channel, specify MessageTransformBean module before standard adapter module CallSapAdapter and use
Module Name: localejbs/AF_Modules/MessageTransformBean
Module Key : XML2Plain
Please see the below links, it might be useful to you.
/people/gabrielsagayaselvam.panneerselvam/blog/2009/12/07/standard-adapter-framework-modules-afmodules-in-pi-71-150part-2
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/frameset.htm
Regards,
P.Rajesh

IDoc to Flat File in SAP PI 7.11

Hi Experts,
I am working on PI 7.11 and I have scenario from Idoc to Flat File.
Idoc is posted from source side R/3 system.My requirement is "With out Converting the Idoc structure to XML Structure i want to send the data to Target system i.e. File system.
But the structure of the target structure is different from source structure.
My questions are:
1). Is it Possible to send the data to Target system without converting Idoc structure in to xml format through our PI 7.11 ?
2). If possible please provide me the way that executes in the Interface is?
Could you please provide the Inputs.
Best regards,
satya.T
Edited by: satyatanuku on May 24, 2010 3:26 PM
<Moved from Trial, Preview~ forum>
Edited by: Prateek Raj Srivastava on May 25, 2010 1:02 PM

Hello Folks ,
I am also facing the same scenario please provide me any options to achieve this scenario .
I am searched in Forums of SDN but no inputs or blogs available.
Let me know i am having one solution is it right or wrong ?
we have to achieve this IDOC Tunneling .... is it right friends ?
Still inputs required....
Regards,
Ravi.

Doubts in SAP(Idoc)-XI-Flat file scenario

Dear All,
I am sending Delivery Idoc from R/3 and I am able to view the Idoc in XI in transaction IDX5. Also i m able to see the XML structure with the data of the idoc in SXMB_MONI.
Now as per my scenario I have to download this to a flat file from XI.
My question is, should I have to do the creation of Data types, message types, mapping interface & interface mapping in IR or should I directly do the designing in the ID.
waiting for your reply.
Warm regards,
N.Jain

Hi,
DT, MT, MI : you will create these things for receiver flat file only.
First create
In Integration Repository :
1.     Import structure of IDOC in your scenario, In imported objects  IDOCs
              a.     In Interface Objects
1.     Create Data type for your flat file
2.     Create Message Type
3.     Create Message Interface (inbound Asy.)
              b.     In Mapping Objects
1.     Message Mapping : IDOC to Message Type of Flat File.
2.     Create Interface Mapping : IDOC to Flat file by using Message Mapping which you have created.
Make activate all these things.
In Integration Directory :
1.     Create Communication channel for File Receiver.
2.     Sender Communication channel is not required.
3.     Create Receiver Agreement.
4.     Sender Agreement is not required.
5.     Interface Determination
6.     Receiver Determination
At sender side you will take your IDoc and at receiver side you will take your flat file.
It can help you,
Regards,
Sandeep Kaushik

R/3 46C(IDOC) -- XI -- Flat file scenario

Hi
Is there anyone who could give me information on a R/3 46C(IDOC) --> XI --> Flat file scenario?
Many thanks!
br
Göran

Hi Manish
We are using a standard IDOC called PROACT.PROACT01
(We are using transaction sa38(Report RSMIPROACT) in R/3 to send our IDOC.)
First we create the technical and business systems in SLD
Second we transfer these to the repository.(I think the only thing you need to do is to update the SLD cache to get them there - Design : Integration builder --> Environment --> clear SLD cache)
Then we just use the configuration wizard(Configuration : Integration builder --> Tools --> configuration wizard) to map everything together - defining sender and receiver etc(You get the configuration wizard tool by patching XI to patch level 4 or 5).
I assume that you have made all the configurations accordingly to the XI configuration guide which you can download from the service marketplace.
This is just a hint but maybe it can give you a start.
br
Göran

IDOC to flat File----Problem in File Content Conversion at receiver

hi experts,
I am doing a IDOC to flat file secnario.
My requirment is IDOCXI-Flat file
Format of flat file is like:--
Every segment in the IDOC will be converted into a single line of file(without any delimiter). So number of lines in flat file will be equal to number of segments in IDOC.
I am facing problem in File Content conversion.
Please help me out..
Thanks
Jaideep

Check this doc...
[How To...Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a]

Idoc to flat file using Integration process does not show up at all

Hello All,
I created a scenario IDOC to Flat File using Integration Process and one without IntegrationProcess. I am able to execute the one without Integration Process easily.
However when I send the IDOC from SAP then the Integration Process scenario just does not work.
I Checked SXMB_MONI There is no entry for the Integration Process.I can see entry for other without Integration Process.
SXI_CACHE : I can see my Integration Process active
SWEQADM : I have activated the Event Queue and Background job
SWF_XI_ADM_BPE : ALL BPE is showing green status.
All syntax check on IP are fine.
There is no Basis Help for me so there could be some additional basis steps which need to be configured. Has anyone faced such an issue with Integration Process?
Regards
Prashanta

Hope this might help you. when u configure an IDoc as Sender with BPM this is how you proceed.
1. let us split the scenario into two.
a. Sender to BPM ( Integration Process).
b. BPM to Receiver.
2. First let us configure the first Sender to BPM.
a. Sender Agreement( Not required ).
b. Receiver Agreement( NOT Required).
c. Receiver Determination( Sender Service, Outbound Interface, Receiver Service(Integration Process).
d. Interface Determination( Inbound Interface(Sender Abstract Interface), Message Mapping(NOT Required if your using transformation stepin Integration Process)).
3. Now let us configure the Second BPM to Receiver.
a. Sender Agreement( NOT Required)
b. Receiver Agreement( Sender Service(Integration process), Receiver Abstarct Interface,Receiver service, Inbound Interface).
c. Receiver Determination( Sender Service(Integration Process), Receiver Abstarct Interface,Receiver Service).
d. Interface Determination( Inbound Interface, Message Mapping(NOT Required)).
So Finally we have One Receiver Agreement, Two Receiver Determinations, Two Interface Determinations.
Please let me know if you have any more queries.
Regards
Gopi

IDOC to flat file and vice versa

Dear community,
we should send IDOCs to flat files and read plain files and map them to IDOCs.
Is there any comfortable way to do this without doing a huge content conversion for
IDOCs? Exist a SAP standard for such process?
We receive the IDOC as normal IDOC. Would it be more easy to save the IDOCs
directly as flat file on ERP file system??
System PI 7.11
IDOCS: WHSCON, WHSORD and WMMBXY
Regards
Chris
Edited by: Christian Riekenberg on Feb 1, 2012 2:41 PM

Hey folks!
We have a PI 7.31 SPS5 Java-only installation here and are using the module IDOCFlatToXmlConvertor. For single IDocs with one line for the EDC_DC40 header and the others for the IDoc payload the conversion works. But when we want to process multiple IDocs from the same type within one file, we see this error in the log:
Module Exception 'com.sap.aii.af.idoc.exception.IDOCModuleException: No data segments for DOCNUM = ' found, cause: <null>
Are there any requirements how the multiple IDocs have to be structured within the file?
Best regards
Heinrich
Update:
I found out that the module wants each record to contain the corresponding DOCNUM to find the matching records. The non-SAP sender system normally does not set this value. Is there a way to "convince" the module to convert the IDocs nevertheless?

IDoc to Flat file scenario - abap mapping

Hi All,
I have to do some IDOC to Flat file scenarios. In Order to generate the file in required format I will have to add all segments(Nodes) of Idoc in FCC receiver. We also have other option of doing it through ABAP Mapping which I found in one blog.
Now my question is : Is it better way of doing it through FCC or ABAP Mapping?
Ofcourse from development point of view ABAP Mapping looks easier as FCC is very time consuming task.
Is there and performance issues in either of the approach?
Thanks and Regards,
Atul

Hi VJ and Harald,
Thanks for your replies.
I am not having PI7.1 however the given blog was very informative.
I will try using file port approach as suggested.
Thanks and Regards,
Atul

Idoc to flat file mapping using XSLT

Hi,
i am using XSLT mapping. my requirement is mapping between idoc and flat file(xml to text). as i do not want to use FCC, i have opted for xslt mapping. please let me know any article which would be helpful for this.
regards,
Meenakshi

Hi Meenakshi,
Two things:
1. Achieving this functionality using XSLT is very difficult.
2. Secondly you may not be able to find a direct document to convert IDoc-XML to flat file using XSLT in sdn. Try google.
I found one link like that may be you can get some idea from there
http://www.stylusstudio.com/SSDN/default.asp?action=9&read=6453&fid=48
Also if you have a XSLT editor like XMLSPY or stylus studio then creating your specific XSLT will b much more simpler
Regards
Suraj

IDOC to flat file without XML conversion

Hi,
I want to implement a scenario like this:
IDOC --> XI --> flat file
The flat file has to have the IDOC structure as you have when you write an IDOC to the R/3 file port. But we want to have this process running through XI.
When you use the IDOC Adapter the IDOC is converted to XML first, which is time consuming. So this I want to skip this step.
So is it possible to receive the IDOC directly in XI without converting it to XML? How should this process be designed.
Ron

Ron
Looks like you need IDOC tunneling. It is possible by making a configuration parameter.
You can find more information in http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
While you try it, I will try to simulate this requirement in our system and let you know the result.
KK

PO Idoc in Flat File format

Hi all,
I am able to generate the PO Idoc in Flat file format using standrad FM IDOC_OUTPUT_ORDERS. but the Flat file appearing is not in a appropriate format.
I'm looking to generate the Flat file in such a way that there will be only one line for each Idoc Segment.( with Line termination).
How to Achieve this.
Regards,
S Anand

Resolved.
we can use CG3Y transaction.
Regards,
S Anand

IDoc - SFTP (Flat File) file name

Similar Messages

Maybe you are looking for