To save data properly using Behavior definition Data mapping is important. As of now field names are different in our BO entity and the table /dmo/travel_m where we want to store the data.
Travel Entity:

Travel Table:

For example Root entity field is TravelId and table field is travel_id.
Let’s start with mapping.
- Open the BDEF ZHA_SA_TRAVEL and add mapping fields for /dmo/travel_m,
managed implementation in class zbp_ha_sa_travel unique;strict ( 2 );define behavior for ZHA_SA_TRAVEL alias Travelpersistent table /dmo/travel_mlock masterauthorization master ( instance )etag master LastChangedAt{ create ( authorization : global ); update; delete;// field ( readonly ) TravelId; association _Booking { create; }mapping for /dmo/travel_m{TravelId = travel_id;AgencyId = agency_id;CustomerId = customer_id;BeginDate = begin_date;EndDate = end_date;TotalPrice = total_price;CurrencyCode = currency_code;BookingFee = booking_fee;LastChangedAt = last_changed_at;LastChangedBy = last_changed_by;CreatedAt = created_at;CreatedBy = created_by;OverallStatus = overall_status;Description = description;}}define behavior for ZHA_SA_BOOKING alias Bookingpersistent table /dmo/booking_mlock dependent by _Travelauthorization dependent by _Traveletag master LastChangedAt{ update; delete; field ( readonly ) TravelId; association _Travel; association _BookingSupplement { create; }mapping for /dmo/booking_m{TravelId = travel_id;BookingId = booking_id;BookingDate = booking_date;CustomerId = customer_id;CarrierID = carier_id;ConnectionId = connection_id;FlightDate = flight_date;CurrencyCode = currency_code;BookingStatus = booking_status;LastChangedAt = last_changed_at;}}define behavior for ZHA_SA_BOOKSUPPL alias BookingSupplpersistent table /dmo/booksuppl_mlock dependent by _Travelauthorization dependent by _Traveletag master LastChangedAt{ update; delete; field ( readonly ) TravelId, BookingId; association _Travel; association _Booking;mapping for /dmo/booksuppl_m{TravelId = travel_id;BookingId = booking_id;BookingSupplementId = booking_supplement_id;SupplementId = supplement_id;price = price;CurrencyCode = currency_code;LastChangedAt = last_changed_at;}}
Save and activate
2. We will check if we are able to save data now.
3. Run the application



Click on create button to create the travel data
Enter details and Click create

Create Booking details


Create Supplement Details


Object is created

Now, let’s see the Travel ID in search.
As you can see Travel ID created successfully with managed behavior definition.

Thanks for reading!

Leave a Reply