Business Service and logical system naming criteria across environments

[Former Member]

Hi !

Imagine this scenario: File-XI-IDOC. There is a file server where files are uploaded by a legacy application. XI polls that directory, converts the file to IDOC and sends it to R/3.

R/3 is a production business system, for example "R3_PROD", the file server is a business SERVICE, because of its abstract nature.

Is it ok to give that business service a name such as "BS_FileServer" and then create the logical system "LS_FileServer" in R/3, to be able to receive IDOCs from the sender business service?

If we need to use 3 different file servers, one for development, one for test and another for production...is it ok to create the business service in each integration directory with SAME name, and the 3 logical systems with same name in each R/3 receiver...because creating business services as "BS_FileServer_DEV", "BS_FileServer_TEST" and "BS_FileServer_PROD" we imagine that could give us problems when transporting scenarios from dev to test, and from test to prod...because we will need to recreate the whole scenario using the new object denomination.. e.g. a scenario including BS_FileServer_DEV in development is called BS_FileServer_TEST in test..or worse..we could have the BS object transported and as a result we would have a BS_FileServer_DEV object in integration directory of our test environment...

Is this the right path?

Thanks,

Matias.

[MichalKrawczyk · Accepted solution]

Hi Matias,

>>>Is this the right path?

I would change it a little bit:

- if you need to change the name of the business service don't use

a business service - create a business system in SLD (and technical system)

- of type 3rd party

and you're business system names will change automatically

during directory export/import procedures just like

for R3 business system (after correct entries in SLD - transport groups)

if you don't need to change the name just leave it as a business service with one name

>>>>and then create the logical system "LS_FileServer" in R/3, to

you can also use one logical system (XI logical system)

for all XI communication

the approach is to use header mapping in receiver agreement

described in my book:

<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member · Accepted solution]

Hi Michal !

Ok, things are now a little bit clearear.

Suppose we don't need the name of the service to change, and we keep using the business service object... what do you mean with:

"you can also use one logical system (XI logical system) for all XI communication"

and about the header mapping, we understand that we only need to use it when who sends the IDOC to R/3 is a BPM...and use sender service = business service who triggered the scenario, for example.

Thanks !!

Regards,

Matias.

[MichalKrawczyk · Accepted solution]

Hi,

>>>>and about the header mapping, we understand that we only need to use it when who sends the IDOC to R/3 is a BPM...and use sender service = business service who triggered the scenario, for example.

you can always use it

>>>"you can also use one logical system (XI logical system) for all XI communication"

you can use it in all IDOC scenarios and put XI business system

in this header mapping but it's just one way of doing it

you can also use one ssytem per one real sender receiver

Regards,

michal

[Former Member]

Hey,

When a technical system is defined for a product / s/w comp version we also enter the parameter for logical system name. If a buisness system is defined for a technical system then it in turns refers to the technical system with buisness system assigned to it.

Itz lyk linkage of <b>PRODUCT -> S/W COM VERSION -> TECHNICAL SYSTEM (LOGICAL SYSTEM) -> BUSINESS SYSTEM</b>

As per file to idoc scenario where <b>BUSINESS SERVICE</b> is used it doesn't refer to technical landscape so there is no question of Business system. With relevance to transports.

With File -XI-Idoc scenario the concept of logical system only comes into picture if we have a integration process also involved in the scenario. Where in adapter specific identifiers we specify the logical system name of the sender file system.

Integration Repository.

1) The Software Component version need to be same in all the landscapes that is a prerequisite else transport will fail.

Integration Directory:

2) Assuming that transport is being done for all the objects under a service and the objects has been transported to the test landscape business service with same name will be create in test sys only address and access parameters that have to be entered again and the change list has to be activated.

I haven't tried exporting individual object from ID so no clue.

Please refer the following link<a href="http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm">Transporting XI Objects</a> .

Hope itz helpfull.

Cheers,

*RAJ*

*REWARD POINTS IF FOUND USEFULL*