Upload
raghav-seth
View
179
Download
11
Embed Size (px)
Citation preview
Technical Design Document
TECHNICAL DESIGN DOCUMENT
Vendor Conversion
Author:Creation Date: 03/01/2011Last Updated: 04/07/2011 Document Ref: 1.0Version: Draft
Approvals:
Client Tech Lead/Manager
1. Document Control
Change Record
C04.TD.AP.VendorConversion Page 1
Technical Design Document
Date Author Version Change Reference
3/01/2011 1.0 Created
Reviewers
Date Reviewed
Name Position
Distribution
Copy No. Name Location
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.
Table of Contents
1. Document Control.................................................................................................................................................................. 2
1 SUMMARY................................................................................................................................4
C04.TD.AP.VendorConversion Page 2
Technical Design Document
1.1 Requirements Overview.................................................................................................................................................. 4
1.2 Technical Overview......................................................................................................................................................... 4
1.3 Logic Flow....................................................................................................................................................................... 5
1.4 Dependencies and Assumptions...................................................................................................................................... 6
1.5 FTP Information............................................................................................................................................................. 9
2 DATABASE OBJECTS............................................................................................................10
2.1 Data Model.................................................................................................................................................................... 10
2.2 Summary....................................................................................................................................................................... 10
2.3 Details............................................................................................................................................................................ 11
2.4 File Layout – Vendor Record....................................................................................................................................... 11
3 PROCESSES AND INTERFACES IMPACTED......................................................................26
3.1 Summary....................................................................................................................................................................... 26
4 MODULE SPECIFICATIONS..................................................................................................27
4.1 XXDCG_AP_VENDOR_CONV_PKG......................................................................................................................... 28
5 DATA CONVERSION.............................................................................................................31
6 TEST PLAN.............................................................................................................................32
7 OPEN / CLOSED ISSUES......................................................................................................33
8 IMPLEMENTATION NOTES...................................................................................................34
9 Appendix.................................................................................................................................35
C04.TD.AP.VendorConversion Page 3
Technical Design Document
1 SUMMARY
This design document talks about the Vendor Conversion to Oracle AP Suppliers module of E Business Financials from Legacy systems. The design document for the conversion program defines the logic and the key assumption rules as required in order to carry out the Vendor conversion process. This document details various sections in order to provide all the information as required by the Vendor conversion process.
1.1 Requirements Overview
Conversion of vendors from SOAR system to Oracle E Business Suite AP Suppliers. This document describes the technical specifications for data conversion of Legacy Vendors to the Oracle EBS application Payables.
Reference Document Document Name
Functional Design Document C04.FD.PO.Vendors.docx
1.2 Technical Overview
The purpose of this document is to detail the steps for conversion of Vendor data from the SOAR system to Oracle EBusiness Suite AP Suppliers. SOAR system will deliver the Vendor data file in Comma Separated file format as per the layout specifications defined in this document. The conversion program will read the file and perform the necessary validations and import the data into Oracle AP Suppliers.
Conversion Program Details:
The custom request set “XXDCG : Load Vendors” is compromised of two request stages
(1) XXDCG: Read Vendor data File – This program reads the Vendor data file specified by the user (user entered parameter input file name) from $XXDCG_TOP/inbound directory and archives the file. The program then uploads the data into the custom table xxdcg_vendor.
(2) XXDCG: Load Vendor Data – This program validates the vendor data from the custom staging table xxdcg_vendor and derives the necessary default values for the vendors to be imported into Oracle EBS. The vendors are loaded with a status of “POST”. The successfully processed rows are marked with status of ‘S’ in the custom table xxdcg_vendor. Any validation errors encountered are logged in the log file.
The approach for this conversion is to use SQL*Loader to load the flat file data into the custom staging table. Using the PL/SQL package, validate the vendor data and transfer the validated data to Supplier Interface tables.
C04.TD.AP.VendorConversion Page 4
Technical Design Document
1.3 Logic Flow
The following process will be run to load the supplier conversion.
C04.TD.AP.VendorConversion Page 5
Technical Design Document
1.4 Dependencies and Assumptions
Foreign Key Dependencies
None
Parent/Child Dependencies
None
Quick Code Dependencies
None
Data Element Domains
None
Use of Sequence Generators
None
The following are the Vendor load assumptions:
1. The data from the SOAR system will be loaded into the staging tables. Any subsequent corrected data from
2. Only those codes in the flat file will be loaded into the Oracle AP table.
3. All extract development work will be performed by the District.
4. The ASCII extracts will be formatted correctly to allow for direct loading of the files.
5. All validating and reviewing of the AP/PO data on the source systems will ensure
that there are no duplicates and all necessary fields in the data are filled in.
6. District will be responsible for the testing and validation of converted data.
1.4.1 Pre-requisites
The following are the pre-requisites for loading Vendors into Oracle Application.
C04.TD.AP.VendorConversion Page 6
Technical Design Document
The Oracle AP and PO setups must be complete which are as follows:
Vendor Type Lookup Code
Organization Type Lookup Code
Pay Group
Freight Terms
FOB
Payment Method
Payment Terms
Ship Via
The District requires Vendors to be identified.
NOTE: The following steps shown are for verification only. These steps ensure the completion of application setup and configuration.
AP/PO SUPPLIER SETUP:
To see the current setup of Payables Options as it relates to the supplier first go ahead and login as DCG Public Sector Payables Manager and go to Setup->Options->Payables Options .
In order to look at the payables system setup go to Setup->Options->Payables System Setup.
To setup different parts of a vendor start by going to Setup->Lookups->Purchasing and push F11 and put VENDOR TYPE.
Click F11 and put ORGANIZATION TYPE for the Type and then click Ctrl-F11 and you will see the organization types.
Click F11 and put PAY GROUP and then click Ctrl-F11 and you will see the Pay Group.
Click F11 and put FREIGHT TERMS for Type and then click Ctrl-F11 and you will see all of the valid freight terms.
Click F11 and put FOB for Type and then click Ctrl-F11 and you will see all of the valid fob types.
C04.TD.AP.VendorConversion Page 7
Technical Design Document
Close out and go to Setup->Lookups->Payables and click F11 and put PAYMENT METHOD for the TYPE and then click Ctrl-F11 so you can see and add values for payment method.
Close out and then go to Setup->Invoice->Payment Terms and then do a F11 and then a Ctrl-F11 to see the first payment term.
1.5 FTP InformationThe agencies generate the csv file in the format specified in this document and place it on a specific directory <TBD>. This file is transferred to the Oracle EBS Financials Production server <TBD>, which is identified below.
Linux BOX: <TBD> IP ADDRESS: <TBD>UNIX DIRECTORY: $XXDCG_TOP/inbound
C04.TD.AP.VendorConversion Page 8
Technical Design Document
2 Database Objects
2.1 Data Model
None
2.2 Summary
Seq #
Object Name Type Standard / Custom
Description
1 XXDCG_VENDOR_STG.sql Table Custom This table stores the Vendor data to be uploaded to oracle EBS
2 XXDCG_VENDOR_SITES_STG.sql
Table Custom This table stores the Vendor Sites data to be uploaded to oracle EBS
3 XXDCG_VENDOR_SITE_CONTACT_STG.sql
Table Custom This table stores the Vendor Site Contact data to be uploaded to oracle EBS
4 XXDCG_AP_VENDOR_CONVERSION_PKG.pks
PackageSpecification
Custom Program to upload the Vendor data file to oracle EBS
5 XXDCG_AP_VENDOR_CONVERSION_PKG.pkb
PackageBody
Custom Program to upload the Vendor Data file to oracle EBS
C04.TD.AP.VendorConversion Page 9
Technical Design Document
2.3 Details
2.3.1 Conversion Vendor Csv File
2.3.2 Custom tables (Staging tables for Vendor data load)
This table is the staging area for storing the vendor data from the input csv file.
2.4 File Layout – Vendor Record
The following information provides an overview of the file layout. The file contains layouts for all different record types and separated by Field Separator and enclosed by Encapsulator (“”). The fields for each record type are explained below.
Column Name Data Type Size Not Null
Sample Data Primary Key
Index column
C04.TD.AP.VendorConversion Page 10
Technical Design Document
Record Id Character 1 Y ‘V’ No No
System Date Character 9 Y No No
VENDOR_NO No No
VENDOR_NAME Character 240
Y No No
ALT_VENDOR_NAME_1
Character 50 No No
ALT_VENDOR_NAME_2
Character 25 No No
VENTYP Character 25 No No
PMT_DISTN_TYPE Character 2 No No
OWNERSHIP_CODE Character 1 No No
TAX_OFFSET_EXEMPT Character 1 No No
W9_REQUEST_DATE Character 8 No No
UPDATE_DATE Character 8 No No
EFF_START_DATE Character 8 No No
EFF_END_DATE Character 8 No No
UPDATE_NO Number 2 No No
NAME_CONTROL Character 320
No No
BATCH_DEPT Character 3 No No
RESTRICT_MC Character 1 No No
MED_PAY_IND Character 1 No No
LSDBE_IND Character 1 No No
File Layout- Vendor Sites Record plus Vendor Site Contacts Record
The following information provides an overview of the file layout. The file contains layouts for all different record types and separated by Field Separator and enclosed by Encapsulator (“”). The fields for each record type are explained below.
C04.TD.AP.VendorConversion Page 11
Technical Design Document
Column Name Data Type Size Not Null
Sample Data Primary Key
Index column
Record Id Character 1 Y ‘V’ No No
System Date Character 9 Y No No
VENDOR_NO Number 10 No No
ADDRESS_CODE Character 15 No No
ADDRESS_LINE_1 Character 240
No No
ADDRESS_LINE_2 Character 240
No No
CITY Character 25 No No
STATE Character 150
No No
ZIP_CODE_5 Character 20 No No
ZIP_CODE_4 Character 20 No No
PHONE_AREA_CODE Character 10 No No
PHONE_EXC Character 15 No No
PHONE_SEQ Character 15 No No
PHONE_EXT Character 15 No No
PMT_DISTN_TYPE Character 2 No No
TRANSIT_CODE Character 9 No No
ACC_NO Character 17 No No
ACCT_TYPE Character 2 No No
DIR_DEP_DATE Character 8 No No
OWNERSHIP_CODE Character 1 No No
HOLD_REASON_CDE Character 3 No No
COUNTRY Character 20 No No
FAX_AREA_CODE Character 10 No No
FAX_EXC Character 15 No No
FAX_SEQ Character 10 No No
UPDATE_REASON_CODE
Character 4 No No
C04.TD.AP.VendorConversion Page 12
Technical Design Document
OFFSET_TAX_FLAG Character 1 No No
UPDATE_DATE Date No No
CONTACT_NAME Character 25 No No
CONTACT_PHONE Character 14 No No
DUNS_NUMBER Character 30 No No
LSDBE_NO Character 16 No No
2.4.1 Mapping Source Vendor Data to Target Interface Tables in Oracle EBS
Target Column Name(Oracle Column for
AP_SUPPLIERS_INT Interface Table)
Required
Data Type Source Column Validation
Transformation Rules
VENDOR_INTERFACE_ID Y No (derived)
LAST_UPDATE_DATE DATE UPDATE_DATE NoLAST_UPDATED_BY NUMBER No (Username/derived)VENDOR_NAME Y VARCHAR2 VENDOR_NAME No
C04.TD.AP.VendorConversion Page 13
Technical Design Document
VENDOR_NAME_ALT VARCHAR2 VENDOR_ NAME_ALT YesSEGMENT1 VARCHAR2 No System Generated
Automatic numberingSUMMARY_FLAG VARCHAR2 No NULL
ENABLED_FLAG VARCHAR2 No ‘Y’
LAST_UPDATE_LOGIN NUMBER (Username/derived)
No
CREATION_DATE DATE No sysdate
CREATED_BY NUMBER (Username/derived)
EMPLOYEE_ID NUMBER If vendor is employee. From HR table(derived)
VENDOR_TYPE_LOOKUP_CODE VARCHAR2 VENTYP Yes If employee number is present set as 'EMPLOYEE'; IF VENDOR_TYPE_LOOKUP_CODE is null, set = 'VENDOR’
CUSTOMER_NUM VARCHAR2 No NULL
ONE_TIME_FLAG VARCHAR2 No NULL
MIN_ORDER_AMOUNT NUMBER No NULLSHIP_TO_LOCATION_ID NUMBER NoSHIP_TO_LOCATION_CODE VARCHAR2 NoBILL_TO_LOCATION_ID NUMBER NoBILL_TO_LOCATION_CODE VARCHAR2 NoSHIP_VIA_LOOKUP_CODE VARCHAR2 NoFREIGHT_TERMS_LOOKUP_CODE
VARCHAR2 No
FOB_LOOKUP_CODE VARCHAR2 NoTERMS_ID NUMBER NoTERMS_NAME VARCHAR2 Yes ‘Net 30’.
If it is null and vendor type = EMPLOYEE set terms to IMMEADIATE; else set to 'Net 30'. Terms name. Default from the Terms table. Needed as a set up.
SET_OF_BOOKS_ID NUMBER No 81ALWAYS_TAKE_DISC_FLAG VARCHAR2 NoPAY_DATE_BASIS_LOOKUP_CODE
VARCHAR2 No
PAY_GROUP_LOOKUP_CODE VARCHAR2 No ‘VENDOR’. Pay group lookup code. (Derive value based on some logic/value)
PAYMENT_PRIORITY NUMBER No ‘1’INVOICE_CURRENCY_CODE VARCHAR2 No ‘USD’PAYMENT_CURRENCY_CODE VARCHAR2 No ‘USD’INVOICE_AMOUNT_LIMIT NUMBER No NULLHOLD_ALL_PAYMENTS_FLAG VARCHAR2 No NULLHOLD_FUTURE_PAYMENTS_FLAG
VARCHAR2 No If NULL then ‘N’
HOLD_REASON VARCHAR2 NoDISTRIBUTION_SET_ID NUMBER No NULLDISTRIBUTION_SET_NAME VARCHAR2 No NULL
C04.TD.AP.VendorConversion Page 14
Technical Design Document
ACCTS_PAY_CODE_COMBINATION_ID
NUMBER No NULL
PREPAY_CODE_COMBINATION_ID
NUMBER No NULL
NUM_1099 VARCHAR2 VENDOR_NO No LTrim first character.TYPE_1099 VARCHAR2 T99IND NoORGANIZATION_TYPE_LOOKUP_CODE
VARCHAR2 OWNERSHIP_CODE No (Derived)If employee number is present then set = 'INDIVIDUAL', else if null set = 'CORPORATION'. Organization type lookup code. Need to be derived.
VAT_CODE VARCHAR2 NoSTART_DATE_ACTIVE EFF_START_DATE No Take from source; else set = '01-JAN-1900'. Start date active
(Input from PASS)END_DATE_ACTIVE DATE EFF_END_DATE No NULLMINORITY_GROUP_LOOKUP_CODE
VARCHAR2 No
PAYMENT_METHOD_LOOKUP_CODE
VARCHAR2 PMT_DISTN_TYPE No Payment method lookup code
WOMEN_OWNED_FLAG VARCHAR2 NoSMALL_BUSINESS_FLAG VARCHAR2 NoSTANDARD_INDUSTRY_CLASS VARCHAR2 LSDBE_IND No NULLHOLD_FLAG VARCHAR2 No NULLPURCHASING_HOLD_REASON VARCHAR2 No NULLHOLD_BY NUMBER No NULLHOLD_DATE DATE No NULLTERMS_DATE_BASIS VARCHAR2 No ‘Invoice Received Date’ or ‘SYSDATE’INSPECTION_REQUIRED_FLAG VARCHAR2 No NullRECEIPT_REQUIRED_FLAG VARCHAR2 NoQTY_RCV_TOLERANCE NUMBER NoQTY_RCV_EXCEPTION_CODE VARCHAR2 NoENFORCE_SHIP_TO_LOCATION_CODE
VARCHAR2 No
DAYS_EARLY_RECEIPT_ALLOWED
NUMBER No
DAYS_LATE_RECEIPT_ALLOWED NUMBER NoRECEIPT_DAYS_EXCEPTION_CODE
VARCHAR2 No
RECEIVING_ROUTING_ID NUMBER No NULLALLOW_SUBSTITUTE_RECEIPTS_FLAG
VARCHAR2 No
ALLOW_UNORDERED_RECEIPTS_FLAG
VARCHAR2 No
HOLD_UNMATCHED_INVOICES_FLAG
VARCHAR2 No NULL
EXCLUSIVE_PAYMENT_FLAG VARCHAR2 NoAP_TAX_ROUNDING_RULE VARCHAR2 No NULLAUTO_TAX_CALC_FLAG VARCHAR2 No NULLAUTO_TAX_CALC_OVERRIDE VARCHAR2 No NULLAMOUNT_INCLUDES_TAX_FLAG VARCHAR2 No NULLTAX_VERIFICATION_DATE DATE W9_REQUEST_DATE No NULLNAME_CONTROL VARCHAR2 NAME_CONTROL NoSTATE_REPORTABLE_FLAG VARCHAR2 No ‘N’FEDERAL_REPORTABLE_FLAG VARCHAR2 T99IND No
C04.TD.AP.VendorConversion Page 15
Technical Design Document
ATTRIBUTE_CATEGORY VARCHAR2 No NULLATTRIBUTE1 VARCHAR2 No NULLATTRIBUTE2 VARCHAR2 No NULLATTRIBUTE3 VARCHAR2 No NULLATTRIBUTE4 VARCHAR2 No NULLATTRIBUTE5 VARCHAR2 No NULLATTRIBUTE6 VARCHAR2 No NULLATTRIBUTE7 VARCHAR2 No NULLATTRIBUTE8 VARCHAR2 No NULLATTRIBUTE9 VARCHAR2 No NULLATTRIBUTE10 VARCHAR2 No NULLATTRIBUTE11 VARCHAR2 No NULLATTRIBUTE12 VARCHAR2 No NULLATTRIBUTE13 VARCHAR2 No NULLATTRIBUTE14 VARCHAR2 No NULLATTRIBUTE15 VARCHAR2 No NULLREQUEST_ID No DerivedPROGRAM_APPLICATION_ID NUMBER No NULLPROGRAM_ID NUMBER No NULLPROGRAM_UPDATE_DATE DATE No NULLVAT_REGISTRATION_NUM VARCHAR2 No NULLAUTO_CALCULATE_INTEREST_FLAG
VARCHAR2 No NULL
EXCLUDE_FREIGHT_FROM_DISCOUNT
VARCHAR2 No NULL
TAX_REPORTING_NAME VARCHAR2 NoALLOW_AWT_FLAG VARCHAR2 No If NULL then ‘N’AWT_GROUP_ID NUMBER No NULLAWT_GROUP_NAME VARCHAR2 No NULLEDI_TRANSACTION_HANDLING VARCHAR2 No NULLEDI_PAYMENT_METHOD VARCHAR2 No NULLEDI_PAYMENT_FORMAT VARCHAR2 No NULLEDI_REMITTANCE_METHOD VARCHAR2 No NULLEDI_REMITTANCE_INSTRUCTION VARCHAR2 No NULLBANK_CHARGE_BEARER VARCHAR2 No NULLMATCH_OPTION VARCHAR2 No ‘INVOICE’FUTURE_DATED_PAYMENT_CCID
NUMBER No NULL
CREATE_DEBIT_MEMO_FLAG VARCHAR2 NoOFFSET_TAX_FLAG VARCHAR2 TAX_OFFSET_EXEMPT NoIMPORT_REQUEST_ID NUMBER No NULLSTATUS VARCHAR2 No ‘NEW’REJECT_CODE VARCHAR2 No NULLECE_TP_LOCATION_CODE VARCHAR2 No NULLIBY_BANK_CHARGE_BEARER VARCHAR2 No NULLBANK_INSTRUCTION1_CODE VARCHAR2 No NULLBANK_INSTRUCTION2_CODE VARCHAR2 No NULLBANK_INSTRUCTION_DETAILS VARCHAR2 No NULLPAYMENT_REASON_CODE VARCHAR2 No NULLPAYMENT_REASON_COMMENTS VARCHAR2 No NULLPAYMENT_TEXT_MESSAGE1 VARCHAR2 No NULLPAYMENT_TEXT_MESSAGE2 VARCHAR2 No NULL
C04.TD.AP.VendorConversion Page 16
Technical Design Document
PAYMENT_TEXT_MESSAGE3 VARCHAR2 No NULLDELIVERY_CHANNEL_CODE VARCHAR2 No NULLPAYMENT_FORMAT_CODE VARCHAR2 No NULLSETTLEMENT_PRIORITY VARCHAR2 No NULLPAYMENT_METHOD_CODE VARCHAR2 No NULLPAY_AWT_GROUP_ID VARCHAR2 No NULLPAY_AWT_GROUP_NAME VARCHAR2 No NULLPROCESS_STATUS VARCHAR2 NoERROR_FLAG VARCHAR2 NoERROR_CODE VARCHAR2 NoERROR_DESCRIPTION VARCHAR2 No
C04.TD.AP.VendorConversion Page 17
Technical Design Document
Target Column Name(Oracle Column for
AP_SUPPLIER_SITES_INT Interface Table)
Required
Data Type Source Column Validation
Transformation Rules
VENDOR_INTERFACE_ID Y NUMBER No Derived from Sequence
VENDOR_SITE_INTERFACE_ID NUMBER No Derived from SequenceNo
LAST_UPDATE_DATE DATE UPDATE_DATE NoLAST_UPDATED_BY NUMBER No Username(derived)VENDOR_ID NUMBER No NULLVENDOR_SITE_CODE VARCHAR2 ADDRESS _CODE
Yes
If the Address_code (Mail_code) is ‘000’ then on the legacy side the address at the header level and the detail level is same. If the Vendor has different addresses then it will be stored under different Mail_Code.
VENDOR_SITE_CODE_ALT No NULLLAST_UPDATE_LOGIN NUMBER No NULLCREATION_DATE DATE No SysdateCREATED_BY NUMBER No Username(derived)PURCHASING_SITE_FLAG VARCHAR2 No ‘Y’RFQ_ONLY_SITE_FLAG VARCHAR2 No ‘Y’PAY_SITE_FLAG VARCHAR2 No ‘Y’ATTENTION_AR_FLAG VARCHAR2 No NULLADDRESS_LINE1 VARCHAR2 ADDRESS_LINE1 NoADDRESS_LINE_ALT VARCHAR2 No NULLADDRESS_LINE2 VARCHAR2 ADDRESS_LINE2 NoADDRESS_LINE3 VARCHAR2 NoCITY VARCHAR2 CITY NoSTATE VARCHAR2 STATE NoZIP VARCHAR2 ZIP NoPROVINCE VARCHAR2 NoCOUNTRY VARCHAR2 COUNTRY No ‘US’AREA_CODE VARCHAR2 PHONE_AREA_CODE No
NoPHONE VARCHAR2 PHONE_EXC || PHONE_SEQ ||
PHONE_EXTNo
CUSTOMER_NUM VARCHAR2 No NULLSHIP_TO_LOCATION_ID NUMBER No NULLSHIP_TO_LOCATION_CODE VARCHAR2 No NULLBILL_TO_LOCATION_ID NUMBER No NULLBILL_TO_LOCATION_CODE VARCHAR2 NoSHIP_VIA_LOOKUP_CODE VARCHAR2 NoFREIGHT_TERMS_LOOKUP_CODE
VARCHAR2 No
FOB_LOOKUP_CODE VARCHAR2 NoINACTIVE_DATE DATE No NULLFAX VARCHAR2 FAX_SEQ NoFAX_AREA_CODE VARCHAR2 FAX_AREA_CODE No
C04.TD.AP.VendorConversion Page 18
Technical Design Document
TELEX VARCHAR2 No NULLPAYMENT_METHOD_LOOKUP_CODE
VARCHAR2 PMT_DISTN_TYPE No
TERMS_DATE_BASIS VARCHAR2 NoVAT_CODE VARCHAR2 No NULLDISTRIBUTION_SET_ID NUMBER No NULLDISTRIBUTION_SET_NAME No NULLACCTS_PAY_CODE_COMBINATION_ID
NUMBER No NULL
PREPAY_CODE_COMBINATION_ID
NUMBER No NULL
PAY_GROUP_LOOKUP_CODE VARCHAR2 No ‘VENDOR’PAYMENT_PRIORITY NUMBER No 1 or 99TERMS_ID NUMBER No (Derived)TERM_NAME VARCHAR2 No ‘Net 30’
Take from source or else set to ‘NET 30’.INVOICE_AMOUNT_LIMIT NUMBER No NULLPAY_DATE_BASIS_LOOKUP_CODE
VARCHAR2 No ‘SYSDATE’
ALWAYS_TAKE_DISC_FLAG VARCHAR2 No NULLINVOICE_CURRENCY_CODE VARCHAR2 No ‘USD’PAYMENT_CURRENCY_CODE VARCHAR2 No ‘USD’HOLD_ALL_PAYMENTS_FLAG VARCHAR2 No ‘Y’HOLD_FUTURE_PAYMENTS_FLAG
VARCHAR2 No ‘Y’
HOLD_REASON VARCHAR2 HOLD_REASON_CDE NoHOLD_UNMATCHED_INVOICES_FLAG
VARCHAR2 No NULL
AP_TAX_ROUNDING_RULE VARCHAR2 No NULLAUTO_TAX_CALC_FLAG VARCHAR2 No NULLAUTO_TAX_CALC_OVERRIDE VARCHAR2 No NULLAMOUNT_INCLUDES_TAX_FLAG VARCHAR2 No NULLEXCLUSIVE_PAYMENT_FLAG VARCHAR2 No NULLTAX_REPORTING_SITE_FLAG VARCHAR2 No ‘Y’ATTRIBUTE_CATEGORY VARCHAR2 No NULLATTRIBUTE1 VARCHAR2 No Original Vendor NumberATTRIBUTE2 VARCHAR2 No NULLATTRIBUTE3 VARCHAR2 No NULLATTRIBUTE4 VARCHAR2 No NULLATTRIBUTE5 VARCHAR2 No NULLATTRIBUTE6 VARCHAR2 No NULLATTRIBUTE7 VARCHAR2 No NULLATTRIBUTE8 VARCHAR2 No NULLATTRIBUTE9 VARCHAR2 No NULLATTRIBUTE10 VARCHAR2 No NULLATTRIBUTE11 VARCHAR2 No NULLATTRIBUTE12 VARCHAR2 No NULLATTRIBUTE13 VARCHAR2 No NULLATTRIBUTE14 VARCHAR2 No NULLATTRIBUTE15 VARCHAR2 No NULLREQUEST_ID NUMBER No NULLPROGRAM_APPLICATION_ID NUMBER No NULL
C04.TD.AP.VendorConversion Page 19
Technical Design Document
PROGRAM_ID NUMBER No NULLPROGRAM_UPDATE_DATE DATE No NULLVALIDATION_NUMBER NUMBER No NULLEXCLUDE_FREIGHT_FROM_DISCOUNT
VARCHAR2 No NULL
VAT_REGISTRATION_NUM VARCHAR2 No NULLORG_ID NUMBER No 81CHECK_DIGITS VARCHAR2 No ‘DCG Operating Unit’ADDRESS_LINE4 VARCHAR2 No NULLCOUNTY VARCHAR2 NoADDRESS_STYLE VARCHAR2 No NULLLANGUAGE VARCHAR2 No ‘ENGLISH’ALLOW_AWT_FLAG VARCHAR2 No NULLAWT_GROUP_ID NUMBER No NULLAWT_GROUP_NAME VARCHAR2 No NULLEDI_TRANSACTION_HANDLING VARCHAR2 No NULLEDI_ID_NUMBER VARCHAR2 No NULLEDI_PAYMENT_METHOD VARCHAR2 No NULLEDI_PAYMENT_FORMAT VARCHAR2 No NULLEDI_REMITTANCE_METHOD VARCHAR2 No NULLBANK_CHARGE_BEARER VARCHAR2 NoEDI_REMITTANCE_INSTRUCTION VARCHAR2 No NULLBANK_BRANCH_TYPE VARCHAR2 NoPAY_ON_CODE VARCHAR2 NoDEFAULT_PAY_SITE_ID NUMBER NoPAY_ON_RECEIPT_SUMMARY_CODE
VARCHAR2 No NULL
TP_HEADER_ID NUMBER No NULLECE_TP_LOCATION_CODE VARCHAR2 No NULLPCARD_SITE_FLAG VARCHAR2 NoMATCH_OPTION VARCHAR2 No ‘INVOICE’COUNTRY_OF_ORIGIN_CODE VARCHAR2 No ‘USA’FUTURE_DATED_PAYMENT_CCID
NUMBER No NULL
CREATE_DEBIT_MEMO_FLAG VARCHAR2 NoOFFSET_TAX_FLAG VARCHAR2 OFFSET_TAX_FLAG No ‘Y’SUPPLIER_NOTIF_METHOD VARCHAR2 NoEMAIL_ADDRESS VARCHAR2 NoREMITTANCE_EMAIL VARCHAR2 No NULLPRIMARY_PAY_SITE_FLAG VARCHAR2 No ‘Y’IMPORT_REQUEST_ID NUMBER NoSTATUS VARCHAR2 No ‘NEW’REJECT_CODE VARCHAR2 No NULLSHIPPING_CONTROL VARCHAR2 No NULLSELLING_COMPANY_IDENTIFIER VARCHAR2 No NULLGAPLESS_INV_NUM_FLAG VARCHAR2 NoDUNS_NUMBER VARCHAR2 DUNS_NO NoTOLERANCE_ID NUMBER NoTOLERANCE_NAME VARCHAR2 NoLOCATION_ID No AutoPARTY_SITE_ID NUMBER No Auto. Party site id (Auto generated from sequence by concurrant
program)
C04.TD.AP.VendorConversion Page 20
Technical Design Document
SERVICES_TOLERANCE_ID No NULLRETAINAGE_RATE NUMBER NoPAY_AWT_GROUP_ID NUMBER NoPAY_AWT_GROUP_NAME VARCHAR2 NoPARTY_SITE_NAME VARCHAR2 NoREMIT_ADVICE_DELIVERY_METHOD
VARCHAR2 No
Target Column Name(Oracle Column for
AP_SUP_SITE_CONTACT_INT Interface Table)
Required
Data Type Source Column Validation
Transformation Rules
LAST_UPDATE_DATE DATE UPDATE_DATE NoLAST_UPDATED_BY NUMBER No Username(derived/constant)
VENDOR_SITE_ID NUMBER No (derived)VENDOR_SITE_CODE VARCHAR2 No (derived)ORG_ID NUMBER No (derived)
OPERATING_UNIT_NAME VARCHAR2 No NULLLAST_UPDATE_LOGIN NUMBER No NULLCREATION_DATE DATE No Sysdate
CREATED_BY NUMBER No Username(derived/constant)INACTIVE_DATE DATE No NULL. Coming in the previous fileFIRST_NAME VARCHAR2 CONTACT_NAME No First name (split the vendor_contact into these three fields)
MIDDLE_NAME VARCHAR2 CONTACT_NAME NoLAST_NAME VARCHAR2 CONTACT_NAME NoPREFIX VARCHAR2 No NULL
TITLE VARCHAR2 No NULLMAIL_STOP VARCHAR2 No NULLAREA_CODE VARCHAR2 PHONE_AREA_CODE No
PHONE VARCHAR2 PHONE_EXC||PHONE_SEQ NoPROGRAM_APPLICATION_ID NUMBER No NULLPROGRAM_ID NUMBER No NULL
PROGRAM_UPDATE_DATE DATE No NULLREQUEST_ID No NULLCONTACT_NAME_ALT VARCHAR2 No Legacy_vendor_site_id
FIRST_NAME_ALT VARCHAR2 No NULLLAST_NAME_ALT VARCHAR2 No NULLDEPARTMENT VARCHAR2 No
C04.TD.AP.VendorConversion Page 21
Technical Design Document
IMPORT_REQUEST_ID NUMBER No NULLSTATUS VARCHAR2 No ‘NEW’REJECT_CODE VARCHAR2 No NULL
EMAIL_ADDRESS VARCHAR2 No XURL VARCHAR2 No NULLALT_AREA_CODE VARCHAR2 No NULL
ALT_PHONE VARCHAR2 No NULLFAX_AREA_CODE VARCHAR2 FAX_AREA_CODE NoFAX VARCHAR2 FAX_EXC || FAX_SEQ No
VENDOR_INTERFACE_ID NUMBER No Vendor interface id (DERIVED)VENDOR_ID NUMBER No (derived)VENDOR_CONTACT_INTERFACE_ID
NUMBER No (derived). Derived from Sequence: ap_sup_site_contact_int_s.NEXTVAL
PARTY_SITE_ID NUMBER No NULLPARTY_SITE_NAME VARCHAR2 No NULL
C04.TD.AP.VendorConversion Page 22
3 Processes and Interfaces Impacted
3.1 Summary
Seq # Processes Description of Impact
4 Module Specifications
Seq # Module Name New / Modified
Type
4.1 XXDCG_DCG_VENDOR_CONVERSION New Package
4.1 XXDCG_AP_VENDOR_CONV_PKG
4.1.1 Module Details
Program Name XXDCG Upload Vendor Conversion
Executable Name XXDCG_AP_VENDOR_CONV_PKG
Executable Type PL/SQL Stored Procedure
Parameters None
Incompatibilities None
Input Parameters: None
Output Parameters:
errbuf -- Standard Oracle Apps out parameter for retuning error messages.
retcode -- Standard Oracle Apps out parameter. 0 - success, 1 - warning 2 – error
Program Logic:
1. Build cursor to select data from Vendor data custom table.
2. Derive the corporate Org id code
3. Loop through all the Vendor records in the custom table
For each record
(a) Validate Employee id
(b) Validate Vendor Type, with the Vendor type lookup code
(c) Validate payment terms.
(d) Insert the data into AP Vendor Interface tables. Populate feeder_system_name as “CONVERSION”
(e) Update status on Vendor data to ‘S’ for successfully loaded rows.
For any error skip that record and log the error in the log file.
Pseudo code:
--Vendors Staging Tablecursor c1 isselect *from xxdcg.xxdcg_vendor_stg swhere 1=1and s.process_flag = 'N';
--Vendor Sites Staging Tablecursor c2(p_vendor_id number) isselect *
from xxdcg.xxdcg_vendor_sites_stg swhere 1=1and s.LEGACY_VENDOR_ID = p_vendor_idand s.process_flag = 'N';
--Vendor Person Id Lookup through Full Namecursor c3(p_fullname VARCHAR2) isselect f.PERSON_IDfrom per_all_people_f fwhere UPPER(TRIM(f.FIRST_NAME || ' ' || f.MIDDLE_NAMES || ' ' || f.LAST_NAME)) = TRIM(p_fullname);
--Vendor Payment Term Id Lookupcursor c5(p_term_name VARCHAR2) isselect a.term_idfrom ap.ap_terms_tl awhere a.NAME = p_term_name;
--to check later after functional setup select a.ORG_ID into v_organization_id from apps.po_system_parameters a;
SELECT ap_suppliers_int_s.NEXTVAL INTO v_vendor_interface_id FROM dual;
--Insert into the ap_suppliers_int table as follows: INSERT INTO ap_suppliers_int ( . ... );--Initialize and get the next vendor_site_interface_id. v_vendor_site_interface_id := 0;
SELECT ap_supplier_sites_int_s.NEXTVAL INTO v_vendor_site_interface_id FROM dual;
INSERT INTO ap_supplier_sites_int ( . . . );
-- Insert contact information into ap.ap_sup_site_contact_int. INSERT INTO ap_sup_site_contact_int (. . . ); END XXDCG_AP_VENDOR_CONV_PKG;
5 Data ConversionThe following steps have to be performed:
1. Get the ASCII comma-delimited format data file from the legacy system.
2. Create the staging tables in to the custom schema XXDCG using the SQL scripts.
3. Upload the data files into main staging table using SQL*Loader and the SQL scripts.
4. Run the concurrent programs to insert the data into the Oracle Applications AP Supplier Interface tables from the staging tables.
The step to successfully load the vendors is detailed below. It is important to follow the order as the next steps are dependent on the successful outcome of the previous step. On error re-run the same step until the errors are resolved and data is loaded error free.
?
5.1.1.1 Step 2 – Run the Concurrent Program Set.Login with the System Administrator responsibility and to the test system and decide which section responsibility you would like to put the request set DCG AP VENDOR CONVERSION by , and then run the request set called DCG AP VENDOR CONVERSION.
6 Test Plan
Test Areas
The following entities / functionalities to be tested for:
1. Conversion of Vendors.2. Validation of vendors that have gone through successfully from the API.3. Review any errors that come out.
Please refer Technical Design sections for more details.
Pre-requisite
Have all AP/PO modules in place. Create all prerequisites described in this document.
Initial Setup
Complete the initial setup as defined in the Functional design document.
S.No Test Condition Expected Results
1 Run Staging Table Creation Script. Creating 3 staging tables which are XXDCG.XXDCG_VENDOR_STG, XXDCG.XXDCG VENDOR_SITES_STG, and XXDCG.XXDCG_SUPPLIER_SITE_CONT_STG.
2 Run SQL*Loader script for loading XXDCG staging table.
Successfully putting the Vendor records into the XXDCG.XXDCG_VENDOR_STG, XXDCG.XXDCG VENDOR_SITES_STG, and XXDCG.XXDCG_SUPPLIER_SITE_CONT_STG tables
3 Run the open interface for vendors and for sites and for contacts.
Successfully put all vendors, vendor sites, and contacts into the system.
7 Open / Closed Issues Need to finalize screen 34 data and the fields
8 Implementation Notes# Execution Steps
1 Run script for grants and synonyms from apps to xxdcg user.
2 Run script for grants, synonyms and custom table creation in xxdcg custom schema.
3 Control script “xxdcg_ap_vendor_load.ctl” to be copied to the $XXDCG_TOP/loader directory
4 Create package xxdcg_ap_vendor_conv_pkg in the XXDCG schema.
5 Setup concurrent program, executable 1. XXDCG: Read Vendor Data File 2. XXDCG : XXDCG Upload Vendor Data to the AP Supplier Interface tables
6 Setup request set “XXDCG : AP Vendor Data Conversion”
7 Attach request set to appropriate responsibility by adding it to the report group associated with the responsibility.
9 Appendix1. Grants using apps user
GRANT EXECUTE ON fnd_file TO xxdcg;
2. Grants using xxdcg user
GRANT ALL ON XXDCG_AP_VENDOR_CONV_PKG TO apps;
3. Synonyms created using xxdcg user
CREATE OR REPLACE SYNONYM fnd_file FOR apps.fnd_file;
4. Synonyms created using apps user
CREATE OR REPLACE SYNONYM XXDCG_AP_VENDOR_CONV_PKG FOR
XXDCG. XXDCG_AP_VENDOR_CONV_PKG;