#UPDATED SAP S/4HANA 2022 Sometimes customers need a special field that is specific for their business since it could be used to make decisions. I have certainly come across this scenario more than once. You may use any kind of standard field to cover the requirements, I have used it this way and it worked perfectly. But sometimes there are no more fields to reuse. In ECC this scenario needs special attention and several tasks. Those tasks include custom code such as adding the field, including the field in several documents in the process. If you need this field for outputs determination, you also need to add this in the “Field Catalog” by development too. At the same way if you need this field in pricing determination again you need custom code. In most of these cases this field should be a primary key because it will be an important filter/grouper in reports and analytics.
Now in SAP S/4HANA this scenario can be covered in a few simple steps and without any developments.
In this Blog I will share to you a Business Case with this kind of requirement, including the custom field in some business contexts.
Business Case – Description.
After analyzing different ways to include a header data in the Sales scenario across the whole end-to-end process, the conclusion is that we need a custom field. Some details regarding the requirement:
Header field – CHAR (2)
The field should be in the Sales Document, Delivery document and Billing Document
The field should be fill in the Sales Document (Creation/Change) copy to the Delivery Document and could be update in it too.
Depend on the field value the Sales will have a particular discount.
And finally, and obviously this field must be shown in some Analytical Fiori apps.
It is great how many things we can do from a simple, intuitive, and powerful tool. If you come from an ERP, at the end of this blog I am confident, you will agree with me!😊
Let’s Get Started!
Step 1. Execute the app. “Custom fields & Logic” (App ID. F1481). We will work only in “custom fields” tab in the whole configuration. First, we will create the field and define attributes, here an explanation about each one:
Business Context -> Is where the field will be used. In our case we need this field in Sales Area and in Sales Document.
Label -> You can define the name of the field, then the app. will create the field by the name ZZZ-Label (Identifier)
Type -> You can define the type of field (checkbox, number, text …). In our case a text.
Length -> when you define the Type, then ask you for the length but it depends on the type of field. In our case 2.
Please, see this video to view our case configuration step by step:
The field has been created in table VBAK (Header Sales Document), you can verify in trx. SE11 :
Step 2. We need the field in the Header Delivery document and in the Header Billing document. To do this we will include the field in the Business Scenario “Sales document to Billing Document on Header Level” and in “Sales Document to Delivery Document on Header Level”.
Please, see the step by step in this video:
The field has been created in table LIKP (Header Delivery Document) and in VBRK (Header Billing Document), you can verify in trx. SE11 :
And depending on the business context where it was enabled, the field value will be copy from the Sales Document to the Delivery Document and from the Sales Document to the Billing Document too.
Step 3. The field could be filled/displayed or changed in the Sales Document and could be displayed or changed in the delivery. To include it in these business contexts, please follow the steps I share with you in this video:
At this point you can check the field by creating a Sales Document, then a Delivery Document in reference to that sales order. Also, an invoice in reference to the sales document. You can see the field has copied to the delivery and to the billing document and you can see the field in the maintenance/view in each Sales Document too.
For example, in the Scenario “Sales Order with Delivery”:
The Tab “Custom Fields” was created and there all customs fields.
Step 4. We need this custom field in our Pricing Control – Field Catalog.First we can check in the customizing that this custom field is missing:
Let’s include the custom field in the field catalog. Please, see the step by step in this video:
And check the custom field available in the field catalogue to use in the pricing determination: