Field posting period is not a document property

Hi Team
We are attaching comment for every manual adjustment.
While one of the user posted entry in the pervious preiod and upload comment also.
Now in this month he did some changes in comment file.
After that he try to see the attachment for manual adjustment posted are not visable and it shows message "Field posting period is not a document property".
Please help me how to fix this.
Regards
Madhu

Hi Team
Thanks for you support.
Issue was solved
Regards
Rajesh

Similar Messages

Production order creation - posting period is not open

Dear All,
Could you please explain me what the impact on CO/FI is when I create a production oder? Indeed, the posting period is not open in OB52 but I am wondering why the System issues this message when I use CO01 or CO40.
Thanks
D.

Hi d,
Whenever a production order is created or converted to planned orders, each of these orders carries some activities
which are linked to cost elements in CO and GL accounts in FI. The system gives you an alert that if posting periods
are not open you cannot settle the production order. If production order is pending that results in Work in progress
which carries gl accounts relevant to be posted in the particular period.
Regards,
Sadashivan

Error: "posting period is not defined for fiscal year variant" in FBICS3

Hi,
I got error "posting period is not defined for fiscal year variant" when I execute t code FBICS3.
I checked in OB29 & t code FBIC010 & noted that the fiscal year variant had ben maintained.
Please advice.

HI,
It was noted that the mentioned t code had been maintain but below mentioned error appear:
Posting period is not defined for fiscal year variant
Message no. GU506
Diagnosis
You have tried to determine a posting date in fiscal year variant for period , fiscal year , but this period is not defined for the variant.
Procedure
You maintain fiscal year variants in table T009.
It was referring to t code OB29. I have checked the detail, in OB29 also details maintain.
Please advice why the error still prompt.

Field 'Contract Period' does not exist in definition for business component

Hi everyone
I create a Field "Contract Period" in BC "Quote" with an extended table and put it in the applet view "Quote Full Form Applet" the field works fine in the view, we can update and insert information in it and shows perfect in the database also.
Our problem is when create a Integration Object for reports in BIP Reports the system said something like this when we try to generate the sample data:
ObjMgrLog     Error     1     0000002d4cd016bc:0     2010-11-02 13:18:39     (adptutils.cpp (5715)) SBL-EAI-04376: Method 'FieldValue' of business component 'Quote' (integration component 'Quote Template') returned the following error:
"Field 'Contract Period' does not exist in definition for business component 'Quote'.
We compiled the BC and the IC, and did the Deployment of the IC in Tools but it didn't work, the thing here is if I remove this field the report works fine. Is there any other component or Object that we have to compile to get Siebel recognition?
Any ideas?
Thanks in advance
Edited by: user7286211 on Nov 2, 2010 8:05 PM

To do the same change with the transaccion FB02 y FB03, create an enhancemente point in the program: SAPMF05L dynpro: 1301, module: DYNPRO_MODIFIKATION, at the of perform open_fi_dynpro_mod and write:
LOOP AT SCREEN.
IF sy-tcode = 'FB02'.
    IF screen-name = 'BSEG-HKTID'.
      screen-input = 1.
      screen-invisible = 0.
      screen-active = 1.
      screen-output = 1.
      screen-group4 = ' '.
      MODIFY SCREEN.
      EXIT.
    ENDIF.
elseif sy-tcode = 'FB03'.
      IF screen-name = 'BSEG-HKTID'.
      screen-input = 0.
      screen-invisible = 0.
      screen-active = 1.
      screen-output = 1.
      screen-group4 = ' '.
      MODIFY SCREEN.
      EXIT.
    ENDIF.
endif.
ENDLOOP.
and, all ready.

Posting period is not open

Hello folks,
I am trying to PGI a delivery against an STO.Though the posting period is current, system throws an error "posting period XXXX is not open"
Before this I ran MMPV to make sure the posting period is current.
Please advise.
Edited by: rksap193 on Jan 29, 2008 10:04 AM

Hi,
Just chek MMRV & what's the Current Period ..?
What's the period with MMPV..?
Regards

Posting Period error in delivery document

Following data in OMSY Screen
Co Cd     Company     Year   Pe     Fyr     LM     Fyr     LM
9001     L                   2007   3     2007     2     2006     12
Following data in MMRV Screen
Company Code    9001   L
Current period                03 2007
Previous period              02 2007
Last period in prev.year 12 2006
Please let me know if we can post goods in month of June as this is 3rd month in Fiscal Year.
I am getting following error message.
Posting only possible in periods 2007/03 and 2007/02 in company code 9001
Please let me know what year format it is following & how to follow financial year method.
Regards,
GHS.

According to the data you have provided u are using V3 - fiscal year i.e. Apr - Mar.
Followed by India and some other countries.
As far as your error solving is concerned, please check the date for which you are posting. May be it is in the future 4th month (i.e. july for V3) probably. That is why the system is giving in the error. If you change the date to june then the problem will be solved.
Hope the answer help you.
Regards
AK
Please reward points if helpful

Exit for to restict Non-leading ledger posting periods for Document Type SA

Hi,
Please give the guidelines to complete the following requirment.
In SAP FI two ledgers Leading(0L), Non-Leading (J2) Posting periods are defined in OB52.
If non-leading ledger is closed also it will take the Leading posting periods and Posting the document..
This is the SAP Behaviour.
Like in FB50L if we enter J2 (Non-Leading) it will display the erro message like
Posting period in not open.
Like that they want for FB70,FB75,MIGO,MIRO,FINT and Invoice(VF01).
Please suggest the suitable exit.
Thanks & Regards,
Padmaja.

Hi Ramu,
Please refer the below points,
1. Leading ledger is only one ledger in one client.
2. In one client you can keep N of non leading ledgers.
3. company codes are need assign to non leading ledgers.
4. All postings will update leading ledger by default.
5. Non leading ledgers will update if company code is assigned to non leading ledger.
6. If you want to post only non leading ledger then please use the tcode FB50L and FB01L.
7 You can set the separeate fiscal year variant for non leading ledger.
I hope above information will resolve you r issue.
Regards
Madhu M
http://wiki.sdn.sap.com/wiki/x/JghNCw    (NewGL Migration Secnarios)
http://wiki.sdn.sap.com/wiki/x/mosOD     (Document Splitting Wizard)
http://wiki.sdn.sap.com/wiki/x/f4OfDg    (NON-LEADING LEDGER SPECIFIC
                                                              POSTING)

FB01 Posting period not open

Hi,
I am an abapper, i am trying to check a BDC for the transaction FB01, in the first screen i get the error message "Posting period <year> not open" Can any body tell me how to find out the correct data to be given in the respective fields.
Regards
Narendiran

hi.
I am working on ECC 5.0 sand box-IDES
IN OMSY, my current period is 09 and ABp indicator is flagged.
In OBY6 i have the variant as 0001.
In OB52, for variant 0001, for one of the account assignment, i have
" From Period 1 Year 1996 To period 12 1999 From Period 2 13 Year 1995 to period 16 1995"
How do i make the FI posting current the FY 07 untill 9999?
Because when i try to change the Year as follows
" From Period 1 year 1996 to Period 12 9999 From Period 2 13 Year 1995 to period 16 9999". i get the following " Error" Message.
" Posting periods should not be opened"
Where can i change the setting from " Error" to " Warning" or how do i make the changes in FI to make it current to year 2007.
Due to this , i am unable to do Goods receipt since when i do MIGO, i get the error message " Posting periods not open"
Much appreciated for your response.

ASKB - POsting Period not open problem

Hi All,
I saw many threads on this problem but not got suiatable solution thats why i am raising this thread again.
Due to some problem my client not Run ASKB for October period, now when he is trying to run ASKB for November month he is getting error that 'Posting period is not open'.
Now we cannot open 'Posting period' 'October' because of some organizational issues.
Kindly suggest me how i run ASKB for 'Current month.
Regards
Sandeep

Hi Sandeep,
To my regret, is the answer here is definitely NO.
A reconciliation of the system would be not possible (For example, in foreign currency and a parallel currency).
This source of error was stopped by switching from batch input sessions to the Direct booking with RAPERB2000. (With batch input sessions it was possible to manipulate).
Furthermore, the values in the periodically posting areas have to be posted into the correct period.
If the reconciliation is not relevant, you can check via testrun which values have to be posted and post them via FB01. In this case you have to manipulate also the table TABAS and T093D. But take into acount that this is on your own risk and will not be supported by SAP.
My personal opinion: Open the periods and run the RAPERB2000 regular.
Regards Bernhard
Edited by: Bernhard Kirchner on Nov 29, 2010 12:54 AM

How to activate the option posting period for T.code F.2E

HI All,
When we execute T.code F.2E the selection parameters available are
1. company code
2. partner company code
3. open at key date
4. display currency.
As the program documentation says we can reconcilie by selecting option for posting period in F.2E
Below is the SAP documentation on the program.
You use the Posting period selection option to specify the time period in which the posting dates of the documents need to fall in order to be included by the program. Open items, cleared items, and payment documents are all selected. See the section Parameter Open for key date and Selection Option Posting period for further information. If you want to start the program with this date selection, the option must be selected accordingly.
But the field for posting period is not available in selection parmeter, we are on 4.7 EE version.
Please let me know how to activate the option for posting period in selection parameters for T.code F.2E
Thanks in advace.
Regards,
Raj.

Hi,
I have tried to execute the program FBICRC003_DATA_REC. But program doesn't exist.
We are on 4.7 version. I have executed program RFICRC00, but stil can't find the option posting period.
Please confrim.
Thanks
Regards,
Raj.
Edited by: Raj Racha on Dec 27, 2010 10:58 AM

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

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

Posting period variant authorization

Hi
We have a issue with posting period variant authorization. Say for example we have 4 company code and 4 posting period variants and we want to restrict one particular user should have authorization to open and close for one posting period variant only. Because mistake other company posting periods are getting opened. so as we have one posting period variant for one company, we want to restict one particular user responsible for one particular posting period variant not for all OB52 transaction code. Please advise how to achieve this.....
Regards
Padma

Hi
I am not finding any thing called authorization field in OB52, where it is? please advise..
Padma

Network confirmation cancell. thru CN29,when past posting period isnot open

Hi Gurus,
I have one query regarding netowrk confirmation. In our scnario, we are confirming network activity/element directly through CN27. Now after confirmation, due to some mistake we are trying to cancel that confimration through CN29 but system gives me error that "posting period is not open". As my network confirmation was done in the month of March'10 and i am trying to cancel it in April'10 that's why system is not allowing me to canel the confimration.
Now my query is that how to cancel the network confimmation without opening past posting period. I looked into the configuration for network confirmations but there is no setting available to allow cacellation of network confirmation done in posting period which is not open now.
however in CAT5, we have a option where we can enter cancellation posting date, and system allows to cancel time postring for that period also which is closed now (by putting cancellation posting date belonging to current posting period wihhc is open).
regards
Alok Mittal

I have not verified the same on system, but It's quite good observation. I think it's standard behavior in system and could be possible, in CN29 you are not having option to put posting date, so, system is taking date of posting date on which it got posted for reversal. i.e. March 10, but period is closed for that date. so, system is giving you error that period is closed.
Now coming to CAT5 if you give posting date of March 10, and try to reverse this document system will give you same error of period close. but if you give posting date of period April 10 system will allow to post. Because current period is open. Reversal program works in SAP based on some logic for different documents.
If you wanted to check why system is behaving in that way in that case, compare both documents ( original posted and reversal document posted in CAT5, check after posting reversal document is there any change done by system to original documents , I understand mostly system put reversal tick mark or so, in original document and give reference document in new documents )
Please check and revert back.
With Regards
Nitin p.

Posting period of "Depreciation Posting Run" problem

Hi all,
I was configured my company code with 12 period of nomal fiscal year (defauld fiscal year variant K4). I think Posting period field of Depreciation Posting Run screen (T-code: AFAB) must have 12 posible entries, are 1,2,3,...,11,12. But when I display posible entries of this filed, it only have to posible entries (000-000, 000-365). So that, I can't choose a period to excute real depreciation run.
How to define posible entries 1,2,3,..,11,12 of posting period field of Depreciation posting run screen?
Chinhvh

Hi,
If I have understood your question correctly
When u do F4 in field "Posting Period" in AFAB you get the following screen:
From            To
000               000
000               365
You don't do F4 in that field. Since your Posting Period Variant is K4, just manual input the relevant posting period in the field. i.e if you want to post depreciation for April then just input Period 4 in the field.
Now what you have to be careful is which depreciation method you are going to select for doing the Posing Run. (i.e the Reason for Posting Run fields)
You have 4 methods which is described below:
1. Planned Posting Run. (This should be done if all the depreciation upto the earlier posting period has been done properly under the planned posting run).
If you have done unplanned run for earlier periods and have never done a planned posting run for the earlier periods for the concerned asset, then you cannot do planned posting run for period 4 directly. You should first do planned posting for period 1, then for period 2, then for period 3, and then finally for period 4. The depreciation will be zero for Posting periods 1,2,3 if your start depn in your asset master is 1st April.
2. Repeat Run: You can use this to do repeat run. You can do Planned depreciation run only once for a particular asset for a particular period. You can then do a repeat run for doing the depreciation run for the same asset.
3.I don't think you wll need to do Restart run.
4. You can do unplanned depreciation run directly for period 4, if you have not done the depreciation run for the particular asset for the earlier period. but this is not recommended. This should be done only in specific circumstances when you have no chance of doing either planned depn run or repeat run.
Pl assign points.
Rgds
PRasad

Field posting period is not a document property

Similar Messages

Maybe you are looking for