We would like to share few common questions and some of the best practices which can be adhered during creation of business configuration contents.
Below is the list of common questions on Business Configuration related to the SAP Cloud Applications Studio, that we frequently receive from partners and customers and we will keep adding new known scenarios to this list.
Q.1 I created a BCO, deployed it to a target system. In the source, I then deleted the BCO and created another with the same name as the deleted one but with different fields in the same patch version. When I deploy this patch to the earlier target, why am I getting BCO activation errors?
Answer- This is because you deleted a BCO and created another with the same name as the deleted one in the same patch. If you want to change the field names of an already delivered BCO then
Create the BCO with different name and deploy to target.
Delete the required BCO in a patch version, deploy to the target system and then in the next patch version, create a BCO with the same name as deleted one and required fields and deploy to target system.
Note - If the BCO is used in a Business Object (BO) then you will not be able to delete the BCO since it is used in other objects.
Q2. Why am I unable to delete specific BC Set entries/values in maintenance mode i.e., solution is already assembled, and a patch is created?
Answer - Deletion of delivered BC Set entries/values in maintenance mode is not allowed.
You cannot delete specific rows in BC Sets. You can only change values for fields of type description. If you need to correct values in entries that are in maintenance mode, the only option is to delete the whole BC Set, create it again with required values.
A good practice if you need to change the entries in a BC Set in maintenance mode would be to create fine-tuning activities and add/remove entries from the BC UI.
Q3. Why can’t I see the fine-tuning entries I created in my source tenant after I deploy that solution to a target?
Answer - Fine-tuning entries are solution and tenant specific which means that when you deploy a solution to another tenant, fine-tuning entries are not transported with the solution zip file. You need to maintain them explicitly in each tenant where the solution is deployed.
Some of the best practices that partners/customer can follow to avoid getting errors when working with Business Configuration contents.
Recommended length for BC Set names is less than 20. If you need bigger names, make sure the first 20 characters are not the same.
Do not change the ordering of BC View by opening it in UI Designer. This will lead to activation error in UI Designer
Do not create a patch for solutions that contain BC Sets created on SAP BCOs. BC Set creation on SAP BCOs is only possible in partner development tenant and not in a test tenant.
Do not change/edit the translation related XLF files that are exported from the SDK in a text editor (ex. notepad) because, some xml tags can get deleted by mistake which will lead to translation not working on import. Always use any translation tools to edit the XLF files.
If you want to edit values of BC Sets, make sure that any foreign key references of these values are adjusted before making the changes. Foreign key references are those references when values for a field in a BC Set come from another BC Set.
Hoping these pointers will be refereed during your development activities to avoid these known issues of Business Configuration Contents.
sasikanth.velagaletibsneha Thanks for your contribution to this blog.