Skip to Content

Bind xbo field in Embedded Component on Account TI screen

We are adding an Embedded Component on the Account TI screen. It has an AdvancedListPane which should list custom BO instances for the current AccountID. The AdvancedListPane does not get filled.

We have experience with similar solutions with an EC in a custom screen. With an EC as an extension in a standard screen it doesn't seem to work.

It would be very helpful to check in debugging if the EC inport AccountID parameter gets populated correctly from the Account outport. For this the inport parameter needs to be bound to a field in our xbo:

However when we bind the inport AccountID parameter to a field in our Customer BO extension (xbo) we get an error when navigating to the Account TI screen:

Error:
500 SAP Internal Server Error

ERROR:
The application running deliberately caused an abort with short dump.
(termination: RABAX_STATE)
    at new a
(https://c4cstatic.hana.ondemand.com/resourcesvc/1802.2.1.0.1520269980943/SAP_UI/HTML5/resources/sap/client/lib-0.js:310:378)
    at constructor._fireErrorOnDispatch
(https://c4cstatic.hana.ondemand.com/resourcesvc/1802.2.1.0.1520269980943/SAP_UI/HTML5/resources/sap/client/lib-0.js:605:7515)
    at constructor.
(https://c4cstatic.hana.ondemand.com/resourcesvc/1802.2.1.0.1520269980943/SAP_UI/HTML5/resources/sap/client/lib-0.js:605:4399)
    at 
Gebruikersinterfacecomponenten en
applicatieondersteuningscomponenten van huidige aanvraag:

object

Description:

500 SAP Internal Server Error

ERROR:
The application running deliberately caused an abort with short dump.
(termination: RABAX_STATE)

ClassName:
sap.client.evt.BaseOperation
Type:
Error
Function_name:
sap.client.evt.BaseOperation.prototype._digestResponse
Transaction_id:
00163E11A6691EE888F17FFF3556D678
Root_context_id:
00163E11A6691EE888F17FFF35563678
Controller:
EventProvider
sap.client.controller.ComponentController
Callstack:

The same error occurs when we try to fire a BO action which is defined in the xbo from the EC event handlers.

Any suggestions on why it is not possible to bind xbo fields in the EC or to fire a xbo action from the EC?

Any suggestions on how to check if the inport AccountID parameter is filled correctly from the Account outport?

blog-image-1.jpg (2.5 kB)
blog-image-2.jpg (37.8 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 10 at 11:43 AM

    Hi Maiko,

    you should not bind your inport parameter with your BO field. Instead fire an event in your inport and get your BO instance in the event with BOOperation Read. Here you can pass your inport parameter.

    Regards, Achim

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Maiko,

      I think the type keyNavigation is not correct. There is a special type for alternative keys. But when I embedded BusinessPartnerSolutionExtensions into Customer TI, I used the AccountUUID.