Skip to Content
avatar image
Former Member

How to change funcionality "Maintain Master Data" to RSA1 instead WebDympro (BW 7.4)

Hello Gurus,

Someone could help me?

In SAP BW 7.4 (Support Package 7) the BW master data maintain function moved from SAP GUI into web dynpro screen.

Can we use it (maintain master data) in SAP GUI RSA1 like SAP BW 7.3?


Is it a configuration in SPRO?


Thank you guys.


PS: It is my first project with SAP BW 7.4

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • Best Answer
    avatar image
    Former Member
    Feb 11, 2015 at 10:54 AM

    Hi All,

    I've found a way to get to the original GUI master data maintenance screen by setting an external break point in function module RSDMD_MDMT on line 281: IF L_USE_OLD_UI EQ RS_C_TRUE.

    When you click the maintain button in the infoobject maintenance screen it will start the debugger where you can change the value for L_USE_OLD_UI to X and then it will call the old UI.

    To be honest SE16 is less effort IMO but at least you can get to it if you really need to and if you wanted it long term you could change the code to set the variable permanently (probably best to make this a lookup to a table or user parameter so it can be changed easily in production).

    What I'd be careful of is maintaining any objects that use the XXL texts as I don't know what the impact of saving these objects through the old UI will be. Also the old UI probably won't be maintained going forward so you need to be aware of that too.

    Regards,

    Gareth

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 11, 2014 at 12:55 PM

    Thank you guys, why SAP change this? Maintain master data in Web Dynpro functionality it's horrible.

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 10, 2014 at 09:03 PM

    Hi Jo Paulo,

    I would like that too because I find the master data maintenance on portal absolutely terrible. Not only the functionality is more restricted, but the performance is attrocious! And I'm sure we're not the only one in that case.

    This change was introduced in 7.40 SP5 I think, because it was meant to be used for InfoObjects with XXL texts.


    I believe this option has been re-introduced in 7.40 SP8 through SAP Note 2022395, because its description says that "The possibility of changing all master data records available in the UI has been introduced again". However I'm not sure of that because we have not implemented that SP or note yet.

    If you do implement this and it does bring that functionality back, would you be kind enough to update this thread with your results?

    Regards,

    Sebastien Francal

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 04, 2015 at 07:09 PM

    Perfect informations.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you Gareth - this works beautifully, hopefully SAP will revert back to the GUI...Its just more productive and user friendly.

  • avatar image
    Former Member
    May 15, 2015 at 06:34 AM

    Hi Gareth,

    I have made the code changes as suggested by you but there is some kind of inconsistency.

    After maintaining master data ,If I go back one step it works fine

    But if I type /nRSA1 or any other tcode on the same screen,it gives a dump.

    Below is the dump.

    Short Text
    The current application has triggered a termination with a short dump.

    What happened?
    The current application program has detected a situation that should
    not occur. A termination with short dump has therefore been triggered
    by the key word MESSAGE (type X).

    What can you do?
    Note down which actions and inputs caused the error.


    To process the problem further, contact you SAP system
    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.

    Error analysis
    Short text of the error message:
    ControlFrameWork: Maximum number of sessions reached
    Long text of the error message:
    Technical information about the message:
    Message class....... CNDP
    Number.............. 011
    Variable 1..........
    Variable 2..........
    Variable 3..........
    Variable 4.......... " "

    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    -
    If the error occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP

    Notes system, check there first using the following keywords:

    "MESSAGE_TYPE_X"
    "SAPLOLEA" bzw. LOLEAU02
    "AC_SYSTEM_FLUSH"
    If you cannot solve the problem yourself, please send the following
    information to SAP:

    1. This description of the problem (short dump)
    To do this, choose System -> List -> Save -> Local File (unconverted)
    on the screen you are in now.

    2. A suitable system log
    To do this, call the system log in transaction SM21. Restrict the time
    interval to ten minutes before the short dump and five minutes after
    it. In the display, choose System -> List -> Save -> Local File
    (unconverted).

    3. If these are programs of your own, or modified SAP programs: Source
    code of these programs
    To do this, choose More Utilities -> Upload/Download -> Download in
    the Editor.

    4. Details regarding the conditions under which the error occurred or
    which actions and input caused the error.

    System environment
    SAP Release..... 740
    SAP Basis level 0009

    Application server... saps009
    Network address...... 137.33.22.24
    Operating system... Windows NT
    Release.............. 6.0
    Hardware type....... 4x AMD64 Level
    Character length..... 16 Bits
    Pointer length........ 64 Bits
    Work process number... 11
    Shortdump setting. full

    Database server... SAPS009
    Database type..... MSSQL
    Database name..... BID
    Database user ID bid


    Terminal.......... GDNL2180

    Character set C

    SAP kernel....... 742
    Created on....... Jan 30 2015 22:06:39
    Created at....... NT 6.1 7601 x86 MS VC++ 16.00
    Database version SQL_Server_9.00
    Patch level....... 37
    Patch text.......

    Database............. MSSQL 9.00.2047 or higher
    SAP database version. 742
    Operating system... Windows NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT
    6.3

    Memory consumption
    Roll.... 0
    EM...... 45930944
    Heap.... 0
    Page.... 40960
    MM used. 29493280
    MM free. 16431408

    User and Transaction
    Client................. 100
    User.................. GDNJAINI
    Language key.......... E
    Transaction......... RSA1
    Transaction ID...... EECAFAE4F51BF1F6B2DD005056950066

    EPP whole context ID...... 0050569500661EE4BED95AD6937632DD
    EPP connection ID........ DFCAFAE4BC6CF115B2DD005056950066
    EPP call counter......... 1

    Program.............. SAPLOLEA
    Screen.............. SAPLRSAWBN_MAIN 1000
    Screen line.......... 0
    Active debugger..... "none"

    RFC Caller Information

    Information on caller of Remote Function Call (RFC):
    System.............. BID
    Installation number 0020244352
    Database Release..... 740
    Kernel Release...... 742
    Connection type..... 3 (2=R/2, 3=ABAP-System, E=External,
    R=Reg.External) call type....... synchronous and non-transactional (emode 0,
    imode 0)
    Inbound TID..........
    Inbound queue name...
    Outbound TID.........
    Outbound queue name..

    Client................. 100
    User.................. GDNJAINI
    Transaction......... RSA1
    Call program...........CL_RSDMD_RSAWBN_TOOL==========CP
    Function module..... RSNDI_MD_ATTR_TEXTS_MAINTAIN
    Call destination..... NONE
    Source server...... saps009_BID_00
    Source IP address.. 137.33.22.24

    Additional information on RFC logon:
    Trusted relationship..
    Logon return code.... 0
    Trusted return code.. 0

    Remarks:
    In Releases prior to 4.0, information about the RFC caller might be
    missing or incomplete.
    - The installation number is provided in caller Release 700 and higher.

    rmation on where terminated
    The termination occurred in ABAP program "SAPLOLEA", in "AC_SYSTEM_FLUSH". The
    main program
    was "RSAWBN_START".

    In the source code, the termination point is in line 38 of (Include)
    program "LOLEAU02".

    Line SourceCde

    8 *" CNTL_ERROR
    9 *"----------------------------------------------------------------------
    10 data: sysubrc like sy-subrc.
    11
    12 CALL FUNCTION 'AC_FLUSH_CALL'
    13 EXPORTING
    14 SYSTEM_FLUSH = 'X'
    15 CALLED_BY_SYSTEM = CALLED_BY_SYSTEM
    16 IMPORTING
    17 MESSAGE_NR = sysubrc
    18 MESSAGE_TEXT = SY-MSGLI.
    19
    20 sy-subrc = sysubrc.
    21
    22 CASE SY-SUBRC.
    23 WHEN 0.
    24 WHEN 1.
    25 * system_error
    26 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.
    27 WHEN 2.
    28 * method_call_error
    29 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
    30 WHEN 3.
    31 * property_set_error
    32 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
    33 WHEN 4.
    34 * property_get_error
    35 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.
    36 WHEN 8.
    37 * maximal number of modi reached
    >>>>> MESSAGE ID 'CNDP' TYPE 'X' NUMBER 011 RAISING CNTL_SYSTEM_ERROR.
    39 WHEN OTHERS.
    40 RAISE CNTL_ERROR.
    41 ENDCASE.
    42
    43 ENDFUNCTION.

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

  • May 20, 2015 at 07:49 PM

    After a recent upgrade to 7.4, we were surprised by the WebDynPro MDM. I'm not a big fan of Web based UI's as they tend to be less accessible (try closing your eyes and not touching your mouse - can you use the app? well then neither can a lot of others...)

    We had wrapped the RSDMD_MDMT transaction in our own code that checked for modified records and activated them. Unfortunately, the new WebDynPro model means RSDMD_MDMT returns immediately (ie: now performs Asynchronously), and our activation step is no longer valid. We have to run our wrapper twice - once to make data changes, and again to activate them.

    This double step is error prone (and has caused us some grief already - since the WebDynPro screen appears to show the data successfully changed, and does not clearly - to an end user - show it not active).

    Is there a way to have the web based mdm editor save AND activate? or are we stuck making the change that downgrades the UI back to SAP GUI (and may cause other display problems with large fields...)

    Add comment
    10|10000 characters needed characters exceeded