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

Segmentation

Hi all'

I am using SAP B1 2005 B and i had configured the system using Segmentation . I had configured multiple companiesin one database and now client wants a restriction at user level for all the accounts and master data.

Employee of one company should not view the accounts or master data of the other company.

Can any one help me out in this .

Regards

Nani

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 20, 2008 at 07:11 AM

    The answer is pretty clear to you already. If you put multi-company in one database, B1 can only treat it as one company. Therefore, you have to use SDK programming to reach your goal.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 19, 2008 at 08:11 AM

    User level authorization is possible only for Marketing Documents.

    It is not possible for Master Data.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 19, 2008 at 03:49 PM

    Hi Nani,

    Other than marketing documents which have data ownership authorization functionality, all other types data level authorizations have to be by SDK programming.

    Thanks,

    Gordon

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 19, 2008 at 06:32 PM

    Nani,

    I am wondering how have you done this -- " I had configured multiple companiesin one database "

    Traditionally in SBO, two companies would require you to set up two separate databases, meaning two separate CoA.

    If you have used the segmentation functionality (whihc is actually dimension based accounting, than multi co. accounting), I see a serious implementation flaw here. I am wondering, how is your account mapping running at GL account determination level ?

    Limited access to accounts can be done my making specific accounts confidential. Secondly, like others have said here, master data cant be really made hidden from users. But I think your problem lies in how you have implemented your solution.

    If you are not so late into the project, better give a fresh thought on your existing implementation.

    Cheers,

    Gautam

    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.