IDOC to EDI scenario

Dear All,
need your help on how to configure and deploy a scenario for a IDOC to EDI (856) . I believe this is like "IDoc to X12 - > X12 to EDI" using AS2 adapter. BASIS has configured the B2B addon installation and I am not sure about the EDI part in this scenario..
can you please inform what that the steps (A to Z) needs to be followed and would be great if example scenarios can be uploaded .
Thanks
Fernando

Hi Fernando,
I guess you're referring to this thread: IDOC to EDI scenario
For that reason, please do close this one.
Thank you.
Dimitri

Similar Messages

Idoc to edi scenarios (mapping help is required)

hi expects ,
    i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
INPUT IDOC :
                    Name                         M/C     Min Use      Max Use        Description
INPUT*                                              M               1           1
Record EDI_DC40*                                 C               0           1                       Control Record
Record E2EDK01*                                  C               0           1                       Document Header General Data
     Record E2EDK14*                                  C               0          12                       Header Organizational Data
     Record E2EDK03*                                  C               0          10                       Header Date Segment
Record TEMP_DATE*                                C               0           1                       Temporary Date Segment
     Record DEL_DATE*                                 C               0           1                       Temporary Date Segment
     Record E2EDK04*                                  C               0          10                       Header Taxes
Record E2EDK05*                                  C               0          16                       Header Conditions
Record E2EDKA1*                                  C               0       99999                       Header Partner Info
Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info
Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info
Record TEMP_PAYER*                               C               0           1                       Payer Info
Record TEMP_CARRIER*                             C               0           1                       Carrier Info
Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info
     Record TEMP_NOTIFY*                              C               0           1                       Notify Info
Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info
Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info
Record TEMP_CONSIGNEE*                           C               0           1                       Consignee
Record TEMP_SHIPPER_INFO*                        C               0           1
Record E2EDK02*                                  C               0          10                       Header Reference Data
     Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02
Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING
Record E2EDK17*                                  C               0         999                       Header Terms of Delivery
     Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms
     Record E2EDK18*                                  C               0          99                       Header Terms of Payment
     Record TEMP_TERMS*                               C               0           1
Record E2EDK35*                                  C               0          10                       Additional Data
Group E2EDKT1:2*
OUTPUT FIELD:
Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION
     Segment B2A*                                     C               0           1                       SET PURPOSE
Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment CUR*                                     C               0           1                       CURRENCY
Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE
     Group DTM_GROUP*                                 C               0           1
Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE
Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE
Segment DTM:3*

Hi,
To do the mapping,,,,even you can go for graphical mapping....
But some of the context handling issues you need to deal with,
like....
1.Never map set context of source fields to element level but Segment level.
2. Always you need to check for qualifiers while mapping it to Traget field.
Thanks & Regards
Akshay.
Dont Forget TO Give Points.

Message mapping challenge in IDOC to EDI scenario

Dear PI message mapping experts,
I'm a newbie in PI and facing a mapping problem using graphical message mapping.
I'm in an IDOC (INVOIC.INVOICE02) to FILE (EDI) scenario.
Here after is the mapping i need to perform :
Source structure IDOC :
<E1EDKA1> (0..99)
   <NAME1> A </NAME1> (0..1)
   <NAME2> B </NAME2> (0..1)
   <NAME3> C </NAME3> (0..1)
   <NAME4> D </NAME4> (0..1)
</E1EDKA1>
Target structure :
<AccountingCustomerParty> (1..1)
   <Party> (0..1)
      <PartyName> (0..unbounded)
          <Name>A</Name> (1..1)
      </PartyName>
      <PartyName>
          <Name>B</Name>
      </PartyName>
      <PartyName>
          <Name>C</Name>
      </PartyName>
      <PartyName>
          <Name>D</Name>
      </PartyName>
   </Party>
</AccountingCustomerParty>
I know i have to play with context and queues with stanard function or UDF but cannot succeed to do it.
Could you please help me ?
Thanks in advance,
Alysee

One approach out of available few ways to implement this:
NAME1 - Exists - CreateIf - PartyName[0]
NAME2 - Exists - CreateIf - PartyName[1] (Create deuplicate segment)
NAME3 - Exists - CreateIf - PartyName[2] (Create deuplicate segment)
NAME4 - Exists - CreateIf - PartyName[3] (Create deuplicate segment)
Srikanth Srinivasan

IDOC to EDI Scenario using Seeburger....

Hi Experts,
On the Scenario IDOC to EDI when will I use As2 adapters or SFTP adapters of seeburger or just a simple FIle adapter?
and any idea what are the modules I need to import on my comm channel using file adapter?
Thanks.

Hello
Check this blog: /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
Regards
Mark

Problem with mapping [Idoc to EDI]

Hi experts,
i am facing a new problem in my mapping (idoc to edi scenario)
my target is as follow:
InvoiceDME
>Invoice 1..1
>>InvoiceHeader 1..1
>>>IncotermsCode 1..1
My Idoc is as follow:
IDOC
>E1EDK17 0..20
>>QUALF
>>LKOND
>>LKTEXT
There can be 2 scenarios in my source:
1st:
IDOC
>E1EDK17
>>QUALF = 001
>>LKOND = lkond001
>>LKTEXT
2nd:
IDOC
>E1EDK17
>>QUALF = 001
>>LKOND = lkond001
>>LKTEXT
>E1EDK17
>>QUALF = 002
>>LKOND = lkond002
>>LKTEXT = lktext002
If QUALF=002 then I have to take both values of LKOND and LKTEXT and map them to incotermcode
else if qualf=001 alone, then map LKOND to incotermcode
my mapping is as follow:
http://www.flickr.com/photos/30317046@N05/2862446903/
as you can see, the problem is if i am in my second scenario, i get the wrong value in incotercode (lkond001 instead of the concatenate of LKOND and LKTEXT for QUALF = 002)
Do you have any idea how I can solve this??
Thanks a lot,
Regards,
Jamal

Actually i used java mapping:
    //write your code here
try
     String returnString = "";
     for (int i = 0; i < QUALF.length; i++)
          if (("002".equals(QUALF<i>.trim())))
               returnString = returnString +" "+ LKOND<i> +" "+ LKTEXT<i>;
               result.addValue(returnString);
catch(Exception e)
     e.printStackTrace();
and the condition on the 'count' of QUALF (if = 2 then else)
Thanks,
Regards,
Jamal

IDOC to EDI Seeburger Mapping Issue

Hi,
I am new to seeburger, Currently I am working on PAYEXT IDOC to EDI scenario using seeburger adapter.
As per my little knowledge i can understand that i need two step mapping:
1) IDOC XML to EDI XML
2) EDI XML to EDI
Now the problem is how can i do 1st mapping if i have to do 1:1 mapping in PI mapper than it will be a tedious task as I dont know which idoc field is mapped to which EDI XML field.
Also i dont know how i can map the 2nd mapping.
when we installed seeburger adapter than i got three files from basis guys related to PAYEXT
msg_PAYEXT_UN_D96A.xml
msg_XML_PAYEXT_UN_D96A.xml
XML_PAYEXT_UN_D96A.xsd
Note: I imported .xsd file in IR, but i dont know what to do with these xml files.
Please experts reply soon as it is delaying my project
Regards,
Shradha

Shradha,
You can check the seeburger software component versions where all the mappings would be provided by Seeburger as part of the package.
You can have a look whether PAYEXT is there and would be useful
To start with
1. You need a functional or EDI Business analyst to guide you on the various mapping specifications needed.
2. You should also liase with your business partners to prepare an business rules and other conditions.
3.Also decide whether you are going to deliver it via AS2 communication or via VAN
4. Accordingly you need to configure the seeburger adapters.
5.The mappings provided to you are from XML to EDI and EDI to XML which is a second stage automatically done by seeburger once you specify the module steps in the comms channel.
I am afraid that without knowing business rules or mapping specifications, you can't work on EDI.
Regards
Krish

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

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

Tax with the help of idoc and EDI

Dear gurus,
how can we process tax data that is used between two systems through the help of IDOC and EdI? It would be great for ur kind support.

Hi Amit,
I do not understand how a non-sap system having an idoc adapte?
Do you mean the non-sap system has the ability to understand the IDOC files?
If yes, then your scenario is typically a IDOC-to File scenario.
Read this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
If you do not intend to use XI in between, then you can just configure the outbound IDOCs in your SAP system and configure a file port in we21 transaction and create the partner profile in we20 transaction.
Regards,
Ravi

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

Urgent: IDOC to EDI with SAP Conversion Agent

Hi,
I have a requiremetn like IDOC to EDI ( Gentran ) scenario.
We have decided to use SAP Conversion Agent to deal the same.
Can anybody share their experiences on this kind of scenario.
Needed step by step information to complete would be appreciated with the full of points.
Cheers.,
E

check with tis may helpful for you
http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/frameset.htm
Regds
Abhishek

IDOC to EDI file in PI 7.0. ( exchange infrastructure)

i have to do one application
SAP ECC 6.0 -> SAP XI -> Non SAP File Server
Non SAP file server accepts only .edi format files.
m trying IDOC to File scenario. IDOC generated is not giving exact EDI format which needs to send. How to transfer EDI format file from this scenario.
if its done by file content conversion, pls describe more.
eg . file output(.edi file) should be in below form
EDI_DC40 100000000000027837646C 3012 O
E2EDK01005 100000000000027837600000100000001 XSEK 5.23120

Hi,
There are two ways:
1. You can find out if an EDI provider (3rd party) which supports XML EDI Messages so you can just send XML EDI messages You can use Seeburger Adapter to conver into EDI Format.
In general , If sender side is File the that file must be generated by EDI mappers tool like BIC.
If file is in receiver side you have to use some Adapter to conver into EDI format.
-you can use FILE/FTP Adapter with Seeburger modules.
-you can use Seeburger OFTP Adapter.
See the following documents to help you ..
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/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
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
2. You can use EDI 834 Enrollment messages with XI you don't need an adapter - you can use adapter module:
a) you can develop the adapter module for file adapter yourself
for one message it will ont be that difficult
b) you can use SAP conversion agent to create the EDI adapter module
(it has many EDI messages included)
Thanks
Swarup

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

AS2 Adapter EDI scenario - question

I am working on a EDI scenario, involving AS2 adapter.
Could anyone tell me any steps to be done on ABAP engine.
reg

Hi Naveen,
follow the below steps:
1) First deploye the Std seeburger mapping provided by see burger on XI
2) If you are using the AS2 adapter then you have to install the AS2 server on XI server.
3) Once you install the std seeburger on SAP XI server you will see the AS2,X400,OFTPS,VAN adapter on XI ID.
5) You need to call the std mapping in the adapter module which does the conversion from EDI to XML and XML to EDI.
steps in IR and ID.
In IR:
You need to use the Standard XSD provided by Seeburger for different mesages like EDFACT ORDERS D96A etc in IR and other steps are similar which we do for the normal scenarios.
In ID:
This is the scenario for AS2
Seeburger has provided std mapping which need to be deployed on Xi server and will be used in XI adapter module tab for EDI-XML and XML-EDi conversion.
Example of mapping:
See_E2X_INVOIC_UN_D96A
See_E2X_INVOIC_UN_D99A
See_E2X_ORDERS_UN_D96A
See_E2X_OSTRPT_EAN_D96A.
1) After deploying mapping program.
We need to give the AS2ID in the party identifier tab,AS2ID that is entered here will be used for identifying the sender and receiver of the document.
1)The value of the Agency field must be Seeburger.
2)The value of the Schema field must be AS2ID.
Every partner is assigned the WAN no which is provided by the WAN service provider. That WAn no we need to configure in the party identifier tab
Configuration in adapter:
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Sender AS2 adapter configuration:
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A which does the conversion of EDI-XML.
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
You can refer my thread reply:
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Re: Seeburger AS2 adapter...
Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
AS2 adpater-- Configuration details for both SND and RCV.
AS2 Sender Adapter -- Need few details.
EDI-SEEberger-XI-IDOc-R/3
flow of the data from EDi to SAp r/3 using seeburger:
1) Data will be coming thorugh WAN or mailbox.
2) If its coming through WAN then every WAN provider will give the partner which is sending the data a partner number for indentification.
3) In your AS2 channel you need to configure the party and for that party you need to give the WAN number which is proivded for that partner. So it will run that configuration whenever that partner send the data.
4) In the adapter you have to give the mapping program name which does the conversion of EDI-XML and XML-EDI.
5) Once you XML is generated then it will be used in MM
6) At the receiver if its IDOC adapter then IDOC adapter will post the IDOC to R3 system.
Thnx
Chirag

IDOC to EDI

Hi all,
I am working on Idoc to EDI ANSI X12 Invoice 810 scenario, I created a receiver communication channel with File adapter and included those modules. But I am not sure is there any other additional module parameter that needs to be specified other than the once that are mentioned below.
Processing sequence:
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
and
Module configuration:
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName See_X2E_ANSIX12_810_V4010.
I am getting the following error in receiver communication channel,
"Message processing failed. Cause: java.lang.Exception: Cannot cast to XI message. Reason: BIC module error: Message which was recieved from module processor was null"
But the file in getting generated in the target directory as an xml file, actually the file has to be in EDI format.
Please let me know whether the module is not properly configured or the File adapter does not handle the IDOC to EDI conversion eventhough the module used does the conversion.
Regards,
Nithiyanandam

Hi,
Seeburger tool will not fail to conver the data into file format,they all are already predefined mappings and ANSI X12 is a common mapping used by most of the users and the module parameters which u have specified i dont find any thing more u have to give.
Check ur mapping which u have done and also check all the setting onces
any way iam giving some links on Seeburger check them.
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards,
phani
Reward points if Helpful

IDOC to EDI scenario

Similar Messages

Maybe you are looking for