Please visit my new domain at http://ediyanto.co.cc

C U there…

Update (as of 08-Nov-2009):

- Oracle Top-N Query
- Bersyukurlah…
- Cinta Sejati
- Nice Story
- 5 Tips Agar Tak Mudah Lelah
- Belajar dari Alphabet
- How To Get the List of All Responsibilities Assigned To A User
- Query To Find Multi-Org Is Enabled Or Not
- How To Find A Patch Is Applied For A Bug
- Excel Limitations on Images
- BLOB Images in XML Publisher
- Today Is Beautiful Day And I Cannot See It
- Scheduled Ship Date Time Always Reset To 23:59:00 in Oracle Apps R11i
- Tandingan Antar Berkumis
- Hati yang Luka
- Mr. Pig
- Changing LOV using Forms Personalization on Oracle Apps R12
- Starting VMware Server Hangs/Crashes on Windows Vista
- Where Context XML File in Oracle Apps R12?
- Kekuatan Pikiran

The below steps for activate special menu on Receipts form and invoice custom form “Receipt DT” when clicked on the special menu on Oracle Application (E-Business Suite)

1. Open the Receipts Form on Receivables Manager Responsibility
2. Open the Personalization form using the navigation “Help > Diagnostics > Custom Code > Personalize”
3. Enter the sequence number as 10 and description “Activate Special Menu”
4. Select the Trigger Event as “WHEN-NEW-FORM-INSTANCE” and save the changes
5. On Actions tab, enter or select the following values
   • Sequence = 10
   • Type = Menu
   • Description = Receipt DT Informations
   • Language = All
   • Enabled = Yes
6. On the right side of Actions tab, enter or select the following values
   • Menu Entry = SPECIAL10
   • Menu Label = Receipt DT
   • Render line before menu = Yes
7. Click on the “Validate” button, then click on “Apply Now” button
8. Close both the forms and reopen the Receipts form
   Result:Check the Tools menu after opening the Receipts form, there should be an additional menu showing the given prompt.
9. Open the personalization form and it should automatically query the existing rule to activate the special menu
10. Enter the sequence number as 20 and description “Invoke Receipt DT Custom Form on Special Menu”
11. Select the Trigger Event as “SPECIAL7” and save the changes
12. On Actions tab, enter or select the following values
    • Sequence = 10
    • Type = Builtin
    • Description = Call Receipt DT form
    • Language = All
    • Enabled = Yes
13. On the right side of Actions tab, enter or select the following values
    • Builtin Type = Launch a Function
    • Function Code = MPICOLLRECEIPT
    Note: Define MPICOLLRECEIPT as form function, associate with a custom form and add the MPICOLLRECEIPT function to the menu of “Receivables Manager” responsibility.
14. Validate, Apply and Save the changes
15. Close both the forms and reopen the Receipts form
    Result: When clicked on the Tools > Receipt DT, it should invoke the custom form attached to the MPICOLLRECEIPT function
    

Three possible errors can occur as below:

• The Output Post Processor is not running or does not pick up the request

…
+————- 1) PUBLISH ————-+
Unable to find an Output Post Processor service to post-process request [request_id].

Check that the Output Post Processor service is running.
+————————————–+
…

Solutions:
* Verify that the Output Post Processor is enabled and active.
* If confirmed, retrieve the OPP log file either via the Forms application or via the Oracle Application Manager.
- Via the Forms application:

1. Login to the application as SYSADMIN
2. Responsibility: System Administrator
3. Function: Concurrent –> Manager –> Administration
4. Select the Output Post Processor
5. Click on the Processes button
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Manager Log button to open the Output Post Processor log file

- Via the Oracle Application Manager

1. Login to the application as SYSADMIN
2. Responsibility: System Administration
3. Function: Oracle Applications Manager –> Concurrent Managers
4. Select the Output Post Processor Service and click on View Details
5. Click on View Processes
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Log button to open the Output Post Processor log file

• The Output Post Processor is running but has not picked up the request

...
+------------- 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.
+--------------------------------------+
...

By default a timeout will occur if it takes longer then 120 seconds (2 min.) for the Output Post Processor to pick up the request from the Concurrent Manager process. In that case, the Concurrent Request will complete with status Warning and the Request log file will contain error message like above.

Solutions:
* Increase the value (in seconds) for the profile option ‘Concurrent:OPP Response Timeout‘.

• The concurrent manager has timed out waiting for the Output Post-processor to finish this request

…
+————- 1) PUBLISH ————-+
The concurrent manager has timed out waiting for the Output Post-processor
to finish this request.

Check that there are enough Output Post-processor service processes running.
More information may be found in the service process logfile.
+————————————–+
…

The concurrent manager process has successfully invoked the OPP but it a timeout is encountered as the OPP takes too long to complete the job.

The time that this takes will depends on various elements such as:

• size of the XML Data File
• complexity of the template
• performance of the server
• ….

By default a timeout will occur if it takes longer then 300 seconds (5 min.) for the XML Publisher engine to generate the output file. The Concurrent Request will complete with status Warning and the Request log file will contain error message like above.

Solutions:
* Increase the value (in seconds) for the profile option ‘Concurrent:OPP Process Timeout‘.

When you submit the XML Report Publisher Program (XDOREPPB) you are prompted to select the Request ID for the data generation program. The LoV for this parameter is not being populated due to an incorrect profile option reference.

To work around this issue, you must change the references to the incorrect profile option in the XDO_REPORT_REQUEST_ID value set as follows:

1. Using the System Administrator responsibility, open the Value Set form. Navigation: Application > Validation > Set.
2. Query value set name XDO_REPORT_REQUEST_ID.
3. Click Edit Information.
4. Modify Where/Order By as follows:
   

Current:

WHERE ( ( FND_PROFILE.VALUE(‘CONC_REPORT_ACCESS_LEVEL’) = ‘U’
AND R.REQUESTED_BY = :$PROFILES$.USER_ID ) or
( FND_PROFILE.VALUE(‘CONC_REPORT_ACCESS_LEVEL’) = ‘R’
AND R.RESPONSIBILITY_ID = :$PROFILES$.RESP_ID ) )
AND R.PROGRAM_APPLICATION_ID = CP.APPLICATION_ID
AND R.CONCURRENT_PROGRAM_ID = CP.CONCURRENT_PROGRAM_ID
AND XDS.APPLICATION_SHORT_NAME=
( SELECT APPLICATION_SHORT_NAME
FROM FND_APPLICATION
WHERE APPLICATION_ID=CP.APPLICATION_ID)
AND XDS.DATA_SOURCE_CODE = CP.CONCURRENT_PROGRAM_NAME
AND R.OUTPUT_FILE_TYPE=’XML’
AND R.STATUS_CODE not in (‘E’, ‘D’, ‘T’, ‘X’)
ORDER BY R.REQUEST_ID DESC

Modified to:

WHERE (R.REQUESTED_BY = :$PROFILES$.USER_ID or
R.RESPONSIBILITY_ID = :$PROFILES$.RESP_ID )
AND R.PROGRAM_APPLICATION_ID = CP.APPLICATION_ID
AND R.CONCURRENT_PROGRAM_ID = CP.CONCURRENT_PROGRAM_ID
AND XDS.APPLICATION_SHORT_NAME=
( SELECT APPLICATION_SHORT_NAME
FROM FND_APPLICATION
WHERE APPLICATION_ID=CP.APPLICATION_ID)
AND XDS.DATA_SOURCE_CODE = CP.CONCURRENT_PROGRAM_NAME
AND R.OUTPUT_FILE_TYPE=’XML’
AND R.STATUS_CODE not in (‘E’, ‘D’, ‘T’, ‘X’)
ORDER BY R.REQUEST_ID DESC

Reference Note:404928.1

You can get the XML file from the XML/BI Publisher report based on concurrent request with the below steps:

1. *) View->Requests
2. *) Find the request you’re interested in
3. *) Click on Diagnostics button
4. *) Click the View XML
5. *) Save the file to your PC by doing File->Save As, *.xml

Or you can get it from this location $APPLCSF/$APPLOUT/o{REQUEST_ID}.out

After entering the address details in Create Customer Form, get error when saving:
“APP-AR-96282:Error The following SQL error occured
ORA-00001 : unique constraint (AR.HZ_CUST_ACCT_SITES_U2) violated”

Cause

The current value of sequence hz_cust_acct_sites_s is smaller than the existing data in hz_cust_acct_sites_all.orig_system_reference.

select hz_cust_acct_sites_s.currval from dual;
returns
3188

SQL> select column_name from dba_ind_columns where index_name=’HZ_CUST_ACCT_SITES_U2′;
COLUMN_NAME
ORIG_SYSTEM_REFERENCE
ORG_ID

But client has records in hz_cust_acct_sites_all table with value greater than 901000 for orig_system_reference column.

Solution

1. DROP sequence ar.hz_cust_acct_sites_s;
2. CREATE SEQUENCE AR.HZ_CUST_ACCT_SITES_S
START WITH 10001
MAXVALUE 900999
MINVALUE 10001
NOCYCLE
NOCACHE;
Note: the start value, minimum/maximum value depends on your needs and  the sequence must be set higher than the largest value stored in HZ_CUST_ACCT_SITES_All.orig_system_reference.

Reference: Doc ID 388728.1

When attempting to apply Patch 6502082 – 11i.AD.I.6, the following error occurs

AutoPatch error:
Error while executing statement

AutoPatch error:
ORA-06550: line 3, column 10:
PLS-00302: component ‘IS_PATCH_APPLIED2′ must be declared
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored

The issue is caused by the following setup:

Following package versions for package APPS.AD_PATCH are not created.
$AD_TOP/patch/115/sql adphpchb.pls   115.16
$AD_TOP/patch/115/sql adphpchs.pls   115.11

To implement the solution, please execute the following steps:
1. Go to $AD_TOP/patch/115/sql
2. Check the version of adphpchs.pls and adphpchb.pls
adident Header $AD_TOP/patch/115/sql/adphpch*.pls
It should be -
$AD_TOP/patch/115/sql/adphpchs.pls (version 115.11)
$AD_TOP/patch/115/sql/adphpchb.pls (version 115.16)

3. If it is not there, run them from <patch-top-directory>/ad/patch/115/sql
4. Once the proper versions are available, run them from sqlplus as APPS user
SQL> @adphpchs.pls
SQL> @adphpchb.pls

5. Check the version and status once again
SQL> select status, object_type, owner from dba_objects where object_name = ‘AD_PATCH’;
SQL> select text from dba_source where line = 2 and name = ‘AD_PATCH’;

6. Retest adpatch from beginning
7. Migrate the solution to appropriate environment

Reference: Doc ID 556785.1

BI Publisher provides the FNDLOAD and XDOLoader utilities to move component across eBusiness Suite instances.

The FNDLOAD utility is used to upload and download the concurrent program, data definition and data template created via created via System Administrator and XML Publisher Administrator responsibility.

The XDOLoader utility is used to upload and download the physical files (Template files, XSD Schema, Sample XML Data , Bursting Control File)

FNDLOAD : Download Concurrent Programs

*) Download all the concurrent programs in a specific product.

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME=MPI

*) Download concurrent program for a specified concurrent program name.

FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME=MPI CONCURRENT_PROGRAM_NAME=MPISHIPPED

FNDLOAD : Upload Concurrent Programs

*) Upload the concurrent programs to an instance.

FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt – CUSTOM_MODE=FORCE

FNDLOAD : Download Data Definition and Data Template

*) Download all the data definitions and the corresponding Templates in a specific product.

FNDLOAD apps/apps 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct file_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=MPI

*) Download a particular data definitions and its corresponding Templates.

FNDLOAD apps/apps 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct file_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=MPI DATA_SOURCE_CODE=MPISHIPPED

FNDLOAD : Upload Data Definition and Data Template

*) Upload the data definitions and its corresponding Templates to an instance.

FNDLOAD apps/apps 0 Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct file_name.ldt

XDOLoader : Download Physical Files

*) Download all the physical files for a specified application short name

java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION oradev:1522:DEV \
-APPS_SHORT_NAME MPI \
-LANGUAGE id \
-TERRITORY ID

*) Download a particular physical file for a specified XDO LOB code

java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION oradev:1522:DEV \
-APPS_SHORT_NAME MPI \
-LOB_TYPE TEMPLATE_SOURCE \
-LOB_CODE MPISHIPPEDT \
-LANGUAGE id \
-TERRITORY ID

XDOLoader : Upload Physical Files

*) Upload the RTF file

java oracle.apps.xdo.oa.util.XDOLoader \
UPLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION oradb:1521:PROD \
-LOB_TYPE TEMPLATE \
-APPS_SHORT_NAME MPI \
-LOB_CODE MPISHIPPEDT \
-LANGUAGE id \
-TERRITORY ID \
-XDO_FILE_TYPE RTF \
-FILE_CONTENT_TYPE ‘application/rtf’ \
-FILE_NAME /oracle/dev/appldev/devappl/MPI_MPISHIPPEDT.rtf \
-CUSTOM_MODE FORCE

-CUSTOM_MODE FORCE = FORCE the update if a data/lob already exists

Posted in Oracle Tagged: development, ebiz, XML/BI Publisher ]]> http://ediyanto83.wordpress.com/2009/01/02/moving-concurrent-programs-data-definitions-and-templates-between-ebusiness-suite-instances/feed/ 0 Edi