Developing Enhanced Services
Inside-Out
● The interface to be used must already be in the application system before you import it to the ES Repository. If you are developing the functions for the first time, SAP recommends that you develop them using the outside-in approach.
●
If you are using
external definitions, note the prerequisites for
external
definitions.
●
You can import RFCs
and IDocs from SAP systems Release 4.0 and higher. You must have the necessary
authorization to import from a system (see Prerequisites under
Importing IDocs and RFCs).

It is the adapter type and not the import function that determines whether a system can be connected to SAP Exchange Infrastructure using an adapter. Note the prerequisites for the respective adapter.
The procedure described below only applies for interfaces that cannot be imported into the ES Repository. If this is the case, ignore the first step.
...
1. Import an interface description for the interface that you want to use to exchange messages using the Integration Server to the design maintenance screen of the ES Builder:
○
For RFCs and IDocs,
you do this by importing from the respective application system (see also:
Importing IDocs
or RFCs). Specify an application system for each software component
version.
○
For third-party
adapters, import
external
definitions. In this case, you can only use the message schema of the
external definition.
2. The imported interface corresponds to either an inbound or an outbound interface. Depending on the communication party, create the corresponding counterpart in the ES Repository. There are different procedures for creating the counterpart depending on which counterpart you use and the demands of the communication parties. More information: Combining Development Approaches

You can also use the mapping editor to import XML and XSD files from the local file system and therefore to define a message mapping for interfaces that cannot be imported.
You can access the message definitions in the ES Builder:
● RFCs: Request, response, or fault parts
● IDoc: Request part only (no other parts exist)
● External definitions: External messages (depending on the import mode)