Skip to Content
0
May 10, 2010 at 03:59 PM

BPC 7.0MS Logic - Using NEXT(12) - Works fine except for december

17 Views

Hi all,

I have a logic where I use TIME=NEXT(12) in order to save current year data to next year data. It works fine except for December.

Here is the script:

*REC(EXPRESSION=%VALUE%,TIME=NEXT(12),DATASRC=INPUT,CATEGORY=BUDGET)

Here is the generated records:

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.JAN,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.FEB,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.MAR,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.APR,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.MAY,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.JUN,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.JUL,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.AUG,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.SEP,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.OCT,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,2010.NOV,-42

LC,80300_PROV,BUDGET,INPUT,06100141,830060811,GA070,,-42

No time member is defined in the last row.

any idea? Which parameters define the next members, ie how it determines that NEXT(1) of 2009.MAR is 2009.APR?

thanks for your help,

Romuald