GRN date ageing

Hi all
Is it possible to get GRN date in MC.1.. there is date field but that gives date of spool.. the date of GRN is required to find ageing of stock.
Rgds
Srini

Hi,
we can findout last GRN in MC.9 & S032 Table
regards,
sasi
Edited by: sasi kumar on Aug 29, 2008 9:23 AM
Edited by: sasi kumar on Aug 29, 2008 9:24 AM

Similar Messages

  • Vendor wise last purchase/grn date

    Hi Experts,
    Please quote if any statndar report is available to vendor wise last purchase/grn date for a partcular pur org or plant.
    Regards

    Hi,
    Not standard report which your req.
    You have to create Qurey report.
    Regds
    Sami

  • GRN Date (Migo Date) as Default date in MIRO

    Dear All,
    The client requirement is like this,
    The default Base Line date for MIRO Document should be the GRN Date (MIGO Date). But in Payment Term configuration only Document Date, Posting Date, No default, Entry Date are there. We can change the base line date at the time of MIRO.
    But Client requirement is it should come by default at the time of doing MIRO,
    Is there any user exit or enhancement for this.
    Sree

    Hi
    Base Line Date
    Vijay

  • GRN date as deafult Base Line Date in MIRO

    Dear All,
    The client requirement is like this,
    The default Base Line date for MIRO Document should be the GRN Date (MIGO Date). But in Payment Term configuration only Document Date, Posting Date, No default, Entry Date are there. We can change the base line date at the time of MIRO.
    But Client requirement is it should come by default at the time of doing MIRO,
    Is there any user exit or enhancement for this.
    Sree

    Hi,
    We have come across this requirement in some implementations and the workaround is done this way:
    During Inovice Verification leave the system to determine Base Line Date based on standard settings.
    You can anyhow change the baseline date in document change mode.
    Have a Development which can identify the docuements posted during a period say every day and get the base line date changed on your logic (you would able to get the full trace with GR).
    Have this program executed every day on background.
    Your logic should also take care of invoice verifications with multiple GRs made at different time for the same invoice (usually the last GR date is taken in this circumstance).
    Hope this helps you.
    Varadharajan

  • How to GRN date (MIGO) and Goods posting date (MB1C) as a Characteristcs

    Dear All,
    Our customer wants to include GRN date (MIGO) and Goods posting date (MB1C) as a Characteristic for a batch.
    And he wants the system to pick up these dates automatically for batch.
    So in batches will be sorted out based on GRN (MIGO) or Goods posting (MB1C) date.
    Is there any standard characteristics available for these fields?
    How to achieve this functionality.
    Regards,
    Mullairaja
    Edited by: MullaiRaja on Jan 7, 2011 8:28 AM

    Closed

  • Capitalization date from GRN date

    Dear All,
    i need a requirement to be configured in the system.
    when we are doing a GRN in MIGO  TC for a particular PO with asset ID 100200, the GRN date should pick up as the capitalization date in the Asset master of 100200.
    How to configure this.
    Please kindly advice me
    Regards
    Man

    Hi
    With the help of your MM Consultant you can do this. Change the field status of Account Assignment Category A in Transaction Code OME9. Remove the Check Box for GR as non valuated. However, note that the asset values would also be updated from the date of GRN. Test the same in Sandbox
    Regards
    Sanil Bhandari

  • Archiving financial document using Data aging

    Hi,
    reading documentation about Data archiving, ILM and SAP Hana I came across archiving of finacial accounting documents in SMART FI 1.0.
    It is stated, that the archiving with the archiving object FI_DOCUMENT is replaced by Data Aging for Financial Documents.
    There are also Data Aging Objects for IDOCs and Application logs, but still the corresponding archiving objects are described.
    Can somebody explain to me, how data aging for FI accounting documents without archiving object FI_DOCUMNT fits to the idea of ILM?
    Kind regards
    Hajo

    Hello Gunasekar,
    please check with  TC:SU53 or set up a authorization trace I assume this is  missing authorization issue on read access of archived documents.
    If you have an older SAP Version please also check the settings in FB00 regarding Read Access Archive or Database.
    If you have I guess 4.7 > please also select in the header of your transaction the button "Data Source" and check whether you can see the archive file and selct this file.
    Regards,
    Sebastian

  • Data Aging design

    Hi
    This may be one for the gurus, or they're could be a standard way to do it.
    I'm looking for some help in designing a database. The problem I have is related to data aging on Oracle instances. I can't find any help on it.
    The problem I have is that I've got 3 categories of data, which is new/warm/old. Essentially, new is data which is 1 hour old. Warm is data which is kept for 24 hours, old is kept for 6-8 weeks.
    So the data needs to age. I think obviously the mechanics of it involves partitioning, and using a rolling or sliding window mechanism to move the partitions, but don't know.
    Any help is appreciated.
    Thanks for your help.
    Bob

    scope_creep wrote:
    The problem I have is that I've got 3 categories of data, which is new/warm/old. Essentially, new is data which is 1 hour old. Warm is data which is kept for 24 hours, old is kept for 6-8 weeks.
    So the data needs to age. I think obviously the mechanics of it involves partitioning, and using a rolling or sliding window mechanism to move the partitions, but don't know. Partitioning without a doubt.
    Any other method will require you to
    a) read the old data from the current table
    b) write the old data to the old table
    c) delete the old data from the current table
    d) commit
    This is horrible expensive as you simply moving and pushing data from one part of the database to another. Lots and lots of I/O. And I/O is the most expensive operation you can do on the database.
    Using partitioning.
    a) create a staging table (this can be done once up front or dynamically at the time for multi-threading/thread safety)
    b) issue an alter table exchange partition (current table) and place the partition with the old data into the staging table
    c) issue an alter table exchange partition (old table) and place the staging table contents into the old partition table
    d) optionally drop and purge staging table if dynamically created
    How much I/O? Negligible as this only entails a data dictionary update. The actual row contents are not moved. It simply changes ownership (sub-second usually). Which means that performance is consistent and not subject to the size of the data to "move".
    I would also include indexes with the partition exchange and skip validation as new data is not placed into a partition - the existing data has already been validated for that specific partition.
    Partitioning is an extra licensing option for Enterprise Edition. IMO, it does not make sense to use EE and not have partitioning. It is one the highest impact features there is - it reduces I/O, significantly increases performance, and makes data management exponentially easier.

  • Exit/BADi for ml81n to check GRN date should be PO Date.

    Exit/BADi for ml81n to check GRN date should be > PO Date.Kindly suggest .

    Hi,
    You can achieve it using the below enhancement.
    Enhancement: SRVEDIT
    Function module: EXIT_SAPLMLSR_001
    Regards,

  • GRN Date or MB1C date should be considered for batch

    Dear All,
    Our customer wants to include GRN date (MIGO) and Goods posting date (MB1C) as a Characteristic for a batch.
    And he wants the system to pick up these dates automatically for batch.
    So in batches will be sorted out based on GRN (MIGO) or Goods posting (MB1C) date.
    How to achieve this functionality.
    Regards,
    Mullairaja
    Edited by: MullaiRaja on Jan 6, 2011 9:42 AM

    Close this thread & Post it in [ERP - Logistics Materials Management (MM) |SAP ERP - Logistics Materials Management (SAP MM); forum to get responses.

  • Blocking Invoice verfication if it is before the GRN date

    Hi,
    I need to create a block where the system does not allow to do invoice verification (MIRO) if it is before the GRN (MIGO) date.... is this possible?
    Example.
    GRN date is 07th March 2007, the system allows to do invoice verfication even on the 06th March. I need to block this.... Pls help...
    Thanks,
    Maleeq

    Please change  in the P.O as GR-IR verification.
    It means the Invoice cannot be verified unless GRN is done so after GRN only you can do the Invoice verifcation.
    This will solve the problem instead of blocking the invoice
    G.Ganesh Kumar

  • Backposting allowed before GRN date..

    Dear All,
    At my client side i am able to post consumption before GRN date (Within a same period)
    For Example- If i am doing GRN on 20th February and while MB1A i am putting date 10th February (which is before GRN date and even batch is also not created on that date) system is allowing me to back post consumption for that batch.
    What is the reason behind?
    Naren

    Hi Naren,
    All user exits and BAdIs available in the MM-IM area are documented in the IMG path:
    Materials Management -> Inventory Management and Physical Inventory -> Maintain Customer Exits and Business Add-Ins.
    I have been checking them and there is not any exit specifically designed for this.
    There are user exits or BAdIs that implement additional checks when posting a goods movement (like MB_CHECK_LINE_BADI), but, in this case, what check could we implement?
    This is only my opinion, but, as far as I understand, we would need the system to check if, when you post a goods issue, there is enough stock according to the date within the period. The BAdI would need to take the material, plant and storage location from the posting and run an analysis similar to the one that MB5B makes and determine, within the period, if you have stock for the date. If not, send an error message.
    I think this would cause performance problems.
    This is the only idea I can think about... sorry that I do not have better news....
    Esther.

  • GRN Date as Baseline Date

    Hi ,
    Want system should capture GRN Posting Date as Base Line date while doing the MIRO.
    ( If payment term is 30 Days , then system shoulld calculate the 30 Days from GRN posting date )
    Any Badi  will serve this purpose ( INVOICE_UPDATE )
    Thanks in advance.

    Hi,
    The BADI : MRM_PAYMENT_TERMS to you used to copy the GRN Posting Date as Base Line date while doing the MIRO
    Go to T code : SE24 enter the object type  CL_EX_MRM_PAYMENT_TERMS click display.
    Copy the code and add the same code in your object for the BADI MRM_PAYMENT_TERMS I will work without any issue.
    Thanks.

  • GRN - Dates

    While making GRN, currently, only posting date is picked up and stored
    by SAP. Along with the same, we need to feed following 2 dates whiel
    making GRN. Pl provide the solution.
    1. Challan/Dnote Date
    2. Physical Material Received date
    Point 2 date is required as sometimes material may be received on 1st of
    x month but may be posted into SAP by 10th of X month. So we can analyse
    the difference.

    Hi Mahesh
    1) The document date in MIGO is your challan/ D.Note date which is stored in
        Table -GOHEAD & Field - BLDAT
    2) If you want to differentiate betn. Actual Matl. Recd. Date & Posting date in SAP
       For this purpose you can inward the material by Mvt. 103 & then for actual posting to inventory you can use Mvt. type 105.  The diff in posting date can be eaisly tracked.(For this you donot use Mvt. 101 directly.)
    Reward if useful
    AK

  • GRN date

    Hello friends,
                        I am working on an alv where i have to display the date on which GRN was created,can any1 tell in which table to look for this date,
                        I have been to the transaction MIGO,there im gettin the field name as BLDAT,I have production number(AUFNR) and matnr as input.
                        Please suggest me the solution

    Hi
    Pass the fields AUFNR and MATNR to MSEG table and Take the MBLNR and pass this MBLNR to MKPF table and take the Date field BLDAT from MKPF
    Reward points for useful Answers
    Regards
    Anji

Maybe you are looking for