EDI to file scenario

Hi,
Can any one explain me EDI to file scenario.
For file how do we configure in SLD. Plzz explain me.
Thanks,
Singh.

Hello Varun,
I have a request to set up EDI communication for EBS MT940 format between the Bank and SAP. This customer already uses MT940 bank statements but they download them straight from homebanking...now they want to set up EDI so that they don´t need to and this gets imported automatically.
I know the ale configuration I need to do....what I don´t know, and the customer has requested me this, is what I need to ask to the bank. Can you give me some details?
For example, is the bank only storing the txt file format (MT940) in a bank server and transfering it periodically (according to the customer requests) to the SAP server? And this will then be converted into and IDOC (how by the way?)?
Or is the translation made elsewhere? Do I need something in particular to translate the txt file to and IDOC? Is this mapping complex? (we are reconciling subledger only bank accounts so this should make it less complex)
Would be grateful if you would give me some ideas on how to kick off this.
Thanks a lot,
AC

Similar Messages

EDI to FILE scenario Problem.

H,
I am working on EDI to FIle scenario. in PI 7.1
I am getting output as XML Format .
Present output.
<BEG01>00<BEG01>
<BEG02>02<BEG02>
<BEG03>01<BEG03>
But I need output as
000102.(No segment data)
How woulds i change this xml format into normal format.
Thanks,
Singh.

Hi ,
If you need normal format please use the file content conversion. Please find the below links which are helpful for you for knowing file content conversion both in sender and receiver side.
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem(keyfield problem)
/people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
http://wiki.sdn.sap.com/wiki/display/XI/XI_File_Content
http://wiki.sdn.sap.com/wiki/display/XI/BasicFileAdapterContentConversion
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion(file content conversion at receiver side)
/people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
/people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure
http://wiki.sdn.sap.com/wiki/display/XI/BasicFileAdapterContentConversion(basic file adapter conversion)
http://wiki.sdn.sap.com/wiki/display/XI/XI_File_Content
http://wiki.sdn.sap.com/wiki/display/XI/TroubleshootingtheFile+Adapter
/people/sukumar.natarajan/blog/2007/06/12/content-conversion-in-sender-file-adapter--2-new-useful-parameters
help.sap.com
http://help.sap.com/saphelp_nw70/helpdata/en/0b/9a50465ccf84479e39a6d50c90fb3f/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/0b/9a50465ccf84479e39a6d50c90fb3f/frameset.htm
Regards,
Rama

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

BIC Module Error in Sender Communication channel for EDI to File scenario.

Hi Experts,
We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
Thanks & Regards,
Abhishek

Hi Abhishek,
Is there any special character present in the EDI file?
the parser is not able to parse the data.
you can check the BIC conversion log for more information.
Regards,
Harish

How to convert 864 Transaction code into XML in EDI to File Scenario

Hello Friends,
 Can any body help me out in using 864 Transaction Code (Tex Message) in EDI to Flat File Conversion?? I mean i am using just 2 Fields i.e Name and Address.I didnt understand the Format given..Here is the format for Name
N1 Name Pos: 040 Max: 1
 Heading - Optional
 Loop: N1 Elements: 4
To identify a party by type of organization, name, and code
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N101 98 Entity Identifier Code M ID 2/3 Must use
Description: Code identifying an organizational entity, a physical
location, property or an individual
All valid standard codes are used.
N102 93 Name C AN 1/60 Used
Description: Free-form name
N103 66 Identification Code Qualifier C ID 1/2 Used
Description: Code designating the system/method of code structure used
for Identification Code (67)
All valid standard codes are used.
N104 67 Identification Code C AN 2/80 Used
Description: Code identifying a party or other code
Syntax:
1. N102 R0203 -- At least one of N102 or N103 is required.
2. N103 P0304 -- If either N103 or N104 are present, then the others are required.
Comments:
1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104)
must provide a key to the table maintained by the transaction processing party.
2. N105 and N106 further define the type of entity in N101.
[b]
Here is the format for Address
N3 Address Information Pos: 060 Max: 2
 Heading - Optional
 Loop: N1 Elements: 2
To specify the location of the named party
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N301 166 Address Information M AN 1/55 Must use
Description: Address information
N302 166 Address Information
Description: Address information O AN 1/55 Used
So Help me hoe to convert this into XML...

try this
For EDI U need SEEBURGER Adapter or Conversion agent by itemfield.
Using Conversion agent convert EDI Into XSD and Import using External definition.
Have look
EDI Conversion
Re: Seeburger Splitter adapter!!
Thanks

IDOC to EDI file scenario and EDI file to IDOC scenario without Seeburger

Hi All,
IDOC (Invoice) to EDI file scenario without Seeburger
Pls let me know if anybody have blogs for the same
EDI file to IDOC (Orders) scenario without Seeburger
Pls let me know if anybody have blogs for the same
Regards

Hi Rachit,
>>Can anybody send me blogs to convert IDoc structure to EDI or EDI to IDoc structure using Conversion Agent or using JAVA Mappings.
Using conversion Agent there is no coding, If you have a conversion agent insatlled in your landscape you will have better understanding..
Also java code for IDoc to EDI have some problems:
1. The EDI format differs based on requirement so there will always be a customized code for it.. Like we have IDco to EDIFACT and ANSX12...
2. Because most of these codes are propriety materials I doubt whether anyone be sharing the complete code here in SDN. Better to have a java consultant at your end and put him with your requirement.. From the reply in above threads you should be clear that what you are looking for can be done from java coding..
All the best
Regards
Suraj

IDoc output type not getting configured in IDoc-File scenario

Hello
I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
1] Created output type
2] Created partner function as EDI LS for this output type
3] Configured RSNASTED as Processing Routines for output type
4] Included this output type in the Header output procedure
5] Configured XI system as the partner in partner profile with appropriate Message control
Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
I checked in SPRO but could not find such flag.
Does anyone had came across such output type configuration.
Thanks in advance.
I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
Regards
Rajeev

Hi,
Please check the following
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
Copy NEU to ZNEU or YNEU
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
G.Ganesh Kumar

Seeburger IDOC-to-File scenario: Error using Classifier module

Hello,
I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
localejbs/SeeClassifier classifier
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
classifier attID classifierAtt
classifier destSourceMsg MainDocument
classifier showInAuditLog true
bic classifierAttID classifierAtt
bic destEncoding UTF8
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName AUTO
bic newLine true
bic srcEncoding UTF8
After conversion in XI, the file fails to write to the folder because of this error:
Message processing failed. Cause: javax.resource.ResourceException: ---
Conversion of synchronous request from module chain ended with errors
---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
BICMapping Error: The mapping [not specified] you are trying to load cannot
be found in the right path! Maybe you forgot to compile or to activate the
mapping!
When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine. But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
I am only facing this problem for the IDOC-to-File scenario. Somehow the same configuration works for a File-to-IDOC scenario.
I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be. Has anyone encountered this problem before?
Any suggestions would be appreciated.
Thanks,
Arianne

Hi Yomesh,
Here is the payload.
<?xml version="1.0" encoding="UTF-8"?>
<LIST>
<S_ISA>
 <D_I01>00</D_I01>
 <D_I02/>
 <D_I03>00</D_I03>
 <D_I04/>
 <D_I05>ZZ</D_I05>
 <D_I06>CELORGS01</D_I06>
 <D_I05_2>ZZ</D_I05_2>
 <D_I07>AVX</D_I07>
 <D_I08>032008</D_I08>
 <D_I09>1718</D_I09>
 <D_I10>X</D_I10>
 <D_I11>00401</D_I11>
 <D_I12>000000008</D_I12>
 <D_I13>0</D_I13>
 <D_I14>T</D_I14>
 <D_I15>^</D_I15>
 <S_GS>
 <D_479>PO</D_479>
 <D_142>CLS01</D_142>
 <D_124>058895921</D_124>
 <D_373>20080320</D_373>
 <D_337>1718</D_337>
 <D_28>8</D_28>
 <D_455>X</D_455>
 <D_480>004010</D_480>
 <S_ST>
 <D_143>850</D_143>
 <D_329>800001</D_329>
 <S_BEG>
 <D_353>00</D_353>
 <D_92>SA</D_92>
 <D_324>4500005037</D_324>
 <D_373>20051110</D_373>
 </S_BEG>
 <S_CUR>
 <D_98>BY</D_98>
 <D_100>USD</D_100>
 </S_CUR>
 <S_FOB>
 <D_146>CC</D_146>
 <D_309>OR</D_309>
 <D_352>FREE CARRIER</D_352>
 <D_334>02</D_334>
 <D_335>FOB</D_335>
 <D_309_2>DE</D_309_2>
 </S_FOB>
 <S_ITD>
 <D_336>01</D_336>
 <D_333>3</D_333>
 <D_351>45</D_351>
 </S_ITD>
 <G_SN9>
 <S_N9>
 <D_128>L1</D_128>
 <D_369>GEN</D_369>
 <S_MSG>
 <D_933>TEST</D_933>
 </S_MSG>
 <S_MSG>
 <D_933>MESSAGE</D_933>
 </S_MSG>
 </S_N9>
 </G_SN9>
 <G_SN1>
 <S_N1>
 <D_98>BY</D_98>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 <S_PER>
 <D_366>BD</D_366>
 <D_93>Graham Crawford</D_93>
 </S_PER>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>BT</D_98>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>SE</D_98>
 <D_93>3M COMPANY</D_93>
 <D_66>92</D_66>
 <D_67>0000019591</D_67>
 </S_N1>
 </G_SN1>
 <G_SN1>
 <S_N1>
 <D_98>ST</D_98>
 <D_93>SAMPLE</D_93>
 <D_66>92</D_66>
 <D_67>6310</D_67>
 </S_N1>
 </G_SN1>
 <G_SPO1>
 <S_PO1>
 <D_350>00010</D_350>
 <D_330>10.000</D_330>
 <D_355>EA</D_355>
 <D_212>10</D_212>
 <D_639>PE</D_639>
 <D_235>BP</D_235>
 <D_234>230-1812-01JDS</D_234>
 <D_235_2>EC</D_235_2>
 <D_234_2>A00000000000002</D_234_2>
 <G_SPID>
 <S_PID>
 <D_349>F</D_349>
 <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
 </S_PID>
 </G_SPID>
 <S_REF>
 <D_128>CO</D_128>
 <D_127>4500005037-00010</D_127>
 </S_REF>
 <G_SSCH>
 <S_SCH>
 <D_380>10.000</D_380>
 <D_355>EA</D_355>
 <D_374>002</D_374>
 <D_373>20051208</D_373>
 </S_SCH>
 </G_SSCH>
 </S_PO1>
 </G_SPO1>
 <G_SCTT>
 <S_CTT>
 <D_354>1</D_354>
 </S_CTT>
 </G_SCTT>
 <S_SE>
 <D_96/>
 <D_329>800001</D_329>
 </S_SE>
 </S_ST>
 <S_GE>
 <D_97>1</D_97>
 <D_28>8</D_28>
 </S_GE>
 </S_GS>
 <S_IEA>
 <D_I16>1</D_I16>
 <D_I12>000000008</D_I12>
 </S_IEA>
</S_ISA>
</LIST>
Thanks,
Arianne

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

Idoc to File scenario using Party

Hi All,
I have to configure Idoc to File scenario .This file needs to be posted in EDI Subsystem .My receiver partner type is LI.That means i need to use Party here.So please let me know the step by step solution to do this.Specially i want to know the configuration in Party Identifier and Receiver Communication channel Identifiers.
How the control record values from idoc are transferred to EDI File structure and how will XI identify one of the many customers to post the file.
All valuable suggestions will be rewarded the points.
Please send me the documents for such scenario with screen shots.

Hi,
Let me see if I had you requirement correct.
When the Idoc is sent from R3, sender partner type is LS and Receiver Partner Type is LI.
If yes,
1. Create a Party in ID.
2. The Agency , Scheme and Identifier will have values,
Agency --> Receiver Business System name or Business Service Name to be used for File.
Scheme --> ALE#LI
Identiier --> Value of the RCVPRN field in the idoc control Record. Basically the Receiver Partner Name.
All the Configuration In ID will use this Party as the Receiver Party and the corresponding Service asthe Receiver service.
No need for a sender party as sender partner is LS.
Regards
Bhavesh

Inbound Function Module SM58 Error in Outbound R3- XI- file Scenario

I am getting an SM58 error message of "Use IDOC Adapter for FM IDOC_INBOUND_ASYNCHRONOUS...." in my R3 system when trying to implement an Outbound R3->XI->file Scenario. This implies that the system thinks I am doing inbound when I am really doing an outbound IDoc to XI. I followed the guides and seem to have everything set up properly.
I also found a closed posting concerning the same error message, but there was no resolution.
My idoc also appears fine (outbound, right ports). To test, I changed my XI rfcDestination to an EDI System rfcDestination and the ORDRSP outbound idoc goes to the edi system as expected.
Any idea why my R3 system thinks I am using IDOC_INBOUND_ASYNCHRONOUS?
Thanks in advance!

Hi,
I have couple questions before exactly answering your question
What type of data you are trying to send like
1. Master data (Customer master, Vendor master)
2. Transactional data (Sales orders, Purchase orders)
If you are trying to send transactional data then check the partner profile configuration for whom you are trying to create outbound IDocs. Select your partners outbound message type and go to Message Control details tab and check your Process code and corresponding functional module if the function module used is ment for creating outbound Idocs then there should be some other that is causing the problem otherwise I guess this is the problem so you can change the associated process code function module.
Jagadish.

Idoc-xi-file scenario. how to display file in html format

I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
In idoc-xi-file scenario....... how to display file in html format ??
Thanks in advance
Kumar

Hi Vijayakumar,
Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
Regards
Kumar

IDOC-XI-FILE Scenario: Error in ABAP Mapping

Dear All,
I am working on IDOC-XI-Flat FIle scenario in which I am using ABAP Mapping as per document "How To Convert an IDoc-XML
structure to a flat file and vice versa in XI 3.0".
I created one customized Idoc for this. The Idoc is reacing XI but its flat file is not getting created. Its giving me following error:
<SAP:Stack>Error in mapping program Z_ABAP_MAPPING_PACKING_LIST (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I have also gone thru threads posted for the same topic earlier but still I am not been to resolve this error.
Please help me out in resolving this error.
Regards,
N.Jain

HI,
 Log saying that, u have problem in the mapping program.
i.e Z_ABAP_MAPPING_PACKING_LIST
 the problem is due declaration of data.
 i hope that, you have some methods.
 those are declared under intialization section in mapping program.
please use start of selection before the method.
other wise, it will come under intilization section.
warm regards
mahesh.

How to use a existing Business Service in IDoc-File Scenario

Hi Experts,
I am new to XI.
I am working on a IDoc to File scenario where in i am importing the CREMAS.CREMAS03 IDoc from the R/3 System.
When i try to create a Business Service in Configuration Scenario Object in Integartion Directory, i get a message saying "SAP system ID ER1 and client 800 already exist in service | CLNT800ER1".
Can i reuse this Business Servie in my Configuration Object?
If yes, can you please guide me How to go about it?
Thanks for the effort.
Cheers
Gaurav Raghav

U may directly use it.
Just select the business service wherever required. It is not necessary that the Business Service is present in ur configuration scenario. But if u still want it, u may add it using "Add to Scenario" option from other configuration scenario or from Objects tab
Regards,
Prateek

Issue in IDOC-File Scenario

Hallo Everybody,
In one of the requirements,for the interface design which involves IDOC-FILE scenario we have a req as:-
Multiple IDOCs would be sent from SAP R/3 to SAP XI. Each IDOC can have 0-4 segments and for each segment a file needs to created.
The files needs to be FTPed to a location, only if all the IDOCs have been processed successfully.
Requirement:
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
2) We need to send a notification from XI, in case any IDOC processing fails.
3) How do we check in XI, if all the IDOCs have been processed successfully.
Please suggest me with some good stategies to resolve this issue.
Appreciations and Rewards in line.
Regards,
Younus

Hi
Are you planning to use BPM as it suits your requirement.
To collect the idocs in small bunches refer
Collecting IDocs without using BPM
1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
BPM will allow you to wait for the time all IDOC are processed
2) We need to send a notification from XI, in case any IDOC processing fails.
BPM exception handling will allow this functionality even to the exact field you want to send notification
3) How do we check in XI, if all the IDOCs have been processed successfully.
Set Acknowledgment for IDOC's
refer
Posting multiple IDocs with Acknowledgement
Thanks
Gaurav

EDI to file scenario

Similar Messages

Maybe you are looking for