SAP S/4HANA create custom field and logic, transporting and delete process.

[serdarulgen]

Greetings,

SAP S/4HANA provides flexibility to cater to the customized needs of businesses. In this article, we will delve into the process of creating custom fields in SAP S/4HANA, the steps involved in customized logic development, and the process of transporting and deleting these customizations when necessary.

Firstly, when a need arises to create a new custom field in SAP S/4HANA, we will explore how this field will be defined and which data types it will support. Then, we will review the necessary steps for customized logic development to determine how this custom field will interact with business processes and optimize existing data flow.

Subsequently, we will move on to the process of testing and approving the customizations. At this stage, we will address how the development in SAP S/4HANA will be transported.

Finally, we will examine how to delete obsolete custom fields or logic developments from the SAP S/4HANA system. This process is crucial for preventing unnecessary data clutter in the system and optimizing performance.

This article will guide readers through the step-by-step processes of creating custom fields, logic development, transportation, and deletion in SAP S/4HANA, helping them better understand and implement these complex procedures.

With the standard Fiori app, a custom field is created, and it records data in tables. For example, if we take Sales-Delivery-Invoice, the data entered in sales can be carried over to the invoice.

1.CREATE CUSTOM FIELDS

The custom field role needs to be assigned to the user in SU01.

We access Fiori applications with the T-Code below using SE93.

When you enter "Custom Field" for English or "Özel Alanlar" for Turkish in the search field, the application will appear.

 

The first step is to create a project.

The critical aspect here is the business context. It's crucial to select the appropriate field in this area.

We are proceeding based on the sales document here. The label section qualifies the name we will give to the field. Accordingly, the descriptor is automatically filled. The descriptor corresponds to the technical name of the field.

The "Type" represents the data type of this field. Upon selecting this field, you will also be asked for the length value.

However, we should not be generous with the length in this regard. In SAP standards, we have limited rights. Therefore, field lengths should be provided according to the need, as updating them later can be quite challenging. Then, we proceed by clicking on "Create" and continue with "Publish." Afterwards, we can view the field with its technical name in SE11. The next step is to display it on the document and the tables associated with the document. For this, we need to activate it in the business scenarios and user interfaces. In my example, I proceeded with delivery, but you can carry it over to the invoice as per your requirement.

After publication, we can check the table and screens through the GUI.

In the VA01 screen, since I have included it in the header, custom fields can now be displayed below the user-defined fields in the header.

2. TRANSPORTING THE EXTENSIONS/ENHANCEMENT

Access the Fiori application "Configure Software Packages" and navigate to the option labeled "Add Registration." From there, choose the desired package. Subsequently, select the relevant Transport Request. Optionally, you can enable automatic Request and Task handling, allowing the system to autonomously generate Transport Requests and tasks.

Open the Fiori App "Register Extensions for Transport".

The system will automatically assign a Transport Request to the package. Alternatively, you can manually assign the transport request using the "Assign to Transport Request" button.

Find and select extension and click on the button "Reassign to Package".

After the process is completed, we observe that the fields created are associated with the request generated by the system.

3.DELETE THE CUSTOM FIELD

Deleting custom fields involves a technical process requiring ABAP dictionary activation. Depending on the application or business context, this process may involve numerous objects, potentially leading to lengthy runtimes.

If you're attempting to remove a custom field by disabling it from the app UI, and it won't be used by any other application, you can proceed with the following steps:

1. Log in to the Fiori Launchpad and search for the Custom Fields and Logic app.
2. Select the custom field intended for deletion. Before deletion, disable field usage.
3. Navigate through each tab (UIs and Reports, Email Templates, Form Templates, Business Scenarios, OData APIs, SOAP APIs, BAPIs, IDOCs) and ensure the field is disabled. If enabled, click "Disable Usage" and ensure it's disabled across all tabs.
4. Click "Delete." You'll encounter a prompt asking, "Do you want to permanently delete data?"
5. Confirm deletion. After a few seconds, you'll receive a "Deleted" message, and the screen will refresh.
6. Keep in mind that affected applications may become temporarily unusable during the publishing or deletion process

NOTE: If you are encountering a short dump despite performing deletion operations, it is advisable to check the table below. If you notice the field you deleted here, that might be the reason. Removing it from the table using table edit will resolve the issues. However, this could be due to an error in your actions. I must emphasize that this is not recommended.

After your deletion processes, your previously created request will be assigned a task, and you can perform the transportation processes.

You can contact us if you have any questions.