Pls.. Help Needed.. Seeburger Mapping Names..!!

[Former Member]

Hi All,

Can any one help me with the default Mapping Program names supplied by SEEBURGER for both inbound and outbound.

<b>EDI Orders

EDI Order Ack/Confirmation outbound

Delivery

Invoice</b>

Also pls clarify below questions if you have an idea.

1. I heard that the XSD's will be already available for all the standard EDI message types.?? If Yes, we can i get them?? I mean which location in the server do i get them.

2. Is it mandatory that i need to use Only AS2 adapter to call the below Seeburger modules.?

Is the below sequence is correct??

<b>Process Sequence :</b>

localejbs/callBicXIRaBean bic

localejbs/ModuleProcessorExitBean exit

<b>Module Configuration :</b>

bic mappingName See_E2X_ORDERS_UN_D96A

exit JNDIName deployedAdapters/OFTP/sharable/OFTP

Thanks in Advance.

Regards

Seema

Message was edited by:

reddy seema

[Former Member · Accepted solution]

HI,

See_E2X_INVOIC_UN_D96A

See_E2X_INVOIC_UN_D99A

See_E2X_ORDERS_UN_D96A

See_E2X_OSTRPT_EAN_D96A.

Seeburger has a tool called BIC in that you will find all the mapping program which does the EDI to XML and XML to EDI conversion with all the std Seeburger structure.

No you can use the different seeburger adapters like X400,OFTPS adapters.

Yes the module configuration is perfect.

Thanks and Regards,

Chirag Gohil

[Former Member · Accepted solution]

Thanks a lot Chirag for your instant reply.

My client asking me to use the AS2 adapter.Can you pls tell me whether the below steps are correct ??

EDI File ---> Idoc Scenario :

<b>AS2 SND adapter -- > File Rcv adapter -> File Sender adapter-> Idoc Adapter</b>

Mapping Names i will be using in the Module sequence of AS2 snd adapter.So that conversion from EDI to XML will takes place from that mapping and the XI mapping also be finished and finally the the converted IDOC-XML will be reached to the directory.

Then i will pick that Idoc-xml and i will do a bypass scenario , so that the idoc adapter will create the Idoc in the R/3 system.

My questions :

1. Is it necessary to use File adapter to acheive this.

2.Can we acheive with only <b>SND AS2 adapter -

---

> RCV Idoc adapter.</b>

Kindly clarify me if you have an idea.

Please share with me if you have any document with step by step approach.

Thank you.

Regards

Seema.

[Former Member · Accepted solution]

HI,

You dont require a file adapter in this case.

Your scenario will be AS2 sender and IDOC receiver.

You need to use the party and identifier.

Do let me know if you need further information,

Thanks and Regards,

Chirag Gohil

[Former Member · Accepted solution]

Hi Chirag,

1) What is this AS2 identifier?? is it the reciver VAN number provided by basis team??

2) so i will be using below steps

<b>EDI File ---> Idoc Scenario :</b>

AS2 SND adapter --> Idoc Adapter

In the AS2 SND adapter in the Module tab we need to give the below parameters

localejbs/CallBicXIRaBean bic

CallSapAdapter 0

bic mappingName See_E2X_EDIFACT_ORDERS_UN_D93A

exit JNDIName deployedAdapters/OFTP/sharable/OFTP

please confirm for EDI->Idoc scenario,

<b>No need of using module " localejbs/ModuleProcessorExitBean exit " and

" exit JNDIName deployedAdapters/OFTP/sharable/OFTP " ???</b>

<b>For IDOC-->EDI Scenario: (X2E)</b>

-

---

In the AS2 RCV adapter in the Module tab we need to give the below parameters

localejbs/callBicXIRaBean bic

localejbs/ModuleProcessorExitBean exit

CallSapAdapter 0

bic mappingName See_X2E_EDIFACT_ORDERS_UN_D93A

exit JNDIName deployedAdapters/OFTP/sharable/OFTP

Can you please provide the sequence of Module names we need to give in AS2 adapter for both sender and receiver side( EDI>XML and XML>EDI).

Thank You.

Regards

Seema.

[Former Member · Accepted solution]

HI,

AS2 identifier is the party identified which will be provided by the WAN network provider.

Under the party identifiere tab

Agency will be seeburger

Scheme=AS2ID

Name = WAN network no of the partner who is sending the file

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

This is the sequence.

Thanks and Regards,

Chirag Gohil

[Former Member · Accepted solution]

Thanks a lot chirag,

So i hope <b>Idoc-->EDI</b> steps are correct??

When we are making use of Standard Message types by using AS2 adapter.

1. No need of touching BIC Mapping tool . Right??

2. Just i need to get the default mapping name what they have deployed?

3. Do i need to ask the basis team for the mapping name or i will be getting from any server??

4. Where can i get the XSD's for these kind of standard message types??

Please let me know if you have an idea.

Your helping my entire team of 20 members by clearing all these major doubts.

Thanks & Regards

Seema.

[Former Member · Accepted solution]

HI,

Yes if you are using the std mapping provided by seeburger then you do not need to use the BIC.

BIC is helps in identifying the structure of message it gives the information like occurrence,mandatory or not and most important the structure which gives you the parent child relation ship information.

Yes you need to deploy the mapping on XI and use that mapping program name in adapter.

You basis team is aware of the mapping program name as they are the one who deploy it on XI server. Generally all std seeburger mapping name starts with See_E2X or See_X2E naming convention.

Normally there is a steps which needs to be followed in BIC in order to convert the structure into the XSD structure so that you can use the structure in external definition of XI.

Can you please give me ur mail id i will forward you one doc which describes the steps of XSD conversion.

Thanks and Regards,

Chirag Gohil

[Former Member · Accepted solution]

Hi chirag,

Please send to <b>reddy.seema@gmail.com</b>.

Also please share if you have any document with step by step procedure for both EDI->XML and XML--> EDI. With module names mainly.

One more thing, When we are using std message types , you said no need of using BIC since already SDA files have been deployed in XI.

Then is it necessary to use the standard Module name

"<b> localejbs/callBicXIRaBean bic</b> ".

Thanks

Seema.

[Former Member · Accepted solution]

HI,

Yes you need to use the same.

Thanks and Regards,

Chirag Gohil

[Former Member · Accepted solution]

Hi Chirag,

Did you send the documents..??

Waiting for them

Thank You.

Regards

Seema.

[Former Member · Accepted solution]

HI,

Just to give more details which is required for AS2 configuration:

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

For sender AS2 adapter I have already given you the details.

Thanks and Regards,

Chirag Gohil

[venky_b]

Hi Seema,

I have gone through all of UR threads related to Seeburger. I am learning seeburger adapter please send all seeburger related documents U have to the below mail ID

venky.gbd@gmailcom.

Thanks in Advance.....

Venkatesh

[Former Member]

Thanks alot mate,

Your Suggestions are very helpfull, but unfortunately I couldnt reward points (is the only eay to honour her ein SDN) as i didnt open the thread.

will do from next time.

Cheers,

Smith

[Former Member]

Thanks alot Chirag & Nithyanand,

I will probably raise a new thread where i can continue, Before that please clarify the final bit.. may be silly for you guys(Gurus)

As per the client, we will receive EDI messages (message types like ORDHDR, DLCHDR, INVFIL etc) from customers through mail boxes, I'm not sure whether we can use BIC mapping tool or import them as XSD's yet?

If we are receiving EDI messages, i believe we can use BIC mapping tool to map them to ORDERS05 and post them in ERP. At this point, i hope we don’t need XSD import, Could you please clarify.

From next queries onwards I’ll be raising new thread.

Thanks guys,

Cheers

[Former Member]

Hi Smith,

U need to have XSD imported in external definition in IR and u need to use that XSD strucutre in message mapping.

So ur source will be XSD and ur target will be idoc strucutre which is imported in IR.

So u need a source and target strucutre in message mapping.

BIC tool is client based tool which is used for generating a mapping program for EDI-XML and XML-EDI and that mapping program has to be deployed on Xi and further used in Xi adapter.

Regarding ur requirement I hav already given u the solution of design and configuration.

Thnx

Chirag

[Former Member]

Hi Chirag,

Thanks for responding.

“The document with steps which needs to be followed in BIC in order to convert the structure into the XSD structure so that you can use the structure in external definition of XI.”

my email id is: sapaulsmith@gmail.com

My scenario is:

We are getting 10 different types of EDI files from 10 different customers to couple of mail boxes and we need to post them into ERP as sales orders. But, some customers 4 out of 10 are sending the data in the same message type format called “ORDHDR”.

We are planning to build 10 outbound interfaces and one inbound interface in XI to post these files as sales orders in ERP.

We are planning to use Seeburger, AS2 as sender adapter , Idoc as receiver and planning to install BIC tool as well.

Also we are planning to map all these EDI data to ORDERS05 (please correct me if I’m wrong), so that the data can be posted into ERP as sales orders.

Could you please clarify?

• Would one inbound interface serve my purpose?

• Do we need to create different AS2 sender adapters for different mail boxes?

Any step by step explanation would really help me a lot

Thanks in advance Chirag

Cheers,

Smith

[Former Member]

Hi,

I dont have the PDF curently but I will try to send it to you on monday.

Seeburger provide u all the standard message XSDs so if u r using the std messages then u do not need to generate the XSD using BIC.

When u import the seeburger SWCV in IR u will get all the XSD under the external definition tab.

Now coming to ur scenario:

1) IF ur four customers using the same message then in this case u can create only one common scenario in IR.

that is common mapping for all the 4 customers.

In the mapping IDOC control record has SNDPTR field u will use the fixed value mapping with input filed which identify ur customer and output as ur party name which u will be using in ID.

suppose if 001 is coming then output will be UK party and corresponding UK ID will be run.

similarly if 002 is coming then it corresponds to US then corresponding US scenario will run.

2) In the integration directory under the Business scenario u will be having

4 Party

1 Business sytem for SAP

4 Receiver determination

4 ID

4 Communication channel

1 IDOC communication channel.

Please raise separate thread with same discussion.

Thnx

Chirag

Edited by: Chirag Gohil on Feb 15, 2008 10:17 AM

[Former Member]

Hi Paul,

If you require a standard XSD file which needs to be imported into XI, the best way I would suggest you is to install the Seeburger in XI, so that you get all the standard structures of EDI as an external definition.

You can use those external definition in your interface.

Or if you are talking about the conversion of EDI-XML or XML to EDI using BIC mapper, let me know. I will try to help you.

Regards,

Nithiyanandam

[Former Member]

Hi,

Check some links on Seeburger.

http://www.seeburger.com

Please see the below blogs

/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-8f2...

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

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_Integratio...

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_Integratio...

Regards,

Phani

Reward Points if Helpful

[Former Member]

Hi

<<Sorry for the formatting. The following are the fields>>

message type, direction, mapping-name within XI EDI converter (to call the 1:1

format-mappings) from mapping_sys.sda, source interface version of XI content mapping, target version of XI content mapping, documenation of content mapping in content folder

<<The following sections show values for each fields above. >>

delivery forecast

=============

VDA 4905 IN See_E2X_VDA4905 VDA 4905 DELFOR02 VDA4905_IN_AUTOMOTIVE.xls

@830V4010 IN See_E2X_ANSIX12_830_004010 @830V4010 DELFOR02 A_830_V4010_IN_AUTOMOTIVE.xls

DELFOR D96 A IN See_E2X_DELFOR_UN_D96A DELFOR D96 A DELFOR02 E_DELFOR_D96A_IN_AUTOMOTIVE.xls

VDA4905 OUT See_X2E_VDA4905 DELFOR02 VDA4905 VDA4905_OUT_AUTOMOTIVE.xls

@830V4010 OUT See_X2E_ANSIX12_830_004010 DELFOR02 @830V4010 A_830_V4010_OUT_AUTOMOTIVE.xls

DELFOR D96A OUT See_X2E_DELFOR_UN_D96A DELFOR02 DELFOR D96A E_DELFOR_D96A_OUT_AUTOMOTIVE.xls

call-off

=====

@862V4010 IN See_E2X_ANSIX12_862_004010 @862V4010 DELFOR02 A_862_V4010_IN_AUTOMOTIVE.xls

despatch advice

===========

@856V4010 OUT See_X2E_ANSIX12_856_004010 DELVRY03 @856V4010 A_856_V4010_OUT_AUTOMOTIVE.xls

DESADV D96 A OUT See_ X2E DESADVUN_D96A DELVRY03 DESADV D96 A E_DESADV_D96A_OUT_AUTOMOTIVE.xls

@856V4010 IN See_E2X_ANSIX12_856_004010 @856V4010 DELVRY03 A_856_V4010_IN_AUTOMOTIVE.xls

VDA4913 IN See_X2E_VDA4913 VDA4913 DELVRY03 VDA4913_IN_AUTOMOTIVE.xls

DESADV D96 A IN See_E2X_DESADV_UN_D96A DESADV D96 A DELVRY03 E_DESADV_D96A_IN_AUTOMOTIVE.xls

invoice

=====

VDA4906 OUT See_X2E_VDA4906 INVOIC02 VDA4906 VDA4906_OUT_AUTOMOTIVE.xls

@810V4010 OUT See_X2E_ANSIX12_810_004010 INVOIC02 @810V4010 A_810_V4010_OUT_AUTOMOTIVE.xls

INVOICE D96 A OUT See_X2E_INVOIC_UN_D96A INVOIC02 INVOICE

D96 A

E_INVOICE_D96A_OUT_AUTOMOTIVE.xls

INVOICE D96 A IN See_E2X_INVOIC_UN_D96A INVOICE D96 A INVOIC02 E_INVOICE_D96A_IN_AUTOMOTIVE.xls

acknowledgement

============

CONTRL D93A OUT See_X2E_EDIFACT_CONTRL_UN_D93A Functional-Acknowledgement-SeeStd CONTRLD93A

CONTRL D96A OUT See_X2E_EDIFACT_CONTRL_UN_D96A Functional-Acknowledgement-SeeStd CONTRLD96A

CONTRL D97A OUT See_X2E_EDIFACT_CONTRL_UN_D97A Functional-Acknowledgement-SeeStd CONTRLD97A

@997V4010 OUT See_X2E_ANSIX12_997_004010 Functional-Acknowledgement-SeeStd @997V4010