Diffrent Fiscal year Variant ?

[Former Member]

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

[former_member581986 · Accepted solution]

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

[Former Member · Accepted solution]

Hello Csaba

I am using version 6.Bothe company codes are diffrent .one in US and One in India

Is there any other way we can maintain the same ( except SPL)

If we are going for diffrent Controlling area,how we r going to consolidate them ?

What are the disadvantages in the above said case?

Pls suggest me .Can u guide me in SPl configuration if possible

Thankx for ur Sugesstion

ANup

[former_member581986 · Accepted solution]

Hi,

I can guide you in SPL config, that's not the problem.

If you want to create different controlling areas, then this may have some (dis)advantages, depending on your business concepts and requirements. In fact, to report on separate controlling areas is a bit more complicated as usually all reports within CO are for a single controlling area only. Also, you won't be able to allocate costs between controlling areas (cost center in controlling area US cannot allocate cost to cost center in controlling area IN, for instance). Again, this may be an advantage or a disadvantage for you.

A separate ledger (either spl or a ledger in new gl) is another way to resolve it by keeping the common controlling area. I assume you have a group with a specific fiscal year variant here, but there are some legal regulations to have another fiscal year in a given country. So the "only" issue is to enable statutory reporting based on the local fiscal year variant while the group should operate on the fiscal year variant of the group. Both SPL and NewGL can offer reliable solutions for that requirement.

Hope that helps, points welcome

Csaba

[Former Member · Accepted solution]

Hello Csaba

Thanks for the advice

canu guide me in onfiguring SPL? any doccumentation for reading and getting an idea and configuration doccument if possible

Can u give me ur mail id to contact

Mine in anupppanda@gmail.com

It would be really helpful

Regards

Anup

points are assured

[former_member581986 · Accepted solution]

Hi,

the best documentation is the <a href="http://help.sap.com/erp2005_ehp_02/helpdata/en/da/6ada3889432f48e10000000a114084/frameset.htm">online documentation at help.sap.com</a>

From your point of view, the most important things are:

1. Define a table group in transaction GCIN. Include all fields in object table 1 that you want to report on (with the different fiscal year variant). If this is a legal requirement as I suppose, then you probably only need the GL account (RACCT) field. You may require other fields as well, depending on your requirements.

2. After the table group is defined, you have to check and install it. Installation means here the new table group is added to the Special Ledger environment, i.e., it is added to many customizing tables + lots of standard ABAP code is regenerated.

3. Now you can create a ledger for your new summary table (this is one of the 4 or 5 tables in your new table group). in transaction GCL1. You should assign the company code where the alternate fiscal year variant must be used to the new ledger. Obviously, you should change the fiscal year variant in the assignment screen to the alternate one (the default would be tha FYV that you have assigned to your company code in OBY6 , this is the controlling area's FYV as well).

4. Then you have to asign "activities", or "business transactions" to the ledger/company code combination. Use the button "Activities like GL" here to make sure all relevant items are transferred to your ledger. That would be about 30 activities. Each of them require a "field movement rule" assigned, but the same rule can be used for all, so you have to create it only once. The best way to do it directly from here (you are still in GCL1), by clicking F4 and when the message comes, no entries found, you can start creating it. The field movement rule is nothing else than the rules how fields of the original (FI, MM, SD) documents are transferred to the fields in your FI-SL table. You can check out the proposal button here. RACCT should be populed from HKONT, the rest is I think obvious.

Back to GCL1, you have to set the posting indicator for each activity (business transaction) to 3. This makes sure online data transfer and subsequent data transfer both are possible.

5. Save your work.

6. Then you can start transaction GCU1 and take over all documents available in FI to your special ledger (if you have some postings already) . Or you can post a new document and check if it was transferred (it should). Example: in FI (fiscal year variant April to March) you post a document with posting date 01.April 2007. This is period 1 in FI then. The same document is transferred for period 4 in the SPL.

7. You can use the Report Painter / Report Writer tools to report your data. ALso you can consider report RFBILA10, which is almost the same as well-known RFBILA00, only that it can display data from a special purpose ledger.

Hope that helps, points welcome

Csaba

[Former Member · Accepted solution]

Hi Csaba

Thanks for the notes

Will it be sufficient to understand and configure my issue?

I hope it will do that.

Pls be in Touch

Can i have ur mail ID pls !

mine is anupppanda@gmail.com

If any issues comes i will contact you

Rgards

Anup

[former_member581986 · Accepted solution]

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

[Former Member]

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

[Former Member]

Hello Mr.Patra

Can i ve ut mail ID pls.

I may requre some clarification on this.

Ur advice is very helpful

I hop ethere i sno issue in giving ur mail ID

Anup

Anupppanda@gmail.com

[Former Member]

Hi Anup

You can contact me in my company id.Surendra.patra@capgemini.com

Regards.

Surendra