SEEBURGER REQUIREMENT

Hi All,
I have a scenario which involves transfer of EDi files
it is a B2B scenario where files need to be transferred from customer ERP to Customer VAN and from there it should be transffered to XI how can it we acheive this ?
Can we use Seeburger VAN adapter to transfer EDI files from customer ERP to Customer VAN?
From there picking in to XI SEEBURGER AS2 can be used or Seeburger VAN adapter which will be more advantageous?
Any more ideas Plz?
Regards,
VKG

hi
before implementation check what is the file format in which message is send to customer, what are the message type involved, what is the WAN id of customer etc then go for the implementation.
which one to use: refer the below link.
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
refer the below link for start.
SAP XI supports EDIFACT
inorder to start:-
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.
refer the below links for configuration and flow details.
configuration details
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
flow details
EDI-SEEberger-XI-IDOc-R/3
chirag

Similar Messages

  • Seeburger AS2 - message does not arrive when "Athentication required" is ON

    Hi guys!
    If somebody of you is using the Seeburger Adapter:
    I have an inbound scenario and everything works fine. But when I set "Authentication Required" flag to be ON, messages are refused. This is strange, because incoming messages are signed.
    Any ideas, what could be wrong? There are several settings for certificates and maybe I have some wrong setting.. Does anybody have experience with this?
    Thank you, Peter

    Sai, you probably don't have experience with Seeburger AS2, do you? It works in a special way - that's why I'm asking people, who have experience with this..
    But for clarification: My inbound Seeburger AS2 channel receives message scorrectly, but when I enable uthentication on it, AS2 messages are refused - so they are not in the AE, they are not in the IE.
    Peter
    p.s. I will not reward your answer, sorry
    Message was edited by:
            Peter Jarunek

  • Seeburger mapping name required for ASN

    Hi
    I am trying to use the Seeburger AS2 adapter to send ASN (Advance shipping notification) to our partners.
    The format of the EDI file is EANCOM2002. I want the standard Seeburger mapping name which will convert from xml to EDI EANCOM2002 format for ASN message.
    Thanks in advance.
    Shantha

    If you are expecting the naming conventions for SEEBURGER Mapping (BIC Mapping designer) here are few .Let me know if they are useful.
    <b>ADOPTED NAMING CONVENTIONS</b>
    1 - For Application Rules:
    DOCUMENT_APLLICATION_DIRECTION_DATA (FILE EXTENSION FOR REFERENCE)
    Length for each:
      Document = 3     Samples of:  PUR, POC, POA, ASN, TXT            
      Application = 4   Samples of:  RECL, SOMS, HRMS, CORP, COMS, CONT  
      Direction = 1       Samples of:  I or  O
      Data = 3              Samples of: DAT, XML, RPT
      NOTE:  Since spaces are not allowed in the names,  ‘S’  will be used as filler .
    Sample Application Naming:
    For 824 for Banking doc   – TXT_CORP_I_RPT
    – <b>General  Rules:</b>
    1- IF mapping is the same with HRMS & COMS
          THEN Use CONT for Application
        ELSE  Use HRMS or COMS (which ever is appropriate)
    2- IF document is the same for the entire corporation
           THEN Use CORP as the Application
    3- IF Generic
          THEN  No Suffix is required
         ELSE Trading Partner Specific maps add the suffix
    For Trading Partner specific rules, add the Name extension to the end of the rule.

  • Seeburger help required for 850, 810, Dispatch Advice (DESADV IDOC)

    Hi All,
    Pls let me know for below 4 points:
    1. Please let me know blogs which clearly shows settings for Seeburger components for 850 or 810.
    --- Seeburger Workbench
    --- Seeburger Mapping Designer (BIC)
    --- Seeburger Counter and Varaibles
    --- Seeburger AS2 Spoke
    --- Any other Seeburger Component setting required
    I have understand blog for 850 -- /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
    3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
    4.  I have heard that Seeburger now provides standard mappings for PI/XI  for 850, 810 , DESADV etc. so we do not require to do mappings in PI/XI now as it is already done. Any one knows about it.
    Regards

    > Pls let me know for below 4 points:
    >
    > 1. Please let me know blogs which clearly shows settings for Seeburger components for 850 or 810.
    > --- Seeburger Workbench
    > --- Seeburger Mapping Designer (BIC)
    > --- Seeburger Counter and Varaibles
    > --- Seeburger AS2 Spoke
    > --- Any other Seeburger Component setting required
    Hello Rickk,
                          There is no blog for the 810 scenario ...
    you need to configure the partner related stuff in seeburger workbench if it is inbound only like 850,852,860..
    not for outbound like 810,856...i.e no need to configure the partner data in seeburger workbench for this..
    You need to look for developing mappings if EDI message is other than Version 4010 by default there are mappings available for
    810,856,850,997..if your edi messages are other than this then you need to look for BIC tool for developing mappings.
    There is no need to set anything for counter and varaibles
    ..no idea about AS2 spoke,,,
    Apart from thjis no need to do anythings in seeburger ...
    HTH
    Rajesh

  • Seeburger help required for 810 and Dispatch Advice (IDOC type DESADV).

    Hi All,
    1. Please let me know blogs which clearly shows settings for Seeburger components for 850 (Purchase Order) to IDOC Scenario
    --- Seeburger Workbench
    --- Seeburger Mapping Designer (BIC)
    --- Seeburger Counter and Varaibles
    --- Seeburger AS2 Spoke
    --- Any other Seeburger Component setting required
    I have understand blog for 850 -- /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
    3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
    Regards

    Hi Rickkk,
    1. Please let me know blogs which clearly shows settings for Seeburger components for 850 (Purchase Order) to IDOC Scenario
    --- Seeburger Workbench
    --- Seeburger Mapping Designer (BIC)
    --- Seeburger Counter and Varaibles
    --- Seeburger AS2 Spoke
    --- Any other Seeburger Component setting required
    For SEEBURGER workbench please go through this blog and navigate the enbebbed links furthur to know about Seeburger workbench too.
    /people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
    2
    2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
    For 810 i think the procedure would be the same but themseeburger mapping program that validates the ANSX 810 would be different.As far as 997is concerned 997 is a functional acknowledgement.Its a genric format that is used to send acknowledgement for any EDI transaction set that has been sent.
    3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
      The logic will be based on the trading partner guidelines which will contain the description of all the semantic and syntactiic description about the segments ,its feilds.we need to consider the guidelines and target side specifications too while mapping.
    Thanks,
    Ram.

  • Many .sda files required,EDI,Seeburger?

    hi,
    do we need to create .sda files using Seeburger BIC Mapper for each mapping and deploy each <b>.sda</b> file on to XI server using SDM?

    Hi Babu,
    Let me tell you the step by step process of SDA creation and deployment.
    1) Go to BIC Mapping designer tool
    2) Create the maps of needed documents(For example if we know that we will be needed EDI 850, 810,855 etc transactions then we need to add E2X(EDI To XML) and X2E (XML to EDI  maps in a project
    3) Select that project folder
    4)Right click on it
    5)Create deployment (SDA) file.
    6)Default name of the created SDA file is "Mapping_User.sda"
    7)Deploy this .sda in to the J2EE side of XI server using SDM.
    Now if you anticipate that you have to add some aditional EDI maps for transtions other then the one covered in the earlier SDA file ::
    1) Add the new maps in the old project.
    2) Create the new SDA file
    3) Again name of the created SDA file is "Mapping_User.sda"
    4) deploy this new SDA file.
    5) It will over write the existing "Mapping_User.sda" .
    Hope i have answered your question
    Let me know if you need any further clarifications.
    regards
    Piyush

  • Seeburger BIC Mapping-Small info required

    Hi folks,
            I am currently working on Seeburger BIC Mapping designer, Are there any forums for Seeburger BIC Mapping related Issues, can we discuss the Seeburger BIC Mapping related issues in this forum.
            Please let me know.
    Regards,
    Varun

    hi
    check the link related to bic mapping
    1./people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
    2.Building own schemas in Seeburger bic mapper
    3.BIC mapping names / classes
    4.Seeburger - BIC configured as Module
    BR
    Kasturika

  • Seeburger help required for Supplier Invoice (EDI 810) and Dispatch Advice

    Hi All,
    Pls let me blog/steps for scenario for Supplier Invoice and Dispatch Advice using Seeburger.
    For Supplier Invoice I assume R/3 will send data to Vendor (810).
    1. Pls let me know for R/3 to XI will we use INVOCE IDOC?
    2. Pls let me know for R/3 to XI Communication do we will use same Distributiion Model setup?
    3. Pls let me know what Seeburger BIC modules I need to use in Seeburger AS2/File Receiver Adapter
    4. Which Interface and Adapter  I need to use for 810 and which Interface and Adapter  I need to use for 997.
        Pls send its setup with its Mappings defined in Modules.
    5. What is Disptach Advice?  Is it also same like Supplier Invoice ? Does it also have EDI Number and if yes then what?
    Pls send me blogs for the above Supplier Invoice and Dispatch Advice settings.
    Regards

    >
    Rickkk wrote:
    > Hi Ravi and All
    >
    > I am thankful to all of you for great help of yours.
    >
    > Steps:
    >
    > 1) I wil create an INvoice in your backend system. It will generate an IDOC.
    > 2) This IDOC will be sent to my XI system.
    > 3) I will map the IDOC to the Target XML 810 --- From where I will get this Target XML 810 ?
    YOu have to login to the Physical box in which XI is installed (Take Basis Help.
    In one of the drives, you will find a folder called seeburger.
    Inside that folder, you can browse to find the XSD structure for your 810 .
    YOu will find different XSDs for different versions of 810.
    Suppose your EDI 810 version is 4010, then you have to use the XSD for 810 4010 version (There will be separate folders for each transaction set/version combination.
    It will be there also in the software CD that seeburger provides when you buy it.
    > 4) I need a seeburger receiver AS2 adapter that consist of modules that will convert the XML 810 docuemnt to EDI document.
    >
    > Below are the modules will be present in you suggested seeburger receiver AS2 adapter
    > module key                  Parameter name               Parameter value
    > bic                                destSourceMsg               MainDocument
    > bic                                destTargetMsg                MainDocument
    > bic                                mappingName                  <the name of your X2E mapping for 810>
    > exit                               JNDIName                         deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
    >
    Yes.
    > 5. As per blog  -
    /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    >
    > For 997 Interface we are using seeburger Sender adapter and for 850 Interface we are using Split997 Sender adapter -- Reverse order
    >
    > For this scenario will it be like this again like
    > For 997 Interface we will use Seeburger Receiver AS2 Adapter where the above modules are configured -- Pls suggest
    >
    > For 810  Interface we will use Split997 Receiver adapter -- No modules configured Pls suggest
    >
    > I request you to kindly send me snapshots or blogs which has snapsot for this scenario.
    >
    No need of split 997 in outbound case. In this case, you will send the 810 and the partner will send the 997.
    So, to receive that 997 file, you need another scenario. You need the split 997 communication channel only in inbound case like in 850, but not in outbound case.
    > Last point -- is Dispatch advice direction is like 850 (Inbound ) or its direction is like 810 (outbound)?
    > Do we have IDOC or something like that present and its mapping ?
    >
    like I said earlier, it is an outbound document if your company is the vendor.
    It will be inbound if your company is the Customer to some other company.
    The IDOC that is used usually will be DESADV idoc.
    > Regards

  • Any setting required in SLD for EDI,XI,Seeburger Implementation.

    hi,
    what we need to do in SLD to implement EDI using seeburger adapter,do we need to install SWCV and create TS and BS like we do in general?
    or we create ,in Integration Directory,party and then Business service (or Business System) and CC?
    thank yoiu,

    Hi Babu,
    Please see the below link,
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e17fdb90-0201-0010-2cb6-fe937f3bfd97
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f70cc090-0201-0010-06bd-ff8d3754cfe4
    Thanks,
    Ram
    Pls reward points if you find useful

  • Seeburger help required.

    Hi All,
    In AS2 Sender Channel for Module Key BIC  we provide  Parameter name as  destDelimiter 
    and provide value for example  ~*.# \n
    I am not able to understand  destDelimiter concept.
    Can anybody explain me with example and also provide blog for the same
    Regards

    Hi,
    See the below links:
    field delimiters coming as text
    Seeburger Adapter
    Regards,
    Shweta.

  • Seeburger help required for Purchase Order,Dispatch Advice,Supplier Invoice

    Dear All,
    I wanted to do the Seeburger implementation.
    I wanted to convert the EDIFACT to XML struture and XML struture to EDIFACT  using the seeburger adpater for --
    Purchase Order , Dispatch Advice and Supplier Invoice.
    Points:
    1. How will vendor will send and receive data to PI. (means how to use Seeburger spoke and how to give unique Ids in Seeburger AS2 adapter)
    2. How to do Edifact to XML conversion and XML to Edifact conversion using Mapping Designer
    3. How to configure modules in Seeburger AS2 adapter
    Regards

    HI,
    For Seeburger implementation you should take licance for BIC MD and Adapters(AS2,SFTP).
    1)You will receive the data from the vendor ,you need to configure the AS2 Sender Adapter and you need configure the Party with AS2ID(Global Indentfier).
    2)For Conversion for the EDIFACT to XML you need to generate the the BIC mapping In BIC MD.once generate the map you can loaded the map into XI server.you need to configure the mapping detials in module(Classifer,BIC,Spliter......).
    Steps to genrate the BIC MAP:
    Steps :-
          1) Right click on Data type and Export structure (msg_....xml).
          2) Run u201CCreateXMLmessageu201D, (source file msg_....xml, target file XML_....xml).
          3) Import XMLu2026.xml to your Project XML Message.
          4) Run u201CCreateMappingXMLToEdiu201D source file (msg_...xml),target file      (X2E_....xml)
          if you are converting XML to Edi format.
          5) Run u201CCreateMappingEdiToXMLu201D source file (msg_....xml),target file      (E2X_....xml) if you are converting Edi to XML format.
          6) Import X2E/E2X_.....xml to your project mappings
    3) you need to open firwall from the vendor and your system..
    AS2 Sender Adapter:
    Transpoert protocl:HTTP
    Message Protocol:AS2
    Authincation Requered(Check box)
    Message subject:
    Asynchorns MDM Settings:
    Server Certifacte:
    Private key:
    HTTP TimeOut:
    MDM retry interval:
    MDM retry Count:
    Proxy Server:
    Proxy prot:
    Proxy User and Password.
    For more information end to end :above menation rajesh weblog.
    regards,
    Ramesh

  • Dynamic filename creation with Seeburger's SFTP adapter

    Hi Experts,
    I read in one of the forum that Seeburger's SFTP adapter supports dynamic configuration.
    My requirement is i need to dynamically create a file name and put it into a predefined folder(of a third party system) with SFTP adapter.
    Can any one help me with some blogs/Materials on this?
    Thanks,
    Niranjan

    HI,
    Have you look into the blogs mentioned in below forum
    How do we do File content conversion using SFTP SEEBURGER Adapter
    Thanks
    Swarup

  • How to file mask in sender seeburger SFTP adapter

    Hello Gurus,
    Please help on
    How to perform a file mask in sender seeburger SFTP adapter? eg. I want to pick all the files but not *.tmp files.
    thanks
    Kishore

    Kishore
    A work around:
    Use another interface File to file (By pass) using file adapter which does the mask exclusion of the file which are not required.
    Regards
    Raj

  • Seeburger FTP Adapter And SAP PI 7.1

    Hi Everyone,
    Just a few questions about Seeburger FTP adapter please. Bit of background for clarity, we are doing an implementation using Seeburger FTP and sap PI 7.1 picking up EDIFACT (Orders) and returning (DESADV, ORDERSP, INVOICES). However we are not using any BIC, using another tool for EDIFACT -> EDIFACT-XML conversion (conversion agent) and in-house mapping development using graphical mapping.
    So couple of things which I haven't been able to figure out from the standard documentation for Seeburger FTP adapter:
    1) First is the functional ACK which we are meant to send back to the VAN is that a STANDARD FUNCTIONALITY with Seeburger FTP adapter?
    2) Because we are receiving a mix bag EDIFACT interchange on the way IN, I need to split messages accordingly and pass them on to the relevant channels and mappings. By using the standard module Splitter can I achieve that?
    3) Lastly some of the standard validations which are applicable to EDIFACT are they supported within the FTP adapter automatically? e.g. Counting number of messages in one interchange etc.
    Any help in this regard will be really great.
    regards

    Now a Good news.
    If you are using Seeburger version 2.1 (which you should be as you want it for PI 7.1), then there is an Internal Classifier and Split option for FTP adapter. You just need to tick checkbox "Use built-in splitting" and you are done. Then I believe there won't be any need for considering all these problems. The earlier version of Seeburger with PI 7.0 doesn't have such option and that could be the reason you haven't received any appropriate response yet.
    Still I will reply all your questions considering that "your case is of PI 7.0". -> remember PI 7.0
    >>even with just splitter we should be able to break it up?????? or am I wrong in thinking this?
    No. You even need BIC or an equivalent custom module for achieving this.
    >>I can't visualize where to handle the overall message count in one Interchange any suggestions?
    You need to write an adapter module for this. Not sure about the code but this module has to be added before the split happens.
    >> seeburger ftp adapter it does talk about a lot of reports which are available on sender/reciever actions. e.g. delivered, despatched etc. Are these reports not essentially ACKs?
    These reports are the ones used at the receiver side for getting the ACKs from the receiver. Your requirement is at present for sender scenario.
    Regards,
    Prateek

  • Seeburger AS2 Adapter - Dynamic Attributes

    Dear all,
    We have a scenario where, we are sending an IDOC from our SAP system via XI to one of our partner using AS2.
    We have to manipulate the file name at the receiver end using the dynamic attributes of the AS2 communication channel.
    As per the documentation and the following threads
    Re: File to AS2 File Name? we have done the necessary configuration in the communication channel. The following activites are done
    Selected the checkbox "Use dynamic attributes"
    Under the Module tab
    In Processing sequence added a new entry
    Number 1
    Module Name : localejbs/Seeburger/solution/as2
    Module Type  : Local enterprise bean
    Module Key   :  "dynfile"
    Under the Module Configuration added the following details
    Module key  :  "dynfile"
    Parameter Name : "http://seeburger.com/xi/AS2/dtAS2FileName"
    Parameter Value : "DYNFILENAME"
    However, I understand that this configuration is incomplete, as somewhere i need to pass the value to the variable "DYNFILENAME".
    As per the thred Re: File to AS2 File Name?, Mr Srinivas Reddy mentioned 5 steps, however I am not clear about the step 3 & 4.
    FYI : What I want to map as the file name is the Parter Profile in the EDIDC40 segment of the idoc and the date+time stamp
    Many thanks for the help , in advance
    Regards : Bobby Bal
    Edited by: Bobby Bal on Sep 20, 2010 9:52 PM

    Hi,
    Use the below UDF in your mapping..
    public String FileName(String a,Container container){
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters()
    .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http://seeburger.com/xi/AS2","dtSubject");
    conf.put(key, a);
    As per your requirement, Use Concatenate function  Idoc + Date + Time .
    Pass the resultant value to the UDF and pass this to any unused Target node.
    IDOC + Time+Date --> UDF --> Target node.
    In your receiver AS2 adapter, Click on use dynamic attributes and  Subject check boxes.
    If you want to use other Dynamic attributes like dtAS2FileName, dtAS2ContentType ..
    Simply replace the dtSubject with dtAS2FileName or  dtAS2ContentType . No need to use any modules.
    Thanks
    Deepthi.

Maybe you are looking for