Posting in backdate

hi all guru`s
Here Im looking for posting stock in backdate by mb1c.
currently two periods are open april 04 and may 05...I want to post stock on date 31.03.2009
I tried ob52 and mmpv ,mmrv but my issue is not getting solved...plz help...
thanks in advance

How to open closed MM Periods:
T-Code: MMPI - from Tool Bar select - System - User Profile - Own Data - In parameter Tab Enter "MMPI_READ_NOTE" in parameter Field
Then, Remove assignment of Plants from Company Code (In SPRO).
Now use T-Code OMSY & Set the required Period.
Re-assign Plants to Company Code & Check whether correct period is open thru T-Code - MMRV
Now use T-code - OMWD to Assign Valuation grouping code to Valuation area because the earlier data gets deleted when assignment of Plants was removed.
Use the transaction code OMS2 then select FERT (for Finished Goods) or any required Material type & then click on the quantity and value update.
Select your plant or valuation area and put Tick Marks in Value update and Quantity update
Regards,
Edamanayil.

Similar Messages

  • Edit  dip posting in backdate

    I am new to this community.I am using SAP in my plant.I did Dip posting in a T code
    /nymu127
    and the same can be viewed in
    /nym101
    But the posting was wrong . so i wanted to edit it.People in SAP management dept. in my company say that it cannot be changed.
    Becoz of tis i face problems in tallying stock in my plant.
    Please help!!!!!

    T codes /nymu127, /nym101 are not standard t codes.
    once material document created will not be canged.
    Do reverse posting for the wrong posting. system creates another material document. It is not a problem.
    Then your stock will be updated properly

  • Delivery Creation based on Backdate stock

    Hi
    Could anyone advise the procedure to have the delivery creation based on the back dated stock.
    IN DETAIIL detail The system should be able to allocate stock in sales order shedule line item based on the back date of last week (example) stock avilablity,  though today no system level inventory due to goods movement.
    Appreciated if could advise in detail.
    Regards
    RG

    Provide with an example.
    At present system checks the stock which is posted in backdate,
    To determine confirmed delivery date, Backward scheduling performed first , if not derived the req del date, then system does forward scheduling- which is a std functionality
    Regards,
    Reazuddin MD

  • Different date

    Dear All,
    In B1 2005A SP01 PL 46, we can cancel the incoming payment in this following case:
    1. Incoming payment posting date : 09/11/2008
    2. Posting period in the B1 menu, belows user name : 2008 - 09
    3. B1 client application date : current date or system date, for example if I run B1 today, the date will be Oct 17, 2008
    Solution:
    In above case, the system will ask user to select one of two options if the incoming payment is going to be canceled. The option is cancel by posting date or creation date. Using posting date, the reverse journal posting date of the canceled incoming payment will be as same as the posting date of the incoming payment. The other option is contrary with above.
    Now, when using B1 2005A SP01 Pl48 or PL50, the above case and its solution can not be used. Inversely, I have to set the system date and posting date to be backdated. It means that all users have to be log out before performing this work.
    This situation really drives our company crazy.
    Pls give advice how to solve this issue. Do I have to downgrade ?
    Rajh

    Thx for your answer. If current posting period is 2008 - 10, I open the document and what date will be used by B1 ? is it system date (computer date) or another date ?
    I am not sure if it won't probably influence the cancellation issue.
    If I use current posting period (2008 - 10) on today's date to cancel the incoming payment that have posting date on Sept 19, 2008,  there is no cancellation options and then the reverse journal for the cancellation is today but if I set posting period backdated to the same month in the document, the cancellation option is available but I can select the posting date as a reverse journal entry posting date.
    it really sounds strange and pls give advice.
    Rajh

  • Issue with delta queue initialization

    Hello
    I am having a problem with an initialization of the delta queue for a certain extractor. The initialization was successfull, and I can see the extractor in the delta queue maintenance (RSA7) in ECC, but when users are posting transactions in ECC, they are not coming into RSA7.
    The extractor is 0CO_OM_WBS_6, so its not standard LO cockpit where we have V3 (background) jobs which have to be triggered.
    One more thing, the record which was posted was backdated, ie the date is sometime in the past. But I think the delta queue still picks the records. Can i know how the delta queue funtions based on the time stamp?
    Please advise.

    Here is the OOS note fro FI Datasources.
    OSS 485958:
    Symptom
    The FI line item delta DataSources can identify new and changed data only to the day because the source tables only contain the CPU date and not the time as time characteristic for the change.
    This results in a safety interval of at least one day.
    This can cause problems if the batch processing of the period-end closing is still running on the day following the period-end closing and all data of the closed period is to be extracted into BW on this day.
    Example:
    The fiscal year of the company ends on December 31, 2002.
    On January 01, 2003, all data of the closed fiscal year is to be extracted into BW.In this case, the FI line item delta DataSources only extract the data with a safety interval of at least one day.
    This is the data that was posted with a CPU date up to December 31, 2002.
    However, the batch programs for closing the 2002 fiscal year are still running on January 01, 2003.
    The postings created by these programs with a January 01 date for the 2002 fiscal year can therefore only be extracted with delta extraction on January 02, 2003. However, extraction should already be possible on January 01, 2003.
    Other terms
    FI line item delta DataSources
    0FI_AP_4; 0FI_AR_4; 0FI_GL_4
    Reason and Prerequisites
    This problem is caused by the program design.
    Solution
    The functions are enhanced as of PI 2002.1, standard version.
    Due to a customized setting, it is now possible for the FI line item extractors to read the data up to the current date during the delta runs.
    During the next delta run, the data is then read again from the day when the previous extraction was called, up to the current day of the call for the new extraction.This means that the delta extraction of the data always occurs with time intervals overlapping by one day.
    The delta calculation by the ODS objects ensures that the repeatedly extracted data does not cause duplicate values in the InfoCube.
    Activate the new functions as follows:
    1. PI 2001.1 or PI 2001.2:
    Implement the new functions with the correction instructions in this note.As of PI 2002.1, these changes are already implemented in the standard version.
    1. Start a test run for an FI line item DataSource via transaction RSA3.
    2. Two new parameters are now available in the BWOM_SETTINGS table.
    3. Parameter BWFIOVERLA (Default _)
    Set this parameter to "X" using transaction SE16, to activate the new function of overlapping time intervals.
    Caution
    The new function also uses a safety interval of one day to determine the To value of the selection, if the time limit set by BWFITIMBOR is not reached.This means that only data up to the day before the extraction was called is selected, if the extraction starts before 02:00:00 (default for BWFITIMBOR).
    Correction: Parameter BWFITIMBOR (Format HH:MM:SS, default 020000)
    The default value for this parameter is 02:00:00.Do not change this value.
    If this time limit is not reached, only data up to the previous day (with BWFIOVERLA = 'X') or the day before this day (with BWFIOVERLA = ' ') is selected.
    This logic prevents records with a CPU date of the previous day being contained in the posting when the extraction is executed.
    Check any OSS notes for your data source.

  • ITunes not updating RSS feed.

    I am hoping someone will be able to help me figure this out:
    After a hiatus of several months, I have started releasing new podcast episodes. The last episode in the iTunes store directory was Nov. 14, 2012.
    In the last week I have released 2 new episodes, but since the content was time sensitive I backdated them. I changed the Nov. 14 podcast to July 20 and then added a September 15 and a February 22, 2013 episode.
    The changes show up through iTunes software, but not in the iTunes store. It still shows the last episode as being Nov. 14, 2012. It has been 4 going on 5 days without any changes.
    Also, iTunes is not displaying my podcast logo, even though I have uploaded a 1400 X 1400 jpeg.
    I have checked and the podcast feed validates without a problem.
    I am at a loss as to what to look for or try next. If anyone has any ideas I would be very appreciative for any advice.
    https://itunes.apple.com/jp/podcast/down-to-business-english-business/id36626569 7?l=en&mt=2
    http://www.speakeasytokyo.net/downtobusinessenglish.xml
    http://www.downtobusinessenglish.com
    Thank you.

    Hi Roger,
    I contacted Apple and received this confusing reply (cut and paste below). It is confusing on 2 counts; 1) My feed validates just fine and 2) within minutes of receiving it, iTunes updated my feed to show 2 missing episodes.
    Still, the artwork is not showing and I posted another (backdated) episode over a week ago and it still hasn't shown up in the store yet either.
    I am wondering if I should resubmit my feed as the Apple support email suggests but do not want to loose my current subscribers.
    Any thoughts?
    This is the email I received from Apple:
    Dear Malcolm,
    Welcome to iTunes Store Customer Support. My name is Abdul and I will be happy to assist you.
    I'm sorry to hear that you have been unable to get your podcast listed on the iTunes Store. Addressing your concern is important to me.
    Malcolm, it appears that your podcast's RSS feed is not validating. To help find the problem, you may want to use a feed validator, such as this one:
    http://www.feedvalidator.org
    You can get help with many specific issues, learn how to test a feed, and view a sample feed in the iTunes Making a Podcast page:
    http://www.apple.com/itunes/podcasts/specs.html
    If you can successfully subscribe to your podcast and listen to each of the episodes, try resubmitting the feed to the iTunes Store. If you receive a message that the feed has already been submitted, the iTunes Store is detecting that the podcast is a duplicate. Please follow these steps to resubmit the podcast:
    1) Change the title and link fields of your RSS feed to something other than what they are now.
    2) Resubmit the podcast feed via iTunes.
    3) Once you have successfully submitted the podcast, you can change the title and link fields back to what they were.
    If you're still having trouble, consider consulting the Apple Discussions forums, which have a wealth of information about specific issues. Click Producing Podcasts in the Pro Digital Production area of this page: http://discussions.apple.com
    I hope the above information will help you.
    If you have any further questions, feel free to contact us and we will be happy to assist you.
    Have a nice day!
    Sincerely,
    Abdul
    iTunes Store Customer Support

  • REFX data conversion

    Hi,
    would have good advises for starting to use REFX?
    In our case the company has been using different legacy systems to handle real estate processes.
    When starting to use REFX, what is the best practise to convert REFX contracts?
    E.g lease-in contracts have originally started year 2004, with certain condition types linked to index series. During the years the contract condtions have been updated according to index changes (with some exceptions).
    Should the currect situation e.g. 2011 condition amounts / the original conditions / both be converted into SAP?
    Please give some advises what to consider!
    Thanks for all comments,
    Sonja

    Hi,
    It looks like you have a good reason to start working with RE-FX. This way you will maintain all the RE data in one system instead of different legacy systems.
    The easiest way to do the migration is by using LSMW. In this LSMW you will have to choose for the BAPI methods to be able to upload the data with Idocs. This works fine. We did at the end of 2010 a migration of 85.000 rental objects with fewer business entities, buildings and the same amount of contracts.
    When migrating the contracts you will have to keep all the original information in SAP. So you start the contract in 2004. Then it is also possible to migrate the conditions from the contract start date. For this purpose SAP has two fields to be able to start posting these conditions with go-live. These are the first posting from (first date for posting in SAP) and the cash flow date (from this date SAP builds the cash flow). In this way the first posting date can be 01-01-2012 and the cash flow date 01-01-2010. Now it is possible to post also backdated changes between 2010 and 2012. SAP knows the original posting is made in a legacy system and will only post the difference.
    I hope this answer will help you to decide what is best for you.
    Good luck,
    Jeroen

  • Backdating posting date for incoming payments.

    Hi All,
    IN FICA, can we backdate posting date to give discounts for the customer payments. When I backdate posting date, the system gives me an error that the month end is closed.
    Is there an event or function module for backdate posting.
    Thanks for the help.
    Kumar

    If you have the requirement to backdate the postings, then you will have to open the period for posting. Normally the finance users close and open periods and most often there will be an overlap of a couple days between current period and previous period during which both of them will be open.
    You can use function module BKK_RFC_GL_FI_PERIOD_CHECK to verify if the posting period is open for a given posting date. If the posting period is closed, you can probably create a BPEM case or put it in clarification list for your users and then they can manually open the period, post the document and close the period.
    Do you have a lot of such backdated transactions? Depending on that your users may or may not like this approach. If everything has to be done in your program, then you will have come up with your own logic to open and close the period for the duration of your program execution. Be cautious as this will be a direct table update and mistakes often happen. Also make sure you close the period that you just opened and keep the current period open.

  • Backdate Posting of Goods Issue using standard BADI

    Hi Experts!
    The standard BADI we are using creates an STO then a Delivery and Goods Issue via a userexit. We have a requirement to backdate the posting dates and have a concern of deficit stock levels at the point of Goods Issue. How do we control this?

    Hi,
    Instead of updating entire data of deliveries and PGI once, you can manually update the stock for a specific period and then update the Deliveries and PGI in the system.
    Or update entire stock at once till date and only then update the Deliveries and PGI in the system.
    Hope this helps.
    Regards,
    Sharan

  • Internal order not posted, backdating

    Hello,
    When AUC is created with investment order was given as reference, but unfortunately, system configuration was given to hide the investment order, hence forth, Controlling document debiting the order didn't take place.
    The order hence forth attached with the budget didn't reduce the budget value.
    Is it possible to update the accounting document to post to internal order, without reversing the original document.
    Regards,
    Keith

    Hello
    Are  u using SAP version lower then ECC5 then you can do this by FI-CO reconcilation transaction.
    thanks
    alok

  • MB5B stock on posting date

    Hi experts,
                            For a material XX which was  zero stock on 15/11/2008.Goods receipt(MIGO 101) done on 15/11/2008 of qty 100kg. So stock was 100kg. I have issued material XX of qty 75 kg to cost center and entered posting date 3/11/2008. My system allowing me to issue that material on 3/11/2008 without any warning or error msg. But at that there was no stock. So that if i check the report MB5B stock on posting date my closing stock showing in negative for 3/11/2008. Our requirement is how to stop this back dated posting? System should not allow me if i am posting on back date?
    Thank you
    SAP

    hi Rehan,
    I have checked all settings also enhancement  but there is no as such control to restrict backposting within current period
    I think its self disipline action not to post backdated GI when GR is done on later date
    Vishal...

  • Change posting date during UD Reversal

    Hi All
    During working with a UD reversal program by using SAP note 175842 i came to know that the posting date only comes as the current date.
    If Today i am  reversing  the UD of a batch which is 15 days old (Example-15.02.2014) then the posting date in the material document will be of today.
    But my requirement is that, date should be the actual inspection lot creation date ie. 15.02.2014 . I have already discussed with the technical team , as
    per their understanding no option is there to edit the standard program.
    Please help me in this regard, is there any option to change the posting date.
    Regards
    D Mohanty

    Hi,
    I understand that you are looking to make 322 movement today but need posting date/ document date in past. I tried my reversal program and I could achieve this. While making the UD reversal, change the date which is required.
    In following case, I made the 321 today but in back posting date i.e 15.02.14. For this, refer Document date.
    Then again, while making the reversal, I entered the backdate (20.02.14) and same is appearing for the document. Refer 322 movement.
    Ofcourse you need to allow posting in previous periods using MMRV.
    If you need something else, please come up again.
    ntn

  • SAP posting period error while mainting stock in MB1C

    Hi,
    Error Description:-
    While I am maintain the stock in MB1C i got an error i.e.
    Error:-  Postingonly possible in periods 2006/12 and 2006/11 in company code CLC1 ( CLC1 is mycompany code.)
    To resolve this error  I did some pre-requisite, 
    First :- In OB29, I define my fiscal year variant ( Here,  I copied the K4 andrename S4 and save )
    Second :- then, in OB37, I Assign fiscal year variant to company code.
    Third :- I define variant for open postingperiod, ( Here, I define my ownvariant  to use the following  menu path - IMG-- FAFinancialaccounting global settingsDocuments-- Posting periods--Define variant forposting periods).
    Forth:- in OB52, i define the open and close posting periods ( Here, in new entries i choose my variantwhich i define in 3rd step  and define myperiods).
    still system not allowing me the current dated posting, then i use the following step to resolve the error,
    I mgoing to MMPV for close the periods. (here I  closed all periods, month wisetill 2012/01).
    stilli got the same error,  so  Icheck  MMRV & OMSY, weather postingperiods change or not.. ( Here, systemshows me backdated posting periods i.e. 2006/12).
    Kindly help me to resolve this error.
    reg.Mayur

    Hi,
    As you Said i closed each period as well as fiscal year , but still my problem not resolved .. system shown me following notification after i closed the period..
    Mode: Close period only
    Client:800
    Period entered (month/year):042010
    Invalid period for company code CLC1; no conversion here.
    Period closing complete; log issued.
    Mode: Close period only
    Client:800
    Period entered (month/year):012012
    CoCd CLC1: table T009B incomplete; no conversion here.
    Period closing complete; log issued.
    Mode: Close period only
    Client:800
    Period entered (month/year):022012
    Incorrect period in control rec. of CoCd CLC1; no conversion
    The current period (month/year) of the control record is122006
    Period closing complete; log issued.
    E N D

  • Any Standard FM  for material stocks on posting date  using  Tcode  MB5B

    Hi,
    I  need   Standard  FM  to get  material stocks on posting date  using   Tcode   :   MB5B
    Stock type  i am using  is  : Storage Location/Batch Stock
    the  Input   i am  providing  is    Material, Plant , Storage Location, selection  date From , selecDate To.
    Then   i need  to get  data  that it  provides   header  and  document  item level.
    Can u please tel me  how do i get  that  material stock data  on posting date and in which tables
    it will be populated in the database.
    ITs required  can u take view and post info
    Thanks & Regards
    sivakumar kasa
    Edited by: siva kumar kasa on Dec 21, 2010 2:30 PM
    Edited by: siva kumar kasa on Dec 22, 2010 7:15 AM

    hi Rehan,
    I have checked all settings also enhancement  but there is no as such control to restrict backposting within current period
    I think its self disipline action not to post backdated GI when GR is done on later date
    Vishal...

  • Posting date for rebate credit note document

    Hi friends,
    This is with reference to settlement of rebate agreement. There is a background job executed say today, but the posting date was backdated to 31/08/2011. The financial posting period for current month starts from 27th of Aug and the posting was done in current period only. The validity of the Rebate agreement ends on 31/08/2011.
    My query is what is the reason behind the system posted the document on 31/08/2011.
    Is it because the validity ends on 31/08/2011.
    Quick responses are appreciated.
    Thanks & regards,
    Praveen.

    Hi Praveen,
    You are correct.  The final settlement credit memo request uses the last day of the agreement validity period as the billing date.
    Please refer to the 29th Page  first and second lines of the Matthias white paper of Rebate management. Below is the link.
    http://www.erpgenie.com/publications/saptips/052005.pdf
    Hope this helps

Maybe you are looking for