AMX DAS-AMP4 Guia de Configuração descarregar pdf (Página 258)

14-28 Oracle Application Management Pack for Oracle E-Business Suite Guide

product created in Oracle E-Business Suite (not in Customization Manager).

• Source Path - The source directory for the file on the source control system or

file system. This would be substituted in the "%file_path%" parameter in the

checkout command.

• File Name - The name of the file. This would be substituted in the

"%file_name%" parameter in the checkout command.

• Version - Optional. The version of the file. The version is only needed if the

checkout command will use the version information. This would be substituted

in the "%version%" parameter in the checkout command.

• Type - The type of the file. Ensure that correct type is selected for the file entry.

type. The Oracle Applications DBA (AD) patch driver instructions are based on

the type selected.

• Destination Path - The destination path for the file in the Oracle E-Business

Suite instance excluding the language subdirectory. This must be an

AD-compliant destination path according to Oracle E-Business Suite standards.

The destination path in the patch driver is automatically suffixed with the

language code chosen with exception to "Generic". The destination path for a

file entry is defaulted to the source path, which may be modified if necessary.

• Language - Optional. The language code for the file. Select the language code as

needed to generate the respective NLS patch.

3. Enter in additional information for the package.

• Enter the E-Business Suite mapping information (Conditionally required). The

E-Business Suite mapping information is only required when the package

contains at least one Java or PLD file. You may select the E-Business Suite

Mapping from the list provided.

• Enter the Package Metadata. You can enter the instructions for package

application here. These instructions will become part of the package readme.

• Enter Comments. These comments will be recorded as part of the package

history for tracking changes made to the package. As a best practice, it is

recommended to add comments describing the changes done to the package

and other details. Any comments added are tracked with the package history

information.

• Enter Prerequisite Information.

For Release 11i packages, you can enter one or more prerequisite patch

numbers that can be used for deployment validation with AD utilities.

1 2 ... 253 254 255 256 257 258 259 260 261 262 263 ... 337 338

Sem comentários

AMX DAS-AMP4 Guia de Configuração Página 258