Business System and Business Service

[Former Member]

Hi,

I want to know one thing that why we need business system while there is business service.

in which case we need to use business system.

i know that business system is defined in SLD and not business service.

apart from that what is the advantage of using business system than business service.

In every scenario can we use business service instead of business system.....

Appriciate your help....

[Former Member · Accepted solution]

HI,

Business system is something which can has a Techincal existence like File system but can nt be associated with a product

Business Service has to be associated with a product like SOAP , webservice

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.

When we talk about Business System, we are talking about those system which have been defined in the System Landscape Directory, For all our A2A Scenario we generally define Business System.

When we talk about Business Services, we are talking about individual services, that services could be one of the service of our Business System also. For all our B2B Scenario we genrally prefer using Business Services. It helps us in communicating with our business partner, without exposing our (Business) Landscape.

Usage of Business System for A2A and Business service for B2B, hides the direct access to SLD to the 3rd party Business services.

Thanks

swarup

Thanks

swarup

[Former Member · Accepted solution]

Hi,

one thing more,

when we open a business system in ID, we can see one tab called"IDOC Partner", but not in business service.

what does it means?

I have seen in SLD when we define one business system we have to give one logical system name, is it somewhere related to this IDOC partner....

[Former Member · Accepted solution]

Hey

Business system is mandatory in some particular cases only,for e.g when you are integrating SAP system,you need to define a business system of type WebAs ABAP.its required when you use IDOC,Proxy or RFC.

Similarly in case of Java systems you need to define business system as WebAs Java.

In most of the other cases you can use business service.

Thanx

Aamir

[Former Member · Accepted solution]

Hi Aamir,

Suppose i have a B2B scenario, where i need to communicate with a IDOC or RFC outside of my landscape, so then how i define a business system(Web AS ABAP) in my landscape and use it in ID.

[Former Member · Accepted solution]

Kindly clear this doubt.

Will apreciate your help....

[Former Member · Accepted solution]

Hi,

Yes the logical system name that you will be giving is same as the Partner Profile taht had setup for Outbound/Inbound IDOCs in R/3.

Thus the IDOCs coming from that port will validate with teh Business system.

Even in adapter specific attributes we need to mainatin the Logical system name.

IDOC Partner is used under the PCK configuration.

Thanks

swarup

[Former Member · Accepted solution]

Hi Swarup,

so when i need to communicate with the IDOC from different Landscape, then how do i define the business system for that system if business system is mandatory for IDOC communication

[Former Member · Accepted solution]

Hi,

With out Business System also we can run the Scenarios for those communicating with the SAP Systems also

Check this

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

Regards

Seshagiri

[Former Member · Accepted solution]

Hi,

You can use the Business Services also...and specify the Logical system name in adapter specific attributes. this way you can deal with IDOCs without Business systems.

thanks

Swarup

[Former Member · Accepted solution]

Hi Swarup,

just anothor thing,

If we use business service for IDOC communication then from where i can get the logical system name to use in Adapter Specific Identifiers of business service.

means, we have to define the logical system in R/3 side in BD54 tcode. now if my sender or receiver system is not in my landscape(B2B) then where do i create the Logical System in that case.

[Former Member · Accepted solution]

Hi Swarup,

Kindly suggest me on this:

If we use business service for IDOC communication then from where i can get the logical system name to use in Adapter Specific Identifiers of business service.

means, we have to define the logical system in R/3 side in BD54 tcode. now if my sender or receiver system is not in my landscape(B2B) then where do i create the Logical System in that case.

[prateek · Accepted solution]

from where i can get the logical system name to use in Adapter Specific Identifiers of business service.

U have to mention it manually. The name should be same as that provided in R3 system.

now if my sender or receiver system is not in my landscape(B2B) then where do i create the Logical System in that case.

U don't have to specify it anywhere in ur landscape. Just use it directly.

Regards,

Prateek

[Former Member · Accepted solution]

Hi Prateek,

In adapter specific parameters we also have to give the R/3 System ID and client. how do i get that..

[prateek · Accepted solution]

U can check the RFC destination for that R3 system. There for the login parameter, u will find the client and other details.

Best is to ask the client :).

Regards,

Prateek

[Former Member · Accepted solution]

Hi Prateek,

For A2A i can check the system id and client from the R/3, i think for B2B you have told to ask from Client.

isn't it?

and one thing more,

you have told to give any name as the Logical system, will it be configured somewhere(like: in PCK or something).

So the ultimate conclusion is we need to use Business Service in B2B scenarios and if we have SAP system than we have to give Logical system in the Adapter Specific Parameters.

[prateek · Accepted solution]

For A2A i can check the system id and client from the R/3, i think for B2B you have told to ask from Client. isn't it?

In any case, whenever possible, ask client. If not, u will have an entry in sm59 and idx1 to connect to the R3 system. U can check the details there.

you have told to give any name as the Logical system, will it be configured somewhere(like: in PCK or something).

Not any name, In case of R3, only the name which is present as Logical system name in R3.

So the ultimate conclusion is we need to use Business Service in B2B scenarios and if we have SAP system than we have to give Logical system in the Adapter Specific Parameters.

Correct.

Regards,

Prateek

[Former Member · Accepted solution]

Hi Prateek

as you replied.

you have told to give any name as the Logical system, will it be configured somewhere(like: in PCK or something).

Not any name, In case of R3, only the name which is present as Logical system name in R3.

In A2A we have access in the R/3 system, so we can easily check the logical system name from there, but in B2B we don't have the access in R/3 so then how i can check the logical system in R/3

[prateek · Accepted solution]

My earlier repliles for checking the details in idx1 and sm59 meant to check these transactions in XI and Not R3

Idx1 does not exist in R3.

Regards,

Prateek

[Former Member · Accepted solution]

Hi Parteek,

ok for the time being.

will ask you later for any furthur quaries.

[former_member192295]

Hi,

Business system and Business service both are use for ID configuration, if we have complete client technical system information for configuration we will choose business system, if we don't have client technical system information we will choose business service.

Business system need whenever we want to communicate with R3 system, i mean IDOC, RFC etc. Without business system we can't configure IDOC and RFC adapters. In this case business service can't use.

Business service can work with remaining adapters like FILE,JDBC, HTTP etc adapters, why because it is through this adapters we can communicate with external system like B2B or A2A.

A2A & B2B application depending on requirement we will choose business system or business service.

If sender is R3 system and receiver is third party system no need business system we can work with business service. This one we can apply to remaining similar scenario also.

I hope clear little bit

[Former Member]

Hi,

Business Sytem-->When we have full details of application system,we go with business system and it is created in the SLD so we dont have authorization to change the business system name.A Business system is something that physically exists

For example, if u want to download a file from a system ABC, by using file adapter and then want to update the

content of this file into r/3 database by using RFC,then the system abc and the r/3 will be ur business systems

i.e. they physically exists.

Business Service-->When we have partial details or no details of Technical system then we go with business service. it is created in ID. we can see and change it.

Business service is mostly used in B2B Scenario (cross-component),where you don't know the Business System of your partner. In other words business Service will be used only

for those partners which do not have a physical landscape set up . Business servces do not have an entry in SLD.

Regards,

Bharath

[Former Member]

Services are used to:

u2022Represent a technical or business unit, which is to be addressed as the sender or receiver of messages.

u2022Group interfaces to exchange messages according to particular task areas.

u2022Address business systems and business processes as senders or receivers of messages.

The Service is used to group interface objects when the Landscape is not described in the System Landscape Directory (i.e., for a Partner System).

Business Service represents an abstract ,addressable unit.Business services are used in cross company processes.Using business service ,you can define the technical or business subunits of the companies involved and then assign them the relevant interfaces.

Business system:

Business systems are logical senders or receivers that exchange messages by using the Integration Server and that are entered in the System Landscape Directory.

The business systems in the System Landscape Directory relate to a system landscape. The business systems of business partners are therefore not entered in the System Landscape Directory. To be able to address such business partners logically, use communication components in the Integration Directory. A business system is a way of specifying a communication component in the Integration Directory more precisely (business system component).

A communication party represents a larger unit which is involved in a cross-system process (for example a company).

Regards,

Nithiyanandam

[Former Member]

URL

http://help.sap.com/saphelp_nw04/helpdata/en/fe/131eb4ef2fb344abf471c9eac0063a/frameset.htm and then navigate back up the tree to the Service heading

I have provided an excerpt from the documentation

Business System

If you want to address an abstract business entity as the sender or receiver of messages, choose this service type.

If you want to address a particular business system as the sender or receiver of messages, choose this service type.

A business system is an actual application system in a system landscape. A business system (service) comprises information about the inbound and outbound interfaces and the software component versions of the business system.

You usually use business system services when configuring internal company processes.

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.

You usually use business services when configuring cross-company processes. In this case, you only make your interfaces known to the business partners involved and either do not make any details about your own system landscape available, or only specific details.

For example, you can define RosettaNet Partner Interface Processes (PIPs) as business services.