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

Diffrent Fiscal year Variant ?

Hello Friends

For the different company codes using the same controlling area must have same fiscal year variant.

But in my scenario 1 company code having period from jan to dec and another having period from April to march

Pls suggest me how we can do that?If not is there any otherway of solving this issue?

I need your suggestions

Thanks

Anup

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Sep 07, 2007 at 09:15 AM

    Hi,

    you are right, if you want to assign both company codes to the same controlling area, the fiscal year variants must be the same.

    Assuming that the following is required:

    - the company codes must have the specified fiscal year variants (legal reasons, or whatever)

    - the company codes must be under the same controlling area,

    you have the following options: first of all, because of this shared controlling area constraint, you have to assign he same fiscal year variant to both company codes. But, you can either set up a special purpose ledger (up to 4.7 the only option) or activate the new GL functionality and assign a ledger to your company code. The special purpose / new GL ledger can keep a different fiscal year variant then. So the legally required reporting can be made from the special ledger / new GL ledger, while the general ledger and controlling are using the same fiscal year variant.

    Hope that helps, points welcome 😊

    Csaba

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      you can contact me here in the forum, pls. I am checking in almost every day (not next Monday).

      If the documentation and my quick quide is not sufficient, do not worry. You can ask me (and other people) and, first of all, the SL is something like a standalone application. You can build it, and if you do not like it, you can delete it completely, without doing ANY harm to the main applications (FI, MM, etc.). Only thing that you should NOT do, is extending the coding block (you can see this IMG activity under the SPL config). But for your current requirement, that is not needed at all anyway. Anything else under the SL config you can try out and change back later, no issues.

      Hope that helps, points welcome 😊

      Csaba

  • author's profile photo Former Member
    Former Member
    Posted on Sep 07, 2007 at 02:25 PM

    Hi Anup

    I have gone through your requirement. I feel your issue can be solved in the following way through new G/L concept.

    To have common controlling you require a common FY variant. I am just taking your example and putting what can be the configuration to arrive at your solution.

    Assumption

    X Ltd: Indian operation

    Y Ltd.: USA operation.

    For both the company code take same FY Variant say Apr to March.

    Consolidation Currency: INR.

    Group currency: INR

    You should define a Non Leading ledger for preparing the Financial report for USA operation Co code with different FY variant i.e Jan to Dec.

    And the co code currency for USA Co Code: USD.

    The consolidation detail will be available in the leading ledger 0L which is defined by SAP and it is applicable to all company code created under the client. However the Non leading ledger will be defined with different FY variant which will help to prepare the Financial Report of USA co code(Y ltd).

    And your requirement of cross company controlling is also possible by following the leading ledger concept.

    If you require any further help or configuration doc. You can contact.

    Regards.

    Surendra

    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.