In SAP Ariba, the Predecessor Project field is designed to help users create logical, traceable, and organized relationships between projects. Although users often assume the predecessor feature is intended for copying data, its primary purpose is to build project relationships that support reporting, visibility, and structured project hierarchies.
This article explains what the Predecessor Project field is used for, how it differs from the Copy from Project capability, and why predecessor projects remain selectable even after they are completed or approved.
What Is the Purpose of the Predecessor Project Field?
The Predecessor Project field serves two main purposes:
Establishing a Link Between Related Projects
Selecting a predecessor project allows you to link the current project to an existing one.
This relationship does not require copying values from the predecessor.If the sole intention is to copy data, users should instead use the Copy from Project option.The predecessor linkage provides context, relationships, and traceability between projects.
2. Supporting Hierarchical Reporting (Subprojects)
When you assign a predecessor project, the system can treat the current project as a follow-on or subproject in reporting views.
This helps teams and organizations visualize chains of related initiatives.It ensures reporting structures reflect how projects truly relate to one another.
Predecessor Project vs. Copy from Project
Although both functions may prepopulate fields, they serve different purposes.
Predecessor Project
Selecting a predecessor from the dropdown menu creates a follow-on relationship.Fields that exist in both the predecessor and the current project may be pre-populated.The main goal is linking projects, not cloning them.The predecessor project retains its identity and lifecycle.
Copy from Project
Creates a copy of an existing project.The copied project retains most of the original project’s attributes.You cannot select a new template or project type when copying.The new project inherits the project type and uses the latest published version of the template originally used.This option is intended for reusing structure and content—not linking projects.
Why Is a Predecessor Project Still Available After Completion or Approval?
A predecessor project remains selectable even after it is completed, approved, or closed, because its function is not tied to its status. The predecessor mechanism exists to maintain continuity and logical connections across related initiatives, regardless of where each project is in its lifecycle.
The purpose of a predecessor is not to transfer or copy data—it is to maintain a conceptual and reporting link.
Example Scenario: ABC Corporate Electronics Procurement
Consider the following use case:
ABC manager creates a parent RFI project to collect information from suppliers.Once the RFI is completed, each team member creates their own individual sourcing or contracting project to procure electronic devices based on their personal needs.Even though the original RFI project is already completed, it remains available as a predecessor.Each team member sets the RFI project as their predecessor, creating a clear traceable line between the parent project and all the follow-on projects.
This ensures:
All child projects remain connected to the original sourcing initiative.Reporting and audits reflect a complete project hierarchy.Stakeholders can easily understand the sequence and relationship between efforts.
How Field Copying Behaviors Are Controlled in SAP Ariba (Advanced Field Configuration)
Whether fields are copied, synced, or inherited across projects (including predecessor and copied projects) depends on Advanced Field Configuration settings. These settings determine when and how field values flow between parent, predecessor, or copied projects.
Below are the key configuration options:
Sync in copied project on create:This option copies fields when using the Copy from Contract field on create or Actions > Copy Project.Sync in follow-on project on create:This option copies fields when using the Actions > Follow-on Project or by selecting a Predecessor Project.Sync in subagreement on create:This option copies fields when using the Parent Agreement field on create or Actions > Sub Agreement.Sync in subproject on create:This option copies fields when using the Actions > Create Subproject (from the Documents tab).Sync in subproject on change:Makes the field in a subproject be auto pulled from its parent project whenever the field is updated in the parent project, including when the subproject is created.These options are not available for all fields and must be configured by an SAP resource.Present under Advanced tab of Field Configuration for specific fields.
Summary
Feature
Predecessor Project
Copy from Project
Purpose
Link projects logically
Reuse content by creating a copy
Effect
Creates follow-on relationship; may prefill shared fields
Creates a new project based on another
Template control
Uses template of the current project
Inherits template of the original project
Best used for
Reporting structure, traceability, subproject relationships
Cloning project design, structure, and content
#Predecessor Project
In SAP Ariba, the Predecessor Project field is designed to help users create logical, traceable, and organized relationships between projects. Although users often assume the predecessor feature is intended for copying data, its primary purpose is to build project relationships that support reporting, visibility, and structured project hierarchies.This article explains what the Predecessor Project field is used for, how it differs from the Copy from Project capability, and why predecessor projects remain selectable even after they are completed or approved.What Is the Purpose of the Predecessor Project Field?The Predecessor Project field serves two main purposes:Establishing a Link Between Related ProjectsSelecting a predecessor project allows you to link the current project to an existing one.This relationship does not require copying values from the predecessor.If the sole intention is to copy data, users should instead use the Copy from Project option.The predecessor linkage provides context, relationships, and traceability between projects.2. Supporting Hierarchical Reporting (Subprojects)When you assign a predecessor project, the system can treat the current project as a follow-on or subproject in reporting views.This helps teams and organizations visualize chains of related initiatives.It ensures reporting structures reflect how projects truly relate to one another.Predecessor Project vs. Copy from ProjectAlthough both functions may prepopulate fields, they serve different purposes.Predecessor ProjectSelecting a predecessor from the dropdown menu creates a follow-on relationship.Fields that exist in both the predecessor and the current project may be pre-populated.The main goal is linking projects, not cloning them.The predecessor project retains its identity and lifecycle.Copy from ProjectCreates a copy of an existing project.The copied project retains most of the original project’s attributes.You cannot select a new template or project type when copying.The new project inherits the project type and uses the latest published version of the template originally used.This option is intended for reusing structure and content—not linking projects.Why Is a Predecessor Project Still Available After Completion or Approval?A predecessor project remains selectable even after it is completed, approved, or closed, because its function is not tied to its status. The predecessor mechanism exists to maintain continuity and logical connections across related initiatives, regardless of where each project is in its lifecycle.The purpose of a predecessor is not to transfer or copy data—it is to maintain a conceptual and reporting link.Example Scenario: ABC Corporate Electronics ProcurementConsider the following use case:ABC manager creates a parent RFI project to collect information from suppliers.Once the RFI is completed, each team member creates their own individual sourcing or contracting project to procure electronic devices based on their personal needs.Even though the original RFI project is already completed, it remains available as a predecessor.Each team member sets the RFI project as their predecessor, creating a clear traceable line between the parent project and all the follow-on projects.This ensures:All child projects remain connected to the original sourcing initiative.Reporting and audits reflect a complete project hierarchy.Stakeholders can easily understand the sequence and relationship between efforts.How Field Copying Behaviors Are Controlled in SAP Ariba (Advanced Field Configuration)Whether fields are copied, synced, or inherited across projects (including predecessor and copied projects) depends on Advanced Field Configuration settings. These settings determine when and how field values flow between parent, predecessor, or copied projects.Below are the key configuration options:Sync in copied project on create:This option copies fields when using the Copy from Contract field on create or Actions > Copy Project.Sync in follow-on project on create:This option copies fields when using the Actions > Follow-on Project or by selecting a Predecessor Project.Sync in subagreement on create:This option copies fields when using the Parent Agreement field on create or Actions > Sub Agreement.Sync in subproject on create:This option copies fields when using the Actions > Create Subproject (from the Documents tab).Sync in subproject on change:Makes the field in a subproject be auto pulled from its parent project whenever the field is updated in the parent project, including when the subproject is created.These options are not available for all fields and must be configured by an SAP resource.Present under Advanced tab of Field Configuration for specific fields. SummaryFeaturePredecessor ProjectCopy from ProjectPurposeLink projects logicallyReuse content by creating a copyEffectCreates follow-on relationship; may prefill shared fieldsCreates a new project based on anotherTemplate controlUses template of the current projectInherits template of the original projectBest used forReporting structure, traceability, subproject relationshipsCloning project design, structure, and content #Predecessor Project Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
