Seeburger 997 Issue

Hello All,
I am having an issue with the Seeburger adapter especailly with 997 or Functional Acknowledgments.
Whenever I receive a X12 997 message, the adapter is sending out a 997 for it. Is there a way, I can tell the Seeburger splitter adapter to disable this?
Thank you in advance for your help.
Sumant.

Sura,
Aamir is talking about the segment ST and D_143 field. So basically you need to check this field to see whether the transactin is 997 or others. If it is 997 then ignore as aamir told else do the original functionality you are doing.
Just for your reference see this field in the file:
ST9977493~
Regards,
---Satish

Similar Messages

  • Localejbs/Seeburger/AttribMapper issue

    Hi all,
    we are using "localejbs/Seeburger/AttribMapper" module in SFTP adapter to add the Date stamp to file name.
    Module Name                                                 Type                                  Module Key
    localejbs/Seeburger/AttribMapper                            Local Enterprise Bean                 1
    localejbs/ModuleProcessorExitBean                         Local Enterprise Bean                   2
    Module Key        parameter Name                                                         Parameter Value                 
    1                         GetDateTime                                                 "mmddyy"
    1                         http://seeburger.com/xi/SFTP/dtSubject                     TEST
    2                         JNDIName                                                      deployedAdapters/SeeXISFTP/shareable/SeeXISFTP
    But, it is not attaching the date stamp to file. its only generating TEST as file name.
    Any ideas......

    Hi, This issue has been solved.
    There was slight mistake with declaration . we needed to use 1 paramters  instead of 2.
    Module Name                                                 Type                                  Module Key
    localejbs/Seeburger/AttribMapper                            Local Enterprise Bean                 1
    localejbs/ModuleProcessorExitBean                         Local Enterprise Bean                   2
    Module Key        parameter Name                                                         Parameter Value                 
    1                         http://seeburger.com/xi/SFTP/dtSubject                     'TEST'&GetDateTime("MMddyy")&'.csv'
    2                         JNDIName                                                      deployedAdapters/SeeXISFTP/shareable/SeeXISFTP
    Ours is file to file interface. No IR objects.
    Another imp thing is , we need to set Dynamic attributes both on sender & reciever.
    -santosh.

  • Seeburger Adapter issue

    Hi,
    when we try to upload multiple file into destination server. We are receiving a error as handshake failure.
    We are working on HA clustered enviornment.
    The error is basically happen, when muti-session pull and push on the
    destination server, the server will reject the connection.
    We tried in Dev, single node server architecture, which works fine for
    muti-file transaction,but getting error traffic for muti-file failed for QA environment.
    I assume it is the crusting server setup in QA that cause the problem. So
    do you have any idea of how to disable cluster nodes only for seeburger FTP
    adapter?
    regards,
    MMK

    Hello Frederic,
    I also have a similar issue.
    I have two communication channels configured: one communication channel which is a VAN sender and one communication channel is a VAN receiver (both are FTP adapters from Seeburger).  From the configuration guide of the Seeburger FTP/VAN adapter, I understand that IE/FTP interfaces only allows for a single connection for a single mailbox.  The documentation refers the users to the "Seeburger Master Installation Guide" but I can't find any relevant details there.
    My XI environment has two server nodes used to connect to the VAN.  Consequently, I ran into problems with "duplication session" errors.  I am currently experimenting with Resource Management available from the Seeburger Workbench, in particular, setting up resources and assignments to ensure that only one session is connected to the VAN at any one time.  However, I am struggling with how the resource should be created/configured (logical/logical choice, # of channels (total), # of channels (incoming)) and how they should be assigned.  Please advise on what is the proper setup in the context of my environment. 
    Your help is greatly appreciated.
    Thanks.
    Henry Lim

  • 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

  • Seeburger AS2 issue after PI Upgrade to 7.31

    Hi,
    After we upgrade the PI from 7.11 to 7.31, we have the following error when we test the Outbound AS2 scenarios.
    Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resources.ResourceException:
    com/seeburger/uri/dt/master/schema/ReportCategoryType : cannot initialize class because prior initialization attempt failed,
    com/seeburger/uri/dt/master/schema/ReportCategoryType : cannot initialize calss because prior initialization attempt failed

    Hi Rick
    What is the SP and patch level of your PI 7.31 system? Also, what is the version of your Seeburger installation, and was it upgraded as well?
    You can refer to Stefan Hilpp's guide for upgrading Seeburger Upgrade Guide available for Seeburger EDI-Adapters , as well as check OSS note 890721 for the compatibility matrix.
    Rgds
    Eng Swee

  • Seeburger forum?

    hi all ,
    I am going to touch Seeburger, is there any forums like SDN where pepople can discuss Seeburger products and technologies, eg. BIC Mapping Designer.
    Regards,
    Hui

    Hi,
    See the below link for Seeburger Forum
    http://www.automobilzulieferer.de/kunden/akhandel/forum.asp
    And also see the below links for seeburger related issues.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
    /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/SEEBURGER_SAP_Adapter_engl.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
    seeburger adapter configuration
    Regards
    Chilla

  • Wm process to reverse the GR

    Hi,
    After did the GR for the PO . did the TO for the material as well the material goes to the Quality stock. and did the UD and post the Q stock to Unrestricted stock.
    if i need to rever the GR. what is process from the WM end.
    from Qm end , i do reverse the UD.

    You would do the general Im process to cancel material docs, based on your config you would move the stock to the destination bins using a transfer order with respect to a material document or create a transfer order using LT01 and mvt type 999 to move it to the respective bin.Make sure u confirm the TO after each operation.
    so in your case if it is the same sloc cancel material doc using mbst for the transfer positing in QI stock then reverse the material doc for the PO receipt.So once u do MBST of the Purchase order material doc a defecit of the quantity reversed will show up in the interim area.Then create a TO using LT01 to move the stock from the bin into which the stock was initially received for ex 998.initial to the bin fro mwhere the defict was created.997.issue.
    Use mov type 999.If the stock was moved to a diff sloc during transfer posting then u will also have to create a TO in the first step.
    Hope that helps,please let me know if you have more questions.

  • Seeburger BIC Mapping deployment issue in PI 7.1

    Hi experts
    We have upgraded from XI 3.0 to PI 7.1 and seeburger is also upgraded to  a compatible version.(2.x).
    Mappings_user.sda was used in 3.0 environment.
    But we are not able to deploy the same in 7.1. I think sda format is not supported in 7.1.
    Is there any way to convert .sda to .sca and deploy?
    Or how can we generate a compatible deployment file for 7.1?
    I have tried using BIC mapping designer,but it shows the option for .sda and .jar only.
    Thanks in advanceDhanish Joseph

    Hi
    I have installed BICMD  632 version and imported .BICMD project file.
    Then assigned sda/sca number to it and created deploy file.(Mapping_user00.sda).
    Then installed this in PI system using JSPM.
    I have tested allmost all the mappings successfully except one in PI system.(EDI 990 message).
    When i send data to PI  data comes to channel and it shows conversion error. But detailed information not available.
    In seeburger monitoring  the message goes to recovery mode.
    I have used the input 990 X12 and tested in Seeburger BIC MD. And there it is success!!!!!! So i am confused what is happening when it comes to PI system.
    I faced some issues>>>
    1.  while importing project file into BIC MD it asked for apply some autocorrection  for one map.(different than this). I have clicked on cancel
    2. When i assigned SDA number to my project i have selected 2.1.0  SDA version( 1.8.0 option was also there).
    Your prompt reply is greatly appreciated .
    Thanks

  • Seeburger SFTP - Message Transformation Bean Issue

    Using Seeburger SFTP adapter to read a tab delimited file. File is being successfully read; however, content conversion need to be performed to convert the file content to XML.  Thus, using Message Transformation Bean with the following module parameters.  
    Issue: It is reading the file as is u2013 there is not content conversion is being performed. 
    Processing Sequence:
    1      localejbs/Seeburger/solution/sftp                Local Enterprise Bean     solutionid
    2     localejbs/AF_Modules/MessageTransformBean          Local Enterprise Bean     mtb
    3     localejbs/CallSapAdapter                    Local Enterprise Bean     exit
    Module Configuration:
    mtb          Transform.Class                          com.sap.aii.messaging.adapter.Conversion
    mtb           Transform.ContentType               text/xml;charset=utf-8
    mtb          xml.conversionType               SimplePlain2XML
    mtb          xml.documentName               XXX_EXPENSES_mt
    mtb          xml.fieldContentFormatting     trim    
    mtb          xml.fieldNames                    FIELD1,FIELD2,FIELD3,FIELD4
    mtb          xml.fieldSeparator               '0x09'
    mtb          xml.processFieldNames               fromConfiguration
    mtb          xml.structureTitle               RECORD
    The following the noticeable details on CC:
    Error type: TASK_ERROR >> Error date: 12/5/10 12:42 PM >> Description: Polling finished with errors. 1 file initiated. 1 file not polled due to errors.
    Message initiated succesfully
    Error type: TASK_ERROR >> Error date:  >> Description: File <amex.dat> could not be polled  from directory </usr/sap/interfaces/FTP1/send> on host <sapdv1ci>; Reason: removeFile: File xxx.dat could not be removed. SftpStatusCode: SSH_FX_NO_SUCH_FILE; Reason: No such file
    Any help is greatly appreciated.
    Thanks

    Check the following...
    1. Make sure you don't have any scripts running at your target folder.
    Example: If you are reading your file from TEST folder make sure you don't have any scripts running here.
    2. In File Setting section make sure you uncheck Delete file checkbok.
    Regards
    Srikanth Baki

  • Issue in Setting up Inbound and Outbound 997 in B2B

    Hello All-
    Please find the background and issue details.
    Background
    =======
    1. We use a common business action (Doc Type:997 and Doc Type Revision: 4010) to send Outbound 997 to the Trading Partners for the corresponding inbound documents from them. This common Business Action is used across all Trading Partners set up in the system to send Outbound 997. We attach this business action to the agreement for a particular Inbound Transaction Agrmnt
    2. As per new requirement, we have to enable Inbound 997 which is also Doc Type : 997 and Doc Type Revision as 4010. However, as mentioned above, since there is already a Business Action with doc type 997 and doc type revision 4010 combination, B2B did not allow us to setup the common inbound 997 business action
    3. As a workaround we modified the Doc Type Revision of the Common Outbound 997 Business Action to some random number and redeployed all the configurations that were using the Outbound 997 Business Action. We retained the Doc Type Revision as 4010 for the Inbound 997 Business Action.
    Issue Details
    =======
    1. After modifying the Outbound Business Action, as mentioned above, B2B is failing to identify the Outbound 997 Business Action and hence not able to generate the Outbound 997 for a particular inbound document.
    If anybody has faced similar issue, I would really appreciate if you can provide me pointers to resolve this issue and also let me know if we are doing the set-ups correctly.
    Please let me know if you need any additional information from my side.
    Thanks,
    Dibya

    Hi Dibya,
    In case of outbound EDI, document type and document type revision is used to identify a transaction set. Check whether you are receiving these two values correct. On the basis of transaction set and trading partner, it will identify the agreement and then find the particular business action in that agreement.
    Can you please mention that till what step your B2B is able to process the outbound EDI document?
    Thanks & Regards,
    Anuj

  • 997 adapter type not present in Seeburger for PI 7.1

    Hello Experts,
    We recently installed Seeburger on our PI 7.1 system. We deployed all the relevant modules successfully and also imported the meta-data to ESR after whcih we were able to see the FTP adapter from Seeburger. But we were not able to see 997 adapter.
    As mentioned in one of the blog, it is necessary to post funcitonal acknowledgements and configuration of 997 adapter is required for the same.
    We checked the installation guide from Seeburger but nothing has been mentioned in the same. any idea how to get the same in ID?
    Also one more doubt. Suppose I am getting 850 orders from 2 customers do i need to configure Identifiers in the Sender Seeburger adapter representing different customers?
    Thanks in advance.
    Regards
    Rajeev

    Rajiv,
    Identifiers are required only when the receiver channel is IDOC. 
    To summarise, you create one party per customer and the same would be done in partner profile as customer rather than logical system,.
    Then you specifiy the identifiers in parties and the same is represented in idoc communication channel . By this the idoc comms channel will know which customer in ERP it needs to post the idoc.
    This will be used only when the receiver is idoc.  Moreover in seeburger, you need to maintain an entry in the message splitter which will enable to use split 997 adapter.
    If you create party in XI, make sure to represent that party in ERP as either vendor or customer rather than logical system.  This will give you more clarity.
    Regards
    Krish

  • Seeburger splitter configuration issue

    Dear All,
    I am trying to configure the Seeburger splitter for my outbound EDI interfaces, i enteredmapping Name, clicked on Search Services for the Sender-Sercvice, clicked on Search Channels for the 850 channel i am not able to get the channels automatically.
    we have same configuration in DEV and QAS but they are working correctly same objects has been transported to PRD and we are not getting those channels automatically.
    Note:but with same configuration objects we are able to get channels automatically in DEV and QAS .. any ideas?
    Your help will be appreciated.
    Thanks,
    Naveen

    Hi Naveen,
    The channel is populated based on party and service. In your case if you have issue only for one interface (one inbound EDI interface), then it might related to cache.
    But if you have problem with all interface, then you need to check the seeburger workbench configuration.
    regards,
    Harish

  • Issue with IDOC occurence and SeeBurger message mapping

    Hey Guys
    While developing a EDI 850 to IDOC scenario i came across this issue with pre-delivered Seeburger mapping(A_850_V4010_to_I_ORDERS05).
    I actually need to post multiple IDOC's to SAP system in the same message so i changed the IDOC occurence to unbounded and re-imported that as a .XSD file in Integration repository.
    Earlier the pre-delivered message mappings provided by SeeBurger(under SEEBURGER_HIGH-TECH, 1.7.1 of seeburger) was working fine for me since i was posting only 1 IDOC but now the mapping is failing as the IDOC occurence has changed(unbounded).
    Is there a way we can do some settings on SeeBurger server or Bic so that we can use the pre-delivered mapping for Multiple IDOC's as well?
    I just want to make sure before i start off with doing whole of the mapping manually.
    Thanx
    Aamir

    Thanx for the input guys
    @Deepthi.
    Doing whole of mapping manualy is definitely the last option but i m looking for ways to re-use the pre-delivered SeeBurger mapping.
    >>Seeburger Mapping is only just to convert XML to EDI and EDI to XML.
    Bic mapping designer does this,i m dealing with message mapping of XI(convert source to target) not Bic designer right now,and Bic does more than just XML to EDI and vice versa,it handles other industry standards too.
    @Jens
    >>The XI message mappings from Seeburger in the Industry solutions are mapping templates
    Yeah,but the mapping template i have deals with 850 to ORDERS05,when i change IDOC occurence and re-import it back in Integration repository,it doesn't stays as ORDERS05,it has to be changed to user defined message interface(in my case MI_ORDERS05) so i m unable to use 850 to ORDERS05 template.
    @Seshagiri
    >>Open the Seeburger SWCV From the IR--goto External Def---Select the right one and copy it and paste it in notepad.
    Changing the occurence is not an issue,i want to re-use the pre-delivered mapping in Integration repository,which is not working.
    Looks like i need to do it manually
    Thanx
    Aamir

  • Seeburger ftp adapter issue

    Hi there,
    We have the following scenario. We want to get EDI 861 via ftp from our partner  to XI to our R3. The challenge we are facing is getting started with seeburger adapters. We looked into seeburger ftp/van adapter. We are not using VAN. Is it possible to configure this adapter in sender communication channel for our scenario? We tried it, but we are stuck at choosing the message protocol, because we get only the VAN supported message protocols from the drop down menu.
    Our goal is to get the EDI 861 from our partner via ftp, parse it to XML representation, map the xml to equvalent IDOC and send it to our R3. Is there a seeburger adapter that receives the edi and parses it into? If yes, how do we go about to solve this issue. Right now, we are not able to configure the adapter right so that we could get the edi flat file via ftp and get the parsed edi xml in xi moni.
    Your help is greatly appreciated.
    Thanks

    Hi,
    You need to configure the AS2_MDN_Sender Communication Channel with transport protocol is AS2 and Message protocol is Reports.
    Regards,
    Ramesh

  • Issue in receiver SFTP seeburger adapter

    Dear all,
    We have a proxy to sFTP scenario.
    The target message is being delivered to a sFTP system using a receiver sFTP Seeburger adapter.
    I have this error being shown in the receiver channel.
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: >> Description: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>> Details: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMPONENT_ERROR>>Retryable: true>>Fatal: true, >> Description: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>> Details: putFile: Target filename <TEMP_20110406_115127.TXT>; Flags set: appending=<false>; useTempFile=<false>; ; Reason: Failure>>SendingStatus: NOT_TRANSMITTED>>FaultCategory: COMPONENT_ERROR>>Retryable: true>>Fatal: true.
    The Seeburger WorkBench monitoring has a 2 error entries which says
    1. PUT command for file <TEMP_20110406_115127.TXT> is in progress.
    2. "Error on send, will be retried"
    Finally, the .txt file is partially written in the receiver system.
    If anyone has any inputs/pointers to resolve this issue. Pls share the details.
    regards,
    Jack.

    Hi Jack,
    We are also facing the same problem with the seeburger SFTP adapter. If you find the solution , Plz let us know.
    Thanks,
    Soumya.

Maybe you are looking for