Software Collection export failure due to dependent items in SAP S/4HANA Cloud
In my last blog post, I covered the importance of transporting software collections before a change project can be closed. In this blog post, I will cover a scenario that will occur in the event you have utilized the SAP S/4HANA Cloud In-app Extensibility feature that allows you to create custom fields for form templates and these custom fields are not included in the same Software Collection as the corresponding custom template.
The client has legal and business form requirements that do not lend themselves to the standard data sources in the SAP S/4HANA Cloud Platform pre-delivered Billing Documents. In this example, the client has three fields that were developed by utilizing the In-app Extensibility Feature provided by SAP to meet the legal and business form requirements.
Custom fields developed using the In-app Extensibility feature
After the custom fields were developed, they were added to the custom form templates, in this case, the Billing Documents. They are now ready to be added to the Software Collection and transported to Production.
SAP S/4HANA Cloud Platform requires that each custom field is in the same Software Collection as the form template that it is utilized in. Even though required it is possible to add custom fields in different software collections. In the event the custom field is not included in the same software collection, you will receive the below error and will be unable to export the Software Collection.
In this example, you’ll notice that YY1_INVOICE_CA has a dependent custom field YY1_ATFLICENSENUMBER. What this means is that for this error message to be resolved we must include YY1_ATFLICENSENUMBER in the same Software Collection as YY1_INVOICE_CA and repeat this process for the remaining custom fields. How this is accomplished is outlined in the steps below.
Adding a software object to an existing Collection
- Go to Export Software Collection app.
- Select the desired Software Collection.
- Once in the desired collection, select “Add Item” in the bottom right.
- Select the Custom Field you would like to add to the Software Collection and press OK.
- You have successfully added the missing item to the Software Collection.
- Repeat this step for each field that is missing and complete the Software Collection export.
In closing, this blog post is my effort to share with the community how to resolve this issue and reduce the time spent resolving this error. It was my goal to communicate that in the event you have created custom fields that are added to custom form templates, you need to add these fields to the same Software Collection as the corresponding custom form template. By doing so, you’ll save time and look like a pro when transporting your custom developments into Production.