Import Sustainability Activities

Use the Import Sustainability Activities scheduled process to import sustainability activities by using file-based data import (FBDI).

The process imports large volumes of data from third-party or other Oracle applications and creates new activity data in Oracle Fusion Cloud Sustainability. Oracle Sustainability uses predefined emission factor mappings to calculate emissions for emission-generating activities and validates all draft activities to highlight issues that may need your attention before posting the activities to a sustainability ledger.

When to Use

Use this process when you use file based data import (FBDI):

  • To import large volumes of data.

  • For frequent data uploads.
  • To integrate with third-party or other Oracle applications.

Privileges Required

Import Sustainability Activity (ORA_SUS_IMPORT_ ACTIVITIES)

Specifications

Review the following before setting up this scheduled process:

Specification Description
Job Type Schedule the job, or run it on an ad hoc basis, as needed
Frequency Daily or weekly, depending on your data volume, and how often you import data to create activities and Sustainability analysts review these activities to post them to the sustainability ledger.
Time of Day After work hours
Duration Variable, based on the volume of data to be imported.
Compatibility

There should be only one instance of the job running at any time, and there’s no current functional need to run multiple instances of this process simultaneously.

Oracle Sustainability prevents this job from running simultaneously while Generate Sustainability Activities from Payables Invoices process is running.

Parameters

Parameter Optional or Required Description Parameter Value Special Combinations Required Notes
Batch ID Optional

Enter the batch ID corresponding to the set of records in the interface table that needs to be retrieved. This is the same batch ID that you had previously populated in the file-based data import template.

Ensure that you specify this ID correctly on the records and in the import job.

  • Records for which the job is never run with the corresponding Batch ID will stay in the interface table as unprocessed.
  • If you do not specify the batch ID in the process, then Oracle Sustainability will retrieve all the records in the interface table for processing.

Batch ID

None N/A
Post to Ledger Optional Set the value to Yes if you want the activities that are created and have passed validation to be posted to the ledger. Otherwise, set it to No. Yes or No. Default value is No. None N/A

Troubleshooting Information

  • You can view the status of the process on the scheduled processes work area.
  • Check the output file for summary information regarding:

    • The number of records selected for processing, the number of records that succeeded in activity creation, and number of records that failed. The output file lists the reasons for each failed record and explains why these records weren't imported into the application. The failed records remain in the interface table for 30 days for reference, allowing them to be corrected in the XLSM template. Once corrected, the records can be imported again.
    • The number of activities needing your attention after validation.
    • The number of activities successfully posted when the Post to Ledger preference is set to Yes.
  • You can query for the resulting activities in the Sustainability Activities page. You can query by the External Reference Number if provided or Source Type as 'File-based data import" to filter for records processed through the Import Sustainability Activities scheduled process.

  • When the process is submitted, you can Resubmit, Put on Hold, Cancel Process, or Release Process as provided by the scheduled processes work area.
  • If the job takes longer than usual to complete,then check if you've received an unusually large volume of records.
  • If the job fails, then check the output file and log file for an error message.
    • If the process has ended in error because of incomplete setup, then complete all setup tasks and try again.
    • If the process failed because of a system error, then resubmit the process with the same set of parameters.