cancel
Showing results for 
Search instead for 
Did you mean: 

BRF+ different behaviour on dev clients

che_eky
Active Contributor
0 Kudos

Hi,

I have changed an existing Application in BRF. The changes include adding a new column to an input structure, new column to an output structure and a new decision table. In the backend ABAP system client 300 is dev and 310 is sandpit. In client 300 the API works fine and returns the new output column using the decision table. But in client 310 the new output column is not populated. From client 300 and 310 I am passing the same values to the BRF call, but the result is different.

Should both clients regenerate code when changes are made in BRFplus?
I did notice that some of the structures I updated in BRF were not updated in client 310. So I had to run the DDIC binding refresh program FDT_DDIC_BINDING_UP_TO_DATE. I did not have this issue with client 300.

Is it possible more objects are misaligned between the two clients? How could this happen?

Ryan-Crosby
Active Contributor

Did you import your customizing transport into client 310?

Accepted Solutions (0)

Answers (3)

Answers (3)

che_eky
Active Contributor
0 Kudos

Thanks to you both, it was resolved with SCC1 :0)

che_eky
Active Contributor
0 Kudos

Hi nanikus

Yes it is indeed defined as Customizing and there are too many FDT000 entries for me to copy to a new customizing request. Is it ok to SCC1 the complete request?

che_eky
Active Contributor
0 Kudos

Hi ryan.crosby,
Do you mean workbench transport? I have a workbench transport with Customizing table contents for FDT000.

Nana
Explorer

Hi Che,

it seams that your BRF+ application is defined as customizing. Could you check this in application's general window, under storage type:

The funny thing with BRF+ is, that even though you have a customizing application, you can still put your changes into workbench transport. If this is the case with your application, I would suggest you transfer FDT000 entries into new customizing request and do a client copy (SCC1).