C_BRSOM_2020 · Question #62
Which classes can you use to define the structure of a Web service-accessible object which is visible in SAP S/4HANA Service: SOM? There are 2 correct answers to this question.
The correct answer is A. Range table class B. Mapping table class. In SAP S/4HANA Service: SOM (Subscription Order Management), Range table class and Mapping table class are the two recognized class types used to define the structure of objects that can be exposed and accessed via web services. Range table classes define interval-based…
Question
Which classes can you use to define the structure of a Web service-accessible object which is visible in SAP S/4HANA Service: SOM? There are 2 correct answers to this question.
Options
- ARange table class
- BMapping table class
- CCharged item class
- DChargeable item class
How the community answered
(62 responses)- A89% (55)
- C3% (2)
- D8% (5)
Explanation
In SAP S/4HANA Service: SOM (Subscription Order Management), Range table class and Mapping table class are the two recognized class types used to define the structure of objects that can be exposed and accessed via web services. Range table classes define interval-based parameter structures (e.g., defining valid ranges for pricing rules), while mapping table classes define input-to-output value mapping structures - both are formal, configurable object templates within SOM's service layer.
Option C (Charged item class) is incorrect because a "charged item" describes a billing result - something already processed - not a class type used to define a web service-accessible object's structure. Option D (Chargeable item class) is a plausible-sounding distractor related to billing, but it is not a recognized class category for defining web service object structures in SOM; it conflates the concept of a billable entity with a structural class definition.
Memory tip: Think "R-M" - Range and Mapping are the two structural class types that shape what the web service sees. The "charged/chargeable" options describe billing states, not structural blueprints - if it sounds like an invoice term, it's probably wrong here.
Topics
Community Discussion
No community discussion yet for this question.