CV40 - Banks and Branches
CV40 - Banks and Branches
CV40 - Banks and Branches
Raj Ashar
1/11/2012
1/11/2012
0.1
Draft
2. Document Control
Document Control
Version
0.1
Final /
Draft
Draft
Release Date
Author
Change Area
Padmaja Moppaneni
Change Detail
First draft - new document
Distribution Record
Distribution Date
336045082.xlsx
Status
Version Number
Distributed to
11/06/2016
2. Document Control
Notes
336045082.xlsx
11/06/2016
3. Index
Section
1.0
2.0
3.0
4.0
4.1
5.0
6.0
7.0
Worksheet
Cover Page
Document Control
Index
Definition
PO Headers
Mapping Rules
Test Cases
Open and Closed Issues
336045082.xlsx
Description
Document Cover Page
Version Control / Distribution Control
Index / Document Contents
Object Definition / Scope / Migration Processing / Steps / Account / Reconciliation
Data definition / mapping for PO Headers
Data Conversion / Transformation Rules & Mappings
Test Cases for Migration Objects
Open and Closed Issues
11/06/2016
4. Definition
This section defines the overall scope of the data migration, including the data extraction
criteria, the migration process and sequence, the pre and post migration steps, the
accounting process/rules and the audit & reconciliation process.
Data Scope
The Data Scope section defines the specific data extraction and load scope for the data
objects covered by this document. Both high-level and detailed scope requirements will be
documented here.
The first sub-section defines the overall scope, which is common for all of the objects.
The second sub-section defines any object specific scope
Common (for all objects)
1
All active banks and braches will be loaded
2
3
4
5
6
Specific
Category
Banks
Object
Data Scope
Detailed Definition
Braches
336045082.xlsx
11/06/2016
4. Definition
336045082.xlsx
11/06/2016
4. Definition
Migration Process
The Migration Process Scope section describes the overall process for the migration of the data objects defined within this document. It
contains the following sub-sections:
Migration Processing - describes the overall migration and transition process
Pre-Migration Steps - defines any business process, application specific or technical steps that must take place prior to migration
Object Sequence
- specifies the sequence in which the data objects must be loaded, plus any eternal dependencies
Post-Migration Steps - defines any business process, application specific or technical steps that must take place following migration
Migration Processing
Mass cancel. Split between PTS and non PTS POs
For PTS: Mass cancel unmatched POs older than 1 month. FSSC to manually close partially match POs
Non PTS: Mass cancel unmatched POs older than 13 months. Buyers to review and close partially and unmatched < 13 months old.
All approved Requisitions to be turned into POs (buyer action)
Step #
1
2
3
Step #
1
2
3
336045082.xlsx
Object
PO Headers
PO Lines
PO Shipments
11/06/2016
4. Definition
4
Step #
1
336045082.xlsx
PO Distributions
11/06/2016
4. Definition
Accounting
The Accounting section defines the process for how any accounting entries are to be generated as part of the load. It also specifies how the
impact of this accounting on the GL balances will be handled (for example, where the generated accounting impacts the GL balances and
the equivalent GL lines are also being migrated, then there would be 'double counting').
Accounting Rules
Duplicate accounting entries between those generated as part of this migration and those migrated as part of the GL balances will be
reversed. This will be performed as follows:
1. .....................etc.
Reconciliation
The reconciliation section defines the process for reconciling the data loaded between the results of the data load and the source data. This
includes ensuring that all accounting reconciles (including GL impacts) and any auditing requirements have been defined and satisfied. The
reconciliation requirements defined in this section will be used as part of the overall signoff of the migration
Ref #
1
2
3
4
5
Object
336045082.xlsx
Description
Audit reports will be generated showing a summary of the whole migration process
Record count would be used to perform end to end recon for all data migration functions.
Spot checks will be performed on ..................
Data comparison between the two systems using the staging tables generated as part of the migration process
etc....
Additional Object Level Reconciliation.
11/06/2016
4. Definition
PO Header
PO Lines
PO
Shipments
PO
Distributions
336045082.xlsx
10
11/06/2016
4. Definition
Rule(s)
336045082.xlsx
Volume(s)
11
11/06/2016
4. Definition
336045082.xlsx
12
11/06/2016
4. Definition
336045082.xlsx
13
11/06/2016
4. Definition
336045082.xlsx
14
11/06/2016
4. Definition
336045082.xlsx
15
11/06/2016
4. Definition
336045082.xlsx
16
11/06/2016
4. Definition
336045082.xlsx
17
11/06/2016
4. Definition
336045082.xlsx
18
11/06/2016
4. Definition
336045082.xlsx
19
11/06/2016
4. Definition
336045082.xlsx
20
11/06/2016
4. Definition
336045082.xlsx
21
11/06/2016
4. Definition
336045082.xlsx
22
11/06/2016
4.1 Banks
The purpose of this section is to document the detailed mapping for a data object from the source data element to the target. For each data element, it includes a list of all fields th
from the source system.
For each element, the details provide are:
- Source Field Name - Field name from the source system (e.g. the 11i field name)
- R12 Field Name
- Name of the R12 field name
- Required
- Specifies whether the load process requires this field as mandatory (i.e. if an API may have a requirement that the field is populated)
- Conversion Logic - Is any data transformation required from source field value to R12? If yes then the mapping logic is then detailed on the Mapping Rules tab
- Ref. Data Column - Identifies whether a field is part of a lookup
- Length & Type
- The length and type of the R12 field
- Description
- Description of the R12 field and its purpose
- Lookup Type / Name - The name of the lookup
- Default Value
- If any, the default value which needs to be passed for this field
- Required for Migration - As part of the R12 solution design, this flag identifies whether this field is required to be migrated. Blank assumes that it is required
- Additional Notes
Overview
This will be used to create header information for the PDOI (Purchase Order Document Open Interface) program to create standard purchase orders and catalog quotations.The P
data, derives or defaults additional information and writes an error message for every validation that fails into the PO_INTERFACE_ERRORS table. Asssumptions are that the follo
PDOI run to create Purchase Order Documents - Master Data for Suppliers , GL Accounting Setup , HR employee names are setup for buyer and requestor data and PO setup iss
Item Categories, Category Sets , Unit of Measure and any Shipping/Classififcation elements required.e.g. Hazard Classes, Approval Groups and Approval Assignments.
Ref
Source
Field Name
Required
Conversion
Logic
Ref. Data
Column
Length &
Type
Country
Mandatory
Number
Bank Name
Mandatory
Char 25
336045082.xlsx
23
23
4.1 Banks
Ref
Source
Field Name
Required
Conversion
Logic
Ref. Data
Column
Length &
Type
Yes
Char 240
Optional
Yes
Char 30
Banck Number
Optional
Char 20
6
7
Decription
Taxpayer ID
Optional
Optional
Number
Date
8
9
Tax Registration
Optional
Number
XML Messages Email Optional
10
Inctive Date
Optional
Date
11
Context Value
Optional
Number
12
Country
Manadatory
336045082.xlsx
Yes
Char 80
Yes
Char 30
Yes
24
Char 240
24
4.1 Banks
Ref
Source
Field Name
Required
Conversion
Logic
Ref. Data
Column
Length &
Type
13
Address Value
Mandatory
14
City
Mandatory
Yes
Char 240
15
16
17
18
County
State
Postal Code
Addresse
Mandatory
Mandatory
Mandatory
Optional
Yes
Yes
Yes
Yes
Char 30
Char 15
Char 15
Char 240
19
20
Status
Geography Code
Override
Optional
Optional
Yes
Yes
Char 60
Char 60
21
Context Value
Optional
Yes
Char 50
22
Prefix
Optional
Yes
Char 25
336045082.xlsx
Char 30
25
25
4.1 Banks
Ref
Source
Field Name
Required
Conversion
Logic
Ref. Data
Column
Length &
Type
23
First Name
Manadatory
24
Middle Name
Optional
25
Last Name
Mandatory
Char 25
26
Suffix
Optional
Date
27
Optional
Date
28
29
30
31
32
Optional
Optional
Optional
Optional
Optional
Number
Char 480
Char 480
Char 240
Number
33
Job Title
Name Initials
Previous Last Name
Alias
Full Name
Pronunciation
Contact Number
Optional
Number
34
Department
Optional
Date
35
Department Code
Optional
Date
336045082.xlsx
Char 25
Yes
26
Char 25
26
4.1 Banks
Ref
Source
Field Name
Required
36
Start Date
Mandatory
37
38
39
End Date
Comments
Context Value
Optional
Optional
Optional
336045082.xlsx
Conversion
Logic
Yes
Ref. Data
Column
Yes
Length &
Type
Char 1
Number
Char 25
Char 15
27
27
4.1 Banks
o the target. For each data element, it includes a list of all fields that will be migrated into R12
to create standard purchase orders and catalog quotations.The PDOI program validates your
PO_INTERFACE_ERRORS table. Asssumptions are that the following are in place before a
e names are setup for buyer and requestor data and PO setup issues are in place - Line Type,
Classes, Approval Groups and Approval Assignments.
Country is
It Identifies whether we are adding the line or
creating a New PO
336045082.xlsx
Default Value
Required for
Migration?
Addtional Notes
28
28
4.1 Banks
R12 Data Specification
Description
Default Value
Required for
Migration?
Addtional Notes
GBP
336045082.xlsx
29
29
4.1 Banks
R12 Data Specification
Description
Default Value
Required for
Migration?
Addtional Notes
336045082.xlsx
30
30
4.1 Banks
R12 Data Specification
Description
Default Value
Required for
Migration?
Addtional Notes
If used it must be a valid Entry in the reference data Must be as per reference
for Freight terms in order to derive the lookup code. data Freight Terms
(fnd_lookup_values =
'FREIGHT TERMS')
Approval status
336045082.xlsx
31
31
4.1 Banks
R12 Data Specification
Description
Default Value
Required for
Migration?
Addtional Notes
336045082.xlsx
Need to confirm
Open
32
Need to be reviewed
Default will be Open
32
4.2 Branches
The purpose of this section is to document the detailed mapping for a data object from the source data element to the target. For each data element, it includes a list of all fields th
migrated into R12 from the source system.
For each element,
Overview
This will be used to create header information for the PDOI (Purchase Order Document Open Interface) program to create standard purchase orders and catalog quotations.The P
validates your data, derives or defaults additional information and wri
Ref
Source
Field Name
Required
Length &
Type
Branch Name
Mandatory
Number
Country is
Alternate Branch
Name
Optional
Char 25
336045082.xlsx
33
33
4.2 Branches
Ref
Source
Field Name
Required
Length &
Type
Optional
Yes
Char 240
Routing Transit
Number
BIC
Optional
Yes
Char 30
Bank Code
Optional
Char 20
6
7
Branch Type
EDI Location
Mandatory
Optional
Number
Date
EFT Number
Optional
Yes
Char 80
Description
Optional
Yes
Char 30
10
RFC Identifier
Optional
Date
11
Inactive Date
Optional
Number
12
Context Value
Optional
336045082.xlsx
Yes
34
Char 240
34
4.2 Branches
Ref
Source
Field Name
Required
13
Country
Mandatory
14
Address Line 1
Mandatory
15
16
City
Length &
Type
Char 30
Yes
Char 240
Mandatory
Mandatory
Yes
Yes
Char 30
Char 15
17
18
County
State
Postal Code
Mandatory
Mandatory
Yes
Yes
Char 15
Char 240
19
Addressee
Optional
Yes
Char 60
20
Status
Optional
Yes
Char 60
21
Identifying Address
Optional
Yes
Char 50
22
Geography Code
Override
Optional
Yes
Char 25
336045082.xlsx
35
35
4.2 Branches
Ref
Source
Field Name
Required
23
Context Value
Optional
24
Prefix
Optional
25
First Name
26
Length &
Type
Char 25
Char 25
Manadatory
Char 25
Approval status
Middle Name
Optional
Date
27
Last Name
Mandatory
Date
28
29
30
31
32
Suffix
Job Title Code
Job Title
Name Initials
Previous Last Name
Optional
Optional
Optional
Optional
Optional
Number
Char 480
Char 480
Char 240
Number
33
Alias
Optional
Number
34
Full Name
Pronunciation
Optional
Date
35
Contact Number
Optional
Date
336045082.xlsx
Yes
36
36
4.2 Branches
Ref
Source
Field Name
Required
36
Department
Optional
37
38
39
Department Code
Start Date
End Date
Optional
Mandatory
Optional
336045082.xlsx
Yes
37
Length &
Type
Char 1
Number
Char 25
Char 15
Cpa Reference
Close status
Gl encumbered period name
37
4.2 Branches
Specification
Lookup Type / Name
Default Value
Required for
Migration?
Addtional Notes
336045082.xlsx
38
38
4.2 Branches
Specification
Lookup Type / Name
Default Value
Required for
Migration?
Addtional Notes
GBP
GL_DAILY_RATES
R12 valid employee name can be provided
that is also a recognised buyer which can be
Validated against the employee migrated.
336045082.xlsx
39
39
4.2 Branches
Specification
Lookup Type / Name
Default Value
Required for
Migration?
Addtional Notes
336045082.xlsx
40
40
4.2 Branches
Specification
Lookup Type / Name
Default Value
Required for
Migration?
Addtional Notes
336045082.xlsx
41
41
4.2 Branches
Specification
Lookup Type / Name
Default Value
Required for
Migration?
Addtional Notes
Must be Y, N or Blank
Need to confirm
336045082.xlsx
Open
Need to be reviewed
Default will be Open
42
42
5. Mapping Rules
This page defines the conversion logic for deriving the R12 field values from the source values. The rules can consist of simple 'match and replace' (e.g. The
value 'YES' in 11i becomes 'Y' in R12), to a full decision table.
For each rule, the following is defined:
- Source Value - The value which exists in the source system and needs to be transformed
- R12 Value
- The value to which the source value needs to be transformed to
- Meaning
- Certain lookups in Oracle are given codes, so this field will give a description of what the code actually means
- Rule Notes
336045082.xlsx
Meaning
Rule Notes
Yes
No
43
11/06/2016
5. Mapping Rules
336045082.xlsx
44
11/06/2016
Return to Index
The following are the high level functional test cases required to validate that the functionality for the data object being migr
ID
Test Case
Details
<Example>
1
2
3
Expected Results
The appropriate project manager is sent a notification
Resolution
Responsibility
Target Date
Impact Date
Resolution
Responsibility
Target Date
Impact Date
Closed Issues
ID
336045082.xlsx
47
11/06/2016
336045082.xlsx
48
11/06/2016