Configuration side need explanation?

[Former Member]

Dear experts,

Please dont send any links i want clear explanation

1) What is the use of Party & Service with out party?

2) What is the use of Receiver Determination/ Interface determination/ Sender agreement/ Receiver agreement?

Points will be rewarded.

Thanks,

Bhavya

[Former Member · Accepted solution]

hi,

A service enables you to address a sender or receiver of messages.

Services with and Without Party

You can assign a service to a communication party or define it as a Service without Party. Services that are assigned to a communication party are displayed in the navigation area of the Integration Builder under Party in the subtree of the party. Services that are not assigned to a communication party are displayed in the subtree as Services Without Party

Party

Party is used to represent a Business Partner (doesnt belong to the current landscape) which is defined in B2B Scenarios.So All the systems/services accociated with the Party are referred only as Services.

Service without Party

It is used to represent any service within the landscape and is used in A2A communication.

Receiver agreement:

You use a receiver agreement during outbound processing. In the receiver agreement, you define how the message is to be transformed so that it can be processed by a receiver.

Sender agreement:

A sender agreement is used during inbound processing. In the agreement, you define how the message is to be transformed so that it can be processed by the PCK.

Interface determination:

You use an interface determination to specify which inbound interface of a receiver a message is to be forwarded to. You can also specify which interface mapping from the Integration Repository is to be used for processing the message.

You define an interface determination for a sender, an outbound interface, and a receiver.

receiver determination:

You use a receiver determination to specify which receivers a message is to be sent to. You have the option of defining conditions for forwarding the message to the receivers. You specify services as receivers of messages.

Thanks,

Madhu

[Former Member]

HI

DWF bwtn party n service w/o party:

1.we go for service without party when we are having A2A communication.

A2A means application to application communication, it is used when two systems in same landscape try to communicate with each other. Systems in same landscape means both the systems are belongs to same organization or a company.

Normally in A2A communication sender and receiver is inside one organization and developer have freedom to define communication rules .

refers to link

http://help.sap.com/saphelp_nw04s/helpdata/en/66/58934257a5c96ae10000000a155106/content.htm

2.we go for service withparty when we are having B2B communication

B2B means Business to Business communication .It is used when there is exchange of information between two different Parties or companies or landscape.

When two applications in different companies communicates with each other we call it B2B Communication.

in case of B2B every party has it own rules which must be followed if we want to communicate between different organization.

refers to link

http://help.sap.com/saphelp_erp2004/helpdata/en/ca/efb540efe68631e10000000a1550b0/content.htm

Receiver Determination:

A Receiver determination is the final step in establishing a logical routing for a message. It allows the association of an outbound message interface from a sender to 1 or more receivers. A condition can be defined for each receiver that, based on data values in the message itself, will allow/prevent the forwarding of a message to that receiver. Then R.D specifies for the incoming message from a given sender all the potential receivers of that message.

We use a receiver determination to define one or more receivers for a sender and an outbound interface. The receiver can be a party or a service. We can also specify that the receiver will be determined at runtime from the message contents.

Interface Determination:

An interface determination allows the association of an outbound message interface from a sender to one or more inbound message interfaces of a single receiver. It focuses on a single sender/receiver pair for that same outbound message interface and all the related inbound message interfaces.

Simply saying, it specifies which interface is to be used for the inbound processing of a message.

An interface determination specifies which interface is to be used for the inbound processing of a message

Sender Agreement:

In the sender agreement, we define how the message is to be transformed so that it can be processesed by the integration engine.

A sender agreement is used to transform an incoming message so that it can be processed by the integration engine.

Steps:

Enter the Sender service.

Select the Outbound Message Interface and namespace.

Enter Description.

Select the sender communication channel.

Receiver Agreement:

In the receiver agreement, we define how the message is to be transformed so that it can be processed by a receiver.

A Receiver agreement is used to transform an outgoing message so that it can be processed by the receiver.

Steps:

Enter the Sender service.

Enter the Receiver service.

Select Inbound Message Interface and namespace.

Enter Description.

Select the Receiver Communication Channel.

cheers

reward points if found useful

[Former Member]

Hi,

You have the following options for addressing the sender or receiver of a message:

· Communication Party (party for short)

· Service

The XI message protocol supports the addressing of senders and receivers on two levels: The first level corresponds to a company unit, the second to a technical or semantic unit within a company unit or company. You represent the first addressing level with the Communication Party object, and the second by the Service object.

Depending on the scenario, you can define the sender and receiver of a message very flexibly with these objects. The options are listed in the following table.

Party with assigned services:

You use this type of addressing when configuring collaborative processes in which whole companies communicate with each other.

You then use a communication party to represent each company. A service represents a business or technical entity within a company.

In cross-company processes, the companies involved usually provide a variety of services for communicating with other companies.

See also : Link: http://help.sap.com/saphelp_nw04/helpdata/en/37/455d6993cd7646ac33674b162ab2a6/frameset.htm

Services without party: You use this type of addressing when configuring processes in which the system landscape is known to you.

The definition of communication parties is not mandatory. This enables you instead to specify the known business systems and integration processes (defined as business system services or integration process services) directly as either the sender or receiver of a message. In this way, you can address individual business systems directly and thus create receiver determinations and interface determinations very easily.

See also : http://help.sap.com/saphelp_nw04/helpdata/en/37/455d6993cd7646ac33674b162ab2a6/frameset.htm

Interface Determination::

You use an interface determination to specify which inbound interface of a receiver a message is to be forwarded to. You can also specify which interface mapping from the Integration Repository is to be used for processing the message.

You define an interface determination for a sender, an outbound interface, and a receiver.

Features

In the Display/Edit Interface Determination editor, you can select between two types of interface determination types (radio buttons):

● Standard

Choose this option if you want to specify manually which inbound interface the message is to be forwarded to.

You can also specify the mapping that is to be executed. If you specify more than one inbound interface, you can specify conditions for forwarding the message to the inbound interfaces. These conditions are evaluated at runtime.

● Enhanced

Choose this option if you want to configure a mapping-based message split.

In this case, you select a multi-mapping from the Integration Repository. In this case you get the inbound interfaces from the target interfaces of the mapping.

You would typically use a mapping-based message split if you have a source message with a number of items that can vary from message to message, and you want to use this source message to generate multiple individual messages for the individual items.

Receiver determination:

You can configure a receiver determination in such a way that the receivers of the message are determined dynamically at runtime by a mapping.

Sender Agreement

In a sender agreement, you define how the message of a sender is to be transformed so that it can be processed by the Integration Engine

Reward points if helps.

Regards,

Soumya

[Former Member]

Hi,

Business System: is a logical representation of a Technical System.

Business Service is a abstract representation of a System. For instance, www.google.com have a several system working together and IPs of this machines change eventually. When we use a Business Services like google we reference a computer that we don't know the phisical implementation.

Business Service: Address an abstract business entity as the sender or receiver of messages.

Using a business service, you can define the technical or business subunits of the companies

involved and then assign them the relevant interfaces. The business services are used when

configuring cross-company processes.

Thanks

Vikranth

[vijay_b4]

HI Bhavya,

8Please reward points*

service and service with out party

1.we go for service without party when we are having A2A communication.

A2A means application to application communication, it is used when two systems in same landscape try to communicate with each other. Systems in same landscape means both the systems are belongs to same organization or a company.

Normally in A2A communication sender and receiver is inside one organization and developer have freedom to define communication rules .

refers to link

2.we go for service withparty when we are having B2B communication

B2B means Business to Business communication .It is used when there is exchange of information between two different Parties or companies or landscape.

When two applications in different companies communicates with each other we call it B2B Communication.

in case of B2B every party has it own rules which must be followed if we want to communicate between different organization.

Interface Determination,Receiver Determination,Sender Agreement,Receiver Agreement

Sender agreement -> it involves your sending system, your corresp. interface and the communicaion channel through which you are pulling data into XI.

Recv. Agr. -> This involves your sending system, receiving sys, the corresp. interface and the communicaion channel through which you are sending data out of XI.

Reward points if this helps

Regards

Pragathi.

[Former Member]

Hi Kumari,

1.What is the use of Party & Service with out party?

A.Party : The sender system is not local It is used for B2B scenarios.

Service without party : We use this when the sender is the same system.It is used for A2A scenarios

Receiver Determination

Use

You use a receiver determination step () to get a list of receivers for a subsequent send step. The receiver determination step calls the receiver determination that you configured in the Integration Directory and returns the receiver list.

Send Context

In the receiver determination step, specify the send context and the multiline container element for the receiver list. You must specify the send context to be able to send messages from the same interface to different receivers in different send steps.

The send context is an arbitrary string. You query this context in a condition in the receiver determination in the Integration Directory.

Interface determinationYou use an interface determination to specify for a sender, an outbound interface, and a receiver, which inbound interface is to be used for receiving the message at the receiver. You can also specify which interface mapping from the Integration Repository is to be used for processing the message.

Sender agreement

Use

A sender agreement is used during inbound processing. In the sender agreement, you define how the message is to be transformed so that it can be processed by the PCK.

Receiver agreement

Use

You use a receiver agreement during outbound processing. In the receiver agreement, you define how the message is to be transformed so that it can be processed by a receiver.

Thanks

Vikranth

[Former Member]

Hi Bhavya,

1) What is the use of Party & Service with out party?

party is generally used in case of B-B scenarios where we have different IT landscapes.

Service with out party is used in A-A scenarios.

2) What is the use of Receiver Determination/ Interface determination/ Sender agreement/ Receiver agreement?

Receiver determination: we identify to whome we are sending the data.

and in interface determination we identify the receiver inbvound interface.

sender agreement we say whoz our sender and what is the communication channel.

and in receiver agreement we say whoz our receiver and what is the communication channel.

Thanks,

Vijaya.

[Former Member]

Hi,

Coming to the business system & business service where we can used exactly?

Please dont send any links.

Edited by: Bhavya Kumari on May 23, 2008 4:17 PM

[Former Member]

Business System

Business systems are logical systems that function as senders or receivers within the SAP Exchange Infrastructure. You configure business systems in the SAP System Landscape Directory (SLD). A business system is always associated with a technical system (here: SAP Web AS ABAP system).

Business Service

Using a business service, you can define the technical or business subunits of the companies involved and then assign them the relevant interfaces.

Thanks,

Vijaya

[Former Member]

Hi,

business system:

Business systems are logical systems, which function as senders or receivers within PI. Business systems can be SAP systems or third-party systems.

Depending on the associated technical system, the following types of business systems are defined in the SLD:

· Web AS ABAP

A business system, which is associated with a Web AS ABAP.

A business system, which is associated with a Web AS ABAP, can play the role either of an application system or an integration server. An integration server is the central component of PI, which provides a framework for the exchange of information among various internal and external entities of a company. The integration server facilitates the interaction between the different operating systems and applications across internal and external networks.

· Web AS Java

A business system, which is associated with a Web AS Java.

· Standalone

A business system, which is associated with a standalone Java application.

· Third-party

A business system, which is associated with a third-party technical system.

Thanks,

Madhu

[Former Member]

Hi,

Coming to the business system & business service where we can used exactly?

Please dont send any links.

Thanks,

Bhavya

[Former Member]

In very simple terms, If you have any technical/business system registered / defined in the SLD, you use business system. Else you use business service. So for application to application you use business systems (A2A), for business to business (B2B) you mostly use business service

[Former Member]

Madhu ,

Can u please explan my second question.

Thanks,

Bhavya

[Former Member]

Receiver agreement:

You use a receiver agreement during outbound processing. In the receiver agreement, you define how the message is to be transformed so that it can be processed by a receiver.

Sender agreement:

A sender agreement is used during inbound processing. In the agreement, you define how the message is to be transformed so that it can be processed by the PCK.

Interface determination:

You use an interface determination to specify which inbound interface of a receiver a message is to be forwarded to. You can also specify which interface mapping from the Integration Repository is to be used for processing the message.

You define an interface determination for a sender, an outbound interface, and a receiver.

receiver determination:

You use a receiver determination to specify which receivers a message is to be sent to. You have the option of defining conditions for forwarding the message to the receivers. You specify services as receivers of messages.

Reward points if it is useful to you

Thanks,

Madhu