Financial Statement Version

[Former Member]

HI ALL

I had a small issue with financial statment version

Endusers were creating GLs in PRD system, but if we want to see them in FSV, the GL should be created in DEV system also...right? so iam not able to find out which GLs in PRD were not assigned to FSV, hense PRD is not modifible.Those GLs created by users, has to be maintained in DEV in accordance with updating FSV. So i want to know is there any function to syncronize PRD and DEV for tables like CDCLS, SKA1, SKAS, SKAT and SKB1 ?

I mean to say that DEV system should refresh with PRD data for the above said GL tables.

Please give your valuable suggestions to fix this issue.

I will assign points as well..

SRINU

[Former Member · Accepted solution]

You will have to set up a distribution model (ALE) for distribution of master data between systems (http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp). Also, in FSV, do not assign individual accounts to the nodes; assign a range of accounts so that whenever a new GL account is added, you do not need to change your FSV.

[Former Member]

We opened up production to allow maintenance of FSV there and extended ALE to enable sending FSV to Dev and QA. Look here.

[Former Member]

HI ,

if the user creates GL in the production system it will not reflact in the Development sysytem.so if u want that GL in the Development system you must create it in the Development system.

To find which GL are not assigned the FSV you go the transaction code S_ALR_87012284 (Balance sheet/PNL statement)and check the Production system all the GL which is created new or not assigned to any group will appear under Accounts not assigned in the output for that perticularFSV.

you can create these GL in the Development system and add these GL to the FSV in the Development and create transport request and transport it to PRD.

Hope this will help you

Regards

Manohar

[Former Member]

Hi,

Please assign those g/l acount to fsvs.

Pleaseassighn the points that is helpfull.

Regards,

Bramha

[iklovski]

Hi Srinu,

I will suggest you a different approach. You may consider making FSV changeable in the production system. I always recommend this to my clients as the maintenance of FSV does not differ from a maintenance of cost centre hierarchy or other groups from functional point of view. By doing so, you will save you and your client time and avoid CR on every minor change in FSV. To do so, you should implement the note 200674.

Otherwise, as suggested before, use the ALE - it's the most efficient way to transfer master data between the systems/clients.

Regards,

Eli

[Former Member]

Eli, as you suggested, my client wishes to enable changes to the FSV in the Production system. In addtition, the client wishes to ALE, or copy in some other fashion, the account group hierarchy contained within the FSV, to lower development environments on a scheduled basis (daily). I have not been able to find a standard ALE to allow this. We already have ALEs set up for GL accounts, cost centers, profit centers, and various other types of master data. But so far, have been unsuccessful in ALE'ing the account group hierarchy. Might you have any suggestions for this problem?

Regards,

Shawn