Posting Period Locked

Hi,
While performing Overall completion confirmation(IW42) in PM,I get error msg "Posting period is locked for 009 2009".
Please let me know how to resolve this issue.
Regards,
Shanmuga

Hi,
Try out T code - MMRV, it will help you to open previous closed posting period.
Or check,
whether there is any authorization mantained for that.
Check thru :
set authorization to users who are allowed to change the status (authorization >>> Administration >>> system Initialization >>> Posting Period >>> change period status)
2)  authorization to users who are allowed to change the status (authorization >>> General >>> Period Status: Unlocked Except Sales or Period Status: Closing Period)
3) Change kinds of date in detail of posting period to meet your requirement.
Dhara.

Similar Messages

  • Posting period locked in controlling area

    Hi
    I am getting error while closing order ( posting period is locked in the controlling area xxxx for the period 11 in 2007)
    i am able to post periods up to 10
    how to rectify this
    regards\
    prasad

    Hi,
    See the tcode OB52 and OMSY
    Regards,
    Sankar

  • Posting Period is locked at the time of CO11

    I am facing an issue in CO11..system is giving mesaage that Posting period in close.
    I hav echecked FI & MM Period is open. What could be the reason...
    Vivek
    Moderator: Please, avoid asking basic questions

    Hi
    Are you posting in previous period? If yes, then check in MMRV that back posting is allowed to previous period or not
    If you are posting in current period, and you have already ensured that FI/MM periods are open - Then check OKP1 for Actiivty locks
    Regards
    Ajay M

  • PCA Manual Posting - Open/close posting periods

    All,
    Is there a way you can open or close PCA posting periods? The FI posting period control does not control the PCA manual posting. We need however to do this. Is there a way to do it. I know I can create a validation. But is there any other way?
    Regards,

    Hello,
    here is the one and only correct answer for your question:
    Unfortunately, there is no possibility to lock periods / posting
    transactions in PCA (including distributions).
    There are only two possibilities to prevent postings to profit centers:
    1. is to completely lock them in the master data via transaction KE52 (tab 'Indicators' -> activate 'Lock indicator'. Please read also the F1-help here for the field 'Lock indicator')
    2. to lock one complete fiscal year in the entire Profit-Center
       Accounting via transaction 1KEF.
    One important reason is that PCA receives its postings from preliminary applications like MM, CO, FI. Therefore, postings can only be locked in those applications (like in FI via TN OB52 or in CO via TN OKP1 or FI-SL via GCP1), but not directly in PCA.
    Excpetions from that are described in the SAP notes 436384 and´836218 for manual postings made with transactions 1KEL and 9KE0. With the coding corrections of the both notes a period lock is possible for these two transactions.
    It is not planned to have a general functionality of period locks in Profitcenter Accounting. PCA should be always open for postings. It is designed to be the receiving application of data delivered by the preliminary applications. Therefore period locks must be handled / maintained also in those applications.
    Best regards,
    Andreas

  • FI Posting Period

    Dear Experts,
    Can any one suggest me the way to maintain authorization group in such a way that i can close the Financial period for all my sites accept the head office and certain users can post the entries but no one else can make the entry for that date from head office.
    Hoping for an early response.
    thanks in advance.
    Rahul

    Hi
    The authorization object F_BKPF_BUP (accounting document: Authorization for posting periods) from posting in periods which are only open for time period 1.
    How this can be used is, usually you have Senior Accountants and Managers. If your manager needs to open the previous month book to post some rectification entries, in this case the Senior accountants also allowed to use the previous posting period if there is no authorization object is assigned particularly.
    But by assigning the above said authorization object to Senior Accountants, he is authorized only for the periods which is mentioned in that Period 1 coloumn and the Period 2 will be locked to him, any changes for the previous periods, special periods all will be available only to the persons who is not restricted.
    Hope it Clears.
    thanks and regards
    Praveen.J

  • Voucher Number in new posting period

    hello,
    I have created new posting period and series for financial year 2011-12.
    In previous year I have created 600 voucher. My issue is that when I am creating new
    voucher, voucher number is showing 601. I want that for new series voucher number should be
    start from 1. but it seems like numbering series doesn't affect the voucher number.
    Because there are no series creation for journal voucher. In this case how can I solve my problem.
    Please help me on this.
    thanks
    Annu

    Hi Annu.............
    You created Posting Period but have you created Period Indicator and Assigned this Indicator to this created Posting period?
    If you have done this then when you define new no. series from one just assign the same indicatorto this New No. Series also and lock old series.....
    Hope this will work....
    Regards,
    Rahul

  • Period locked for new data on PO an SO

    Since last week when we try to update a PO anr SO we got this Message
    PERIODE LOCKED FOR NEW DATA.
    For exemple we change the remark feild only and we got this message.
    Since PO and SO are not impacting any gl entry this is not normal. on the DEMO DB i can update a SO or PO when the perio is close without any problem

    Hi Roy,
    First you have to change if your posting perioud is close.
    if close then choose your posting perioud then in your window left side a sign of triangle click on.
    after change ur status  and after u are able to do changes in previous posting perioud.
    this may help u...
    Thanks.
    JRAJPUT

  • Problem with period lock OKP1

    Hi all,
    I locked period in Tcode OKP1 for all transaction
    However, transaction in 9KE0 is not locked yet
    I don't know why. Can anybody help me?
    Thanks and regards

    Hi,
    thathere is no possibility to lock periods / posting transactions in PCA (including distributions), because PCA should be always open for postings. It is designed to be the receiving application of data delivered by the preliminary applications like FI, MM and CO. Therefore period locks must be handled / maintained in those applications. In PCA, there are only two possibilities to prevent postings to profit centers:
    1. is to completely lock profit centers in the master data via    transaction KE52 (tab 'Indicators' -> activate 'Lock indicator'.
       Please read also the F1-help here for the field 'Lock indicator')
    2. to lock one complete fiscal year in the entire Profit-Center Accounting via transaction 1KEF.
    There are two exceptions for that which are provided for transactions 1KEL and 9KE0 by SAP notes 836218 & 436384. As in these notes described, you can block periods via using FI-SL periode-block, but only for manual posting.
    Regards,
    Greta

  • Client Creates incorrect posting period

    Good Day,
    I have a client that wanted to create a new period for January 2012.
    He however did it incorrectly, and set the sub-periods as year, and thus the posting dates, due dates and document dates have all been set from the 1 jan to the 31 dec 2012.
    he has posted two purchase orders to this posting period and thus the period cannot be removed and the correct one added.
    Any Suggestions?
    Thanks
    Regards
    Dario

    HI
    Yes you right we can update Dates.
    You can Locked This posting period and can make new posting period with Monthly sub-period .
    Thanks & Regard
    Khan Imran

  • Posting Period Authorization

    SAP Version: SAP B1 8.8 PL 10
    Hi All,
                On 1st of  every month we close the Previous moth Posting Period, so that No user can Add or Update any Documents which belongs to the previous month. But we had to give authorization to few managers to update.
                We tried to achieve this in this way:
                1. Previous month Posting period set to Closing Period
                2. Set Authorization to all users No Authorization for Period Status: Closing Period & Period Status: Unlocked Except Sales in Authorization window.
                3. And Set Posting Periods to NO Authorization in authorization window.
                       By Doing this should make all users who have got NO Authorization to Period Closing should not be allowed to  Update OR Add any Documents which belongs to Previous month.
                       But this is not happening. I am able to cancel the document and add the document in to previous month logging into the user who doesn't have authorizations to do so.
    Is there any other way to Achieve this.
    Cheers,
    Sree.

    Check the solution as follows:
    dministration -> System Initialization -> Posting Periods
       1. The implications of different Posting Period Status.
    When Posting Period status is set as:
    Locked
    any data entry or journal entry will be disabled for all users.
    Unlocked
    data or journal entry can be done by any user in this period provided that General Authorization does not restrict the user from certain actions.The functionality is as the following combination of fields values 'Active'=Yes, 'Locked'=No from the previous versions.
    Unlocked Except Sales
    data and journal entry can be entered within all document types appplications and tools except any Sales document under (Sales - AR). The functionality is as the following combination of fields values 'Active = No, 'Locked'= No from the previous versions. Work under this period status is allowed only for those users who have assigned 'Full Authorization' in General Authorizations form -> General group -> Period Status: Unlocked Except Sales.
    Closing Period
    data and journal entry can be performed within all document types, applications and tools. Work under this period status is allowed only for those users who have assigned 'Full Authorization' in General Authorizations form -> General group -> Period Status: Period Closing.
    NOTE: The Period Indicator set for certain Posting Period does not influence on the possibility of entering data (marketing documents and journal entries).
    NOTE: When you log to a company after its upgrade from previous versions then SAP Business One checks for "Unlocked" and "Unlocked Except Sales" periods whether their 'To Date' are older than Actual System Date. If YES those period statuses are changed to "Period Closing".
    It is also possible to switch on / off this automatic update of periodstatus and also define a delay in days. For more details please refer to the 'Automatic change of period status' section.
       1. Automatic change of period status:
    Period status of just ended posting period (based on actual system date) should be automatically changed from "Unlocked" or "Unlocked Except Sales" to "Period Closing" after the very first log into the system in a new subsequent posting period (based on actual system date) when "Automatic Change of Period Status to 'Closing Period' " checkbox is checked and value in "Date When Automatic Change Is Applied" field equels 1 (what are actually their default settings after upgrade or when new company is created). However, if authorized user would change the period status back to "Unlocked" or "Unlocked Except Sales" from "Period Closing" and the system would be started again e.g. next day or simply in a few seconds later, automatic change would not be applied any more.
    User can decide to disable function of Automatic Change of Period Status by unchecking "Automatic Change of Period Status to 'Closing Period' " checkbox.
    User can also decide to execute automatic change on the second or later day in new period or even the period after by entering a new value in "Date When Automatic Change Is Applied" field on Posting Period. When the value = 1, the change is applied on the first or later day of new period depending on the first login into the system. When the value = 2, the change is applied on the second or later day depending on the first login into the system. Default value for new company and after upgrade is 1.
       1. "Posting Date To" field is disabled.
    When you try to add a new Posting Period, SAP Business One offers the next free year which has not been defined yet. For example, when you have already defined Posting Period for 2006 year and then you want to add a new one, SAP Business One proposes you the next 2007 year (in Administration -> System Initialization -> Posting Periods -> orange arrow callingparticular posting period form -> 'Dates From... To' fields) automatically. Moreover, when you want to add a not annual period (e.g. quarter, month, etc.) then even if the "Posting Date To" field is disabled and has wrong value in process of adding, after the period is created the value of the field "Posting Date To" is recalculated and changed to correct date (usually end of the year).
       1. When any data or journal entry is being created behind some system document (exactly when a user tries to add the document), SAP Business One checks whether the entered date value in 'Posting Date' field fits any defined posting period. If NOT i.e. there is no posting period defined coveringthe entered Posting Date, the following system error message will appear as a pop-up: 'Posting Date deviates from the defined range. To complete the action, define posting period matching the entered Posting Date.'
       2. When deleting Posting Periods (by sub-periods) SAP Business One checks whether there is no data entered within the particular period, additionally SAP Business One checks if at least one very last posting sub-period remains defined in the database. If not, the deletion will not be allowed under any circumstances. As part of this restriction, the following system error message will appear for the user: 'Cannot remove the last period'.
    it is from SAP note 1050246. if not resolve, log a message to SAP support or upgrade the PL version from 10 to 13.
    JimM

  • MMPV Posting Periods

    Hi All
    I have closed the periods in advance by mistake like for 9th month closed till 11th month. how do i revert back to the 9th month. i have followed the sap note 487381 but the problem after that is in Trans MMPI when i try to execute it says some material master record are loced as a result initilization is not possible please help me and can you let me know how to check if any material is locked as there are loads of materials and i cant check each material individually
    thankyou in advance

    Reopen The Closed Period
    It is possible to re-open a previously closed period. However, it is NOT advisable to do so because the valuation data of the previous period could be affected.
    In general, it is only safe to reopen a previously closed period when no material postings have been done after the period shifting to the new period.
    If there has already been postings after the period shifting to the new period, reverting the period back will cause database inconsistencies in the history tables.
    If you decide to proceed with this process, you can use the program RMMMINIT, but, please review the documentation of this program first!! and the check the SAP notes 487381 (for the error message that you are receiving) and the 369637 (for an explanation about the inconsistencies that will be generated.
    Steps are as below;
    Go to Transaction Code SE38
    Enter program name RMMMINIT
    Execute or press F8 function button
    Enter your company code (From and To)
    Enter relevant date: Say 01/03/2008 for Mar. 2008 month to be opened as of now
    That means, user can post for the month of Feb 2008 as well as Mar. 2008
    Refer SAP Note No. 487381 for more details.
    As per SAP Notes 487381 ( If the periods are opened in advance in mmpv to again change it to current period the following process should be follow ), Go to Tcode MMPI, then go to menu bar and select system -> user profile->owndata.In that screen , under the parameters tab enter MMPI_READ_NOTE in Parameter ID field and enter, then under short description you will get Initialise period. Next Save.
    Again go to MMPI enter company code, period and year and execute.
    XXXXXXXXXXXXXXXXXX
    Other way of doing it is follow these steps( But try this method in Sand box Only):
    1. Go to OX18, and delete the plants assigned to your CO.Cd and save.
    2. Go to OMSY and change the posting period to the one u want and save.
    3.Go to OX18 and assign the plants you have deleted in step 1.and save.
    SHD0: http://www.mortenhjorthnielsen.dk/Security/transactionvariants.htm
    If oyu have knowledge of Transaction variant then you can use SHD0 tcode and generate the transaction using defualt type and give that transction to user instead of ME21N so they will not have the issue.
    The exact solution for your problem is as follows
    Go to Tcode SHD0 and enter the transaction variant
    In T code field enter MIRO and then enter the ZMIRO or the name you want to keep in transaction variant field and hit create button
    This will take you to MIRO transaction and here you just post the invoice but make sure you enter the House bank key whic you want to default.
    Once you finish system will save this one as a variant
    Every time you hit or enter the pop up screen comes here you just hit enter and which ever data you want to default that you have to select in the Popup by checking the Box
    W content and output only for your case the field XXXXXXXX should be selected for W content and output only
    Make sure you have value 1 in contents field
    If not then restart the variant again and on the MIRO screen reselect the invoice field
    Later exit and save (save in the object which you can transport)
    Then from SHD0 transaction select GOTO create variant transaction and here you careate the tcode and use that tcode for MIRO

  • BDC or BAPI for Actual period Locking

    Hi,
    Thank You very much for reading this query.
    I have to deveop the SE38 program with a selection screen which should contain following fields.
    1) Controlling Area
    2) Fiscal period,
    3) Fiscal year
    4) Version,
    5) Actual/Plan
    6) Lock/Unlock
    7) Business transaction.
    My requirement is if user creates a variant by giving proper values and runs the job, it should lock the given the business transactions.Functionally this task will be done by functional people in OKP1 transaction code (CO-Controlling.)
    Please suggest me if any BAPI is there and shall I go ahead with BDC.
    The problem if i go with BDC is, some times user may scroll down the table control depending on the given values. So how to satisfy this condition.
    Thanks and Regards,
    K.krishna Chaitanya.

    Hi Krishna,
    I know this is an old post, but in case someone else comes across it while searching for a solution to this same problem (as I did), Sanjeev Kumar has written a document, Automate Period Opening in SAP which, among other things, discusses using report RKCOOKP1 (Set Period Locks in Batch) to set or delete period locks in controlling (OKP1). In addition to scheduling a job for RKCOOKP1 as the document demonstrates, you could also call RKCOOKP1 programmatically with SUBMIT report ... AND RETURN.
    Cheers,
    Amy

  • Posting period is showing in future date

    Hi,
    This is issue am facing in my IDES system.
    The error it is showing is as below:
    Posting only possible in periods 2015/03 and 2015/02 in company code z001  and message number M7053
    other inputs: MMRV :  Current peiod   : 03 2015
                                           Previous period: 03 2015
                                       Last period in previous .year 12 2014
    And one more input about this is, in my system  the system timing was showing 2011, this i did not recogbise, and when i tried to do the post goods issue(PGI) system shown some Posting error then i cloed the periods through MMPV t code, and closed upto 02 2015, then i reliazed why still system is allowoing to close the periods. then i checked the sytem timing and corrected it to current date.(13 th July 2014).
    In OB29 my Fiscal year variant is K4 (number of posting periods 12 and no of Special periods 4) is assigned to my company code z001 in t code ob37
    In OMSY "also showing the 2015 3
    Now even after changing the sytem date to correct date still system is showing the periods problem, when i tried to initialize the periods in t code MMPI sytem is showing the below message "Follow the instruction note 487381 before initialiazation"
    I found many treads similar to this issue, but all of them faced past date, needs to be closed the periods until current date, where as in my case the periods alredy open in future date.
    am not much familiar with this periods problem as am SD consultant.
    Please help to resolve this issue.
    thanks,

    Nobody needs help of an ABAPer to close or open periods, this is just normal customizing.
    Goto service.sap.com/notes and read the content of the OSS note mentioned in your message and just follow it, as it is the only way to run period initialization. It does not matter it you rolled it to far into the future or if you still have stone old periods like in the hundreds of other discussions on the same issue.
    And since this is that often discussed I am locking this thread.

  • Remove Posting Period with transaction

    Hello everybody,
    How I can remove Posting Period that already have transaction
    If i create posting period and choose wrong sub period (example,choose year but correct is month)
    and post some transaction into period
    if i reverse all transaction in wrong period
    Can i remove posting period and create new postiong period with correct condition.
    sorry with my poor english
    Thank,Seang
    Edited by: Suthee Thurathanmanon on Oct 1, 2008 9:07 AM

    Hi,
    In the posting period window u can find 2 drop downs. Active and Locked. Try them to make the period inactive.
    Hope it helps,
    Vasu Natari.

  • Error while running a query-Input for variable 'Posting Period is invalid

    Hi All,
    NOTE: This error is only cropping up when I input 12 in the posting period variable selection. If I put in any other value from 1-11 I am not getting any errors. Any ideas why this might be happening?
    I am getting the following error when I try and run a query - "Input for variable 'Posting Period (Single entry, mandatory)' is invalid" - On further clicking on this error the message displayed is as follows -
    Diagnosis
    Variable Posting Period (Single Value Entry, Mandatory) is used as a lower limit (X) and an upper limit () in an interval selection. This limit has the value #.
    System Response
    Procedure
    Enter a different value for variable Posting Period (Single Value Entry, Mandatory). If the value of the other limit is determined by another variable, you can change its value also.
    Procedure for System Administration

    OK.
    Well, if the variable is not used in any interval selection, then I would say "something happened to it".
    I would make a copy of the query and run it to check if I get the same problem with period 12.
       -> If not, something is wrong in the original query (you can proceed as below, if changes to original are permitted).
    If so, then try removing the variable completely from the query and hardcode restriction to 12.
       -> If problem still persists, I would have to do some thinking.
    If problem is gone, then add the variable again. Check.
       -> If problem is back, then the variable "is sick". Only quick thing to do, is to build an identical variable and use that one.
    If problem also happens with the new variable, then it's time to share this experience with someone else and consider raising an OSS.
    Good luck!
    Jacob
    P.S: what fisc year variant are you using?
    Edited by: Jacob Jansen on Jan 25, 2010 8:36 PM

Maybe you are looking for