In SAP Build Apps, what are some classic data entities available? Note: There are 2 correct answers to this question.

Question

Options

• AOData Integration
• BRFC Integration
• CREST API Direct Integration
• DSOAP Integration

• A
  88% (23)
• B
  4% (1)
• C
  8% (2)

Explanation

In SAP Build Apps, Classic data entities are the legacy integration types built directly into the platform's data layer. OData (A) is correct because it is a standardized SAP-native protocol widely used to connect to SAP backends (like S/4HANA via SAP Gateway), and has been a foundational data entity type since AppGyver days. SOAP (D) is correct because it is a classic XML-based web service protocol supported as a built-in classic data entity for integrating with older enterprise services.

RFC Integration (B) is wrong because RFC (Remote Function Call) is an SAP-proprietary protocol that is not directly accessible as a classic data entity in Build Apps - it must be exposed via an OData or REST wrapper first. REST API Direct Integration (C) is wrong because REST integrations in Build Apps are handled under a different category (typically via the "REST API" resource type), not classified as a "classic" data entity.

Memory tip: Think "Classic = Old-school web service standards." OData and SOAP are both mature, standardized protocols with long histories in enterprise integration - that's what makes them the classic pair. RFC is SAP-only and not directly supported, and REST is modern, not classic.

No community discussion yet for this question.