CV-070 TDC OEBS R12 D17 Vendors Notes v2.1

CV.
070 Dataconversion Specs
Doc Ref: D30

20 February 2008
AIM
CV.070 DATACONVERSION
SPECS
TDC
D17: Vendors and Notes
(Included D63 and D64)
Author
Uppalapati Vidya Sagarbabu
Creation Date
21 September 2007
Last Updated
20 February 2008
Document Ref
D17
Version
2.1
Approvals:
Mette Hauberg
Andrea Cobis

File Ref: 308982221.doc
CV.070 Dataconversion Specs
Doc Ref: D30

20 February 2008
Document Control
Change Record
14
Date
Author
Versio
n
Change Reference
21-Sep07
10-Oct-07
Uppalapati Vidya
Sagarbabu
Somenath
Bhattacharya
Somenath
Bhattacharya
Uppalapati Vidya
Sagarbabu
Uppalapati Vidya
Sagarbabu
Uppalapati Vidya
Sagarbabu
0.1
No Previous Document
1.1
Added Mapping Rule
1.2
Table/Column Mapping modified
1.3
308982221.doc
Modified as per Andreas Comments
Updated as per the Import of Vendors for Unit
test cases
Updated as per the new changes from TDC.
23-Oct-07
14-Nov07
7-Jan-08
20-Feb-08
2.0
2.1
Reviewers
Name
Position
Andrea Cobis
Subramya VS Peddada
Somenath Bhattacharya
Soeren Gustafsen
Maria Jolanta Pedersen
Mariko Hyllested
IBM, DTC PM
IBM, DTC Teamlead
IBM, DTC KOS Functional Consultant
IBM, DTC Teamlead
IBM, KOS responsible
TDC, KOS responsible
Distribution
Copy
No.
Name
Location
1
2
3
4
Library Master
Jesper Mortensen
Hanne Juel Larsen
DataConversion Team
Project Library
Project Manager, IBM
Project Manager, TDC
IBMIN
Note to Holders:
If you receive an electronic copy of this document and print it out, please
write your name on the equivalent of the cover page, for document
control purposes.
If you receive a hard copy of this document, please write your name on
the front cover, for document control purposes.

Doc Ref: D30

20 February 2008
Contents
Document Control.......................................................................................2
General....................................................................................................... 4
Scope.................................................................................................... 4
Basic Business Needs............................................................................5
Definitions............................................................................................. 5
Major Features.......................................................................................5
Expected Volumes.................................................................................6
User Procedures....................................................................................6
Assumptions..........................................................................................6
Dependencies.......................................................................................6
Vendors and Sites Extraction - General Description....................................8
Vendors and Sites..................................................................................8
ORG Limitation......................................................................................8
Screenshots from Source System..........................................................8
Architecture......................................................................................... 10
Extraction Program..............................................................................12
Mapping Rules.....................................................................................13
Translation Rule Sets...........................................................................13
Conversion of Vendors and Sites to R12...................................................14
Prerequisite setups in R12 before importing the Vendor Data into R12
instance............................................................................................... 14
Upload- Vendors and Notes.......................................................................30
Source to Target Mapping....................................................................30
Mapping Rules.......................................................................................... 37
Installation- Vendors.................................................................................34
Installation
this section will be updated in next version. .34
Unit Test.................................................................................................... 38
Test Scenarios.....................................................................................38
Open and Closed Issues for this Deliverable.............................................40
Open Issues......................................................................................... 40
Closed Issues.......................................................................................40

Doc Ref: D30

20 February 2008
General
Topical Essay
This document specifies how data conversion from Oracle TDC R11i to
Oracle TDC R12 will be carried out for the Vendors master data.
The Vendor Master and vendor Sites including notes data from 11i
instance will be extracted to a Flat file generated by UTL_FILE package
and Using sql*loader, the information in the flat file will be uploaded into
custom staging table.
Then the staged data will be loaded into the Supplier interface table by
Custom validation program and by running the Supplier open interface
program, Supplier Information can be populated into the Supplier base
tables in R12 instance.
The Vendors Data Conversion will cover
All the Live Vendor Master data from TDC 11i instance except the
Vendors where Vendor Type = EMPLOYEE.
Create the flat file in .xls or text format.
Upload the flat file data into the staging table
Use the custom program to validate and upload the staging data
into interface table
Run the Supplier open interface to upload vendors data into

Supplier base tables.
Scope
It is TDC responsibility to provide the following:
Data mapping requirements like table/column details.
Conversion rules and requirements need to be specified.
Reconcile source data
Sign off source data
Signoff data conversion
It is IBM responsibility to accomplish the following tasks:

Doc Ref: D30

20 February 2008
Create data Conversion strategy
Create Conversion specification document
Extract data in agreed format
Create conversion program
Load data into staging table(Custom) with load program
Run the custom program to validate and upload the data into
interface tables
Run the open interface to populate the data into base tables
Conversion of Vendors scope contains:

The master data will be extracted to the xls/text file format.
A component that loads the data from the extracted file from 11i
into the Oracle TDC R12 PO Suppliers open interface program, since
the conversion rules defined by TDC have already been applied in a
earlier stage.
A full data-conversion unit test.
Basic Business Needs

With the system going live in R12 instance on May08 (proposed), TDC
wants all Active Vendors and Sites data to be imported from 11i instance
to TDC R12 environment except for the Vendors where Supplier Type
= EMPLOYEE.
Definitions
Flat File
ASCII files to be extracted from KOS.
KOS
KOS is the current financial system for TDC.
Mapping Rules
A group of rules used to generate convert vendors data from 11i KOS to
R12.
Major Features
Conversion of Vendors along with vendor sites master data from Oracle
TDC 11i (KOS) to Oracle TDC R12 through Conversion rules.
Doc Ref: D30

20 February 2008
Data Conversion from Finance system

Master data of Vendors from KOS system are extracted from Oracle 11i to
the flat file and then uploaded into the data base Oracle R12.
Expected Volumes
The number of Records to be selected from 11i instance is expected to be

shown in below
Vendors
Amount of records in
DERP
Vendors
10671
Vendor Sites
70968
Vendor Contacts
1512
Notes
1 (This record is not in

scope of this object )
Table 1. Volume of Vendors data conversion.
User Procedures
N.A.
Assumptions
This design assumes that the following statements are true:
All the required set ups such as defining the look up codes,
currency codes, Ledger, payment terms, tax codes, banks, bank
accounts and necessary system setups etc will be done.
The data elements/fields are to be determined and Extract

specification document will be freeze before extract program
build stage starts.
TDC will provide all necessary licensed software to execute the

project
Dependencies
The following Dependencies need to be taken under consideration before
starting the data conversion activity:-

Setup Dependency-Prerequisite Setups to be done
Doc Ref: D30

20 February 2008
Standard Setups to be done before data conversion
Chart of Account
Ledger
Subledger Accounting Method
Descriptive Flexfields
Payment Terms
Tax Codes
Withholding Tax
Location
Distribution Set
Financial and Payables Options
Data Conversion Dependency-Prerequisite Data conversions to be done

(as per Master list)

Account Valid Values (COA) --- D02
Cross Validations --- D08
Doc Ref: D30

20 February 2008
Vendors and Sites Extraction - General Description

The following section containes the details of the Vendors Extraction
process:
Vendors and Sites

This conversion is designed to convert all the Vendors master data from
Oracle TDC 11i to Oracle TDC R12 from the following Base Tables from
KOS:
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
AP_NOTES
The Extract will be done considering the following
All vendors where (END_DATE_ACTIVE>date or is null) and
VENDOR_TYPE_LOOKUP_CODE <> ""EMPLOYEE""
All Active PAY sites and PURCHASING sites for the active
suppliers need to be converted.
SELECT * FROM PO_VENDORS

WHERE ENABLED_FLAG = Y
AND END_DATE_ACTIVE IS NULL
AND VENDOR_TYPE_LOOKUP_CODE! = EMPLOYEE
ORG Limitation
The Supplier Sites are to be extracted for the following orgs:Only extract for org_id's (DERP): 1, 2, 3, 4, 12, 13, 363, 2531, 2631, 3351, 3371, and
3491.
PERP: notice that org_id for company 209 is not the same as in DERP (3491). Org_id in
PERP is = 3511.
Screenshots from Source System

The following screeshots taken from the Source system illustrate the
organization of data in E-Business Suite for Vendors and sites.
Supplier header data as follows

Doc Ref: D30

20 February 2008
DFF segments structure in the supplier Header form is as follows
Screenshot for Supplier Sites
Screenshot for Supplier Site DFF structure

Doc Ref: D30

20 February 2008
Architecture
All the master data of PO Vendors, Vendor Sites and Vendor Contacts from KOS to
external source system such as flat file can be done by executing the Extract
program. This Extract Program generates the flat file in .xls.
The data mapping of table/column with flat file will be done, and the entire mapped
master data will be loaded into Vendors Staging table/tables. After the required
validations, use the custom program to upload the vendor master data into
interface table AP_SUPPLIERS_INT, AP_SUPPLIER_SITES_INT and
AP_SUP_SITE_CONTACT_INT. Then run the Supplier open interface to populate the
master data into base tables.
The Steps are as follows,
Extracting Supplier Header and Site data into the flat file.
Loading data into staging table
Use the custom program to upload the staging table data into Interface table
AP_SUPPLIERS_INT for Supplier Header, AP_SUPPLIER_SITES_INT for Supplier Site
and AP_SUP_SITE_CONTACT_INT for Supplier Contacts.
Run Supplier Open interface to populate the data into base tables
Steps are described as below.

Extracting the data into flat file
The vendor and vendor sites master data will be extracted from oracle
R11 using UTL_FILE package
Loading data into staging table

10
Doc Ref: D30

20 February 2008
Loading data into the custom staging table using a control file from a
flat file with the help of the feeder mechanism (SQL*LOADER).
Use the Custom program to upload the staging data into

the interface table
Run the custom program to validate and upload the staging data
into supplier interface table AP_SUPPLIERS_INT.
into supplier site interface table AP_SUPPLIER_SITES_INT.
into supplier contacts interface table AP_SUP_SITE_CONTACT_INT.
Run Supplier Open interface to populate the data
into base tables

Run Supplier Open Interface Import program to

populate the Supplier Header data into base table
(AP_SUPPLIERS)
Run Supplier Sites Open Interface Import program

to populate Supplier Site data into base table
(AP_SUPPLIER_SITES_ALL)
Run Supplier Site Contacts Open Interface Import

program to populate Supplier site contact data into
base table (AP_SUPPLIER_CONTACTS)
11
Doc Ref: D30

20 February 2008
Figure: PO Vendors Data Conversion program flow.
Extraction Program
All the extraction programs will be registered as concurrent programs in the legacy system.
12
Doc Ref: D30

20 February 2008
The Extract code can be found in the below attachment.
XXCV_D17_VEN_NOT
ES_DE_PKG.zip
Mapping Rules
Mapping Rule 1:
Currently in 11i, there are seven SOBs for 7 balancing segments,
201,209,200,110,204,304 and 203. Except SOB- Kabel TV
(company 203), all other SOBs will be merged to TDC ONE
COMPANY LEDGER.
The Operating Units and Balancing segments will have one to one
mapping
Balancerende
201
Segment
Operating
Units
Kabel
TV
TV
TDC One company
Ledgers
Mobil
Norden
209
Erhver
v
Norden
200
110
204
Fastne
t
Norden
Koncer
n
Stabe
IT
Norde
n
304
203
Interrnati
.
Holding
Kabe
l
TV
Translation Rule Sets

The following rule sets are needed for translating the 11i Vendor
extraction to R12 from Danish to English.
Rules and attached files for transalation from Danish to English can be
found in the mapping section in this document.

13
Doc Ref: D30

20 February 2008
Conversion of Vendors and Sites to R12

Prerequisite setups in R12 before importing the Vendor Data into
R12 instance
The following setups are mandatory in R12 instance before executing the
Supplier Open Interface program.
Chart of Account
Ledger
Subledger Accounting Method
Descriptive Flexfields
Payment Terms
Tax Codes
Withholding Tax
Location
Distribution Set
Financial and Payables Options
The following section describes the:

Detailed data mapping from the 11i to the OracleApplicationsR12.
File layout to be used for extraction of the data from 11i system.
14
Doc Ref: D30

20 February 2008
Upload- Vendors and Notes

The following section describes the upload part.
Table/Column mapping
Source to Target Mapping
The following section details the source to target table mapping.
All vendors where

(END_DATE_ACTIVE>date or is null) and
VENDOR_TYPE_LOOKUP_CODE <> "EMPLOYEE"
Number of vendors is 16184 pr. 27 Sep 2007.
(Note: The table column mapping shows the data fields for Vendors, Vendor
sites, Contacts and Notes. As per as recent versions of the master list, sites
and Contacts are not under the go by PM=y list, however this document is
designed assuming that the sites and contacts also under scope, since there
is no much impact on extract part and to fecilitate the doc completely when
ever the sites and contacts also needed. If not the doc will be updated in the
later versions accordingly).
Source: PO_VENDORS
Target Table: XXCV_D17_PO_VENDORS_STG
Se
q.
Source: PO_VENDORS
Target: XXCV_D17_PO_VENDORS_STG
Column Name
Table Name
Column Name
Data Type
VENDOR_ID
XXCV_D17_PO_VENDORS_STG
VENDOR_ID
NUMBER
VENDOR_NAME
VENDOR_NAME
VARCHAR2
VENDOR_NAME_ALT
VENDOR_NAME_ALT
VARCHAR2
SEGMENT1
NUMBER
SUMMARY_FLAG
SUPPLIER_NUM_SEG1
SUMMARY_FLAG
ENABLED_FLAG
ENABLED_FLAG
VARCHAR2
EMPLOYEE_ID
EMPLOYEE_NAME
VARCHAR2
VENDOR_TYPE_LOOKUP_CODE
VENDOR_TYPE_LOOKUP_CODE
VARCHAR2
CUSTOMER_NUM
CUSTOMER_NUM
VARCHAR2
ONE_TIME_FLAG
ONE_TIME_FLAG
VARCHAR2
MIN_ORDER_AMOUNT
MIN_ORDER_AMOUNT
NUMBER
SHIP_TO_LOCATION_ID
SHIP_TO_LOCATION_CODE
VARCHAR2
BILL_TO_LOCATION_ID
BILL_TO_LOCATION_CODE
VARCHAR2
SHIP_VIA_LOOKUP_CODE
VARCHAR2
FREIGHT_TERMS_LOOKUP_CODE
VARCHAR2
FOB_LOOKUP_CODE
FOB_LOOKUP_CODE
VARCHAR2
TERMS_ID
TERMS_NAME
VARCHAR2
SET_OF_BOOKS_ID
LEDGER_NAME
VARCHAR2
ALWAYS_TAKE_DISC_FLAG
VARCHAR2
PAY_DATE_BASIS_LOOKUP_CODE
VARCHAR2
PAY_GROUP_LOOKUP_CODE
VARCHAR2
PAYMENT_PRIORITY
PAYMENT_PRIORITY
NUMBER
VARCHAR2
30
Doc Ref: D30

20 February 2008
INVOICE_CURRENCY_CODE
VARCHAR2
PAYMENT_CURRENCY_CODE
VARCHAR2
INVOICE_AMOUNT_LIMIT
VARCHAR2
HOLD_ALL_PAYMENTS_FLAG
VARCHAR2
HOLD_FUTURE_PAYMENTS_FLAG
VARCHAR2
HOLD_REASON
HOLD_REASON
VARCHAR2
DISTRIBUTION_SET_ID
ACCTS_PAY_CODE_COMBINATIO
N_ID
DISTRIBUTION_SET_NAME
VARCHAR2
ACCT_PAY_SEG1
VARCHAR2
ACCT_PAY_SEG2
VARCHAR2
ACCT_PAY_SEG3
VARCHAR2
ACCT_PAY_SEG4
VARCHAR2
ACCT_PAY_SEG5
VARCHAR2
ACCT_PAY_SEG6
VARCHAR2
ACCT_PAY_SEG7
VARCHAR2
ACCT_PAY_SEG8
VARCHAR2
ACCT_PAY_SEG9
VARCHAR2
ACCT_PAY_SEG17
VARCHAR2
ACCT_PAY_SEG11
VARCHAR2
PREPAY_SEG1
VARCHAR2
PREPAY_SEG2
VARCHAR2
PREPAY_SEG3
VARCHAR2
PREPAY_SEG4
VARCHAR2
PREPAY_SEG5
VARCHAR2
PREPAY_SEG6
VARCHAR2
PREPAY_SEG7
VARCHAR2
PREPAY_SEG8
VARCHAR2
PREPAY_SEG9
VARCHAR2
PREPAY_SEG17
VARCHAR2
VARCHAR2
ORGANIZATION_TYPE_LOOKUP_C
ODE
VAT_CODE
PREPAY_SEG11
ORGANIZATION_TYPE_LOOKUP_C
ODE
VAT_CODE
START_DATE_ACTIVE
START_DATE_ACTIVE
DATE
END_DATE_ACTIVE
MINORITY_GROUP_LOOKUP_COD
E
PAYMENT_METHOD_LOOKUP_CO
DE
WOMEN_OWNED_FLAG
END_DATE_ACTIVE
MINORITY_GROUP_LOOKUP_COD
E
DE
WOMEN_OWNED_FLAG
DATE
SMALL_BUSINESS_FLAG
SMALL_BUSINESS_FLAG
VARCHAR2
STANDARD_INDUSTRY_CLASS
STANDARD_INDUSTRY_CLASS
VARCHAR2
HOLD_FLAG
HOLD_FLAG
VARCHAR2
PURCHASING_HOLD_REASON
PURCHASING_HOLD_REASON
VARCHAR2
TERMS_DATE_BASIS
TERMS_DATE_BASIS
VARCHAR2
INSPECTION_REQUIRED_FLAG
INSPECTION_REQUIRED_FLAG
VARCHAR2
RECEIPT_REQUIRED_FLAG
RECEIPT_REQUIRED_FLAG
VARCHAR2
QTY_RCV_TOLERANCE
QTY_RCV_TOLERANCE
VARCHAR2
QTY_RCV_EXCEPTION_CODE
ENFORCE_SHIP_TO_LOCATION_C
ODE
DAYS_EARLY_RECEIPT_ALLOWED
QTY_RCV_EXCEPTION_CODE
ENFORCE_SHIP_TO_LOCATION_C
ODE
DAYS_EARLY_RECEIPT_ALLOWED
VARCHAR2
DAYS_LATE_RECEIPT_ALLOWED
RECEIPT_DAYS_EXCEPTION_COD
E
ALLOW_SUBSTITUTE_RECEPTS_F
LAG
DAYS_LATE_RECEIPT_ALLOWED
RECEIPT_DAYS_EXCEPTION_COD
E
ALLOW_SUBSTITUTE_RECEPTS_F
LAG
NUMBER
PREPAY_CODE_COMBINATION_ID
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
NUMBER
VARCHAR2
VARCHAR2
31
Doc Ref: D30

20 February 2008
ALLOW_UNORDERED_RECEIPTS_
FLAG
HOLD_UNMATCHED_INVOICES_F
LAG
EXCLUSIVE_PAYMENT_FLAG
ALLOW_UNORDERED_RECEIPTS_
FLAG
LAG
AP_TAX_ROUNDING_RULE
VARCHAR2
AUTO_TAX_CALC_FLAG
AUTO_TAX_CALC_FLAG
VARCHAR2
AUTO_TAX_CALC_OVERRIDE
VARCHAR2
AMOUNT_INCLUDES_TAX_FLAG
VARCHAR2
TAX_VERIFICATION_DATE
TAX_VERIFICATION_DATE
DATE
NAME_CONTROL
NAME_CONTROL
VARCHAR2
STATE_REPORTABLE_FLAG
STATE_REPORTABLE_FLAG
VARCHAR2
FEDERAL_REPORTABLE_FLAG
FEDERAL_REPORTABLE_FLAG
VARCHAR2
ATTRIBUTE_CATEGORY
ATTRIBUTE_CATEGORY
VARCHAR2
ATTRIBUTE1
UND_ATTR1
VARCHAR2
ATTRIBUTE4
EAN_ATTR4
VARCHAR2
ATTRIBUTE5
LOB_ATTR5
VARCHAR2
ATTRIBUTE6
MOM_ATTR6
VARCHAR2
ATTRIBUTE17
ISO_ATTR17
VARCHAR2
ATTRIBUTE11
MIL_ATTR11
VARCHAR2
ATTRIBUTE12
ETI_ATTR12
VARCHAR2
ATTRIBUTE15
SMA_ATTR15
VARCHAR2
VAT_REGISTRATION_NUM
AUTO_CALCULATE_INTEREST_FL
AG
EXCLUDE_FREIGHT_FROM_DISC
OUNT
TAX_REPORTING_NAME
AUTO_CALCULATE_INTEREST_FL
AG
OUNT
TAX_REPORTING_NAME
VARCHAR2
ALLOW_AWT_FLAG
ALLOW_AWT_FLAG
VARCHAR2
AWT_GROUP_NAME
AWT_GROUP_NAME
VARCHAR2
EDI_TRANSACTION_HANDLING
VARCHAR2
EDI_PAYMENT_METHOD
EDI_PAYMENT_METHOD
VARCHAR2
EDI_PAYMENT_FORMAT
EDI_PAYMENT_FORMAT
VARCHAR2
EDI_REMITTANCE_METHOD
VARCHAR2
EDI_REMITTANCE_INSTRUCTION
VARCHAR2
BANK_CHARGE_BEARER
BANK_CHARGE_BEARER
VARCHAR2
MATCH_OPTION
MATCH_OPTION
VARCHAR2
FUTURE_DATED_PAYMENT_CCID
FUTURE_DATED_SEG1
VARCHAR2
FUTURE_DATED_SEG2
VARCHAR2
FUTURE_DATED_SEG3
VARCHAR2
FUTURE_DATED_SEG4
VARCHAR2
FUTURE_DATED_SEG5
VARCHAR2
FUTURE_DATED_SEG6
VARCHAR2
FUTURE_DATED_SEG7
VARCHAR2
FUTURE_DATED_SEG8
VARCHAR2
FUTURE_DATED_SEG9
VARCHAR2
FUTURE_DATED_SEG17
VARCHAR2
FUTURE_DATED_SEG11
VARCHAR2
CREATE_DEBIT_MEMO_FLAG
VARCHAR2
OFFSET_TAX_FLAG
OFFSET_TAX_FLAG
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
32
Doc Ref: D30

20 February 2008
Source: PO_VENDOR_SITES_ALL
Target Table: XXCV_D17_PO_VENDOR_SITES_STG
Se
q.
Source:
PO_VENDOR_SITES_ALL
Target: XXCV_D17_PO_VENDOR_SITES_STG
Column Name
Table Name
Column Name
Data Type
VENDOR_ID
XXCV_D17_PO_VENDOR_SITES
_STG
VENDOR_ID
NUMBER
VENDOR_SITE_ID
VENDOR_SITE_ID
NUMBER
VENDOR_SITE_CODE
VENDOR_SITE_CODE
VARCHAR2
VENDOR_SITE_CODE_ALT
VENDOR_SITE_CODE_ALT
VARCHAR2
PURCHASING_SITE_FLAG
PURCHASING_SITE_FLAG
VARCHAR2
RFQ_ONLY_SITE_FLAG
RFQ_ONLY_SITE_FLAG
VARCHAR2
PAY_SITE_FLAG
PAY_SITE_FLAG
VARCHAR2
ATTENTION_AR_FLAG
ATTENTION_AR_FLAG
VARCHAR2
ADDRESS_LINE1
ADDRESS_LINE1
VARCHAR2
ADDRESS_LINES_ALT
ADDRESS_LINES_ALT
VARCHAR2
ADDRESS_LINE2
ADDRESS_LINE2
VARCHAR2
ADDRESS_LINE3
ADDRESS_LINE3
VARCHAR2
CITY
CITY
VARCHAR2
STATE
STATE
VARCHAR2
ZIP
ZIP
VARCHAR2
PROVINCE
PROVINCE
VARCHAR2
COUNTRY
COUNTRY
VARCHAR2
AREA_CODE
AREA_CODE
VARCHAR2
PHONE
PHONE
VARCHAR2
CUSTOMER_NUM
CUSTOMER_NUM
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
FOB_LOOKUP_CODE
FOB_LOOKUP_CODE
VARCHAR2
INACTIVE_DATE
INACTIVE_DATE
DATE
FAX
FAX
VARCHAR2
FAX_AREA_CODE
FAX_AREA_CODE
VARCHAR2
TELEX
VARCHAR2
DE
TERMS_DATE_BASIS
TELEX
DE
TERMS_DATE_BASIS
VAT_CODE
VAT_CODE
VARCHAR2
VARCHAR2
ACCTS_PAY_CODE_COMBINATIO
N_ID
ACCT_PAY_SEG1
VARCHAR2
ACCT_PAY_SEG2
VARCHAR2
ACCT_PAY_SEG3
VARCHAR2
ACCT_PAY_SEG4
VARCHAR2
ACCT_PAY_SEG5
VARCHAR2
ACCT_PAY_SEG6
VARCHAR2
ACCT_PAY_SEG7
VARCHAR2
ACCT_PAY_SEG8
VARCHAR2
ACCT_PAY_SEG9
VARCHAR2
ACCT_PAY_SEG17
VARCHAR2
ACCT_PAY_SEG11
VARCHAR2
VARCHAR2
VARCHAR2
33
Doc Ref: D30

20 February 2008
PREPAY_CODE_COMBINATION_ID
PREPAY_SEG1
VARCHAR2
PREPAY_SEG2
VARCHAR2
PREPAY_SEG3
VARCHAR2
PREPAY_SEG4
VARCHAR2
PREPAY_SEG5
VARCHAR2
PREPAY_SEG6
VARCHAR2
PREPAY_SEG7
VARCHAR2
PREPAY_SEG8
VARCHAR2
PREPAY_SEG9
VARCHAR2
PREPAY_SEG17
VARCHAR2
PREPAY_SEG11
VARCHAR2
VARCHAR2
PAYMENT_PRIORITY
PAYMENT_PRIORITY
VARCHAR2
TERMS_ID
TERMS_NAME
VARCHAR2
NUMBER
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
HOLD_REASON
LAG
HOLD_REASON
LAG
VARCHAR2
AUTO_TAX_CALC_FLAG
AUTO_TAX_CALC_FLAG
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
TAX_REPORTING_SITE_FLAG
TAX_REPORTING_SITE_FLAG
VARCHAR2
ATTRIBUTE_CATEGORY
ATTRIBUTE_CATEGORY
VARCHAR2
ATTRIBUTE1
ATTRIBUTE1
VARCHAR2
ATTRIBUTE3
ATTRIBUTE3
VARCHAR2
ATTRIBUTE4
ATTRIBUTE4
VARCHAR2
ATTRIBUTE5
ATTRIBUTE5
VARCHAR2
ATTRIBUTE6
ATTRIBUTE6
VARCHAR2
ATTRIBUTE7
ATTRIBUTE3
VARCHAR2
ATTRIBUTE8
ATTRIBUTE8
VARCHAR2
ATTRIBUTE17
ATTRIBUTE17
VARCHAR2
ATTRIBUTE11
ATTRIBUTE11
VARCHAR2
ATTRIBUTE12
ATTRIBUTE12
VARCHAR2
ATTRIBUTE15
OUNT
ATTRIBUTE15
OUNT
VARCHAR2
OPERATING_UNIT_NAME
OPERATING_UNIT_NAME
VARCHAR2
ADDRESS_LINE4
ADDRESS_LINE4
VARCHAR2
COUNTY
COUNTY
VARCHAR2
ADDRESS_STYLE
ADDRESS_STYLE
VARCHAR2
LANGUAGE
LANGUAGE
VARCHAR2
ALLOW_AWT_FLAG
ALLOW_AWT_FLAG
VARCHAR2
AWT_GROUP_NAME
AWT_GROUP_NAME
VARCHAR2
VARCHAR2
EDI_ID_NUMBER
EDI_ID_NUMBER
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
VARCHAR2
34
Doc Ref: D30

20 February 2008
EDI_PAYMENT_METHOD
EDI_PAYMENT_METHOD
VARCHAR2
EDI_PAYMENT_FORMAT
EDI_PAYMENT_FORMAT
VARCHAR2
VARCHAR2
BANK_CHARGE_BEARER
BANK_CHARGE_BEARER
VARCHAR2
VARCHAR2
PAY_ON_CODE
PAY_ON_RECEIPT_SUMMARY_CO
DE
ECE_TP_LOCATION_CODE
PAY_ON_CODE
PAY_ON_RECEIPT_SUMMARY_CO
DE
ECE_TP_LOCATION_CODE
VARCHAR2
PCARD_SITE_FLAG
PCARD_SITE_FLAG
VARCHAR2
MATCH_OPTION
MATCH_OPTION
VARCHAR2
COUNTRY_OF_ORIGIN_CODE
COUNTRY_OF_ORIGIN_CODE
VARCHAR2
FUTURE_DATED_PAYMENT_CCID
FUTURE_DATED_SEG1
VARCHAR2
FUTURE_DATED_SEG2
VARCHAR2
FUTURE_DATED_SEG3
VARCHAR2
FUTURE_DATED_SEG4
VARCHAR2
FUTURE_DATED_SEG5
VARCHAR2
FUTURE_DATED_SEG6
VARCHAR2
FUTURE_DATED_SEG7
VARCHAR2
FUTURE_DATED_SEG8
VARCHAR2
FUTURE_DATED_SEG9
VARCHAR2
FUTURE_DATED_SEG17
VARCHAR2
VARCHAR2
VARCHAR2
FUTURE_DATED_SEG11
VARCHAR2
VARCHAR2
OFFSET_TAX_FLAG
OFFSET_TAX_FLAG
VARCHAR2
SUPPLIER_NOTIF_METHOD
SUPPLIER_NOTIF_METHOD
VARCHAR2
EMAIL_ADDRESS
EMAIL_ADDRESS
VARCHAR2
REMITTANCE_EMAIL
REMITTANCE_EMAIL
VARCHAR2
PRIMARY_PAY_SITE_FLAG
PRIMARY_PAY_SITE_FLAG
VARCHAR2
Source: PO_VENDOR_CONTACTS
Target Table: XXCV_D17_PO_VENDOR_CONTACTS_STG
Se
q.
Source:
PO_VENDOR_SITES_ALL
Target: XXCV_D17_PO_VENDOR_SITES_STG
Column Name
Table Name
Column Name
Data Type
VENDOR_ID
XXCV_D17_PO_VENDOR_CONT
ACTS_STG
VENDOR_ID
NUMBER
VENDOR_SITE_ID
VENDOR_SITE_ID
NUMBER
VENDOR_SITE_CODE
VENDOR_SITE_CODE
VARCHAR2
OPERATING_UNIT_NAME
OPERATING_UNIT_NAME
VARCHAR2
INACTIVE_DATE
INACTIVE_DATE
DATE
FIRST_NAME
FIRST_NAME
VARCHAR2
MIDDLE_NAME
MIDDLE_NAME
VARCHAR2
LAST_NAME
LAST_NAME
VARCHAR2
35
Doc Ref: D30

20 February 2008
PREFIX
PREFIX
VARCHAR2
TITLE
TITLE
VARCHAR2
MAIL_STOP
MAIL_STOP
VARCHAR2
AREA_CODE
AREA_CODE
VARCHAR2
PHONE
PHONE
VARCHAR2
CONTACT_NAME_ALT
CONTACT_NAME_ALT
VARCHAR2
FIRST_NAME_ALT
FIRST_NAME_ALT
VARCHAR2
LAST_NAME_ALT
LAST_NAME_ALT
DEPARTMENT
VARCHAR2
DEPARTMENT
VARCHAR2
36
Doc Ref: D30

20 February 2008
Mapping Rules
Mapping of Suppliers and Supplier sites
1) Vendor IDs and Vendor Sites ID must begin with 6.000.000 (six millions).
The related sequences must be updated before starting the upload.
2) R11i vendor_ID 5014116, 5014113, 5046240, 5013619, 5014114,
5014111 and 5123182 must not be converted.
3) Vendor Sites: Active sites in company 110 must be created in the
correspondent organizations in companies 110, 200, 201, 204, 209 and 304
in R12 (Mariko/Maria tp define this model in DERP before the
extraction).Active sites in companies 120, 203, 220, 298 and 299 in R11i
must be converted 1-1 in R12 (not affected by One-Company).
4) For account combinations at vendor site level: If segment 4 = E segment
3 must be changed to 44150. If segment 4 = K, segment 3 must be changed
to 45150. We don't need to store the original values.
5) Mapping rules for payment methods (old global
bank_accounts), bill to locations, and Payment Terms:
Bill to location.xls
Payment Method.xls
attribute20
on
Payment Terms
R12.xls
6) The global attributes on the R11i bank account tables must be mapped
otherwise in R12: for example global attribute 20 must be copied over the
field "Payment Method" in the supplier sites tabel. Other global attributes to
be investigated (Andrea to provide a list with values not null).
Rules:
Rule 1
All Active Suppliers and Supplier

Sites are to be extracted
Rule 2
Suppliers with Vendor Type =

EMPLOYEE should not be extracted.
Rule 3
Supplier Sites to be extracted only

for org_ids: 1, 2, 3, 4, 12, 13, 363,
2531, 2631, 3351, 3371, 3511.
Mapping of org items to One company:

All the objects follow the mapping of the organization, described in the spreadsheet R11 vs R12
organisation structure.
37
Doc Ref: D30

20 February 2008
Operati
ng Unit
Org
Org Org
code type
New
value
in
segme
nt 1
(Virkso
mheds
nr)
New
Operating
value
Unit
in
segme
nt 2
(Ansva
rsomr
de)
Org
Org
code
Split is done
38
Doc Ref: D30

20 February 2008
Mobil
Norden
Mobil
Lager
Mobil
Mobil
Central
Norden lager
Mobil
Mobil
Norden Transit
Erhverv Erhverv
Norden Lager
Total
Total
Lsning Lsning
er
er Lager
7920
ML
201
Koncern
Stabe
Koncern
Stabe
Erhverv
Norden
Mobil
Lager
Stabe
Centrallag
er
Stabe
Transit
Erhverv
Lager
Fastnet
Norden
Fastnet
Lager
FL
Erhverv
Norden
Erhverv
Lager
EL
Mobil Norden
Mobil
Lager
ML
Koncern
Stabe
Stabe
Centrallag
er
SC
Mobil Norden
6814
MC
110
6814
MT
110
4088
EL
209
ML
SC
ST
EL
8013
TL
200
4088
Total
Total
Lsning Lsning
er
er Lager TL
209
7920
Total
Total
Lsning Lsning
er
er Lager
Total
Lsning
Total
er
Lsning Central
er
lager
Total
Total
Lsning
Lsning er
er
Transit
Service Service
s
s VAL
Total
Total
Lsning Lsning
er
er VAL
TL
201
6814
TC
110
6814
TT
110
6843
SVA
110
Koncern
Stabe
Koncern
Stabe
Stabe
Transit
ST
Stabe VAL SVA
6843
TVA
110
Koncern
Stabe
Stabe VAL SVA
Koncern
Stabe
Stabe
Lager
SL
IT Norden
IT Lager
IL
Koncern
Stabe
Koncern
Stabe
Stabe
Centrallag
er
SC
Stabe
Transit
ST
Koncern
Stabe
Stabe
Vrksted
lborg
SV1
Koncern
Stabe
Stabe
Vrksted
rhus SV2 SV2
Koncern
Stabe
Stabe
Vrksted
Produktion SV3
6814
Service Service
s
s Lager
SL
110
6614
Service Service
s
s Lager
Service
s
Service Centrall
s
ager
Service Service
s
s Transit
Service
s
Vrkste
Service d rhus
s
SV1
Service
s
Vrkste
Service d rhus
s
SV2
Service
s
Vrkste
d
Service Produkti
s
on
All the items from TL

should be assigned
to FL
not already assigned
to EL should be
assigned to EL.
not already assigned
to ML should be
assigned to ML.
SL
204
The items should be

assigned to both SL
and to IL
The items should be
assigned to both SL
and to IL
6814
SC
110
ST
110
6814
6833
SV1
110
SV1
6997
SV2
110
6834
SV3
110
39
Doc Ref: D30

20 February 2008
Kabel
TV
Kabel
TV
Kabel
TV
Kabel
TV
Mobil
Norde
n
Erhver
v
Norde
n
Total
Lsnin
ger
Total
Lsning
er
Total
Lsning
er
Service
s
Service
s
Mobile
Internati
onal
Kabel
TV
Kabel
TV
Lager
Kabel
TV
Centrall
ager
Kabel
TV
Transit
Kabel
TV
Valcent
er
Mobil
Rekvire
nt
Erhver
v
Rekvire
nt
Total
Lsnin
ger
Rekvire
nt
Total
Lsning
er
Rekvire
nt
Total
Lsning
er
Rekvire
nt
Service
s
Rekvire
nt
Service
s
Rekvire
nt
Mobile
Internati
onal
Rekvire
nt
Kabel
TV
Rekvire
nt
6412
TVL
203
YOUSEE
YOUSEE
Lager
YL
YOUSEE
Centrallag
er
YC
YOUSEE
YOUSEE
Transit
YT
YOUSEE
YOUSEE
Valcenter
YVA
YOUSEE
6412
TVC C
203
6412
TVT
203
6419
KVA
203
MR
201
Mobil
7920 Norden
Mobil
Rekvirent MR
ER
209
Erhverv
4088 Norden
Erhverv
Rekvirent ER
TR
200
Fastnet
8013 Norden
Fastnet
Rekvirent FR
TR
209
Erhverv
4088 Norden
Erhverv
Rekvirent ER
TR
201
Mobil
7920 Norden
Mobil
Rekvirent MR
SR
110
Koncern
6814 Stabe
Stabe
Rekvirent SR
SR
204
6614 IT Norden
IT
Rekvirent IR
304
Internati
onal
Internationa Holding
9296 l Holding
Rekvirent IHR
TVR R
203
6412 YOUSEE
MIR
All items not already

assigned should be
assigned
All items not already
assigned should be
assigned
YOUSEE
Rekvirent YR
40
Doc Ref: D30

20 February 2008
Installation- Vendors
This section will be updated in coming versions.
Implementation Notes
This section describes the needed technical installation and set-up in TDCs
Oracle Application environment in order to implement the extraction
program.
The following should be always specified:
1. List of the files needed
2. Name and location of the input/output files
3. Responsibilities to be used to install and run the extract program.
4. Name and location of the Release file (file.zip) for this out bound
program/Import program.
Installation
this section will be updated in next version
Release file
All files needed for this interface (including functional and technical specs
and installation scripts) are found in the following zip file:
XXCV_D17_yyymmdd_Rn.zip
List of the input/output files
The following file is generated and moved into the specified location by this
Extraction:
Path and Filename
Input/Outp Comments
ut
XXCV_TOP/TDC/data_extraction/
XXCV_D17_Vendors_notes.csv
Responsibilities
The following Responsibilities are required to run this Extraction:
Responsibility name
Standard/Custom Comments
Purchase_Order_SuperUser
Std
Purchase_SuperUser TDC
Custom
Only for Department Managers
34
Doc Ref: D30

20 February 2008
Responsibility name
Standard/Custom Comments
Payables_SuperUser TDC
Custom
System_Administrator
Std
XXCV_Superuser
Custom
Installing the Interface

The following files are required to install this interface in the Oracle Ebusiness Suite:
All *.ctl files

All *.txt files
XXCVD17VENDORSANDNOTES.sh
Comma.sh
Script to create database objects (tables, indexes, views, grants,
synonyms): XXCVD17VENDORSANDNOTES.sql
Script to create error report while data extraction
XXCVD17VENDORSANDNOTES .pks and
XXCVD17VENDORSANDNOTES .pkb
Scripts to create package XXCV_D17_VEN_NOTES_DE_PKG.pks and
XXCV_D17_VEN_NOTES_DE_PKG.pkb for data extraction
Scripts to install and set-up concurrent program
XXCVD17VENDORSANDNOTESCONCPRO.sql
Scripts to create package XXCV_D017_VENDOR_VAL_PKG.pks and
XXCV_D017_VENDOR_VAL_PKG.pkb for loading data into interface
table
Step 1
Make sure the following directories are created as specified below.
$XXCV_TOP/sqlldr/control
$XXCV_TOP/sqlldr/logfiles
$XXCV_TOP/TDC/DC/data
$XXCV_TOP/TDC/DC/data/success
$XXCV_TOP/TDC/DC/data/failed
Then copy and paste the XXCVD17VENDORSANDNOTES.pks and

XXCVD17VENDORSANDNOTES.pkb into the SQL*Plus session. This
should also return messages that they have been created successfully.
Step 2
Register the above package as a concurrent program in source oracle apps
11i system in custom application request group.
Create the request set Vendors and vendorsites contains concurrent
requests XXCV_D17_VEN_NOTES _DE_PKG.pks, XXCV_D17_VEN_NOTES
_DE_PKG.pkb and error report XXCVD17VENDORSANDNOTES.rdf
35
Doc Ref: D30

20 February 2008
Running the Extract Program

Submit the request set from the custom application to run the TDC KOS PO
Vendors and sites and error report to generate, after successful
generation of flat file,
Step 3
Copy all *.ctl files, XXCVD17VENDORSANDNOTES.sh to
$XXCV_TOP/sqlldr/control
1.
2. Copy all *.txt files, comma.sh to $XXCV_TOP/TDC/DC/data

After you copied the file, use telnet to connect to this environment, go to the
directories where the *.sh files are, and change their execute attributes
as follows:
chmod 777 comma.sh

chmod 777 XXCVD17VENDORSANDNOTES.sh
Step 4
Use SQL*Plus to make a connection to the database and copy and paste the
contents of the creation table XXCVD17VENDORSANDNOTES.sql into the
SQL*Plus session.
If everything goes well, a message appears at the end. It should mention
that the table is created successfully.
Step 5
Log on the UNIX server via telnet and execute the following commands to
upload all the input data into a temporary table and all mapping rules into
their respective tables:
source the environment by running the DERP.env shell script
cd $XXCV_TOP/TDC/DC/data/
. comma.sh (not needed if amounts already with a dot as decimal

separator)
cd $XXCV_TOP/sqlldr/control
. XXCVD17VENDORSANDSITES.sh
Step 6
Use SQL*Plus to run the custom program
XXCV_D017_VENDOR_VAL_PKG.pks and
XXCV_D017_VENDOR_VAL_PKG.pkb to validate upload the staging data
into interface tables
Step 7
Run the Supplier open Interface program to populate the interface table
data into the base tables
36
Doc Ref: D30

20 February 2008
Run the Supplier sites Open interface program to populate the interface
table data into the Vendor sites base tables
Run the Supplier Contacts Open interface program to populate the
interface table data into the vendor contacts base tables.
Installing the Forms / Reports

NA.
AP Vendors and sites Data Conversion Post Activities

1) Run the sql scripts and analyze the output, whether the master data
extracted satisfies the extraction rules specified.
2) Log on to Applications and verify the data from the front end, whether
the data extracted is in synch or not with the out put.
3) Count the data in custom staging table and compare the data with target
system and note the count of the data.
37
Doc Ref: D30

20 February 2008
Unit Test
This section describes the unit test for this component.
Test Scenarios
Test case Test Case

Id
3
4
Extract File for

Vendors, Sites and
Contacts Interface
Data Upload to
staging table
Data Upload to
interface table
Run Suppliers
Description
Run the program

xxcv_d17_ven_not
es_de_pkg from
XXCV Superuser
responsibility
Create a sample file
having around five
Vendors from the
total extract file and
run sql loader (Set
the environment
variable NLS_LANG
before running the
sql loader)
The sample data in
the staging table
should be uploaded
to Vendors interface
table after
validation. Vendors
in the staging
table :- 99800400,
9986970,
9976998,14287795,
29523729
Run the suppliers
Expected Result
Actual Result
Unit Test 1 Unit Test 2

(Pass/Fail) (Pass/Fail)
Extract file should be created for

Vendors, Sites, and Contacts with file
name as
XXCV_D17_PO_VENDORS.xls,
XXCV_D17_PO_VENDOR_SITES.xls
and
XXCV_D17_PO_VENDOR_CONTACT
S.xls respectively
Extract file was created as

Pass
XXCV_D17_PO_VENDORS.xls,
XXCV_D17_PO_VENDOR_SITES.x
lsand
XXCV_D17_PO_VENDOR_CONTA
CTS.xls
All the records from the sample file

should be uploaded to staging table
for Vendors, Sites, and Contacts.
All the records from the sample file

was uploaded to the staging table
XXCV_D17_AP_VENDORS_STG,
XXCV_D17_AP_VENDOR_CONT_
STG and
XXCV_D17_AP_VENDOR_SITES_
STG
Pass
Pass
Vendors, Sites and Contacts of the

vendors 99800400, 9986970,
9976998,14287795, 29523729 should
be uploaded to interface table after
validation
Vendors - 99800400, 9986970,
After validations and mappings

against Organization, terms, Liability
code combination, Account pay
code combination the records
uploaded successfully
Vendors - 99800400, 9986970,
38
Doc Ref: D30

20 February 2008
Open Inteface
Run Supplier Sites

Open Interface
Run Supplier
Contacts Open
Interface
interface Import
suppliers from
Payables Manager
User to upload
99800400, 9986970,
9976998,14287795,
29523729 to R12
(MOEBS) system
Run the Supplier
sites Open Interface
from Payables
Manger to Upload
Vendor sites of the
Vendors 99800400,
9986970,
9976998,14287795,
29523729 to R12
(MOEBS) system
Run the Supplier
Contacts Open
Interface from
Payables Manger to
Upload Vendor sites
of the Vendors
99800400, 9986970,
9976998,14287795,
29523729 to R12
(MOEBS) system
Pass
9976998,14287795, 29523729 should

be uploaded to R12 (MOEBS) system
if the interface validation is passed
9976998,14287795, 29523729 was

uploaded into R12(MOEBS)
Pass
Vendors Sites of Vendors 99800400,

9986970, 9976998, 14287795,
29523729 Should be Uploaded to R12
(MOEBS) system if the Interface
validation is passed.
Vendor Sites of Vendros 99800400,

9986970, 9976998,14287795,
29523729 was Uploaded into
R12(MOEBS)
Pass
Vendor Contacts of Vendors

99800400, 9986970, 9976998,
14287795, 29523729 Should be
Uploaded to R12 (MOEBS) system if
the Interface validation is passed.
Vendor Contacts of Vendros

99800400, 9986970,
9976998,14287795, 29523729 was
Uploaded into R12(MOEBS)
39
Doc Ref: D30

20 February 2008
Open and Closed Issues for this Deliverable

Open Issues
ID
Issue
TDC to confirm whether

Vendor sites and
contacts needs to be
converted or not. This
document prepared (as
there is no impact on
extraction) assuming
that vendor sites and
contacts to be
converted. If not, doc
will be updated in the
later versions)
Resolution
Responsibility
Target
Date
Impact Date
TDC
ASAP
Immediate
1.
Closed Issues
ID
Issue
Resolution
Responsibility
Target Date
Impact
Date
40

CV-070 TDC OEBS R12 D17 Vendors Notes v2.1

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CV-070 TDC OEBS R12 D17 Vendors Notes v2.1

Încărcat de

Drepturi de autor:

Formate disponibile

CV.

070 Dataconversion Specs

Doc Ref: D30

Uppalapati Vidya Sagarbabu

D17: Vendors and Notes

CV.070 Dataconversion Specs

Doc Ref: D30

Added Mapping Rule

Table/Column Mapping modified

D17: Vendors and Notes

CV.070 Dataconversion Specs

Doc Ref: D30

this section will be updated in next version. .34

D17: Vendors and Notes

CV.070 Dataconversion Specs

Doc Ref: D30

Create the flat file in .xls or text format.

Upload the flat file data into the staging table

Run the Supplier open interface to upload vendors data into

Data mapping requirements like table/column details.

Conversion rules and requirements need to be specified.

Reconcile source data

Sign off source data

Signoff data conversion

It is IBM responsibility to accomplish the following tasks:

D17: Vendors and Notes

CV.070 Dataconversion Specs

Doc Ref: D30

Create data Conversion strategy

Create Conversion specification document

Extract data in agreed format

Create conversion program

Load data into staging table(Custom) with load program

Conversion of Vendors scope contains:

Basic Business Needs

CV.070 Dataconversion Specs

Doc Ref: D30

Data Conversion from Finance system

The number of Records to be selected from 11i instance is expected to be

1 (This record is not in

Table 1. Volume of Vendors data conversion.

The data elements/fields are to be determined and Extract

TDC will provide all necessary licensed software to execute the

D17: Vendors and Notes

CV.070 Dataconversion Specs

Setup Dependency-Prerequisite Setups to be done

Doc Ref: D30

Standard Setups to be done before data conversion

Subledger Accounting Method

Financial and Payables Options

Data Conversion Dependency-Prerequisite Data conversions to be done

D17: Vendors and Notes

Account Valid Values (COA) --- D02

Cross Validations --- D08

CV.070 Dataconversion Specs

Doc Ref: D30

Vendors and Sites Extraction - General Description

Vendors and Sites

SELECT * FROM PO_VENDORS

Screenshots from Source System

D17: Vendors and Notes

CV.070 Dataconversion Specs

Doc Ref: D30

DFF segments structure in the supplier Header form is as follows