Question on seeburger mappings

Question

Iam going to work on seeburger, at the moment we have installed seeburger on PI7.11
We have some vendors who woukd initiate the EDI transactions, we would be getting a request in EDI format for wchch we need to respond back.
I have a little ide that EDI message  needs to be converted EDI XML  and then it needs to be mapped with in PI to SAP understandable format.
Could somebody guide me what I need to in Seeburger BIC and how can I get them in Integration Repository,
What purpose we need to use AS2 and how can it be set up in PI

Answer 1

Hi Rajesh
Here is what documentation says, it did not tell  to use  CreateMappingEdiToXML to generate the mapping.
Creating New Mappings (Except XML Sources)
(Covers all types except XML as source type)
1. Click in the Project Explorer in a desired project on any mapping or on the Mappings node.
2. Then open the context menu with a right-mouse-click and choose New | Mapping, or click on the
second icon in the tool bar.
The Property panel for a mapping is opened and offers now the possibility to choose the Source and
Destination Message format for the new mapping. Choosing the involved messages has the effect that
also a suggestive and unique (in the current project) name for the new mapping is created, which can
be accepted, or modified by the user. Not commonly used characters should be avoided for mapping
names.
3. Confirm the settings, close the Property panel, and now the new created mapping can be opened
as explained in the previous section.
To edit or create mapping code, just select a record in the Source message. Expand the sub nodes
(sub records) eventually with a click on +. The written code in the Mapping Editor (record program) is
now automatically associated with a certain record.
When a conversion is performed, the converter will read the source file sequentially. For every found
record the corresponding record program will be executed. This happens automatically multiple times,
if the record is found more than once u2013 an explicitly loop programming is not necessary.
Editing the mapping code is quite convenient u2013 a Source field can be dragged and dropped on a
Destination field. The corresponding mapping code appears instantly in the Mapping Editor
I could not see the fields needed when I see the ANSI X12 structure, so I did not drag & drop on any field.
Do I still do any thing with CreateMappingEdiToXML to generate the mapping.