To find the KPI's (CKF, RKF,Formula) where used in Bex queries.

 

Access required to SE11/SE16, SE37.

Views - V_COMPDIR_COMPIC

 

Steps to Follow

  1. Go to SE11/SE16
  2. Enter the View Name - V_COMPDIR_COMPIC

 

1.png

3.Select a Definition type of an Element with A version, I am selecting  RKF here.

7.png

4. Execute and get the COMPUID .

 

2.png

5. Go to SE37 , use the FM RSZ_DB_COMP_WHERE_USED

3.png

6.Input the COMPUID  got from STEP 4 into I_COMPUID

4.png

7.After Execution you will get the where used list entries as highlighted5.png

 

8. 9 Entries shown below. Since i have chose RKF, the list shows the RKF's used in CKF's and the query names

6.png


PS : You can get the COMPUID  from the table  RSZELTDIR .By choosing the needed element definitions , input the COMPUID in the FM.


Hope this helps....

Creating Authorization in BW System

Steps for creating authorization

RSD1-To maintain info object authorization relevant.

PFCG – To maintain roles

RSECADMIN – To maintain analysis authorization and role assignment to user

1. Make a variable authorization relevant.

2. Create roles.

3. Create BI Analysis Authorization.

1. Make a variable authorization relevant

Go to RSA1 select info object target and go to business Explorer and check the box for authorization relevant 

2. Create BI Analysis Authorization

Use transaction RSECADMIN

Select AUTHORIZATION Tab

Select MAINTENANCE

 

Give the name for the authorization and click create

Give the short text

Below characteristics are mandatory while creating authorization object.

1. 0TCAACTVT: This characteristic handles the general activity like create, change, display etc.

2. 0TCAVALID: This characteristic handles the authorization for Info Provider by default it gives access to all the Info Providers i.e. full access. We can restrict authorizations for particular Info Providers using this characteristic.

3. 0TCAVALID:  This characteristic handles the validity of an authorization. Always valid (*) is set as the default for validity. You can restrict this validity. You can also specify a single value or an interval.

Insert new row and add the dimension and give a value

  1. For giving values double click the intervals cell

 

Add a row and give the value depending upon the requirement

Save the authorization

3. Creating the role

Select user tab

Select Role maintenance

Give the role name and select either single role or composite role (in my case I selected single role)

Select menu tab

Select transaction

Give the transaction to be allowed

Ex- RSRT – Query monitor

Select Authorization Tab

Add the authorization created to S_RS_AUTH

Generate then Save

Select the user tab

Add the users which has the role

Then do user comparison

Creating Authorization variable

Open query designer

Creating authorizing variable

 

In Query Designer Put the authorization variable under filter panel.

Checking the authorization

Go to the analysis tab -> select execute as -> give the user (EX – RETUSER1) -> select with log

Select start transaction -> select the authorization query -> execute

Then run as the user to which role was assign then run the query

Query display as HTML

Now check the below out only for the RUKSHAYA

Thanks,

Phani.

Dear Followers,

 

Over the past weeks we are seeing many incidents being opened by BI Java customers which upgraded their portal systems to Netweaver 7.30 SPS 09, 10 and 11, NW 7.31 SPS 09, 10 and 11 and NW 7.40 SPS 04, 05 and 06.

 

The cause for the issue is a missing .jar file (urbrowser) on EP-BASIS SCA, because of a regression caused by SAP Note 1972506.

 

Our development team has already delivered two notes with the corrections for this:


1995970 - Missing urbrowser.jar caused an exception com.sapportals.portal.useragent.UserAgentSetException
2000082 - Runtime Exception when trying to add new user agent string

 

Please refer to these notes on which patch contains the corrections for the relevant NW Portal version you are using.


We hope with these new patches the issue is completely solved now.

 

Kind Regards,
Marcio

Purpose: Find unused InfoObjects which are available in any Infoprovider (Multiprovider,InfoCube and DSO),

                 and NOT used in any report which are built on provided infoprovider.


Step 1 : Run Given ABAP program and provide Infoprovider name as shown in below screenshot.



Note: Unused  infoobjects  means,  which are available in infoprovider but not used in any report which are built on given infoprovider.

1.jpg

Step 2 : ABAP program finds the unused InfoObjects and list in ALV output , as shown in below screenshot.

2.jpg


ABAP Code.



Hi Friends,

 

Here is the blog which drives to write this blog Restricting a Characteristic With Its Compounding Characteristic.. Thanks Yasemin ULUTURK

 

 

Above blog has greatly explained an approach how to overcome issue which arise while restricting characteristic which is compounded with another characteristic.

 

To do above approach we need to do modelling changes by writing routine at Transformation level and enable navigational attribute at Infocube level. Then transporting whole flow to production system. It may difficult some times to transports in big clients.

 

 

Here I am providing another additional approach to get same results.

 

Let’s see the approach

 

Here I am considering Storage location and Plant as Scenario to explain method.

 

pic 2.PNG

 

Find the data for our scenario:

pic 1.PNG

 

 

Here user wants to exclude Storage location of 0088 of plant 1000. If I simply exclude storage location 0088, then I will lose data of storage location 0088 belongs to  plant 1001 also. This shouldn't happen.

 

To overcome this issue , I am providing another approach which can achieve directly at BEx level  without  doing modelling changes. All we need do some workaround at BEx level by creating Selections and formulas logically.

 

I restricted Closing stock with  Storage location 0088 of plant 1000. (KF2)

 

pic 3.PNG

 

Then created another KF with restricting Closing Stock KF with only Plant 1000.(KF1)

 

pic 4.PNG

 

 

Then create formula by subtracting KF2 from KF1.

 

pic 5.PNG

 

 

Finally we got closing stock of plant 1000, after deducting stock belongs to  Storage location 0088 of plant 1000.

 

 

Here find stock of plant 1001 and user doesn't want to exclude any storage location. So simply restricted Stock with plant 1001.

 

pic 6.PNG

 

Thanks for reading this article and hope it helps you.

 

Best Wishes,

Vijay

There are situations when there is a need to make a restriction on a characteristic with its compounding characteristic. I will try to explain the problem with an example, mention about the SAP Note related with this problem and propose a shortcut solution for this problem.

 

Problem Definition:

 

Suppose we have a characteristics ZDUMMY_PA (Personnel Area) and ZDUMMYPSA (Personel Sub Area). ZDUMMY_PA is the compounding characteristic of ZDUMMY_PSA. We have data such as:

24022014_01.JPG

We have an infoprovider using these two characteristics. We have a query where we make a restriction on ZDUMMY_PA. We want to restrict the Sub Areas: 100 from A area and 200 from C area. In the query when we drag A/100 for the restriction, only 100 is dragged and all personnel areas related with 100 are included in the restriction as seen below:

24022014_02.JPG

 

An overview on SAP Note related with this problem:

 

The SAP Note: 541253 describes this situation and proposes a solution. However, this solution is not suitable for the requirement described above. The note suggests restricting the compounded infoobject. When we do that in this case, we have to restrict A and C for personnel area and 100 and 200 for personnel subarea. Then in the report we will see all 100 and 200 subareas belonging to A and C. That is; even if we don’t want to show A/200, it will be shown in the report.

 

Solution approach for the problem:

 

The shortcut solution I suggest will be defining a new attribute to Personnel Subarea characteristic. For this aim, we define a new characteristic with data type char 8 (8 comes from the total number of characters defined in personnel area and personnel subarea. In our example, personnel area is defined as char 4 and personnel subarea is also defined as char 4).

We add this new characteristic as the attribute of personnel sub area: ZDUMMYPSA.

24022014_03.JPG

In the transformation for master data we add personnel area and subarea to source fields list and select rule type as routine:

24022014_04.JPG

We write a small routine to update ZDUMMYCH:

  CONCATENATE SOURCE_FIELDS_RULE-/BIC/ZDUMMY_PA
  SOURCE_FIELDS_RULE
-/BIC/ZDUMMYPSA   INTO RESULT.

In this part, we may give any other character in between the personnel and subarea. I generally use '/' sign in between.

This kind of approach may become a must in some situations. For example if we had personnel_areas such as A and A1 and subarea

such as 100 and 00, when we concatenate there will be one concatenated value for two different personnel area - subareas: A100.

Then it will mislead the report when filtered. For sake of simplicity in this blog I go with direct assignment without any character in between.

 

After we load and activate master data we see the master data as:

24022014_05.JPG

Now we need to add ZDUMMYCH to the navigation attributes of the infoprovider. Then in the query designer we can add ZDUMMYCH to the characteristic restrictions pane and we can easily select ZDUMMYCH to filter with our desired restrictions:

24022014_06.JPG

As a result, with some modeling changes in both characteristic and the infoprovider, we can achieve to see the desired results. I hope it gives an idea.

 

Yasemin Uluturk

 

 

How to utilize Exception Aggregation using BEx Query Designer.


Exception  aggregation can be used to derive additional information out of a limited number of Key Figures provided in the InfoCube that is to be analyzed.
Thereby, you can create Calculated Key Figures by using a formula that uses exception aggregation itself (this is a nested exception aggregation). Furthermore, it is possible to use Calculated Key Figures created on cell level (using the cell editor) with the new functions of exception aggregation.

 

Example: If a sales manager wants to analyze the number of materials sold and the average number of different materials sold to different customers for each sales month. In the sales InfoCube, only a Key Figure of the Sales Volume in EUR for the different sold materials is provided.  Using the functions for exception aggregation,  he can derive the additionally required two Key Figures just from the sales volume in EUR for sold materials.

 

Procedure: To define an exception aggregation for the example above, the following steps are performed

1.  You create a Query that contains the Characteristics "Sold-to Party" (Customer) and "Material" in the free Characteristics, the characteristics

      "Cal. year/ month" in the rows and the Key Figure "Sales Volume EUR"

2. In the next step, you define a new formula ("Different materials"), which simply includes the Query Key Figure "Sales Volume in EUR" (no operator       required in this example).

Then you access the properties of this formula and choose the exception aggregation setting "count all values<> 0" for the reference Characteristic "Material".  In this way, you have defined a counter for your sold materials derived from the Key Figure "Sales Volume in EUR". You have simply counted

the number of occurrences of "Sales Volume in EUR" to give you the new Key Figure 'Different Materials'.

 

3. Now you will nest the exceptions: You are now able to count the number of materials sold in each month for all customers using the step above, but you want to know what the average number of materials the customers bought in each month. To achieve this, you must define another formula   ("Avg. sold materials/ customers"), which simply refers to the first formula. Again no other operators are required. You access the properties of the second formula and choose the exception aggregation "Average of all Values" for the reference Characteristic "Sold-to Party". The Key point here is that the results of the first aggregation are further processed by the second aggregation.

 

View.png

 

4. Check your query by performing a validity check to know if your query is correct or not.

 

5. Save your Query with a description and a technical name and then click on execute to see how exception aggregation works.

     How to calculate the total amount before and after aggregation?

Product name, quantity and amount
defining the formula at local level

Total amount= product quantity x amount

It will give out put like means total amount not yet aggregated it is giving product quantity x product price = total amount

Now report output but achievement total amount should be aggregated value.

Creating global level calculated key figure

Creating KF at Global level

Here not using exception aggregation

This Total amount KF defined at global level

global level calculated KF will appear the calculation after aggregation

Output should be below report

After un check the calculation after aggregation means before aggregation it will give total aggregated total amount value.

Output of the report now showing total amount was aggregated

Now report out put total amount is given aggregated value.

hope it will help beginners.

Introduction


                   I am going to share my experiences in migrating Web Templates from 3.5 to 7.0 in this blog. There will be some Tips and Tricks as well as Observations too.

 

Strategy

 

  • Anything on lower version will have to be upgraded to latest or at least -1. I mean currently we have BW 7.3/7.4 version. So we should be at least on 7.0 or above.
  • If we are still on 3.5, then we will not be able to upgrade to SAP GUI 7.3. I am making one thing very clear here. I am talking about just GUI 7.3 upgrade. It's not about BW 7.3 upgradation
  • SAP GUI 7.3 is compatible only with 7.0 and above

 

Steps to be carried out for Migration

 

  • Go through all your designs of 3.5 Web templates to observe the usage of 3.X library items. You might have used below 3.X library items. There may be others as well.

               0ADHOC_BAR_CHART

               0ADHOC_COLUMN_STACKED_CHART

               0ADHOC_LINE_CHART

 

  • Important SAP Notes to be followed are Notes: 844012 , 832712 and 832713


  • We need to migrate all observed 3.X library items with a standard SAP Program : RSZW_ITEM_MIGRATION_3X_TO_70


  • Goto SE38 and carefully observe all Selection options( Simulate, Overwrite originals and Role Adjustments etc) in Execute screen. You can take your own call What to choose
  • To migrate above 3.X items, you have to choose first selection like below. Choose Multiple selection and paste all items

         Migr1.JPG

When you execute with above selection, it will ask you to confirm below entries. Say OK

          Migr2.JPG

Migration will be completed and will show us results like below.

          Migr3.JPG

  • WAD 7.0 has given us a nice Migration Tool which can be found below :--

             Migr4.JPG

 

  • Select 3.5 Web Template and continue to migrate. If no errors found , your web templates will be migrated to 7.0. System will ask us to save in new technical names. One good thing here is, migration process does not over write on 3.5 Web templates. I mean you can still access 3.5 templates by logging through WAD 3.5

 

  • Most possible errors could be :--


              It may throw any 3.X library Items to be migrated through SAP standard FM

 

              If any custom Web Items/Templates of 3.5 also have to be migrated

 

  • The most important thing here is,

               All your 3.5 web templates are in HTML code. When we migrate them to 7.0, it gets converted to XML(XHTML) Code with some extra lines of code.

       Migr5.JPG

  • We need to select that particular code in XML(XHTML) tab and delete it. Then all your errors will be vanished.

 

Observations

 

  • Do not expect 100% exact look and feel in 7.0 web templates after migration.

 

  • We need to adjust our new web templates till we get similar layouts like 3.5

 

  • In fact, we can show much better and effective layouts with WAD 7.0

 

  • Alignments will be a headache task and we should make them very carefully in all web templates

 

  • You might have used "Text Elements" in 3.5 templates to show Query Description on top of the Report as Header. The same does not look great after migration to 7.0. To make it more brighter and highlighted, we can simply type the Report name in 7.0 Template in Bold and decent font size.

 

  • No custom XHTML codes are required to show buttons like Export to Excel, CSV, Print, PDF etc..They can be easily achieved in 7.0 by using "Button Group" web items with respective commands

 

Conclusion

 

               We can achieve all our WAD 3.5 requirements with various workarounds in WAD 7.0. It is very effective as far as Portal or Web Analyzer usage is concerned. Hope my experiences will help you mates.

When i was working with BEx Query designer i got errors while opening the BEx queries.

Initially As for client requirement i added all char in free char panel user will drill down based on their requirement after testing the queries they suggested unwanted objects. Then i removed unwanted objects form targets (Info Cube and DSO)

While opening the queries through BEx Analyzer respective info cube we are getting some errors

Characteristics not available in Info provider

Then run the same query in RSRT going to ABAP debug mode.

After saving the query in BEx Query designer level getting errors.

Means initially removed these objects form Target level (Info cube and DSO)

Now see unwanted objects is have capital letters means these are all objects unwanted objects

After removing all objects from BEx query designer level its working fine.

After running the same query in RSRT and BEx Analyzer it is working and now query executed.

 

Thanks,

Phani.

Scenerio :

 

When you are working with multilingual client. It is quite obvious that some key user create workbooks and maintain titles only in their log on language.

As we monitor the broadcast queue (RSPRECALCADMIN), we find such entries without titles.

PSA - BE.jpg

It is tough sometimes to catch each workbook created and maintain title in the required languege.

 

Please do not get confused with the translation here. It is just maintaining the same title in another languege. ( It is better to have something than nothing ).

 

Background information :

 

RSRWBINDEXT - Titles of binary objects (Excel workbooks) in InfoCatalog

 

The above table will be updated with title for required languege.

 

Program code :

 

*&---------------------------------------------------------------------*
*& Report  ZBW_WB_DESC_EN_DE
*&
*&---------------------------------------------------------------------*
*&The table RSRWBINDEXT contains the titles of the workbooks created
*&trhough BEx, the program checks the single entries in the said table
*&and maintains the same title in EN or DE vice versa.
*&---------------------------------------------------------------------*
REPORT  ZBW_WB_DESC_EN_DE MESSAGE-ID Zm.
Data :     ZRSRWBINDEXT type TABLE OF RSRWBINDEXT WITH HEADER LINE,
              ZRSRWBINDEXTT type TABLE OF RSRWBINDEXT WITH HEADER LINE,
              ZRSRWBINDEXT1 type TABLE OF RSRWBINDEXT WITH HEADER LINE,
             itab type table of istr WITH HEADER LINE.
types:  BEGIN OF istr,
           WORKBOOKID TYPE RSRWBINDEXT-WORKBOOKID,
           CNT type i,
           END OF istr.
SELECT * FROM RSRWBINDEXT INTO TABLE ZRSRWBINDEXT WHERE OBJVERS = 'A'.
SORT ZRSRWBINDEXT ASCENDING BY WORKBOOKID.
LOOP AT ZRSRWBINDEXT.
     READ TABLE ITAB WITH TABLE KEY WORKBOOKID =  ZRSRWBINDEXT-WORKBOOKID.
     IF SY-SUBRC = 0.
            ITAB-CNT = ITAB-CNT + 1.
            modify itab TRANSPORTING CNT where WORKBOOKID = ZRSRWBINDEXT-WORKBOOKID.
     ELSE.
            ITAB-WORKBOOKID = ZRSRWBINDEXT-WORKBOOKID.
            ITAB-CNT = 1.
            INSERT TABLE ITAB.
      ENDIF.
ENDLOOP.
LOOP AT ITAB WHERE CNT = 1.
     READ TABLE ZRSRWBINDEXT WITH KEY WORKBOOKID =  ITAB-WORKBOOKID.
     INSERT ZRSRWBINDEXT INTO TABLE ZRSRWBINDEXT1.\
ENDLOOP.
LOOP AT ZRSRWBINDEXT1.
     IF ZRSRWBINDEXT1-LANGU = 'E'.
          ZRSRWBINDEXT1-LANGU = 'D'.
          INSERT ZRSRWBINDEXT1 INTO TABLE ZRSRWBINDEXTT.
     ELSEIF ZRSRWBINDEXT1-LANGU = 'D'.
         ZRSRWBINDEXT1-LANGU = 'E'.
         INSERT ZRSRWBINDEXT1 INTO TABLE ZRSRWBINDEXTT.
     ELSE.
         ZRSRWBINDEXT1-LANGU = 'D'.
         INSERT ZRSRWBINDEXT1 INTO TABLE ZRSRWBINDEXTT.
         ZRSRWBINDEXT1-LANGU = 'E'.
         INSERT ZRSRWBINDEXT1 INTO TABLE ZRSRWBINDEXTT.
      ENDIF.
ENDLOOP.
MODIFY RSRWBINDEXT from TABLE ZRSRWBINDEXTT.
MESSAGE S000 with sy-dbcnt.

 

As I am not an expert in ABAP, you may find the coding as novice.

Hope it helps, do share your suggestions and thoughts about it.

Hi,

 

with this blog post I want to share a code example of how to implement Country Settings of SAP Note 1064448 during runtime. The code is a modified copy of Kai Gutenkunst's blog post http://scn.sap.com/people/kai.gutenkunst/blog/2008/10/22/bi-chart-item-modifying-chart-settings-at-runtime.

 

The scenario is simple. A company wants texts to be displayed in one language (for example English for all users) and the number format should follow another country setting (for example Swedish).

 

Without BAdI Implementation (example EN)With BAdI implementation (example SV)
1064448_EN.png1064448_SV.png

 

At the end of Note 1064448 there is an XML snippet that describes how to change Country Settings. Here is how you can change the XML during runtime using BAdI RS_BADI_CHART:

 

Method  if_rs_chart_enhancement~modify_chart_request

 

METHOD if_rs_chart_enhancement~modify_chart_request
*
* Customizing XML
   c_customizing_xml = set_xml_language( iv_language = 'SV'  "Swedish
                                              iv_xml = c_customizing_xml ).
*
* Delta Customizing XML
   c_delta_customizing_xml = set_xml_language( iv_language =  'SV'  "Swedish
                                                    iv_xml = c_delta_customizing_xml ).
ENDMETHOD.








 

The determination of what language to set can be made much more sofisticated. For the purpose of simplicity, I have hardcoded the language in the example above.

 

Method  set_xml_language

 

The parameters of the set_xml_language method looks like this:

set_xml_language.png

 

METHOD set_xml_language.
*
 TYPE-POOLS: ixml.
*
 CLASS cl_ixml DEFINITION LOAD.
*
   DATA: lr_ixml TYPE REF TO if_ixml.
   DATA: lr_streamfactory TYPE REF TO if_ixml_stream_factory.
   DATA: lr_xml TYPE REF TO if_ixml_istream.
   DATA: lr_xml_ostr TYPE REF TO if_ixml_ostream.
   DATA: lr_document TYPE REF TO if_ixml_document.
   DATA: lr_parser TYPE REF TO if_ixml_parser.
   DATA: lr_global_settings TYPE REF TO if_ixml_node.
   DATA: lr_first_child TYPE REF TO if_ixml_node.
   DATA: lr_language_node TYPE REF TO if_ixml_node.
   DATA: lr_language_element TYPE REF TO if_ixml_element.
   DATA: lv_xml TYPE xstring.
   DATA: lv_rc TYPE i.
*
* Create iXml factory
   lr_ixml = cl_ixml=>create( ).
*
* Create stream factory
   lr_streamfactory = lr_ixml->create_stream_factory( ).
*
* Create input stream
   lr_xml = lr_streamfactory->create_istream_xstring( iv_xml ).
*
* Create output stream
   lr_xml_ostr = lr_streamfactory->create_ostream_xstring( lv_xml ).
*
* Create document
   lr_document = lr_ixml->create_document( ).
*
* Parse Xml
   lr_parser = lr_ixml->create_parser( stream_factory = lr_streamfactory
                                              istream = lr_xml
                                             document = lr_document ).
*
* Parsing successful?
   IF lr_parser->parse( ) = 0.
*
* Find <Language> element
     lr_language_element = lr_document->find_from_name( name = 'Language' ).
     IF lr_language_element IS NOT INITIAL.
*
* Set language of the <Language> element
       lr_language_element->set_value( iv_language ).
     ELSE.
*
* Find <GlobalSettings> element
       lr_global_settings = lr_document->find_from_name( name = 'GlobalSettings' ).
       lr_first_child = lr_global_settings->get_first_child( ).
       lr_language_node = lr_first_child->clone( ).
       lr_language_node->set_name( 'Language').
       lr_language_node->set_value( 'SV' ).
*
* Insert a <Language> element in the XML
       lr_global_settings->insert_child( new_child = lr_language_node ref_child = lr_first_child ).
     ENDIF.
*
* Serialize xml
     lv_rc = lr_ixml->create_renderer( ostream = lr_xml_ostr document = lr_document )->render( ).
*
* Return xml
     rv_xml = lv_xml.
   ENDIF.
ENDMETHOD.








 

All strings should of course be externalized, but I excluded that here to enhance the readability.

If user wants to refresh the queries individually  in a workbook with multiple queries and give different variable inputs for queries separately.

 

Steps for resolution:

1. Maintain 'X' for ANA_SINGLEDREFRESH in tcode RS_FRONTEND_INIT.

multiple.jpg

2. Check Allow Refresh Function For Individual Queries

2.jpg

3. Uncheck Display Duplicate Variables only Once.

    If the same query is used multiple times and user wants to give different inputs in workbooks, below option should be unchecked.

     save workbook.

3.jpg

Thanks for Reading,

Regards,

Emily.

When locally saved Workbooks are migrated from 3.x to 7.3,

When you open the migrated workbook, click on change variables, save variant option in not enabled and have error message as ‘Variants not possible, as the workbook has not been saved on the server'.


Below is the screen print for error message.

Error message.jpg

Steps to resolve the issue.     

     1. Open BEx Analyzer.

     2. Open locally saved workbook.

Error message 2.jpg

     3. Save workbook in favorites/Roles with the same name in BEx.

     4. Open the saved workbook from favorites, save it locally on the PC.

     5. Now open the locally saved workbook and save variants.

 

Thanks for reading.

Regards,

Emily

I recently was faced with the challenge to start a transaction in our SAP-System with Windows-SAPGui.
This can be done with the appintegrator in the SAP-portal.

 

 

 

Here's an example how to call MM03:

 

/irj/servlet/prt/portal/prtroot/com.sap.portal.appintegrator.sap.bwc.Transaction?System=SAP_ERP_SSO&TCode=MM03&Technique=SSF&GuiType=WinGui&WinGui_Type=&ApplicationParameter=RMMG1-MATNR%3D60004499

 

 

The result is a small scriptfile which starts the MM03.

 

The opening SAP-window is very small and id doesn't keep it's size when you're adjusting it.

 

The solution is a parameter in a configuration file. In this file you can customize how to call the transaction.

 

The path to this file is very long and it depends on the hardware an on the Java-Version.

 

Filepath on our IBM I-series maschine is currently:

 

\usr\sap\PEI\J44\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\property\Transaction\WinGuiRenderLayer.properties

 

and the filename is

 

WinGuiRenderLayer.properties

 

I modified the following section by adding the parameter <GuiSize=Maximized>

 

SSFCommandTemplate =[System]\r\n\
                    Name=<System.r3name>\r\n\
                    Client=<System.client>\r\n\
                    GuiParm=<ConnectionString><ConnectionParams>\r\n\
                    <Authentication[PROCESS_RECURSIVE]>\r\n\
                    [Function]\r\n\
                    Command=<CommandField>\r\n\
                    Type=Transaction\r\n\
                    [Configuration]\r\n\
                    GuiSize=Maximized
#                   Workplace=true\r\n\
                    [Options]\r\n\
                    Reuse=<ReuseWinguiConnection[01_BOOL]>\r\n

 

It worked after bouncing the system.

 

Hope this was helpful.

Actions

Filter Blog

By author:
By date:
By tag: