IDoc Adapter and Error Management

Hi Experts,
I don't understand tha management of business logic error.
My External System communicate with SAP ERP via SAP PI IDOC Adapter (HTTP protocol, asynchronous mode).
SAP ERP sends an IDOC via PI to my system, my system receives IDoc, an error occurs during business operation in my system.
What should I do?
In my scenario there are not message of error or IDOC to communicate a problem.
Thanks,
Marco Genova
Edited by: m.genova on May 21, 2009 6:41 PM

Hi,
For the same wrong rfc destination i've got
in sxmb_moni : <SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with ARS Name or password is incorrect. Please re-enter FM NLS_GET_LANGU_CP_TAB</SAP:P1>
OR
in sm58 : XIAFUSER IDOC_INBOUND_ASYNCHRONOUS ARS 17.02.2006 15:57:33 Name or password is incorrect. Please re-enter
It's so strange ?
Regards,
Vincent

Similar Messages

Reciever idoc adapter Determination error

Hi,
I have scenario File-XI-R/3.I am using Idoc adapter to send data to R/3.
I am getting Reciever determination error.I have done all the steps according to the below weblog.
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
When I test my steps in configuration with test tool it is succesfull but give me error at runtime.
Below is error description.
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Plz help me out if any one has some idea abt it.
Thanx
Rekha

Hi Rekha,
The End Point Type for your scenario should be an IDoc Adapter with parameters from your RFC destination in SM59.
The most common reason for this error is:
1. An error in configuration of sender adapter/proxy: wrong sender business system or namespace or interface name. Look, all this information you must put manually so be carefull on typos (one wrong or ommited letter and you can spend hours looking what is wrong). Copy (from Repository) and paste procedure is strongly recommended.
2. An error in Directory (Endpoint Configuration). Be careful to specified the correct host and port!!!
Hope this helps.
Regards
Suraj

IDoc Adapter throws error

We are trying to send data to SAPR/3 47 IDES using IDoc Adapter.
the data is sent to XI from SQL database thro JDBC adapter and then to R/3 thro IDoc adapter.
All this is in Asynchronous mode and at no point we chose synchronous (IDoc adapter does not suppost Asynchronous process right).
But we are getting the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>B7685EB2-42F1-554B-80CC-6ADFC86C7975</SAP:MessageId>
<SAP:RefToMessageId>35A42550-81F9-11D9-AFC7-00C09F450580</SAP:RefToMessageId>
<SAP:TimeSent>2005-02-18T22:05:33Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>S70_812</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS04</SAP:Interface>
</SAP:Sender>
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processing</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
We are not sure where from this synchronous is being picked?
Please advise.
Thanks,
Bhaskar and Anil

In the Processing Parameters section of the JDBC adapter, make sure you have Exactly Once (Asynchronous) selected.

IDOC adapter and number of tRFC records

We have idoc inbound scenario file -> XI -> idoc -> R/3.
For each file record an IDOC is created.
Can somebody explain, why only one tRFC record is created containing all IDOCs? Can you influence with interface config how many tRFC records are created? Does settings ' exactly once ' / ' exactly once in order ' have something to do with how many tRFC entries are created?
We faced a situation with our interface scenario that file unexpectedly contained huge number of records causing huge number of idocs generated in XI. However only one tRFC entry was created that contained all idocs. As consequence the receiving system had performance problems and the tRFC call had to be cancelled.
As workaround we splitted the source file in file adapter to interval of 1000recs, thus causing multiple tRFC records created and performance was ok in background system.
Is XI trying to keep IDOCs created out of each incoming message in one "LUW" and send them alltogether in one tRFC call to R/3? Or is there a config parameter that each created IDOC could be sent independent of other idocs still to be created?
br: Kimmo

Kimmo,
There will be one TRFC call per message from XI.
The whole input file is treated as a XI message.
The Receiver IDOC Adapter call the SAP system via ONE TRFC call and posts the message.
By mentioning Exactly Once in the Receiver Idoc Adapter Communication Channel, XI guarantees the delivery of that message.
One way is to split the file into multiple Messages.
You can do this via BPM. But this is not advisable for large files.
We had the same problem for very large files.
We used XI to just pass through the file from Source system and post as file in the Application Server of SAP.
We defined a LSMW project for Periodic Processing, which would take this file and post as Idocs in the SAP System.
Our Scenario
File -> XI -> File.
In the Receiver File Adapter, use the Execute Operating System Command to trigger event sapevt in the SAP system.
You can define events for Background jobs.
So when XI posts the file in the Application server of SAP, XI will trigger the background event defined in the Communication Channel.
The LSMW project which has been scheduled to listen to this background event will kick off.
Hope this helps.

Inbound adapter exception/error management

I was wandering is there any best practice for handling inbound adapter exceptions ? For example if I have inbound MQ-adapter and MQ-server is down how can I get some kind of exception catched from this? Only thing I've found out that it SOA Suite writes these exceptions to server log. Is the only way to catch these exception to poll the server log (using for example grep...)?
Thank you
Best Regards Tuomas

Any light / idea on the following issue ?
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

Difference between Idoc Adapter and Proxies..

HI XI Guru's,
I am new to XI, I wanted to know what is the difference between Idoc adpater and proxies. When and what should be preffered ?
Warm Regards,
- Priya R

idocs which mean - (intermediate documents) are standard document formats which sap systems use to store as well send data from one system to another. If this is the format in which data has to received by R/3 then you will use idoc adapter in XI. idoc adapter can be used to communicate between systems is with SAP release higher than 3.1.X. Communication using idoc adapter is always asynchronous.
proxies are available for communication between SAP systems with version WAS 6.20 and above. They support both synchronous as well as asynchronous modes of communication. Generally when you are looking at developing new application using WAS 6.20 and above then you can design the interfaces for this new applications in SAP XI and generate the required code for these interfaces automatically in SAP systems using transaction code - SPROXY in the case of ABAP Proxy and in the case of Java proxies the code is generated by SAP XI system itself. You only have to implement these interfaces in your new application. So, basically you have to only worry about building the application and the interface part is taken care by XI itself. you can also look at using proxies when data has to be inserted or fetched from custom/standard tables in R/3 using XI.
,idoc adapter can be used for commuincation between ABAP stacks only but Proxy can be used for both ABAP as well JAVA stack.

IDOC ADAPTER , ATTRIBUTE_IDOC_METADATA Error

Hi everyone!
XI have sent Idoc to SAP A5P.
But there is an error log,
"IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA
> Metadata EDISDEF for port SAPA5P, IDoc type ORDERS02 and CIM type ZORDERS2 not maintained
Kindly advise what is wrong with our configurations.
Thank you very much!
Fred

hi,
Your error is IDOC metadata related
(probably incorrect entry in IDX1 - or RFC to R3 is ont working)
download your idoc in IDX2 to check it
Also check if you are using the right port in IDX1.
else,
Goto ID and open the relevant Business system.
Goto --->Menu tab "Service" --->Adapter Specific Identifiers.
Check if the proper logical system details have provided.
Refer
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
SAP Network Blog: Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Thanks
Swarup

ESB DB adapter and error logging

Hi !
I need a DB adapter in ESB to read records from a table and do a logical delete (update a status column) .
I can get it to work om my laptop, but not in our dev machines.
I noticed that if I change the the 'mcf-properties' in the wsdl-file for the READ function like this
mcf.DriverClassName="oracle.jdbc.OracleDriver" mcf.PlatformClassName="oracle.toplink.platform.database.oracle.Oracle10Platform"
mcf.ConnectionString="jdbc:oracle:thin:@localhost:1521:ORCLAAAAAA"
mcf.UserName="soatest" mcf.Password="A932C53E63FFDE3D4A8267B2FCE4A0044C1B70BFD42DD194"
so that is wrong I never get any error in any log-file I found.
This makes is very tiresome to debug.
Is there a log where I can find an error message ?
If not , what should I do ?

Hello Everyone,
I am stuck with the ESB's "logging" behavior. Due to some problems we had increased the Logging level to FINEST for some and as a result there were too many messages - mainly "Traces" -generated in /../oc4j/log.xml Now the problem is that i am seeing that ESB maintains only 10 to 12 log files.
My query is does it archives the older log files somewhere- if yes then which location?
-Or does it simply overwrites the files (that doesnt seems likely)?
For example: While searching the OC4J Diagnostic Logs from Enterprise Manager Console it is showing that there are 10 selected log files.
But where are the older log files. We need those badly as there are some issues we are trying to fix hinged on the Error Messages.
Thanks
--debashis

IDOC Adapter and RFC Adapter

Hi experts,
Q1. What are the configurations steps (Transaction codes) required at R/3 and XI while sending the IDOC to XI? Please provide the list of TCodes required at both sides. if any weblog is exists which provides detail explanation on IDOC scenarios plz provide the path.
Q2. While sending the IDOC we need to generate partner profile and port. How many types of port exist and wht each port represents?
Q3. In RFC Sender Adapter we need to create RFC port in R/3 and there we specify Connection type as T which TCP/IPwhy we use connection type T instead of 3 (which represents connection type as R/3). While communicating with SAP systems we need to specify the connection type as 3.
Q4. How many types of partner profiles exist and wht each type represents?
Q5. How to transport design, configuration objects and SLD objects from Development system to Quality system. Please provide me the steps to transport the objects?
Q6. Once the objects are transported a .tpz file is created wht is the purpose of the file and where it will generated? Suppose if Ive transported the namespace from Dev to Quality system then at quality side to which SWC this transported namespace is assigned. Do we need to create any SWC at quality system side?
Cheers
Faisal

Hi Abdul,
for the first one u need to create a logical system and assign that logical system and need to create a port and partner profile and distribute the system,, for that follow this blog
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
2.& 3 ) for the 2nd question the answer was in above u need to create the partner profile and port.
port can be created as HTTP Port and RFC port which are used to communicate with the R/3 server and depends on the requirement we need to choose the port..
4. partner profile creation depends on ur scenario, it is a custmized one it purely depends on the customer requirement, there is no specific partner profiles exists in R/3.
5. For transportation u may choose File level transport or CMS, if u trnasfer through File level it is very easy to maintain and reimport in the production server,, just while exporting from the development server a .TPZ file was created and import this .TPZ file in the production server this gives the entire objects of IR and ID, but when u deal with SLD instead of .tpz there u will be creating .zip file, so u neeed to reimport the file in the production server..
6. The .TPZ file will be created when u export the objects either in IR and ID..., so as i explained in the above point it will go top the export directory of development server and import in production server with IMPORT directory..
regards,
Kishore

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

>so i cant use apply control rec values from payload.........
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

XI and IDOC-Adapter / Restriction to certain IDOC Types?

Hi all!
We have some problems in trying to enable our XI systems for using our central user administration. The reason for that is that the "USERCLONE", ... IDOCs sent to XI by the CUA system are not processed normally in the ALE Layer but XI tries to process it through it's IDOC Adapter hence wants to route the IDOCs through the Integration Engine.
Is there a way to define the IDOC-Types to be processed by the IDOC-Adapter and to exclude certain IDOC types such that those are processed via standard ALE?
Many thanks in advance for any input you can give ...
Andy

Hi all!
For those who are interested - we have found the solution for this problem using some debugging
There is an "excemption table" where you can define required IDOC Types that should be processed via the normal ALE layer (instead of routing it through the IE).
To maintain the table entries you have to use report
"IDX_SELECT_IDOCTYP_WITHOUT_IS".
However - if you want to get rid of entries already made
with this report just have a look at note "790175"
Best regards,
Andy

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Configuration Problem on IDOC Adapter

Hi,
I am trying to configure the IDOC Adapter and am badly stuck.
On the sender system: I have configured
-RFC destination, ports and partner profile.
- I have also configured the SLD as per documentation
On the Integration Server:
-RFC Destination, Port maintanence(IDX1.
- Imported Metadata (IDX2)
My IDOC is getting created and is being sent properly, I can see that in WE02
But I cannot see it in Integration Server using transaction IDX5.
Please help.
Regards
Ramesh

Ramesh,
Try to refresh the cache
in Xi using transaction SXI_CACHE > delta Cache refresh.
Then go to Integration Server and Environment Cache Notifications.
Status should be green once you refresh the cache.
This may look a bit silly, but it worked for us.
(We used to get errors with SXI_CACHE in XI3 Service pack 9. Then we followed the steps of Checking Instalaltion part 1 as in XI3 install guide. Once we repeated these steps . SXI_CACHE worked and everything was fine).
To find what exacly is happening, try to send the IDoc from one R/3 to anotehr thro Xi.
The other R/3 will tell you the errors even if it does not show up in SXMB_MONI.
Hope this helps.
Thanks,
BG
Message was edited by: Bhaskar Ghandikota

Difference In RFC Adapter and XI proxy

I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
Thanking you
sridhar

Hi,
Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.
In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
RFC Adapter :
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
For FAQs about the RFC adapter, see SAP Note 730870
The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
The RFC adapter maps the following RFC calls to XML messages and the other way around:
Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
●     Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
●     The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
You require the sender adapter if you want to use the Integration Engine or the PCK to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine or the PCK.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
Proxy :
Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
·        Interfaces designed for message exchange between application systems
·        Interfaces used by a cross-component integration process to receive or send messages, or both
Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
Interfaces are an essential component of SAP Exchange Infrastructure:
·        You define the interfaces to be used in an integration scenario.
·        Cross-component integration processes use interfaces to exchange messages.
·        You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
·        You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
·        You generate proxies to implement your scenario based on message interfaces.
You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

Meta data Overview for Idoc Adapter

Hi All,
When i am trying to create meta data overivew for Idoc adpater of my source port, i am gettign this error "Error: I::000" and surprising abt this error.Any clues on this.........:) what should i do to do this??
Thanks in Advance
Cheers
Veera

Hi All,
Once i have cross check RFC destination & Port and tried to load the meta data it was succesfully loded with out ant errors.The same port i have mention in Receivr Idoc adapter and tested the sceanrio File2Idoc.It is working fine.
I have solved the problem my own ( And the tricky thing is i have deleted and recreated RFC dest,Port from XI to R3).However what is the cause of this error??
Cheers
Veera

IDoc Adapter and Error Management

Similar Messages

Maybe you are looking for