1.

Set Profile Option ‘HZ: Generate Party Number’ to blank at site level
(Set this profile option back to Yes when conversion is done)
Set this value so that Party number is system generated.

2. Insert the Receivable, Revenue, freight account records in the

BCI_CM_ACC_CROSS_REF table (if it does not exist yet)
It is OU based. We need to insert for the corresponding OU. Sample insert
statements below.

insert into BCI_CM_ACC_CROSS_REF values('Japan OU',

'Freight','Fr','037.90.4908.000.0000000.037.000.00.00000.00000');

insert into BCI_CM_ACC_CROSS_REF values('Japan OU',

'Revenue','Rev','037.90.3100.000.0000000.037.001.01.00000.00000');

insert into BCI_CM_ACC_CROSS_REF values('Japan OU',

'Receivable','Rec','037.90.1211.000.0000000.037.000.00.00000.00000');

3. Format the data file as in the given attached format(.csv). (See sample file
“CM_Conv.csv” in share point)

4. Put the file in Dropzone (anywhere) and give permission to that file chmod 777

5. Run the data load program (select the correct file path) from the corresponding ou
customer master batch scheduler responsibility (BCI CM Conversion Data Load).

This will load data into custom staging table.

Once loaded you can check in the BCI_CM_conversion_data table

 6. Run the Cross reference program (BCI CM Conversion Create References) --
BCICMCREF -- BCI_CM_CONVERSION.CREATE_REFERENCES

You can get the Cross_Reference file from the utl file path. For RICE it is
/RICE/d13/oratmp (or linux in /EBSTST/applmgr/applptmp )
This program will generate the cross reference file and also update staging table
County,Site_code, Address1,Telphone,Ship_to,bill_to,contact reference.

7. Run the Split data program (BCI CM Conversion Split Data).

select * from bci.bciar_customer_master_02 – Main table

select * from bci.bciar_cm_temp_table_01 – Parent references, business_purpose, fob,
freight_terms, radioactive_license_no,radioactive_license_exp_date,
tax_registration_number,tax_payer_id,dealer_commission_bill_to,
dealer_commission_bill_to_2,price_list_name,

Notes: Truncate all the temp and staging tables before processing ,take a back-up if
needed.
If not the final request set will read all the records from these tables and update Customer
Master.

This program will split the data into 2 tables

8. Run the Validation Program (BCI - AR Customer Validation Program) -- 1

begin
dbms_application_info.set_client_info('5631');
end;

select * from ra_customers_interface

where org_id = 5631

select * from ra_customer_profiles_interface

where org_id = 5631

select * from ra_contact_phones_interface

where org_id = 5631

9. Run the Customer Interface

 10. Finally run the Customer Master Update set

This set is for updating the attributes ,freight_terms ..etc from bciar_cm_temp_table_01

BCI - AR Update Customer Account -- BCIAR_UPD_CUSTACCT

BCI - AR Update Customer Relationship -- BCIAR_UPD_CUST_RELATIONSHIP

BCI - AR Create Customer Relationship -- BCIAR_CREATE_CUST_RELATE

Create customer relations, parent_reference1 to parent_reference20 are used for this.
BCI - AR Update Party -- BCIAR_UPD_PARTY
BCI - AR Update Site Contact -- BCIAR_UPD_SITE_CONTACT

BCI - AR Update Customer Site Use -- BCIAR_UPD_CUST_SITE_USE

p_cust_site_use_rec.attribute1 := r1.admin_to_site;
 p_cust_site_use_rec.attribute2 := r1.freight_consignee;
p_cust_site_use_rec.attribute3 := r1.grouping;
p_cust_site_use_rec.attribute4 := r1.grouping_number;
p_cust_site_use_rec.attribute5 := r1.use_dealer_name;
p_cust_site_use_rec.attribute6 := r1.dealer_commission_bill_to;
p_cust_site_use_rec.attribute10 := r1.dealer_commission_bill_to_2;
p_cust_site_use_rec.attribute7 := r1.radioactive_license_no;
p_cust_site_use_rec.attribute8 := r1.radioactive_license_exp_date;
p_cust_site_use_rec.attribute9 := r1.reporting_country_code;

Notes:
1. Org_id is not getting populated
2. Truncate the temp tables before starting the process.
3. DQM Synchronization Program – Run this program in test instances ,should be
already scheduled in Prod.
My Comment

Request Set Name: BCI Receivables All

BCI Customer Master Validation Program
BCI - AR Customer Validation Program

1)BCI CM Conversion Data Load

Executable: BCIARCMCVAL

1.1 Process Flow Diagram – Mandatory

Start Load data into custom table

BCI_CM_CONVERSION_DATA
Run BCI CM Conversion Split Data
program
Submitto split and insert data to BCI
Run BCIStandard program
- AR Customer
custom tables Interface for loading
Customer
Validation Program for validating
bci.bciar_customer_master_02 and 
data and
to base tables
data insert data to Interface
bci.bciar_cm_temp_table_01
tables
 Run BCI CM Conversion Create References Program to
validate, Update BCI_CM_CONVERSION_DATA
staging table, insert cross references to
BCIAR_GLOBAL_CM_XREF table and create cross
reference file (Outbound)

Run the Request Set BCI - AR Customer Master Update

Set
BCI - AR Update Customer Account
BCI - AR Update Customer Relationship
BCI - AR Create Customer Relationship
BCI - AR Update Party
BCI - AR Update Site Contact
BCI - AR Update Customer Site Use
BCIAR Update Customer Master
Stop
This has several concurrent stages in which development will happen as listed below.

BCI CM Conversion Data Load  Program to load data to basic staging table BCI_CM_conversion_data. (Select
the correct file path with file name as parameter to this program from the corresponding Customer master Batch
Scheduler responsibility)

BCI CM Conversion Create References  This program validate data and inserting cross references to
BCIAR_GLOBAL_CM_XREF table and creates cross reference file (outbound). As a process this will also update
status to staging table BCI_CM_conversion_data.

BCI CM Conversion Split Data  This program will split data into BCI custom tables
bci.bciar_customer_master_02 and bci.bciar_cm_temp_table_01.

BCI - AR Customer Validation Program  This program validates the customer information in staging table and
insert records to interface tables.

BCI - AR Customer Master Update Set  Request Set for Updating Customer Master

BCI - AR Update Customer Account  To update customer account

BCI - AR Update Customer Relationship  To update customer details when parent customer and related
customer are provided in the data file.

BCI - AR Create Customer Relationship  To create customer relation when customer has more than one parent

BCI - AR Update Party  To update the party tax registration details

BCI - AR Update Site Contact  To update customer contact role

BCI - AR Update Customer Site Use  To update customer payment and freight terms at site level

BCIAR Update Customer Master  To update customer account for additional fields (Credit Hold, GSA, Sales
Channel, Site aggregation) mentioned in the data file
Request

1)BCI CM Conversion Data Load- BCICMLOAD.ctl

SELECT * FROM BCI_CM_CONVERSION_DATA without Org Reference

2)BCI CM Conversion Create References--- BCI_CM_CONVERSION.CREATE_REFERENCES

bci_cm_conversion.

Validating Table: select * from bciar_ra_customers_v

Table: BCIAR_GLOBAL_CM_XREF

3) BCI CM Conversion Split Data - BCI_CM_CONVERSION.SPLIT_DATA

1. bciar_customer_master_02

2. bciar_cm_temp_table_01

4) BCI - AR Customer Validation Program -- BCIARCMCVAL.sql

---Staging Table

SELECT * FROM bci.bciar_customer_master_02 WHERE ERROR_MESSAGE IS NOT NULL

select * from bciar_global_cm_xref

where last_update_date > sysdate-1

GENOMICS_10019_28340

-- selection for Validation

select * from bci.bciar_customer_master_02 where ORIG_SYSTEM_CUSTOMER_REF ='LTJF'

---After running Validation -- Interface table for Customer, Profile, Phone

select * from ra_customers_interface_all where orig_system_customer_ref ='LTJF'

select * from RA_CUSTOMER_PROFILES_INT_ALL where orig_system_customer_ref ='LTJF'

select * from ra_contact_phones_interface -- where orig_system_customer_ref ='LTJF'

 select * from RA_CONTACT_PHONES_INT_all where orig_system_customer_ref ='LTJF'

BCI - AR Update Customer Account

Executable : BCIAR_UPD_CUSTACCT

Replacement : BCI AR Update Customer Account New

Executable : BCIAR_UPD_CUSTACCT_NEW

Procedure : bci_cm_conversion_pkg.update_customer_accnt

select distinct

customer_reference,customer_name,customer_number,

fob, freight_terms, sales_channel,customer_class_code, cust_attr_2,

cust_attr_3,cust_attr_4, cust_attr_5

from bciar_cm_temp_table_01

where fob is not null

or freight_terms is not null

or sales_channel is not null

or customer_class_code is not null

or cust_attr_2 is not null

or cust_attr_3 is not null

or cust_attr_4 is not null

or cust_attr_5 is not null

order by customer_reference;

hz_cust_account_v2pub.update_cust_account

Replacement:

Table Name :

RA_CUSTOMERS_INTERFACE_ALL

INSERT_UPDATE_FLAG

BCI - AR Update Customer Relationship

cursor c_custrel_record is
 select distinct parent_reference_01, parent_reference_02, parent_reference_03,

parent_reference_04, parent_reference_05,parent_reference_06,

parent_reference_07, parent_reference_08, parent_reference_09,

parent_reference_10, parent_reference_11, parent_reference_12,

parent_reference_13, parent_reference_14,parent_reference_15,

parent_reference_16, parent_reference_17, parent_reference_18,

parent_reference_19, parent_reference_20,

customer_reference,customer_number

from bciar_cm_temp_table_01

where (parent_reference_01 is not null or parent_reference_02 is not null

or parent_reference_03 is not null or parent_reference_04 is not null

or parent_reference_05 is not null or parent_reference_06 is not null

or parent_reference_07 is not null or parent_reference_08 is not null

or parent_reference_09 is not null or parent_reference_10 is not null

or parent_reference_11 is not null or parent_reference_12 is not null

or parent_reference_13 is not null or parent_reference_14 is not null

or parent_reference_15 is not null or parent_reference_16 is not null

or parent_reference_17 is not null or parent_reference_18 is not null

or parent_reference_19 is not null or parent_reference_20 is not null)

order by customer_reference;

Executable: BCIAR_CREATE_CUST_RELATE.sql internally calls

Procedure : bciar_insert_cust_relate

HZ_CUST_ACCOUNT_V2PUB.create_cust_acct_relate(

'T',

p_cust_acct_relate_type,

x_return_status,

x_msg_count,

x_msg_data);

BCI - AR Update Party

BCIAR_UPD_PARTY.sql
 cursor c_party_record is

select distinct customer_reference,customer_number,

tax_registration_number,tax_payer_id, category_code,duns_number

from bciar_cm_temp_table_01

where tax_registration_number is not NULL or

tax_payer_id is not NULL or

category_code is not NULL or

duns_number is not NULL

order by customer_reference;

hz_party_v2pub.update_organization(

'T',

p_organization_rec,

p_party_object_version_number,

x_profile_id,

x_return_status,

x_msg_count,

x_msg_data)

BCI - AR Update Site Contact

bciar_upd_site_contact.sql

--- No Customer Table Involved

hz_cust_account_role_v2pub.create_role_responsibility(

'T',

p_role_responsibility_rec,

x_responsibility_id,

x_return_status,

x_msg_count,

x_msg_data);

Program BCI - AR Update Customer Site Use BCI Receivables

BCIAR Customer Master Account Update

BCIARCOL_CUST_UPDATE_PKB.bciarcol_update_cust_profile