Regarding AS2 seeburger to idoc interface

Hi Team,
I hope you are doing well.
I am working on as2 seeburger to idoc interface.
what are the steps required for this in IR and ID ?
where can we monitor if we get the error in as2 adapter side?
Regards
ANJAN

Hi,
>>>what are the steps required for this in IR and ID ?
In ESR:
1.First you need to get the xsd of EDI document and import it into ESR under External definitions and import the IDoc also into ESR.
2. Create a service interface for the EDI document structure.
3.create message mapping between the ED(xsd of EDI doc) and Idoc.
4.Create operation mapping.
In ID:
1.Configure the parties using the AS2 IDs.
2.Create an AS2 sender communication channel(refer the configuration guide that you receive from seeburger).
3.Create an IDOC receiver communication channel.
All the remaining steps are same what we do for normal scenarios like receiver determination,interface determination and agreements.
>>>where can we monitor if we get the error in as2 adapter side?
In Seeburger workbench
Regards,
Priyanka

Similar Messages

Regarding documentation on User Exits, IDOCS, Interfaces etc.

Hi Friends,
Can any one help me if any documentation on User Exits(MM/WM related), ALE IDOCS/ INTERFACES etc available which shall help in understanding the above concepts.
Quick help will be highly appreciated and rewarded pls.
Thanks in Advance
Regards,
Prasanna.

this info is spread though all channels SAP has, but unfortunatly not consistent, thats why it is so hard to find something.
You can find info at help.sap.com
e.g. this link (see the menu on the left as well)
http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/frameset.htm
Further you can find info at SAP MArketplace (OSS notes)
Or directly to the coding in SE37 and SE38.
IDOC and ALE documentation can be found here:
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
and
http://www.logosworld.com/www5/books/IDocBook/IDocBook.htm
Edited by: Jürgen L. on Oct 24, 2008 12:21 PM

Information on AS2 Seeburger monitoring

Hi All,
Recently a Seeburger interface got introduced in our production,could any one please share their experience or documents for monitoring AS2 .
2)In As2 scenarios ,how to correlate the MDN number with XI Message Ids.
Regards,
Vidya

Hi look at this Thread
Re: Mapping and Monitoring in B2B(Seeburger adapters) scenarios
AS2 Seeburger error troubleshooting
Regards
Abhishek
Edited by: Abhishek Agrahari on Jun 1, 2009 7:02 AM

Unable to interpret IDoc interface Error

Hi All,
We are getting the following error while trying to translate a X12 to IDOC , we are using Seeburger Adapters for the translation.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to interpret IDoc interface I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The Reason we are using a Interface rather than using a IDOC directly is because our the IDOC Structure is 867.ORDERS01.ZORDRS1x and this is a custom IDOC in ECC and when we try to directly use the structure in the Interface Determination we get the error
Check Result for Object ARROWUS | ARROWUS_IN_AS2 | A_867_V4010_ABS | | BS_ECC_D03_DEV
First character invalid: 8 Only a(A)-z(Z), 0-9, and "/" and "_" are permitted
Has anyone faced a similar problem ? If so please let me know how you fixed it.
Appreciate your help
Regards,
Madhu

have you seend below threads:
[link1|Unable to interpret IDoc interface ZSHIPDEL_packageRD;
[link2|IDOC Error;

AS2 Seeburger error troubleshooting

Hi,
I just would like to ask if anybody knows how to troubleshoot errors on AS2 Seeburger. We usually have the below errors in the Seeburger Monitor:
- Error on send, will not be retried     Could not send ansynchrone MDN to partner!
- Error on receive, task will not be retried     Cannot initiate received message to backend system AND max retry reached!
- Error on receive, task will not be retried      Could not send ansynchrone MDN to partner - url not set!
- Initiation to Backend Pending                    Could not send ansynchrone MDN to partner!
- MIC error
Do you happen to have materials about Seeburger which shows how to resolve and prevent such issues? I also need to get the root cause of these issues, can you kindly help me identify the actions I need to take to get to the root cause?
I look forward to hearing form you.
Kind regards,
Grace

- Error on send, will not be retried Could not send ansynchrone MDN to partner!
   1. Tell Business partner to not to request MDN when they send document to you.
   2. check the authentication certificate in your sender agreement
- Error on receive, task will not be retried Cannot initiate received message to backend system AND max retry reached!
   1.Sender might be using wrong certificate.
- Error on receive, task will not be retried Could not send ansynchrone MDN to partner - url not set!
same like first answer
- Initiation to Backend Pending Could not send ansynchrone MDN to partner!
same like like first answer
- MIC error
valide sender is not identified, check the AS2 id and certifcates

File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

Hi All,
Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
Anyidea what might have gone wrong??
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
+<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
<SAP:Retry>M</SAP:Retry>
Waiting for your answers.
Thank You.
Seema.

Hi Seema,
I think you are using mi_Orders05_In_Asyn as the IDOC interface.
Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
Let us know if that doesnt solve your problem.
Regards,
Sumit

Error in communication channel AS2 Seeburger EDI Adapter

Hi,
I am facing one issue in communication channel at receiver side. Adapter type is AS2 Seeburger EDI adapter.
Brief overview of scenario: Sender is R/3 sending an IDOC and Reciever is Party (Vastra_Gotaland).
The error in reciever communication channel is : Error type: REPORT_ERROR >> Error date: 8/26/10 10:18 AM >> Description: MIC not verified # integrity-check-failed [8/26/10 10:18 AM].
Please give your important feedbacks.

Hi Vikrant,
I have already checked channel configurations and there is no problem with signing certificate. I have checked that also.
Edited by: Sadhna Achhra on Aug 26, 2010 1:10 PM

Reg idoc interface

hi all,
its regarding idoc interface,try to help me.
i have a programRHALEINI and defined in Work Item WA00012 - "IDOC Extract for HR Master Data"
This IDoc will be created in SAP but not delivered to any external system.
The interface created in this work item will then read these IDOCs and the required fields will be identified and reformatted so that it can be processed by the FMS system.
Program RHALEINI is executed to create the IDocs for all employees. Refer to Work Item WA00012 - "IDOC Extract for HR Master Data
WI WA00012 will also provide Function Module Z_TP_INI_IDOCS to pull all the IDOCs needed to extract all of the employee data (latest employee extract).
The purpose of this interface program is to read all IDOCs created by program in WA00012 and map the required data into a flat file structure.
here to map i have header trailor and body data how to do this.
provide me solution asap with an example
thanking u

Hi,
Once you get the idocs then you have to read the info from these idocs and then you have to populate it into your file.
It depends on the data format that they want to create it.
cretae a file of type l_v_filename TYPE draw-filep,
then start creating header structure item structure and footer structure.
keep passing data to these structures and transfer it to file
TRANSFER l_wa_header TO l_v_filename_temp
same thing you cna do for ur item data,
loop on this and pass line by line to the file.
same way populate the footer data also.
It entirely depends ont he way they want to populate in the final file.
Reward points if you find useful.
Regards,
Sasi

Idoc interface not found..

I'm attempting to pull in an XML file to Idoc and I'm getting an error stating "Unable to interpret IDoc interface ZINCOMINGINVOICE_CREATEFROMD01" in the monitor.
I have imported the Idoc into XI and mapped to it and the translation is working fine. I have also gone into IDX1 and IDX2 on the target R/3 system and on the XI system and setup the port and Idoc in the inbound list. I have also managed the port and setup the inbound document in WE20 and WE21 on the target R/3 system.
I have a couple questions.
1. Have I done all the setup?
2. With the Idoc of ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 and the setup above for WE20 inbound set to ZINCOMINGINVOICE_CREATEFROMDAT is that sufficient?
3. Likewise with the ZINCOMINGINVOICE_CREATEFROMDAT.ZINCOMINGINVOICE_CREATEFROMD01 idoc and IDX2 set to ZINCOMINGINVOICE_CREATEFROMD01 is that sufficient?
My inbound xml document is below.
<?xml version="1.0" encoding="UTF-8" ?>
- <ZINCOMINGINVOICE_CREATEFROMD01>
- <IDOC BEGIN="1">
- <Z1BP_INCINV_CREATE_HEADER SEGMENT="1">
<INVOICE_IND>X</INVOICE_IND>
<DOC_TYPE>ZA</DOC_TYPE>
<DOC_DATE>2001-04-20T23:59:20-07:00</DOC_DATE>
<PSTNG_DATE>2005/05/02</PSTNG_DATE>
<REF_DOC_NO>123456</REF_DOC_NO>
<CURRENCY>USD</CURRENCY>
<GROSS_AMOUNT>4900</GROSS_AMOUNT>
<HEADER_TXT>[email protected]</HEADER_TXT>
</Z1BP_INCINV_CREATE_HEADER>
- <Z1BP_INCINV_CREATE_ITEM SEGMENT="1">
<INVOICE_DOC_ITEM>1</INVOICE_DOC_ITEM>
<PO_NUMBER />
<PO_ITEM>2</PO_ITEM>
<ITEM_AMOUNT>130</ITEM_AMOUNT>
<QUANTITY>30</QUANTITY>
<PO_UNIT>EA</PO_UNIT>
</Z1BP_INCINV_CREATE_ITEM>
</IDOC>
</ZINCOMINGINVOICE_CREATEFROMD01>

Hello,
I encountered the same problem. If you are sure to have configure correctly your IDX2 transaction, be sure you have import the idoc in the repository under the good composant.
For example if IDOC is for R/3 4.6, import your idoc under SAP APPL 4.6C or SAP BASIS 4.6C to use it in the directory with a component that you defined before in your SLD as a SAP R/3 product.
Regards,
Chris

Gerneric IDoc Interface

Hi,
We have the following set up:
A JMS sender channel sends IDocs in a non XML format (some kind of flat file IDoc). I created a ABAP mapping that converts this flat IDoc to an XML IDoc. The problem is, that the sender sends diffrent kind of IDocs through the same channel.
1.try: I imported all possible IDoc types and tryed to do a content based routing. The problem is the input message. Due the fact, that this is no XML on input side, I cannot check the input data. Is there a possibility to do content based routing AFTER the mapping?
2.try: I created a dummy IDoc interface. The message type is just one tag (I created the complete IDoc XML in the ABAP mapping). So I send all data from the JMS to an IDoc receiver with the same dummy interface. The content of the receiver message contains all IDoc control data (EDI_DC40). The idea is, to use this interface as an generic IDoc interface but I get the error "ATTRIBUTE_WRONG_INTF" - "Unable to interpret IDoc interface MI_IDoc_any_IB_Async". Is there a way to set the IDoc attributes generic in the ABAP mapping or do I have to use the IDoc interface, that I imported?
Thanks for your help
JP

1. The use of BPM may ease the routing part after mapping wherein u may use transform step folowed by send step
2. While doing idoc communication, even if u change the structure, u ll have to use the interface name as the original imported idoc name only. Otherwise u ll get the same error.
Regards,
Prateek

IDOC Interface Error

Hi Experts,
I am getting the same error: and from the forums I came to know that we need to use the IDOC name in the Interface mapping.
I used the modified IDOC structure(External Definition) in mapping, but when I select the original interface in Interface mapping I am not able to get the message mapping name.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MI_IDOC_IA</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface MI_IDOC_IA</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please provide me some hint.
regards,
sri.

Hi Sri,
I used the modified IDOC structure(External Definition) in mapping,
but when I select the original interface in Interface mapping I am not able
to get the message mapping name
Are you following the steps as mentioned in the blog /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change or SAP note 814393
Are you creating any separate Message interface after creating the External Definition?Pls don't create any separate interface.
just export the XSD of the IDOC and change the occurrence (dont save ED with any other name ,keep the same IDOC name)
now in message mapping import the XSD you save earlier. and do the mapping.
In Interface mapping and in the ID configuration use the imported IDOC name only
Regards,
Srinivas
Edited by: Srinivas on May 15, 2010 10:15 PM

Unable to interpret IDoc interface ZSHIPDEL_packageRD

Hi,
I am doing a file-xi-idoc scenerio.
I've exported my custom idoc as an xsd and modified the schema to allow for multiple idocs to be generated for each file - as per note 814393.
However I get the following error message at runtime (Call Adapter):
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>ZSHIPDEL_packageRD</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface ZSHIPDEL_packageRD</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Has anyone else experienced this error?
Regards
leenor

I have a scenario exactly like the above one.
My file structure is like
TransactionDetailList
 TransactionDetail (1:N)
 Transaction_Type (0:1)
 Transaction_Date (0:1)
 Add_Revise_Cancel_USER_ID (0:1)
 Add_Revise_Cancel_Date_Time (0:1)
My IDOC has the below structure,
ZIDOC_BDS_DIVERSION
 IDOC
 ZSEGL_DIVERSION_HEADER
 SEGMENT
 NOMNR
 NOMIT
 EVENT_DATE
 ZSEGL_ DIVERSION_ITEM
 SEGMENT
 WHO_PAYS_DIVERSI
 LOCID
 DEST_CITY
so i have to generate multiple idocs in the target side.
I have created external defination based on my IDOC.Defined mapping between File and the external defination crerated from the IDOC. also defiined interface mapping between file and external defination.
In the Integration Directory ->Interface Defination, I have used the actual Idoc as Inbound interface for which there is no mapping as we have not defined anything for this. This is exactly what you have defined above.
I am getting the following errors like,
"Error: MSGGUID A5EE4A305B4111DABFBE0002551F08EE: Tag TransactionDetailList found instead of tag IDOC BEGIN="
Please let me know if I am missing some steps while configuring or I have to do something else.
Thanks & Regards,
Mukesh

Unable to interpret IDoc interface

Hi,
I have a File to multiple IDOC scenario. I have change the IDOC occurance by creating ED.
I have developed everything but the following error is coming during my end to end testing.
Unable to interpret IDoc interface
Thanks,
Raj

Raj Says..
I have change the IDOC occurance by creating ED.
Hi Raj,
Since you have changed the IDOC occurrences by creating an ED so you have to make sure that IDOC and ED has been used properly in your scenario.
1. MM = use ED
2. IM = use original IDOC
3. ID = use original IDOC
Regards,
Madan Agrawal

IDoc - IDoc interfacing with multiple mappings

Hi,
We want to use two different mappings for the same IDoc interface (based on a condition). So we use the ORDERS idoc for a sales scenario and also for a purchase scenario. The sending service is the same for both ORDERS messages, lets call it service SEND. Furthermore, for both ORDERS messages, the receiving service is also the same lets call it RECV.
The problem is that we want to use a different mapping for the ORDERS sales scenario as for the ORDERS purchase scenario. The sending and receiving interface in both cases is the same.
The receiver determination and interface/mapping determination is a problem in this case.
One way to solve this is to use a party, but in the configuration of the party you can only use the same sending logical system name ONCE. So party A cannot have the same logical system name (SEND) as party B (SEND) for scheme ALE#LS.
Another way would be to use different services, one for the first scenario and mapping and one for the second. Again the problem is that you need to enter adapter settings for both services (RECV1 and RECV2), but a logical system name can only be used in ONE service. If you want to assgin it to a second service, this is not allowed.
Does anybody have a solution for this?
thanks !

Hi Alexander,
why don't you try doing it in one BPM?
something like this:
one sender
one receiver
2 mapping programs
Receive step -> Swich Step - if PO go to Transformation step one (mapping 1), else go to Transformation step two (mapping for the SO) - Send Step?
you can base you swith step on E1EDK14 segment qualifier = 013
(As far as I remamber only Purches orders have it)
but check it:)
BTW
if you use the Swith Step you probably want to use a Transformation step before the Swith step (mapping from ORDERS to dummy message with one TAG - indication if this is PO or SO based on content of the ORDERS) this way the swich step will work for sure
Regards,
michal
Message was edited by: Michal Krawczyk

Idoc interface!

Hello all,
Can somebody send me documentation over Idoc interfaces? I need for Inbound now...but Outbound will be helpful though for future use )
And I have a question related to middleware too. A flat file will be the input to middleware (XI or webmethods). What is the output? Is it an IDOC format file or IDOCS with status 64 in SAP?
Thanks,
Message was edited by: Somen

Hi,
For inbound idoc in partner profiles if you set trigger immediately for a message type , whenever idoc comes from middleware , it will be processed automatically . for process success idoc status will become 53, if it is failed idoc status becomes 51.
at partner profiles if idoc process selected as process through background program , whenever idoc comes from middleware it goes to 64 status. for these idoc's we need to schedule RBDAPP01 program to process 64 status idoc's or we can process these idoc's from BD87 transaction
Check these links:
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18eff546a11d182cc0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/9c/2744f5fa7464429a13345be4050fb6/frameset.htm
http://www.sappoint.com/ppt/ale.ppt
below details might help you.
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE19 EDI test tool. Use to test inbound Function module changes.
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30 Create IDoc extension type
WE31 Segment create
WE57 Assign function module to logical message and IDoc type
WE60 IDoc type documentation tool
WE82 Link Release detail to Extension IDoc Type
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA ALE Application Distribution
BALM ALE Master Data Distribution
WEDI - main transaction for all ALE settings
Regards
Appana
*Award Points for helpful answers

Regarding AS2 seeburger to idoc interface

Similar Messages

Maybe you are looking for