No interface in Reciever agreement

[Former Member]

Hi all,

I am configuring a idoc scenario in reciever agreement i am selecting the service and then come to interface (display ) i am unable to get the interface there (from the BUSINESS SYSTEM). If i click ALL then i can see the interface .

I am getting an error stating Message interface does not exist in any software components installed in this Business system.

This prevents the reciever determination .

Thanks in advance ,

Regards Naveen.

[Former Member]

hi

as you are doing idoc to file scenario your sender system should be the business system not the business service. So in receiver dtremination you need to select the your business system. i think this might be reason for not getting the interface of your idoc.

plesae refer to the links

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb...

rewards point if helpful

regards

Kasturika

[Former Member]

HI Phukan,

I have selected the business system as the sender service.

[Former Member]

hi

plesae refer to this link its a step by step guide to idoc to file scenario.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd....

plesae check you ALE settings .

hope it will help u to find your error.

regards

Kasturika

[Former Member]

Hi,

Check the Buiness system in sld whether it is correctly configured

If that is correct go with click all option then also your scenario will work

try this if there is any issue let me know that

Yuga

[Former Member]

HI Navveen,

The problem of the software component to be missing can be resolved by follwoing the below simeple steps.

1. In Integration Directory (ID) open the Business System, goto "Other Attributes" tab.

here you will get list of Software compnent list. Verify your required Software component is available in it or not.

2. If its not avaialble then you will not be able to see the interface in Business system..

Then add the software component in the Business system via SLD.

Plesae refer below discussion, it will help you in more troubleshooting for it.

Thanks

Swarup

[Former Member]

hi

Swarup Sawant

I am getting the software component in the "attributes " tab in the business system. but i am not getting the interface ...

Thanks in advance

Naveen

[justin_santhanam]

Naveen,

Plz follow the steps as I mentioned in the thread

raj.

[Former Member]

HI Raj,

In Reciever determination i am giving the service .If i try to import the interface i am not getting the interface .

where as i am getting that interface when i click business system (sender interface)in ID . Can you please suggest me .

Thanks in Regards ,

Naveen

[Former Member]

Hi raj,

I have a small doubt regarding my issue . this is a idoc scenario and there is no interface and message mapping will this effect to get my interface in the reciever determination.

Thanks in advance,

Naveen

[Former Member]

Hi Naveen,

If your Scenario is File-IDOC means and you are getting the following message while you are selecting the Service in Receiver Determination

"Message interface does not exist in any software components installed on this business system.txt"

Follow these Steps

1) Open ID-----Double click on Business system that which u are using in the scenario

2) Check whether you are able to see the SWC in the Othere attributes TAB

3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type

4) Click on Installed Products TAB

5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it

6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.

7) Click on Installed products and Check the check box of your Product and then finally save that.

Now you should be able to see the SWC in the Othere attributes TAB in ID

Regards

Seshagiri

[former_member208856]

You have to use Business system for this IDOC Scenario.

This is complete step by step document for configuring the idoc to file scenario along with ALE Settings

*************************************************************************************************************************

To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS

***********************************************************************************************************************

STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3

We need to do the following settings in XI

1) Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful

****************************************************************

2) Create Port Using Transaction Code 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 Using transaction Using Transaction (IDX2)

**********************************************************************

a) Create new

b) IDOC Message Type

c) Enter port created in IDX1

**********************************************************************************************************************

SETTINGS IN SAP R/3

***********************************************************************************************************************

We need to do the following settings in R/3

Logon to Sap R/3 System

**********************************************************************

1) Create an RFC Destination to XI in transaction code (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.Both must be succesful

***********************************************************************

2) Create communication Port for Idoc processing Using Transaction(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)

d) Enter the RFC Destination created in SAP R/3 towards other system.

e) Save

***********************************************************************

3) Create Partner Profile with Outbound Parameters (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

Then Save

e) Select Partner no. and LS which were create above

f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter

g) Select Message type

h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type

I) save

*****************************************

4) In Transaction SALE, Create Logical System

*******************************************

a). Go to Basic Settings-> First Define logical systems

and then assign logical systems

b) Double click on Define the logical systems

c) Give data for your Logicaal System and Name

d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready

e) Assign the logical system name to the client

*******************************************************************

5) Create Customer Distribution model in the transaction code BD64

******************************************************************

1) Click on the Create modal View button and enter the short text, Technical name etc as shown below

2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type

3) Save the Distribution model

Generate Partner Profiles

Click on Menu Item ‘Generate Partner Profiles’

It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute

Then, you will be intimated about the partners, port creation, and outbound parameters creation

4) Distribute Customer Distribution Model

In the menu item GO to Edit->Modal View-> ‘Distribute’ to the destination client

Popup window appears ,press Enter

You will be intimated about the the Modal View Distributed

****************************************************************************************

Step2:Repository

*****************************************************************************

1) From the Integration Builder page, select “Integration Repository”. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server

2) Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions

From the list of Software Component Versions, Choose your own software component version .Click Import.

3) On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.

Your NameSpace is urn : DSZVFGD

4) Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted

After this specify the connection parameters to the R/3 system:

4.1) System :SAPFOX

4.2) Client :800

Then Save it. The new namespace will be visible under software component version node in the left frame.

Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.

4.3) Application server:172.25.5.7

4.4) System number:00

4.5) User name: DEVELOPER

4.6) Password: Password of Sap R/3 system.

Then click continue .You will find IDOC node. Click on this node and select the Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.

5). Under your namespace in the left frame, expand the node “Interface objects”. You will find a node “DATA TYPES”

************************************************************************************

6) Create new data types.

*************************************************************************************

6.1) Right click on “Data types” and select “New”.

Your Data Type is :DT_FILE

In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.

Save the object.

6.2) The Import function for XSD files enables you to upload message definitions from external sources. The object type “External Definition” is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from “External Definition

no need to create Data types. They are imported directly as Message types.

6.3) To do so, In the left hand frame Under ” Interface objects” Create a new object of type “External Definition” and give name to it.

Select the following.

6.3.1) Category: XSD.

6.3.2) Messages: From All Available Global Elements.

6.3.3) File:

Once the XSD is imported, click on “Message” tab , You should be able to see 2 messages(Request and Response)

*************************************************************************************

7). Create a new Message Type.

*************************************************************************************

7.1) In the left hand frame under “Interface objects”, right click on the “Message types” and select new.

7.2) Give a suitable name to the Message type.(MT_ messagetype).

7.3) For the section “Data type used” you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.

Save it.

***********************************************************************************

8). Create a Message interface

”.***********************************************************************************

8.1) In the left hand frame under “Interface objects”, right click on the “Message Interface” and select new and name(MI_ messageinterface) it

8.2). The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).

Save it.

************************************************************************************

9) . Create a graphical mapping between the target document and the sender .

************************************************************************************

9.1) In the left hand frame ,expand “Mapping objects”. Right click on “Message mapping” and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.

9.2) As Source message select your own Idoc .You can choose “Search for Integration Object”.As a reminder you can find your Idoc or Rfc under Software Component- > Namespace->Imported Objects.

9.3) As Target Message you can choose your Message type .Choose “Search for Integration Object”.

9.4) Now that we have defined the Source and Target message, we can start defining the Mapping rules.

9.5) Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the Source fields to the respective Target Fields.

Save It.

9.6) You can also Test your Mapping by selecting the 'Test Tab'.

9.7) Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.

***********************************************************************************

10). Create an Interface Mapping.

***********************************************************************************

10.1) In the left hand Frame expand “Mapping objects”. Right Click on “Interface Mapping” and Name it. You are in a Interface Mapping Editor .Assign the following References.

10.2) Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose” Search for Integration Object”.

10.3) Target interface: Your Inbound Interface( The Target document interface).

Then Select 'Read Interface' and Assign your 'Mapping Program' .

Mapping Program: Your Message mapping.

Then Save it.

11.) Finally , in the left hand frame ,go to your change list and Activate it

********************************************************************************

STEP 3: Directory

********************************************************************************

1) From the Integration Builder page, select “Integration Directory”. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.

**********************************************************************************

Create a Scenario Object

**********************************************************************************

2). The First Step is to create a Scenario Object

This will serve as container for all your configuration work. Create and save a scenario object

3) In the left hand frame you can see the created scenario object. Under that Object Expand the node “Service without Party” and right –click on “Business System”->Assign Business System

4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box ”Create Communication Channel Automatically”.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.

*****************************************************************************

5) . Create a Communication Channel.

******************************************************************************

6). Expand your service and right click on “Communication Channel”. Name your Communication Channel

Here we need to configure the adapter.

*********************************************************************************

Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.

*********************************************************************************

*********************************************************************************

For the Receiver, Specify the following Parameters

*********************************************************************************

6.1 For the adapter type , use the F4 help and select FILE.

6.2 Specify “Receiver” since the adapter will be sending XML files from XI to the FTP server.

6.3 Specify the following parameters.

Transport Protocol: File Transport Protocol.(FTP)

Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)

Adapter Engine: Integration Server

For the File system access Parameters, enter the following

Source Directory:VILAS

File Name: Input.txt

6.4 For the FTP Connection Parameters, Specify the Following

Server: 172.25.7.116

Port: 21(by default)

Data Connection: Passive

Connection security: None

Connection Mode: Permanently

Transfer Mode: Binary

6.5 For Processing Parameters, Specify the following

File construction mode: Add Time Stamp

File Type: Binary

6.6 For Content Conversion Parameters, Specify the Following

RecordSet Structure:

Adapter Status: Active

The receiver file adapter is now configured. Save your Communication Channel.

*********************************************************************************

Create an Receiver Determination.

*********************************************************************************

7). From the left frame Create a new “Receiver Determination” object. This is the main part of routing process, where you assign a receiver for your message.

7.1) Select your sender service and interface.

Sender:

Party: blank

Service: Sender service(Business system)

Interface : Sender interface

7.2) In the “Configured Receivers” area , choose the Service for the Target System.. Save your Receiver Determination

*********************************************************************************

Create an Interface Determination.

*********************************************************************************

7.3) Next create an “Interface Determination” object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping

7.3.1) In the Receiver Determination you just created, have a look at the area “Configuration Overview for Receiver Determination” at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.

7.3.2) In the column “Receiver(Partner/Service)” open the details by clicking the node .The Entry “Not defined” shows you that there is no interface determination present.

Right click on the Entry “Not defined” and select “ New specific”, in order to create a new interface determination object

7.3.3) You are now in the screen “Edit Interface Determination”. In the section “Configured Inbound Interfaces” select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.

After choosing the Inbound Interface, It is shown in the Interface Determination

7.3.4) A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.

7.3.5) When you are done , Save the Interface determination object.

*********************************************************************************

8.) Create a Sender Agreement.

*********************************************************************************

In the left hand frame , right click on “Sender Agreement” ->New

8.1) Specify the following:

Party: blank

Service: Select your own Business system

Interface: Outbound Interface

8.2) In the screen “Edit Service Agreement” use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close

*********************************************************************************

9.) Create a Receiver Agreement.

*********************************************************************************

Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.

9.1) Go back to the main screen for your receiver determination. In the area “Configuration Overview for Receiver Determination” at the bottom of your screen click Refresh.

9.2) In the Column “Receiver Agreement(Communication Channel) “ right click and select “New Specific”.

Specify the following:

Party: blank

Service: Select your own Business system

Interface: Inbound Interface

9.3) In the screen ”Edit Receiver Agreement” for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it

Your Configuration is complete. Activate the objects.

Regards,

Sandeep Kaushik