Interface of an IDoc

Hi all,
I am new to Idoc's...How can I find the interface of an IDoc?
Thanks.
Moderator message : Search for available information, thread locked.
Edited by: Vinod Kumar on Feb 10, 2012 10:12 AM

Hi,
You can search SDN for the same, there are lots of document/wiki pages available here.
To find the details of interface you need the IDOC number or msg type. Your question is not very clear to me.. Can you be specific what the requirement ?

Similar Messages

Enhanced Interface Determination for IDOCs

Hi All,
I've a query on the usage of Enhanced Interface Determination for IDocs.
I've to create IDocs based on the condition in the Message Mapping i.e. say if recordtype in the source is A then IDoc1 should be created and if recordtype is B then IDoc2 should be created.
Is it possible to use Enhanced Interface Determination to achieve this??.. Because I was told by someone that Enhanced Interface Determination can't be used for IDoc based scenarios though am using External Definitions for the mapping purpose. Please clarify.
Thanks in advance
Regards,
Joe.

Hi Sridhar/ Bhavesh,
Thanks for your prompt reply. I think I wasn't clear in my previous post.
The scenario is the input file has three different record types (3 different structures) and the IDocs should be created based on the record type. I don't think I can use the condition based scenario as the record types are totally different. Please suggest.
Thanks,
Joe.

ABAPer responsibility in Interface and Incoming Idocs

Hello All,
Could any body please explain me what is ABAPers responsibilitis in Interfaces and Incoming Idocs.
Case: We are getting an idoc(inbound) in our system to create sales order so please let me know in this case what would be my roles and responsibilities as an abaper in detail..
Thanks to reply at the earliest..
If you would like to share some documents then here is my email id: [email protected]
Thanks,
Devasing.

Hi,
An ABAPers role in this case could be incase any enhancements are needed, this is if all the settings for the ALE are going to be handled by an ALE consultant.
In this case if some consumization needs to be done like enhancing the existing IDOC for creating a sales order, then an ABAPer would come into picture.
Thanks & Regards,
Vanita M.

Sender Namespace and Sender Interface in the IDOC to IDOC scenario

My question maybe very basic...
It is SAP IDOC to SAP IDOC scenario.
Lets assume that I have done config in XI for:
 Sender = A,
 Interface = B,
 Namespace = C.
My question is:
Is there a place in the source system or somewhere to point that
when an IDOC e.g. DEBMAS is triggered in the source system,
then the Interface should be B and Namespace should be C in the xml file ?
Cheers
Agnie

Hi Agnieszka,
 Check these threads/blogs from you may get some help:
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Idoc-to-idoc scenario
IDoc to IDoc scenario necessary configuration steps
For A-Z help on IDOC, you can refer Michal's book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
Regards,
Subhasha Ranjan

Error when trying multiple inbound interface determination for IDOC

Hi !
I have this scenario: File -> XI -> IDOC.
For each source file, I need to send multiple idoc packages, all to the same business system, but each package should be the result of different interface mappings.
All mappings have same source and target message types...e.g. source: MT_MyFile, target: CREMAS04.
To avoid creating a generic mapping program, we need to duplicate the current mapping program, make it handle the new case, and then add it as second interface mapping in Interface Determination, with same inbound interface, but different interface mapping, without conditions. All interface mapping should execute.
We are receving this error:
<SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:P1>
<SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:Stack>
Any clues?
Regards,
Matias.

Hi Satish !
Thanks.
I need to send different IDOCs to SAME business system.
In Interface determination I need this:
Inbound Interface -
Condition -
Interface Mapping
IF_1 no condition M_1
IF_1 no condition M_2
I need to send BOTH IDOC packages to same business system.
But it keeps throwing the posted error.
Regards,
Matias.

Two Interface with same IDOC sperated by Document Type

Hi All,
I have Two interface which is for RFQ and Purchase order, bother uses same IDOC orders05, i need to indentify which one for which interface using Document type for purchase NB and and AN for RFQ , please help me to slove this isssue , hope we muct use Context object for this , but i dont know how to use it , please help me
thanking you
Sridhar

Hi,
Can you explain a bit about your scenario, coz I think it can be handle in other way without using context objects..
But if you want to use the context object, then you can add it in Message Interace ---> Context Objects, and in ID while doing RD you can find it under Condition Editor ---> take F4 help and then select context objects.
Regards,
Sarvesh

Inbound interface with multiple IDOC processing

Hi,
I have to create an inbound interface which has to be triggered only when a batch job is completed in the middleware. The batch job will create 2000 records and 1 IDOC for each record. I have to get all the 2000 IDOCs and then process them together. I have to manipulate the data in these 2000 IDOCs and update them in a SAP table.
Please let me know how do I proceed with this.
Should I go with a custom func module or a custom program?
Thanks,
Abhishek

Hi,
Custom function module with standard parameters : For details refer to the topic Implementing Inbound Processing on page 85 of the
[ALE Programming Guide|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf]
regards,
Advait

PI 7.4 - interface from ECC(idoc) JDBC, idoc not making it from sm58 '

Hi Experts,
I've got an interface which works in our dev and 2 of our test systems but NOT the 3rd test system. It doesnt work in our live system either. (essentially its a split receiver determination - goes to both jdbc and a file).
I've reintroduced the config from the dev system to the 3rd test system and overwritten its ico/scenario in the hope that it might work - it didnt make any difference as was getting the first error below in bold.
I've checked all RFC connections, destinations, partner profiles and ports, all seem in order and mirror systems that work, bar the naming conventions.
I've checked The FM version, its the same version as the system which works.
In sm58 I was originally getting the error 'Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad', upon 'googling' this error it was suggested on SCN to essentially delete old config and reimport / rebuild the interface (Commit fault: ASJ.ejb.005043) . I've tried to reimport the config scenario / ico, i then deleted the config scenario and reimported it. This hasnt worked.
I have had our Basis team double check the NWA settings, and the ResourceAdaptor settings were reset.
When re running the trfc in sm58, i now get the error ' Failed to resolve repository reference @XI_IDOC_DE FAULT_DESTINATION_DEV'
Would appreciate some feedback as to what to try next..

Hi George,
We have seen this issue sporadically too while deploying to our QA system. What I have generally done in the past to get it working is the following (I have run all the steps because I don't know if they are all required to get it going again):
1. Open ID and clear the SLD data cache
2. Open sender system in ID and do compare of adapter specific identifiers with SLD and then apply
3. Deactivate sender IDoc channel and then reactivate (I would double check your destination in the settings also)
Hopefully this will help.
Regards,
Ryan Crosby

FI - Interface triggerring multiple idoc is not getting posted

Hi all,
I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
But the same idoc, when i proccess indivisually get's process gets posted successfully.
I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
As an abaper, I am not able to understand problem to take corrective steps.
Thanks & Regards
shashikant

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

ID : interface determination - Interface mapping (file- IDOC with externa)

Hi,
scenario : XML file read and mapped to Multiple IDOC in single message
all IR stuf are done but in the ID I cannot choose the mapping interface
here is a document of everything that was done...http://docs.google.com/Doc?id=dcsvs2n3_51jnrfw6
Thanks for the help

Hi Stepen,
Simple for Reciever Business System did you add the Idoc itself that was imported as Receiver Interface..
Just double click the Receiver Business System and Then click Receiver and See if the IDOC name exists other wise insert it...
Also In the Interface determinatin select the actual idoc that you imported and not the XSD....
Finally if the above doesnt work Try this since you are using ED create Message Interface and mention the xsd as MT.... and in Interface Determination use the Actual idoc imported and not ED ....
Regards,
sridhar
Message was edited by:
sridhar reddy kondam

MES Interface Development (Standard IDOC-MATMAS enriched with Z-Fields)

Hello Everyone,
We have an issue that we want to sent IDOC data to our local MES System. The XML Target Structure of the MES System is given and cannot be changed.
Most of the fields to be sent are in the MATMAS IDOC but some fields need to be enriched with material classification data which are maintained for each material individually in the ERP. To retrieve the data out of ERP we using the u201CBAPI_OBJCL_GETDETAILu201D. Here we perform an iteration about all these fields to read the classification description and the associated characteristic value. Sometimes it can happen that not for each material the value are maintained and then we are getting blank values
Now I coming back to my main questions.
The target structure of the MES XML File is given and need basically just two core segments from MATMAS IDOC.
E1MARAM SEGMENT="1" -> Key fields needed: Material Number, MEINH, EAN Number etc.
E1MAKTM SEGMENT="1" -> Key fields needed:: Material Description
The n- Classifcation field need to be listed directly under the segment E1MARM Segment. So the target structure need to be dynamically built with these n Z Field under den Segment with the following structure.
E1MARAM SEGMENT="1" Material Number, MEINH, EAN Number etc.
1
u2026<ZL161AUSPM SEGMENT="1">
 <ATNAM>MGBEZ_</ATNAM>
 <ATWRT>Galenical Bulk Prod.</ATWRT>
..</ZL161AUSPM>
n
E1MAKTM SEGMENT="1"  Material Description
As stated out above the information from the classification data are filled in an internal table (XML document with several Row)
Questions:
How do I get the information from the internal XML Document into such ZL161AUSPM structure. Shall I rename the rows in the XML Document from Row to <ATMAN>? And how is this possible? I assume that I cannot change the row name in an "MII XML Document"
<?xml version="1.0" encoding="UTF-8"?>
<Rowsets DateCreated="2009-09-04T14:24:58" EndDate="2009-08-31T14:43:13" StartDate="2009-08-31T14:43:13" Version="12.0.6 Build(12)"><Rowset><Columns><Column Description="CHARACT" MaxRange="1" MinRange="0" Name="CHARACT" SQLDataType="1" SourceColumn="CHARACT"/><Column Description="CHARACT_DESCR" MaxRange="1" MinRange="0" Name="CHARACT_DESCR" SQLDataType="1" SourceColumn="CHARACT_DESCR"/><Column Description="VALUE_NEUTRAL" MaxRange="1" MinRange="0" Name="VALUE_NEUTRAL" SQLDataType="1" SourceColumn="VALUE_NEUTRAL"/></Columns><Row><CHARACT>CH0_MES_01</CHARACT><CHARACT_DESCR>CH0_MES_01</CHARACT_DESCR><VALUE_NEUTRAL>AT</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_16</CHARACT><CHARACT_DESCR>CH0_MES_16</CHARACT_DESCR><VALUE_NEUTRAL>AAI-WC</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_01</CHARACT><CHARACT_DESCR>CH0_MES_01</CHARACT_DESCR><VALUE_NEUTRAL>AT</VALUE_NEUTRAL></Row><Row><CHARACT>CH0_MES_05</CHARACT><CHARACT_DESCR>CH0_MES_05</CHARACT_DESCR><VALUE_NEUTRAL>10000.0</VALUE_NEUTRAL></Row></Rowset></Rowsets
How do I get the dynamically the structure under the E1MARAM SEGMENT="1"? with n u2013 integration? This mean if the material has been assigned three characteristic then I need three time the structure under the segment u201CE1MARAMu201D
Is someone experienced with interface development of such Z-Message respectively has someone an idea or guideline to dealt with such issues?
Thanks in advance,
Markus
PGST
PT Business Solution Management- Manufacturing
F. Hoffmann-La Roche Ltd. Switzerland, Basel
Edited by: Markus Schmeckenbecher on Sep 4, 2009 2:33 PM

Markus,
it is a bit difficult to get the structure from your post, but when I get it right you need to add new nodes in a predefined xml structure.
Did you have a look at the Link editor action "Data Item" from the SAP xMII XML Output? You can define a name and value and add it to a given xml structure. A problem might be the target xml if it is not an IlluminatorDocument (which is of kind /Rowsets / Rowset / Row).
If this does not work, you may try to build Local xml structures for all your Z fields, and append those xmls to your target, using the Link Editor Append XML function.
Michael

Inbound Interface using HRSM_D01 Idoc

Hi,
We have an inbound Idoc using the HRSM_D01 idoc. This interface allows an external system to send data to our SAP HR system to update infotypes 2001 and 2002.
We are planning on extending this interface by not only allowing new values to enter the system but also cancellations of old records. For example an employee has reported working time for one day but would like to change the record into absence. The employee should then be able to change the record in the source system and the cancellation of the old record (deduction from IT2002) for the attendance and a new record (IT2001) for the absence should be sent to SAP.
There is a field in the Idoc that indicates if the record should be reversed. But it seems like the RBDAPP01 program that processes the inbound idocs does not update the interface table PTEX2000 with records that have X in the REVERSED field in the idoc.
Does anyone have experiences from cancelling records in a source system and the passing the cancellation to SAP HR?
Thank you
/Björn

Hi,
We have an inbound Idoc using the HRSM_D01 idoc. This interface allows an external system to send data to our SAP HR system to update infotypes 2001 and 2002.
We are planning on extending this interface by not only allowing new values to enter the system but also cancellations of old records. For example an employee has reported working time for one day but would like to change the record into absence. The employee should then be able to change the record in the source system and the cancellation of the old record (deduction from IT2002) for the attendance and a new record (IT2001) for the absence should be sent to SAP.
There is a field in the Idoc that indicates if the record should be reversed. But it seems like the RBDAPP01 program that processes the inbound idocs does not update the interface table PTEX2000 with records that have X in the REVERSED field in the idoc.
Does anyone have experiences from cancelling records in a source system and the passing the cancellation to SAP HR?
Thank you
/Björn

Create interface or use idoc structure directly?

Dear all,
I am creating a scenario from a FILE (as IDOC structure) to RFC message.
If I create a Interface Mapping, do I use the IDOC structure and RFC message as source and target Interface or do I first create interface definitions based on these structures and then use these?
Regards.

> I am creating a scenario from a FILE (as IDOC
> structure) to RFC message.
>
> If I create a Interface Mapping, do I use the IDOC
> structure and RFC message as source and target
> Interface or do I first create interface definitions
> based on these structures and then use these?
You are talking about IDoc-XML? Then you should be able to use the IDoc Interfaces with your sender service directly.
CHRIS

IDoc Collection Scenario (IDoc to Mail Interface)

Hi,
I am configuring IDoc to Mail Scenario using BPM.
I gone through following link for develop the scenario. I am still unable to complete the scenario.
Collect Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
I have done following steps in my configuration. Please correct my steps if i am wrong.
Source is Outbound Invoice IDoc (SAP System).
Target is Inbound EDI 810 format send as a email(Mail System).
1. Create an Abstract Interface for Invoice IDoc(MI_IDoc_ABS)
2. Create a Message Interface for EDI 810 for Inbound(MI_EDI810_IN)
3. Create an Abstract Interface for EDI 810(MI_EDI810_ABS)
4. Message Mapping between Outbound IDoc and Abstract Invoice IDoc. I did this as per one of the above link. but did not understand the importance of this. On Message tab of Message Mapping, it shows the occurance as 1 for both source and target. I did not see the mention of this mapping in the BPM. Not sure if this was required?(MM_IDoc_ABS)
5. Message mapping between Abstract Invoice IDoc to Abstract EDI 810. On the message tab of message mapping, occurance of Source message is changed to 0-unbounded and occurance of target is kept as 1.(MM_EDI810_ABS)
6. Define Interface Mapping for above mappings
a) IM_IDoc_ABS - Outbound Invoice IDoc + MI_IDoc_ABS
MM_IDoc_ABS
b) IM_EDI810_ABS - MI_IDoc_ABS + MI_EDI810_ABS
MM_EDI810_ABS
7. Create a BPM in Integration process. Define 3 Containers namely
a) collectIDoc - Abstract Interface - MI_IDoc_ABS
b) collectIDocList - Abstract Interface - MI_IDoc_ABS(Multiline)
c) targetFile - Abstract Interface - MI_EDI810_ABS
8. Create a Block and define a infinite while loop with Block. Condition to be defined as (1=1)
9. Define a deadline block withing Block with duration = 5minutes
10. Define a Correlation in Correlation editor as SNDPOR as a ID.
11. Define a recieve step inside infinite while loop with following properties
Message = collectIDoc
Start Process = Checked
Use Correlation = Correlation
Activate Correlation = Correlation
Correlation
SNDPOR = collectIDoc./INVOIC02/IDOC/EDI_DC40/SNDPOR
12. Define Container operation next to recieve step. properties are
Target = collectIDocList
Operation = Append
expression = collectIDoc
13. Outside the block, there is Transformation Step with following properties
Interface Mapping = IM_EDI810_ABS
Source message = collectIDocList
Target message = targetFile
Acknowledgement = None
Reciever From = Send Context
Now the next step is to define Communication Channel and Receiver determination, Interface determination in the Integration Directory.
I don't know, how to go further on these steps.
In addition, could you please validate my above steps.
I appreciate your help.
Thanks,
Gowri

Hi Bhavesh,
Thanks for the directions and help. I appreciate your help. I understand the steps but i am unable to implement it.
I have few more questions on above answer.
a) Do i have to create Sender Agreement?
b) Do i have to import bmp process in Integration Process in Integration Directory?
The steps that i carried out in Integration Directory.
1. Create a Scenario EDI810_Scenario
2. Create a party called EDI810_Party and EDI810_Service.
3. In EDI810_Service, Receiver tab has interfaces defined. MI_EDI_IN and MI_IDoc_ABS. In sender tab, it is INVOIC.INVOICE02 (IDoc) and MI_EDI810_ABS.
4. Define a receiver communication channel CC_EDI810_Receiver(RFC).
5. Business System for SAP is defined in Service without Party.
6. Defined Sender communication channel CC_IDoc_Sender(IDoc)
7. Create Interface Determination (First)
Properties are
Sender Service : SAP Business System
Sender Interface : INVOIC.INVOICE02 (IDoc)
Sender Namespace : IDoc namespace
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_IDoc_ABS and IM_IDoc_ABS
8. Create Interface Determination Determination (Second)
Properties are
Sender Service : BPM_IP (Bpm process is imported in Integratio directory)
Sender Interface : MI_EDI810_ABS
Receiver Party : EDI810_Party
Receiver Service : EDI810_Service
Configured Inbound Interface is
MI_EDI_IN. I do not see IM_EDI_ABS in the list. How do i get that.
What step did i miss?
Thanks,
Gowri

BPM Abstract Interface for IDOC?

Hi all,
I am doing an IDOC XI File scenario with BPM.
I have created an Inbound Asynchronous and an Abstract Interface for the LEGACY SYSTEM(Target Message).
I didn't create any Abstract interface for the IDOC(Source message).
I am getting this error:
"Expression must return the interface type DEBMAS.DEBMAS06.DEBMAS06".
Do I need to create an Abstarct Interface for the IDOC?
According to the above error, BPM is expecting an ABSTRACT INTERFACE Type for the IDOC.
Experts need help from you.
Thank you,
Joslyn.

That mapping is an dummy mapping between Idoc to Abstract Idoc Type. Here Sender Idoc Interface is mapped with Reciever Abstract Idoc interface.
So inside the BPM, Abstract Idoc interface acts as a Container variable to collect the idocs.
For simplicity-for collection of idocs
You can see, BPMPatterns from the SAP BASIS Software Component in your XI Repository.
http://help.sap.com/saphelp_nw2004s/helpdata/en/08/16163ff8519a06e10000000a114084/frameset.htm
Regards,
Moorthy

Interface of an IDoc

Similar Messages

Maybe you are looking for