on 06-19-2017 7:48 AM
Hi All,
I have a requirement to create a decision table in my development system and to transport this decision table to production. Once the decision table moves to production the user will create entries into this decision table.
As the decision table should be transported to quality and production, I have maintained the storage type as "customizing" ,"transportable". But with this settings even the entries are also being captured in the TR and also in quality it is requesting for transport whenever we want to create a new entry in the decision call.(Ideally this should not happen)
I have created this decision table inside the function mode.
I have tried to change the storage type setting to "Master" but in Master only "local" is possible that means the decision table cannot be transported. 😞
I have tried to use the application exit but still couldn't able to find any suitable solution.
Please help me on how to proceed with this.
Hi,
in BRFplus, in general, you have the two options you described:
There are some workarounds that you can use here:
If this is a common scenario in your development, it would make sense to take a closer look to the SAP Decision Service Management which allows the maintenance of BRFplus objects in a central system and deployment in any other system. For more information see: help.sap.com Decision Service Management
Best reagrds,
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As my my analysis there is no easy way of doing this activity without using SAP Decision Service Management.
If SAP Decision Service Management is not available, the workaround would be to create 2 applications, 1 application with the function (Customizing TR) and 1 application with decision table (non transportable Master). Transport the function and other thing of the 1st application and upload the decision table directly to the Quality/Production (manual activity). use the decision table in the function. 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Storage type Master is correct if it is to be maintained. An alternative to Christian's excellent input is to 'transport' using XML export/import from Dev into QA and Prod. A good approach is to use XML for the entire table and then use Excel export/import for backing up or maintaining the table contents.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
77 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.