According to PO number and Line item data should come once but its repeatin

I am calculating IR Quantity and IR value......
for a PO  if there are four same  line items i wanted them once but they are displaying for each and every line item
If my po is 2003000151 and line item 0010 if both are same then i wanted ir quantity 500
but its displaying like this
  PO                 item   IR
2003000151   0010 500
2003000151   0010 500
2003000151   0010 500
2003000151   0010 500
I need like this
2003000151   0010 500
2003000151   0010
2003000151   0010
2003000151   0010
If po number and line item are same IR quantity should be displayed only once..
What should be done if it should not repeat in each and every line item if both PO and line item are same

i am having internal table of it_ekko.
in that i am having some data of PO no, Line Item,IR value and IR qty......
i am having data like below.
PO                        Line Item   IR Value    IR QTY 
200310051          0010         1500           4500
200310051          0010        1500           4500
200310052         0010           0                   0
200310052          0010       0               0
now where ever IR value and IR qty is present i wanted that to display only once against that PO and line item
i wanted like below
PO                        Line Item   IR Value    IR QTY 
200310051          0010         1500           4500
200310051          0010            0              0
200310052         0010             0                0
200310052          0010            0               0
Field names for IR value and IR Qty are Menge2 and dmbtr2.
How to do that.........
I cant use
Delete adjacent duplicates of it_ekko by ebeln = wa_ekko-ebeln and
                                                                      ebelp = wa_ekko-ebelp.
because i wanted that po and same line items , how many times it is like that only.....
in it_ekko table i only wanted to delete duplicates of menge2 and dmbtr2.
Pls suggest the code

Similar Messages

  • MIGO-sales order number and line item not validated for 501E mvt in MIGO.

    Hi All,
    In MIGO i am trying to post for 501E(specisl stock=order on hand) movement type, here i am entering the material and in the where TAb even if I enter wrong sales order number or wrong sales order line item number. the system allows to post .
    its not validating the material against the sales order number and line item number that is entered to check whether that material really exists in that particular sales order or not.
    is there a way to fix this?
    Thanks
    Mahendra

    hi
    i dont think vvalidation is possibel
    as the system dont know whaich material is assigned to which SO
    as we r takeing the stock without PO
    if u want to validate then system can validate the quantity that is also with use of some user exit
    correct me if i am wrong

  • PO comparison with similar materila number and line items

    Dear Friends,
       I wish to know in a report how i classify the pos having similar material and line items in each other, Like po number is 12 and has material numbers 1, 2, 3
    where po number 13 and has material 1,2,3. how i fetched the data from the table and classify them with similar material and line items, please tell me. any article, example, code will be grete help of mine,
    thanking you
    regards
    Naim

    Guess you need to display report with Purchase Order nos where Material nos are similar.
    On selection screen add parameters Material and Line Item no. Both should ba mandatory.
    Get data from EKPO where MATNR = P_MATNR and EBELP = P_EBELP.
    Display the same in report output.
    Just need to check with you - Material nos can be same on multiple POs but Material, Item no combination may not be.
    I can use same material in another PO with different Line Item as other PO already has some line items. Why do you need this check?

  • Purchase requistion number and line item number linkage with work order opr

    Hello,
    I want to know what is the link between Purchase requisition number along with its line item number with work order operation number.
    For the non stock component assign to Work order operation ( say operation 10) the PR get generated for that component which assign to that operation .
    in which table we can find that PR as input and output as Work order number along with its operation .
    In AFVC table if we put PR as input then it does not show any entry for that PR number?
    Regards
    Vaibhav

    HI Vaibhav,
    If you have the Work Order Number AUFNR, then you can get AUFPL from AFKO.
    Then Pass AUFPL to AFVC table to get BANFN(Purchase requisition number) and BNFPO(Item number of the purchase requisition in the order).
    Regards,
    Ravi

  • GL Custom Reports not displaying source and line item Data after Upgrade

    Hi,
    I am having this issue even though General Ledger Journal Entry Summarization is set to "No Summarization" and in SLA the Line Type is set in detail for Transfer to GL. Have you come accross a specfic example like this? Can you please guide me to what the problem may be?
    None of the GL reports is showing the Source and Line Item details.
    Thanks,
    Arun

    I am having this issue even though General Ledger Journal Entry Summarization is set to "No Summarization" and in SLA the Line Type is set in detail for Transfer to GL. Have you come accross a specfic example like this? Can you please guide me to what the problem may be?
    None of the GL reports is showing the Source and Line Item details.Have you verified the queries of those reports after the upgrade? And, when you say upgrade, do you mean from 11i to R12?
    Did you set the application context properly?
    How to set the Organization Context in R12? [ID 437119.1]
    Oracle Applications Multiple Organizations Access Control for Custom Code [ID 420787.1]
    SQL Queries and Multi-Org Architecture in Release 12 [ID 462383.1]
    Setting APPS Context is mandatory step while loading data using public APIs [ID 473615.1]
    Thanks,
    Hussein

  • How to get PO number and line item in he check item method of MB_MIGO_BADI

    Hi All,
    First time I am using BADI and I am stuck in one issue.
    I am using CHECK_ITEM method of MB_MIGO_BADI.
    While pressing CHECK button MIGO for a GR(wrt to a PO),a warning message has to displayed.This warning message has to displayed according to the line item in the purchase order.
    In the CHECK_ITEM method, how I will get the PO number and the line item imported into that method.?
    Thanks.

    HI  ,
    in Check_item method 
    DATA: ls_extdata TYPE zqsscrap_screen_field .
    LOOP AT gt_extdata INTO ls_extdata .
    endloop.
    Check what you are getting  .
    regards
    Deepak.

  • PO Number and Line Item Number for Invoice Plan Number

    Hi Experts,
    Can somebody please guide me how to fetch the PO Number and respective PO Line Item Number for an Invoice Plan (FPLNR).
    In FPLA Table, PO number is available but line item number is not available.  If a PO is having multiple line items, different line items will have different Invoice Plan numbers.
    Thanks in Advance.
    Radha Krishna Madineedi

    Hi Ramesh,
    I have got the answer after posting this thread.  We can get the PO Number and the Line Item from EKPO Table itself by passing the FPLNR.
    Anyway,  thanks for your reply.
    Regards
    Radha Krishna.

  • Line item data is not saving while creating a Sales order using Interactive

    Hi all,
    I am creating a sales order Using Interactive forms. In the form i am having Header data and line item data.I had created two structures one for Header data and one for Line item data. For entering  the LINE ITEM DATA i had created a Dynamic table with Buttons ADD ROW and DELETE ROW.
    User will Add the Row or Delete the Row based on the requirement.
    My issue is When ever the user clicks the SUBMIT button after entering the header data and 3 line items data , Sales order has been created with only first line item and the remaining two line items are not created.
    My Interactive form is like below
    HEADER DATA
    DOC_TYPE
    SALES_ORG
    DIST_CHN
    DIVISION
    PURCH_NO
    PARTN_ROLE
    PART_NO
    LINE ITEM DATA
                             ITEM_NO      MATERIAL          PLANT          QTY        COND_TYPE            COND_VALUE
    ADD ROW
    DELETE ROW
                                                                                    SUBMIT
    My  code for the method ONACTIONCLICK is like below
    method ONACTIONCLICK .
    data:
          Node_Adobe       type ref to If_Wd_Context_Node,
          Node_Zsaleheader       type ref to If_Wd_Context_Node,
          Elem_Zsaleheader       type ref to If_Wd_Context_Element,
          Stru_Zsaleheader       type If_Main=>Element_Zsaleheader,
          Node_Zsaleitem       type ref to If_Wd_Context_Node,
          Elem_Zsaleitem       type ref to If_Wd_Context_Element,
          Stru_Zsaleitem       type If_Main=>Element_Zsaleitem.
      data: header_data type BAPISDHEAD.
      data: item_wa type BAPIITEMIN.
      data: item_data type table of BAPIITEMIN.
      data: partner_wa type BAPIPARTNR.
      data: partner_data type table of BAPIPARTNR.
      data: sales_order type BAPIVBELN-VBELN.
      data: Errorlog type BAPIRETURN1.
    navigate from <CONTEXT> to <ADOBE> via lead selection
      Node_Adobe = wd_Context->get_Child_Node( Name = IF_MAIN=>wdctx_Adobe ).
    navigate from <ADOBE> to <Zsaleheader> via lead selection
      Node_Zsaleheader = Node_Adobe->get_Child_Node( Name = IF_MAIN=>wdctx_Zsaleheader ).
      Node_Zsaleitem = Node_Adobe->get_Child_Node( Name = IF_MAIN=>wdctx_Zsaleitem ).
    get element via lead selection
      Elem_Zsaleheader = Node_Zsaleheader->get_Element(  ).
      Elem_Zsaleitem = Node_Zsaleitem->get_Element(  ).
    get all declared attributes
      Elem_Zsaleheader->get_Static_Attributes(
        importing
          Static_Attributes = Stru_Zsaleheader ).
      header_data-DOC_TYPE = Stru_Zsaleheader-DOC_TYPE.
      header_data-SALES_ORG = Stru_Zsaleheader-SALES_ORG.
      header_data-DISTR_CHAN   = Stru_Zsaleheader-DISTR_CHAN.
      header_data-DIVISION = Stru_Zsaleheader-DIVISION.
      header_data-PURCH_NO = Stru_Zsaleheader-PURCH_NO.
      partner_wa-PARTN_ROLE   = Stru_Zsaleheader-PARTN_ROLE.
      partner_wa-PARTN_NUMB = Stru_Zsaleheader-PARTN_NUMB.
       append partner_wa to partner_data.
        Elem_Zsaleitem->get_Static_Attributes(
        importing
          Static_Attributes = Stru_Zsaleitem ).
      item_wa-ITM_NUMBER = Stru_Zsaleitem-ITM_NUMBER.
      item_wa-MATERIAL   = Stru_Zsaleitem-MATERIAL.
      item_wa-PLANT = Stru_Zsaleitem-PLANT.
      item_wa-REQ_QTY = Stru_Zsaleitem-REQ_QTY.
      item_wa-COND_TYPE   = Stru_Zsaleitem-COND_TYPE.
      item_wa-COND_VALUE = Stru_Zsaleitem-COND_VALUE.
      append item_wa to item_data.
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
      EXPORTING
        ORDER_HEADER_IN           = header_data
      WITHOUT_COMMIT            = ' '
      CONVERT_PARVW_AUART       = ' '
    IMPORTING
       SALESDOCUMENT             = sales_order
      SOLD_TO_PARTY             =
      SHIP_TO_PARTY             =
      BILLING_PARTY             =
       RETURN                    = errorlog
      TABLES
        ORDER_ITEMS_IN            = item_data
        ORDER_PARTNERS            = partner_data
      ORDER_ITEMS_OUT           =
      ORDER_CFGS_REF            =
      ORDER_CFGS_INST           =
      ORDER_CFGS_PART_OF        =
      ORDER_CFGS_VALUE          =
      ORDER_CCARD               =
      ORDER_CFGS_BLOB           =
      ORDER_SCHEDULE_EX         =
    endmethod.
    PLEASE SUGGEST ME IF ANY CODE CHANGE IS REQUIRED
    Thanks in advance
    Ajay

    Hi,
    The item data is not read because, the dynamically added rows should also reflect back to the Web Dynpro context. When the user clicks on Add Row, use the Onsubmit event to add a empty line to internal table and then bind it to the context. And if the user removes a row, remove a row from internal table and bind it back to the context.
    You may refer this article.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/802f0ed1-a17a-2c10-7db4-d515a5b047ed
    Regards,
    Runal

  • Problem in dynamically handling the number of line Items in Main Window

    Hi Gurus,
    I want to know is there any way by which we can handle the Line items that is being Printed in the Main Window.i.e can we split a Line item to the next/subsequent page if it is not fitting in the First/subsequent page.
    Please throw some light .
    Regards,
    Asish Dash

    Hi Haritha,
    No,  suppose there are 10 line items.suppose the 10th value is not fitting in the first page and some part gets printed in the first page and the rest is splitted to the second page.What I want is the whole 10th line item value should come in the second page i.e if the line item value doesnot fit in the First page then the whole value should get printed in the second page.
    Regards .
    Asish Dash

  • Header data in xml tags and line items in fixed length but both in same fil

    Hi,
    In my scenario target side in header level i am passing all the values are fixed values and line item vaues are getting from the source data.how to write udf for this scenario.It should be graphical mapping.
    Please help to me
    please reply fast
    Thanks&Regards
    Swathi
    Edited by: SWATHIP on Feb 4, 2011 7:16 AM

    Hi,
    1) If your values are numerical you can use the "FormatNum" function under Arithmetic Functions.
    This will help you fix the length of the number and even the decimal part.
    2) If you want to fix the length of field which is of type string, you can try the following code:
    public String setLength(String var1, String var2,  Container container) throws StreamTransformationException
         /*   var1 will have the String Value, in var2 pass a constant integer of fixed length you want  */
         int len = Integer.parseInt(var2);
         String rslt = var1;
         if( var1.length() < len)
             for(int i = var1.length(); i < len; i++)
                 rslt = rslt + " "; // appending space
         else
               rslt = rslt.substring(0,var1.length - 1)l
         return rslt;
    regards,
    Aravind
    Edited by: ajnayak on Feb 7, 2011 7:25 AM

  • Line item number and ledger item number posted differently

    Hi Friends ,
      I have a BAPI for posting the documents in SAP from another system.This BAPI is using the standard BAPI -  'BAPI_ACC_DOCUMENT_POST' to post the documents.But when I post the document using this BAPI the line item number and ledger item number in the document are posted differently. ie . for line item no 1 ledger item is 24 .But when I am posting it directly it is same ie for line item no 1 ledger item no is also 1.Lot of other programs in our R/3 system is dependent in this logic.What could be the parameters in BAPI that could affect line item and ledager item ? Can anybody help me in finding out the reason for this ?
    Thanks in advance ,
    Joby

    Hi ,
    Anybody can help me on this issue ?
    Thanks in advance ,
    Joby

  • Gr Ir Assignment Updation with PO and Line Item

    In the GL for GR IR Account the sort key was not  maintained with PO number due to which the assigment field in the line item was getting updated with the posting date and not with the PO & LIne Item details.
    We have made the requiste changes and new items are getting updated properly.
    But require assitance in updating the earlier line items.
    As of date total line items are more than  0.15 mn.
    Please suggest some method to automatically update the assigment field of the GR IR Line items with the PO Details.
    Regards
    Mukesh

    Hi,
    You can use a substitution to update the field through FI. Use GGB4 for wirting a substitution you may need some ABAP coding to substitute PO no and line items in the assignment field.  rule would be Co code =XXX and GL account =xxx and Posting date earlier than =xxxx  then concatenrate EBELN and EBELP in Assigment field Zounr.
    Then execute FBL3N and edit the assignment field by selecting all the documents and then save it you should see the PO line items populated. You can leave the substitution on or you can remove it after updating,
    Regards
    K.R

  • Header and Line Item reporting (MultiProvider)

    Hello All,
    We have data coming in from a LO Extractor.  There are 2 extractors.  1 for line item the other for Header.  The line item extractor has all the fields for both so we decided to use this extractor (the line item).
    Question is, when extracting this data multiple records come over.  Let's say the order has 2 line items.  It brings over a header record and then 2 line item records.  We have it going to an ODS and then Cube.  The ODS key is order number and item.  Well the header record comes over with item number #, so 3 records hit the ODS.
    How do you handle this?  We saw something about denormalization and make this header record item number a 0.
    Can someone explain to us how to handle this?  We also read about a Constant selection and loading the header record and line item as we are to both the InfoCube, but we just don't understand this solution.
    Please help, Thank you

    Item level will have all fields those are in Header level.Header level data will be a subset of Item level data.Load only Item level and when you require header data remove Item number in that relevant DSO and you can see all the data summarized to header level in overwrite mode.
    This will not be good option if you require some fields that may have different records in the header and the item.
    One better option is create a secondary staging DSO that updated by header, item and schedule line level and you can choose your own data fields and key fields. You can update them in overwrite mode to have summarized records that avoids duplication of records from header and item for same document.
    Constant selection wil be helpful in the report level not during load process.
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e7/5f983c1a356858e10000000a114084/frameset.htm
    This will ensure total displayed is constant even after navigation. So it hides repetitive records displaying after drilldown.

  • FI Line Item Data

    Hi,
            I have report against FIAR line items data(0FIAR_O03).The purpose is to report at Customer level for aged trail balance amounts(only for charge back amounts).I have the report ready and restricted document type only with CB- charge back.But the problem is,on the R/3 side for some CB accounts,there is a reference amounts like Credit memos or Customer Payments(document type DZ and DG).How can get these refrences into my report when i restrict the report only with CB.So under charge back ammount,the user should be able to see the associated Credit memos and Customer Payments as in R/3.Thanks for the help.
    Ravi.

    Hi Revathi,
    Kindly find the answers below :
    1.How the table BWOM2_TIMEST will work for delta & what is the selection will happen at BKPF-CPUDT
    Basically, BWOM2_TIMEST will show you the Last Time stamp for both Init and Delta..
    Whenever you will do an Init load.....automatically an entry will take place in this table.....and you will see a "X" sign in the field "LAst TS"....
    Also for Delta...there may be N number of entries with Update mode D....but only for the latest delta you will see a "X" sign in the field "LAst TS"....
    With Financial Accounting line items that have been posted in the SAP R/3 system since the last data request, the extractors identify the following delta dataset using the time stamp in the document header (BKPF-CPUDT).
    2.How the tbale will wok BWOM_SETTINGS for delta
    With these settings your delta extraction uses CPU date of recording records in table in R/3 to define your security interval with at least 1 day
    This means that your data is loaded until the actual day - 1.
    You can check the SAP note : 485958
    Regards,
    Debjani..

  • Line Item Data?

    Hi experts,
                   What is Line Item Data? Can somebody give me an example to understand better the use of Line item data from the reporting prospective?
    thanks in advance
    regards,
    dubbu

    Hi
    I think ur question releted to LINE ITEM DIMENSION
    Line Item and High Cardinality
    Use
    When compared to a fact table, dimensions ideally have a small cardinality.  However, there is an exception to this rule. For example, there are InfoCubes in which a characteristic document is used, in which case almost every entry in the fact table is assigned to a different document. This means that the dimension (or the associated dimension table) has almost as many entries as the fact table itself. We refer here to a degenerated dimension. In BW 2.0, this was also known as a line item dimension, in which case the characteristic responsible for the high cardinality was seen as a line item. Generally, relational and multi-dimensional database systems have problems to efficiently process such dimensions. You can use the indicators line item and high cardinality to execute the following optimizations:
           1.      Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
    ¡        When loading transaction data, no IDs are generated for the entries in the dimension table.  This number range operation can compromise performance precisely in the case where a degenerated dimension is involved. 
    ¡        A table- having a very large cardinality- is removed from the star schema.  As a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
    Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
           2.      High cardinality: This means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
    Note: In SAP BW 3.0, the term line item dimension from SAP BW 2.0 must a) have precisely one characteristic and b) this characteristic must have a high cardinality. Before, the term line item dimension was often only associated with a). Hence the inclusion of this property in the above.  Be aware that a line item dimension has a different meaning now than in SAP BW2.0.

Maybe you are looking for