Problem while calculating date based on the selection

Hi friends,
On my selection screen i have 2 fields
a) 1 WEEK
b) 2 weeks
now when the user enters value yes in 1 week it should display the data which are less than one week old from current date and if user enters yes in 2weeks field then it should display the data which are less than 2 weeks old from the current date.
ie : in my internal table i have a date field zdate
now i should check if the ZDATE is within one week range ( for 1WEEK FIELD ) it should display only that data.
similary i should check for ( 2week field on the selection scree)
How can i do that...
Any function modules available for the above requirment.
Thanks in advance.
Regards
Kumar

Hi Kumar,
SY-DATUUM - X does not work when the month and year changes..
for example if the current date is 02/01/2010
now if i say sy-datum - 7 , the system will not recognise the month and year change here...
I'm not sure what you're saying here is accurate. I created the following piece of code to check;
data l_var type datum.
l_var = '20100102'.
l_var = l_var - 7.
Write: / L_var.
The value of l_var at the end was 26.12.2009, which seems to work for me. Anurag's answer seems to be correct.
Regards,
Nick
P.S. Your question actually breaks the forum rules, questions on manipulating dates have been asked many times before and the answers typically only require basic arithmatic

Similar Messages

Report to show data based on the Selection

I have a prompt which is having three filters i.e. Region Country and City.
I have to create a report which shuold show the revenue share based on the selection of the Prompt.
Say When the Region is selected as Eurpoe then report should be:
Europe : 12%
Say When the Counrty is selected as UK then report should be:
UK: 6%
Say When the City iis selected as London then report should be:
London : 1.2%
How can we get this implemented?

You want a level based measure in the BMM which will allow you to derive the region share regardless of filtering.
Then simply use Region is prompted in the report to filter for only the region you want.
For level based measure, duplicate your measure and drag it to the total level of your Region hierarchy. Define you % measure in the BMM as a logical calc.
Hope this helps,
Regards
Alastair

Filtering of the data based upon the selection screen data using ldb

Hi Experts ,
I am using ldb pnpce, for my report ,and i created my own report category with selection paramaters
action type and payroll area
now the problem is when i am giving the action type as Z0 ,the data to be extracted is not getting filtered
based upon the action type ,the data consists the records having different action types other than Z0
Please give me some solution for this

Thanks Durga ,but the link wat ever u was for hiding the selection screen fields
but my question is when am using get pernr event my data is not getting filtered with the selection screen paramater value
i,e m giving action type as only hiring ,but m getting the data for all the action types ,its not filtering based upon my selection

Splitting the date based on the selection screen input

Hi all,
In the Selection screen of my report i had maintained two fields
SELECT-OPTIONS : S_DATE    FOR TPCDATE-FROM_DATE.
PARAMETERS      : P_NUMBER TYPE ZMMAREA-NUMBER.
I need to code such that
S_DATE should be splitted into P_NUMBER times
for example if P_NUMBER is 4 i need S_DATE should be splitted into 4 equal parts or near by equal parts
                    IF P_NUMBER is 2 i need S_DATE should be splitted into 2 equal parts or near by equal parts
Please suggest me the code of if any Function module exists fot this date splitting
Thanks in advance
Ajay.D

though date question are not allowed, this requirement sounds little different.
you can take a difference between those days by: S_date-high - S_date-low.
then divide the difference by p_number. now you get the split positions.
now in a do enddo you can negate the dates by the split amount you got from the divisions.
like...
PARAMETERS: num type i.
select-OPTIONS: s_date for sy-datum.
data : gv_split type i, gv_temp type sy-datum.
gv_split = s_date-high - s_date-low.
gv_split = gv_split / num.
gv_temp = s_date-high.
do num times.
gv_temp = gv_temp - gv_split.
WRITE / gv_temp.
enddo.

While selecting value from combo box in one frame, based on the selection..

Hi friends,
can someone help me out on a issue as it follows:-
iam developing an application where Iam using xsl,html,javascript and xml.
There is no existense of Database at all. data is read from xml.
now,
In a window there are 3 frames. In the 1st frame combo box is there.
Based on the selection in the combo box data will be displayed in the 2nd frame.
now onchange or onselect methods not giving the expected result.
actually,in the the xsl which is having 3 frames,the 1st and 3rd frame
calling src="abc.xml" and src="abc.xml"which are static.
but in the 2nd frame the data need to be changed dynamically.
I have given frame name="frame_ExchangeDetails2" rows="3%" src="cc_marketWatch_02.xml"/>
usually data dynamically comes from database.but here i have to refer xml file
something like [window.href.location="abc.xml"]
but the problem is when you refer supose:-
<frame name="frame_ExchangeDetails2" rows="3%" src="cc_marketWatch_02.xml"/>
the frame is having static page,though there are functions in javascript which are called in onload and onchange.which are not working.
I have tried putting if condition like:-
if(document.abc.fieldname.value=='6'
{ window.location.href = "cc_custLookUpData-mobileno.xml";
so that it could go to the repective page.
but it is not working.
so what should i do if I select from combo box in one frame and based on the selection xml/html page will be displayed in the 2nd frame.
if anybody has google account i can forward the zip file so it will be easier to understand.
Regards
Message was edited by:
Postqueries
Message was edited by:
Postqueries

If you have rights to modify tabular model then, you can create a measure in your Tabular model which returns previous week and then use this measure in Pivot Table.
Thanks,
Sagar K
(Blog: http://datamazik.blogspot.in/)

Problem while retrving data from a view

Hi Friends
i have a problem while retriving data from a view <b>v_t685a</b>.
the error message is :""" "V_T685A" is not defined in the ABAP Dictionary as a table, projection view or database view."""
i wrote : select single VTEXT1 from V_T685A into w_cst_jin1 where
                    KSCHL = 'JIN1' and
                    KAPPL = 'V'.
how to retrive the data.
waiting for quick response
Regards
Mukesh

Hi
This is a Maintenance View, not a Database View
SO can't fetch data using select statement.
You can use the Table <b>T685</b> directly to fetch the condition Types data straight away instead of the view. write the same select for this table and use.
Regards
Anji
Message was edited by:
        Anji Reddy Vangala

I have to combo box content change based on the selection on the other

I have huge unsolve problem where by I have to combo box change content of the combo box based on the selection in the first combo box . The problem is The value changes do not have effect on the second combo box. Below is the content of the coding used for both the combo box.
function setReasonCode(obj){
                     <%String sql_query3 = "SELECT DISTINCT (ir_tran_typ) "+
                                          " FROM intrcd ";
                           System.out.println("trans type"+sql_query3 );
                            try{
                                rset = db.execSQL(sql_query3);
                            catch(SQLException e) {
                                System.err.println("Error in query - intrcd - transaction_main.jsp " +e +" sql " +sql_query3);
                            while(rset.next()){
                                tran_cde = rset.getString("ir_tran_typ");
                                        tran_typ.addElement(rset.getString("ir_tran_typ"));
                                        System.out.println("trans type 34 "+tran_typ );%>
                                        <% }%>
                                      alert(obj.value);
                              <%for(int i=0 ;i<tran_typ.size();i++){
                                 System.out.println("trans type 222 "+ tran_typ.size());
                                   tran_cde =tran_typ.elementAt(index).toString();%>
                                   <%System.out.println("trans type before "+ tran_cde);%>
                                    eval(document.all.tran_cde.option
                                  if(D == <%=tran_cde%> ){
                                   <%System.out.println("trans type D"+ tran_cde);%>
                                 <%String sql_query2 = "SELECT ir_rea_cde,ir_rea_desc"+
                                          " FROM intrcd"+
                                          " WHERE ir_tran_typ = 'D' " +
                                                    " ORDER BY ir_rea_cde ";
                           System.out.println("query"+ sql_query2);
                            try{
                                rset = db.execSQL(sql_query2);
                            catch(SQLException e) {
                                System.err.println("Error in query - emmast2 - transaction_main.jsp " +e +" sql " +sql_query2);
                                    index = 1;
                            while(rset.next()){
                                    rea_cde = rset.getString("ir_rea_cde");
                                    rea_desc = rset.getString("ir_rea_desc");
                                   tran_typ.removeAllElements();
                                   }%>
                              if( R == obj.value){
                                   alert(R)
                                  if(R== <%=tran_cde%> ){
                                   <%System.out.println("trans type R"+ tran_cde);%>
                                 <% sql_query2 = "SELECT ir_rea_cde,ir_rea_desc"+
                                          " FROM intrcd"+
                                          " WHERE ir_tran_typ = 'R' " +
                                                    " ORDER BY ir_rea_cde ";
                           System.out.println("query 2"+ sql_query2 );
                            try{
                                rset = db.execSQL(sql_query2);
                            catch(SQLException e) {
                                System.err.println("Error in query - intrcd - transaction_main.jsp " +e +" sql " +sql_query2);
                                    index = 1;
                            while(rset.next()){
                                    rea_cde = rset.getString("ir_rea_cde");
                                    rea_desc = rset.getString("ir_rea_desc");
                                   }%>
          <%}%>
            }

Not unless you know which file in the app sets the choices. I've been through it pretty thoroughly and can't find the one.

Problem while loading data from ODS to infoobject

Hi guys,
I am facing problem while loading data from <b>ODS to infoobject</b>.
If I load data via PSA it works fine but
if I load data without PSA its giving error as Duplicate records.
Do u have any idea why it is so.
Thanks in advance
savio

Hi,
when you load the data via the PSA, what did you select? Serial or Paralel?
If you select serial most likely you don't have duplicates within the same datapackage and your load can go through.
Loading directly in the IObj will happen thefore if you have the same key in two different packages, the "duplicate records" will be raised; you can perhaps flag your IPack with the option "ignore duplicate records" as suggested...
hope this helps...
Olivier.

What is the procedure/code in VBA for passing the calc scripts dynamically based on the selection.

Hello Gurus,
I want to know what is the procedure/code in VBA for passing the calc scripts dynamically based on the selection.
For example:
X=EssVCalculate("Sheetname","Calc_Script name",True)
In the above code instead of the *"Calc_Script name"* I want a script which is called dynamically and the values are calculated accordingly.
Thanks in advance
Saurabh

Hi Todd,
This is the situation:
I have a calc script in Essbase which I can call to perform the calculations on the current sheet that is retrieved. I want calculation for the following formulas:
x = EssVCalculate("Sheet2", "CalcBC", False)
CalcBC is my calc script which is present in Essbase
So instead of passing the above script I want to pass the conditions dynamically in the VBA code . I don't want to mention the script name directly in EssVCalculate option
For example:
I have three drop down menus from which I would select three different( zero level )members. It would then retrieve the data for that particular values in the excel sheet and now when I click on Calculate button it should calculate the script dynamically.
I don't know how calc scripts can be executed dynamically in the VBA code itself.
Thanks in Advance
Saurabh

Problem while transferring data between views

HI,
I have been assigned to a requirement wherein i am working first time in web dynpro. So i followed all the pdf training document for developing application. Now there is a requirement wherein have created 2 views and its required nodes and i have attached those 2 views to window with necessary plug binding. Its for travel report . On first view i have one selection screen and ALV display for header data. Now i am using using components for alv which is defined both in controller as well as in view. Also i am suing onclick property of that alv. Now the thing is that there are 2 nodes respectively HEAD and ITEM. HEAD node would get displayed on first screen and based on selection of one row from that ALV, its corresponding item data would get displayed in another view for which i have written code in method of first view . From that method i am filling data based on raw selection and passing it to second view. The problem is i have done necessary binding and pluging but still when i pass data from first view to second view dump get displayed saying that ITEM node not found for which i have added that ITEM node to both view first view and second view.still problem persist. As an RND i also removed table from second view and it was observed that control is flowing to second view it means there is no issue wid plug binding. Even when i removed alv from second view and put in first view then its working fine.What could be cause of this problem ? I am using ALV component SALV for first view and for second view i am using TABLE element of layout. Can i use same component for second view also ?
Kindly suggest.
Thanks
Parag

Hi,
You have to created a new method subscribing ON_LEAD_SELECTION event of the ALV, which will get triggered on selection of a row in the ALV.
Now, in the same method get the selected row data and write the logic to fill fetch the item details for the selected row and bind the item data to the ITEM node which you are going to display in second view. So as the item data is binded to the ITEM node, the data gets populated in the table ( which is there in second view ) .
DATA:         node_X    TYPE REF TO if_wd_context_node,
                    elem_X    TYPE REF TO if_wd_context_element,
                    stru_X      TYPE f_main=>element_X .
node_X = wd_context->get_child_node( name = wd_this->wdctx_X ).
* get element via lead selection
elem_X = node_search_results->get_element( r_param->index ).
* get all declared attributes
elem_X->get_static_attributes(
    IMPORTING
      static_attributes = stru_X ).
depending on the stru_X values fetch the item data and bind the data to the ITEM node.
Thanks,
Shailaja Ainala.

Problem when sorting data based on date

I am trying to sort the following data based on the Transaction Receipt date column,unable to do it usi g the following syntax:
<?sort:TRANSACTION_RECEIPT_DATE;'ascending';data-type='date'?>
I have problem in converting the date in report to canonical date ,is there any other way to achieve the output without converting the date format.
<?xml version="1.0"?>

<RECDTREP>
<LIST_G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO104</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24636</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863063</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO107</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24641</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863068</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO123</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24658</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863086</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO75</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>22190</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860842</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO116</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64271</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863077</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO92</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>22253</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860890</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO99</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>31-MAR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>22263</OBJECT_ID>
<INITIALIZATION_DATE>14-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510860899</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>31-Mar-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>971515</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO109</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>64204</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863070</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO135</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/18 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64296</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510875546</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO101</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24618</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863046</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO120</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24653</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863081</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO122</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24657</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863085</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO127</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>24662</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863090</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO100</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>07-APR-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1></SNO_ATTRIBUTE1>
<OBJECT_ID>24585</OBJECT_ID>
<INITIALIZATION_DATE>07-APR-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863033</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO110</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/11 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64265</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510863071</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
<G_ASW_REC_DATE>
<SNO_CREATED_BY>1433</SNO_CREATED_BY>
<SNO_REQUEST_ID>-1</SNO_REQUEST_ID>
<VENDOR_LOT_NUM>PO130</VENDOR_LOT_NUM>
<SNO_CREATION_DATE>25-JUN-09</SNO_CREATION_DATE>
<SNO_ATTRIBUTE1>2008/06/13 00:00:00</SNO_ATTRIBUTE1>
<OBJECT_ID>64275</OBJECT_ID>
<INITIALIZATION_DATE>30-JUN-09</INITIALIZATION_DATE>
<ORGANIZATION_CODE>10</ORGANIZATION_CODE>
<ORGANISATION_NAME>NDC - PARTS</ORGANISATION_NAME>
<SERIAL_NUMBER>6510875487</SERIAL_NUMBER>
<ITEM_CODE>3000.006</ITEM_CODE>
<DESCRIPTION>ALLISON 3000 SERIES ON HWY TRANSMISSION E016392</DESCRIPTION>
<MANUFACTURER>ALLISON</MANUFACTURER>
<APPLICATION>On Highway</APPLICATION>
<ITEM_COST>8879.02</ITEM_COST>
<MATERIAL_COST>631.09</MATERIAL_COST>
<CURRENCY_CODE>AUD</CURRENCY_CODE>
<PO_UNIT_PRICE></PO_UNIT_PRICE>
<TRANSACTION_RECEIPT_DATE>25-Jun-09</TRANSACTION_RECEIPT_DATE>
<PO_NUMBER>982121</PO_NUMBER>
</G_ASW_REC_DATE>
</LIST_G_ASW_REC_DATE>
<CF_SORT_BY>Manufacture,Receipt Date,Organization,Item Code</CF_SORT_BY>
<CF_SERIAL_WHERE></CF_SERIAL_WHERE>
</RECDTREP>

HI Mahesh,
<TRANSACTION_RECEIPT_DATE>07-Apr-09</TRANSACTION_RECEIPT_DATE>
this is not a date,
so you should change the query to get you the format in xsd format : YYYY-MM-DDThh:mm:ss+HH:MM
otherwise, you have to write a custom sort function to decode and order it it.
if you dont do the custom order and use
<?sort:TRANSACTION_RECEIPT_DATE;'ascending';data-type='date'?>
the data will be treated as string and you will see the row is sorted on string.

Populating other fields in a form based on the selection in a combobox field

We have done a form(masterdetail) in which we have a combobox field.When we make a selection in the field we require some two other fields to be automatically populated retrieving data from a table(which has the details required) based on the selection made.For eg. Selecting emp id(combobox) should populate empname and salary automatically in the form.Is this possible?If so how can this be done?
Thanks & Regards,
Jayanthi.S

This is what I did following Michael's suggestion and it works fine :-
1> Created a dynamic LOV named LOV_EMPNO as:-
select empno,empno from scott.emp
2> Started creating a form named FORM024_EMP2 on scott.emp.
3> On reaching the Formatting and Validation section, I chose the EMPNO field in the left frame.
In the right frame for EMPNO, I changed the item-type to Combobox and selected the lov LOV_EMPNO.
Then I went to the Javascript handler section for EMPNO, chose the Javascript event onChange and in the
adjacent Textarea, I wrote:-
popdetails(this);
We will create the javascript function popdetails() in the Additional pl/sql section.
4> Click next and goto the Additional PL/SQL section and I wrote the following code in
"...after displaying the page" area.
(You can write this either in
before displaying the page,
before displaying the form,
after displaying the form,
after displaying the page).
declare
type tvcarr is table of varchar2(2000) index by binary_integer;
l_empno_arr tvcarr;
l_ename_arr tvcarr;
l_sal_arr tvcarr;
begin
select empno,ename,sal
bulk collect into
l_empno_arr,l_ename_arr,l_sal_arr
from scott.emp;
htp.p('
<script>
var empdets = new Array();
empdets[0] = new Array("","");
for i in 1..l_empno_arr.count
loop
htp.p('empdets['||l_empno_arr(i)||'] = new Array("'||l_ename_arr(i)||'","'||l_sal_arr(i)||'");');
end loop;
htp.p('
function popdetails(ele)
var val = new Number();
var thisform = ele.form;
val = parseInt(ele.value);
if (isNaN(val))
val = 0;
for (var i = 0; i < thisform.length; i++){
if (thisform.name == "FORM024_EMP2.DEFAULT.ENAME.01")
thisform[i].value = empdets[val][0];
else if(thisform[i].name == "FORM024_EMP2.DEFAULT.SAL.01")
thisform[i].value = empdets[val][1];
htp.p('</script>');
end;

How to fetch data based on this selection screen

Hi Friends:
I've a selection screen which contains these 3 fields:
company code (t001-bukrs)
material division (mara-spart)
posting date (bkpf-budat)
based on the above fields, I've to fetch the following:
ekpo-bukrs
mara-spart
mseg-werks
mseg-lgort
bseg-hkont
bseg-kostl
bseg-hkont
skat-txt50
mseg-mblnr
mseg-zeile
bseg-belnr
bkpf-bktxt
mseg-insmk
bkpf-monat
bkpf-budat
mseg-bwart
mbew-matnr
makt-maktx
mseg-menge
mseg-meins
mbew-stprs
mseg-dmbtr
bseg-pswsl
ausp-atwrt
mara-matkl
mara-mtart
mbew-bklas
mbew-bwtar
mkpf-vgart
mcha-charg
mseg-ebeln
aufk-aufnr
mseg-ummat
vbak-vbeln
likp-vbeln
bkpf-usnam
Please help me with the logic . I want to ask that in which order I should start fetching data.How to relate it from selection screen. Which table I should fetch first based on the selection screen.how to relate mseg/bseg/mara/mbew/vbak/bkpf etc.
Please help.
Thanks for your time.

Hi,
I dont think you need EKPO to fetch your bukrs. It is available in BKPF too.
Use inner join to join MKPF, BKPF, MAKT, fetch all the related entreis.
Use Inner join on MBEW, MCHA for all entries from above query.
use inner join on AUSP for all entries from above query.
Use may use separate queries or inner joins for LIKP and VBAK with for all entries.
Use separate for all entries for BSEG and MSEG. Do not use any JOIN on BSEG as it is a pooled table.
As per the need you may change the queries..
Regards,
Subramanian

I've to extract the data based on the sysdate...like today dd is 11,

BM_PERF is the table name and
BM_PERF_YR,BM_PERF_MONTH,BM_NOP_CT_1........BM_NOP_CT_31 are the column names.
I've to extract the data based on the sysdate...like today dd is 11
so i've to get data from BM_NOP_CT_11 and the column names changes dynamically based on the sysdate. don't use any procedures and functions.

You could always pivot it into a more convenient form for querying:
WITH t1 AS
     ( SELECT 2008 AS yr, 4 AS mnth
            , 20 AS dy1
            , 10 AS dy2
            , 15 AS dy3
            , 1 AS dy4
            , 17 AS dy5
            , 99 AS dy6
            , 55 AS dy7
            , 45 AS dy8
            , 33 AS dy9
            , 22 AS dy10
            , 74 AS dy11
            , 35 AS dy12
            , 62 AS dy13
            , 24 AS dy14
            , 85 AS dy15
       FROM dual )
   , t2 AS
     ( SELECT yr
            , mnth
            , sys.DBMS_DEBUG_VC2COLL
              (dy1,dy2,dy3,dy4,dy5,dy6,dy7,dy8,dy9,dy10,dy11,dy12,dy13,dy14,dy15)
              AS day_data
       FROM   t1 )
SELECT t2.yr, t2.mnth, sys_op_ceg(t2.day_data,5) day_value
FROM   t2;
        YR       MNTH DAY_VALUE
      2008          4 17
1 row selected.Note that SYS_OP_CEG (first discovered by Padders) is undocumented and unsupported - for production code you'd need to pick the collection row using a WHERE clause, and for that you'd need a custom object and collection type with an attribute to hold the day number.
Message was edited by:
William Robertson
...like this:
CREATE TYPE id_value_ot AS OBJECT
( id INTEGER, val NUMBER );
CREATE TYPE id_value_tt AS TABLE OF id_value_ot ;
WITH t1 AS
     ( SELECT 2008 AS yr, 4 AS mnth
            , 20 AS dy1
            , 10 AS dy2
            , 15 AS dy3
            , 1 AS dy4
            , 17 AS dy5
            , 99 AS dy6
            , 55 AS dy7
            , 45 AS dy8
            , 33 AS dy9
            , 22 AS dy10
            , 74 AS dy11
            , 35 AS dy12
            , 62 AS dy13
            , 24 AS dy14
            , 85 AS dy15
       FROM dual )
   , t2 AS
     ( SELECT yr
            , mnth
            , id_value_tt
              ( id_value_ot(1,dy1)
              , id_value_ot(2,dy2)
              , id_value_ot(3,dy3)
              , id_value_ot(4,dy4)
              , id_value_ot(5,dy5)
              , id_value_ot(6,dy6)
              , id_value_ot(7,dy7)
              , id_value_ot(8,dy8)
              , id_value_ot(9,dy9)
              , id_value_ot(10,dy10)
              , id_value_ot(11,dy11)
              , id_value_ot(12,dy12)
              , id_value_ot(13,dy13)
              , id_value_ot(14,dy14)
              , id_value_ot(15,dy15) )
              AS day_data
       FROM   t1 )
SELECT yr, mnth, dd.val
FROM   t2, TABLE(t2.day_data) dd
WHERE dd.id = 5;
        YR       MNTH        VAL
      2008          4         17
1 row selected.

Problem while uploading data with GUI UPLOAD Function

Hi,
I am facing problem while uploading data with FM GUI UPLOAD in out text file there are 7 row but after the FM GUI UPLOAD there are 14 entries are coming in Internal table and each alternate row is coming as blank with 0000 in some column in internal table first row is proper and second line is blank so on.
what can be the problem .
The program in which we are using this we are using it from last 2 year but we are facing problem today only.
regards,
zafar

Hi,
The file formate is same as it is from last two years it is automatically generated by one another bar code server and there is no change in the file formate.
So waht can be the problem to check any inconsistancy in system i have develop a samll program fro uploading a text file with same function module , but it is working fine.
regards,
zafar

Problem while calculating date based on the selection

Similar Messages

Maybe you are looking for