Error in Moni

[Former Member]

Hi All,

Can anyone tell me what below errored message means.

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>

<SAP:P1>ip_collectPaymentIDOC</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to convert the sender service ip_collectPaymentIDOC to an ALE logical system</SAP:Stack>

Thanks in Advance.

Regards,

Prajwal

[Former Member]

Hi,

Check ALE settings.

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 u2018Generate Partner Profilesu2019

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-> u2018Distributeu2019 to the destination client

Popup window appears ,press Enter

You will be intimated about the the Modal View Distributed

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

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 u2018Generate Partner Profilesu2019

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-> u2018Distributeu2019 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 u201CIntegration Repositoryu201D. 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 u201CInterface objectsu201D. You will find a node u201CDATA TYPESu201D

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

6) Create new data types.

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

6.1) Right click on u201CData typesu201D and select u201CNewu201D.

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 u201CExternal Definitionu201D is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from u201CExternal 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 u201D Interface objectsu201D Create a new object of type u201CExternal Definitionu201D 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 u201CMessageu201D 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 u201CInterface objectsu201D, right click on the u201CMessage typesu201D and select new.

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

7.3) For the section u201CData type usedu201D 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

u201D.***********************************************************************************

8.1) In the left hand frame under u201CInterface objectsu201D, right click on the u201CMessage Interfaceu201D 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 u201CMapping objectsu201D. Right click on u201CMessage mappingu201D 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 u201CSearch for Integration Objectu201D.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 u201CSearch for Integration Objectu201D.

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 u201CMapping objectsu201D. Right Click on u201CInterface Mappingu201D 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 Chooseu201D Search for Integration Objectu201D.

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 u201CIntegration Directoryu201D. 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 u201CService without Partyu201D and right u2013click on u201CBusiness Systemu201D->Assign Business System

4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box u201DCreate Communication Channel Automaticallyu201D.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 u201CCommunication Channelu201D. 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 u201CReceiveru201D 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 u201CReceiver Determinationu201D 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 u201CConfigured Receiversu201D area , choose the Service for the Target System.. Save your Receiver Determination

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

Create an Interface Determination.

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

7.3) Next create an u201CInterface Determinationu201D 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 u201CConfiguration Overview for Receiver Determinationu201D 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 u201CReceiver(Partner/Service)u201D open the details by clicking the node .The Entry u201CNot definedu201D shows you that there is no interface determination present.

Right click on the Entry u201CNot definedu201D and select u201C New specificu201D, in order to create a new interface determination object

7.3.3) You are now in the screen u201CEdit Interface Determinationu201D. In the section u201CConfigured Inbound Interfacesu201D 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 u201CSender Agreementu201D ->New

8.1) Specify the following:

Party: blank

Service: Select your own Business system

Interface: Outbound Interface

8.2) In the screen u201CEdit Service Agreementu201D 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 u201CConfiguration Overview for Receiver Determinationu201D at the bottom of your screen click Refresh.

9.2) In the Column u201CReceiver Agreement(Communication Channel) u201C right click and select u201CNew Specificu201D.

Specify the following:

Party: blank

Service: Select your own Business system

Interface: Inbound Interface

9.3) In the screen u201DEdit Receiver Agreementu201D 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

Phani

[former_member192295]

Hi,

It is due to configuration and parameters missing check it once again all configuration. If idoc is sender check IDX1 & IDX2 meanwhile check idoc control record parameters if idoc is receiver.

Note:

1. For IDOC sender no need communication channel & sender agreement also

2. If idoc is receiver need communication channel and receiver agreement also

[former_member187339]

Hi,

The sender service (ip_collectPaymentIDOC ) should have Adapter-specific identifiers given. Please note a valid identifier (maintained in receiving R/3 system) should be used as Adapter-specific Identifer.

Regards

Suraj