Changes are not reflected into SEM-BPS 1 layout.

[Former Member]

Hi,

1st, I've included code in SAPAfterDataPut that copies data from SEM-BPS 1 into New Sheet.

Now, I've inserted a method in the sheet module of New Sheet. This method takes care of reflecting changes from New Sheet into SEM-BPS 1 layout. but, finally am not getting changes back to SEM-BPS 1 sheet.

I've tested this in excel (outside of BPS) and it works fine.

in BPS, I went into VB debugging mode (after inserting a break point) and I can see that change that has been made in New Sheet was reflected back to SEM-BPS 1. But, when i test the same out of debugging mode, am not getting the same result.

Looks like,after changes in New Sheet, SAPAfterDataPut is again being executed and is overwriting the changes that I made in new sheet.

Do i need to inlclude code only in SAPBeforeDataPut to reflect changes from new Sheet into SEM-BPS 1?

In excel (outside of BPS), this method works in such a way that, as soon as i make changes in Sheet2 will get reflected into Sheet1 without runnning any macro.

but, with same code, this doesn't work in BPS. (instead of reflecting changes to SEM-BPS 1, changed value in New Sheet is reverted back to original value that is same as the value in SEM-BPS 1)

Appreciate any ideas/thoughts on this.

[gerd_schoeffl]

Hi,

Usually you work with a second sheet in the following way: write a macro that copies the data from the SEM-BPS 1 sheet to the new sheet. In order to run that macro include it into the macro "SAPAfterDataPut" and set the flag in the check box of in the popup of the third screen of the layout builder. The system will call the macro after the data has been written to the sheet SEM-BPS 1.

There is a second predefined macro that the system will executed provided that the flag is set on the popup in the layout builder. This macro is called "SAPBeforeDataGet". It is called before the BPS reads data from the SEM-BPS 1 and should be used for transferring the data back to the first screen (similar to the coding you have done in SAPAfterDataPut). Using this macro should solve your problem.

I did not understand how the changes are transferred from the new sheet in your (stand alone) case. Unfortunately it sometimes does make a difference if you test a macro in a stand alone Excel or in the Excel inplace. Some features are disabled in Excel Inplace (by Microsoft!!).

Best regards,

Gerd Schoeffl

SAPNetWeaver RIG BI EMEA