Skip to Content
author's profile photo Former Member
Former Member

Fiscal year variant not maintained for calendar year

Hi All,

We are currently doing some test extraction in ECC for some SAP standard datasources and two of them (0PM_PRM_PLCS_1 and 0PM_PRM_PLCS_2) are both encountering the same error below:

"Fiscal year variant BC is not maintained for calendar year 1900"

We have checked in OB29 transaction and this particular fiscal year variant and calendar year are both maintained.

Are there other transactions or table/s that we need to check that could help resolve this issue?

Thanks in advance!

Best regards,

Helene

Add a comment
10|10000 characters needed characters exceeded

Related questions

6 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 08, 2014 at 09:14 AM

    We have resolved the issue by applying the solution mentioned in Note 6556. By beginning the maintenance of the fiscal year one year earlier in OB29 transaction.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 22, 2014 at 08:35 AM

    Hi,

    If your seeing those values at your source system then same values need to be transferred into bw by using transfer global settings options at Bw Tx - RSA1---> Source system.

    Check the table at source and target servers. Table - T009 for fiscal year variants.

    You can check other tables T009B,T009C and T009Y.

    Source and target system need have same values.

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 22, 2014 at 07:56 AM

    Just "Transfer Global Settings" on your Source System in RSA1.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 22, 2014 at 08:28 AM

    HI Helena,

    select your source system -> right click -> global setting -> select the Fiscal year variants -> use different modes

    Thanks,

    Phani.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 23, 2014 at 12:38 AM

    Thanks for responding to our inquiry. Unfortunately, even after performing the "transfer global setting" we are still encountering the error.

    We also checked the T009 and other related tables (T009B, T009C and T009Y) and the data are matching in both BW and source system for this particular fiscal year variant.

    In any case, do we really need to check the dependencies of the tables in BW even if we are only performing the test extraction in the source system? Shouldn't we check them only when we actually execute the infopackage in BW and encounters the issue there but not in the source system? (Assuming that the datasource is executing perfectly in the source system but not in BW).

    Pls note that we are experiencing the error in the source system level via RSA3 transaction so BW setup shouldn't be related to this yet.

    Thanks and BR,

    Helene

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 16, 2016 at 06:46 PM

    This message was moderated.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.