Skip to main content
Question

Clarification on Supplier Visibility and Company-Level Data Segregation

  • June 4, 2026
  • 2 replies
  • 33 views

 

We operate multiple legal entities within the same IFS database and have a business requirement that users of one company should not be able to access or view data belonging to another company unless specifically authorized. While this segregation is supported in many areas of IFS, we have identified concerns regarding Supplier management.

To avoid duplicate supplier records, we have implemented a validation that prevents the creation of suppliers with the same Tax Registration Number. As a result, a single supplier record may be connected to multiple companies.

We would like clarification on the following limitations and whether they are expected standard behavior:

  1. Company-Specific Supplier Restrictions

We have scenarios where a supplier should be available for procurement in one company but blocked from procurement activities in another company. Currently, we do not see a standard way to restrict supplier visibility or usage for procurement on a company-specific basis.

  1. Finance-Only Suppliers Appearing in Procurement

Some suppliers are created only for Accounts Payable and financial transactions and should not be available for procurement activities. However, once procurement-related information is maintained, the supplier becomes visible and available within procurement processes, creating challenges in enforcing company-specific controls.

  1. Lack of Company-Specific Registration History

Supplier creation information appears to be maintained at the supplier level rather than at the company-supplier relationship level. As a result, we are unable to determine when a supplier was registered or activated for a specific company, which creates audit and governance challenges.

Our users have raised concerns that suppliers associated with one company are visible to users of other companies within the same database. From a data governance and segregation perspective, they expect supplier visibility and usability to be controlled at the company level.

Could you please clarify:

  • Is supplier visibility across companies the intended standard behavior in IFS?
  • Are there any standard configurations, security settings, or permission controls that can restrict supplier visibility and usage by company?
  • What is the recommended approach for organizations that require strict company-level segregation while maintaining a centralized supplier master?
  • Is there any standard functionality to track when a supplier was registered or activated for a specific company?

We would appreciate your guidance on the recommended solution .

 

Thanks in advance.

 

2 replies

Piyal Perera
Hero (Employee)
Forum|alt.badge.img+12
  • Hero (Employee)
  • June 4, 2026

Hi ​@XitSivasJ,

When I do a cursor-assisted code/functional search for your second question, I feel that I can agree with the responses given. I hope these insights are beneficial to you as well.

Goal Standard approach

User must not see Company B supplier finance

User Finance – remove Company B

User must not buy from sites in another division

User Site Authorization

Supplier only valid in Company A

Set up Invoice/Payment/Purchase only for Company A

User cannot maintain suppliers at all

Role / permission set – remove supplier projections

Limit operational supplier analytics

Combination of company + site auth (e.g. Supplier 360)

There is no standard single parameter that hides a supplier master record from one company while leaving it visible globally; restriction is achieved by not connecting the supplier to that company plus user company/site authorization and projection permissions.

regards,

Piyal


Forum|alt.badge.img+3
  • Do Gooder (Partner)
  • June 7, 2026

Purchase tab in supplier is not company wise, this seems to be problem.