Action Plan

Embed Size (px)

Citation preview

Hello khaled - Please do the following in your TEST instance:1.Review readme of patch 14461780:R12.GME.B 2.apply patch 14461780:R12.GME.B in your TEST.3.Confirm the following file versionGMETTMTX.fmb 120.77.12010000.65 + 4.Retest the issue .Thank youGihan ----------------------------------------------------------------------------Hello khaled - In the Read me of patch 14461780:R12.GME.B PATCH SEQUENCE:The following patches are required and should be applied to a test areafirst. Thoroughly test the issue as well as all the normal day to day batchactions you commonly use !!You must download and install these patches unless they have beenpreviously applied. Please apply in the order listed.1. Apply the prerequisite patch 8486861:R12.GMA.B2. Apply the prerequisite patch 9446274:R12.GMD.B3. Apply the prerequisite patch 12916273:R12.INV.B4. Apply the prerequisite patch 12916291:R12.WMS.B5. Apply the prerequisite patch 11819064:R12.FND.B6. Apply the prerequisite patch 13967250:R12.INV.B7. Apply the prerequisite patch 9417673:R12.GMF.B8. Apply the prerequisite patch 14080575:R12.INV.B9. Apply patch 14461780:R12.GME.BSPECIAL INSTALL NOTES/INSTRUCTIONS:Please recompile all INV and GME PLLs and forms after applying this patch.This patch includes 13981238:R12.GME.B.If you make use of release_step and/or complete_step api's, and you arepassing in p_commit of False, then you will have to change your wrapper codeto call the save_batch api to have the data properly saved after callingrelease or complete step. If you are already making a call to save_batchyou will have to pass in 2 for the p_table parameter.Please ask your DBA to follow the instructions in the read me of patch 14461780:R12.GME.B Thank youGihan----------------------------------------------------------------------------------------------------------on the /APP1- enable maintenance mode ./adadmin2- apply the patches ./adpatch------------------1- English/APP/patch/15102012/1/14080575R12.INV.B/p14080575_R12.INV.B_R12_AIX64-5L/14080575u14080575.drv - Arabic/APP/patch/15102012/1/14080575R12.INV.B/p14080575_R12.INV.B_R12_ar/14080575_ARu14080575.drv------------------2- English/APP/patch/15102012/2/13967250R12.INV.B/p13967250_R12.INV.B_R12_AIX64-5L/13967250u13967250.drv - Arabic/APP/patch/15102012/2/13967250R12.INV.B/p13967250_R12.INV.B_R12_ar/13967250_ARu13967250.drv------------------3- English/APP/patch/15102012/3/8618150R12.GME.B/p8618150_R12.GME.B_R12_GENERIC/8618150u8618150.drv - Arabic/APP/patch/15102012/3/8618150R12.GME.B/p8618150_R12.GME.B_R12_ar/8618150_ARu8618150.drv------------------4- Disable maintenance mode-----------------5- Close /APP , /services-----------------6- Recompile all INV , GME----------------7- Open /APP , /services---------------8- Enable maintenance mode---------------9- English /APP/patch/15102012/4/9417673R12.GMF.B/p9417673_R12.GMF.B_R12_AIX64-5L/9417673 u9417673.drv - Arabic/APP/patch/15102012/4/9417673R12.GMF.B/p9417673_R12.GMF.B_R12_ar/9417673_ARu9417673.drv------------------10- English /APP/patch/15102012/5/12916273R12.INV.B/p12916273_R12.INV.B_R12_AIX64-5L/12916273 u12916273.drv - Arabic/APP/patch/15102012/5/12916273R12.INV.B/p12916273_R12.INV.B_R12_ar/12916273_ARu12916273.drv------------------11- English /APP/patch/15102012/6/12916291R12.WMS.B/p12916291_R12.WMS.B_R12_AIX64-5L/12916291 u12916291.drv - Arabic/APP/patch/15102012/6/12916291R12.WMS.B/p12916291_R12.WMS.B_R12_ar/12916291_ARu12916291.drv------------------12- English /APP/patch/15102012/7/11819064R12.FND.B/p11819064_R12.FND.B_R12_AIX64-5L/11819064 u11819064.drv - Arabic/APP/patch/15102012/7/11819064R12.FND.B/p11819064_R12.FND.B_R12_ar/11819064_ARu11819064.drv------------------13- English /APP/patch/15102012/8/14461780R12.GME.B/p14461780_R12.GME.B_R12_GENERIC/14461780 u14461780.drv - Arabic/APP/patch/15102012/8/14461780R12.GME.B/p14461780_R12.GME.B_R12_ar/14461780_ARu14461780.drv--------------------14- The problem happend ---error inthe apps--------------------------------------------------------Hello AhmedPlease provide the following :1. invalid objects appears after applying the patch2.screen shot verify error messagethank youGihan -----------------------------------------------------------Hello khaled - Please try to compile the Invalid objects using the following Note Please review the following note to solve the invalid objects Note 300056.1 Debug and Validate Invalid ObjectsNote 314538.1 How to Compile Invalid Objectsif you get compilation error please provide me this errors RegardsSamer------------------------------------------------------------------Hello khaled - Please compile the following invalids and provide me the errorsalter package GME_MOBILE_LOVS compile body;alter package GME_MOBILE_TXN compile body;alter package OE_MASS_CHANGE_PVT compile body;alter package WMS_OP_INBOUND_PVT compile body;alter INL_ENTER_RECEIPTS_V compile;alter INL_IR_SOURCE_LINES_V compile;alter INL_PO_SOURCE_LINES_V compile;alter INL_RMA_SOURCE_LINES_V compile;RegardsSamer----------------------------------------------------------------HiSQL> alter package GME_MOBILE_LOVS compile body;Warning: Package Body altered with compilation errors.SQL> show errorErrors for PACKAGE BODY GME_MOBILE_LOVS:LINE/COL ERROR-------- -----------------------------------------------------------------312/13 PLS-00323: subprogram or cursor 'LOT_ONHAND_EXP_LOV' is declaredin a package specification and must be defined in the packagebody----------------------SQL> alter package GME_MOBILE_TXN compile body;Warning: Package Body altered with compilation errors.SQL> show errorErrors for PACKAGE BODY GME_MOBILE_TXN:LINE/COL ERROR-------- -----------------------------------------------------------------51/13 PLS-00323: subprogram or cursor 'CREATE_MATERIAL_TXN' is declaredin a package specification and must be defined in the packagebody640/11 PLS-00323: subprogram or cursor 'PRINT_LABEL' is declared in apackage specification and must be defined in the package body---------------------------SQL> alter package OE_MASS_CHANGE_PVT compile body;Package body altered.------------------------SQL> alter package WMS_OP_INBOUND_PVT compile body;Warning: Package Body altered with compilation errors.SQL> show errorErrors for PACKAGE BODY WMS_OP_INBOUND_PVT:LINE/COL ERROR-------- -----------------------------------------------------------------2102/6 PL/SQL: Statement ignored2102/6 PLS-00306: wrong number or types of arguments in call to'REVERT_LOC_SUGGESTED_CAPACITY'------------SQL> alter view INL_ENTER_RECEIPTS_V compile;Warning: View altered with compilation errors.SQL> show errorErrors for PACKAGE BODY WMS_OP_INBOUND_PVT:LINE/COL ERROR-------- -----------------------------------------------------------------2102/6 PL/SQL: Statement ignored2102/6 PLS-00306: wrong number or types of arguments in call to'REVERT_LOC_SUGGESTED_CAPACITY'---------------------------------SQL> alter view INL_IR_SOURCE_LINES_V compile;Warning: View altered with compilation errors.SQL> show errorErrors for PACKAGE BODY WMS_OP_INBOUND_PVT:LINE/COL ERROR-------- -----------------------------------------------------------------2102/6 PL/SQL: Statement ignored2102/6 PLS-00306: wrong number or types of arguments in call to'REVERT_LOC_SUGGESTED_CAPACITY'----------------SQL> alter view INL_PO_SOURCE_LINES_V compile;Warning: View altered with compilation errors.SQL> show errorErrors for PACKAGE BODY WMS_OP_INBOUND_PVT:LINE/COL ERROR-------- -----------------------------------------------------------------2102/6 PL/SQL: Statement ignored2102/6 PLS-00306: wrong number or types of arguments in call to'REVERT_LOC_SUGGESTED_CAPACITY'------------------------------------------SQL> alter view INL_RMA_SOURCE_LINES_V compile;Warning: View altered with compilation errors.SQL> show errorErrors for PACKAGE BODY WMS_OP_INBOUND_PVT:LINE/COL ERROR-------- -------------------------2102/6 PL/SQL: Statement ignored2102/6 PLS-00306: wrong number or types of arguments in call to'REVERT_LOC_SUGGESTED_CAPACITY'Thanks,------------------------------------------------------------------------------Hello khaled - please check if the following prerequest is applied prerequisite patch 8486861:R12.GMA.Bprerequisite patch 9446274:R12.GMD.Bprerequisite patch 12916273:R12.INV.Bprerequisite patch 12916291:R12.WMS.Bprerequisite patch 11819064:R12.FND.Bprerequisite patch 13967250:R12.INV.Bprerequisite patch 9417673:R12.GMF.Bprerequisite patch 14080575:R12.INV.Bpatch 14461780:R12.GME.B---------------------------------------------------------------------------------Hello khaled - please after all the patch installed use the Ad-admin Utility to recompile all INV and GME PLLs and forms RegardsSamer-------------------------------------------------------------------------------Hello khaled - please provide me the output of the followingselect text from user_source where name='GME_MOBILE_LOVS' and line=2select text from user_source where name=GME_MOBILE_TXN ' and line=2select text from user_source where name='OE_MASS_CHANGE_PVT' and line=2select text from user_source where name=WMS_OP_INBOUND_PVT ' and line=2RegardsSamer---------------------------------------------------------------------------------Hi,select text from user_source where name='GME_MOBILE_LOVS' and line=2"/* $Header: GMEMLOVS.pls 120.17.12010000.3 2011/05/20 14:38:26 gmurator ship $ */""/* $Header: GMEMLOVB.pls 120.33.12010000.2 2008/07/29 10:07:45 skommine ship $ */"=============================================================select text from user_source where name='GME_MOBILE_TXN ' and line=2"/* $Header: GMEMOTXS.pls 120.13.12010000.5 2011/05/20 14:42:53 gmurator ship $ */""/* $Header: GMEMOTXB.pls 120.29 2008/04/15 19:13:03 adeshmuk ship $ */"=============================================================select text from user_source where name='OE_MASS_CHANGE_PVT' and line=2"/* $Header: OEXVMSCS.pls 120.4.12010000.4 2008/11/15 10:57:41 sgoli ship $ */""/* $Header: OEXVMSCB.pls 120.8.12010000.5 2008/11/15 10:58:25 sgoli ship $ */"========================================================select text from user_source where name=WMS_OP_INBOUND_PVT ' and line=2"/*$Header: WMSOPIBS.pls 120.2.12010000.2 2008/10/10 07:43:51 abasheer ship $*/""/*$Header: WMSOPIBB.pls 120.16.12010000.9 2010/12/31 09:00:41 abasheer ship $*/"Waiting for your action planThanks-----------------------------------------------------------------------------------Hi Khaled,There seems to be a rather large gap between the spec and the body of these problematic packages.GMEMOTXS.pls 120.13.12010000.5 This does contain a reference to CREATE_MATERIAL_TXN and PRINT_LABEL.GMEMOTXB.pls This does contain a reference to CREATE_MATERIAL_TXN but does not have a reference to PRINT_LABEL.Therefore this package body will need to be upgraded.EBS WMS: Putaway Failed Due to Invalid Object WMS_OP_INBOUND_PVT (Doc ID 1443394.1)Appears to address WMS_OP_INBOUND_PVT error.Thank you.Paul---------------------------------------------------------------------------------------Hi,According to the provided document , the solution is applying patch 11684093In the description section in the read me in this patch the following note :6. Patch applicable only when a particular application installed:Oracle Warehouse Management SystemAnd we are not WMS organizations .. should we complete applying this patch ?Please update me ASAP.Thanks-------------------------------------------------------------------------------------Have you tried to run Adadmin, Compile Apps schema? Does the number of invalids go down?Can you check and see what version you have of $INV_TOP/patch/115/sql/INVLCPYB.pls Please also run the following:cd $AD_TOP/sqlsqlplus apps/apps @adutconf.sql and upload the resulting adutconf.lst file.Thank you.Paul------------------------------------------------------------------------------------Hi ,any way we applied the patch on test server ,just this package was solved [ WMS_OP_INBOUND_PVT ]other objects still invalid .--------------------------------------------------------------------------------------Update from Customer [email protected] - Oct 15, 2012 9:11 PM (18 days ago) Hi1- We ran Adadmin, Compile Apps schema more than three times and the same result.2- Can you check and see what version you have of $INV_TOP/patch/115/sql/INVLCPYB.pls bash-3.2$ strings -a $INV_TOP/patch/115/sql/INVLCPYB.pls |grep 'Header:'/* $Header: INVLCPYB.pls 120.11.12010000.18 2011/01/11 04:56:37 mchemban ship $*/3- cd $AD_TOP/sqlsqlplus apps/apps @adutconf.sql and upload the resulting adutconf.lst file.Kindly find the attached file.Thanks --------------------------------------------------------------------------------------Hi Khaled,I think the problem is coming from the rather large difference in time between the spec and body for these packages.For example, you show the following:$Header: GMEMLOVS.pls 120.17.12010000.3 2011/05/20 14:38:26 gmurator ship $ */$Header: GMEMLOVB.pls 120.33.12010000.2 2008/07/29 10:07:45 skommine ship $ */So the spec file here is almost 3 years newer than the body. Normally, these two files are fairly close, time stamp wise.In this case, the body does not have the same definition as the spec file for the procedure LOT_ONHAND_EXP_LOV.Applying a patch that contains the same definition for the procedure should eliminate this error.Patch 9483781:R12.GME.B is quite small, and contains the needed version of GMEMLOVB.pls.Please let us know your results.Thank you.Paul----------------------------------------------------------------------------------------------HiThe error still appears although the all packages have been compiled successfully and became valid but the views still invalid, kindly find the attached file.Thanks-------------------------------------------------------------------------------------------------Hi Khaled,This SR is to address the problems applying the patch.If you have an issue with like the one seen in your error.png, you will need to log a new SR with:Order Management Suite, product ID 497.Thank you.Paul----------------------------------------------------------------------Hi ,SQL> alter view apps.INL_ENTER_RECEIPTS_V compile;Warning: View altered with compilation errors.SQL> show errorNo errors.================================================SQL> alter view apps.INL_IR_SOURCE_LINES_V compile;Warning: View altered with compilation errors.SQL> show errorNo errors.============================================SQL> alter view apps.INL_PO_SOURCE_LINES_V compile;Warning: View altered with compilation errors.SQL> show errorNo errors.=====================================SQL> alter view apps.INL_RMA_SOURCE_LINES_V compile;Warning: View altered with compilation errors.SQL> show errorNo errors.!Thanks----------------------------------------------------------------------Hi Khaled,Please perform the following action plan:1. Check for a license for LCM and fully installedSystem Administrator>Oracle Applications Manager >License Manager>Products>license> applications product 2. Or you can run the following SQL:select fav.application_name app_name,decode(fpi.status, 'I', 'Yes','S', 'Shared','N', 'No', fpi.status) inst_status,fav.application_id app_idfrom fnd_application_tl fav,fnd_product_installations fpiwhere fav.application_id = fpi.application_idand fav.application_id = 9004order by 1;License the product and the views will compileRefer Oracle note: Views INL_ENTER_RECEIPTS_V, INL_IR_SOURCE_LINES_V, INL_PO_SOURCE_LINES_V, INL_RMA_SOURCE_LINES_V Will Not compile (Doc ID 1282260.1)Thanks and Regards------------------------------------------------------------------------Hi,select line,text from user_errors where name='INL_ENTER_RECEIPTS_V';"ORA-01790: expression must have same datatype as corresponding expression"=====================================================select line,text from user_errors where name='INL_IR_SOURCE_LINES_V';"ORA-04063: view "APPS.INL_ENTER_RECEIPTS_V" has errors"====================================================select line,text from user_errors where name='INL_PO_SOURCE_LINES_V';"ORA-04063: view "APPS.INL_ENTER_RECEIPTS_V" has errors"====================================================select line,text from user_errors where name='INL_RMA_SOURCE_LINES_V';"ORA-04063: view "APPS.INL_ENTER_RECEIPTS_V" has errors-----------------------------------------------------------------------------------------------Hi Khaled,1. Download and review the readme and pre-requisites for Patch.9836174:R12.INL.B - RECEIVING TRANSACTION STUCK WITH LC_PENDING STATUS2. Ensure that you have taken a backup of your system before applying the recommended patch.3. Apply the patch in a test environment.4. Confirm the following file versions:patch/115/manualsteps/ad_apply_patch.xml 120.4patch/115/odf/inlmtch.odf 120.2.12010000.12patch/115/odf/inlsetu.odf 120.7.12010000.4patch/115/odf/inlship.odf 120.7.12010000.24patch/115/odf/inlview.odf 120.18.12010000.52You can use the commands like the following:strings -a $INL_TOP/patch/115/odf/inl*.odf | grep '$Header'5. Retest the issue.6. Migrate the solution as appropriate to other environments.Refer Oracle note: Invalid objects: INL_IR_SOURCE_LINES_V, INL_PO_SOURCE_LINES_V, INL_RMA_SOURCE_LINES_V and INL_ENTER_RECEIPTS_V (Doc ID 1317456.1)Thanks and Regards---------------------------------------------------------------------------------------Hi ,after applying this last patch , there are no invalid objects ..But the same error [APP-WSH-23120] Still appearing in shipping transaction form , and this error is result from patch 14461780:R12.GME.Bso please if you see that this needs separated SR , open it for us with the same severity.The main issue for us still not solved.Thanks-------------------------------------------------------------------------------------------Dear Khaled,Please note this SR has been assigned to us as a highest Severity SR. A Severity 1 TAR indicates that both your Analysts and the Oracle Analysts will work this tar on a 24 by 7 basis until resolved. In order for Support to efficiently work your Severity 1 issue, please complete the following information and return it as soon as possible. While some of this may be redundant and already available in the TAR, it is to your benefit to confirm all the information regarding your issue. The more complete and detailed the information is, the better we can assist you towards resolution.1) Please confirm if the issue is visible in your PRODUCTION instance.2) Does this affect a major Milestone? If yes, please indicate clearly which is the Milestone Date and Milestone Name?3) Date by which the fix must be available for the issue.4) What is the current or projected loss in dollars as a result of this issue ?5) How is this loss of functionality causing you to not meet the business goals or requirements ?6) How many sales orders / deliveries do you have on this situation ?7) Reconfirm 2 , 24/7 Contact Information: (At least 2 contacts are necessary on a Severity 1 TAR)Manager Name:Phone Number:Email AddressContact1Contact person:E-mail Address:Phone Number:Contact2Contact person:E-mail Address:Phone Number:8) Please provide the output of the concurrent program " Diagnostics: Apps Check "Navigation path to run the concurrent request:Step 1. OM superuser -> Reports, Requests -> Request -> Single Request -> Diagnostics: Apps CheckStep 2. Please key in following parametersName = Diagnostics: Apps CheckParameters to enter:Application 1 = Order ManagementApplication 2 = Shipping ExecutionApplication 3 = InventoryApplication 4 = Advanced PricingApplication 5 = Receivables9) Screen-Shots of the issue.10) Please compile the complete APPS schema using adadmin utility and then Re-compile all the forms and Libraries for WSH. Please execute this as a first step and then if issue does not get resolved, Please execute step 8 and 9.Thanks,-------------------------------------------------------------------------------------Hi,After compiling complete APPS schema and all WSH forms and Libraries , the error still exists .Please check uploaded files .Thanks----------------------------------------------------------------------------------Hi Silviu ,1. Please confirm if this issue occur for all Sales Orders, or just for some of themIt occurs for all sales orders after picking .2. Since when you notice this issue, and what were the latest changes, such as patch install, setup change, etc, that could lead to this issue?This error appears directly after applying patch 14461780:R12.GME.B according to SR 3-6210096231and please refer to this SR too [ 3-6319977661: Error appears after applying patch 14461780:R12.GME.B ]Both currently still opened .Thanks--------------------------------------------------------------------Hello Khaled,-- To implement the solution, please execute the following steps::1. Download and review the readme and pre-requisites for Patch.8294645:R12.WSH.B2. Ensure that you have taken a backup of your system before applying the recommended patch.3. Apply the patch in a test environment.4. Confirm the following file versions:WSHDDICS.pls 120.4.12010000.1WSHDDICB.pls 120.10.12010000.1WSHSTREF.fmb 120.113.12010000.8WSHFSTRX.fmb 120.61.12010000.3 -- Shipping Transactions FormWSHQSSUI.fmb 120.20.12010000.1 -- Quick Ship FormYou can use the commands like the following:strings -a $WSH_TOP/filename |grep '$Header'5. Retest the issue.Regards,-------------------------------------------------------------------------------------Hello Khaled,From Apps Check you have the following file version:WSHSTREF.fmb 120.93.12000000.24While the patch indicated will update to the following:WSHSTREF.fmb 120.113.12010000.8 Please apply the patch in a test instance and retest the issue.Regards,-----------------------------------------------------------------------------The patch is already applied !----------------------------------------------'$Header: WSHSTREF.fmb 120.113.12010000.32 level:2 2010/02/23 08:08:27 pkm ship------------------------------------------------------------Notes [email protected] - Oct 17, 2012 6:18 PM (17 days ago) Oracle Support - Oct 17, 2012 6:18 PM (17 days ago) The appscheck provided showsDB Name Creation Date ========== ==================== ORA 20-MAR-2012 10:29:55 Oracle RDBMS/Tools Version(s) ================================================================ Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bi t Production PL/SQL Release 11.1.0.7.0 - Production CORE 11.1.0.7.0 Production TNS for IBM/AIX RISC System/6000: Version 11.1.0.7.0 - Productio n NLSRTL Version 11.1.0.7.0 - Production forms/US/WSHSTREF.fmb - 120.93.12000000.24

Action Plan:1. Please confirm that the apps check is from the instance with issue, and if it is, you will need to either apply the patch to that instance, or provide test the issue on the instance where you found:'$Header: WSHSTREF.fmb 120.113.12010000.32 level:2 2010/02/23 08:08:27 pkm ship 2. If this still occurs on the instance with WSHSTREF.fmb 120.113.12010000.32, please provide a new AppsCheck for that instance for:INV - Inventory ONT - Order Management QP - Advanced Pricing WSH - Shipping Execution 3. I could not open the files in Versions.rar - can you please provide these in a different format - possibly .doc or .pdfThanks, -----------------------------------------------------------------------The apps check is from the instance with issue and and its the same instance where '$Header: WSHSTREF.fmb 120.113.12010000.32 I dont know why the contains different versions !The versions :/* $Header: WSHDDICS.pls 120.4.12010000.1 2008/07/29 05:59:31 appldev ship $ *//* $Header: WSHDDICB.pls 120.10.12010000.1 2008/07/29 05:59:30 appldev ship $ */FDRCSID('$Header: APPSTAND.fmb 120.11 2009/12/11 12:12 dbowles ship $');tFDRCSID('$Header: WSHSTREF.fmb 120.113.12010000.32 level:2 2010/02/23 08:08:27 pkm ship $');--FDRCSID('$Header: TEMPLATE.fmb 115.11 2000/05/25 17:20 dbowles ship $');FDRCSID('$Header: APPSTAND.fmb 120.11 2009/12/11 12:12 dbowles ship $');FDRCSID('$Header: WSHFSTRX.fmb 120.61.12010000.11 level:2 2010/02/24 06:05:28 pkm ship $');FDRCSID('$Header: APPSTAND.fmb 120.11 2009/12/11 12:12 dbowles ship $');Fdrcsid('$Header: $');FDRCSID('$Header: WSHQSSUI.fmb 120.20.12010000.6 level:2 2010/02/23 08:07:46 pkm ship $');Thanks---------------------------------------------------------------------------------------Hello,1) What was the value of initialization parameter "_disable_fast_validate" in the init.ora file when the upgrade / patch was done.2) Provide us the output of following query : select dep.d_obj#, d.owner# d_owner, d.name d_name, p.owner# p_owner, p.name p_name, case when p.status not in (1, 2, 4) then 'P Status: ' || to_char(p.status) else 'TS mismatch: ' || to_char(dep.p_timestamp, 'DD-MON-YY HH24:MI:SS') || to_char(p.stime, 'DD-MON-YY HH24:MI:SS') end reason from sys.obj$ d, sys.dependency$ dep, sys.obj$ p where d.obj# = dep.d_obj# and p.obj# = dep.p_obj# and d.status = 1 and bitand(dep.property, 1) = 1 and d.subname is null and not(p.type# = 32 and d.type# = 1) and not(p.type# = 29 and d.type# = 5) and not(p.type# in(5, 13) and d.type# in (2, 55)) and (p.status not in (1, 2, 4) or p.stime != dep.p_timestamp); .3.Please check for invalid shipping objects in the instance and provide with the list of invalid objects.4. perform the following steps.--------a. drop package apps.WSH_DELIVERY_DETAILS_INV;$WSH_TOP/patch/115/sql/@WSHDDICS.pls;$WSH_TOP/patch/115/sql/@WSHDDICB.pls;b. Recompile all WSH forms using adadmin.c. Once the above is completed, retest querying an order in the Shipping Transaction Form to see if the error messages are gone.Thanks----------------------------------------------------------------------Hi,The error messages gone after dropping the package and Recompiling .1) What was the value of initialization parameter "_disable_fast_validate" False2) No rows found3) No invalid objectsThanks--------------------------------------------------------------------Hi,The Apps Check output was retrieved from the DB with name 'ORA'.Confirm that the file you checked from the Operating System corresponds to that instance.1) What version do you see from the UI from Help>About applications?2) Run adadmin to compile forms and choose this form and let us know if you get any error.If no error is retrieved, list the form files as 'las -last WSHSTREF*' and provide the output.Thanks------------------------------------------------------------------Hi ,yes the file i checked from the Operating System corresponds to the same instance [ORA]1) What version do you see from the UI from Help>About applications?I don't know what is the form name and path in the application to get the version from the UI ..2) Run adadmin to compile forms and choose this form and let us know if you get any error.If no error is retrieved, list the form files as 'las -last WSHSTREF*' and provide the output.Compiled with no errors retrieved ..Please view uploaded file.----------------------------------------------------------------ODM Customer Feedback To get the from version through the application navigate to Oracle Shipping > Transactions > Select Help / About Oracle Applications. The form name and version will be displayed.Thanks, Steve Reid. -----------------------------------------------------------Hi ,I knew That , but in the shipping transaction form this is what i getForms----------------------------------------APPSTAND : 12.0.6.12010000.2FNDSCSGN : 12.0.15.12010000.6WSHFSTRX : 12.0.61.12010000.3there is no exist to WSHSTREFThanks