Flat File to EDI

Hi Guys,
I have a flat file coming into XI and i need to send it in EDI format.
can anybody help me how to covert the incoming flat file to EDI format and send to a buisness partner ?
Thanks,
Raj

Hi
Which structure you are refering to i mean ODERS EDIFACT or any other.
See for converting the EDI XML to EDI or flat file to EDI you need to have a mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
May be this will help you.
Here is the link for your reference:
/people/ricardoandres.maienza/blog/2007/04/06/edifact-to-xml--stylus-studio-solution
http://www.stylusstudio.com/edi/EDIFACT_translate.html
The steps to convert EDI to XML / XSD can be found at the following link:
http://www.stylusstudio.com/edifact_to_xml.html
Stylus studio download link: http://www.stylusstudio.com/xml_download.html
Or
Using the Conversion agent
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch
/people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
Thanks and Regards,
Chirag Gohil

Similar Messages

Facing Problem in IDOC to EDI FLAT File Scenario

Hi,
I am working on a scenario IDOC to EDI FLAT File. For this I have used ABAP mapping.
The problem i am facing is that the EDI FILE contains the segment name as E1EDK01 for eg. while I need the name as per the latest segment definiton released. I have also tried this using File port and it gives the required segment names in file. But we dont have to use File ports. Please suggest me if something is missing in PI Abap stack ?? Why I am not getting the segments name as per latest segment definition mainatined in R3.
Thanks
Neha

Hi Neha,
Please check the segment name in sxmb_moni. Is this showing new value or the old value?
If SXMB_MONI shows old value then the source SAP (R/3) system which is sending the idoc may not have released the segment after changing the name. You need to ensure that the idoc segment has been released properly. Then re-import the iodc into PI server again. Finally delete entry of the iodc structure in idx2 transaction, no need to re-import the idoc structute again in idx2, since once you run the scenario the metadata automatically gets imported.
regards
Anupam

New EDI Implementation - Flat File format for SPSI in eCommerce Gateway

Hi,
we are trying to setup EDI with a business partner, goal is to import a DELFOR message into Oracle Order Management. Plans are: translate the inbound message into the SPSI flat file format, load it through eCommerce Gateway / Release Management into Order Management.
For this purpose I'd like to test to the import of a SPSI flat file into eCommerce Gateway / Release Management, however I have difficulties to get a proper flat file. Is there a way to generate example flat files somehow? I tried to generate my own flat file, based on the Oracle manuals, but how can I be sure that the format is correct (besides of running the import program)? Any advice on this?
Or is there a better way, e.g. through XML files?
Thanks in advance,
David.

Hi, thanks for the response.
Yes I use that report already to get the details of the flat file. But what I am missing is for example which records are repeated, e.g. for every 4000 record, do I need one 0010 record, or can I put multiple 4000 records within one 0010 record?
regards,
David.

EDI Flat file Content Conversion

Hi Experts,
I have got a question on File Content Conversion, Please have look the following structure, is it possible with FCC or what is the best possible solution for this, which is very big favour to me.
Some information about this structure,
This is EDI message in flat file structure, each segment has got 700 characters as a row, LIN item is repeating many times,
ST ,XQ , N1 , DTM, LIN, P04, N9,ZA , ZA ,ZA , etc are segments, LIN item is repeating, at the end CTT is last segment. Again from ST segment to CTT segment comes 3 more times.
ST 0000001     4444444
XQ H            20100531
N1 xxxxxxxx                            u 00000
N4 aaaaaaaa, kk                  xx87654
DTM600                                                        20100531
LIN           CB224790                        HH002720033676                  PP00027200336760                ZZ0
P0400001000000000         000000000 000000000 000000000000000000000000
N9 VN0000000594
ZA QA238.00000000000CT         LJXX
ZA QN1.0000000000000CT         LJXX
ZA QO000000000000000CT         LJXX
ZA QP210.00000000000CT         LJXX
ZA QS61.000000000000CT         LJXX
ZA QW208.00000000000CT         LJXX
LIN           CB320275                        SS004330033052                  PP00043300330521                ZZ0
P0400001000000000         000000000 000000000 000000000000000000000000
N9 VN0000000594
ZA QA36.000000000000CT         LJXX
ZA QN1.0000000000000CT         LJXX
ZA QO000000000000000CT         LJXX
ZA QP120.00000000000CT         LJXX
ZA QS8.0000000000000CT         LJXX
ZA QW36.000000000000CT         LJXX
CTT00005300000000000000000000 00000000
ST 0000001     4444444
XQ H            20100531
N1 xxxxxxxx                            u 00000
N4 aaaaaaaa, kk                  xx87654
DTM600                                                        20100531
LIN           CB224790                        HH002720033676                  PP00027200336760                ZZ0
P0400001000000000         000000000 000000000 000000000000000000000000
N9 VN0000000594
ZA QA238.00000000000CT         LJXX
ZA QN1.0000000000000CT         LJXX
ZA QO000000000000000CT         LJXX
ZA QP210.00000000000CT         LJXX
ZA QS61.000000000000CT         LJXX
ZA QW208.00000000000CT         LJXX
LIN           CB320275                        SS004330033052                  PP00043300330521                ZZ0
P0400001000000000         000000000 000000000 000000000000000000000000
N9 VN0000000594
ZA QA36.000000000000CT         LJXX
ZA QN1.0000000000000CT         LJXX
ZA QO000000000000000CT         LJXX
ZA QP120.00000000000CT         LJXX
ZA QS8.0000000000000CT         LJXX
ZA QW36.000000000000CT         LJXX
CTT00005300000000000000000000 00000000
Please I am really requesting you get appropriate answer and quick response please
Thanks in Advance
Regards
Sandya

Hi Suresh, Raj,
Thanks for quick reply, but we haven't got Seeburger Adapter in our landscape. Please one small clarification please this message looks to me, we can do with FCC, but i need some experties from you guys.
1. ST segment comes in one line with 700 characters - has got 5 fields 1..1 cardinolity
2. XO segment comes in another line with same length 700 ch, but 8 fields different lengths 1..1 cardinality
10 LIN segment comes in another line 700 characters, but 0..n
Can't we take structure as follows:
Header     --    0..n
    SegID ---    1..1
    field 2 -
    1..1
    field 3 -
    1..1
    field 4 -
    1..1
    field 5 ---      1..1
    Row2   -
   1..1
       SegID -
   1..1
       field2 -
   1..1
    Row6    -
    1..n (for LIN segment)
       SegID ---   1..1
       field 2 --- 1...1
Please can you give me your experties please??
Regards
Sandya

Help needed on Transforming input File to EDI Format

I have an input flat file in one location. Using BizTalk, i need to pick that file from that Recieve location, transform it to EDI format and send it to Destination location.
Now, when I place input file in the "Recieve location", it is being processed and it is erased from recieve location. But I am not able to see the output in the Destination location.
And when i query it in BizTalk Administration console, the state is "Completed" without any errors.
Any guidance/suggestions are appreciated. Thanks in advance.

Hi all, I have just collated everything and have put it in my words below..Please
let me know your valuable inputs as I am struck in this point from more than a week.
I need to fetch an input flat file (.txt format) from the "Receive location" and I am supposed to transform that to an EDI message X12 format and send it to Destination folder.
I have set up the receive port and send port configurations in the Admin Console, have created the Trading Partners, agreement and other settings.
The problem I am facing : Now, when I place input file in the "Receive location", it is being processed and I am able to pick up the file from the input folder
but I am not able to figure out why the file is not being processed and sent to the destination folder.. (If I query for All In Progress instances, suspended instances or Running instances : I am not getting any results and the below grid is always empty).
And when i query it in Biz-talk Administration console for Tracked instances, the Receive pipeline component's state is "Completed" without any errors.
And I am not using any Orchestration in between..
Thank you all in advance....

IDoc - XI - IDoc Flat File

Hi Everyone:
We have a situation where we need to process an outbound IDoc through XI and create a flat IDoc file on a file server.
Everything works fine, but when file is created; it's in XML format. I have done the configuration in SXMB_ADM, so that it won't convert the IDoc to XML, but it still does i.e. segments and fields tags are added before and after the values. For example,
<Z1JBRS SEGMENT="1">
<CTEUSR>SOMEUSER</CTEUSR>
<CTEDTE>20000906</CTEDTE>
<CHEUSR>No User</CHEUSR>
<CHEDTE>00000000</CHEDTE>
<CHETME>000000</CHETME>
</Z1JBRS>
All I want is to create the same flat file that will get created if I use the "rfcexec"/"startrfc" criteria from SAP, which transfers the file to EDI Sub-System. Has anyone come across this situation? Any information / direction / suggestion will be appreciated.
Thanks,
JB

Hi,
If it Idoc is passing thru XI, then it will convert into xml as XI can understand xml format.,
So if you want to get flat file, you need to convert xml into flat structure,. For this you need to use option of "File Content Conversion" in File Reciever Communication channel. If so, you need to configure content conversion for this.
Refer this guide-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Regards,
Moorthy

I can't build an xsd for a flat file (txt) to handle repeating records

Hi - have looked at many posts around flat file schema and they don't seem to address my question.
I have a flat file that is \n delimited
the pattern of the data is simple:
record1 - 90 characters
record2 - 20 characters
record3 - n 248 characters - each of these records is parsed into children by the positional method
record n+1 10 characters
record n+2 20 characters
so I used the flat file schema generator to generate the schema and built a map mapping the flat file schema to another xml schema. The schema looks ok - record1, record2, record n+1, record n+2 are child elements of the root. the repeating record
section is showing up as a node with the parsed children.
The transform is only mapping the children of the repeating records. When I test the map only the first repeating record gets parsed. No repeating happens (the actual flat file has 400+ repeating records). When I run the map in debug mode, the input
xml shows that record1 is read in correctly, record2 is read in correctly, record3 is read in and parsed and record4 is treated like record n+1 and record5 is treated like record n+2 and the map thinks it's all finished.
the section of the repeat part of the schema is and you can see that I set the minOccurs=1 and maxOccurs=unbounded for the node (INVOICE) and the complexType but this is not an affective syntax. I have looked at how the EDI X12 schema look and how they handle
looping and it is a lot different than what the Flat File schema wizard is doing. Is there a good set of rules published that would guide me though this? otherwise I will basically have to read in the lines from the file and parse them out with functoids -
seems so inelegant. Thanks in advance.
<xs:element minOccurs="1" maxOccurs="unbounded" name="INVOICE">
          <xs:annotation>
            <xs:appinfo>
              <b:recordInfo structure="positional" sequence_number="3" preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false"
/>
            </xs:appinfo>
          </xs:annotation>
          <xs:complexType>
            <xs:sequence minOccurs="1" maxOccurs="unbounded">
              <xs:annotation>
                <xs:appinfo>
                  <groupInfo sequence_number="0" xmlns="http://schemas.microsoft.com/BizTalk/2003"
/>
                </xs:appinfo>
              </xs:annotation>
              <xs:element name="SegmentType" type="xs:string">
                <xs:annotation>
                  <xs:appinfo>
                    <b:fieldInfo justification="left" pos_offset="0" pos_length="2" sequence_number="1" />
                  </xs:appinfo>
                </xs:annotation>
              </xs:element>....... more children elements
Harold Rosenkrans

Thanks for responding
I gave up trying to parse the repeating record into fields. Instead I just loop through the repeating record section with an <xs:for-each> block in the xsl and use functoids to grab the fields.
So that works for having the two, shorter header records (structure is positional) before the section of repeating records. Now I just have to figure out how to get the schema to handle the two, shorter trailer (or footer, whatever you prefer) records after
the section of repeating records
the error I get in VS when I test the map is [BTW I changed the element names in the schema which is why you don't see INVOICE in the error]
When I declare the last element as being positional with a character length of 10 I get the error:
Error 18 Native Parsing Error: Unexpected end of stream while looking for:
'\r\n'
The current definition being parsed is SAPARData. The stream offset where the error occured is 1359. The line number where the error occured is 9. The column where the error occured is 0.
so the first record is 77 char in length and the second is 16 char and then the repeating records (5 in the file) are 248 char and the last record is 10 char
so an offset of 1359 puts it beyond the last record by 16 characters - so the stream reader is looking for the next repeating record.
if I try to declare the last element as delimited I get the error:
Error 14 Native Parsing Error: Unexpected data found while looking for:
'\r\n'
The current definition being parsed is SAPARData. The stream offset where the error occured is 597. The line number where the error occured is 5. The column where the error occured is 0.
so the first record is 77 char in length and the second is 16 char and then the repeating records are 248 char.
a stream offset of 597 puts me 8 characters into the third repeating record - at this point I have only declared one trailer record in the schema, 10 characters long.
Why is stream reader stopping at such a weird spot?
The bottom line is I still haven't discovered the correct schema to handle the trailer records. even if I set the maxOccurs="4" (for the repeat record declaration) it still gets the first error. How does it find an unexpected end of stream looking
for \r\n when the maxOccurs for the repeat record declaration should have the stream pointer in the 5th repeat record.
I unfortunately don't have any options concerning the file structure.
I have read a lot of posts concerning the trailer issue. I have seen a couple that looked interesting. I guess I'll just have to give them a try. The other option is to create a custom pipeline that will only take file lines of 248 characters.
That's just disgusting !
Harold Rosenkrans

Parse multiple files in one flat file?

Hi all,
I'm currently working with flat file with this kind of structure:
"849000","1","2","3","4"             <- begin of file
"849HD","","1939","12"              <- header level
"849D1","39193","313","1"         <- detail level
"849D2","","description","48,13" <- detail description level
"849RT","133,1","N4","203"        <- totals level
The problem is that the file i have to pick up (the map is File => EDI)
can contain many structures (every estructure is an edi to generate)
example:
"849000","1","2","3","4"             <- first file
"849HD","","1939","12"
"849D1","39193","313","1"
"849D2","","description","48,13"
"849RT","133,1","N4","203"         <- end of first file
"849000","2","","","6"              <- second file
"849HD","","92","23"
"849D1","99","912","1"
"849D2","","second description","3,11"
"849RT","61","2","UP","102"         <- end of second file
- How can i parse this file in order to get a nested structure?
MT_file
MT_file/row (0.unbounded) <- that would contain 2 files
MT_file/row/849000
MT_file/row/849HD
MT_file/row/849D1
MT_file/row/849D2
MT_file/row/849RT
Because i believe content conversion (KeyFieldValue) is not effective since it will take the key as generate the segments all together without respecting the order
Any ideas?
Thanks!

I'm not so sure about that, i mean i think that the KeyField won't we able to understand the hiercachy
example:
"849000","1","2","3","4" <- first file
"849HD","","1939","12"
"849D1","39193","313","1"
"849D2","","description","48,13"
"849RT","133,1","N4","203" <- end of first file
"849000","2","","","6" <- second file
"849HD","","92","23"
"849D1","99","912","1"
"849D2","","second description","3,11"
"849RT","61","2","UP","102" <- end of second file
with keys:
849000
849HD
849D1
849D2
849RT
i will probably get all in a group, and in doing that i'll loose the reference for the first and second file
resulting:
"849000","1","2","3","4" <- first file
"849000","2","","","6" <- second file
"849HD","","1939","12"
"849HD","","92","23"
"849D1","39193","313","1"
"849D1","99","912","1"
"849D2","","description","48,13"
"849D2","","second description","3,11"
"849RT","133,1","N4","203" <- end of first file
"849RT","61","2","UP","102" <- end of second file
Or am i missing something?
This is file => EDI, so the channel would be SENDER

Proxy to File scenario - IDOC as an flat file

Hi,
I am working on ABAP Sender Proxy to File scenario. The target structure in the message mapping is SHPMNT05 IDOC and the output of the file needs to be in the text format and then the file will be send to an EDI subsystem.
Currently, EDI subsystem gets the IDOC from ERP system as a flat file and expects the similar kind of file from XI system
The requirement is to have all the fields of the IDOC in the target file. If data does not exist for a particular field, then there should be a space for that field in the text file.
I would like to know if there is any other standard way of executing this scenario apart from using File Content conversion. In case if we have to use FCC, how difficult it would to be implementing the scenario. Please note that the output file needs all the fields of IDOC in it.
Regards,
Sakthi
Edited by: Sakthi on Sep 26, 2008 11:24 AM

Hello Sakthi,
By coding in proxy populate the idoc structure if it is difficult to handle thru Content conversion parameters then create an intermediate structure and populate that structure by concatenating the fields from idoc segments. If the fields are not having the values then add blank spaces as per length of the field.
You can configure the file channel and content converison parameters for the intermediate structure.
Hope it will helps to you.
Cheers
Veera

Flat file message is not recognized.

I have been pulling my hair out for days now. I have an ANSI x12 214 v4010 document that validates against the xsd file in visual studio when I remove the Interchange headers
I add the interchange headers back and deploy for it to pick up the file and I get the error:
The flat file message is not recognized. Unrecognized messages are not allowed as per the specified configuration.
This is the extent of the error information that Biztalk will respond with. I have to assume the issue is with the interchange headers since I know the transaction portion of the document itself validates. Below is a copy of my headers.
ISA*00* *00* *ZZ*SEND *ZZ*RECV *040805*0416*U*00401*000000001*0*T*^~GS*QM*SEND*RECV*20040805*0416*000000001*X*004010~[214 Transaction]~GE*1*000000001~IEA*1*000000001~
I am beginning to believe the problem may be due to the trading partner agreement. I originally didn't have an agreement at all and was just publishing my service. I have now added two partners for the send and the receive. I also created
an agreement with the Hosted Partner qualifier matching the sender info in the header and the Guest Partner being the receiver info. I set the version and type to match, added the sender application qualifier (GS02) which matches the sender info (ISA06)
and set the schema to the one I validate locally X12_00401_214.
Despite having the agreement in place that matches the headers I still receiving a flat file message not recognized error with no additional error information.
Please rescue me from the insanity...

Hi,
We need a few more details about his scenario.
have you uploaded this particular schema to the service?
What kind of bridge are you using – EDI / AS2 / XML
What tool are you using to push the message to BizTalk service? If you are using EDI / As2 bridge, are you adding proper HTTP headers while sending message from the client?
You may go through the blog
Test the Bridges - Post messages – 3 easy tools for the developers
http://blogs.msdn.com/b/mabs/archive/2014/10/14/test-the-bridges-post-messages-3-easy-tools-for-the-developers.aspx
Check the section
Considerations for the EDI / AS2 Bridges
Hope this helps you
Girish Prajwal

Creating a flat file in the IDOC format

Hi everybody,
Need help.....urgently. Can somebody please tell me how to create a flat file in the IDOC format? I am creating a bill of lading/Documentary payments (EDI 858) and can't figure out a way to write the data generate through the report in a flat file in IDOC format. My deadline is right around the corner and I need help.
Thanks,
M

Hi Minal,
I still don't understand your question.
So, you have a report which selects data and puts it into an internal table. This part looks fine.
You want to create a flat file? Ok, to create a flat file on the application server then use the commands OPEN DATASET, TRANSFER, and CLOSE DATASET. To create a flat file on the presentation server then use the FM GUI_DOWNLOAD (or the GUI class, I forgets its name for the moment).
In both cases you should build up an internal table which has the exact structure required for your (EDIFACT?) EDI message, and then use the appropriate method to write the file.
If the following steps are manual then there is nothing more for you to do.
I don't see any need to use Idoc technology, or make any reference to it in your solution.
I hope that helps. If not, please be more specific when asking your questions.
Brad

Convert flat file to Idoc format

Due to some security reasons , the ALE scenario for material master is not allowed directly between 2 SAP systems
So the SAP system A is sending a flat file (not in Idoc format)
From SAP system B , we need to do an Inbound process to post the Idocs with following rough steps
1) Flat file upload
2) Flat file -> Idoc format conversion (EDI subsystem is not existing in this scenario and so this step has to be done within SAP)
3) Idoc processing
Even though this scenario can be accomplished without using Idocs ,
for better monitoring and reprocessing options it is required that Idocs need to be used.
Please explain the detailed steps for the above scenario

Hi,
This sounds very much lie complicating things unnecessary...Are this 2 SAP systems of the same company ?
Why would using IDOCS be more insecure then using flat files ?
If the purpose is to have a manual check before upload, you can achieve the same with IDOCS.
Please add some background to the process,
regards
Dirk

Which is the better format for message handling - flat files or SOAP?

We have the possibility to specify from our EDI partner how to send messages into XI. We can ask them to send the messages in as SOAP or flat files.
Is there a definite preference for one format over the other? Can somebody advise with reasons?
BR,
Tony.

>>We have the possibility to specify from our EDI partner how to send messages into XI. We can ask them to send the messages in as SOAP or flat files.
I would strongly suggest you go with SOAP rather than File.
Reason : In case of file, the EDI partner will send a file to a machine in your network where FTP server is running and you make your XI server poll the particular folder every 10 min or so. But in case of SOAP, the <b>communication is real time</b>. Your EDI partner can invoke either the SOAP adapter directly or send a SOAP msg directly to Integration Server.
Just my ideas.
Regards,
Jai Shankar

Import flat file to multiple tables based on identifier column

Hello,
I am trying to setup a package that will import one pipe-delimited flat file (a utility bill) to multiple data tables based on the value of the first column. I have been told it is similar in format to an EDI file, but there are some differences.
The number of columns is consistent where the first columns are the same. Meaning a record that has '00' in the first column will always have 10 columns; a record that has '01' in the first column will always have 9 columns; etc.
Each value in the first column represents a separate destination data table. Meaning a record that has '00' in the first column should be output to table '00'; a record that has '01' in the first column should be output to table '01'; etc. All
destination tables reside on the same SQL Server.
Identifier columns can repeat multiple times throughout the flat file. Meaning a record that starts with '01' may be repeated multiple times in the same.
Sample Data:
00|XXXXXXXX|XXX|XXXXXXXX|XXXXXX|XXXX|X|XXXXXXXXXX|XX|XXXXX
01|XXXXXXXXXXX|XXX|XXXXXXXX|XXXXX|XXXXXXXXXXXXXXXXXXXX|XXXXXXXXXX|XXXXXXX|XXXXXXXXXXXXXX
02|XXXXXXXXXXX|XXXXXXXX|XXXXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX
04|XXXXXXXXXXX|XXXXXXXXXXXXX|XXX|XXXXXXXX
05|XXXXXXXXXXX|XXXXXXXXXXXXX|XXX|XXXXXXXX|XXXX
07|XXXXXXXXXXXXX|X|XXXXXXXXXXXXXXX|XXX|XXXXXXXX|XXXX|XXXXXXX|XXXXXXXXXXX
07|XXXXXXXXXXXXX|X|XXXXXXXXXXXXXXX|XXX|XXXXXXXX|XXXX|XXXXXXX|XXXXXXXXXXX
07|XXXXXXXXXXXXX|X|XXXXXXXXXXXXXXX|XXX|XXXXXXXX|XXXX|XXXXXXX|XXXXXXXXXXX
07|XXXXXXXXXXXXX|X|XXXXXXXXXXXXXXX|XXX|XXXXXXXX|XXXX|XXXXXXX|XXXXXXXXXXX
01|XXXXXXXXXXX|XXX|XXXXXXXX|XXXXX|XXXXXXXXXXXXXXXXXXXX|XXXXXXXXXX|XXXXXXX|XXXXXXXXXXXXXX
02|XXXXXXXXXXX|XXXXXXXX|XXXXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX|XXXXX
04|XXXXXXXXXXX|XXXXXXXXXXXXX|XXX|XXXXXXXX
Any help would be appreciated.

Hi koldar.308,
If there are few distinct values in the first column, we can use Flat File Source connect to that flat file, then use Conditional Split Transformation to split the first column to multiples, and then load the data to multiple tables with OLE DB Destination
based on the outputs of Conditional Split.
After testing the issue in my environment, please refer to the following steps to achieve this requirement:
Drag a Flat File Source connect to that flat file with Flat File Connection Manager.
Drag a Conditional Split Transformation connects to the Flat File Source.
Double-click the Conditional Split Transformation, add several Output based on the first column values as below:
Drag same number OLE DB Destinations as the outputs of Conditional Split, connect to Conditional Split with one case output:
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Inbound idocs with flat file

Hi
Iam creating INBOUND IDOCS from flat file ...so my sending and recieving systems are same...
In WE20 i have setup the logical system and assigned inbound parameters with message type and proces code.
Iam using IDOC_INBOUND_ASYNCHRONOUS to create the inbound IDOCS but iam getting the error
EDI: Partner profile inbound not available
It looks like iam missing some settings here..
Please let me know what checks i need to make sure to get rid of this error and post the idoc.
Thanks
Govi

Hello,
You need to create partner profile in WE20 transaction code.
For more details follow the link: [creating PARTNER PROFILE|http://help.sap.com/saphelp_nw04/helpdata/en/2d/f371e4d24a11d289810000e8216438/frameset.htm].
Hope this resolves your issue!
Thanks,
Augustin.

Flat File to EDI

Similar Messages

Maybe you are looking for