Extend the Manage Purchase Order FIORI app (F0842A) with an existing field from EKPO

[jay_d1]

Hello All,

I am still new to FIORI app extensions, so your feedback is much appreciated. I have the following requirement.

I need to extend the Manage Purchase Order App (F0842A) with an existing field from EKPO. The extension needs to occur at the Item level of the Purchase order since the field is from EKPO. And the field should also be available when one tries to create a purchase order via the app.

I tried to achieve this using CDS view extension but it is failing. I have extended the following CDS views:

E_PurchasingDocumentItem----->I_PurchaseOrderItemTP------->C_PurchaseOrderItemTP.

I am able to see the data in SQL viewer but while trying open the FIORI app, it throws a dump stating the following:

From the error, I understand that the field I am using in the CDS views needs to be incorporated in the table PURORDITMTP_D. And here the extension is done by adding the field in EKPO_INCL_EEW_PS. But this is creating an entirely new custom field and defeats the purpose of using the existing field from EKPO.

Could anyone please guide me through this? Is this even possible with CDS extension ? Or do I need to look for FIORI APP extensibility project to achieve this requirement?

Thanks in advance.

[jay_d1]

Thanks for the response. But the field is not a custom field. It's a standard field BEDNR in EKPO.

[junwu]

if it is an existing z field:

1.revert what you have done

2.tcode: scfd_eui convert that z field to a field which is recognizable in custom field&logic app

3.go to custom field &logic app to enable the field for fiori screen(if not yet).

[jay_d1]

Hello,

[jay_d1]

Thanks for the response. But the field is not a custom field. It's a standard field BEDNR in EKPO.

[junwu]

how about just adding that field to PURORDITMTP_D using append?

[jay_d1]

Adding the field in PURORDITMTP_D treats it as a new custom field and if I use the standard field name "BEDNR", it gives an error.

So then I need to define the field with a different name, In that case how do I make sure the data from EKPO field is porpagated to this extension field?

Because these two will be treated as separate fields.

Regards,