Skip to Content
-1

Transport BRF+ table cross client

Oct 21, 2016 at 05:55 PM

213

avatar image

Hi Experts,

I made a custom change request and filled the decision table. the custom changes are in a TR in one of the Dev client.

When i am trying to use SCC1 transaction to move the changes to another client of same system, i cannot see the decision table entries in rule based workflow for that custom change request.

I also tried to write my application to a TR using FDT_HELPERS, and than tried SCC1. i do not see any error in the SCC1 log as well.

Also i made sure the BRF editor is closed before doing the transports.

Any hints will be highly appreciated.

Thank You, Shaila.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Christian Lechner
Oct 29, 2016 at 08:08 PM
0

Hi Shaila,

what is the type of the application your decision table is assigned to? Is ot customizing (and hence client dependent)?

Best regards

Christian

Share
10 |10000 characters needed characters left characters exceeded
Shaila Kasha Nov 02, 2016 at 11:57 PM
0

Hi Christian,

Thank you for your message.

Yes, it is customizing and transportable. The issue is resolved now. SCC1 copied the DT to a different GUID in the target system.

However, i have few questions

1) when we configure rule based workflow, we generally provide the CR type and start entering the DT entries. This can be done using MDGIMG->Process Modelling-> Rule based workflow-> Configure rule based workflow, OR Tcode UMSD_SSW_RULE

2) once can also user BRFPLUS tcode to see the catalog/application- but how is this different from USMD_SSW_RULE

The issue is USMD_SSW_RULE and BRFPLUS displays different DT for the same CR type in our system. coz it is stored under different GUIDs.

Thank You,

Shaila.

Share
10 |10000 characters needed characters left characters exceeded
Christian Lechner
Nov 03, 2016 at 07:25 AM
0

Hi Shaila,

I am not a MDG expert and have no system to look up the detail behind the Tcode, so mor guessing than proven facts:

Usually the rules should be the same no matter which transaction you use to display them. The only difference that can cause such an issue is that the decision tables are client dependent and, as you already mentioned, get different UUIDs. So you should chekc if both transactions lead to the same client or not.

In addition it would make sense to add as secondary tag a master data governance related tag, so that the experts from that area can also take a look at this question

BR

Christian

Share
10 |10000 characters needed characters left characters exceeded