PO line item deletion and its effects

Dear all,
When I delete the line item of po after MIGO and MIRO, it is allowing to do so.
but after migo/miro it should not allow.
what rectification can be done?
also can u tell me because of this deletion any background entry happens or any stock changes happens?
Thanks,
Narendra

Dear Frnd..
plz try and change the status of message no 06 - 115 to "E - Error"... in SPRO ->> PURCHASING ->> ENVIORNMENT ->>Define Attributes of System Messages. - >> sYSTEM mESSAGES...
hpe this will help..
plz confirm
Amit P Hiran
njoy SAP..
njjoy Lyf...

Similar Messages

  • PO Line item deletion and change documents

    Hello All
    We have cases where when we delete certain lines of a Purchase order, a change document gets created while for certain other lines it doesn't. Has anyone expereienced this issue before ? Any solutions on how to resolve it please ?

    Yes we find such problems in purchase orders such as
    - deleting PO line item
    - Add PO line item
    - change qty
    We had restricted through ABAP program plus release indicator.
    Check..,,,
    Vijay

  • Line item extract and delete query

    If you change the default view for a scenario and line-item detail has been entered,
    you should first extract the line-item detail and save it. Then delete the line-item
    detail from the scenario before changing the view. You must change the extracted
    line-item detail to match the new default view before loading it.
    The above is a reference from HFM-Admin guide.
    Could any one tell how to extract or delete line item??
    Thanx in Advance

    Dear Sree,
    Here my query is addition and deletion of line items in delivery suggestionable or not if not any alternate solution please............
    -->You can delete the line item in the delivery if PGI not done for that delivery,
    -->But system will not allow you the new item in the delivery,because as per the standard functionality system will copy the items from the sales order and this is advaisable also.
    -->So if you want to add new item add in the sales order then create delivery for that order.
    -->Still you want to add item at delivery ( for your business requirement) you need to do the item categroy determination for the deliveries through 0184 transaction.
    -->Redetermine the pricing at billing level for that item by maintaining proper copy control settings between delivery and billing at item level in VTFL transaction.
    Maintain pricing type field as B-Carry out new pricing
    Make sure that you done the pricing procedure detrmination with the combination of billing document pricing procedure in OVKK transaction.
    I hope this will help you,
    Regards,
    Murali.

  • Infocube line item dimension and performance optimization

    Hi,
    I remodelled an infocube and line item dimension contains only one characteristics set as line item dimension.
    previously the dimension as one characteristics but it wasn't set as line item dimension.
    and when I checked the SAP_INFOCUBE_DESIGNS from SE38  it looks ok.
    /SAP/CUBE   /SAP/CUBE3   rows:        8663  ratio:          3  %
    After setting it as line item the rows is now minus but it is showing red which means that there is problem with the dimension
    /SAP/CUBE   /SAP/CUBE3   rows:          1-   ratio:          0  %
    Its this a performance problem since it is showing red.
    thanks

    hi,
    No,its not performance issue.
    for a dimension to be line item dimension...the dimension size shouldn't be more than 20% size of the fact table size.
    when a dimension is set as line item dimension,the regarding SID will be placed in Fact Table,but not the DIM ID.
    may be that is the reason when your dimension is not line item dimension,it shows the number of rows and when it is made line item dimension,its not showing any rows and the ratio also null.
    hope this is clear for you.
    Regards
    Ramsunder

  • Sales order line item delete error for MTO sales order

    Dear Experts
    iam facing below error for MTO sales order line item deletion
    "For reasons of cost management, item 000040 cannot
    be deleted"
    Please help
    Regards,
    KEdar

    It looks you try to delete the sales order line item and you get this error message.
    Try to put reason for rejection for the line item and save the order. This is equal to deleting the line item.
    You can also refer the OSS note 14097 - Order item cannot be deleted/overwritten for further information.
    Regards,

  • Customer/Vendor A/C with line item details and with opening and closing Bal

    Dear Sir / Madam,
    Is it possible to have a customer and / or vendor Sub-Ledger account-
    with line item details and with opening and closing balance detail
    for a particular period.?
    Regards
    Chirag Shah
    I thank for the given below thread which has solved the same problem for G/L Account
    Re: Report to get the ledger printout with opening balances

    Hello Srinujalleda,
    Thanks for your precious time.
    I tried the referred T-Code
    But this report is not showing Opening balance, closing balance detail.
    It only gives transactions during the specified posting period and total of it.
    Please guide me further in case if I need to give proper input at selection screen or elsewhere.
    Client Requires Report in a fashion
    Opening Balance as on Date
    + / -  Transactions during the period
    = Closing Balance as on date
    As that of appearing for G/L Account by S_ALR_87012311
    Thanks once again & Regards
    Chirag Shah

  • What is line item dimension and cardinality in BI 7.0

    Can u plz suggest me what is line item dimension and cardinality in BI 7.0..
    Thanks in advance.
    Venkat

    Hi Babu
    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.
    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.
    SAP recommends that you use ODS objects, where possible, instead of InfoCubes for line items.
    Hope this helps.
    Plz check these links:
    SAP Help:
    http://help.sap.com/saphelp_nw04s/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
    Thanks & Regards
    Reward if helped
    Edited by: Noor Ahmed khan on Aug 5, 2008 2:36 PM

  • Is it possible multiple line items debit & single line item credit and different cost centers and different profit centers in fbcj

    Hi all ,
    I have a requirement to Post Cash Journal Document using FBCJ tcode.
    Is it possible multiple line items debit & single line item credit and different cost centers and different profit centers
    for exp:
    pk   GL a/c   description       amount   cost center  profit center
    40  400101  telephone exp   500        1403            P 1000
    40  400101  telephone exp    100       1404            P 2000
    50  200100  cash in hand      600-                             
       This is My requirement  is it possible in fbcj
        Please suggest me.ASAP.
    Regards
       Naresh.

    Hi,
      This you can do it in two ways:
    1. Make three header under top level....one Product A, 2nd Product B ( as Billing element) and third as Common expense ( only cost). Now 1st & 2 nd WBS, you have to have sales order linking with individual lint item, for third you will accumulate all the common expense till the period end then make a reposting of the same in desired proportion to both products WBS hierarchy
    (This is if you want to have a track on the common expense as well.......like planning, budgeting & control)
    After this reposting, run RA for individual billing element and hence you will all the complement detailing and control over Revenue and expense with respect to Product A and Product B individually.
    2. If you don't want to maintain that kind of detailing the common expense and keep track of it through project, then have cost centers accordingly and make an assesment/ distribution with respect to expenses accumulated at those cost centers for the period to the respective WBS under each product. Then execute the period end processes for the project.
    Or
    You can try with have two more line items in the costing sheet as an overhead against common expenses with respect each product.
    I hope this should help you.
    Regards
    Avisek Bhardwaj

  • T.code required for Vendor line item display and Customer line item display

    Hi Gurus,
    Pl provide me transaction code for "Vendor line item display and " Customer line item display apart from FBL1n for vendor and FBL5n for customers.
    Kindly advise.
    Regards,
    Samar

    Hi,
    You could use these, for example:
    S_ALR_87012103 - List of Vendor Line Items
    S_ALR_87012197 - List of Customer Line Items
    Just curious: what's wrong with FBL1(5)N?
    Regards,
    Eli

  • 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

  • Text element with line item content and include text

    Hi All,
    How to write in smartform in single text element with line item content and include text.I am using this text element in table . Pls help me out. i am writing the include command in text element ,but this command is not enough for single line of text editor.
    thanks ,
    Rakesh singh

    I have been pulling my hair out for a few days trying to find
    this solution. This fixed my problems as well.
    I was getting ready to scrap the Report Builder altogether
    and move to SQL Server Reporting Services over this issue.
    I'm running 7.0.2 also, that version alone fixed many small
    issues like creating borders and such.
    Thanks

  • Diffence in line item display and Balance display

    Hi Gurus,
    Please let me know why there is difference in line item display and balance display in one of GL account in previous year for 1 posting period.what can be cause for this, If I go at FS10n and check the balance for specific period it shows different balance and if I double click on same period and I can see the different Balance for same GL.
    Thanks
    Edited by: Manu Rathore on Feb 8, 2012 3:06 AM
    Edited by: Manu Rathore on Feb 8, 2012 3:15 AM

    Hi,
    this is FS10N - Balance display-GL X
    Period                    Dr                  Cr                 Balance
    12/2011                  33,229.00       49,395.00     16,166.00-Cr
      Type     Doc. Date  Amount in local cur. DocumentNo
      KG       31.12.2011              400.00  65762562
      KG       31.12.2011              200.00  65762563
      KA       28.12.2011              900.00  68250089
      KA       28.12.2011            1,000.00  68250090
    Line item Display Account             X 
    company Code            0000
      Type     Doc. Date  Amount in local cur. DocumentNo
      KZ       22.12.2011              500.00  69461532
      KA       22.12.2011              200.00  68250072
      KZ       22.12.2011              200.00  69461534
      RE       28.12.2011            4,445.00  60000201
      RE       28.12.2011            1,445.00  60000202
      KA       28.12.2011              250.00  68250084
      KA       28.12.2011            1,500.00  68250085
      KA       15.12.2011            2,000.00  68250077
      KZ       29.12.2011            6,555.00  69461633
      KZ       29.12.2011            7,868.00  69461633
      RG       30.12.2011            5,566.00  64000464
    Account x           33,029.00     
    See the difference in Dr side at FS10N it= 33229
    and line item total =33029
    Difference of 200.
    Same there is difference in credit side.
    Hope you understand it.
    Thanks

  • Line item dimensions and cardinality?

    hi all,
    how to identify nor use the cardinality relationship as well as the line item dimension?
    can anyone explain me about it. since i am trying to create an multi provider which enables to fetch data from 3 ods.
    regds
    Hari Chintu

    Hi,
    Below is some useful information on Line item dimension and high cardinality.
    These concepts hold good for Cube design only, coming to ODS, these dont help you. As ODS is nothin but a flat structure, we do not have the facility of Star schema. Reporting on ODS can lead to performance issues, it is better to load data from ODS into Cube and then have a multiprovider on them instead of having it on ODS.
    Hope this helps.
    Regards,
    Kalyan
    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.
    However, we recommend that you use ODS objects, where possible, instead of InfoCubes for line items. See Creating ODS Objects.
    Activities
    When creating dimensions in the InfoCube maintenance, flag the relevant dimension as a Line Item/ having High Cardinality.

  • Line Item Dimension and Navigational attribute

    Hi Gurus,
    Can somebody tell me how line item Dimensions and navigational attributes works technically?
    What are the pros and cons for them?
    Regards
    Alex

    Hi Alex,
                You will use navigational attributes based on how you want to track and report history. Let me explain with an example.
    Customer Bubba is assigned Sales Group XYZ in Jan 2007. In July the Sales Group on the Customer Master record is changed to  ABC. Your are looking at the sales report.
    1). If you want to see all the sales made to Customer Bubba at the time of reporting (current) then you will use navigational attributes You will create 0SALESGRP as the navigational attribute of 0CUSTOMER .  Then all sales to the customer will show up under Sales Group ABC.
    2). If you want to see  all the sales made to the customer at the time the actual transaction occured then you will add Sales Group as a characteristic of the InfoCube. Then sales from Jan - June 2007 will show under Sales Group XYZ and from July - Present will show under Sales Group ABC.
    Performance issue occurs because navigational attribute is stored outside of the dimension table of the cube and is stored in separate master data tables. So query has to perform additional table read. So essentially there are advantages and disadvantages of usng navigational attributes. It is business requirement that will drive the use of navigational attribute.
    Hope this helps!!!. Please assign points.

  • ECC6 - Line item display and Open item management Questions.

    Hi All,
    For SAP ECC6, although I do not maintain line item display and open item management for Recon GL (for Debtor), I still can use FAGLB03 to view the GL balances and even Drill down to line item level by double click the value from FAGLB03 until line item level.
    Questions:
    Could anyone confirm whether my assumption below, true?
    1) If Line item display (Tcode: FS00) is ON, then the data will be stored at table: BSIS
    2) If NO open item management, then there should be no data to be stored at table BSAS for thaty particular GL account
    3) BSAS will only have data, after clearing was carried out ... move from BSIS to BSAS.
    In ECC 6
    4) FAGLB03 can drill down to line item level, although the GL (Tcode: FS00) was NOT set open item management and line item display is because from FAGLB03 when drill down to line item level, it actually extract data from BSEG, right?
    Additionally, we can use FBL3N to check the line item data for NON line item display GL as well.
    In SAP R/3 4.7, if not mistaken, if the GL is NOT line item display and open item management, we cannot drill down the line item reading and CANNOT use FBL3N to check the line item data.
    Kindly advise on these.
    Thanks.
    sbmel

    1) If Line item display (Tcode: FS00) is ON, then the data will be stored at table: BSIS
    BSIS is an open items table. You can see all GL open items there. GL's which are not open item managed can't go here
    2) If NO open item management, then there should be no data to be stored at table BSAS for thaty particular GL account
    Yes. Your understanding is correct
    3) BSAS will only have data, after clearing was carried out ... move from BSIS to BSAS.
    Yes. In case of partial clearing data will be there in both the tables BSIS & BSAS
    4) FAGLB03 can drill down to line item level, although the GL (Tcode: FS00) was NOT set open item management and line item display is because from FAGLB03 when drill down to line item level, it actually extract data from BSEG, right?
    These are New GL reports and report is based on document split object. if your document split is active at segment level then you can see line item report at segment level using FAGLL03. These reports has no link to FS00 settings.
    Hope this helps

Maybe you are looking for

  • Looking for an author to write a book on Flash CS5

    I'm searching for a qualified individual(s) who might be interested in writing an intermediate-advanced level book for the retail market. Please contact me directly for more information at [email protected]  Thanks so much!

  • HOW to retrive data from SAP Tabel

    Hi Friends,    1)Can you please explain how to retrive data from SAP table(example AFRU).    2) we had requriment based on the qunatity , Product name and date we need to display KPI's .KPI is based no products manfactured per day with some condition

  • Stichwörter in Bridge in Elements 6 / MAC

    Wer weiss, wie ich Stichwörter in Bridge/MAC zuordne? Bis Version 5 (Windows) ging dies durch Drag&Drop, was hier nicht zu funktionieren scheint. Danke im Voraus!

  • Mac OS X 10.5: How can I change my computer's name?

    This may seem trivial, however it's driving me crazy. When I set up my Macbook Pro, I neglected to change the name from the default. Now the computer is identified by a name that I would like to change to reflect the primary user (me). Ho do I do thi

  • Book never downloaded

    my book appeared in downloads, but only got about 1/4 downloaded and i had to shut down.  when i turn i-tunes store back on the download was not there to finish the download.  this was a $29.00 book and i really want to get it.  what should i do.  th