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

Similar Messages

  • POSTING PERIOD ERROR WHILE DOING GR

    Dear All,
    I am facing error in posting period while doing GR -
    1) Posting period 007 2010 is not open - For current date GR
    2) Posting only lies in periods 2010/07 and 2010/06 in Company Code - For future date in 2010-08
    3) Posting period 006 2010 is not open - For back date GR in 2010-06
    Checked T Code MMRV - Ticked -  Allow posting in previous per. (Still facing the same error)
    Also as per MMRV -
    Current period  07 2010
    Previous period  06 2010
    Last period in prev. year 12 2009
    Please guide
    Vikas

    Hi,
    Check on it:-
    COGI Posting period error
    Re: Error in Opening the Posting Period.
    http://www.sap-img.com/sap-sd/movement-type-posting-error-in-delivery.htm
    pherasath

  • Error while  uploading stock using Mb1c and migo

    Hi
    Following error is showing,while  uploading stock using Mb1c and migo
    Return code 8 is not permitted with BAdI 'FAGL_PERIOD_CHECK'
    Can anyone help me?/
    Thanks

    Hi
    You will need the help of an abaper in solving this , as a BAdi FAGL_PERIOD_CHECK - Posting Period Check has been activated.
    Please check the implementation of the BAdi , i feel that it has not been implemented properly.
    This Business Add-In (BAdI) enables you to extend the existing check of open posting periods.
    The result of the period check is provided to you as a parameter (CH_SUBRC). In your implementation, you can derive this parameter again (for example, if a posting is rejected under a certain condition).
    The following values are allowed for parameter CH_SUBRC:
    0 Posting allowed
    4 Period & is not open for account type & and general ledger &
    6 No authorization for posting period & &
    This is a custome developemnt , so only the ABAper present at your end will be able to resolve it.
    Thanks & Regards
    Kishore

  • Error -while updating stock in MB1C for make to order (561-E)

    Hi all,
    I have created a sales order with reference to quotation.
    Stock is updating for Quotation number. But i stock should be updated to the sales order number.
    When i am updating the stock for this sales order number, its not accepting. Its asking the preceding number.
    system shows the following error,
    "Account assignment cannot be carried out because of different origin no.
    Message no. V1134
    Diagnosis
    The sales document to which you want to refer is based on sales document 10000001 and item 000010. Therefore, the settlement and possibly inventory management are carried out using the number of the preceding document.
    System Response
    This entry is not allowed.
    Procedure
    Enter the document and the item number of the preceding sales document."
    Can anyone tell me how to solve this issue?
    Thanks in advance,
    Babu

    solved

  • Posting period issue while deleting a confirmation posted for a limit PO

    Hi ..
    I am facing an issue whiel deleting a confirmation posted for a limit PO.
    Confirmation was posted for a limit PO in SRM and it created a service entry sheet in SAP. If I deleted that confirmation in the same posting period, then it is getting deleted. No issue here.
    But if I deleted that confirmation in the next posting period then the reversal document is going to error in process. RZ20 is showing the error "Positng only possible in periods 2012/2 and 2012/3".
    Posting date of reversal document is current date only and the backend posting period is 2012/3, but still it is failing with this posting period error.
    If I tried to delete a confirmation posted for a normal PO then I could able to delete it even in next posting period by just changing the posting date.
    Why this posting occurs while deleting the limit confirmation, even through the posting date is falls within the backenn posting periiod? Is it like, SAP system is trying to delete the service entry sheet in original posting period? Kindly help.
    I am in SRM 5.0 (server 5.5) SP12.
    Thanks,
    Arun

    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

  • Unable to Log-in *SAP System Message : Error while reading a Dynpro*

    Hi,
    We are facing issues while logging-in through SAP logon 710.
    The system throws an error dialog box with the below message:
    SAP System Message : Error while reading a Dynpro
    At the OS level Java process  server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

    Hi Please find the contents of std_server.out below.
    stdout/stderr redirect
    node name   : server0
    pid         : 4124
    system name : KEC
    system nr.  : 01
    started at  : Mon Jul 27 15:44:57 2009
    [Thr 5656] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel 110760.44 is starting...
    Loading: LogManager ... 250 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 47 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 0 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 93 ms.
    Loading: LockingManager ... 32 ms.
    Loading: ConfigurationManager ... 1032 ms.
    Loading: LicensingManager ... 0 ms.
    Loading: CacheManager ... 93 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service runtimeinfo started. (16 ms).
      Service cross started. (31 ms).
      Service file started. (31 ms).
      Service memory started. (31 ms).
      Service timeout started. (16 ms).
      Service trex.service started. (32 ms).
      Service userstore started. (0 ms).
      Service jmx_notification started. (15 ms).
      Service p4 started. (62 ms).
      Service classpath_resolver started. (16 ms).
      Service deploy started. (3722 ms).
      Service MigrationService started. (31 ms).
      Service bimmrdeployer started. (0 ms).
      Service log_configurator started. (5177 ms).
      Service locking started. (0 ms).
      Service http started. (126 ms).
      Service naming started. (157 ms).
      Service failover started. (16 ms).
      Service appclient started. (31 ms).
      Service javamail started. (47 ms).
      Service ts started. (47 ms).
      Service jmsconnector started. (47 ms).
      Service licensing started. (15 ms).
      Service connector started. (93 ms).
      Service iiop started. (94 ms).
      Service configuration started. (16 ms).
      Service webservices started. (265 ms).
      Service dbpool started. (1204 ms).
      Service UT started. (0 ms).
    Jul 27, 2009 3:45:09 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "     Error while reading a dynpro                                        ". This message is critical if it appears during the startup of the AS Java.
    Jul 27, 2009 3:45:09 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro                                       
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro                                       
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro                                       
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro                                       
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jul 27, 2009 3:45:09 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

  • Error while creating stock using tcode: MB1C

    Error while creating stock using tcode: MB1C
    The Error is: Check table T004F:entry G006 does not exist

    Hi ,
    Please check the FSV (field status variant) for your company code in OBY6 .
    then go to transaction code OB14 --> enter the FSV --> Check if field status group G006(Material account) is maintained there or not.
    if not please maintain it.
    Thanks & Regards
    Anshu

  • Error while create stock without order_MB1C_Mov 521

    Dear Experts,
    we have creating new plant with reference to old plant. While create stock through MB1C with movement type 521, system given the error message "Busi area 1A not allowed for CoCode 1100; Check whether Busi area is blank" Message no. /EACA/GL_TOOLS006.
    Please help
    Regards
    BK GAIKWAD

    Sorry to late replay,
    We have tray to use another movement, but same error message occurred. Also we have already assign the plant in OKB9 & OMJ7.  please advice.
    Regards
    BK GAIKWAD

  • Someone can help me here with posting period error in doing GR post in SAP

    Hi Seniors,
    I've been getting below error while doing GR post. could someone help me to step on further with this error.
    "Check table T001B for record type "0", the selected company code, account type S and G/L account 191***  If required, make sure that an entry is made in the table or an interval is changed."
    i'm using test system as am a student of SAP MM.
    Thank you very much..
    Shivakumar

    Open and Close Posting Periods
    In this activity, you can specify which periods are open for posting for each variant. You have two time intervals (time period 1 and time period 2). In each interval, specify a period lower limit, a period upper limit, and the fiscal year.
    You close a period by selecting the period specifications so that the period to be closed does not fall within them.
    You can also assign authorization groups for permitted posting periods. This means that in month-end or year-end closing for example, you can open some posting periods for specific users only. The authorization group only has an effect on time period 1. The authorization object is F_BKPF_BUP (Accounting document: Authorizations for posting periods). For more information about assigning authorizations, see the corresponding section for User Maintenance.
    Note
    Specify G/L account numbers for your specifications. You define the permitted posting periods for the subledger accounting accounts using the relevant reconciliation accounts. To do this, specify the account type for the subledger accounting, such as D or K, and the relevant reconciliation account.
    Caution
    There must be a minimum entry for each variant. This entry must have + in column K, and the columns From Account and To Account must not contain entries. In the columns for the posting periods, specify the periods you want to always be open in this variant. With further entries, you define more specifically which periods are to be open for which accounts.
    Activities
    1. Specify the periods permitted for posting.
    2. First enter the periods permitted for posting for all variants (minimum entry).
    3. Then add entries for account types or account areas if the periods are to be further restricted for specific accounts.
    4. In addition, enter an authorization group for each time period 1 in order to limit user access.

  • Re: Posting period error message  while QM inventory posting

    Hi All,
    I am having a situation where the client is not able to make the UD for inspection lots because of the postinng period message.
    Now as there might several backlogs in the previous month I have suggested the client to make the posting on 31.08.2008.
    I need to ask one question:
    But in case of UD for inspection lot the 'inspection END Date' is picked from the inspection lot.
    So, whenever the user is trying to do UD he is getting the message that " posting only possible in period 2008/05 & 2008/04.
    To avoid this error I suggested the user to change the "insp. END Date " in the inspection lot i.e. QA02 to 31.08.2008.
    Is this the right way
    Please advice.
    Regards,
    Vivek

    Dear Vivek,
                     Babu Singh is absolutely right that you have to ask FI/CO person to open current period so that the Stock Posting and Document Date as wel as UD can be saved.
    Further if you want to post the Stock in Back Date ( For Example if you are working on 1st Sep. and want to post stock on 31.08.2008) then you have to go to Inspection Lot Stock Tab----> Click on 'DOC...' (Posting Date, Doc. Date) Then you can change the date as per your requirement.
    I Hope that it will solve your problem.
    Please close the Thread if you get your answer.
    Thanks.

  • Posting period error in MIGO

    Hi Friends,
    I am getting the same error while doing posting a GR for PO as
    " Posting only possible in periods 1998/06 and 1998/05 in dev server. I checked in OB52 for opening periods. It starts from 1st month of 1998 to 12 2010. The fiscal year variant for CO Code is V3. I gave posting date as 15.6.1998 but still the same error comes.
    PL help to resolve this.
    Regards.
    Ram

    Hi,
    Use MMPV..
    Enter your company code-09
    Enter period you wanna open--1998
    Enter year--
    Press inside execute button
    System will show you message that the period is nt current period jus after taht press main execute button..
    Go on opening till you reach the current one...
    Can check the open periods in OMSY
    Regards,
    Priyanka.P
    AWARD IF HELPFULL
    Edited by: Priyanka Paltanwale on Aug 7, 2008 2:18 PM

  • GETTING ERROR WHILE CREATING STOCK RELATED TO FI

    ERROR: Period 001/2012 is not open for account type S and G/L 799999.
    please give me the solution for this error
    Moderator: Please, avoid asking basic questions in CAPITAL letters

    Hi Expert,
    In T-Code: OB52, We need to open the period 001 for Year - 2012 for the Account Type - S and for GL Account - 799999.
    Configure as shown below for your Posting Period Variant:
    Account Type: S
    From Account: (Only provide any GL Accounts From Range, If you require any specific GL Accounts to be open. Else leave blank)
    To Account:(Only provide any GL Accounts To Range, If you require any specific GL Accounts to be open. Else leave blank)
    From Period: 01
    Year: 2012
    To Period:01
    Year:2012
    From Period:13
    Year:2012
    To Period:16
    Year:2012
    Save
    Regards,
    GK
    SAP

  • Error, While Creating stock

    Dear Guru
    When i was create a stock (Trans : MB1C) entering all the details
    error is " Posting can only be made to G/L acct 79999 in cur EUR"
    i understand the error, but where i can change currency eur to inr.
    pls give me your suggestion
    regards
    [email protected]

    Hi Renu,
    currency every where you have to mauntain the same like sales org- company code -plant- shipping point- you can't maintain defferent place difference currency.
    maintain every where same currency noe go to FS00 give G/L account 799999 and go to control data change the currency i don't think you will  have the problam.
    i hope you have understood.
    your doubt is clear don'tforget to reward.
    thanks
    surya

  • Posting Period Error

    hi guys
    I created PO and Migo and after that when i am raising MIRO with Credit Memo. Following Error occurs
    Error Message :
    Allowed posting periods: 06 2008 / 05 2008 / 12 2007
    Message no. M8022
    Diagnosis
    The posting date is not within one of the allowed posting periods.
    This can be due to one of two reasons:
    The correct current period has not been set in the system.
    For the system, the first of the specified periods is the current period. At the beginning of a new period, your system administrator must change the current period in the material master record using the function "Close period". This has not yet been done.
    You have entered the wrong date in the field "Posting date".
    Procedure
    Check the posting date and correct it if necessary. If your entry is correct, inform your system administrator that the "period closing" procedure has not yet been implemented
    Even When i closing Periods its not allowing  to close the periods.
    Kindly suggest me the solution.

    Hi,
    FI period not open now.
    1st Check in MM side in T.code: MMRV and see which period is open for ur Co.Cod .
    Now in FI side use t.code: OB52 and open the 07, 2008 period in Account Types A, K, D,M, S and specially Account Type u201C+u201D which stands for valid for all accounts type and save.
    Now try ur transaction.
    Note: Check Fiscal year variant in OBY6, hope it is K4.
    Regards,
    Biju K

  • POSTING PERIOD ERROR URGENT

    I am getting the error is POSTING PERIOD 012 2007 IS NOT OPEN. Please solve my problem.

    Please check your Company Code posting period in MMPV, you may have to check and close all the period or months one by one from the period given there, till 2007 curent month. You can also check it up for status alternatively in OMSY. Note : Period refers to months in accounting.
    Award points if helpful.
    Thanks

Maybe you are looking for

  • [solved] Makepkg fails to sign package w/o asking password.

    I'm not sure when exactly this issue really started happening, but it was somewhere around the time that the new versions of Pacman and gnupg came out (a few weeks). I have a local ~/.makepkg.conf configured to sign any package I build with my key. T

  • Can't set the time on the 6500 Slide

    I just bought a 6500 slide and can't do one of the most basic things - set the time! I have gone to auto-update but it is shows the wrong time. At the time I purchased the handset the sales assistant turned the phone on to check if my sim card was wo

  • Problem with adobe flash player content

    Hello Everybody, I'm using an 'ActiveBook & DVD' (for English Language Teaching) that uses adobe flashplayer audio - when the ActiveBook is open (from the DVD) I have the following problem: if I click on any audio file button in the ActiveBook (ebook

  • N8 - Ram memory

    Ive got a problem with the Ram Memory on my Nokia N8. When i switch the phone on i have 115mb free and 131 used, this is fine and the phone works quite quickly. However over the next few days i lose about 20 to 25mb a day resulting in less than 50mb

  • Sql developer query window corrupting on scroll

    Hi there I have a weird error - when I scroll in my SQL developer query window (tab) the text corrupts and only comes back if I click in the window somewhere or save. Has anyone else seen this? I'm on version 1.5.5 and don't really want to upgrade to