Add column in Staff Assignemnt Area(Structure) of transaction PPOME

Hi,
I want to add a new column with custom information in Staff assignment( staructure search) area of transaction PPOME. I tried using the confirguration to add this information but couldnt reach any conclusion. Need Help.
Regards

Hi,
For adding fields at the item level to VL01N Transaction you can use the BADI LE_SHP_TAB_CUST_ITEM.
I dont think it is a good idea to add fields right next to the standard fields in the transaction. A separate tab should be created which will include all the customer fields.
Check the documentation of this BADI for more details. If you want this field only in VL03N transaction then you can implement the BADI accordingly so that it triggers only for VL03N transaction.

Similar Messages

HR - People are unsorted in transaction PPOME

Hi!
In transaction PPOME, there is a hierarchical display of the elements. If I want to check an organisation structure then I can see the people assigned under the relevant organisation unit (or position).
My problem is, that these people are not sorted in any way. Nor by their name, nor by their personal ID.
It is very though to handle them, if there are more than 20 people in one organisation unit.
So you know a way to sort them somehow? With a user-exit maybe?
Thank you
Tamá

Solved.

How to add columns in field-symbol

Dear All,
Have made a report for HR - ZHR_CTC by using logical database and field-symbol. Report is working fine, but now have to add columns e.g business area text, positions text etc.
Have added columns in field-symbol.But not able to fetch data into that.
Data has to be fetched from different trasparent table comparing <field-symbol>-field.
Plz suggest the proper way to do it.
<<text removed>>
Regards,
Gulrez Alam
Edited by: Gulrez Alam on Dec 16, 2008 11:02 AM
Edited by: Matt on Dec 16, 2008 11:36 AM

Hi Rimpa,
Thanks a lot for you reply, have tried ur suggestion but it's not working. I am not able to understand how to insert data into field-symbol. Plz give some more clarifications about the same.
Regards,
Gulrez Alam

MSS - OADP - possibility to add columns in navigation area

Dear SDN members,
I would like to know if there is a way to add a column in the navigation area (column tree) for object navigation like Organization.
In standard only the text (char 40) is displayed.
Thanks for your answers
Regards,

well the column can be added using data views IMG under OADP
But i m not sure this can be used to add in navigation area, it ll require modification there
function modules: HRWPC_ RFC_OADP_EVAL_DATAVIEW and
HRWPC_OADP_GET_DATAVIEW_COLDT

How to add columns for existing table dynamically?

Hi,
I created table structure only. I want to add columns for this existing table. Columns are not fixed, according to the user choice i need to write code.
Plz give me reply asap.
Thanks
Shirisha

Hi Shirisha,
I think the following code snippet will help you.
int l_no_cols = 0;
//Get the number of columns in this variable, something like the following
//l_no_cols = wdContext().currentContextElement().get<Context_attribute_name>;
IWDTable l_tab;
IWDTransparentContainer l_tbl_cont = (IWDTransparentContainer)view.getElement("TableDataCont");//ID of Container
l_tab = (IWDTable)view.getElement("TableData");//ID of Table
l_tab.setVisible(WDVisibility.VISIBLE);
l_tab.bindDataSource(wdContext.nodeTable_Data().getNodeInfo());
for(int a = 1; a <=l_no_cols; a++)
//Creating the column
IWDTableColumn l_tab_col = (IWDTableColumn)view.createElement(IWDTableColumn.class,"COL"+a);
//Creating Caption for Column Header
IWDCaption l_tab_cap = (IWDCaption)view.createElement(IWDCaption.class,"Caption"+a);
l_tab_cap.setText("Col"+i);
l_tab_col.setHeader(l_tab_cap);
//Creating Table Cell Editor for column
IWDInputField l_tab_cell = (IWDInputField)view.createElement(IWDInputField.class,"CellEditor"+a);
//creating context node attribute for the column dynamically
wdContext.nodeTable_Data().getNodeInfo().addAttribute("Col"+i,"com.sap.dictionary.String");
l_tab_cell.bindValue(wdContext.nodeTable_Data().getNodeInfo().getAttribute("Col"+i));
l_tab_col.setTableCellEditor(l_tab_cell);
l_tab.addColumn(l_tab_col);
l_tbl_cont.addChild(l_tab);
Regards,
Alka

Fiscal year in the columns outside the key figure structure

Dear Experts
I have a report requirement to show the keyfigures in the columns from year 1 to year 10 and in each year there are 4 keyfigures each restricted to 1 quarter for 4 quarters.
So, there are too many keyfigures to create.
I am using fiscal year in the columns outside the Key figure structure containing the keyfigures restricted at each of 4 quarters.
So, when the report displays, all the 10 years will automatically be displayed.
The problem is one of the 4 quarter level keyfigures needs to be restricted by calendar year.
How can I read what is the fiscal year for each column at runtime so that I can reference this value to determine the calendar year ?
As you know, each FY spans 2 Calendar Years. So, i need to restrict this on the 4th keyfigure by calendar year but while having the FY outside the keyfigure structure i can get all the FY, I am not sure how to access this value at runtime so that eg.
if FY for column 1 is 2010, i can set calendar year to be 2010 to 2011.
Hope you can give me some clues.
Thanks you Gurus!
Best regards
John

Dear Sunnybt
Copy Riyes, I find your response interesting. Please could you elaborate your idea of using condition in more detail.
Sorry for my late response.
Allow me to clarify my statement, which you are right, is unclear.
By :
"if the current QuarterFY is less than the current QuarterFY"
I mean :
eg. user enters FY range : 2009 to 20NN (eg. 2017)
KF_column1_FY2009_Q1______KF_column2_FY2009_Q2____KF_column3_FY2009_Q3______KF_column_FY2009_Q4______KF_column_FY2010_Q1______KF_column2_FY2010_Q2____KF_column3_FY2010_Q3______KF_column_FY2010_Q4_____KF_column_FY_NNNN_Q1
For each column, where the FY can be any year range entered by user,
the Text Description of the Column should show either 'Actual' or 'Plan' based on what is the current FY Quarter at runtime.
If the FY Quarter (eg. 1st column is 200101) is before current FY Quarter (i.e 201103), then the Description of this column should be "Actual" , else "Plan".
In my current design, I am unable to use customer exit text variable to meet this requirement.
So, I like to check with you for fresher ideas.
If not , I would use a workbook, which I am avoiding as the user needs to drilldown and I believe drilldown is not possible in workbooks where report layout needs to be rigid or cell positions fixed. Of course, unless there is a way out of this which I do not know.
Best regards
Bass

What are structures of logical database.

hi
what are structures of logical database.

Dear Chaitanya,
The structure of LDB can be divided into three sections:
>Structure
>Selection
>Database Program
STRUCTURE:
The structure defines the data view of the logical database. It adopts the hierarchy of the database tables defined by their foreign key relationships. This also controls the sequence in which the tables are accessed. It determines the structure of the other components and the behavior of the logical database at runtime.
The structure of a logical database is usually based on the foreign key relationships between hierarchical tables in the SAP System. Logical databases have a tree-like structure, which can be defined as follows:
· There is a single node at the highest level. This is known as the root node.
· Each node can have one or several branches.
· Each node is derived from one other node.
The nodes must be structures defined in the ABAP Dictionary or data types from a type group. Normally, these are the structures of database tables which the logical database reads and passes to the user for further evaluation. However, it is also possible, and sometimes useful, to use ABAP Dictionary structures without an underlying database. For technical reasons, the maximum number of nodes allowed in the structure of a logical database is 300.
Any executable ABAP program that has a logical database linked to it can contain a GET statement for each node of the structure. When you run the program, the corresponding event blocks are processed in the sequence prescribed by the hierarchical structure of the logical database. If a program does not contain a GET statement for every node of a logical database, the processing passes through all the nodes that lie in the path from the root to the nodes specified by GET statements.
If you call a logical database using the function module LDB_PROCESS, the depth to which the system reads is controlled by an interface parameter.
SELECTIONS:
The selections define a selection screen, which forms the user interface of the executable programs that use the logical database. Its layout is usually determined by the structure. You can adapt the selections to your own requirements and also add new ones. When you link a logical database to an executable program, the selections of the logical database become part of the standard selection screen of the program (screen number 1000). If you call a logical database using the function module LDB_PROCESS, the selections are filled using interface parameters.
The selections in a logical database are defined using the normal statements for defining selection screens, that is, PARAMETERS, SELECT-OPTIONS and SELECTION-SCREEN. In a logical database, you can also use the additions VALUE-REQUEST and HELP-REQUEST to define specific input and value help. You define the selection screen in a special include program known as the selection include.
When you write programs using a logical database, you can also add your own program specific selections. The standard selection screen then contains the database-specific selections, followed by the program-specific selections that you have defined.
When the system generates the selection screen for an executable program, database-specific selection criteria and parameters are only displayed if you have declared an interface work area for them in your program using the NODES or TABLES statement.
Suppose you have a selection include containing the following lines:
SELECT-OPTIONS slifnr FOR lfa1-lifnr.
PARAMETERS pbukrs LIKE lfb1-bukrs FOR TABLE lfb1.
The selection criterion SLIFNR is linked to table LFA1, the parameter PBUKRS to table LFB1. If the TABLES statement in an executable program (report) declares LFA1 but not LFB1, SLIFNR is displayed on the selection screen, but PBUKRS does not appear.
The selection screen of a logical database can contain dynamic selections as well as static ones. Dynamic selections are extra, user-defined selections that the user can make as well as using the static selections defined in the selection include. To improve performance, you should always use this option instead of reading more data than you need and then sorting it out in the application program.
To make dynamic selections available for the node nodeof a logical database, the selection include must contain the following statement:
SELECTION-SCREEN DYNAMIC SELECTIONS FOR NODE|TABLE node.
If the node node is requested by the user of the logical databases, the dynamic selections are included in the selection screen. A user can then choose Dynamic selections to enter extra selections for the corresponding fields. If you call the logical database using the function module LDB_PROCESS, you can pass a corresponding parameter. You can use these selections in dynamic statements in the logical database program to read data. The values of the program-specific selection criteria that you defined for a node for which dynamic selections were available are also passed to the logical database. The user can also define the fields for dynamic selections as a selection view for the logical database.
The selection screen of a logical database is part of the standard selection screen (number 1000) of the executable program to which the logical database is attached. It has a standardized layout - the selection criteria and parameters appear on separate lines in the order in which they were declared. You can change the layout using the SELECTION-SCREENstatement.
The runtime environment generates the selection screen with number 1000 for every program in which the attributes do not contain a different selection screen version. You can prevent certain input fields from the selection screen of a logical database from appearing on the selection screen by defining selection screen versions with a screen number lower than 1000 in the selection include, and entering this version number in the program attributes. By pressing F4 there, you can get an overview of the selection screen versions defined in the logical database concerned. To define a selection screen version, use the statements SELECTION-SCREEN BEGIN|END OF VERSION. Within these statements you can use SELECTION-SCREEN EXCLUDEto specify fields that you do not want to appear on the selection screen.
If the attributes of an executable program contain the number of a selection screen version, the version is used in the standard selection screen. Although the input fields that you excluded from the selection screen are not displayed, the corresponding selections still exist, and you can still edit them in the program or by calling the function module LDB_PROCESS.
DATABASE PROGRAM:
The database program contains the ABAP statements used to read the data and pass it to the user of the logical database. There is a container for special subroutines into which, amongst other things, the data from the database tables is read. These subroutines are called by the reporting processor in the runtime environment in a sequence that has been predefined by the structure. The database program is determined by the structure and selections and can be adapted or expanded to meet your requirements.
The name of the database program of a logical database ldbconforms to the naming convention SAPDBldb. It serves as a container for subroutines, which the ABAP runtime environment calls when a logical database is processed. The sequence of the calls and their interaction with the events in executable programs or the function module LDB_PROCESS depends on the structure of the logical database.
A logical database program usually contains the following subroutines:
· FORM LDB_PROCESS_INIT
Called once only before the logical database is processed. It prepares it to be called more than once by the function module LDB_PROCESS.
· FORM INIT
Called once only before the selection screen is processed.
· FORM PBO
Called before the selection screen is displayed, each time it is displayed. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS.
· FORM PAI
Called when the user interacts with the selection screen. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS. The interface parameters FNAME and MARK are passed to the subroutine.
FNAME contains the name of a selection criterion or parameter on the selection screen.
MARK describes the selection made by the user: MARK = space means that the user has entered a simple single value or range selection. MARK = '*' means that the user has also made entries on the Multiple Selection screen.
· FORM LDB_PROCESS_CHECK_SELECTIONS
Called instead of the subroutine PAI if the logical database is called using the function module LDB_PROCESS without a selection screen. This subroutine can check the selections passed in the function module interface.
· FORM PUT_node
Called in the sequence defined in the structure. Reads the data from the node nodeand uses the
PUT node.
statement to trigger a corresponding GETevent in the ABAP runtime environment. The PUT statement is the central statement in this subroutine: It can only be used within a subroutine of a logical database. The logical database must contain the node node, and the subroutine name must begin with PUT_node. The PUT statement directs the program flow according to the structure of the logical database. The depth to which the logical database is read is determined by the GET statements in the application program or the interface parameter CALLBACK of the function module LDB_PROCESS.
First, the subroutine PUT_root is executed for the root node. The PUT statement then directs the program flow as follows:
i. If the database program contains the subroutine AUTHORITY_CHECK_node, the first thing the PUT_node statement does is to call it.
ii. Next, the PUT statement triggers a GET event in the runtime environment. If there is a corresponding GET nodestatement in the executable program to which the logical database is linked, the associated event block is processed. If the CALLBACK parameter of the function module LDB_PROCESS is filled accordingly, the corresponding callback routine is called.
iii. The PUT statement directs the program flow
(a) To the next subroutine of a node that follows directly, if a lower-level node (not necessarily the very next) in the same subtree is requested by GET in the executable program or in the function module.
(b) To the subroutine of a node at the same level, if the preceding node branches to such a node and if a GET statement exists for such a node in the executable program or the function module.
The PUT statement in that subroutine starts again at step (i). In the subroutine of the lowest node in a subtree to be processed using GET, the program control does not branch further. Instead, the current subroutine is processed further. When a subroutine PUT_node has been executed in its entirety, the program flow returns to the PUTstatement from which it branched to the subroutine PUT_node.
iv. When control has returned from a lower-level subroutine PUT_node, the PUTstatement triggers the event GET node LATEin the runtime environment.
· FORM AUTHORITY_CHECK_node
Called automatically by the PUT node statement. In this subroutine, you can specify authorization checks for the appropriate node node from the structure of the logical database.
· FORM PUT_ldb_SP
Called when the user makes a selection using a search help to process the key chosen in the search help. ldb is the name of the logical database. From this subroutine, you can use the entries in the search help tables to read the relevant entries from the root node root. The processing in the program can then be triggered using PUT root. The subroutine PUT_root is then not called automatically.
· FORM BEFORE_EVENT
Called before an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value START-OF-SELECTION, to call a subroutine before this event.
· FORM AFTER_EVENT
Called after an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value END-OF-SELECTION, to call a subroutine after this event.
· FORM par_VAL, selop_VAL, selop-LOW_VAL, selop-HIGH_VAL
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
· FORM par_HLP, selop_HLP, selop-LOW_HLP, selop-HIGH_HLP
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
Example
Suppose that in the logical database structure, LFB1 is a branch of LFA1.
and that the following selection criteria are defined in the selection include:
SELECT-OPTIONS: slifnr FOR lfa1-lifnr,
sbukrs FOR lfb1-bukrs.
A section of the database program would then read:
FORM put_lfa1.
SELECT * FROM lfa1
WHERE lifnr IN slifnr.
PUT lfa1.
ENDSELECT.
ENDFORM.
FORM put_lfb1.
SELECT * FROM lfb1
WHERE lifnr = lfa1-lifnr.
AND bukrs IN sbukrs.
PUT lfb1.
ENDSELECT.
ENDFORM.
An executable program (report) linked to the logical database could contain the lines:
GET lfa1.
WRITE lfa1-lifnr.
GET lfb1.
WRITE lfb1-bukrs.
In this example, the runtime environment calls the routine put_lfa1 after the event START-OF-SELECTION. The event GET lfa1 is triggered by the statement PUT lfa1.
Once the corresponding event block in the program is complete, PUT lfa1 branches to the subroutine put_lfb1.
From this subroutine, the event GET lfb1 is triggered in the application program. If LFB1 is the last node to be read, processing resumes with the SELECTloop in put_lfb1. Otherwise, the program flow moves to the subroutine put_node of the next node. At the end of the SELECT loop of the last node, processing resumes in the SELECTloop of the node at the next level up. The example of programming using nested SELECT loops is only used to make the program flow clearer. In a real logical database, you would avoid doing this in order to minimize the number of database accesses.
Regards,
Rajesh K Soman
Please reward points if helpful.

Add Column name conditionally in a query

Hi i have an stored procedure where one parameter is passing
@Type
UserTable (columns) => username, canAdminDelete,canCustomerDelete,CanMerchantDelete
i wants to add column conditionally like when usertype =1 then query should be like
Select * from userTable where canAdminDelete=0
when userType=2
Select * from userTable where canCustomerDelete=0
Like in this way. I know i can write three if statments and write specific query.
But this is just an example i have very big query actually.
Please give some idea.
Thanks
Niki

Hi Niki,
As per my understanding, I think the query post by Olaf is correct. It only return the results when column canAdminDelete = 0 and userTpe = 1 or column canCustomerDelete = 0 and userType = 2.
So when userType=1 and column canAdminDelete=1, how could you get the results? Could you please test the issue again based on the query post by Olaf.
If there are any misunderstanding, please elaborate the issue for further investigation.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

AdvancedDataGrid - Add columns with ActionScript

I'm trying to add columns to an AdvancedDataGrid via ActionScript.
I can't get it to work.
I've tried two approaches -- One with an intermediary array to store the columns then set the adg's columns to the array; One where I assign the columns directly to the adg's columns array.
They both fail in their own way. The columns don't "take" and the adg uses the dataProviders defaults, or there are no columns at all.
"adg_test.mxml" has the AdvancedDataGrids/code.
"adg_test_renderer.mxml" is a renderer for one of the columns.
Would appreciate learning what I'm doing wrong.
Thanks for any help.
=== START adg_test_renderer.mxml ===
<?xml version="1.0" encoding="utf-8"?>
<mx:VBox xmlns:mx="http://www.adobe.com/2006/mxml">
     <mx:Button id="btnTest" label="Renderer Working"/>
</mx:VBox>
=== END adg_test_renderer.mxml ===
== START adg_test.mxml ====
<?xml version="1.0"?>
<mx:Application
    xmlns:mx="http://www.adobe.com/2006/mxml"
    initialize="init()">
    <mx:Script>
      <![CDATA[
         import mx.collections.ArrayCollection;
         [Bindable]
         private var dpADGExplicit:ArrayCollection = new ArrayCollection([
           {Artist:'Pavement', Album:'Slanted and Enchanted', Price:11.99},
           {Artist:'Pavement', Album:'Brighten the Corners', Price:11.99},
           {Artist:'Saner', Album:'A Child Once', Price:11.99},
           {Artist:'Saner', Album:'Helium Wings', Price:12.99},
           {Artist:'The Doors', Album:'The Doors', Price:10.99},
           {Artist:'The Doors', Album:'Morrison Hotel', Price:12.99},
           {Artist:'Grateful Dead', Album:'American Beauty', Price:11.99},
           {Artist:'Grateful Dead', Album:'In the Dark', Price:11.99},
           {Artist:'Grateful Dead', Album:'Shakedown Street', Price:11.99},
           {Artist:'The Doors', Album:'Strange Days', Price:12.99},
           {Artist:'The Doors', Album:'The Best of the Doors', Price:10.99}
         [Bindable]
         private var dpADGActionScript:ArrayCollection = new ArrayCollection([
           {Artist:'Pavement', Album:'Slanted and Enchanted', Price:11.99},
           {Artist:'Pavement', Album:'Brighten the Corners', Price:11.99},
           {Artist:'Saner', Album:'A Child Once', Price:11.99},
           {Artist:'Saner', Album:'Helium Wings', Price:12.99},
           {Artist:'The Doors', Album:'The Doors', Price:10.99},
           {Artist:'The Doors', Album:'Morrison Hotel', Price:12.99},
           {Artist:'Grateful Dead', Album:'American Beauty', Price:11.99},
           {Artist:'Grateful Dead', Album:'In the Dark', Price:11.99},
           {Artist:'Grateful Dead', Album:'Shakedown Street', Price:11.99},
           {Artist:'The Doors', Album:'Strange Days', Price:12.99},
           {Artist:'The Doors', Album:'The Best of the Doors', Price:10.99}
        private function init():void
            var arr:Array=[];//Intermediary array that will become the AdvancedDataGridColumn array
            var col:AdvancedDataGridColumn = new AdvancedDataGridColumn();
            col.dataField = "Artist";
            arr.push(col);
            col.dataField = "Album";
            col.visible = false;
            arr.push(col);
            col.dataField = "Price";
            col.itemRenderer = new ClassFactory(adg_test_renderer);
            arr.push(col);
            adgActionScript.columns = arr;
            //ALTERNATE UNSUCCESFUL APPROACH
            col.dataField = "Artist";
            adgActionScript.columns.push(col);
            col.dataField = "Album";
            col.visible = false;
            adgActionScript.columns.push(col);
            col.dataField = "Price";
            col.itemRenderer = new ClassFactory(adg_test_renderer);
            adgActionScript.columns.push(col);
      ]]>
    </mx:Script>
    <mx:Label text="Explicit Columns"/>
    <mx:AdvancedDataGrid
        id="adgExplicit"
        width="100%" height="100%"
        sortExpertMode="true"
        dataProvider="{dpADGExplicit}">
        <mx:columns>
            <mx:AdvancedDataGridColumn dataField="Artist" />
            <mx:AdvancedDataGridColumn dataField="Album" visible="false"/>
            <mx:AdvancedDataGridColumn dataField="Price" itemRenderer="adg_test_renderer"/>
        </mx:columns>
   </mx:AdvancedDataGrid>
   <mx:Label text="ActionScript Columns (If ActionScript works: Arist column should be hidden. Should see Album column with data and Price column with buttons."/>
    <mx:AdvancedDataGrid
        id="adgActionScript"
        width="100%" height="100%"
        sortExpertMode="true"
        dataProvider="{dpADGActionScript}">
   </mx:AdvancedDataGrid>
</mx:Application>
== END adg_test.mxml ====

Thanks so much for your help.
Here's how I altered your code for my example. This logic allows easier assignment of additional column parameters.
=== START adg_test_renderer.mxml ===
<?xml version="1.0" encoding="utf-8"?>
<mx:VBox xmlns:mx="http://www.adobe.com/2006/mxml">
    <mx:Button id="btnTest" label="Renderer Working"/>
</mx:VBox>
=== END adg_test_renderer.mxml ===
== START adg_test.mxml ====
<?xml version="1.0"?>
<mx:Application
    xmlns:mx="http://www.adobe.com/2006/mxml"
    initialize="init()">
    <mx:Script>
      <![CDATA[
         import mx.collections.ArrayCollection;
         [Bindable]
         private var dpADGExplicit:ArrayCollection = new ArrayCollection([
           {Artist:'Pavement', Album:'Slanted and Enchanted', Price:11.99},
           {Artist:'Pavement', Album:'Brighten the Corners', Price:11.99},
           {Artist:'Saner', Album:'A Child Once', Price:11.99},
           {Artist:'Saner', Album:'Helium Wings', Price:12.99},
           {Artist:'The Doors', Album:'The Doors', Price:10.99},
           {Artist:'The Doors', Album:'Morrison Hotel', Price:12.99},
           {Artist:'Grateful Dead', Album:'American Beauty', Price:11.99},
           {Artist:'Grateful Dead', Album:'In the Dark', Price:11.99},
           {Artist:'Grateful Dead', Album:'Shakedown Street', Price:11.99},
           {Artist:'The Doors', Album:'Strange Days', Price:12.99},
           {Artist:'The Doors', Album:'The Best of the Doors', Price:10.99}
         [Bindable]
         private var dpADGActionScript:ArrayCollection = new ArrayCollection([
           {Artist:'Pavement', Album:'Slanted and Enchanted', Price:11.99},
           {Artist:'Pavement', Album:'Brighten the Corners', Price:11.99},
           {Artist:'Saner', Album:'A Child Once', Price:11.99},
           {Artist:'Saner', Album:'Helium Wings', Price:12.99},
           {Artist:'The Doors', Album:'The Doors', Price:10.99},
           {Artist:'The Doors', Album:'Morrison Hotel', Price:12.99},
           {Artist:'Grateful Dead', Album:'American Beauty', Price:11.99},
           {Artist:'Grateful Dead', Album:'In the Dark', Price:11.99},
           {Artist:'Grateful Dead', Album:'Shakedown Street', Price:11.99},
           {Artist:'The Doors', Album:'Strange Days', Price:12.99},
           {Artist:'The Doors', Album:'The Best of the Doors', Price:10.99}
        private function init():void
            var arrCols:Array = adgActionScript.columns;
            var col:AdvancedDataGridColumn;
            col = new AdvancedDataGridColumn;
            col.dataField = "Artist";
            arrCols.push(col);
            col = new AdvancedDataGridColumn;
            col.dataField = "Album";
            col.visible = false;
            arrCols.push(col);
            col = new AdvancedDataGridColumn;
            col.dataField = "Price";
            col.itemRenderer = new ClassFactory(adg_test_renderer);
            arrCols.push(col);
            adgActionScript.columns = arrCols;
            adgActionScript.validateNow();
      ]]>
    </mx:Script>
    <mx:Label text="Explicit Columns"/>
    <mx:AdvancedDataGrid
        id="adgExplicit"
        width="100%"
        height="100%"
        dataProvider="{dpADGExplicit}">
        <mx:columns>
            <mx:AdvancedDataGridColumn dataField="Artist" />
            <mx:AdvancedDataGridColumn dataField="Album" visible="false"/>
            <mx:AdvancedDataGridColumn dataField="Price" itemRenderer="adg_test_renderer"/>
        </mx:columns>
   </mx:AdvancedDataGrid>
   <mx:Label text="ActionScript Columns"/>
    <mx:AdvancedDataGrid
        id="adgActionScript"
        width="100%"
        height="100%"
        dataProvider="{dpADGActionScript}">
   </mx:AdvancedDataGrid>
</mx:Application>
== END adg_test.mxml ====

Add columns to RCOPOC_WKLT

Hi.
Does anyone know how can I add columns (from my structure) at the above report?
It's the CO60 transaction (Worklist for PI Sheets).
I think it's somthing about an enhancement for this report but how can I do it??
Thanks,
Rebeka

Robeka
There is no way you can do enhancement to add new column to the ALV.... See report RCOPOC_WKLT, subroutine "build_fieldcat"....
Though, you can modify this report by using access key or create Z-Copy of this report and modify it....
Thanks
Amol Lohade

Bad performance when deleting report column in webi(with "Design – Structure only")

Hi all,
One of our customer has recently upgraded from BO XI to BO4.1. In the new BO 4.1, they encountered a bad performance issue when they were deleting a column in Webi(using "Design – Structure only" mode).
With “Design – Structure only" mode, it took webi about 10 seconds to complete after the customer right-clicked a report column and clicked the "delete". The customer said that they only need to wait for less than 1 second when they did the same in BO XI old version.
The new BO version used is 4.1SP02, installed in Windows Server 2008 R2. (Server with 32 core CPU, 32G memory)
This bad performance happened in both Webi web and Rich Client. (in Webi Rich Client, the performance is a little bit better. The 'delete column' action takes about 8 seconds to complete).
Do anyone know how to tune this performance in webi? Thank you.
Besides, it seems that each time we are making change in the webi report structure in IE or Rich Client, webi need to interact with Server site to upload the changes. Is there any option to change this behavior? Say, do not upload change to Server for when 'deleting report column', only trigger the upload after a set of actions(e.g. trigger when click the "Save" button).
Thank you.
Regards,
Eton.

Hi all,
Could anyone help me on this? Thanks!
What customer concerns now is that when they did the same 'column editing' action in BO XI R2 for the same report, they did not need to wait. And they need to wait for at least 7-8 second in the BO 4.1SP02 environment for this action to complete.(data already purged, in structure-only mode)
One more information about the webi report being editing is: there are many sheets in the report(about 6~10 sheets in one report). Customer don't want to separate these sheet into different reports as it will increase the effort of their end users to locate similar report sheets.
Regards,
Eton.

How to add column to report from the same table? Gives error now

Steps to reproduce:
Build a report on a table with easy report, select all columns
Add column to the table
Edit report and add column (one has to click Show Related Tables Only: No to view the same table!)
Report will give error as it will be build as
SELECT ... FROM table1, table1

AH HAAA!!!!
And I was afraid to convert from the "SQL (Structured Query)" to "SQL". Probably because I blew up my other reports...
Thanks!

Add column with preq number to ALV grid in me53n

hi all,
i am trying to add column with preq number (BANFN) to ALV with preq items in ME53N. it is not available in column set, when trying to add by "change layout" button - i dont understand why, when the strcucture MEREQ3211GRID contains it :-(
i also tried to add new field ZZBANFN into the structure CI_EBANMEM and after that, i could add the new field to ALV through change layout, but it was empty of course. so i implemented EXIT_SAPLMEREQ_001 from MEREQ001, but ZZBANFN is still empty, because this exit is not called when opening ME53N, but when clicking on tab "customer data" in preq item detail.
how to solve this? is there any exit that is called before displaying the ALV grid?

Here is some more detail. I included my code from the Enhancement.
ENHANCEMENT-POINT MM06EFPO_POT_AUFBAUEN_02 SPOTS ES_MM06EFPO_POT_AUFBAUEN INCLUDE BOUND.
   ENHANCEMENT 1 Z_MM06EFPO_POT_AUFBAUEN_1.    "active version
SELECT SINGLE zz_old_material FROM mara
    INTO pot-zz_old_material
    WHERE matnr = pot-matnr.
ENDENHANCEMENT.
You will also need to change the layout in Item Overview to bring your field in.

How to add column in Dynamic VO

Hello All,
We are on 11.5.10 and
i am trying to add a column toProduct - Supplier Items - click Orders page
when i click about this page it is showing this
POS_SUPPLIER_INQUIRIES177_POS_PO_LINES_D2177_177POS_PO_LINES_DDynamicVO
This has Dynamci VO.
How do i add column to this view.
It seems that this view is based on AK Region POS_PO_LINES_D and this region is based on a view POS_PO_LINES_V.
Please help me in doing this.
Thanks,
Mehta.

Check the page's controller code. That will point you to the base definition of the VO used in the dynamic view.
--Shiv

Nsert/Update and Add Column at the same Table and at the "same" Time

Hello,
I want Insert/Update and Add Column at the same Table and at the "same" Time but in different sessions.
Example:
At first the "insert/update" statement:
Insert into TestTable (Testid,Value) values (1,5105);
After that the "add" statement:
Alter table TestTable add TestColumn number;
- sadly now I get the message: ORA-00054: resource busy and acquire with NOWAIT specified
"insert/update" statement:
Insert into TestTable (Testid,Value) values (2,1135);
After that the execute commit.
I don't know when the first session set the commit statement so I want that the DB the "Alter Table..." statement execute if it's possible.
If it's possible I want to save a repeat loop with the "Alter Table..." statemtent.
Thanks for ideas

Well I want to walk in the rain without and umbrella and still stay dry, but it ain't gonna happen.
You can't run a DDL statement against a table with transactions pending. Session 2 has to wait until session commits or rollbacks (or until the session is killed). That's just the way it is.
This makes sense if you think about it. The data dictionary has to be consistent across all sessions. If session 2 was allowed to change the table structure whilst session 1 has a pending transaction then the database is in an inconsistent state. This is easier to see if you consider the reverse situation - the ALTER TABLE statement run by session 2 does a DROP COLUMN TESTID rather than adding a column: now what should happen to session 1's INSERT statement? You have retrospectively invalidated a statement that was perfectly legal when it was executed.
If it's possible I want to save a repeat loop with the "Alter Table..." statemtent.Fnord.
Cheers, APC

Add column in Staff Assignemnt Area(Structure) of transaction PPOME

Similar Messages

Maybe you are looking for