AP_SUPPLIERS ENABLE_FLAG

Hello,
I'm using ap_vendor_pub_pkg.update_vendor to update enabled_flag='N' and end_date_active=SYSDATE of ap_suppliers in R12.1.3.
I want to leave a option for users to be able to activate the vendor if needed in future.I'm able to clear inactive dates on supplier and supplier sites from supplier form.
But I don't see ENABLED_FLAG anywhere on the Supplier form. Is there a way to update it back to 'Y' from Oracle Forms?
Appreciate any help!!
Thanks

Hi Sandeep,
I understand that is an option, actually that is what I'm doing now, But I just wanted to understand if these flags are updatable from application.
Thanks
Manu

Similar Messages

Can any one please send me an update trigger (pl/sql procedure) for ap tables(ap_suppliers,ap_supplier_site_all,and contacts)

Please send an query for update trigger for those tables .
     1: ap_suppliers
     2: ap_supplier_sites_all
     3: ap_supplier_contacts.
Thanks,
Chaitanya.

Hi,
Actually ID and Data are different names in my API. Here I mentioned like that.
Am using Oracle 10g version.
Yes I am going to get the multiple values using this Ref Cursor. The same ref cursor is used in another API of my package.
In this API, the user actually enters Application_id and data. API should insert/update the version_master table with the inputs. See application_id is the foriegn key for app_master table.
The requirement is whenever they enters application_id and data, if application_id already present in the version_master table, then the data should be updated and we should get a status flag for this using Out variable(i.e. using ref cursor only we are showing the status). if the application_id is not present in the version_master table, new record should be inserted. The sequence will generate the version_id for version_master table.
But the Merge statement is working fine for update and insert also. Problem is am unable to see the success or failure through ref cursor. I don't know how exactly I can use this.
If data is NULL the operation should be failed. i.e. I should get Failure status here. But am not getting this.
Please remove the comments here and then check. If I use the NVL2 function I was able to get the status flag, i.e. S or F.
OPEN resultset_o FOR
SELECT NVL2 (data, 'S', 'F')
FROM version_master
WHERE application_id = application_id_i;
1.How the value of data being not null will determine Success of the api and how null failure
2.If the above select statement goes in to exception when others how I will no the failure
I have to achieve the above scenarios.
Please advice me.

Num_1099, individual_1099 columns in ap_suppliers

We are on Oracle EBS 12.1.3. In supplier screen there are two places where user can enter tax number. One is by clicking on "Tax and Reporting" page and other location is "Tax and Financial Information" section under Organization page. Based on where user enter information system populate column NUM_1099 or INDIVIDUAL_1099 in AP_SUPPLIERS table. Can someone tell me what is difference between two locations? Which one should be used?
Thanks.

In my experience with both 12.0.X and 12.1.3, the Taxpayer ID field (yes it appears twice in the Supplier Pages) feeds into the individual_1099 and num_1099 fields (both in the AP_SUPPLIERS table) based on whether it is a SSN or EIN. Unfortunately, I do not recall at the moment what the trigger is which distiguishes them. I don't believe it is format, meaning xxx-xx-xxxx vs xx-xxxxxxx, or if it is based off the value entered for Organization_Type_Lookup_Code, meaning Corporation, Individual, etc.
Having said all that, about 2 months ago, in a 12.1.3 environment, I ran into a bug in the supplier pages that caused a conflict between the Taxpayer ID field on the Organizations page and the Taxpayer ID field on the other page. Oracle sent us a patch that actually removed the second occurance of the Taxpayer ID field. The reason we were given for the desparity was that within the last year, Oracle decided to slightly change the direction of the supplier architecture. We figured out that this meant they changed the queries on the supplier pages to stop trying to always hit the HZ tables as the primary tables.
Testing to identify this issue would be to change the TIN in one of the fields, save and see if the other TIN field was also updated or if it retained the old value. Hope this helps.
Deb

Ap_suppliers have wrong employee_id

Hi,
ap_suppliers table is having the wrong (ex) employee id. This employee has two ids in HR (one is terminated)
How can i correct this issue?
Thanks
Senthil

I don't think you can update the employee associated to a vendor, you'll have to create a new one selecting employee as the type and then picking the active employee for it,

URGENT -- Linking GL to AR & AP for custom report

Hello All,
I am having trouble linking GL tables to AR and AP tables for a customized Account Analysis report.
I have an initial query but the values for Accounted_DR/CR and Entered_DR/CR do no seem to be correct, so it is possible that the links I have are possibly wrong.
Any help would be greatly appreciated.
Here is my initial query:
SELECT DISTINCT NVL(src.user_je_source_name, '**********') SOURCE,
NVL(cat.user_je_category_name, '**********') CATEGORY,
jeh.NAME JOURNAL_NAME,
jeb.NAME BATCH_NAME,
jeh.period_name PERIOD_NAME,
gcc.segment1 CO,
gcc.segment2 COST_CENTER,
gcc.segment3 ACCOUNT,
gcc.segment4 SECTOR,
gcc.segment5 AC_TYPE,
gcc.segment6 PROJ,
gcc.segment7 FUTURE,
(gcc.segment1 || '-' || gcc.segment2 || '-' || gcc.segment3 || '-' || gcc.segment4 || '-' || gcc.segment5 || '-' || gcc.segment6 || '-' || gcc.segment7) ACCOUNT1,
jel.accounted_dr ACCOUNTED_DR,
jel.accounted_cr ACCOUNTED_CR,
jel.entered_dr ENTERED_DR,
jel.entered_cr ENTERED_CR,
jel.description LINE_DESCRIPTION,
(SELECT ffv.description
FROM FND_FLEX_VALUES_VL ffv
WHERE ffv.flex_value = gcc.segment3) ACCOUNT_DESCRIPTION,
(SELECT ffv.description
FROM FND_FLEX_VALUES_VL ffv
WHERE ffv.flex_value = gcc.segment4) SECTOR_DESCRIPTION,
ap.vendor_name VENDOR_NAME,
ca.check_number CHECK_NUMBER,
ca.check_date CHECK_DATE,
aia.invoice_num INVOICE_NUM,
aia.invoice_date INVOICE_DATE,
jeh.posted_date POSTED_DATE,
/*(SELECT DISTINCT awt.NAME
FROM
ap_invoice_lines_all ail,
ap_awt_groups awt
WHERE aia.invoice_id = ail.invoice_id
AND ail.awt_group_id = awt.group_id
AND rownum=1) TAX_NAME*/
FROM gl_je_headers jeh,
gl_je_lines jel,
gl_je_batches jeb,
gl_je_sources src,
gl_je_categories cat,
gl_code_combinations gcc,
fnd_flex_values_vl ffv,
gl_import_references gli,
xla.xla_ae_lines xal,
xla.xla_ae_headers xah,
xla.xla_events xe,
xla.xla_transaction_entities xte,
apps.ap_invoices_all aia,
ap.ap_suppliers ap,
ap_invoice_payments_all aipa,
ap_checks_all ca
WHERE
jeh.je_header_id = jel.je_header_id
AND jeh.je_batch_id = jeb.je_batch_id
AND jeh.je_source = src.je_source_name
AND jeh.je_category = cat.je_category_name
AND jel.code_combination_id = gcc.code_combination_id
AND gcc.segment4 = ffv.flex_value
AND jeh.je_batch_id = gli.je_batch_id
AND jeh.je_header_id = gli.je_header_id
AND jel.je_line_num = gli.je_line_num
AND (NVL(gli.reference_9, 1) = 1 OR gli.reference_9 >0)
AND gcc.code_combination_id = xal.code_combination_id
AND gli.gl_sl_link_id = xal.gl_sl_link_id
AND gli.gl_sl_link_table = xal.gl_sl_link_table
AND xal.application_id = xah.application_id
AND xal.ae_header_id = xah.ae_header_id
AND xah.application_id = xe.application_id
AND xah.event_id = xe.event_id
AND xe.application_id = xte.application_id
AND xe.entity_id = xte.entity_id
AND xte.source_id_int_1 =aia.invoice_id
AND aia.vendor_id = ap.vendor_id
AND aia.invoice_id = aipa.invoice_id(+)
AND aipa.check_id = ca.check_id(+)
AND jel.status || '' = 'P'
AND jeb.average_journal_flag = 'N'
AND jeh.period_name = :P_PERIOD_NAME
--AND gcc.CODE_COMBINATION_ID=NVL(aia.ACCTS_PAY_CODE_COMBINATION_ID,gcc.CODE_COMBINATION_ID) /*link for GL and AP*/
--AND gcc.CODE_COMBINATION_ID=NVL(aia.ACCTS_PAY_CODE_COMBINATION_ID,gcc.CODE_COMBINATION_ID) /*link for GL and AP*/
ORDER BY ACCOUNT1,
SOURCE ,
CATEGORY,
jeb.NAME
Regards,
Jovee
Edited by: JoveeL on May 23, 2012 5:19 PM

Hello again,
I am still having trouble linking the data from GL. Specifically GL_JE_LINES and AP/AR values.
Currently trying to link invoice details to GL details and Accounted CR/DR do not match up with the invoices and are sometimes repeating for different invoices.
Upon checking, the values for GJ_JE_LINES repeat when I include the invoice details, but if I comment them out, they are okay.
I suspect that there is something wrong with my link between the XLA and GL tables, but I could not narrow it down.
I have tried looking it up in Google but there is nothing I found that is remotely helpful.
Any helpful advice would be greatly appreciated.
Regards,
Jovelyn
Edited by: JoveeL on May 23, 2012 5:15 PM

11i to R12 Upgrade- Doubt in XLA tables

Hi All,
     I am migrating the 11i AP reports to R12..
     In the below query I have commented the obselete and changed 11i columns & tables , but I wasnt able to find the alternate column in WHERE clause for 2 columns in xla_ae_lines and 1 in xla_ae_headers.
     I have marked the ones for which I didn't find the alternate column in red
SELECT c.check_id,
        to_char(c.check_number) check_num ,
        i.invoice_id,
        i.invoice_num,
        c.amount,
        ael.accounted_dr accounted_dr,
        ael.entered_dr entered_dr,
        &p_flexdata4 c_flexdata4,
        aeh.accounting_date check_date,
        c.doc_sequence_value voucher_number,
        --ael.ae_line_type_code acct_line_type,
        ael.accounting_class_code acct_line_type,
        l3.displayed_field acct_line_type_name,
        ael.code_combination_id code_combination_id,
        ael.description comments ,
        v.segment1 vendor_num,
        v.vendor_name vendor_name,
        vs.vendor_site_code third_party_sub_name,
        c.check_date trx_date ,
        c.check_number trx_number_n,
        c.bank_account_name bank_account_name,
        abb.bank_name,
        aba.bank_account_num
FROM
      --ap_bank_accounts_all aba,
      --ap_bank_branches abb,
      ce_bank_accounts aba,
      ce_bank_branches_v abb,
      ap_invoice_distributions_all d,
      ap_invoices_all i,
      ap_invoice_payments_all p,
      ap_checks_all c,
      --ap_accounting_events_all ae,
      --ap_ae_headers_all aeh,
      --ap_ae_lines_all ael,
      xla_events ae,
      xla_ae_headers aeh,
      xla_ae_lines ael,
      xla_transaction_entities xte,
      ce_statement_lines sl,
      --ce_statement_headers_all sh,
      ce_statement_headers sh,
      ce_statement_reconcils_all csr,
      --po_vendor_sites_all vs,
      --po_vendors v,
      --ap_tax_codes AT,
      ap_supplier_sites_all vs,
      ap_suppliers v,
      zx_lines zl,
      rcv_shipment_headers rsh,
      po_releases_all pr,
      po_headers_all ph,
      po_distributions_all pd,
      rcv_transactions rct,
      gl_je_categories jc,
      gl_daily_conversion_types glct,
      fnd_document_sequences fd,
      fnd_document_sequences fd2,
      ap_lookup_codes l1,
      ap_lookup_codes l2 ,
      ap_lookup_codes l3 ,
      ap_lookup_codes l4 ,
      ap_lookup_codes l5 ,
      ap_lookup_codes l6,
      ap_lookup_codes l7,
      ap_lookup_codes l8 ,
      ap_lookup_codes l9 ,
      ap_lookup_codes l10 ,
      ap_lookup_codes l11 ,
      ap_lookup_codes l12,
      ap_lookup_codes l13,
      gl_code_combinations gcc1
WHERE c.bank_account_id =aba.bank_account_id
      --AND aba.bank_branch_id =abb.bank_branch_id
      AND aba.bank_branch_id =abb.branch_party_id
      AND ael.code_combination_id =gcc1.code_combination_id(+)
      AND l1.lookup_code = c.payment_method_lookup_code
      AND l1.lookup_type = 'PAYMENT METHOD'
      AND l2.lookup_code(+) = d.line_type_lookup_code
      AND l2.lookup_type(+) = 'INVOICE DISTRIBUTION TYPE'
      --AND l3.lookup_code = ael.ae_line_type_code
      AND l3.lookup_code = ael.accounting_class_code
      AND l3.lookup_type = 'AE LINE TYPE'
      --AND l4.lookup_code = aeh.gl_transfer_flag
      AND l4.lookup_code = aeh.gl_transfer_status_code
      AND l4.lookup_type = 'POSTING STATUS'
      AND l5.lookup_code = ae.event_type_code
      AND l5.lookup_type = 'EVENT TYPE'
--AND l6.lookup_code(+) = aeh.accounting_error_code
      AND l6.lookup_type(+) = 'ACCOUNTING ERROR TYPE'
--AND l7.lookup_code(+) = ael.accounting_error_code
      AND l7.lookup_type(+) = 'ACCOUNTING ERROR TYPE'
      AND l8.lookup_code = 'Payments'
      AND l8.lookup_type = 'POSTING CATEGORY'
--AND l9.lookup_code(+) = ael.gl_transfer_error_code
      AND l9.lookup_type(+) = 'POSTING EXCEPTIONS'
      AND l10.lookup_code = 'EVENT'
      AND l10.lookup_type = 'VIEW_ACCOUNTING'
      AND l11.lookup_code = 'LINE'
      AND l11.lookup_type = 'VIEW_ACCOUNTING'
      AND l12.lookup_code = 'APPLIED_TO'
      AND l12.lookup_type = 'VIEW_ACCOUNTING'
      AND l13.lookup_code = 'BANK_STATEMENT'
      AND l13.lookup_type = 'VIEW_ACCOUNTING'
      --AND AT.tax_id(+) = ael.tax_code_id
      AND i.invoice_id = zl.trx_id(+)
      AND zl.entity_code = 'AP_INVOICES'
      --AND jc.je_category_name = aeh.ae_category
      AND jc.je_category_name = aeh.je_category_name
      AND rsh.shipment_header_id = rct.shipment_header_id
      AND d.rcv_transaction_id = rct.transaction_id
      AND pr.po_release_id(+) = pd.po_release_id
      AND ph.po_header_id(+) = pd.po_header_id
      AND pd.po_distribution_id(+) = d.po_distribution_id
      AND ael.currency_conversion_type = glct.conversion_type(+)
      AND c.doc_sequence_id = fd.doc_sequence_id
      AND sh.doc_sequence_id = fd2.doc_sequence_id
      --AND ael.third_party_sub_id = vs.vendor_site_id
      --AND ael.third_party_id = v.vendor_id
      AND ael.party_site_id = vs.vendor_site_id
      AND ael.party_id = v.vendor_id
      AND i.invoice_id(+) = p.invoice_id
      --AND c.check_id = ae.source_id
      --AND ae.source_table = 'AP_CHECKS'
      --AND ae.accounting_event_id = aeh.accounting_event_id
      --AND aeh.ae_header_id = ael.ae_header_id
      AND i.invoice_id = xte.source_id_int_1
      AND xte.entity_code = 'AP_CHECKS'
      AND aeh.ae_header_id = ael.ae_header_id
      AND aeh.application_id = ael.application_id
      AND aeh.event_id=ae.event_id
      AND aeh.application_id = ae.application_id
      AND ae.entity_id=xte.entity_id
      AND ae.application_id = xte.application_id
      AND sl.statement_header_id = sh.statement_header_id(+)
      AND csr.statement_line_id = sl.statement_line_id(+)
      AND c.check_id = csr.reference_id(+)
      AND csr.reference_type = 'PAYMENT'
      AND csr.current_record_flag(+) = 'Y'
      AND decode(ael.source_table,'AP_INVOICE_PAYMENTS', ael.source_id,NULL) = p.invoice_payment_id(+)
      AND decode(ael.source_table,'AP_INVOICE_DISTRIBUTIONS', ael.source_id,NULL) = d.invoice_distribution_id(+)
      AND ael.accounted_dr IS NOT NULL
      AND (v.segment1 = :p_vendor_code
      OR :p_vendor_code IS NULL)
      AND (v.vendor_name = :p_vendor_name
      OR :p_vendor_name IS NULL)
      AND (abb.bank_name = :p_bank_name
      OR :p_bank_name IS NULL)
      AND (c.currency_code = :p_currency
      OR :p_currency IS NULL)
      AND (c.doc_sequence_value = :p_doc_sequence_value
      OR :p_doc_sequence_value IS NULL)
      AND (i.pay_group_lookup_code = :p_paygroup
      OR :p_paygroup IS NULL)
      AND ( c.check_date IS NULL
      OR trunc(c.check_date) = nvl(:p_payment_date, trunc(c.check_date)))
Thanks and Regards,
Madonna

Hi Cheryl,
     Thank you for the reply..
     It would be nice if you could illustrate with a sample code..
Thanks and Regards,
Madonna

Execute dynamic sql statement

Hi all
CREATE TABLE XX_OFFICE_USER_IMP
    ID              NUMBER,
    OFFICE          VARCHAR2(10 BYTE),
    USER_NAME       VARCHAR2(10 BYTE),
    BANK_ACCOUNT_ID NUMBER,
    TRANSFERED      NUMBER
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (421,'0000','F0000',10029,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (422,'0000','F0000',10031,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (423,'0000','F0000',10033,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (424,'0000','F0000',10036,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (425,'0000','F0000',10037,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (426,'0000','F0000',10039,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (427,'0000','F0000',10041,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (428,'0000','F0000',10046,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (429,'0000','F0000',10048,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (430,'0000','F0000',10067,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (431,'0000','F0000',10072,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (432,'0000','F0000',10087,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (433,'0000','F0000',10092,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (434,'0000','F0000',10008,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (435,'0000','F0000',10012,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (436,'0000','F0000',10013,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (437,'0000','F0000',10014,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (438,'0000','F0000',10017,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (439,'0000','F0000',10019,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (440,'0000','F0000',10024,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (441,'0000','F0000',10025,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (442,'0000','F0000',10001,null);
Insert into xx_office_user_imp (ID,OFFICE,USER_NAME,BANK_ACCOUNT_ID,TRANSFERED) values (443,'0000','F0000',10002,null);
CREATE TABLE XXBG_CASIER_CASH
    CASHIER         VARCHAR2(32 BYTE),
    BANK_ACCOUNT_ID NUMBER(38,0)
declare
v_exe_grant varchar2(32767 char);
begin
for i in (select * from xx_office_user_imp where office = '0000') loop
insert into XXBG_CASIER_CASH values (i.user_name, i.bank_account_id);
v_exe_grant :=
                 'create user ' || i.user_name || ' identified by ' || i.user_name || ';'
              || 'GRANT create session to ' || i.user_name || ';'
              || 'GRANT select on apps.XXBG_CE_STATEMENT_HEADERS_CASH to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.FND_USER TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.dFND_DESCR_FLEX_COL_USAGE_TL TO ' || i.user_name || ';'
              || 'GRANT select on apps.fnd_descr_flex_column_usages to ' || i.user_name || ';'
              || 'GRANT select on apps.fnd_descriptive_flexs to ' || i.user_name || ';'
              || 'GRANT select on apps.fnd_descriptive_flexs_tl to ' || i.user_name || ';'
              || 'GRANT select on ce.ce_statement_headers to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.fnd_doc_sequence_assignments TO ' || i.user_name || ';'
              || 'GRANT SELECT ON CE.CE_STATEMENT_HEADERS_S TO ' || i.user_name || ';'
              || 'GRANT EXECUTE ON APPS.XXBG_GET_NEXTVAL TO ' || i.user_name || ';'
              || 'GRANT SELECT ON CE.CE_STATEMENT_LINES TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.XXBG_CE_STATEMENT_LINES TO ' || i.user_name || ';'
              || 'GRANT select on apps.CE_BANK_ACCOUNTS to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.CE_BANK_BRANCHES_V TO ' || i.user_name || ';'
              || 'GRANT SELECT ON CE.XXBG_CASIER_CASH TO ' || i.user_name || ';'
              || 'GRANT EXECUTE ON APPS.XXBG_ST TO ' || i.user_name || ';'
              || 'GRANT select on ce.xxbg_ce_statement_lines_detail to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.ce_transaction_codes TO ' || i.user_name || ';'
              || 'GRANT select on ce.ce_statement_lines_s to ' || i.user_name || ';'
              || 'GRANT SELECT ON CE.XXBG_CE_STATEMENT_LINES_DET_SQ TO ' || i.user_name || ';'
              || 'GRANT select on apps.xx_pko_lines to ' || i.user_name || ';'
              || 'GRANT SELECT ON apps.xx_rko_lines TO ' || i.user_name || ';'
              || 'GRANT select on apps.XX_INVOICE_RELATIONS_CASH to ' || i.user_name || ';'
              || 'GRANT select on APPS.PO_VENDOR_SITES_ALL to ' || i.user_name || ';'
              || 'GRANT select on ap.AP_INVOICE_LINES_INTERFACE_S to ' || i.user_name || ';'
              || 'GRANT select on ap.AP_INVOICE_LINES_INTERFACE to ' || i.user_name || ';'
              || 'GRANT select on APPS.ap_distribution_set_lines_all to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.AP_INVOICES_INTERFACE_S TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.AP_INVOICES_INTERFACE TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.AP_DISTRIBUTION_SETS_ALL TO ' || i.user_name || ';'
              || 'GRANT select on apps.ce_lookups to ' || i.user_name || ';'
              || 'GRANT select on ar.HZ_CUST_SITE_USES_ALL to ' || i.user_name || ';'
              || 'GRANT select on ar.HZ_LOCATIONS to ' || i.user_name || ';'
              || 'GRANT select on ar.HZ_PARTIES to ' || i.user_name || ';'
              || 'GRANT select on ar.HZ_PARTY_SITES to ' || i.user_name || ';'
              || 'GRANT SELECT ON AR.HZ_CUST_ACCT_SITES_ALL TO ' || i.user_name || ';'
              || 'GRANT SELECT ON AR.HZ_CUST_ACCOUNTS TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.XXBG_CLAIMS_V TO ' || i.user_name || ';'
              || 'GRANT select on apps.xxbg_insis_agents_v to ' || i.user_name || ';'
              || 'GRANT select on ce.xxbg_cash_doc_types to ' || i.user_name || ';'
              || 'GRANT select on AP.AP_BANK_ACCOUNTS_ALL to ' || i.user_name || ';'
              || 'GRANT SELECT ON AP.AP_BANK_BRANCHES TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.FND_DESCR_FLEX_CONTEXTS TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.FND_DESCR_FLEX_CONTEXTS_TL TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.AP_SUPPLIERS to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.per_employees_x TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.fnd_doc_seq_categories_ap_v TO ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.AP_LC_INVOICE_TYPES_V to ' || i.user_name || ';'
              || 'GRANT SELECT ON ce.xxbg_ce_statement_lines_sq to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.XXBG_STATEMENT_HEADERS_CASH to ' || i.user_name || ';'
              || 'GRANT SELECT ON APPS.XXBG_INSIS_POLICY_V TO ' || i.user_name || ';'
              || 'GRANT insert ON ce.ce_statement_lines to ' || i.user_name || ';'
              || 'GRANT INSERT ON CE.XXBG_CE_STATEMENT_LINES_DETAIL TO ' || i.user_name || ';'
              || 'GRANT INSERT ON APPS.AP_INVOICES_INTERFACE TO ' || i.user_name || ';'
              || 'GRANT INSERT ON APPS.AP_INVOICE_LINES_INTERFACE TO ' || i.user_name || ';'
              || 'GRANT INSERT ON APPS.XX_RKO_LINES TO ' || i.user_name || ';'
              || 'GRANT INSERT ON APPS.XX_PKO_LINES TO ' || i.user_name || ';'
              || 'GRANT delete on ce.xxbg_ce_statement_lines_detail to ' || i.user_name || ';'
              || 'GRANT update on ce.XXBG_CE_STATEMENT_LINES_DETAIL to ' || i.user_name || ';'
              || 'GRANT DELETE ON CE.CE_STATEMENT_LINES TO ' || i.user_name || ';'
              || 'GRANT INSERT ON CE.CE_STATEMENT_HEADERS TO ' || i.user_name || ';'
              || 'GRANT update on CE.CE_STATEMENT_HEADERS to ' || i.user_name || ';'
              || 'GRANT update on ce.CE_STATEMENT_LINES to ' || i.user_name || ';'
              || 'GRANT select on apps.XX_AGENTS_NO_V to ' || i.user_name || ';' ;
execute immediate v_exe_grant;
update xx_office_user_imp
set transfered = 1
where id = i.id
v_exe_grant := '';
end loop;
end;
/After execute the PL/SQL block i receive the error:
Error report:
ORA-00911: invalid character
ORA-06512: at line 79
00911. 00000 - "invalid character"
*Cause:    identifiers may not start with any ASCII character other than
           letters and numbers. $#_ are also allowed after the first
           character. Identifiers enclosed by doublequotes may contain
           any character other than a doublequote. Alternative quotes
           (q'#...#') cannot use spaces, tabs, or carriage returns as
           delimiters. For all other contexts, consult the SQL Language
           Reference Manual.
*Action:Any ideas? I think i call execute immediate correctly.
DB Version: 11g
Unfortunately i cannot provide you with the sql of the other tables to create them.... Maybe you should try without all the grants... :)
Thanks in advance,
Bahchevanov.
Edited by: bahchevanov on Oct 11, 2012 6:14 AM

bahchevanov wrote:
Any ideas? Sure. EXECUTE IMMEDIATE executes a single statment while you are trying to execute whole bunch. So use:
execute immediate 'create user ' || i.user_name || ' identified by ' || i.user_name;
execute immediate 'GRANT create session to ' || i.user_name;
execute immediate 'GRANT select on apps.XXBG_CE_STATEMENT_HEADERS_CASH to ' || i.user_name;
.SY.

Business Folder Upgrade from 11i to R12

Hi,
We are upgrading from 11.5.10.2 to R12.
In the process, we have to upgrade discoverer folder also.
To undergo the change, we are testing one report from 11i to R12.
The report has the business folder as po_vendors in 11i, which is taking data from PO_VENDORS table from PO schema.
As the PO_VENDORS table is obselete in R12.
We are trying to change the PO_VENDORS table to AP_SUPPLIERS table and we are changing schema from PO to AP.
We were able to do that in Disco Admin, but when I run the report from Desktop, we are not able to get the data.
Where in SQLInspector we can that the query is changed, one more interesting thing is when we run the query from backend for exact set of parameters, its returning data.
Is there anything which we need to take care, are we doing anything wrong.
Please help.
Thanks,
S

Hi,
We are using 3 views and a materialized view.
Object names are
1) AP_INVOICES
2) AP_INVOICES_DISTRIBUTIONS
3) AP_SUPPLIERS
now when we change the views to base tables for e.g. AP_INVOICES to AP_INVOICES_ALL and AP_INVOICES_DISTRIBUTIONS to AP_INVOICES_DISTRIBUTIONS_ALL then our report is givng data.
PFB the query.
SELECT DISTINCT o215482.SEGMENT2 as E215623,o215482.SEGMENT2_DESCRIPTION as E215625,o215476.ATTRIBUTE5 as E216133,o215482.SEGMENT4 as E216142,o215482.SEGMENT1 as E216190,o215482.SEGMENT3 as E216208,o215482.SEGMENT3_DESCRIPTION as E216210,o215476.INVOICE_DATE as E216817,o215476.PAYMENT_STATUS_FLAG as E217125,o215473.PERIOD_NAME as E217133,o215487.VENDOR_NAME as E217379,o215487.SEGMENT1 as E217385,(SUBSTR(o215476.INVOICE_NUM,1,12)) as E217632,as215592_217133_OLD as as215592_217133_OLD,o215473.AMOUNT as E215705,NVL(o215476.INVOICE_AMOUNT,0) as E216800
FROM APPS.AP_INVOICE_DISTRIBUTIONS o215473,
APPS.AP_INVOICES o215476,
APPS.JS_GL_CODE_COMBINATIONS_MV o215482,
AP.AP_SUPPLIERS o215487,
( SELECT o215509.PERIOD_NAME AS as215592_217133_OLD_2, MAX(o215509.START_DATE) AS as215592_217133_OLD FROM ( SELECT gl.period_name ,gl.start_date ,gl.end_date ,gl.period_set_name FROM gl.gl_periods gl ) o215509 WHERE (o215509.PERIOD_SET_NAME = 'JS_GL_Calendar') GROUP BY o215509.PERIOD_NAME)
WHERE ( (o215476.INVOICE_ID = o215473.INVOICE_ID)
and (o215482.CODE_COMBINATION_ID = o215473.DIST_CODE_COMBINATION_ID)
and (o215487.VENDOR_ID = o215476.VENDOR_ID)
and (o215473.PERIOD_NAME = as215592_217133_OLD_2(+)))
AND (o215482.SEGMENT6 LIKE :"Project Parameter 1")
AND (o215482.SEGMENT5 LIKE :"Category Code Parameter 1")
AND (o215482.SEGMENT4 LIKE :"Business Unit Parameter 1")
AND (o215482.SEGMENT3 LIKE :"Cost Centre Parameter 1")
AND (o215482.SEGMENT2 LIKE :"Account Parameter 1")
AND (o215482.SEGMENT1 LIKE :"Company Parameter 1")
AND (o215473.PERIOD_NAME LIKE :"Period Name Parameter 1")
AND (o215487.SEGMENT1 LIKE :"Supplier Number Parameter 1")
AND (o215476.CANCELLED_DATE IS NULL )
AND ( ( UPPER(o215473.LINE_TYPE_LOOKUP_CODE) = UPPER('ITEM') OR UPPER(o215473.LINE_TYPE_LOOKUP_CODE) = UPPER('FREIGHT') ) )
ORDER BY o215482.SEGMENT1 ASC , o215482.SEGMENT3 ASC , o215482.SEGMENT2 ASC , o215482.SEGMENT4 ASC , o215487.SEGMENT1 ASC , o215487.VENDOR_NAME ASC , (SUBSTR(o215476.INVOICE_NUM,1,12)) ASC ;
Kindly help.
Thanks,
S

Importing CIS: Extended Suppliers fields

We are migrating supplier (and sub-con) data for our client. Sub-contractor requires data in additional fields
CIS_ENABLED_FLAG
CIS_VERIFICATION_DATE
UNIQUE_TAX_REFERENCE_NUM
NATIONAL_INSURANCE_NUMBER
COMPANY_REGISTRATION_NUMBER
VERIFICATION_NUMBER
SALUTATION
FIRST_NAME
SECOND_NAME
LAST_NAME
TRADING_NAME
PARTNERSHIP_UTR
PARTNERSHIP_NAME
WORK_REFERENCE
MATCH_STATUS_FLAG
These fields are available in AP_SUPPLIERS but not available in supplier open interface table.
How can we import these fields?
As of now my plan is to create suppliers and supplier sites by Oracle Supplier open interface. Then write a manual update to update the CIS information.
Please confirm the correct approach. Is there an API to import the CIS: Extended Suppliers fields
Edited by: user13656910 on 01-Mar-2011 03:56

(Do Not Post Product-Related Questions Here)
(Do Not Post Product-Related Questions Here)
(Do Not Post Product-Related Questions Here)
(Do Not Post Product-Related Questions Here)
(Do Not Post Product-Related Questions Here)
I think you meant to ask on one of the E-Business Suite forums

Supplier Open Interface Import Employee Name

Hi,
I have a question regarding Supplier Open Interface Import. I insert an employee supplier record in ap_suppliers_int table with vendor_name = "last name + first name" of employee. But when the Supplier Open Interface Import program is executed, the vendor_name inserted in ap_suppliers table becomes "first name + last name". Why does Supplier Open Interface Import behave like this?
Any help will be appreciated. Thanks.

Hi,
Unhide the Debug (Debug Switch) parameter of the Report, Supplier Open Interface Import and run the program with Debug flag as Yes.
Please post the log to help us understand the issue.
Regards,
Sridhar

Iby_ext_party_pmt_mthds is not being created from supplier open interface

In 11i payment method the PAYMENT_METHOD_LOOKUP_CODE was stored on the po_vendors record.this value could be retrieved by :
SELECT payment_method_lookup_code
INTO v_temp_look_up
FROM po.po_vendors
WHERE Trim(UPPER (vendor_name)) = Trim(UPPER (var_vendor_nm));
Sites record also had PAYMENT_METHOD_LOOKUP_CODE that could be retrieved by:
select pos.payment_method_lookup_code
INTO v_temp_look_up
from po_vendors po,PO_VENDOR_SITES_ALL pos
where po.vendor_id=pos.vendor_id
AND Vendor_site_Id=var_Vendor_site_Id ;
Some of our old custom applications however ONLY USE the PAYMENT_METHOD_LOOKUP_CODE from the po.po_vendors RECORD.
Hence upon completion of the SUPPLIER OPEN INTERFACE the PAYMENT_METHOD_LOOKUP_CODE would be accessible from the po.po_vendors record.
Now we are upgrading to R12.
I did some reading and realized that r12 PAYMENT_METHOD_LOOKUP_CODE
Is stored in IBY_EXTERNAL_PAYEES_ALL and iby_ext_party_pmt_mthds.
I loaded a vendor via the interface using:
INSERT INTO AP.AP_SUPPLIERS_INT
(VENDOR_INTERFACE_ID,
VENDOR_NAME,
SEGMENT1,
VENDOR_TYPE_LOOKUP_CODE,
TERMS_ID,
SET_OF_BOOKS_ID,
PAY_DATE_BASIS_LOOKUP_CODE,
PAY_GROUP_LOOKUP_CODE,
PAYMENT_PRIORITY,
INVOICE_CURRENCY_CODE,
PAYMENT_CURRENCY_CODE,
DISTRIBUTION_SET_ID ,
ACCTS_PAY_CODE_COMBINATION_ID ,
PREPAY_CODE_COMBINATION_ID,
PAYMENT_METHOD_LOOKUP_CODE ,
TERMS_DATE_BASIS ,
ATTRIBUTE_CATEGORY,
ATTRIBUTE1,
payment_method_code)
VALUES
VAR_VENDOR_INTERFACE_ID ,
SUP_VENDOR_NAME_var,
SUP_SEGMENT1_var,
Upper(Trim(VENDOR_TYPE_LOOKUP_CODE_var)),
10000 ,
2024 ,
SUP_PAY_DATE_BASIS_LOOKUP_CODE_var,
Upper(Trim(Nvl(PAY_GROUP_LOOKUP_CODE_var))) ,
SUP_PAYMENT_PRIORITY_var,
SUP_INVOICE_CURRENCY_CODE_var,
SUP_PAYMENT_CURRENCY_CODE_var,
SUP_DISTRIBUTION_SET_ID_var,
'3007',
'3007',
'EFT',
SUP_TERMS_DATE_BASIS_var,
SUP_ATTRIBUTE_CATEGORY_var,
SUP_ATTRIBUTE1_var ,
'EFT') ;
I ran the supplier interface and it completed successfully.
I ran the query for the supplier:
SELECT * FROM ap_suppliers WHERE VENDOR_NAME ='MARVEN, MARVEN'
AND VENDOR_ID='35425'
AND PARTY_ID ='47546' ;
This query returned the correct record.
I then ran another query to get the iby_ext_party_pmt_mthds for the SUPPLIER.
SELECT * FROM iby_ext_party_pmt_mthds
WHERE ext_pmt_party_id IN (
SELECT EXT_PAYEE_ID FROM IBY_EXTERNAL_PAYEES_ALL
WHERE PAYEE_PARTY_ID='47546'
BUT IT DID NOT RETURN ANY VALUE!!!
I logged into the oracle payables and then went to the suppliers screen.
I then clicked the Payment Details link. Under the Payment Method section none of the payment methods were selected !
I checked the ‘Wire’ Payment method and saved.
I then ran the query :
I then ran another query to get the iby_ext_party_pmt_mthds for the SUPPLIER.
SELECT * FROM iby_ext_party_pmt_mthds
WHERE ext_pmt_party_id IN (
SELECT EXT_PAYEE_ID FROM IBY_EXTERNAL_PAYEES_ALL
WHERE PAYEE_PARTY_ID='47546'
And it returned the correct row.
Now I would like to know
Why is the iby_ext_party_pmt_mthds record was not created from the supplier open interface seeing that I specified a value (‘EFT’) for the payment method for the supplier?
kindly help...thanks in advance

It looks like the final answer is, I had it configured correctly. The problem I encountered was my testing of the signature. I assumed I could control the interval that was used to track the failed attempts.
I never found a way to do that and I can't find any documentation that tells me what the interval is. It is fairly small because I couldn't key in 3 failed attempts fast enough to trigger the deny action. A little patience and a scripted attack hit my server and it banned it every hour. All 3 attempts are hitting in < one second.
Signature statistics [process switch:fast switch]
signature 2157:2: packets checked [0:1] alarmed [0:0] dropped [0:0]
signature 2157:1: packets checked [0:19] alarmed [0:0] dropped [0:0]
signature 3106:0: packets checked [0:83] alarmed [0:0] dropped [0:0]
signature 3109:0: packets checked [0:10] alarmed [0:10] dropped [0:0]
signature 6250:0: packets checked [31:0] alarmed [10:0] dropped [0:0]
deny acl's created 10
signature 6056:0: packets checked [1:0] alarmed [1:0] dropped [0:0]
Interfaces configured for ips 1

Expense Report Expense Program errors in R12.1.2

Hi gurus,
I am trying to run the Expesne Report Export Program and it is erroring out the Reject code is (INCONSISTENT SUPPL SITE).Here we have to Sources
1:XpenseXpress
2: EXTAMEX
and when i run the export program for source 2 the invoices are getting created and when i run the export program for the source 1 the records are getting rejected with the error (INCONSISTENT SUPPL SITE).
The interesting thing is the vendor_id(12759) and vendor_site_id(462101) for both the sources is Same.The data for which I am running is the data from the 11i Production Instace for the previous day.The error I am getting is in R12.1.2 Instance.
I searched the tables ap_suppliers,ap_supplier_sites_all,hz_parties and hz_party_sites_all the supplier is active it has site's defined every where only thing i Observed is for the same vendor we have Vendor_site_codes as [M5H 1T1(site_id :424663,M5H1T1:462101).This is what i could research and found out.I am struck Here
                 Help would be highly appreciated.
   Thanks & Regards
        Krishna

Hi Krishna,
please check the vendor type should be "Employee".
Try to create a expense report for the same vendor site manually you will get the exact issue.
If still getting issue please send the exact error code/desc and vendor site screen shot.
Regards,
Ajit
[email protected]

Link between xla_distribution_links and ap_invoices_all

SELECT SUP.VENDOR_NAME,
              API.INVOICE_NUM,
              SUM (NVL (AEL.ACCOUNTED_DR, 0) - NVL (AEL.ACCOUNTED_CR, 0)) "BALANCE"
FROM xla.xla_ae_lines AEL,
         xla.xla_ae_headers AEH,
         (SELECT   XDL.AE_HEADER_ID,
                          XDL.AE_LINE_NUM,
                          XDL.APPLIED_TO_SOURCE_ID_NUM_1,
                          XDL.ALLOC_TO_SOURCE_ID_NUM_1,
                          APSI.INVOICE_NUM "ALLOC_TO_INVOICE_NUM",
                          XDL.EVENT_CLASS_CODE
            FROM APPS.XLA_DISTRIBUTION_LINKS XDL, AP.AP_INVOICES_ALL APSI
           WHERE XDL.APPLICATION_ID = 200
                 AND XDL.EVENT_CLASS_CODE IN
                        ('PREPAYMENTS', 'PREPAYMENT APPLICATIONS')
                 AND XDL.ROUNDING_CLASS_CODE = 'PREPAID_EXPENSE'
                 AND XDL.ALLOC_TO_SOURCE_ID_NUM_1 = APSI.INVOICE_ID
                 GROUP BY XDL.AE_HEADER_ID,
                          XDL.AE_LINE_NUM,
                          XDL.APPLIED_TO_SOURCE_ID_NUM_1,
                          XDL.ALLOC_TO_SOURCE_ID_NUM_1,
                          APSI.INVOICE_NUM,
                          XDL.EVENT_CLASS_CODE
                 ) dl, --------------VERY IMPORTANT---------------
         GL.GL_CODE_COMBINATIONS CC,
         AP.AP_SUPPLIERS SUP,
         AP.AP_INVOICES_ALL API
   WHERE     aeh.balance_type_code = 'A'
         AND aeh.ae_header_id = ael.ae_header_id
         ---hh
         AND aeh.ae_header_id = DL.ae_header_id
         AND ael.ae_line_num = DL.ae_line_num
         AND ael.ledger_id = 2022
         AND ael.code_combination_id = CC.CODE_COMBINATION_ID
         AND DL.APPLIED_TO_SOURCE_ID_NUM_1 = API.INVOICE_ID --------------VERY IMPORTANT-----------------
         AND CC.SEGMENT1 = '131061'
         AND AEL.PARTY_ID = SUP.VENDOR_ID
         AND SUP.VENDOR_NAME = 'COMPANY_NAME'
         AND TRUNC (AEH.ACCOUNTING_DATE) <= TO_DATE ('31-DEC-2012', 'DD-MON-YYYY')
GROUP BY API.INVOICE_NUM, SUP.VENDOR_NAME
HAVING          SUM (NVL (AEL.ACCOUNTED_DR, 0) - NVL (AEL.ACCOUNTED_CR, 0)) <> 0
Pleaes explain the above query. The result is the prepayment balance grouped by Vendor_name and Invoice_num. What I don't understand is the use of the inline view DL. Why would you need it? I tried to rewrite the above task as following.
select inv.vendor_id, INV.INVOICE_NUM, sum(AEL.ACCOUNTED_DR) - sum(AEL.ACCOUNTED_CR) balance
from xla.xla_ae_lines ael,
        xla.xla_ae_headers aeh,
        XLA.XLA_DISTRIBUTION_LINKS xld,
        AP.AP_INVOICES_ALL inv,
        ap.ap_invoice_distributions_all dist,
        AP.AP_SUPPLIERS sup
where ael.ae_header_id = aeh.ae_header_id AND
            XLD.AE_HEADER_ID = aeh.ae_header_id AND
            inv.invoice_id = dist.invoice_id AND
            INV.vendor_id = SUP.VENDOR_ID AND
            INV.VENDOR_ID = 407012 AND
            AEL.APPLICATION_ID = 200 AND
            INV.INVOICE_NUM = '30'
Group by inv.vendor_id, INV.INVOICE_NUM
I linked AP_INVOICES_ALL to XLA_DISTRIBUTION_LINKS with APPLIED_TO_SOURCE_ID_NUM_1. But in the first query I posted, XLA_DISTRIBUTION_LINKS and AP_INVOICES_ALL were joined twice - first in the inline view DL using ALLOC_TO_SOURCE_ID_NUM_1, then in the main query using APPLIED_TO_SOURCE_ID_NUM_1. Oracle ETRM says nothing about the usage of ALLOC_TO_SOURCE_ID_NUM_1. So I am totally confused. Any hints would be appreciated

In the top query the detail level of information has been gathered from the sub query DL to make the query easy to understand but when one uses a sub query the performance takes a hit.
Thanks&Regards
[email protected]

Not being remove Blank space in Supplier Name

Dear,
Actully we have round more than 200 supplier having supplier name with space due to this client face problem especially in parameter while running reprots or sometime occur in oracle application, therefor i have developed this routine to remove space from the left & right side of suppliername, but not being update although some update get performed when package execute showig status sucessfull & error is blank as mentioned below.
If any know about to update supplier name in Fron-End, right now we update supplier name but it's not wokrin could y please guide how can we upadate supplier name individulay so we can do it fron-end as per needed.
DBMS_OUTPUT.PUT_LINE(' STATUS '||v_return_status||' ERROR '||v_error_msg);
STATUS S ERROR
declare
v_return_status varchar2(100); --OUT NOCOPY VARCHAR2,
v_error_msg varchar2(100); --OUT NOCOPY VARCHAR2);
begin
for i in (
select s.*,par.jgzz_fiscal_code,par.sic_code,par.tax_reference,par.tax_name From ap_suppliers s,hz_parties par
where ltrim(rtrim(s.vendor_name)) <> s.vendor_name
and s.vendor_name = par.party_name
and created_by_module = 'AP_SUPPLIERS_API'
and vendor_name = 'ABC ' ) loop
v_return_status := null;
v_error_msg := null;
POS_VENDOR_PUB_PKG.Update_Vendor
p_vendor_id => i.vendor_id ,
p_segment1 => i.segment1 ,
p_vendor_name => ltrim(rtrim(i.vendor_name)),
p_vendor_name_alt => i.vendor_name_alt ,
p_summary_flag => i.summary_flag ,
p_enabled_flag => i.enabled_flag ,
p_segment2 => i.segment2 ,
p_segment3 => i.segment3 ,
p_segment4 => i.segment4 ,
p_segment5 => i.segment5 ,
p_employee_id => i.employee_id ,
p_vendor_type_lookup_code => i.vendor_type_lookup_code ,
p_customer_num => i.customer_num ,
p_one_time_flag => i.one_time_flag ,
p_parent_vendor_id => i.parent_vendor_id ,
p_min_order_amount => i.min_order_amount ,
p_terms_id => i.terms_id ,
p_set_of_books_id => i.set_of_books_id ,
p_always_take_disc_flag => i.always_take_disc_flag ,
p_pay_date_basis_lookup_code => i.pay_date_basis_lookup_code ,
p_pay_group_lookup_code => i.pay_group_lookup_code ,
p_payment_priority => i.payment_priority ,
p_invoice_currency_code => i.invoice_currency_code ,
p_payment_currency_code => i.payment_currency_code ,
p_invoice_amount_limit => i.invoice_amount_limit ,
p_hold_all_payments_flag => i.hold_all_payments_flag ,
p_hold_future_payments_flag => i.hold_future_payments_flag ,
p_hold_reason => i.hold_reason ,
p_type_1099 => i.type_1099 ,
p_withhold_status_lookup_code => i.withholding_status_lookup_code ,
p_withholding_start_date => i.withholding_start_date ,
p_org_type_lookup_code => i.organization_type_lookup_code ,
p_start_date_active => i.start_date_active ,
p_end_date_active => i.end_date_active ,
p_minority_group_lookup_code => i.minority_group_lookup_code ,
p_women_owned_flag => i.women_owned_flag ,
p_small_business_flag => i.small_business_flag ,
p_hold_flag => i.hold_flag ,
p_purchasing_hold_reason => i.purchasing_hold_reason ,
p_hold_by => i.hold_by ,
p_hold_date => i.hold_date ,
p_terms_date_basis => i.terms_date_basis ,
p_inspection_required_flag => i.inspection_required_flag ,
p_receipt_required_flag => i.receipt_required_flag ,
p_qty_rcv_tolerance => i.qty_rcv_tolerance ,
p_qty_rcv_exception_code => i.qty_rcv_exception_code ,
p_enforce_ship_to_loc_code => i.enforce_ship_to_location_code ,
p_days_early_receipt_allowed => i.days_early_receipt_allowed ,
p_days_late_receipt_allowed => i.days_late_receipt_allowed ,
p_receipt_days_exception_code => i.receipt_days_exception_code ,
p_receiving_routing_id => i.receiving_routing_id ,
p_allow_substi_receipts_flag => i.allow_substitute_receipts_flag ,
p_allow_unorder_receipts_flag => i.allow_unordered_receipts_flag ,
p_hold_unmatched_invoices_flag => i.hold_unmatched_invoices_flag ,
p_tax_verification_date => i.tax_verification_date ,
p_name_control => i.name_control ,
p_state_reportable_flag => i.state_reportable_flag ,
p_federal_reportable_flag => i.federal_reportable_flag ,
p_attribute_category => i.attribute_category ,
p_attribute1 => i.attribute1 ,
p_attribute2 => i.attribute2 ,
p_attribute3 => i.attribute3 ,
p_attribute4 => i.attribute4 ,
p_attribute5 => i.attribute5 ,
p_attribute6 => i.attribute6 ,
p_attribute7 => i.attribute7 ,
p_attribute8 => i.attribute8 ,
p_attribute9 => i.attribute9 ,
p_attribute10 => i.attribute10 ,
p_attribute11 => i.attribute11 ,
p_attribute12 => i.attribute12 ,
p_attribute13 => i.attribute13 ,
p_attribute14 => i.attribute14 ,
p_attribute15 => i.attribute15 ,
p_auto_calculate_interest_flag => i.auto_calculate_interest_flag ,
p_validation_number => i.validation_number ,
p_tax_reporting_name => i.tax_reporting_name ,
p_check_digits => i.check_digits ,
p_allow_awt_flag => i.allow_awt_flag ,
p_awt_group_id => i.awt_group_id ,
p_pay_awt_group_id => i.pay_awt_group_id ,
p_awt_group_name => null ,
p_pay_awt_group_name => NULL ,
p_global_attribute1 => i.global_attribute1 ,
p_global_attribute2 => i.global_attribute2 ,
p_global_attribute3 => i.global_attribute3 ,
p_global_attribute4 => i.global_attribute4 ,
p_global_attribute5 => i.global_attribute5 ,
p_global_attribute6 => i.global_attribute6 ,
p_global_attribute7 => i.global_attribute7 ,
p_global_attribute8 => i.global_attribute8 ,
p_global_attribute9 => i.global_attribute9,
p_global_attribute10 => i.global_attribute10 ,
p_global_attribute11 => i.global_attribute11 ,
p_global_attribute12 => i.global_attribute12 ,
p_global_attribute13 => i.global_attribute13 ,
p_global_attribute14 => i.global_attribute14 ,
p_global_attribute15 => i.global_attribute15 ,
p_global_attribute16 => i.global_attribute16 ,
p_global_attribute17 => i.global_attribute17 ,
p_global_attribute18 => i.global_attribute18 ,
p_global_attribute19 => i.global_attribute19 ,
p_global_attribute20 => i.global_attribute20 ,
p_global_attribute_category => i.global_attribute_category ,
p_bank_charge_bearer => i.bank_charge_bearer ,
p_bank_branch_type => i.bank_branch_type,
p_match_option => i.match_option ,
p_create_debit_memo_flag => i.create_debit_memo_flag ,
p_party_id => 2085 ,
p_parent_party_id => i.parent_party_id ,
p_jgzz_fiscal_code => i.jgzz_fiscal_code,
p_sic_code => i.sic_code ,
p_tax_reference => i.tax_reference,
p_inventory_organization_id => NULL ,
p_terms_name => NULL ,
p_default_terms_id => NULL ,
p_ni_number => NULL ,
p_last_update_date => NULL ,
x_return_status => v_return_status,
x_error_msg => v_error_msg
DBMS_OUTPUT.PUT_LINE(' STATU S '||v_return_status||' ERROR '||v_error_msg);
end loop;
end;
Edited by: oracle0282 on Dec 24, 2011 3:36 AM
Edited by: oracle0282 on Dec 25, 2011 9:51 PM

Just a thought..
How about creating a new supplier and then opt for Supplier Merge?
Using supplier merge you may transfer all the open PO's and invoices of the old supplier to the new
supplier. By using the supplier merge, the old supplier would be end date automatically by the
system.
P.S. I am NOT sure whether there exist a datafix to edit the supplier name.
Regards,
Srini

How can I pass dynamic value as a user input parameter in discoverer?

Hi,
I have a requirement for a discoverer report like this: The report will display only details for Suppliers that have expired (or soon to be) Insurance details. That is the Expiration Date is less than or equal to the day the report is being run plus any days specified in the Number of Days in the Future Parameter.
The sample code as:
SELECT s.segment1 vendor_number
,s.vendor_name
,flv1.meaning classification
,pca.certificate_number
,pca.certifying_agency
,pca.expiration_date
,flv2.meaning status
FROM ap_suppliers s
,pos_bus_class_attr pca
,fnd_lookup_values flv1
,fnd_lookup_values flv2
WHERE pca.vendor_id = s.vendor_id
AND flv1.lookup_code = pca.lookup_code
AND flv1.lookup_type = pca.lookup_type
AND flv2.lookup_code = pca.class_status
AND flv2.lookup_type = 'POS_BUS_CLASS_STATUSES'
AND pca.expiration_date <= trunc(sysdate) + <No. of Days in the Future>
order by pca.expiration_date asc
Now the parameter is Number of Days in the Future (Enter the number days in the future to extract the data. This will default to 0).
Is it possible in discoverer to do so as in query i do that like a condition as pca.expiration_date <= trunc(sysdate) + <No. of Days in the Future>.
How can I pass <No. of Days in the Future> as a user input parameter in discoverer?
Please help.

Hi,
All you need to do is to create the condition in the discoverer instead of in the query.
Create a custom folder containing the following sq (note that i removed the condition)l:
SELECT s.segment1 vendor_number
,s.vendor_name
,flv1.meaning classification
,pca.certificate_number
,pca.certifying_agency
,pca.expiration_date
,flv2.meaning status
FROM ap_suppliers s
,pos_bus_class_attr pca
,fnd_lookup_values flv1
,fnd_lookup_values flv2
WHERE pca.vendor_id = s.vendor_id
AND flv1.lookup_code = pca.lookup_code
AND flv1.lookup_type = pca.lookup_type
AND flv2.lookup_code = pca.class_status
AND flv2.lookup_type = 'POS_BUS_CLASS_STATUSES'
Then create a discoverer report using this folder using all fields.
Create a new calculation as (use this exact syntax):
Sysdate + :No_of_Days_in_the_Future
Create a new condition:
pca.expiration_date <= <your calculation>
To complete it add a sort as you did in the SQL.
That's it.
Tamir

AP_SUPPLIERS ENABLE_FLAG

Similar Messages

Maybe you are looking for