Skip to Content
Product Information
Author's profile photo Jisa Mathew

Solution Order Extensibility – Part 1: Process Extensibility

Introduction

In this blog, I would like to show how you can use extensibility options in the context of solution order and its follow-up business transactions.

Extensibility in SAP S/4HANA Cloud provides options for customers and partners to build extensions. Key users can make custom fields available in several apps, including handing over data by using business scenarios. This blog series aims to show how you can use different aspects of solution order extensibility to fulfil your individual extension requirement.

This blog series is split into the following parts which will be made available gradually:

  • Process extensibility (this blog)
  • OData API extensibility
  • UI extensibility
  • Progress extensibility
  • Analytics extensibility

What is solution order?

The solution order management provided by SAP S/4HANA Cloud is designed to provide innovative business offerings by combining sales, related services, service contracts, and subscriptions as a solution bundle. This provides flexibility to the customers by enabling them to adapt to new business models and helps in creating a competitive edge to boost their business. This also supports the transformation journey from a pure product business to higher-margin services and subscription business.

Solution order management provides an end-to-end process of sales and fulfilment of the solution bundle. The fulfilment of solution order is done by various follow-up business documents and the solution order provides the latest view of their current state. Solution order reference is used for the billing and finance process.

When to use process extensibility?

 The solution order end-to-end process includes multiple business documents. Process extensibility is useful when you want to enable a custom field throughout the whole business process. When creating a custom field, you can configure it to transfer its content automatically to follow-up process steps in the same tool.

For example, if you want the extension field created in the sales order to be automatically available in the customer invoice created from that order, you can achieve this by enabling a suitable business scenario for the custom field. You can use process extensibility to enhance the business process starting from solution order to journal entries.

How to achieve process extensibility in solution order?

To enable custom field across the business process, you can follow the steps below:

  • Login as administrator in the Custom Fields and Logic application.
  • Create a custom field by selecting the suitable business context (for example, Service Header and Service Item). The business context “Service Header” is used to create custom field in solution order header and “Service Item” for item in solution order.

  • Click “for the relevant business scenario (for example, service header to sales document) for the custom field.

          Note: All the data transfers corresponding to the business scenario are listed.

  • Publish the custom field after enabling the business scenario.

  • The custom fields are good to use once enabled via API or UI.

The value of the custom field will be transferred between the corresponding documents by enabling the appropriate business scenarios.  In the scenario overview below, you will find a letter indicator. With this indicator, you can identify the appropriate business scenarios that have to be enabled in the tables below.

Header Level:

Item Level:

Let us now look at an example of extending business process from solution order (service contract item) to accounting document.

The custom field ‘YY1_SOLOH_2_LEDGER’ in service contract item of solution order is listed below.

The custom field has to be propagated from the beginning of the process chain. Create the custom field in the context of the Service Item. The custom fields get business context dependent name suffixes like ‘YY1_SOLOI_2_LEDGER_SRI’. Enable the business scenario “Service Item to Sales: Billing Document Item”, a new field ‘YY1_SOLOI_2_LEDGER_BDI’ is added to the billing document item. You can go to the context of the Billing Document item and enable the business scenario “Billing Document to Journal Entry on Item Level” to propagate the field to journal entries.

This custom field is transferred to the respective follow-up documents through the enabled business scenarios as listed above.

Known limitations

  • There is no support of process extensibility for subscription billing item yet.

Conclusion

 In this blog you have learnt how and when to use extensibility options for solution order and its follow-up business transactions.

Reference

Solution order orchestration

Extensibility in SAP S/4 HANA Cloud

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.