Documentation for Integration Repository Interfaces

[Former Member]

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

[Former Member · Accepted solution]

Hi Mark,

Normally you can find the documentation in the R/3 System. not sure about other on-line sources.

you can also download these BAPIs to your IR, but if you need the WSDL/XML of these BAPIs, I can mail you. let me know ur mail id.

Regards

Vishnu

[Former Member · Accepted solution]

Vishnu,

My email is mark@javector.com.

I would greatly appreciate it if you could email me the WSDL/XML of these BAPIs. I do not have access to an R/3 System.

Thanks a million!

-- Mark

[Former Member · Accepted solution]

Hi Mark,

Sent you the mail with the required BAPI WSDLs.

Regards

Vishnu

[Former Member · Accepted solution]

Thanks.

I notice that the <wsdl:binding ...> uses a non-soap binding:

<rfc:binding style="rfc" xmlns:rfc="urn:sap-com:document:sap:rfc:functions" />

What is this rfc:binding? Is it a SAP standard for invoking BAPIs? Does SAP provide a traditional SOAP binding for BAPIs?

-- Mark

[Former Member · Accepted solution]

Hi Mark,

This is the structure, what you get when you import your BAPIs (from R/3) to your XI system IR.

This is used as msg types, when you configure the interfaces in the IR. all information in that system generated, so SAP specific. In a way these are realted with invoking of BAPIs.

Regards

Vishnu

[Former Member · Accepted solution]

OK - do you know if it is possible to get a standard SOAP binding for a BAPI?

[Former Member · Accepted solution]

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