The suffix following a filename that identifies the file type, for example, .cbl and .sql | |
The file type format. Options include ASCII, EBCDIC, and Image. | |
For Unix-style file types, the file permission mask in octal for files of this type. NOTE: Selecting Unix File Permission in the File Server tab overrides any value you specify in this field. | |
(Oracle Applications only) For schema object, file object, and setup object types. Indicates the order in which objects of this type are migrated relative to other file object, schema object, and setup (AOL) object types in an archive set. The values specified here override the default values displayed in the Default Order field. Object types assigned a lower number are migrated before object types assigned higher numbers. | |
(Oracle Applications only) For schema object, file object, and setup object types. | |
(Oracle Applications only) For custom and generic file object types. | |
Stat supports different types of file objects for Oracle Applications. These include:
• |
Generic file types are user-defined file types that exist outside the Oracle Applications file structure but which can still be archived and migrated. |
• |
Custom file types are user-defined file types that exist within or outside of the Oracle Applications file system. There are three types of Custom file types: |
• |
Custom with Prod file types that exist within the Oracle Applications file system and are associated with Products. |
• |
1 |
In the Custom Type field, do one of the following: |
• |
Select Custom with Prod to create a custom file type that is associated with a product. |
• |
Select Custom with Prod/Lang to create a custom file type that is associated with a product and language. |
• |
Select Custom to create a custom file type that is outside the Oracle Applications file structure. |
NOTE: After you have defined a custom file type, you need to specify where files of this type are located. See the section Source File Locations for more information. Be aware that the value in the Custom Type field cannot be modified after source file locations have been set or after an object of that custom file type has been added to a CSR (e.g., a Custom with Prod file type cannot be changed to a Custom with Prod/Lang file type). |
3 |
NOTE: As an example note how TARGET_OBJECT_NAME_FULL_PATH_NE parameter could be used to create a soft link to a file name being migrated: ln -s %%FND_TOP%%/bin/fndcpesr %%TARGET_OBJECT_NAME_FULL_PATH_NE%% |
4 |
The following example illustrates how to create generic file types:
After you have defined a file type, you need to specify where files of this type are located by selecting the file type and clicking File Location. This opens the File Locations window. Here you specify per environment the server and pathway where files of the selected type are stored. In this window you can also specify a different working directory for each user.
1 |
Click New. Stat activates a new row in the Source File Locations tab. |
2 |
In the Environment field, select the environment in which you want to define a source file location. |
• |
• |
• |
• |
• |
5 |
(Optional) Select Default Path if you want this to be the file type’s default source file location. |
6 |
Click Test Connection. |
7 |
When defining file type user directories, keep in mind the following considerations:
• |
• |
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center