Oracle eBS Knowledge Hub

Conditionally mandatory parameters of concurrent program Overview of  Conditionally mandatory parameters: Oracle Application does not support conditionally mandatory parameters . But sometime business requires conditionally mandatory parameters. So we need to achieve the same functionality using some workaround so that the program will be submitted with proper parameters. Requirement of  Conditionally mandatory parameters : We have customized report wherein there is a mandatory parameter 'Print of New' can have either of two values 1) Yes, 2) No at the time of submission of concurrent program.                          If user has selected 'Yes' as a parameter and has not entered any value in the parameter Transaction number low or Transaction number High then parameters for the printing original date Low and printing original date High should be made mandatory. In all other case parameters printing original date Low and printing original date

FNDLOAD utility for Oracle Apps FNDLOAD is a great Oracle utility to migrate data from one instance to another. It can be used with several different entities/data types within Oracle e-Business Suite. Some of the examples in this FNDLOAD article include:- FNDLOAD to transfer Request Groups FNDLOAD for moving Concurrent Programs FNDLOAD to download and upload Forms Personalization FNDLOAD for Data Definition FNDLOAD can be used to migrate Key FlexFields , Descriptive Flexfield s, Responsibilitie s and almost every other FND entity. Usage of FNDLOAD utility: FNDLOAD Request groups: Download: FNDLOAD apps/$apps_PWD O Y DOWNLOAD FND_TOP/patch/115/import/afcpreqg.lct XX_REQ_GRP.ldt REQUEST_GROUP REQUEST_GROUP_NAME="XX_REPORT_GROUP_SRT_NAME" APPLICATION_SHORT_NAME="XXGMS" Upload: FNDLOAD apps/$apps_PWD O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct FNDLOAD Concurrent Programs: Download: FNDLOAD apps/$apps_PWD O Y DOWNLOAD $FND_TOP/patch

Requirement of Timecard Layout Modification: Let's assume that following SFDC /Partner Name field needs to be modified to increase the length of the field  in Timecard Layout: I am going to tell you how we can increase the length of the field in Oracle Timecard layout. But the field cannot modified using Personalization from the standard Oracle Applications Framework (OAF) functionality. All the changes to the layout must be made via the Oracle Time and Labor page layout definition. We need to modify the Timecard Layout configuration file for this requirement. Solution to Timecard Layout Modification: In order to increase the length of the field in the Timecard Layout , we need to get the layout name and ldt file for the Timecard layout . T o get the current layout name follow the below steps: Global OTL Administrator --> Preference Press Timecard Layout --> Preference Values, following window will open: Timecard Layout: Projects Timecard La

Issues of Oracle Database Connection to TOAD Connections to Oracle database via TNS are bit of a painful until you get all the components in the TNS configured correctly. We generally get different types of errors when we try to connect the DB using TOAD.  Usually we get Host, Port & Service Name in the TNS Entry but SID is excluded from it. But if we supply the SID information instead of service name it gets connected easily. If we get the SID for the database we can easily connect to the DB using TOAD. Solution of Oracle Database Connection by TOAD: We can connect to any database instance using TOAD by the following steps: 1.        Connect to the database using SQL*Plus as below Ø   User Name:  ORACLE_USER Ø   Password: ORACLE_password1 Ø   Host String: 156.14.200.90:1542/VISSVC(host:port/Service Name) Ø   Or conn  ORACLE_USER / ORACLE_password1@156.14.200.90:1542/ORAVISSVC (Conn user/password@host:portNumber/ServiceName) 2.        Execute the following

OPP Log file: To obtain the OPP log file, follow the bellow steps: §   Select the System Administrator responsibility. §   Navigate to Concurrent à Manager à Administer. §   Select the Output Post Processor Service. §   Select the Processes button. §   Select Manager Log. Issues: BI Publisher concurrent request completed with warning due to a timeout caused by the Output Post Processor (OPP).  Given bellow the possible common errors may occur due to OPP issue: Issue 1. OPP No Response : +------------- 1) PUBLISH -------------+ The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status. Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary. +--------------------------------------+ Issue 2.   OPP Process Timeout : +------------- 1) PUBLISH -------------+ The concurrent ma