Purpose
A new object service should be generally usable for business objects of various types. Individual services that are only valid for specific applications go against the aim of object services. The object services are user friendly because they are uniform and cross-application. The object service should always refer to the object that the user is currently editing (therefore, the published object).
Prerequisites
The object must be entered in the
Business Object Repository (BOR).Process Flow
Result
Your service is available for the business objects that are connected to the object services and that have not explicitly excluded your service.