目前日期文章:200907 (11)

瀏覽方式: 標題列表 簡短摘要

System Administration


SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

Discoverer4i in Apps


SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

EBS Key Configuartion Files

image


SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

今天開始想要Study Web ADI..(已經有上Notes:287080.1 Patch環境下測試)

How to start..

1. 我給自己在測試環境加了 Desktop Integration Responsibility

2. User Guide 都告訴我們第一步要"Default Layout"... 於是我也照做了

image  

SomebabyTina 發表在 痞客邦 PIXNET 留言(4) 人氣()

參考朋友朋友的網站才知道原來Oracle ERP也有快速連結的方法,好方便喔~~

可是Security 是屬於Low Level的,提供大家參考。

http://<servername>:<port>/OA_HTML/fndvald.jsp?username=<username?password=<password>

<example>

http://demoapp.company.com:8000/OA_HTML/fndvald.jsp?username=kevintest?password=password123

SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

現況:Order Line的Pricing Date 是帶系統時間,並無依據Header 的資料帶出。

需求:Order Line的Pricing Date 要Default 從Order Header 帶下來..

問題描述:

想要使用Defaulting Rule 設定時發現 Related 選不到Order Header Object,故無法設定Reference 到Header的Pricing Date.

Responsibility: Order Management Super User

SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

image

Profile Option: Java Color Scheme

以下是不同的值帶出來Window顏色

  • Blaf

image

  • Blue

image

  • Khaki

image

  • Olive

image

  • Purple

image

SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

Concurrent Managers  REL 10.6 & 10.7

Items you Need to Know:When Tuning or Installing.

 

Contents

Introduction

Install Issues

Passwords

Demo Database

Fresh Install or Upgrade

USDSOP failed during spawn of INVLIBR process

Migration

Startup of Concurrent Manager Failed

Are the Concurrent Managers Down?

The Concurrent Managers are Down

10.7 NT Concurrent Managers

Errors when Starting the Managers on NT

Concurrent Manager Tables

FND_CONCURRENT_PROCESSES

FND_CONCURRENT_REQUESTS

FND_CONCURRENT_QUEUES

Introduction

Concurrent Managers are one of the most important and often the most feared process within Oracle's Applications. When a customer can not get a concurrent manager up and all of their production or testing is backing up, this is a very stressful time. This paper will try to remove some of the mystery and ease some of your fears. It will NOT go over every possible problem. It will also only cover the concepts for UNIX and not VMS or NT. There are other white papers that cover most of the known errors. This paper will also cover some of the basic tuning aspects of concurrent managers. It will NOT cover system-tuning parameters. Then finally, this paper will go over the three most important tables for the concurrent managers. We will cover some of the most common and our solutions for them.

Concurrent Managers

Internal Concurrent Manager

Concurrent Managers are composed of two different types of managers. One type is the Internal Concurrent Manager (ICM). The ICM controls all of the other concurrent managers. One of its' most important jobs in life is to ensure that the other concurrent managers are up and running. This is accomplished when the ICM wakes up and that is normally every 20 minutes. This will be discussed later in the paper. The ICM also performs the function of applying any incompatibility rules. Starting in 10.7, this can be done by the Conflict resolution Manager. This is where one program can not run with another. The other types of concurrent manager, are product concurrent managers (this is my phrasing).

The ICM logfiles will be located in either $FND_TOP/$APPLLOG or $APPLCSF/$APPLLOG ($APPLLOG is normally set to log). The file name is normally "std.mgr" but the name could also be "SID.mgr". When starting up the ICM, a parameter called "mgrname" can be used to rename the logfile.

APPLCSF is an optional parameter that can come in handy. The reasoning for APPLCSF, you have multiple APPL_TOPs and want to keep all of your logfiles and output files in the same place. Also, if APPLCSF is set all of the files (logfiles and output) for your products will be placed in this directory. This is convenient but never necessary. APPLCSF is set within the environment file on APPL_TOP.

Product Concurrent Managers

During the course of this paper specialized concurrent managers will consist of all concurrent managers with the exception of the ICM (e.g. Standard, Inventory, MRP, PA, and any user defined managers). These are the Concurrent Managers that run your jobs. They run concurrent requests, reports and processes. If the variable of $APPLCSF is NOT set the log and output files will be in each Product Top directory. All of the manager logs will be in either $FND_TOP/$APPLLOG or $APPLCSF/$APPLLOG ($APPLLOG is normally set to log).

Control of the Concurrent Managers

The ICM can be controlled from the operating system or within the applications.

This is the only manager that can be controlled from the operating system. When all of the concurrent managers have to be shutdown, shutting down the ICM is the way to do it. When the ICM is shutdown it will automatically shut down any running concurrent managers. Likewise, when the ICM is started it will restart any concurrent manager that were enabled (before shutdown) and the "target processes > 0" when the ICM was shutdown. Again this can be accomplished from either the o/s or within applications. If a product manager or the standard manager was deactivated prior to the ICM coming down, it will have to be restarted manually after the ICM comes back up.

In Char Mode (under SYSADMIN) go to: \Nav Con Man Admin

In GUI (under SYSADMIN) go to: Concurrent Manager Administrator

  • You need to query the concurrent manager record, by doing a "Query Run".
  • In the Control column either type 'Terminate' or 'Deactivate' or do a QuickPick and then save the screen.

From the command line the following will bring down the ICM:

10.6 and prior Releases

CONCSUB applsys/<password> SYSADMIN 'System Administrator' SYSADMIN CONCURRENT FND ABORT

For 10.7

CONCSUB apps/<password> SYSADMIN 'System Administrator' SYSADMIN CONCURRENT FND ABORT

The ICM can also be started for within the applications and from the command line. From the applications do the following:

In Char Mode (under SYSADMIN) go to: \Nav Con Man Admin

In GUI (under SYSADMIN) go to: Concurrent Manager Administrator

  • You need to query the concurrent manager record, by doing a "Query Run".
  • In the Control column either type 'Activate' or do a QuickPick and then save the screen.

From the command line the following will start the ICM. If you are experiencing problems, you can add "diag=y" to the end of the command line.

10.6 and prior Releases

startmgr sysmgr=applsys/<password> mgrname='SID'

For 10.7

SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

Concurrent Program Executable -> Execution Method = Host

ps .Host Language (i.e., shell or DCL)

Concurrent Manager screen or from the operating system, the script that starts the managers is “startmgr” located in $FND_TOP/bin.

image

 

SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

XML Publisher Report Issue:

目前為止已經開發了三四隻XML Report (Output Format = Excel).

這兩天竟然出現這個怪異的現象.. 這隻報表只要Run 3 以上就會出現Warning,

重點是之後跑XML Rerport 也都會Warning ,跑不出來了,

也就是說只有有隻XML Report Fail 就會擋到後面XML Report的路,大家都不能走了!!!

SomebabyTina 發表在 痞客邦 PIXNET 留言(1) 人氣()

Metalink Doc ID:743490.1

In this Document
Purpose
Scope and Application
Customization in Oracle Applications

SomebabyTina 發表在 痞客邦 PIXNET 留言(0) 人氣()

找更多相關文章與討論