Reverse Autopopulate in Oracle Primavera Unifier is a feature that allows you to update or
modify data in a Business Process (BP) based on changes or values in related records or fields.
Unlike standard autopopulate, which fills fields based on predefined rules, reverse autopopulate
updates fields based on changes or values from other records.
Here’s how you can use Reverse Autopopulate in a BP in Unifier:
Steps to Use Reverse Autopopulate in a Business Process (BP)
1. Identify the Source and Target Fields
o Source Field: Determine which field or record will provide the data for the
autopopulate action. This could be a field from a related BP or a lookup field.
o Target Field: Identify the field within the current BP that will be updated based
on the data from the source field.
2. Set Up or Modify the Business Process
o Access BP Configuration: Go to the BP configuration area where you want to
implement reverse autopopulate.
o Define Source and Target Relationships: Ensure that the source and target
fields are correctly related or linked within the BP or between different BPs.
3. Configure Reverse Autopopulate Rules
o Open the Rule Editor: In the BP configuration, access the rules or scripting
editor where you can define the autopopulate logic.
o Define Autopopulate Logic: Write the logic or rules that specify how and when
the target field should be updated based on changes in the source field. This might
involve scripting or setting up conditions.
o Example Logic: If you want to update a “Cost” field in BP A based on the
“Total” field from BP B, you would set up a rule to pull data from BP B when a
relevant condition is met.
4. Specify Conditions for Update
o Update Triggers: Define the conditions under which the target field should be
updated. This could be based on changes in the source field, record status
changes, or other triggers.
o Data Validation: Ensure that the data being pulled from the source field is
validated before updating the target field.
5. Test the Configuration
o Create Test Records: Create or modify records to test the reverse autopopulate
functionality. Ensure that the target field updates correctly based on changes in
the source field.
o Review Results: Verify that the reverse autopopulate logic works as intended and
that data integrity is maintained.
6. Deploy and Monitor
o Deploy Changes: Once testing is successful, deploy the updated BP configuration
to the live environment.
o Monitor Functionality: Regularly monitor the reverse autopopulate functionality
to ensure it operates correctly and make adjustments as needed.
7. Maintain and Update
o Review and Adjust: Periodically review the autopopulate logic to ensure it
continues to meet business needs. Update the rules or logic as required based on
changes in business processes or requirements.
Example Scenario
Scenario: You have two BPs—BP A (Change Order) and BP B (Contract). You want to
automatically update the “Contract Value” field in BP A based on changes in the “Total Contract
Amount” field in BP B.
1. Source Field: “Total Contract Amount” in BP B.
2. Target Field: “Contract Value” in BP A.
3. Configuration:
o Rule Setup: When the “Total Contract Amount” field in BP B is updated, use
reverse autopopulate logic to update the “Contract Value” field in BP A with the
new value.
o Conditions: Define conditions such as linking the BP A record with the
corresponding BP B record.
Conclusion
Reverse Autopopulate in Unifier allows you to dynamically update fields in a BP based on
changes or values from related records or fields. By configuring source and target fields, defining
autopopulate rules, and specifying update conditions, you can ensure that your BPs reflect
accurate and up-to-date information.
