Hello,
We recently had a database refresh from production to devlopment. After refresh, the AP20.1 screen is not working properly. When we do a Next or Previous
the system hangs showing the hourglass for long time. I tried to debug the issue and found the system hangs when trying to execute the APISET3 NLT command.we are unable to find out the issue. There is nothing wrong in the code , the problem is only with database i think.
when i see the ladb.log file after the process is killed i see the following query
select /*+ INDEX_ASC("API" "APISET3")*/ TO_CHAR("API"."COMPANY",'FM0999'), "API "."VENDOR", "API"."INVOICE", TO_CHAR("API"."SUFFIX",'FM099'), TO_CHAR("API"."CAN CEL_SEQ",'FM0999'), TO_CHAR("API"."CANCEL_DATE", 'YYYYMMDD'), TO_CHAR("API"."BAT CH_NUM",'FM099999'), TO_CHAR("API"."BATCH_DATE", 'YYYYMMDD'), "API"."VOUCHER_NBR ", "API"."AUTH_CODE", "API"."PROC_LEVEL", "API"."ACCR_CODE", "API"."INVOICE_TYPE ", "API"."INV_CURRENCY", "API"."PAY_CURRENCY", TO_CHAR("API"."INVOICE_DTE", 'YYY YMMDD'), "API"."PURCH_FR_LOC", "API"."PO_NUMBER", TO_CHAR("API"."PO_RELEASE",'FM 0999'), "API"."PO_CODE", "API"."DESCRIPTION", "API"."BASE_INV_AMT", "API"."BASE_ ACT_AMT", TO_CHAR("API"."BASE_ND",'FM0'), "API"."TRAN_INV_AMT", "API"."TRAN_ALOW _AMT", "API"."TRAN_TXBL_AMT", TO_CHAR("API"."TRAN_ND",'FM0'), "API"."TRAN_TAX_AM T", "API"."BASE_DISC_AMT", "API"."TRAN_DISC_AMT", "API"."BASE_TOT_PMT", "API"."T RAN_TOT_PMT", "API"."BASE_TOT_DIST", "API"."TRAN_TOT_DIST", "API"."TRAN_TOT_TAX" , "API"."TRAN_TOT_TXBL", "API"."TRAN_PAID_AMT", "API"."ORIG_CNV_RATE", "API"."AN TICIPATION", "API"."DISCOUNT_RT", TO_CHAR("API"."DISC_DATE", 'YYYYMMDD'), TO_CHA R("API"."DUE_DATE", 'YYYYMMDD'), TO_CHAR("API"."NBR_SPLIT_PMT",'FM099'), "API"." SPLIT_PMT_SCH", TO_CHAR("API"."NBR_RECUR_PMT",'FM099'), "API"."RECUR_FREQ", "API "."REMIT_TO_CODE", "API"."CASH_CODE", "API"."BANK_INST_CODE", "API"."CURR_RECALC ", "API"."TAX_CODE", "API"."INCOME_CODE", "API"."DIST_CODE", TO_CHAR("API"."REC_ STATUS",'FM0'), TO_CHAR("API"."CREATE_DATE", 'YYYYMMDD'), TO_CHAR("API"."DISTRIB _DATE", 'YYYYMMDD'), "API"."OPERATOR", TO_CHAR("API"."CREATION_TIME",'FM099999') , "API"."VENDOR_GROUP", "API"."PAY_VENDOR", "API"."PAY_GROUP", "API"."INVOICE_GR OUP", TO_CHAR("API"."LAST_DIST_SEQ",'FM0999'), TO_CHAR("API"."LAST_PMT_SEQ",'FM0 999'), "API"."DISCOUNT_CODE", "API"."INVOICE_SOURCE", "API"."INVC_REF_TYPE", "AP
I"."APPROVED_FLAG", "API"."APPRV_OPERATOR", TO_CHAR("API"."RETURN_NUMBER",'FM099 9999999'), "API"."JRNL_BOOK_NBR", "API"."TAX_POINT", TO_CHAR("API"."OBJ_ID",'FM0 99999999999'), TO_CHAR("API"."RECON_DATE", 'YYYYMMDD'), TO_CHAR("API"."POD_PRINT ED",'FM0'), "API"."MATCH_REF_NBR", "API"."MATCH_FL", "API"."TERMS_CD", TO_CHAR(" API"."RCPT_INV_DATE", 'YYYYMMDD'), "API"."RETAIL_AMT", TO_CHAR("API"."MATCH_STAT US",'FM0'), "API"."REASON_CODE", "API"."HANDLING_CODE", "API"."MATCH_AMT", "API" ."AOC_ALLOW_AMT", "API"."LOCATION", TO_CHAR("API"."MATCH_OBJ_ID",'FM099999999999 '), "API"."CBPRINT_FL", "API"."MATCH_TABLE", "API"."TAX_CODE_CNTL", TO_CHAR("API "."LAST_MATCH_LN",'FM0999'), "API"."MATCH_LEVEL", TO_CHAR("API"."MATCH_DATE", 'Y YYYMMDD'), "API"."PO_INV_TAX", "API"."BYPASS_MATCH", "API"."SERVICE_FL", "API"." SERVICE_AMT", "API"."BUYER", "API"."FINAL_DST_FLAG", "API"."NOTC", "API"."STAT_P ROC", "API"."SHIP_VIA", "API"."UNLOADING_PORT", TO_CHAR("API"."INTRASTAT_NBR",'F M099999999999'), "API"."DROPSHIP_FL", "API"."FOB_CODE", TO_CHAR("API"."JBK_SEQ_N BR",'FM0999999999'), "API"."DIVERSE_CODE", "API"."FLEX_FLAG", "API"."RULE_GROUP" , TO_CHAR("API"."FLOAT_DAYS",'FM099'), "API"."MTCH_PREPAY_FL", TO_CHAR("API"."MT CH_PREPAY_MT",'FM0'), TO_CHAR("API"."PREPAY_DATE", 'YYYYMMDD'), "API"."PRPY_DISC _CODE", "API"."PRPY_REF_NBR", "API"."PRPY_RTL_AMT", "API"."PRPY_AMT", "API"."PRP Y_AOC_AMT", "API"."PRPY_TAX_AMT", "API"."PRPY_SERV_AMT", TO_CHAR("API"."COCO_FL" ,'FM0'), "API"."MATCH_AOC", "API"."HASH_QTY", "API"."XREF_VENDOR", TO_CHAR("API" ."MTCH_ERR_TYPE",'FM09'), "API"."BT_AMT", TO_CHAR("API"."DISC_POINT",'FM0'), "AP I"."TAX_FLAG", "API"."CHARGEBACK_FL", "API"."ORIGIN_COUNTRY", "API"."ORIGIN_REGI ON", "API"."DEST_COUNTRY", "API"."DEST_REGION", "API"."TRANSPORT_MODE", "API"."L _INDEX" from LAWSON."APINVOICE" "API" where "API"."REC_STATUS">:1 order by "API
"."REC_STATUS", "API"."COMPANY", "API"."BATCH_NUM", "API"."AUTH_CODE", "API"."OP ERATOR", "API"."CREATE_DATE", "API"."CREATION_TIME", "API"."VENDOR", "API"."INVO ICE", "API"."SUFFIX", "API"."CANCEL_SEQ" --- Start of Key area dump --- "REC_STATUS"=0 "COMPANY"=9005 "BATCH_NUM"=000000 "AUTH_CODE"= "OPERATOR"= "CREATE_DATE"=00000000 "CREATION_TIME"=000000 "VENDOR"= "INVOICE"= "SUFFIX"=000 "CANCEL_SEQ"=0000 --- End of Key area dump ---
I could not understand anything here in this message. But i feel there is something wrong in the query built by Lawso. The where clause has only
one condition rec_status > 0 but we are looking for the data rec_status=0 and there is no condition on company field at all. But the key dump area
show data correctly what we passed.
any help on this please?
--Srikanth
There are a set of verify* commands you can use to check for missing indexes compared to Lawson dictionary. Run that against APINVOICE, AP system code, and entire product line and then rebuild missing indexes using the appropriate bld*ddl utility.
i verified with ora and the index APISET3 is build correctly...
one more finding is that i could run the same test cases in another test environment without any problem...
How was the data copied from prod to test?
we did sand copy to copy from prod to test..