Skip Headers

Oracle E-Business Suite Integrated SOA Gateway User's Guide
Release 12.1
Part Number E12064-06
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Working with Native Services and Integration Interfaces

This chapter covers the following topics:

Common Information

The details page of each integration interface type contains the following two types of information:

Interface Details Page

the picture is described in the document text

Each interface details page also includes Search and Printable Page allowing you to perform a search or view the details page of a selected interface in a printable format if you want. See Searching for an Integration Interface for details.

Important: Information specific to Web services is discussed under Understanding Service Enablement.

Information specific to composite services is discussed under Working with Composite Services.

Common Information on Interface Details

Each interface information page includes a header region with general information about the interface. The following fields are common to almost all interface types:

Field Notes
Internal Name This is the PL/SQL package name, the document name, or the Java service interface name.

Note: For Java service interfaces, this is called Qualified Name, and includes the full Java package name and the class name.

Type The interface type.

Note: This field does not appear for Java service interfaces.

Product The Oracle E-Business Suite product that supplies the interface.
Business Entity Business entities are objects that either perform business activities or have business activities performed on them. For example, sales orders, account numbers, employees, purchase orders, customers, and receipts are all business entities. An interface can be used by multiple business entities, and a business entity can be accessed using multiple interfaces.
The Business Entity field lists the business entities accessed by an interface. Click a business entity name to view a list of available interfaces to that entity.

Note: This field does not appear for Java service interfaces.

Status Valid status codes are:
  • Active

  • Deprecated - this interface should not be used, but it will be supported until obsolete.

  • Obsolete - the interface is no longer supported.

  • Planned - This interface will be activated at a future date.

Scope The scope can be one of the following:
  • Public

  • Internal To Oracle

  • Private To Application


For more information, see Scope on the Oracle Integration Repository Search page.
Interface Source The only available interface source in Oracle Integration Repository is Oracle native packaged integration interfaces.
Interface Source on the Oracle Integration Repository Search page.
MetaLink Included for any interface that has a related My Oracle Support (formerly OracleMetaLink) Knowledge Document. Click the link to log in to My Oracle Support and view the Knowledge Document. A valid user name and password is required to access My Oracle Support.
Documentation Included for any interface that has related online documentation. Click the link to view or download the documentation.
Online Help Provided for any interface that has related Oracle E-Business Suite online help. Click the link to view online help for the interface.

Each interface information page also includes a Source Information region that contains the following fields:

Field Notes
Source File The source code file for this interface, and its location in the file system.
Source Version The version of the source file. The first portion of the number corresponds to the base release version of Oracle E-Business Suite and the second portion is the version of the file. For example, 120.8 is Oracle E-Business Suite 12.0, and 8 indicates that this is the 8th version of the file.

Note: The version number changes only when it has been worked on by Oracle development. Therefore the version may increment multiple times between releases, or not at all.

Source Product The product code of the source product. The source product specifies under which product directory the file resides in the Oracle E-Business Suite file system (also referred to as the product top).

Tip: This field shows the product shortname. You can learn the corresponding full product name by choosing the System Administration responsibility from the Navigator menu, then selecting Oracle Applications Manager > License Manager > Reports > Licensed Products. On the product list that appears, you can filter the results for any product abbreviation (shortname) or license status.

Integration repository administrators or only users granted with the integration repository administrator role can find the following buttons available in the interface details page:

the picture is described in the document text

Note: The integration repository administrators (defined by the Integration Repository Administrator role) can find the Administration tab containing the following information displayed next to the Integration Repository tab:

Common Information on Web Services

Web service information is displayed in the appropriate Web Service region of the interface details page.

For example, the Web Service - SOA Provider region by default appears in the details page if the selected interface type is not Business Service Object. This region allows you to review a Web service details in WSDL code, and allows the administrators (or users granted with the integration repository administrator role) to perform administrative tasks including deploying or undeploying Web services.

Note: XML Gateway Map and Business Service Object (formerly known as Service Bean) interface types are service enabled in Release 12.0 through Web Service Provider. To enable services for more interface types, SOA Provider is used in this release to support XML Gateway Map, plus additional interface types including PL/SQL, Concurrent Program, Business Event, and Composite Service - BPEL types. Therefore, you might still find Web Service - SOA Provider region available for XML Gateway Map interface type if the service is enabled by SOA Provider in this release.

Web Service Region(s) for XML Gateway Map and Business Service Object

From the appropriate Web service region, you can perform the following tasks:

Reviewing Web Service WSDL Sources

To make integration interfaces available to customers over a network where customers can dynamically interact between applications, Oracle Integration Repository allows integration repository administrators (or users granted with the integration repository administrator role) to generate Web services WSDL files.

Once Web services are generated, you will find the appropriate Web Services region(s) available when viewing an interface detail for a given interface type.

Viewing Web Service WSDL Information

the picture is described in the document text

To view WSDL file:

  1. Log on to Oracle Integration Repository and locate your desired interface definition through a search or from the navigation tree.

  2. Click the interface name to open the interface details.

  3. Click the View WSDL link in the Web Service region to view the WSDL source code.

    The following sample shows the WSDL description for the PLSQL Interface: Repair Order:

    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="CSD_REPAIRS_PUB" 
    targetNamespace="http://xmlns.oracle.com/apps/csd/soaprovider/plsql/csd_repairs_pub/"
      xmlns="http://xmlns.oracle.com/apps/csd/soaprovider/plsql/csd_repairs_pub/"
      xmlns="http://schemas.xmlsoap.org/wsdl/" 
      xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
      xmlns:tns1="http://xmlns.oracle.com/apps/csd/soaprovider/plsql/csd_repairs_pub/create_repair_order/"
      xmlns:tns2="http://xmlns.oracle.com/apps/csd/soaprovider/plsql/csd_repairs_pub/update_ro_status/">>
    <types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
     targetNamespace="http://xmlns.oracle.com/apps/csd/soaprovider/plsql/csd_repairs_pub/create_repair_order/">
     <include schemaLocation="http://<myhost>:<port>/webservices/SOAProvider/plsql/csd_repairs_pub/APPS_ISG_CREATE_REPAIR_ORDER_CSD_REPAIRS_PUB-24CREATE_REPAIR.xsd"/>
    </schema> 
    <schema xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
     targetNamespace="http://xmlns.oracle.com/apps/csd/soaprovider/plsql/csd_repairs_pub/update_ro_status/">
     <include schemaLocation="http://<myhost>:<port>/webservices/SOAProvider/plsql/csd_repairs_pub/APPS_ISG_UPDATE_RO_STATUS_CSD_REPAIRS_PUB-24UPDATE_RO_STA.xsd"/> 
     </schema> 
    <schema xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
     targetNamespace="http://xmlns.oracle.com/apps/csd/soaprovider/plsql/csd_repairs_pub/">
      <element name="SOAHeader">
        <complexType>
          <sequence>
          	<element name="Responsibility" minOccurs="0" type="string" /> 
           <element name="RespApplication" minOccurs="0" type="string" /> 
           <element name="SecurityGroup" minOccurs="0" type="string" /> 
           <element name="NLSLanguage" minOccurs="0" type="string" /> 
           <element name="Org_Id" minOccurs="0" type="string" /> 
         </sequence>
       </complexType>
      </element>
     </schema>
    </type>
       . . .

    Note: Values passed in the Responsibility, Responsibility Application, Security Group, NLS Language, and Organization ID complex types listed under the "SOAHeader" are used to set applications context during service execution.

    Please note that NLS Language and Organization ID are optional values to be passed. However, if the execution of a service is dependent on any particular organization, then you must pass the ORG_ID element in the "SOAHeader" of that SOAP request.

    For more information, see Setting Other Web Service Input Message Parts, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

    Please note that the user information is defined by the wsseUsername property passed within the security headers. Detailed instructions on how to pass the security headers along with the SOAP request, see Passing Values to Security Headers, Oracle E-Business Suite Integrated SOA Gateway Developer's Guide.

    For more WSDL element information, see Reviewing WSDL Element Details, Oracle E-Business Suite Integrated SOA Gateway Developer's Guide.

To view a deployed WSDL file:

When an integration repository administrator successfully deploys or redeploys a Web service, the Web Service Status field appears with 'Deployed' value along with selected authentication type(s). A deployed WSDL link also appears confirming that the service has been successfully deployed.

Click the View WSDL link to view the deployed WSDL file.

Performing Additional Web Service Activities

Oracle E-Business Suite Integrated SOA Gateway allows integration repository administrators to perform the following tasks:

For more administrative tasks, see Oracle E-Business Suite Integrated SOA Gateway Implementation Guide for details.

Managing Grants

Only integration repository administrators (or users granted with the integration repository administrator role) can create security grants by authorizing the access permission of a selected interface method or procedure and function to an appropriate user, user group, or all users.

Note: Interface types that have the security grant feature available are PL/SQL, Concurrent Program, Business Event, Business Service Object, and Java interfaces.

Oracle Integration Repository also allows the administrators to revoke the grants for a particular user on a selected event or service.

To create a grant

In the interface details page, select appropriate method name check boxes in the Methods region or appropriate procedure and function names in the Procedures and Functions region. Click Create Grant to open the Create Grants page.

Create Grants

the picture is described in the document text

Note: Each of the overloaded function contained in an interface can be uniquely granted to a specific user, user group, or all users through the create grant feature. If you select more than one overloaded function, an Overloaded column appears in the selected methods table indicating more than one overloaded function is selected for the grant.

From here, you can select a grantee type and grantee name if applicable and click Apply.

To revoke a grant

In the interface details page, select the Show link for the method or procedure and function that you want to view or revoke the grant. The Grant Details section of the selected method or procedure and function name appears detailing the grantee and grantee type information. Click the Revoke icon for the grant that you want to revoke to revoke the grant.

Note: To create and revoke grants, you must log on to Oracle Integration Repository through the username granted with the integration repository administrator role.

For more information on security grants, see Managing Security Grants, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

XML Gateway Map Information

The following diagram illustrates the basic structure of the XML Gateway Map information page and its connections to related pages:

the picture is described in the document text

The XML Gateway Map information page contains the following information:

The general section of the XML Gateway Map displays common information.

The information page or interface details page includes a table listing the XML Gateway methods. Click a method name to access the information page for that method.

XML Gateway Map Web Service Region

To support the XML Gateway Map service enabled by Web Service Provider in Release 12.0 and to differentiate the service enablement by SOA Provider in this release, Oracle E-Business Suite Integrated SOA Gateway uses the following profile option to let you select an appropriate service provider in enabling services for XML Gateway Map interface type. Based on the selected profile value, the interface details page displays an appropriate Web Service region or more than one region.

Select one of the following values to define the FND: XML Gateway Map Service Provider profile option:

For more profile option information used in Oracle E-Business Suite Integrated SOA Gateway, see Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

Integration repository administrators (defined by the Integration Repository Administrator role) can also find the following buttons available if the Web service has been generated successfully:

See: Performing Additional Web Service Activities.

XML Gateway Method Information

The XML Gateway method information page appears when you click a method name on an XML Gateway Map information page.

XML Gateway method information page

the picture is described in the document text

The general section of this page displays common information for the XML Gateway method, plus the following additional field:

Direction

This page also contains a table listing the XML Gateway method parameters, including each parameter's data type and whether the parameter is required.

PL/SQL Information

The following diagram illustrates the basic structure of the PL/SQL information page and its connection to the related PL/SQL procedure/function information page:

the picture is described in the document text

The PL/SQL information details page contains the following information:

The general section of the PL/SQL information page displays common information for the selected PL/SQL package.

PL/SQL information page

the picture is described in the document text

This page also contains a table listing the package procedures and functions, including active status and internal name. Click a procedure or function name to access its information page.

PL/SQL Procedure and Function Information

The PL/SQL procedure/function information page appears when you click a procedure or function name on the PL/SQL information page.

PL/SQL procedure/function information page

the picture is described in the document text

The general section of this page displays common information for the selected PL/SQL procedure or function, plus the Interface field. Click the link to view the interface that uses this package.

This page also displays the signature of this procedure or function, and it contains a table listing the procedure or function parameters and their attributes, including parameter name, data type, message direction (inbound or outbound), precision size, default value, and description.

Integration repository administrators (or users with the integration repository administrator role) can find the Create Grant button available which allows the administrators to grant the access of selected PL/SQL procedure and functions to a specific user, user group, or all users. See: Managing Grants.

Java Information

The following diagram illustrates the basic structure of the Java information page and its connection to the related Java method information page.

the picture is described in the document text

The general section of the Java information page displays common information for the selected Java class.

Java information page

the picture is described in the document text

This page also contains a table listing the class methods, including active status and internal name. Click a method name to access its information page.

Java Method Information

The Java method information page appears when you click a method name on the Java information page.

Java method information page

the picture is described in the document text

The general section of the Java method information page displays common information for the selected method, plus the following additional fields:

This page also displays the signature of this method, and information about the return type, and it contains a table listing the method parameters.

Integration repository administrators (or users with the integration repository administrator role) can find the Create Grant button available which allows the administrators to grant the access of selected methods to a specific user, user group, or all users. See: Managing Grants.

Java APIs for Forms

Java APIs for Forms are categorized as a subtype of Java interface type. These specialized Java classes are XML document-based integration points wrapped in Java classes for executing business logic in Oracle Forms. Similar to other service enabled integration interface types, Java APIs for Forms interfaces can be service enabled through SOA Provider.

The following diagram illustrates the basic structure of the Java APIs for Forms information page:

the picture is described in the document text

Searching and Viewing Java APIs for Forms

To locate Java APIs for Forms interfaces, you must perform a search through the combination of Category (subtype) and Category Value (Java APIs for Forms) fields.

Click Search to access the main Search page, and then click Show More Search Options to display more search fields. Enter the following key search values along with any product family or scope if needed as the search criteria:

For information about category and category value fields, see Category and Category Value.

The general section of this page displays common information for the selected Java APIs for Forms. Additionally, the Interface Subtype field is displayed with 'Java APIs for Forms' value.

Java APIs for Forms Interface Details

the picture is described in the document text

The interface details page contains the following information:

Business Service Object

Business service object interface type, formerly known as service bean, provides the access to SOA services and facilitates integration between Oracle E-Business Suite and trading partners. They can be used directly, or they can be exposed as Web services. They often employ service data objects as parameters to pass complex data.

A service data objects (SDO) defines a generic API for accessing and manipulating structured data as part of a Service Oriented Architecture (SOA). It is designed to simplify and unify the way in which applications handle data. The SDO API is independent of the actual data source. For example, SDO can be used to access XML data or SQL data. For more information about SDO, see Reviewing Service Data Objects.

Note: A business service object is not actually an interface type; rather, it is an object used by one or more Java service interfaces or other service data objects to pass data. Oracle Integration Repository includes it on lists of interface types, so you can browse or search for Java service interfaces based on the business service objects that they use.

The following diagram illustrates the basic structure of the business service object interface information page and its connections to related pages:

the picture is described in the document text

Business Service Object Interface Information

The general section displays common information for the selected business service object interface, plus interface name, the interface that extends, and XML schema information:

An XML schema is a description of a type of XML document, typically expressed in terms of constraints on the structure and content of documents of that type. It describes all input and output message definition and data type.

Click the XML schema link that is associated with your selected business service object to view the XML schema document displayed in a separate window.

The business service object interface information page contains the following information:

Business Service Object Web Service Region

Unlike XML Gateway Map interface type that can be service enabled by both Web Service Provider (in Release 12.0) and SOA Provider (after Release 12.0), business service object interface type is service enabled only through Web Service Provider, not by SOA Provider.

When a service is generated successfully for a given business service object, the Web Service - Web Service Provider region appears with Web Service Status information.

Business Service Object Interface Information Page

the picture is described in the document text

The View WSDL link is provided with appropriate Web Service Status information in the Web Service - Web Service Provider region. Click the View WSDL link allowing you to view the WSDL file.

The following sample shows the WSDL description for the Integration Repository Service:

<?xml version="1.0"?>
<definitions name="IntegrationRepositoryService" 
targetNamespace="http://xmlns.oracle.com/oracle/apps/fnd/rep/ws/IntegrationRepositoryService"
  xmlns="http://schemas.xmlsoap.org/wsdl/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
  xmlns:tns2="http://xmlns.oracle.com/apps/fnd/ServiceBean"
  xmlns:tns1="http://xmlns.oracle.com/apps/fnd/rep/ws"
  xmlns:tns="http://xmlns.oracle.com/oracle/apps/fnd/rep/ws/IntegrationRepositoryService">
<types>
<xsd:schema>
  <xsd:import namespace="http://xmlns.oracle.com/apps/fnd/rep/ws" schemaLocation="http://myurl.us.oracle.com:1234/webservices/AppsWSProvider/oracle/apps/fnd/rep/ws/IntegrationRepositoryService.xsd"/>
</xsd:schema>
<xsd:schema elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/apps/fnd/ServiceBean" >
  <xsd:element name="ServiceBean_Header">
    <xsd:complexType>
      <xsd:element name="RESPONSIBILITY_NAME" minOccurs="0" type="xsd:string"/>
      <xsd:element name="RESPONSIBILITY_APPL_NAME" minOccurs="0" type="xsd:string"/>
      <xsd:element name="SECURITY_GROUP_NAME" minOccurs="0" type="xsd:string"/>
      <xsd:element name="NLS_LANGUAGE" minOccurs="0" type="xsd:string"/>
      <xsd:element name="ORG_ID" minOccurs="0" type="xsd:string"/>
     </xsd:sequence>
   </xsd:complexType>
  </xsd:element>
 </xsd:schema>
   . . .

Note: Values passed in the Responsibility Name, Responsibility Application Name, Security Group, NLS Language, and Organization ID elements listed under the ServiceBean_Header are used to set applications context during service execution.

Please note that NLS Language and Organization ID are optional values to be passed. However, if the execution of a Business Service Object interface is dependent on any particular organization, then you must pass the ORG_ID element in the ServiceBean_Header of that SOAP request.

For more information, see Setting Other Web Service Input Message Parts, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

Please note that the user information is defined by the wsseUsername property passed within the security headers. Detailed instructions on how to pass the security headers along with the SOAP request, see Passing Values to Security Headers, Oracle E-Business Suite Integrated SOA Gateway Developer's Guide.

You might find the following information under <Method>_Response about error messages if occur:

...
<xsd: complexType name ="IntegrationRepositoryService_GetServiceDescription_Response">
		...
		<xsd:sequence>
 				<xsd:element name="serviceDescription" type="oans3:ServiceDescription" minOccurs="0" nillable="true"/>
				<xsd:element name="Message" type="oans1:ServiceMessage" minOccurs="0" maxOccurs="unbounded"/>

				<xsd:element name="ErrorMessage" type="oans1:ServiceMessage" minOccurs="0" maxOccurs="unbounded"/>
		</xsd:sequence>
</xsd: complexType name>

Note: The Message and ErrorMessage elements listed under <Method>_Response are used for error messages if occur. The Message element will appear as warning messages in the SOAP response. It is used to display any warning messages returned by the API. The ErrorMessage element corresponds to OAExceptions that were raised during the method invocation. In general, the response for any service method can contain any of the following:

For more information about error messages, see Error Handling section, Building an OA Framework Application (the Basics) chapter, Oracle Application Framework Developer's Guide, available from My Oracle Support Knowledge Document 1087332.1, Oracle Application Framework Release Notes for Release 12.1.3.

Authentication Type

Additionally, you can find the Authentication Type field with the following read-only check boxes:

These authentication types are used to secure Web service content and authenticate Web service operation. Before a service is deployed by an integration repository administrator, the administrator must select at least one authentication type for the service. For information on how to deploy a service, see: Deploying and Undeploying Web Services, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

Business Service Object Interface Method Information

The business service object interface method information page appears when you click a method name on the business service object interface information page.

For more information about the Method region for business service object, see Business Service Object Web Service Region.

Business Service Object Method Information Page

the picture is described in the document text

In addition to common information, the general section of the method information page contains a link to the interface that uses this method.

The following regions also appear on the method information page:

Integration Repository Service

Based on business service object interface, Integration Repository Service is a service component residing in Oracle Integration Repository. It queries Integration Repository data, and provides information about all the interface definitions to facilitate the integration between Oracle E-Business Suite and trading partners.

When you search for Integration Repository Service through the business service object interface type, all business service objects contained in the Integration Repository Service are displayed. You can grant the control access of each business service object method to appropriate users.

To access the Integration Repository Service interface, log on to Oracle Integration Repository and use the following steps to navigate to Integration Repository Service:

  1. Select Integration Repository responsibility from the Navigator menu, and click the Integration Repository link that appears.

  2. Click Search.

  3. Enter the following information in the Search page:

  4. Click Go to execute the search.

  5. Click Integration Repository Service link from the search result table.

    This opens the Business Service Object Interface information page. If the service is exposed as Web service for Integration Repository Service, the Web Service region also appears.

    See: Business Service Object Interface information page.

  6. Click a method name link in the Methods region to get to business service object method details.

    See: Business Service Object Method Information.

  7. Integration repository administrators can find Create Grant displayed in the Methods region.

    Select a method name and click Create Grant, you can grant the control access of a selected business service object interface method to appropriate users.

    See: Managing Grants.

Reviewing Service Data Object

A service data objects (SDO) defines a generic API for accessing and manipulating structured data as part of a Service Oriented Architecture (SOA). It is designed to simplify and unify the way in which applications handle data. The SDO API is independent of the actual data source. For example, SDO can be used to access XML data or SQL data.

The data objects associated with business service objects include service data objects (SDO) and filter data objects (FDO).

Service Data Object Information

This page is accessible from the getDataList and processDataList method information pages. You can also access it directly from the Oracle Integration Repository browse interface, through the list of interface types.

The following diagram illustrates the basic structure of the service object information page and its connections to related pages.

the picture is described in the document text

The general section of the service data object page displays common information, plus the data object class name, implementation name, and its associated XML schema.

Click the XML schema name link to view the schema document displayed in a separate window.

Service Data Object Information Page

the picture is described in the document text

The following regions also appear on the service object information page:

Filter Data Object Information

This page is accessible only from the getDataList method information page.

The following diagram illustrates the basic structure of the filter data object information page and its connections to related pages.

the picture is described in the document text

A filter data object is a type of service object. The general section of the filter data object page displays common information, plus the data object class name, implementation name, filter type, and its associated XML schema information.

Note: There are two types of filter:

For more information on filters, see Oracle Application Framework Developer's Guide, available from My Oracle Support Knowledge Document 1087332.1, Oracle Application Framework Release Notes for Release 12.1.3.

Click the XML schema name link to view the schema document displayed in a separate window.

Filter data object information page

the picture is described in the document text

The following regions also appear on the service object information page:

Service Data Object Method Information

The type of information provided for filter data object methods is the same as for service data object methods. The data object method information page appears when you click a method name on the service data object information page or the filter data object information page.

Service Data Object Method Information Page

the picture is described in the document text

In addition to a description, the following regions also appear on the service data object method information page:

Concurrent Program Information

The following diagram illustrates the basic structure of the concurrent program information page.

the picture is described in the document text

The concurrent program details page contains the following information:

Note: Since Oracle Integration Repository does not support Open Interface Tables and Views for service enablement, if a concurrent program is linked to Open Interface tables or views, this concurrent program will be viewed and displayed under the Open Interface category and cannot be service enabled.

For more information about the Open Interface integration type, see Open Interface Information.

Concurrent program information page

the picture is described in the document text

The general section of the concurrent program information page displays common information.

In the Parameters region, the parameters used in the selected interface are listed in a table. It includes parameter name, parameter type, required or not, displayed or not, and description information.

Note: The Type and Displayed columns are parameters used by Standard Report Submission (SRS).

Open Interface Information

Open interface integrations are always implemented using concurrent programs, so open interface information is listed in a region on a concurrent program information page. The following diagram illustrates the basic structure of the open interface information region and its connection to the related interface table information page.

the picture is described in the document text

Open Interface table list

the picture is described in the document text

The Open Interface information table lists the open interface tables and views that store the interface data, including active status, and whether it stores data inbound to Oracle E-Business Suite or outbound to another system. Click an interface table name to access the information page for that table.

Interface Table Information

The interface table information page appears when you click an Open Interface table name on a concurrent program information page.

Open Interface table information page

the picture is described in the document text

The general section of this page displays common information for the selected interface table.

By clicking a name link in the Open Interface Tables/Views region, you will find the selected table details displayed in a separate page. This open interface details page contains a table listing the interface table columns and their attributes, including a table column data type, data length, data precision, and data scale for each column, and whether the column is required or not.

Open Interface Table Details

the picture is described in the document text

Interface View Information

The general section of the interface view information page displays common information for the selected interface view.

Open Interface View List

the picture is described in the document text

Interface View Information Page

the picture is described in the document text

This page also contains a table listing the interface view columns and their attributes, including the data type, data length, data precision, and data scale for each view column.

EDI Message Information

The general section of the EDI message information page displays common information for the selected EDI message.

EDI message information page

the picture is described in the document text

The EDI Message information page also displays the message direction in the Direction field:

Business Event Information

The general section of the Business Event displays common information for business event.

the picture is described in the document text

An integration repository administrator can perform the administrative tasks:

For more information about subscribing to business events, see Subscribing to Business Events, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.