One of the integration architects is attempting to standardize the path locations for inbound and
outbound feeds for the applications.
Currently they are providing the full path name of the file on the file system when they submit the
request to load the feeds. They would like to soft code the path of the file name by server to
shorten the parameter entry and retime key errors when submitting the interfaces.
Currently all of the feeds, both inbound and outbound, are being kept in a single directory. They
would like to separate the files into directories by application, and have a separate inbound
outbound feed directory.
This is a global implementation with middle-tier services strategically placed around the world.
North American services are all from the data center in New York. The European services are
being provided from the European data center in England, and the Asia-Pacific services are
hosted in a data center in India.
The architect’s plan is to create two profile options: one for inbound path and one for outbound
path. All the utl_file directories used by the integration programs would be standardized for use.
His plan is to set them at the application and server level to soft code the directory path for all of
the integration points.
He would also like to provide users with the ability to change the path for their user, or for a
development-centric responsibility only to support individual testing efforts on non-production
servers.
He would also prefer to prevent anyone from setting the value of the profile option at the operating
unit level. Indentify the flaw in the architect’s proposed solution.
A.
Interfaces do not run under a specific responsibility.
B.
Profile options cannot be controlled by the operating unit.
C.
A profile option can only be assigned to one hierarchy type.
D.
The value of the profile option cannot be controlled by the server.
E.
The interfaceswould not be able to read the value of the profile option at the server level
Explanation:
Note:
A profile option can be set at one or more levels, depending on its hierarchy type. Most profile
options use the Security hierarchy type, meaning that they can potentially be set at the four levels:
Site (lowest level) , Application, Responsibility, and User (highest level).
Hierarchy types enable system administrators to group and set profile options according to their
business needs or the needs of the installation.There are several hierarchy types: Security, Organization, Server, and Server+Responsibility.
Reference: Oracle E-Business Suite System Administrator’s Guide – Maintenance:
Reference: User Profiles