DP - Seasonality groups posting period conversion error
Hi,
I have recently configured Seasonality Groups which was released in APO SCM7 EHP2 with the Demand Planning Worklist. We are using posting periods (fiscal periods) in all planning books and background jobs,
The following notes have been implemented in our system: 1871842-1879577-1900933-1855921, and our latest APO support pack is SAPKY70204.
The following steps were successfully processed:
- Specify planning level
- Maintain settings for seasonality
- Create seasonality groups
However, the assignment of planning objects to seasonality groups generate an error when using period indicator P. It was successful with period indicator M. Here is a sample message from the short dump generated.
The following error occurred in system XXX : Period for date 0000.00.00 cannot be determined
The error occurred on application server XXXX and in work process. 8
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: /SAPAPO/MC_PERIODE_ZUM_DATUM of program /SAPAPO/SAPLMCP2
Function: /SAPAPO/MC_PERDY_GET of program /SAPAPO/SAPLMCP2
Function: /SAPAPO/DM_GET_COLS of program /SAPAPO/SAPLDM_DEMAND_PLANNING
Form: CREATE_COLS_FOR_PERKZ of program /SAPAPO/SAPLOO_TS_DM
Form: GET_COLS_FOR_PERKZ of program /SAPAPO/SAPLOO_TS_DM
Form: CREATE_COLS of program /SAPAPO/SAPLOO_TS_DM
Function: /SAPAPO/TS_DM_GET of program /SAPAPO/SAPLOO_TS_DM
Method: GET_HISTORY_COMBI of program /SAPAPO/CL_DP_SEASON_CONF=====CP
Method: GET_SEASONALITY_COMBI of program
/SAPAPO/CL_DP_SEASON_CONF=====CP
Method: GET_HISTORY of program /SAPAPO/CL_MDL_SEAS_PLM=======CP
I believe it is a program error, but I am wondering if anyone has any suggestions?
Thanks,
MZ
As per SAP, periodicity P is not supported.
Similar Messages
-
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.MayurHi,
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 -
ASKB error - Posting period 012 2009 is not open
Hi All,
We are using ECC 6.0 version.
We have posted an asset acquisition on 31st Dec 2008 in a Local Dep area with posting date 31st Dec 2009. Posting was made only in Local ledger and not in leading ledger.
It was a mistake from our side and rectified immediately on the same day by reversing the entry and reposted with posting date 31st Dec 2008
This issue is erroneous as posting period 12 2009 was open at the time of posting and later realized and has been closed.
Now, We are trying to run ASKB for all the assets in that Co.Code. But, System is blocking the entire log for processing. The Error being u201Cposting period 012 2009 is not openu201D
We cannot exclude this particular asset for this run and we cannot even open period 012 2009 for security reasons
Pls advise.
Thanks,
Pavan.Hi Pawan,
May be you can try posting with period 12/2009 opened. For security reasons, you can block the period for others and keep it opened only for a particular authorisation group and have the auth. group assigned to only one person who runs the transaction.
Regards,
Mike -
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..
ShivakumarOpen 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. -
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 AdministrationOK.
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 -
Error that "specify a value for variable posting period (single value entry
hi
My query is running testing fine in RSECADMIN under some username..but when i try and open it using analyzer (under same username) it gives me error that "specify a value for variable posting period (single value entry, mandatry)" it does'nt even asks to enter variable values and gives this error message.
However the same query appears to be working fine under different username.
plz advise.Hi Abhinav,
Just do one thing compare the Roles of two different users for which Query is getting executed and not.
Check the Object S_RFC.
Compare the Objects detail for Both the Users.
Please Assign points if useful.
Regards,
Rajdeep. -
Assign posting periods to authorization group in tcode S_ARL_87003642
Hello,
I want to restrict posting periods for some users. Therefore, I have created 2 functions associated to 2 authorization groups.
In transaction S_ARL_87003642, when I try to assign different posting periods to each authorization group to the same company code (Posting Period Variant) it appears a message saying u2018Target key must be different from source keyu2019.
What am I doing wrong? Do you know how can I restrict posting periods for some users?
Thanks and regards
Ana RitaDear,
You simply have to define authorisation groups in OB52 and assign this group to F_bkpf_bup in SU01 against user proflie as desired. Take basis help.
Regards -
OB52 authorisation group (close&open posting periods only for partic users
Dear FI-CO Guru's
In ob52- I want open postin periods
1)Certain group of user will allow for posting only normal periods
and
2) Certain group of users will allow for posting normal and special periods
this is our business requirement kindly suggest how can I maintain
Regards
GuruPrsadHi Guru,
If only a limited set of users is to be able to post in a particular
posting period, proceed as follows:
Add the posting period authorization (authorization object
F_BKPF_BUP) to the authorizations of the selected users. Assign an
authorization group (e.g. '0001').
Enter the account type '+' for the posting period variant to which
the restriction is to apply. Enter the period(s) whose use is to be restricted in the first period, those which are available to all
users in the second period, and the authorization group (e.g.
'0001') in the last column.
For this you need to consult with Basis people authorization matrix.
Regards,
Teja -
Authroisation group in posting periods
Dear Sapians,
Kindly help me in this issue
I have an authorisation group in open and closed posting periods(OB52), so that i am maintaining posting periods in INterval 1 as from 09 to 09 which is applicable for authorisation grouo users. in inerval 2 i am maintaining posting periods as 10 to 10 which is applicable for all, that means who doesnt contains the authorisation group.
But here the problem is the user who dont have an authorisation group is able to post in posting period 09.
kindly look in to this issue, it is very important for me.
And the user who is posting 9 th period can only post to some g/l accounts.
regards
T N RDear TNR,
Can you please list out the transactions which you are using, this because the object F_BKPF_BUP does not selected by all the transactions while executing the object is selected only for few transactions below.
AB01
ABCO
AW01
AW01N
F.80
F.81
FB05_OLD
FB09D
FB15
FB1S
FB21
FB41
FBA7_OLD
FBA8_OLD
FBB1
FBL4
FBRA
FBRC
FBU8
FBWD
FBWE
FOMZ
GB01
GB06
GB11
GB16
GJGB
GJGP
GP12
GP13
WLFN
Regards,
SANDEEP -
Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed RoshanThank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan -
Error in Opening Posting Period in MM
Dear Gurus,
I am facign an error when i am opening a posting period in MM. In MMPV, when i open the Period and execute system displays the following error message:
Client 300
Period Entered : 112009
Log
ABEND
MMPV_Date_Check Error Occured (See note 1082841)
Transaction MMPV (period closing program) cannot be executed . For more infomation see note 1082841.
Kindly provide me with the solution .
thanks in advance....Below is straight from the OSS note. You need to set the parameter id MMPV_READ_NOTE to current date for yourself or change the number of days in CKMLMVADMIN-KDATA to 999 (for example) and then you will be able to do. Probably better to set the parameter id for yourself and suitable colleagues only:
This note provides a feature to prevent using MMPV to shift into a future period. This feature is activated automatically after implementing this note and works with our without Material Ledger active. MMPV can continue only if the new period is within 10 days (by default but is configurable) away from the current date in the system. Otherwise, it will terminate and no change will be made.
To disable this feature, you must set parameter ID MMPV_READ_NOTE with the current date in the user parameters in form YYYYMMDD (Y = year, M = month, D = day).
To change the number of days to a value other than the default (10 days), set the following entry in table CKMLMVADMIN:
KKEY : MMPV_NUMBER_DAYS_ALLOWED
KDATA : <number of days MMPV is allowed>
Only integers are allowed, with 0 meaning MMPV is allowed only on or after the first day of a new period. If the value is greater than the actual number of days in a period then it means MMPV is allowed for the entire month. Any invalid entry in the KDATA field will be ignored and the default value will be used.
Regards,
Nick -
Error in document date & posting date-- Posting period 001 2008 is not open
hi guru's
while doing vendor creation in XK01, i m not getting the data screens like address, ..etc.i m getting error..posting period not open". what does it mean..
What date i need to give in both fields...?
can anybody send a set of data for me to create a vendor to test for my bdc/lsmw?
can any help me step by step vendor creation in xk01,
I am getting this below....
Posting period 001 2008 is not open
Message no. F5201
Diagnosis
Period 001 of fiscal year 2008 is not open for posting for the variant of posting period 1000.
System Response
Processing cannot be continued.
Procedure
The error can have several causes. In order to eliminate the error, proceed as follows:
1. Check whether the posting date was entered correctly. The system determines the posting period by means of the date.
2. Check whether the required posting period is open for posting for the variant of posting period 1000 and account type +. Make sure that the period is open for posting.
To do this, specify a period interval in which the required period for the variant of posting period 1000 and account type + is contained.
Proceed
thanksHi
Kris is right, that message means you can't post a FI document in the period 1 (probably Gennuary) of the 2008, but this can't mean you can't create a new vendor.
So are you sure on trx?
If the trx is right perhaps somebody has inserted a control in a user-exit.
Max -
Error saying 'Posting period 000 is not defined for fiscal year variant K4'
Hi All,
When I try to add a new entry in the transaction OB52, I get an error message saying 'Posting period 000 is not defined for fiscal year variant K4'. The entry that I add is,
Variant : 0001
Account Type: +
From Period : 1
Year : 1995
To Period : 12
Year : 2010
From Period2 : 13
Year : 2000
To period2 : 16
Year : 2010
Please let me know what customising needs to be done to solve this issue.
Thanks a ton.
Best Regards,
JeffHi,
Hava you checked in OB52 screen, by default 0001 posting period variant will be there for +, A, D, K, S account types.
If it is already existed in your OB52 screen, you won't create one more record with the same name. You have to edit the existing 0001 posting period with new values.
Thanks
Chandra -
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 -
Hi Experts,
We are not able to create posting period of 2014-15 as we are getting this error.
Enter Valid code,Tax Definition [Message 173-36] error .Please find the enclosed error screen shot for your reference.
Regards
KMJHello KM Jayaprakash
I have the same problem, but i dont see (know) the screen which i can check "Advanced G/L account determination check box". I am in SAP B1 9.0 PL15. Please can you publish a screen shot.
it's urgent please.
Thanks
Maybe you are looking for
-
Adobe Pixel Bender Plug-In for Photoshop CS5
Can the Adobe Pixel Bender Plug-In for Photoshop CS5 be used in Photoshop CS6? And, more specifically can it be used with Windows 7 operating system?
-
Are there any good drivers that finally allow a Mac user to take advantage of this equipment's capabilities?
-
Hi all is there a way to map a XML file to PDF Thanks
-
HT1343 can a single key be used to delete text in a word document?
when using mbair, can the keyboard be set up to have one key only delete text?
-
How do i make word open at 150% every time
how do i make word open at 150% every time