Trying to create a 13th month adjustment period

Question

Hi all,
I am trying to setup a 13th month in fdm (the HFM application has a end of year adjustment period). I'm hitting difficulty as fdm wont let me have 2 load periods in the same month range (as far as i can tell) and I cant leave the date range blank. Has anyone successfully dealt with this before?
Previous attempts have lead to "invalid period" then "cant delete period" issues. The FDM app also has multiple adapters (HFM and ESSbase) to complicate the issue.
Thanks

Answer 1

Just to provide feedback,
The period shortening solution does not work in FDM 9.3.1. The error log and control table inputs of the attempt (screenshot wont attach unfortunately) are included below.
------CONTROL TABLE INPUT-----
| PERIOD | PRIOR DATE KEY | TEXT DESCR | TARGET PER(M) | .... | .... | .... | .... | YEAR TARGET |
> | 6/29/2003 | 5/31/2003 | <Sys generates> | JUNE | | | | | 2003 |
> | 6/30/2003 | 6/29/2003 | <Sys generates> | PERIOD13 | | | | | 2003 |
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><!--[if gte mso 9]><xml>
Normal
0
false
false
false
MicrosoftInternetExplorer4
</xml><![endif]--><!--[if gte mso 9]><xml>
</xml><![endif]-->
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;}
</style>
<![endif]--><!--[if gte vml 1]>
<![endif]-->
*&lt;Sys generates&gt; fields can only be modified using table editor after created as far as i am aware....
-------ERROR LOG---------------------
** Begin FDM Runtime Error Log Entry [2008-11-18-11:22:03|http://forums.oracle.com/forums/] **
ERROR:
Code......................................... -2147217873
Description.................................. Duplicate key found, Insert/Update failed.
ORA-00001: unique constraint (FDMDEV.IX_TPOVPERIOD_PERIODDESC) violated
Procedure.................................... clsDataManipulation.fProcessRecord
Component.................................... upsWDataWindowDM
Version...................................... 931
Thread....................................... 2892
IDENTIFICATION:
User......................................... monrojam1
Computer Name................................ PBAUEBHY03
App Name..................................... oldfdm
Client App................................... WebClient
CONNECTION:
Provider..................................... ORAOLEDB.ORACLE
Data Server..................................
Database Name................................ hypd
Trusted Connect.............................. False
Connect Status.. Connection Open
GLOBALS:
Location..................................... CONTROLSREVIEW
Location ID.................................. 730
Location Seg................................. 1
Category..................................... WLCat
Category ID.................................. 12
Period....................................... Nov - 2008
Period ID.................................... 30/11/2008
POV Local.................................... False
Language..................................... 1033
User Level................................... 1
All Partitions............................... True
Is Auditor................................... False
** Begin FDM Runtime Error Log Entry [2008-11-18-11:22:03|http://forums.oracle.com/forums/] **
ERROR:
Code......................................... -2147217873
Description.................................. Duplicate key found, Insert/Update failed.
Procedure.................................... RSMarshaler.PutToStreamAndUpdate
IDENTIFICATION:
User......................................... monrojam1
Computer Name................................ PBAUEBHY03
App Name..................................... oldfdm
Client App................................... WebClient
CONNECTION:
Provider..................................... ORAOLEDB.ORACLE
Data Server..................................
Database Name................................ hypd
Trusted Connect.............................. False
Connect Status.. Connection Open
GLOBALS:
Location..................................... CONTROLSREVIEW
Location ID.................................. 730
Location Seg................................. 1
Category..................................... WLCat
Category ID.................................. 12
Period....................................... Nov - 2008
Period ID.................................... 30/11/2008
POV Local.................................... False
Language..................................... 1033
User Level................................... 1
All Partitions............................... True
Is Auditor................................... False
The first solution involving creating the adjustment period in an extrapolated date range (e.g. 5\31\1950, 6\30\1950) does work - with issues. Doing this will allow you to upload data into the adjustment period, but may cause tpov violations in batch load processes.