Configuration Tree Maintenance
To maintain the runtime “field status” of a field in any Promenta Webflow process (e.g. Material Master, Vendor Master, Customer Master or other), you should follow these steps:
Make sure that you carry out all changes in your configuration client in your SAP development system. You will always be prompted to save your changes in an SAP customizing transport which you can use to transport your changes through the SAP landscape to Production following your own internal technical change management procedures (this will align the full SAP landscape with your changes).
Steps:
- Run transaction code /PROMENTA/DEC_TREEV3
- Enter the name of the configuration tree you intend to maintain. This generic example depicts a material master configuration tree. The structure will be the same regardless of the process you are maintaining e.g. material, vendor, customer etc. (Note that you should not change any configuration trees that are in the /PROMENTA/ or /PRMNTCUS/ namespaces. If you do there is a risk that your local changes will be overwritten the next time Promenta deliver a software patch to your organization. The correct process to follow is to copy the nominated standard Promenta configuration tree to a replica configuration tree in the “Z” namespace, which your company will own. You can then override the Promenta standard tree with your own configuration tree which you created in the “Z” namespace. Please access this link to find guidance on copying and overriding configuration trees).
- Select the change radio button then click the execute button on the application toolbar
- The first screen will look similar to the screen below on first entry. The two folders where Promenta authorize customer changes are highlighted in the image below (i.e. DataFlow Fields and DataFlow Defaults). In all other cases customers are requested to contact Promenta support for further assistance using support@promenta.com or raise an enhancement request ticket
- Refer to the specific sub folder for more information on maintaining DataFlow Fields and DataFlow Defaults
