Ansicht
Dokumentation

ABENBDL_TYPE_MAPPING_ABSTRACT - BDL TYPE MAPPING ABSTRACT

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

- Mapping, Abstract BDEF

Type mapping

... mapping for PartnerType ...

Deep mapping

... deep mapping for NestedDeepDDICType $[corresponding$]
   {
      EntityComp1 = PartnerComp1
     $[...$]
     $[sub _Compos1 = Partnersub1$]$[,
      sub _Compos2 = Partnersub2$]
     $[...$]
    }
...

Alternatives:

1. mapping for PartnerType ...

2. deep mapping for NestedDeepDDICType ...

Effect

RAP type mapping maps data types of the abstract BDEF to DDIC partner types. If the DDIC partner type is a flat structure and only elementary data types are mapped, flat type mapping can be used. If the DDIC partner type is a nested or deep structure, deep mapping can be used. It defines a mapping for nested table components or substructures.

Alternative 1

mapping for PartnerType ...

Effect

To map elements to flat DDIC structures, type mapping using the syntax mapping for PartnerType can be used. The syntax is the same as for managed and unmanaged RAP BOs and it is described in topic CDS BDL - type mapping.

Alternative 2

deep mapping for NestedDeepDDICType ...

Effect

In an abstract BDEF with hierarchy, mappings can be defined between the generated hierarchical derived types and nested or deep DDIC types.

Such a mapping must be introduced with the keyword deep.

The optional addition sub can be used for sub specifications. Child entities with a composition cardinality > 1 can be mapped to nested table components. If the composition cardinality is <= 1, a mapping to a substructure can be defined.

Syntax for sub specification:

sub _Compos1 = Partnersub1

The left-hand side of a sub equation sub _Compos1 contains the name of a composition association of the entity. The right-hand side contains the name of a component PartnerComp1 of the nested or deep partner type NestedDeepDDICType. The components that are mapped onto each other must match, both must be either tables or structures. To cover the full hierarchical derived type, such a mapping must be defined for every entity in the abstract composition hierarchy and its corresponding partner type, with sub specifications for child entities at each level.

Example

The following abstract BDEF defines the behavior for three nodes of a CDS composition tree. For each entity, a mapping to a partner type is defined.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 4969 Date: 20240512 Time: 100616     sap01-206 ( 61 ms )