Skip to Content

C4C: How to add a new column to a OWL (e.g. COD_Quote_OWL)

Hi there,

I have now a problem with extenstion in C4C world.

My task is to add a new column to the list in COD_Quote_OWL. The new column is the product description of the quote . If there are more than one products in this quote then just take the first one.

Actually I was able to define the new extension field by creaing Bussines Object Extension, and to add the new field as new column into the COD_Quote_OWL.OWL.xuicomponent as well. This new column called "Produkt" can then be displayed in Frontend (s. Screenshot).

I tried to fill this field using event like AfterModify or BeforeSave. But it didn't work. This new column is totally empty.

I also tried to use debug and breakpoints to analyse this issue. But it turned out, that the programm was stopped at NONE of those breakpoints .

Could anyone give me a hint or suggestion?

How can I gerenaly add new column to the list in OWL? How can I fill the value to this new column.

Thanks in advance

Siwei

newcolumn.png (24.1 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Sep 16, 2019 at 04:10 PM

    Dear Siwei,

    Hope you are doing well.

    In terms of your issue, you can extend (with PDI) SAP Solution UI Component screens by using the extensibility explorer functionality in the UI Designer.

    The usual process flow would be something similar to the following:

    1. Create your extension business object in the SDK.
    2. Add a PDI field to any node of your choice.
    3. Right-Click on the extension BO and choose enhance screens.
    4. Pick the screen you wish. You will get a xuicomponent file in the SDK now.
    5. When the UI designer opens for the screen you wish to change, you then check the pane / list pane etc where you wish to extend.
    6. Note: There must be an anchor to extend onto the SAP Standard Screens. If not, you will need to log a request to be evaluated by the application development.
    7. If you have selected an anchor for the mentioned place, then use the extensibility explorer to "Add extension field" to the screen.

    .

    I can see you mention that no scripts worked in this process. I can only image that no scripts worked in the process because the field is located on a node that has not been extended with ABSL scripts.

    What I mean is this scenario:

    1. Extension field on the Item node of BO.
    2. You have AfterModify script on the Root node of the BO.
    3. If you modify the field or any fields on the Item node, your ABSL script will NOT be called.
    4. If you then change a field on the Root node, your ABSL script WILL be called.

    .

    This is the only reason I can see (without looking) that the script did not get triggered. I would also recommend checking the debugging settings in the Admin settings in the SDK too!

    If this solve your issue, mark the response as answered!

    Thank you.

    Andy Blankley

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 24, 2019 at 03:12 PM

    Hi Andrew,

    thank you for your answer. I will try it out.

    Best wishes

    Siwei

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.