Product Modeling for the OData Service

Product models in the Product Finder and Configurator in the Interaction Center scenario can be reused directly in the OData service if their user interface supports this.

The service responds differently in some areas for security reasons. These areas are as follows:

  • In the standard system, all visible attributes for product determination objects are provided.

  • The standard system can be influenced during attribute maintenance using the new field External Visibility. This enables you to hide PDO attributes and value helps and to display result attributes.

  • In the standard system, no attributes are provided for results.

  • Invisible attributes are not generally provided using the service.

You can generally influence the response for all rules by querying the user or the active OData service. This applies to the following functions:

  • Attribute description

  • Value determination

  • Results list

  • Configuration

  • Visualization

  • Descriptions

  • Input helps

The following options have been added to the presentation control for the attribute specifically for the OData service, which can be accessed by choosing Enhance Result Context from the menu:

  • Override attribute description (IUR_DESCRIPTION)

  • Symbol URL (OData) - for external usage, that is usage beyond the Interaction Center. The user can use this URL to load a certain symbol for a specific attribute or product.

  • Additional information for visualization and notes about response on the user interface.

  • Option COMBINE_WITH to link fields so they are displayed jointly (such as name/first name, street/house number or value range slider).

  • Additional render types that you can only use in the OData service. These are as follows:

    • Button

    • Slider (with Range From,Range To, value step)

  • Accordion

  • Multiple Selection

  • RoadMap

The Picture and Additional Information columns have been added to the product list, which are also only evaluated in the OData service.

OData Service – Function

The service is designed to supply all of the data to be visualized after each entry. Data should be therefore sent to the back-end system and the new data received following every change. The attributes and value helps that are changed here are selected using value updated and value help updated. For more information, see the section Model for OData Service.

Save Document and Subsequent Processing

Since the service is designed to be used by anonymous users, direct creation of quotation and contract documents is not supported. However, you can trigger saving from product modeling.

This can be triggered using the following two options:

  • By performing value determination for a field, for example to determine and display a reference number simultaneously.

  • As a product action, for example as a response to a value change, for example for a button or a RoadMap.

You schedule the method CL_CRM_ISU_ORDER_REF=>SAVE_AS_DOCUMENT for this. You can also create an optional workflow event or task here. We recommend selecting one of thse options or developing your own link, since this is necessary to be able to locate the document again at a later stage.

If you choose the Task option, a support employee can then open the task in the inbox, navigate to a stored PFC document and transfer this to a new PFC document for data transfer and correction. Specific BRFplus events can be used to transfer data entered to the identification as required. When you save, the document is locked for changes and a success message is sent.

Technical Information

Relevant data is stored for each click in the table CRMD_PFC_ODATA /CRMD_PFC_ODAT2. It is not stored in document tables until modeling prompts the user to save.