Standard Costs Conversion Mapping Specification

 

 

Standard Costs Conversion Mapping Specification

 

 

              Standard Costs Data Conversion

 

 

 

 

 

 

Author:                                  

Creation Date:                     

Last Updated:                     

Document Ref:                   

Version:                                 0.1

 

Note:Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents.  When you change any of these values, be careful not to accidentally delete the bookmark.  You can make bookmarks visible by selecting Tools->Options…View and checking the Bookmarks option in the Show region.

 

 

Document Control

Change Record

2

Date	Author	Version	Change Reference

 

 

Reviewers

Name	Position

 

Approvers

 

Name	Position

 

 

Contents

Document Control...................................................................................... 2

Change Record........................................................................................... 2

Reviewers.................................................................................................. 2

Approvers.................................................................................................. 2

Introduction.............................................................................................. 4

Conversion Scope, Strategy And Assumptions.................................................. 4

Prerequisites.............................................................................................. 4

Oracle FUSION ITEM TEMPLATE Lookup Field MAPPING................................... 5

MAPPING SPECIFICATIONS........................................................................... 6

Data Extract Component Logic...................................................................... 7

Data Extraction Rules................................................................................... 7

Upload Component Logic............................................................................. 8

Data Flow Assumptions/ Prerequisites............................................................ 8

Open and Closed Issues............................................................................. 10

Open Issues.............................................................................................. 10

Closed Issues............................................................................................ 10

 

Note:To update the table of contents, put the cursor anywhere in the table and press [F9].  To change the number of levels displayed, select the menu option Insert‑>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

 

Introduction

Note:A work product document should be produced for each of the business entities being converted.  You may want to use the Subject field to indicate the business entity.

The purpose of this document is to document and communicate the configurations, data mapping, interdependency and component design specifications for the conversion of an individual entity that is going to be converted to the Oracle Cloud applications.

Following Objects will be converted:

Standard Costs of all the Items

Conversion Scope, Strategy And Assumptions

The Conversion Component Designs is used by the Technical team as the basis for the design and construction of the Standard Costs conversion.

High Level Conversion Process Overview- Standard Costs Conversion

a.      The Data Migration of Oracle Standard Cost data will involve conversion of data from CLIENT’s old legacy system into CLIENT’s new Oracle Fusion.

b.      The data being migrated from CLIENT’s old system into new system will be transformed because the source and target data structures are different.

c.      The datafile provided will be used to build the import FBDI templates with Metadata of Standard Cost

 

Prerequisites

Following configurations are required in SaaS

S.no	Task Name	Status	Comments
01.	Enterprise Design Setup	Completed
02.	Item and Related Item Setups	Open	All the Items still to be converted and Open Point on Category and Attribute
03.	Cost Organization	Completed
04.	Cost Book	Completed
05.	Cost Element	Completed
06.	Valuation Unit	Completed
07.	Valuation Unit Code	Completed
08.	Cost Scenario Setup	Completed

 

 

Oracle FUSION Standard Costing Lookup Field MAPPING

No Lookup reference required in Standard Cost FBDI

 

MAPPING SPECIFICATIONS

 

 

Standard Costing FBDI

Oracle FBDI Field Name	Description	Mapping from legacy system/Values

 

 

DATA FIELD MAPPING

 

Data conversion process involves mapping of source and destination columns which is the critical part of entire conversion process. As discussed on Standard Costs conversion with Videojet IT and Business, mapping of the columns will be provided along with data in standard FBDI template.

 Sample Data provided in FBDI template:

Fusion Navigations:

Standard Cost screen: Supply Chain Execution -> Cost Accounting -> Manage Standard Costs

Run ESS job: Tools -> Scheduled Processes -> Schedule New Process  

Standard ESS Jobs used in Item Conversion:

Interface file for Import

Once the ESS jobs successful follow the below process.

Navigate to below screen and run the Import Standard Costs button:

Supply Chain Execution -> Cost Accounting -> Manage Standard Cost Import Exceptions

Click on Import Standard Costs button as shown below

Data Extract Component Logic

Note:Describe the component logic for the download component(s) used to convert the entity being converted.

Bring  Standard Cost and related details from existing legacy system to New Fusion

 

To bring in Standard Cost Data into Oracle fusion we need pre-requisites of Enterprise Design Setup, Item and Related Item Setups, Cost Organization, Cost Book, Cost Element, Valuation Unit, Valuation Unit Code, Cost Scenario into Oracle Fusion. These will be loaded as part of separate conversions or created as part of configuration.

 

Pool: Only Include Active Item Data

 

 

Data Extraction Rules

 

S.no	Business Rules
01.	Standard Costing will be used in USGAAP (Primary Ledger) and for LocalGAAP (Secondary Ledger) different costing method will be used
02.	Standard Costs of an Item will be converted and getting associated with only Primary Cost Book in the system
03.	Separate Standard Cost of each Item will be getting created and getting assigned to Cost Scenario.
04.	Valuation Code and Valuation Unit will remain constant for all the Item

 

Upload Component Logic

Note:        Describe the component logic for the upload component(s) used to convert the entity being converted.

·        After you finish preparing the data in the parent and child sheets, click the Generate CSV File button. The program generates both a CSV file and a ZIP file. 

·        Load the data using the Load Interface File for Import process:

     1. Log in to the Oracle Cloud SFTP server.

     2. Transfer the ZIP file to the SFTP server location.

     3. Log in to Oracle Fusion Applications.

     4. Navigate to Scheduled Processes.

     5. Select the Load Interface File for Import process. 

     6. Select the process indicated in the Overview section to load the CSV file to the interface tables.

     7. Review the results of the process.

·        Correct load errors:

1.      If the load of the CSV file fails on any row, the Load Interface File for Import process ends in error and the Load File to Interface child process ends in either warning or error. 

2.      All rows that were loaded from the CSV file are deleted, even those rows that loaded successfully. This lets you edit the problematic data in the spreadsheet and resubmit without having to separate the successful rows from the rows that need modification.  

3.      Review the log and output files of the Load File to Interface child process for information about the data that caused the failure.

4.      Correct the data in the template you used as part of the steps outlined in Preparing the Table Data above.

5.      Repeat steps 1 and 2 of this section: Generate the CSV file and load the data using the Load Interface File for Import process.

6.      Repeat all of these steps until all data is loaded successfully.

 

Data Flow Assumptions/ Prerequisites

The development specifications for Standard Cost data assume the following:

Key Assumptions are:

·        The data of Standard Cost will be provided by the CLIENT extraction team directly into CSV Datafile.

·        Oracle technical team will prepare the data in the required Oracle FBDI format.

·        FBDI will be build based on single Standard Cost datafile provided.

·        All required setups/configurations have been completed before the program is run.

ü  Enterprise Design Setup

ü  Item and Related Item Setups

ü  Cost Organization

ü  Cost Book

ü  Cost Element

ü  Valuation Unit

ü  Valuation Unit Code

ü  Cost Scenario Setup

 

 

 

Open and Closed Issues

 

Note:Add open issues that you identify while writing or reviewing this document to the open issues section.  As you resolve issues, move them to the closed issues section and keep the issue ID the same.  Include an explanation of the resolution.

When this work product is complete, any open issues should be transferred to the project- or process-level Issue Log (Manage focus area) and managed using a project level Issue Form (Manage focus area).  In addition, the open items should remain in the open issues section of this work product, but flagged in the resolution column as being transferred.

Open Issues

 

ID	Issue	Resolution	Responsibility	Target Date	Impact Date
1
2
3.
4

 

Closed Issues

 

ID	Issue	Resolution	Responsibility	Target Date	Impact Date
1
2
3.
4