on 03-01-2011 11:10 AM
Dear experts,
is there any way to create a tranport target for buisness service like we do for buisness system.
we have buisness services which needs to have different names in develpment and production.
how to do it .. please give suggestions
Thanks,
Aju
> we have buisness services which needs to have different names in develpment and production.
Use business systems and not services.
The idea of a business service is just the identity of names in dev and prod.
Mainly used in a B2B process to have a unique identifier.
In an A2A process you should not use business services at all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Stefan,
thank you for your reply ..
Is there a specific advantage of using buisness system instead of buisness service if the same name is allowed in both development and production ? we have a system where even A2A scenarios are using buisness services ... in this case what are the
limitations compared to buisiness systems ..
in buisness systems the interfaces are available in ID since the product is linked to the technical systems. If that link is broken after the ID configuration is done will it affect message flow in runtime...? pls help ...
Thanks,
Aju
Hi,
If the link gets broken after creating the objects in ID the message flow wont gets affected...
because runtime wont validate the interface names and namespaces available(take example of file to file scenario with out IR objects..) so obviously it wont check the link between them...
Apart from the above take the case of the business systems once the objects gets transported to other environments..will not have any link between the product and business systems in that case..
I strongly believe Business systems play a crucial role only in case of integration between SAP Systems only..( for determining the sender business systems in case sender system is SAP )..
HTH
Rajesh
If that is the case then create business system in SLD as third party system
chirag
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
What Puneet said is correct, we cant create the transport target to the Business service.
Use common name in all environments.
Regards,
Phani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>
> Hi ,
>
> Now the situation is we have buisness service with different names in development and production just like the way it happens in the case of buisness systems .. but can't figure out how it happens .. could you pls help.
>
> Thanks,
> Aju
this might be because the configurations were manually created and not transported.
Note that there is no transport mechanism that changes the name of a business service. Only Business systems can be assigned paths that result in their names being changed
Yes, its a common problem.
Business service created in ID can be transported between environments but the Name cant be changed.
So a better approach would be to keep the Business service/component name constant across the system or use it as a 3rd Party Business system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.