7 Replies Latest reply on Oct 26, 2011 12:26 PM by SH_INT

    trying to create a 13th month adjustment period

    KMacintosh
      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
        • 1. Re: trying to create a 13th month adjustment period
          631379
          Because those dates have no bearing on where the data goes in HFM, I would suggest using older dates, then manually overriding where they point to.

          12/31/1908 = Adj-2008 | ADJ | 2008
          • 2. Re: trying to create a 13th month adjustment period
            KMacintosh
            Ahh good idea. Thanks for the advice.
            • 3. Re: trying to create a 13th month adjustment period
              657263
              Hello,

              From an Auditing perspective inside of FDM this would not be a good idea. Since FDM is a Data Management software not an ETL.

              What you could do is shorten a period by 1 day, and then use that extra day as your 13th period. This way it can be referrenced accordingly and in a time-standard fashion.

              Thank you.
              • 4. Re: trying to create a 13th month adjustment period
                KMacintosh
                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.
                • 5. Re: trying to create a 13th month adjustment period
                  676575
                  This is an old post but I figured I'd chime in with how we overcame this issue.

                  We use the solution of using the last day in the month as the 13th period.

                  You can do this if you go to Administration -> Application Settings -> Period Key Date Format Mask

                  Change to something that accounts for days in the month. If you leave it as MMM YYYY, then you will get DEC 2008 twice. This can not happen. However if you change it to MM DD YYYY, you will get 12-30-2008 and 12-31-2008.

                  Problem Solved :-)

                  Just make sure that if you export and import the FDM application that you check this setting. Sometimes it does not transfer and you will have to change it before you will be able to import properly.
                  • 6. Re: trying to create a 13th month adjustment period
                    896245
                    Hi Richard,

                    But this problem still persists. we are using 11.1.1.3 and following the method described by you brings up "duplicate field" error. May be it doesnt allow value from same month to appear in the list.
                    • 7. Re: trying to create a 13th month adjustment period
                      SH_INT
                      All you need to do is make sure you check the Allow custom description in period option in the Configuration Settings. You can then enter your own unique Period description for your Adjustment periods and will not get the duplicate field error you currently get.