SAP Financial Consolidation is a very powerful tool for managing financial data but it could also seem very confusing for beginners due to its high customizability.

A very common question is “Why can’t I input data in the package?” The answer: There are about a dozen settings that are involved.

This blog tries to list all the possibilities that prevent you from entering package data in a report, mainly from four aspects: Category Builder, Security, RU Organizer and Package Manager

 

Category Builder contains hundreds of settings so let’s focus on the ones that have a say in whether or not data entry is allowed.

Category Builder – Options Step – Restrictions Tab

CB-Options.png

Here you can define the read-only flow(s) and read-only periods. So in the example above, the amount for flow F00 will be read-only if there
is an opening balance.

The Data entry restrictions define in general which data is selected for entry, it can apply to package amount as well as journal amounts.

DataEntryRistriction.png

Please note that these settings on the Options Step- Restrictions Tab in Category Builder are only default settings for the associated Reporting IDs and Reporting Unit Organizers. So be sure to check these objects too.

RID.pngRUO.png

Category Builder – Flows Behaviors Step

CB_Flows_Bahavior.png

This step manages the flows behavior on each account family, which are defined in the Account Families step.
Find your Flow/Account Family combination and make sure “Authorized in package schedules” is checked.

“Authorized comment” allows you to put comments on the amount.

  

Category Builder – Dimensional Analysis Step

CB-DA.png

With proper dimensional analysis, you can breakdown your data input to a certain level.

In the example above, you’ll be able to input data for at the AN level {AC=A1110; FL=F00; AN=XXXX}, but the amount for {AC=A1110; FL=F00} is
calculated automatically (as breakdown total) so it would be read only.

Category Builder – Formulas Step

Similarly, if a formula is in place to calculate a certain value, this value would also always be read only.

CB-Formulas.png

Security

Administrators have unlimited access to the application but for standard users, there are restrictions.

user.PNG

User himself has to have certain access right to see and edit data.

This is managed in functional profiles. Check that the user functional profile has the necessary access right, here is an example of one who has access to see and modify package data.

FP.png

There are also circumstances where only a certain range of the data is visible to a certain group of users.

This is managed by Data Access Group.

DAG.png

In this example, the user is not able to edit the amount for accounts other than A1111.

If Data Analysis Access is also set to DEAA then he wouldn’t even be able to see the amounts for accounts other than A1111. He would see blank data instead.

RU Organizer – Roadmap Tab

Roadmap restricts access right to a specific package (generated by the associated RU Organizer)

RUO_NoAccess.pngRUO_Lv1.png

If you are set to No Access, or if you are at a lower level, you’ll see this error when opening the package.

NotAuthorized.png

Package Manager

If the package is protected or locked, you’ll see this when opening it.

/wp-content/uploads/2015/04/locked_686454.png

And of course if you checked the Read-Only option on the FC desktop
then you open everything in read-only mode.

/wp-content/uploads/2015/04/readonly_686455.png

Having checked all these settings above, you should now be able to open the package in read-write mode and see the data you wish to modify with a nice little blue triangle right in front of it.

/wp-content/uploads/2015/04/editable_686456.png

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply