Integration Repository Interfaces - Documentation??

I'm looking for an on-line source for the integration respository interfaces - similar to the now deprecated Interface Repository (IFR)(http://ifr.sap.com).
In particular, I'm looking for the WSDL/XML and Java Proxy interfaces for the following BAPIs.
- BAPI_CUSTOMER_GETDETAIL or BAPI_CUSTOMER_GETDETAIL1
- BAPI_CUSTOMER_CHANGEFROMDATA
- BAPI_SALESORDER_GETSTATUS
- BAPI_SALESORDER_CHANGE
Does anybody know if those interfaces are available online anyplace?
Thanks,
Mark

Gregor,
Thanks. That is what I was looking for. Unfortunately, it seems to be password protected.
I'm trying to view the StandardSalesOrderChangeRequestResponse service here -> https://www.sdn.sap.com/irj/sdn/esapreviewsystem and when I select "Inbound Interface WSDL" or "Inbound Interface Documentation", I get hit with a logon screen.
Ny SDN username/pwd doesn't work. Is there a guest username/pwd that can be used?
-- Mark

Similar Messages

Documentation for Integration Repository Interfaces

I'm looking for an on-line source for the integration respository interfaces - similar to the now deprecated Interface Repository (IFR)(http://ifr.sap.com).
In particular, I'm looking for the WSDL/XML and Java Proxy interfaces for the following BAPIs.
- BAPI_CUSTOMER_GETDETAIL or BAPI_CUSTOMER_GETDETAIL1
- BAPI_CUSTOMER_CHANGEFROMDATA
- BAPI_SALESORDER_GETSTATUS
- BAPI_SALESORDER_CHANGE
Does anybody know if those interfaces are available online anyplace?
Thanks,
Mark

Hi Mark,
"Standard SOAP binding for BAPI - I dont think so."
more explanation.
with your queries, I assume that you want to expose your BAPIs as webservices or to put it in other way, you need the below,
(some Webservice)<> XI <> BAPI
If this is the case, then you may need to replicate the XSDs (which you can find embedded in the WSDL of BAPIs) and have them as external definitions in your IR.
Now with oneend as ur ext defn & other as BAPI, you need to do a ONE-to-ONE mapping (this is logically not required, but it is essential for XI to invoke BAPIs, by doing this you would avoid the unwanted Namespaces because of which the XI errs out).
Now once you developed all the interfaces and necessary configurations in ID (Int Dir), you can use the tools menu to define a webservice.
This is the actual WSDL, which would contain an end to end call. this WSDL can be esposed to any partner to hit your XI (and the R/3) as a webservice call. so they can use it from any websevice client.
Regards
Vishnu

LinkageError at Interface Mapping in Integration Repository

Hello,
I have created interface Mapping and when I test them in Integration repository, it gives the following error.
Please can anyone suggest on the same.
Thanks
vijaya
Messages:11:53:40 Start of Test
- LinkageError at JavaMapping.load(): Could not load class: com/sap/xi/tf/_MM_Material_
- java.lang.NoClassDefFoundError: Illegal name: com/sap/xi/tf/_MM_Material_
     at java.lang.ClassLoader.defineClass(ClassLoader.java:538)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:448)
     at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingLoader.findClass(RepMappingLoader.java:173)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
     at com.sap.aii.ibrep.server.mapping.ibrun.RepJavaMapping.load(RepJavaMapping.java:130)
     at com.sap.aii.ibrep.server.mapping.ibrun.RepJavaMapping.execute(RepJavaMapping.java:49)
     at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:75)
     at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:110)
     at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:141)
     at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:120)
     at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:51)
     at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:305)
     at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:266)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:292)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:118)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:144)
11:53:40 End of Test

Hello Homiar,
Thanks for the Reply.
I am on SAP J2EE Engine/6.30.
Also, I a using j2re1.4.2_05 and j2sdk1.4.2_05. But I am still having the same error.
The above Java versions are on my m/c. Should the Java runtime on server also should be the same.
Please suggest.
PS: I am putting the same reply on my initial Query also. If u need to reply to that linkage, you can select the hyperlink above the message saying 'Reply to the message'
thanks
Vijaya

Import of SAP Objects into Integration Repository in XI 3.0

Hi all,
I am not able to import SAP objects into the Integration Repository in XI 3.0. This option is under any Software Component Version. I have selected the radio button "Import of RFC and IDoc interfaces from SAP systems permitted", in the Software Component Version settings. After the connection data is specified for the SAP system nothing appears under the IDoc, Whereas the import of RFCs is successfull.
We also have another installation of SAP XI 3.0, here this option is working properly. Can anyone tell me what is the problem, is is there something else to be configured inorder to do this.
Best regards,
Norway

Hi Stephan
Thank you for your answer. We have followed your instructions but did only get half a success. Here is what we have done:
1) Created "External Definitions" for all related xsd-files with the same name as the xsd-filename and in our own namespace. Our namespace is different from those specified in the xsd-files. We have not change the namespaces in the xsd-files.
2) Maintained the "source"-field with the name for the xsd-file and not the url as specified in our answer. When we used the filename only we got a value the field "name" in the "External References".
3) We made a message mapping and imported the "top-level-xsd-element" from the "External Definition". This resulted in only the top level element and nothing else. What we expected was the possibility to drill down through the complete structure.
What did we doe wrong? Perhaps I could talk you into spending 10 min. and try it your self? This url leads to a zip file with all the related xsd files: http://rep.oio.dk/ubl/xml/schemas/0p71/documentation/resources.html
Do you know if it will be possible to make references across namespaces in a later version of XI?
Regards
Christian

How to create abapProxy in nw 7.01 not 7.1 from integration repository

i use nw 7.01 , it's sproxy inteface is different old and new ones like 7.1 so i couldnt create abap proxy in sproxy.I created an message interface in integration repository but i couldnt find any object releated to this in sproxy..
I found some documentation about 7.1 , it mentions that you must create a service interface in IR but in my version it doesnt exist.
so how to create or copy existing proxy class?
Thanks alot

I guess it should be similar to PI 7.0 environment wherein you have to create message interface in IR. Then use SPROXY transaction at R3 (not XI). From there you may select the interface and create proxy. For this make sure that abap proxy is activated at your R3 system.
Regards,
Prateek

Manufacturing Interfaces documentation in R12

Hi,
For manufacturing interfaces, is the documentation in 11i still valid for R12? If not, where can I find it? I checked the doc library CD for R12 and couldn't find the 'Manufacturing Open Interfaces Guide', as it was in 11i.

Hi,
Refer to the latest version of the 11i Oracle Manufacturing APIs and Open Interfaces Manual for complete documentation on the Purchasing APIs and Open Interfaces and refer (Note: 437587.1 - Release 12 Oracle Purchasing API and Open Interface Changes) for the change made in Release 12.
You can also refer to "Oracle Integration Repository" which comes with R12 as a responsibility.
Regards,
Hussein

Open Interfaces Documentation

Hi
I need to get the list of Open Interfaces dynamically using certain API.
Can you provide any documentation for this.
Where is the documentation of Oracle Integration Repository available,
Thanks

That is the correct API, but I have never seen any documentation. I would avoid it for R12 based on Metalink Doc 7018312. Maybe OK in R12.1?
I'm often amazed at how much work goes into the Projects API's, yet so much goes undocumented!
Also see: PA_CONTROL_API_PUB

Integration Repository objects

Is it possible to store Integration Repository objects (Data Types,Message Types,Message Interfaces,Message Mappings and Interface Mappings) separately in the repository like (VSS ,CVS etc,.).Some times it will be helpful to merge specific versions of the objects and activate.If i am not wrong i can only see exporting IR objects as a whole and store in the repository.

Hi Anand,
I dont have a exct answer for it but i can give you a solution.....
the thing is you can export your datatype as XSD and save that XSD at your coninient path.....so once your are in need of datatype you just import that XSD so you can see your datatype there..............so once you have your datatype i dont think it will take much of time to build IR Objects other than Mapping....this too can be solve if you use Java or XSLT Mapping...just have a copy of your pgm in local so that you can make use of it wherever you want ....hope this simplifies your task...f you feel im wrong kindly inform me...
Cheers,
Sundararamaprasad

User roles in Integration Repository

Hi everybody,
does anybody have experience with user roles in XI 3.0? We want to limit access to various namespaces in the Integration Repository with use of these roles that can be created in the IR. That way, various XI developers working on the same XI-Repository should not be able to work in the namespaces of other developers.
We created the role in the IR and assigned it to a user in the J2EE Engine. But so far, it doesn't seem to work.
Am I missing something??
Thanks a lot,
Francis Wolf

Hi,
it looks like the integration to the "abap" backend (=IS-Server) is missing.
J2EE-R3 integration regards user management maps R3 roles onto J2EE user groups. Thus, if the term "role" is used in R3 context, it has to be translated to "user group" in J2EE.
Next steps:
1. Create user in "R3", with transaction SU01.
2. In "R3", create a role with transaction PFCG
3. UME Admin WebApp: assign role to user group
4. XI Exchange Profile WebApp: activate data-dependent authorization checks. Put: com.sap.aii.util.server.auth.activation" in section "IntegrationBuilder.Repository" to true
Please check the documentation on Netweaver security and Integration of UME Roles with SAP Roles
Hope that gives an idea!
Good luck
Holger

Not able to see "External Definitions" in Integration Repository

Hi Experts,
I am working on PI 7.1.
In the Integration Repository Menu :
SAP Basis --->SAP Basis 7.10 ->http://sap.com/xi/XI/System ->
"Service Interfaces",
"Message Types"
"Fault Message Types",
"Data Types",
"Adapter Metadata"
only are visible.
We need the "External Definitions". Is it not available in the standard SAP PI 7.1 ?
Do we have to import it explicitly?
Kindly advice.
Thanks in advance
~ Suraj

Hey NM,
Thanks a lot for your suggestion. problem got resolved when i did what you said (checking the attributes with developers user id's)
Thanks
Sourav

Does EBS Integration Repository has API capability or Export facility?

Now looking into the Integration repository in V12 from the perspective of application integration. Is is possible to interrogate the repository from an outside program using APIs? Or is the repository only meant to to be a browser within the Oracle Apps environment? It would be very useful to have the API capability so that the discovery, import and mapping activities to the V12 integration objects (interface tables, stored procedures, concurrent program,..) can be performed from an integration program.
If the repository is only a browser and does not expose a queryable API, is there an export facility so that could be exported a whole set of interface metadata and import that into an external integration application?
Edited by: Patty on Nov 9, 2008 5:39 AM
Edited by: Patty on Nov 9, 2008 5:44 AM

Hi Srini,
Thanks for your attention to my question.
As we know, Oracle Integration Repository provides a complete catalog of Oracle E-Business Suite's business service interfaces. One of our applications needs to integrate with Oracle E-Business Suite. That means we need to get all the business service interfaces through IRep. Is there are APIs can be called from integration applications, or IRep metadata can be exported, we can easily implement integration with Oracle E-Business Suite.
Hopefully you can give me some suggestions or information. Thanks.

Basic Dought.. In Integration Repository

Hi All,
Any body Explain me the below topics
Integration Scenario & Integration Process
 - Integration Scenarios,
 - Action,
 - Integration Processes,
Interface object
1. message Interfaces
2. message type
3. fault message types
4. data types
- exchangefaultdata
- exchangeLogData
5. Datatype Enhancements
6. Context Objects
7. External Definitions
Mapping Objects
- Interface Mapping
- Message Mapping
- Mapping Templates
- Imported Archives
Adapter Objects- Adapter Metadata
- Communication Channel Template
This information very use full to me
Thanks & Regards

Hi,
I have taken some time off for you and have given the best possible explanation for the doubts you have.
Integration Scenarios:
An integration scenario completely models the exchange of
messages for a collaborative process and provides an overview of the process flow.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/ec/21ee117a909f44a8b69794b9ed6221/frameset.htm
Integration Processes
An integration process is an executable, cross-system process for processing messages. In an integration process you define all the process steps that are to be executed and the parameters relevant for controlling the process.
You implement integration processes when you want to define, control, and monitor complex integration processes that extend across enterprise and application boundaries. The design and processing of integration processes is also known as cross-component Business Process Management (cross-component BPM, ccBPM).
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f7/d4653fd1d3b81ae10000000a114084/frameset.htm

Interface object
1. message Interfaces
ou use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/55/c5633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/06/1522417c22f323e10000000a155106/frameset.htm

2. message type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e7/7356405aff1e24e10000000a1550b0/frameset.htm

3. fault message types
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
4. data types
A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a5/04623c4f69b712e10000000a114084/frameset.htm
exchangefaultdata and exchangeLogData
All fault message types reference the data type ExchangeFaultData for this part and, indirectly, the data type ExchangeLogData. These data types are automatically created in a namespace when you create the first fault message type there.

5. Datatype Enhancements
SAP applications enable customers to enhance application source code without making modifications and thus to meet customer-specific requirements that are not provided for in the standard shipment. The applications can use Business Add-Ins (BAdIs) for this purpose. Furthermore, if customers use applications that exchange messages by using XI, they can define data type enhancements for Integration Repository data types.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/a8/bfc6373c8fea43bdb3541535bcbd43/frameset.htm
6. Context Objects
Context objects are a simple alternative to XPath expressions for accessing the contents of a message.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/frameset.htm

7. External Definitions
External definitions enable you to import WSDL, XSD, and DTD documents to the Integration Repository so that you can access the message definitions they contain as external messages.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/frameset.htm
Mapping Objects

Interface Mapping
Interface mappings register your mapping program for an interface pair in the Integration Repository.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/4f/ef761a5ecfb1418b79896e10fe4c57/frameset.htm

Message Mapping
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/d9/cea942ad920c31e10000000a1550b0/frameset.htm

Mapping Templates
Just like you can reuse data types in different message types, you can also save parts of message mappings as Mapping Templates and reuse them elsewhere. Once you have saved a mapping template it serves as a copy template that you can then load into other message mappings and modify to fit your requirements.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/79/2835b7848c458bb42cf8de0bcc1ace/frameset.htm
Adapter Objects
Adapter Metadata
With adapter metadata you can define configuration data needed for a certain type of adapter at design time. Adapter metadata define the part of a communication channel that is specific to the adapter type.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/12/f9bb2fe604a94cbcb4c50dc510b799/frameset.htm
Communication Channel Template
You can preconfigure a communication channel with a communication channel template. You can use the communication channel template as a template to define a communication channel at configuration time.
Please go through this link for further reference:
http://help.sap.com/saphelp_nw04/helpdata/en/bd/6af766076e384ebdce621d25161184/frameset.htm
I am sure i have clearly explained your doubts.
Regards,
Abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

Mapping edited in Integration repository

Hi
can anyone let me know which all mappings are edited in integration repository
regards
jm

Hi,
XSLT is eidtable in IR. The restriction is that the XSLT Structure has to be defined extrernly , jar created and uploaded in Xi. Import as Archive.
The value -of Statements ( selects in XSLTs) can change in XI.
Java : Develop you code using Eclipse of NWDI.
Implement the stream Transformation interface.
Create a JAR
Import as Archive.
Hope this clarifies the Doubt.
Regards
Abhishek

Integration Repository: change XSD type in data types

Hi,
we created data types for our interface where we used the XSD type float and integer. We built on that Message types and Message interfaces and used them as abstract types in a BPM scenario.
During our test phase we encountered errors with these XSD types and found out that it is better to switch the XSD type to string to get correct values.
However the changes in XSD types are obviously only visible in the Integration Repository. XI creates on Application Server side in the XML Object Type Builder an object which doesn't notice this change. And because of that we get still errors.
So does anyone know how to get this XML Object Type changed? We don't want to delete everything and create new message types?
Thanks in advance,
Christina

Hi Christina,
First go to SXI_CACHE -> Refresh the cache.
Also check for the Repository Cache Refresh/Notifciations..
You mean you have changed the xsd in the External Definition ...
If so , just go to Message Interfaces and just select the External definition once again and activate the same.
If you change the Data types then , if there is a change in field length/type then try to redo/reselect the datat types for the message types and activate once again.
For BPM just change something.. and activate once again..
Also check this blog- to activate Runtime version of the BPM
/people/krishna.moorthyp/blog/2005/11/28/inactive-integration-process-ip-at-run-time
Hope this helps,
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

XI: new termonologies in Integration Repository "operation" "action"

Hi Friends,
Can anyone tell me how new concepts within integration repository like "actions" "operation" are mapped to old way of "message interface" etc.
Thanks in advance,
Regards,
Ujwal

Hi,
"Message Operation" is old "Message Type" and "Action" is used in integration process or BPM and it is depicted by Service Interface (http://help.sap.com/saphelp_nwpi711/helpdata/en/2b/cd6a8bceed26469f3b0952a030c711/content.htm).
The difference b/w old and new PI is about webservice methods. In old PI (XI3.0 and PI7.0) one message interface can have only one message type which means one webservice with one method only, which is not real world depiction of webservices.
That's why in PI7.1 you can have multiple methods per webservice i.e. multiple operations per service interface.
Regards,
Gourav
PS: For other meaning of Action see RNIF adapters.

Integration Repository Interfaces - Documentation??

Similar Messages

Maybe you are looking for