Albertsons TREX

ACI_INTE18_TDD_Demand_Forecast
Attributes to Oracle

Technical Design Document

© Copyright 2020 Oracle Consulting (OC), Cloud Adoption Services (CAS)

Table of Contents
Document Control__________________________________________________________________________3
Change Record___________________________________________________________________________________3
Overview________________________________________________________________________________4
Business Objective________________________________________________________________________________4
Technical Assumptions____________________________________________________________________________4
Scope__________________________________________________________________________________________5
High Level Flow__________________________________________________________________________________6
Technical Flow Diagram____________________________________________________________________________6
Flow Diagram____________________________________________________________________________________7
Integration Flow Logic_____________________________________________________________________________8
Planning Launcher Service_________________________________________________________________________________8
Launcher Service_________________________________________________________________________________________8
Transaction Processor Service______________________________________________________________________________8
Transformation Service____________________________________________________________________________________8
Import Service___________________________________________________________________________________________8
Callback Service__________________________________________________________________________________________8
Middleware Components_________________________________________________________________________10
Object Storage Components_______________________________________________________________________11
SFTP Configuration Details_______________________________________________________________11
Env : [Endpoint details will vary based on the instances]________________________________________________11
SaaS Components_______________________________________________________________________12
Import Job Details:______________________________________________________________________________________12
ESS Job Details:_________________________________________________________________________________________12
BIP Report Details:______________________________________________________________________________________14
Data Mapping___________________________________________________________________________________14
Data File Format:________________________________________________________________________________15
Demand Forecast Warehouse Attributes Metadata____________________________________________________15
Setup/Configurations_____________________________________________________________________________15
User and Security________________________________________________________________________________15
Exception Handling______________________________________________________________________16
Notification Requirements_______________________________________________________________17
Success Notification______________________________________________________________________________17
Error Notification________________________________________________________________________________17

OC Cloud Adoption Services | Cloud Integration Design Specification

Re-processing Strategy__________________________________________________________________17
Unit test Results_________________________________________________________________________17
Installation Steps________________________________________________________________________18
Open Closed Issues______________________________________________________________________18
Open Issues____________________________________________________________________________________18
Closed Issues___________________________________________________________________________________18

OC Cloud Adoption Services | Cloud Integration Design Specification

Document Control
Change Record

Versio
Date Author Summary of Changes
n

1 6-Dec-2024 Sravani K Initial Draft

Reviewer Date Role / Responsibility

Shravan Kumar Valakonda Technical Lead

Vasu Raju Technical Lead

Abhijit Functional Lead

Praveen Rentala ACI Tech

Manu Krishnan ACI Tech

Santosh Honnavalli ACI Tech

OC Cloud Adoption Services | Cloud Integration Design Specification

Overview
Albertsons is one of the largest food and drug retailers in the United States, with both strong local presence and
national scale. The Transformation of Replenishment Execution (T-REX) program will transform and modernize
replenishment execution using modernize architecture from a siloed set of systems into a unified platform and a
seamless part of Supply Chain ecosystem.

The objective of this document is to provide Albertsons with a Technical Specification part of their Oracle Cloud
Adoption initiative to seamlessly sync the Demand Forecast Attributes flow from SSIMS through Azure Data base to
Oracle Supply Panning area.

Business Objective
The key objective of this inbound integration is to establish an interface that can communicate the forecast generated
in BY, DA and Afresh to Oracle. As part of this integration flow, we need to import the FBDI files that are received from
SSIMS system to SFTP folder to Oracle ERP cloud.

Technical Assumptions
This design assumes the following.
 All the below required setup exists in Oracle SCM Cloud for Demand Forecast Attributes Import.
Oracle Supply Planning Configurations
Planning source system - OPS
 Built using Oracle Integration Cloud, Visual builder cloud service, SFTP and Object Storage Cloud Service.
 Business Data validation is accomplished in source systems.
 Always one zip file is placed in SFTP folder for creation or updating of any of the Demand Forecast Attributes
 Data file sent in the source SFTP location will be of comma (,) delimited format.
 All system related error handling is handled by OIC Common Error Handling Framework.
 A common Integration User “ACI_OEPR_SCP_*” needs to be configured for OIC and ERP Cloud for each
environment to support scheduling or Import Processes from OIC.
 All the connections including SFTP, VBCS, Object Storage and ERP Cloud should be configured with appropriate
credentials.
 If there are errors while importing Demand Forecast Attributes information in Oracle Fusion, then those errors
are corrected by Albertsons and processed in subsequent runs.
 A new ESS job set is created and scheduled. This job will internally trigger a BIP report, which will then invoke
the customized common launcher service. From there, the Supply Chain Planning FBDI process will be
executed.

OC Cloud Adoption Services | Cloud Integration Design Specification

All the configuration parameters like File path, Email ids, Notification flag etc. will be defined in the VBCS business
object as metadata entry. OIC Integration looks for these parameters while processing the Demand Forecast Attribute
records.

Scope
The complete Integration solution will be built using Oracle Cloud integration platform. Inbound integrations will have
below distinct blocks as described below.
 SFTP
o Source files are placed in respective folders at the SFTP location.
 Oracle Integration Cloud
o Tool to orchestrate, move zip files from SFTP to OIC stage location.
o Orchestrate Processes to initiate Demand Forecast Attributes Data import to SaaS.
o Receives Call back from SaaS on Job completion (Success/Warning/Error)
o Sends Repose to target system owners with failure, if any.
 Visual Builder Cloud Service
o Stores metadata entries like lookup information for the integration
o Maintains the transaction date and used to display the integration run details in Dashboard.
o Used to submit Ad-hoc run.
 Oracle Cloud Object Storage
o Staging location for data to be loaded to Object Storage.
o Staging location for FBDI Zip file to be loaded into ERP Cloud
o Optionally can be used for long term file retention if needed.
 ERP Cloud
o Demand Forecast Attributes data gets imported into the Oracle SCM Cloud.

OC Cloud Adoption Services | Cloud Integration Design Specification

High Level Flow

Technical Flow Diagram

OC Cloud Adoption Services | Cloud Integration Design Specification

 7

OC Cloud Adoption Services | Cloud Integration Design Specification

Flow Diagram

OC Cloud Adoption Services | Cloud Integration Design Specification

Integration Flow Logic
Planning Launcher Service
 Launcher service is initiated through Scheduler in real time with file prefix and other input parameters.
 Fetches the raw files from the object storage with transaction entries if the count is greater than zero
invokes Transaction Processor Service and updates the business objects with last run date in metadata info.

Launcher Service
 Launcher service is initiated through planning launcher service with file prefix and other input parameters.
 Fetches the raw files from the object storage with transaction entries if the count is greater than zero
invokes Transaction Processor Service and updates the business objects with last run date in metadata info.

Transaction Processor Service

 Transaction Processor Service is initiated through Launcher in real time with file prefix and other input
parameters.
 Fetches files from object storage/FTP and based on parallel flag, for each file it fetches transaction details,
updates the logger information, and invokes Demand Forecast Attributes Transformation Integration
defined in the metadata.

Transformation Service
 Transformation Service is initiated through Transaction Processor for each file in real time with Transaction
ID, Filename, and other input parameters.
 Fetches the source transformed file from object storage/FTP, creates special parameter file, zip both source
file and parameter file and upload the FBDI zip file in object storage/FTP.
 Invokes Demand Forecast Attributes FBDI Import integration to import Demand Forecast Attributes records
into Supply Chain Planning

Import Service
 Import Service is initiated through Demand Forecast Attributes Transformation Service for each zip file in
real time with Transaction ID, ZIP Filename and other input parameters.
 Triggers the Demand Forecast Attributes scheduled process according to the source file received and
updates Job Details, checks for Call back status, and updates Logger Information.
 Runs the Error Report, downloads the run Instance Logs, moves Logs to relevant buckets and sends
Notification.
 The error records are re-processed in the subsequent runs based on the fixes of the errors shared.

Callback Service
1. Call back service is instantiated from SaaS once all the ESS job processes are completed.
2. Fetches FBDI Import Job Details and updates the status in Transaction Business Object for Demand Forecast
Attributes Integration

OC Cloud Adoption Services | Cloud Integration Design Specification

Solution Components
Middleware Components
# List of OIC Orchestration Description
An App-Driven integration which will be invoked by ESS Job and Moves
1 ACI_OEPR_PLANNING_LAUNCHER
Demand Forecast Files from SFTP to Object Storage/FTP
ACI_OEPR_UTIL_CMN_LAUNCHER_ Invokes Transaction Processor
2
SCP ‘ACI_OEPR_TRANSACTION_PROCESSOR_IB_SCP’
ACI_OEPR_TRANSACTION_PROCES Invokes Transformation Integration ‘ACI_OEPR_ERP_
3
SOR_IB_SCP DEMANDFORECAST _IB‘ for each file based on parallel flag
ACI_OEPR_ERP_ DEMANDFORECAST Populates FBDI zip file with Property file and initiates ‘ACI_OEPR_ERP_
4
_IB DEMANDFORECAST_IB’
ACI_OEPR_ERP_ERPINT_
5 Imports Demand Forecast Attributes Bulk Data and notifies status report
DEMANDFORECAST_IB
6 ACI_OEPR_CALLBACK_SERVICE_IB Based on the Callback, Updates the Jobs status
ACI_OEPR_UTIL_CMN_NOTIFICATION
7 Common Service to send notification, attach files based on metadata
_SERVICE

Components Type Values Purpose

DVM Lookup ACI_OEPR_ENVGLOBAL_LKP, Stores Job Path, Parameters, OIC
ACI_OEPR_TRANSACTIONSTATUS_LKP, integrations names, BIP reports
ACI_OEPR_CMN_NOTIF_LKP, path and static values
ACI_OEPR_LOGGER_LKP_285,
ACI_OEPR_CMN_INT_LKP,
ACI_OEPR_INTEGRATION_PATTERN_LKP,
ACI_OEPR_LOGGER_LKP,
ACI_OEPR_PROCESSINGSTATUS_LKP
Oracle ERP Adapter ACI_OEPR_ORCL_ERP_FIN_ADAPTER Invoke ERP services from OIC
Cloud
REST Adapter ACI_OEPR_REST_CONN, Invoke OIC Integrations
ACI_OEPR_ORCL_REST
REST Adapter ACI_OEPR_ORCL_LOGGERSERVICE_REST Populate values in VBCS business
objects
SOAP Adapter ACI_OEPR_ERP_BIP_SOAP_FIN Invoke BIP reports from OIC
SOAP Adapter ACI_OEPR_ORCL_GENERIC_FIN_SOAP Invoke ERP services to download
logs

10

OC Cloud Adoption Services | Cloud Integration Design Specification

Object Storage Components
Object Storage/FTP
# Buckets Description
1 RAW Source Files
2 FBDI FBDI Files to be loaded into ERP Cloud
3 ARCHIVE Success files
4 ERROR Error reports and files

SFTP Configuration Details

Env : [Endpoint details will vary based on the
instances]
Env : fs-oepr-integration-dev-oic-01-id3viihxuv8k-ia.integration.us-ashburn-1.ocp.oraclecloud.com [Endpoint
details will vary based on the OIC instances]

# Key Value
1 Host Name 147.154.47.159
2 Port 10154
3 Folder Structure IN - /Inventory/DemandForecast/Inbound/Data

11

OC Cloud Adoption Services | Cloud Integration Design Specification

SaaS Components
Import Job Details:

Attribute Name Value

Import Job Name Load Planning Data from Flat Files

Import Job Path /oracle/apps/ess/scm/advancedPlanning/collection/configuration/

Import Job Code CSVController
UCM Account scm/planningDataLoader/import
UCM Security Group FAFusionImportExport
Import Job Parameter 1 SR_INSTANCE_CODE
Import Job Parameter 2 COLLECTION_MODE
Import Job Parameter 3 ORG_GROUP
Import Job Parameter 4 RETAIN_FCST_BY_DESIGNATOR
Import Job Name Load Planning Data from Flat Files

ESS Job Details:

ESS Job and parameters with the following details:

Attribute Name Value

Display Name ACI OEPR Supply Chain Planning FBDI Import Process
Name ACIOEPRSCPFBDI
Path /fin/
Job Application Name FscmESS
Job Type BIPJobType
Bursting Report No
Report ID /Custom/ACI_SCM_Integrations/DemandForecastAttributes/
ACI_OEPR_SCP_LAUNCHER.xdo
Allow Multiple Pending False
Submissions

Parameter Data Date Page Require Do Default Value List Attribute Display
Name type and Eleme d Not of Attribute
Time nt Displ Valu
/ ay e
Date Sour
Only ce
Invoked By String N/A Text Y Y N/A N/A N/A
Box
Interface Id String N/A LOV Y Y YTD N/A N/A N/A

12

OC Cloud Adoption Services | Cloud Integration Design Specification

** Please select ACI_OEPR_DEMANDFORECAST_IMPORT_IB**

Attribute Name Value

Display Name ACI Publish Demand Forecast Attributes Errors
Name ACI_VENATTRWH_ERRORS
Path /int/
Job Application Name FscmESS
Job Type BIPJobType
Bursting Report Yes
Report ID /Custom/ACI_SCM_Integrations/DemandForecastAttributes/
ACI_OEPR_SCP_STATUS_Report.xdo
Allow Multiple Pending False
Submissions

Parameter Data Date Page Require Do Default Value List Attribute Display
Name type and Eleme d Not of Attribute
Time nt Displ Valu
/ ay e
Date Sour
Only ce
Request Id String N/A Text Y Y N/A N/A N/A
Box

13

OC Cloud Adoption Services | Cloud Integration Design Specification

BIP Report Details:

Attribute Name Value

Data Model Location /shared/Custom/ACI_SCM_Integrations/DemandForecastAttributes/
DataModels/
Data Model Name ACI_OEPR_DemandForecastAttributes_Status_DM
Report Path Name /shared/Custom/ACI_SCM_Integrations/DemandForecastAttributes
Report Name ACI_OEPR_DemandForecastAttributes_Status_Report
Report Template ACI_OEPR_DemandForecastAttributes_Status_Layout.rtf
Parameters P_LOAD_REQUEST_ID
Output Format Type .csv

Attribute Name Value

Data Model Location /shared/Custom/ACI_SCM_Integrations/DemandForecastAttributes/
DataModels/
Data Model Name ACI_OEPR_DemandForecastAttributes_Count_DM
Report Path Name /shared/Custom/ACI_SCM_Integrations/DemandForecastAttributes
Report Name ACI_OEPR_DemandForecastAttributes_Count_Report
Report Template ACI_OEPR_DemandForecastAttributes_Count_Layout.rtf
Parameters P_BTACH_ID,P_LOAD_REQUEST_ID
Output Format Type .csv

Attribute Name Value

Data Model Location /shared/Custom/ACI_SCM_Integrations/DemandForecastAttributes/
DataModels/
Data Model Name ACI_OEPR_DemandForecastAttributes_Count_DM
Report Path Name /shared/Custom/ACI_SCM_Integrations/DemandForecastAttributes
Report Name ACI_OEPR_DemandForecastAttributes_Count_Report
Report Template ACI_OEPR_ DemandForecastAttributes_Count_Layout.rtf
Parameters P_BTACH_ID,P_LOAD_REQUEST_ID
Output Format Type .csv

Data Mapping
Refer to FSD.

14

OC Cloud Adoption Services | Cloud Integration Design Specification

Data File Format:

Data File Security PGP Encryption required (Yes/No)

Transmission Method  SFTP file Server
File Naming ACI_OEPR_SCP*_<BatchID>.zip
Convention[zip]
File Naming ExternalForecast.csv
Convention[csv]
Scheduling Requirement YTD
Integration Behavior Create / Update/Sync
Expected Volume 2000k records per file
Source File Location /Inventory/DemandForecast/Inbound/Data
Record Delimiter ‘,’
File Format .Zip

Demand Forecast Warehouse Attributes

Metadata

Setup/Configurations
Specify any dependent SaaS configuration to support this technical solution e.g., extract configuration, schedule jobs.

User and Security

Specify integration specific user& roles in Fusion and other systems.
Security Level Applicable Details View/Schedule/Run
Users Y DEV_OIC_SVC V/S/R
Roles Y Inventory Administrator
Roles Y Order Promising Manager

15

OC Cloud Adoption Services | Cloud Integration Design Specification

Exception Handling
The Demand Forecast Attributes files containing the Demand Forecast Attribute entries for importing and loading into
ERP Cloud are placed in OIC SFTP server from where this integration gets the file.
Exceptions in OIC Layer

Error Probable Reasons Error Category Recovery

OIC Data Preparation and SaaS connection failure System Notify Customer with the custom
Import to ERP Cloud OIC layer connection failure message

Load failed to interface Data not loaded to the Business Notify Customer with the custom
tables interface message

Import failed to base Missing Configuration Business Fix the configuration setup and
tables reprocess the input data file.

 In case of any failures while fetching the source, file or Preparing FBDI zip file, an Email notification is sent to the
concerned users and the error is logged into Transaction/Instances/Logger Business Object in VBCS dashboard
with all error details.
 Once the zip file is prepared with the special parameters file and FBDI file successfully import is initiated
using FBDI job name.
 OIC receives a call back once the job has completed or failed,
 In case of any failures at the base table import level, partial processing happens within ERP Cloud. OIC runs a
BIP Error report based on the request if to identify records imported successfully vs failed, correspondingly
updates Transaction/Instances Business Object and notification is sent to the concerned users.

16

OC Cloud Adoption Services | Cloud Integration Design Specification

Notification Requirements
Specify the technical approach to notify errors regarding the execution details.

On Job Failure On Warning

Notifying On Success
(Full File (Partial data Notification to
System
rejection) rejection)

OIC Yes Yes No XXX@oracle.com

Success Notification
YTD

Error Notification
YTD
Re-processing Strategy

Demand Forecast Attributes Inbound Integration follows a batch File based design pattern, with this approach we
are generating a Transaction ID at while moving the file from SFTP to Object Storage/FTP. This Transaction ID is
carried forward throughout the lifecycle of the transaction. Also, transformation Integration which generates the
FBDI Zip accepts the Transaction ID as input. With this design approach, in case of failure at any step, we can
reprocess a particular batch with Transaction ID as input parameter.
In addition, OIC flow instances can be resubmitted in the event of failure. All the failed instances will be sent to
Albertsons for modification and those failed records will be processed in subsequent runs in new files. They can be
selected from OIC monitoring console errors page or other views as well. These can either be discarded or
resubmitted.

Unit test Results

YTD

NOTE: In case of purge scenario, if successful, base table planning data from MSC_ITEM_SUPPLIERS table is deleted and as it is a
successful scenario, interface table is also purged as part of regular import process. So, in this case, we will only be able to fetch
success and error counts and no recon report will be provided.

17

OC Cloud Adoption Services | Cloud Integration Design Specification

Installation Steps
 A separate IM090 document will be produced for code bundle preparation and migration purpose.
 ACI GIT hub repository will be used for source code control/version.

Open Closed Issues

Open Issues
ID Issue Resolution Responsibility Target Impact
Date Date
1 When in the night the ACI
forecast files will be
available to be interfaced
to Oracle? This will impact
the overall planning cycle
on daily basis.
2 If the required datafile OCS
from ACI Legacy system
arrives sometime later
than expected (pre-
defined), the integration
process should wait and
process the file. If it is too
late, the integration
process should abort and
notify?
Email Notifications, Build Sravani
6 and UT document to be
updated
If any changes comes up in Sravani
plano discussions, we will
7
be updating this document
accordingly

18

OC Cloud Adoption Services | Cloud Integration Design Specification

Closed Issues
ID Issue Resolution Responsibili Target Impact
ty Date Date
1 Error Log O/P is shared, can you Clarified which are the Abhijit
confirm whether we need to columns need to be
include any specific columns in populated in the error
the error report. report.
2 For Interface, whether We are going to Abhijit
we are going to publish publish the error
only error report or recon report.
report.

19

OC Cloud Adoption Services | Cloud Integration Design Specification

Workflow Design files

20

OC Cloud Adoption Services | Cloud Integration Design Specification