Posting only Possible in Periods 2012/12 and 2012/11 in Company Code

syed farooq asked Mar 4, 2012 | Replies (19)

Dear Gurus, 

I have open 12th(march) period instead of 11th(February)in my co.code. It means I have closed the

11th period when I m in 11th period only. Now when posting goods receipt through migo it is

showing error Posting only possible in periods 2012/12 and 2012/11 in company code .. I unable to

post the document I have checked in and the tick box posting allowed in previous period in omsy

mmrv. Now I'm in 12th period still I'm getting the same error. could you please do the needful. 

Regards, 

Farooq

Answer this question

|

Join this group

Popular White Paper On This Topic

 Data is Your Catalyst to Success in an SAP Deployment

19 Replies

1

Shihab MS replied Mar 5, 2012

Hi Friend 

Please Check the Period status in the MMPV and close the period if needed and use MMPI for

opening New period.0

jhansi priya replied Mar 5, 2012

hi 

create no. ranges for 2012 in OMBT t.code and go to groups--> select WE 

---> go to menu intervel-->maintain or shift+f5 

and select any one of intervals and go to menu ----> edit----> insert year 

or F6. I hope your problem will solve. 

jhansipriya0

Dipti Thakur replied Mar 5, 2012

Hi, 

Have you checked in MMPV? 

Regards 

Dipti0

syed farooq replied Mar 5, 2012

Yes, I have created no ranges for we still i am getting the same problem.. Initially instead of closing

10th period i have closed 11th period.. now it is showing current year/period 2012/12White Papers and Webcasts

Popular  Antivirus Comparison Guide

Related  Digital transformation: Creating new business models where ...  2011 Focus Experts Guide to CRM for Growing Midsize ...  State of ERP Systems

More   White   Papers

0

syed farooq replied Mar 5, 2012

Dear jhansi priya, 

thanks for your reply. 

I got the answer through this way Hi, 

By using transaction MMPV you can close the year and months up to current month or otherwise go

to OX18 and delete company code and plant assignment , after that go to transaction code OMSY

and select your company code and maintain current year and current month . Again go to OX18

transaction and assign plant to company code and post the stock in MB1C.0

vetri selvan replied Mar 5, 2012

Hi friend, 

Please check the Doc.date and Posting dt in MIGO 

Regards, 

Vetri0

Dinky replied Mar 9, 2012

Check OB52.0

Mergz_711 replied Mar 9, 2012

Hi Dinky, 

Please use tcode MMPV to update posting period. 

thanks.0

venkattatavarthi replied Mar 11, 2012

CHECK OB520

SAP_FICO replied Mar 11, 2012

Check once in T.Code OB52 and OMSY. Whether 11 and 12 periods are open or 

not.0

tapanmaity replied Mar 11, 2012

hi 

check once t code OB52, AND OMSY AND check present period are showing or not otherwise you

go to OX18 and delete plant from co. code. and again go to OMSY and change period and save it

after save it again you go to OX18 and assign your plant and save it. I think your problem solve 

regards 

Tapan0

tapanmaity replied Mar 11, 2012

hi 

at the time of MIGO of 11 period showing error do one thing, you go to T. Code OX18 and delete

plant in company code level and save it. then go to OMSY and change your present period than its

work. 

Regards. 

Tapan0

Anshu replied Mar 14, 2012

same prob n I also use t.code OX18,OMWD,OMSY,OB52 but still facing prob. posting only possible

in periods 2012/12 and 2012/11 in company code :((0

Shihab MS replied Mar 14, 2012

HI Anshu 

use MMRV to check which posting period is open for company code and use T Code MMPI to open

new posting period0

Anshu replied Mar 18, 2012

hello Shihab MS Sir... i have already check this t.code but same prob :(0

bikesh gautam replied Mar 23, 2012

use t .code mmpv. hope it will help you.0

meher nagadev replied Mar 27, 2012

Hi frnd, 

If it is not possible im MMPV, MMRV, go through table level update through 

debugging ..take abbar help, check which table is effected before that one 

..... 

Regards, 

Meher0

syed farooq replied Apr 13, 2012

Thanks, my problem has been resolved.