Person EITs for Redwood Add Person flows

Enhanced Add Person flows allow you to enter Person Extra Information Types (EITs), also known as Extensible Flex Fields or EFFs, while using these Redwood flows:

  • Hire an Employee
  • Add Contingent Worker
  • Add Pending Worker
  • Add Nonworker
  • Convert Pending Worker
  • Edit Pending Worker

Person Extra Information Types (EITs), also known as Extensible Flexfields (EFFs), offer several benefits in applications like Oracle Cloud and E-Business Suite. These flexible data structures allow businesses to capture, store, and manage additional custom data beyond standard fields. Here are the key advantages:

1. Enhanced Customization

  • Allows organizations to extend standard tables with additional attributes without modifying core applications.

  • Enables tailored data capture for specific business needs.

2. Flexibility & Scalability

  • Supports dynamic data modeling without requiring system-wide changes.

  • New fields can be added without IT development effort, making the system adaptable to evolving requirements.

3. No Impact on Core Upgrades

  • Unlike direct database customizations, EITs/EFFs remain intact during software upgrades, reducing maintenance effort.

  • Helps organizations future-proof their custom data.

4. Role-Based Security & Data Control

  • Can be configured with user access controls, ensuring that only authorized users can view or edit specific fields.

  • Helps maintain data integrity and compliance with security policies.

5. Improved Reporting & Analytics

  • Additional fields allow for better data segmentation and improved decision-making.

  • Enhanced reporting capabilities by capturing business-specific information that standard fields might not cover.

6. Reduces Need for Workarounds

  • Eliminates the use of spreadsheets or third-party solutions to manage extra data.

  • Centralizes all business data within the ERP or HRMS system for better efficiency.

7. Minimal Technical Dependency

  • Business users (with appropriate permissions) can configure EITs/EFFs without needing developer support.

  • Reduces IT workload while empowering functional teams to manage their own custom fields.

Steps to Enable

Use VB Studio show and hide section functionality to enable this section.

Tips And Considerations

When implementing Person Extra Information Types (EITs) / Extensible Flexfields (EFFs) in Oracle applications, it's essential to follow best practices to maximize flexibility while maintaining performance and data integrity. Here are some key tips and considerations:

1. Plan Before Implementation

  • Clearly define why you need EITs/EFFs—avoid unnecessary fields that may clutter the system.

  • Ensure that the new fields align with business processes and reporting requirements.

  • Decide whether to use EITs (for HR-related data) or EFFs (for broader applications like Finance, Procurement, etc.) based on your needs.

2. Follow Naming Conventions & Documentation

  • Use consistent naming conventions for easier identification and maintenance.

  • Document the purpose, business logic, and data dependencies of each EIT/EFF for future reference.

  • Avoid abbreviations that may be unclear to new users.

3. Use the Right Data Types & Validation

  • Choose appropriate field types (text, number, date, lookup values) to enforce data accuracy.

  • Apply value sets, LOVs (Lists of Values), or validation rules to prevent invalid entries.

  • Consider using mandatory fields where necessary to ensure critical data is always captured.

4. Optimize Performance & Minimize Impact

  • Avoid adding excessive EITs/EFFs that could slow down form loads or reports.

  • Use context-sensitive flexfields to only display relevant fields based on criteria, reducing clutter.

  • Regularly review and clean up unused fields to optimize system performance.

5. Implement Proper Security Controls

  • Configure role-based access so only relevant users can view/edit specific fields.

  • Apply data security policies to prevent unauthorized access to sensitive information.

  • Use audit trails if the data is critical for compliance or tracking changes.

6. Test Before Deployment

  • Perform thorough testing in a non-production environment before deploying changes.

  • Validate integrations with other modules or external systems to ensure data consistency.

  • Check for performance impact in reports and forms.

7. Ensure Compatibility with Upgrades

  • Avoid modifying standard Oracle database tables directly—always use EITs/EFFs properly to keep upgrades smooth.

  • Check Oracle documentation for any upgrade-related impacts on existing flexfields.

8. Consider Alternative Solutions If Needed

  • If an EIT/EFF seems overly complex, consider if a DFF (Descriptive Flexfield) or a custom report might be a better fit.

  • If frequent data updates are required, consider using tables or APIs instead of storing excessive information in EITs/EFFs.

Key Resources

For more information about VB Studio Business Rules, refer to this resource on the Oracle Help Center.

For a listing of all profile options for the recreated pages across applications, see the following document in My Oracle Support:

  • HCM Redwood Pages with Profile Options – MOS Document - 2922407.1

Access Requirements

To be able to extend any Redwood pages using VB Studio, users need to have the Application Implementation Manager or equivalent user role.