It is recommended to first Download Projects information into the worksheet, ensuring identifying columns are populated for accurate updating.
Please become familiar with the current Integrator limitations. These will be resolved over time as Oracle improves the underlying web services and we add additional functionality to this product.
The following values must be populated as a minimum to successfully update a standard purchase order:
Upload Action (at any level). Enter Update or Update records if you wish to cascade to child records.
Upload Action columns can be populated with an Update or Update records action if the values are to be updated or left blank if no processing of the data is required.
Scenario1
Amy is a project manager, and she would like to update the start and end date of one of her projects and update the Task Name for two of the Tasks on the project.
The image below illustrates how the Upload Action is left blank for Classifications and Team Members sections. Update action is populated in Header section and Tasks section for Task 1 and Task 3. When the project is uploaded, Header section and two Tasks in the Tasks section will be updated. Classifications, Team Members and Task 2 will not be updated.
Downloaded Project Information:
|
Header Action
|
Header Details
|
Classifications Action
|
Classifications Details
|
Team Members Action
|
Team Members Details
|
Tasks Action
|
Tasks Details
|
|
Update
|
123
|
-
|
1
|
-
|
1
|
Update
|
1
|
|
|
|
-
|
2
|
-
|
2
|
-
|
2
|
|
|
|
-
|
|
-
|
3
|
Update
|
3
|
Scenario 2
Amy is a project manager and she would like to update the Class Code for two of the three existing Classifications and end-date one of the team members on one of her projects.
The image below illustrates how the Upload Action is left blank for Header and Tasks sections. Update action is populated in the Classifications section for two classifications and one the Team Members. When the record is uploaded, Classification section and Team Members section will be updated. Header and Tasks will be ignored.
Downloaded Project Information:
|
Header Action
|
Header Details
|
Classifications Action
|
Classifications Details
|
Team Members Action
|
Team Members Details
|
Tasks Action
|
Tasks Details
|
|
-
|
123
|
Update
|
1
|
Update
|
1
|
-
|
1
|
|
|
|
Update
|
2
|
-
|
2
|
-
|
2
|
|
|
|
-
|
3
|
-
|
3
|
-
|
3
|
Scenario 3
Amy is a project manager, and she would like to update one of the Tasks and Create a new Task on one of her projects.
The image below illustrates how the Upload Action is left blank for Header, Classifications and Team Members sections. Update action is populated for Task 1 and Create action is populated for a new task, Task 3. When the project is uploaded, Task 1 will be updated and Task 3 will be created. All other sections will be ignored.
Downloaded Project Information:
|
Header Action
|
Header Details
|
Classifications Action
|
Classifications Details
|
Team Members Action
|
Team Members Details
|
Tasks Action
|
Tasks Details
|
|
-
|
123
|
-
|
1
|
-
|
1
|
Update
|
1
|
|
|
|
-
|
2
|
-
|
2
|
-
|
2
|
|
|
|
-
|
3
|
-
|
3
|
Create
|
3
|
Update Project Name, Class Code, Team Member Start Date, and Task Number
To update the fields mentioned above, please use a column that is specified for updating them. For example, to update the Project Name, use the column New Project Name to replace the name. Each section has a unique key value to identify the record in the database. For the Project Header section, Project Name is used as a unique key identifier so to update this field, the New Project Name field must be used. This applies to other sections that require an update to a unique key value.
What columns are needed?
The following columns must have values when updating the various sections of a project:
|
|
Section
|
|
Columns
|
Header
|
Classifications
|
Team Members
|
Tasks
|
Transaction Controls
|
|
Upload Action
|
○
|
○
|
○
|
○
|
○
|
|
Existing Project Name or Project Number
|
○
|
○
|
○
|
○
|
○
|
To elaborate on the table above:
● When updating a section, Project Name or Project Number along with the Upload Action for the section that requires an update must be populated if the data in those sections are to be updated. Sections without the Upload Action column populated will be ignored.
● Another example is, when updating Classifications, Project Name must be present on the sheet.
Column Update Restrictions
The underlying Oracle web service rejects the update of the following fields:
Note: all the columns that are grey cannot be updated.
|
Header
|
Classifications
|
Team Members
|
Tasks
|
|
Source Template Name
Project Number
Legal Entity
Source Application Code
Source Project Reference
Project Currency (if transactions for the project exists)
|
Class Category
|
Project Role
Team Member Name
Team Member Email
|
Parent Task Number
|
If you need to update any of these values, the project must be updated in the front-end, although some values cannot be updated in the front-end either (e.g., Project Number).
Sections:
