oracle apps scm interview questions

Oracle SCM Interview Questions
  • How Do You Calculate the Total Annual Cost?
  • What Are Different Planning Methods in Inventory.
  • What Are the Setups for Expense Items?
  • What Is the Use of Sales Order Kff?
  • What Is the Process of Cycle Count?
  • What Is the Picking Rule in Inventory.
  • What Does the Account Generator Process Do?

What all setups have you done in Inventory Organisation Implementation?

I’ve worked on setting up:

  • Location
  • Organisation
  • Calendar
  • Intercompany Transaction flows
  • Cost Group
  • Parameter
  • Stock Locator
  • Sub inventory
  • Shipping Networks
  • Receiving Options
  • Cost Sub elements
  • What are the different setups for expense items?

    The various setups are:

  • Should not be Inventory Item
  • No Transactable
  • No Stackable
  • No Costing Inventory Asset
  • Oracle Access Manager Interview Questions

    Q.What Is Single Sign On? Ans: Single Sign-On allows users to sign on once to a protected application and gain access to the other protected resources within the same domain defined with same authentication level. Q.What Is Multi Domain Single Sign-on? Ans: Multi Domain SSO gives users the ability to access more than one protected resource (URL and Applications), which are scattered across multiple domains with one time authentication. Q.What Is The Authentication Mechanism Used By Oracle Access Manager? Ans : ObSSOCookie and it is stateless. Q.Explain Various Security Modes Present In Oracle Access Manager? Ans: Open: Allows unencrypted communication. In Open mode, there is no authentication or encryption between the AccessGate and Access Server. The AccessGate does not ask for proof of the Access Server’s identity and the Access Server accepts connections from all AccessGates. Similarly, Identity Server does not require proof of identity from WebPass. Simple: Supports encryption by Oracle. In Simple mode communications between Web clients (WebPass and Identity Server, Policy Manager and WebPass, and Access Server and WebGate are encrypted using TLS v1. In both Simple and Cert mode, Oracle Access Manager components use X.509 digital certificates only. This includes Cert Authentication between WebGates and the Access Server where the standard cert-decode plug-in decodes the certificate and passes certificate information to the standard credential_mapping authentication plug-in. For each public key there exists a corresponding private key that Oracle Access Manager stores in the aaa_key.pem file for the Access Server (or ois_key.pem for Identity Server). Cert: Requires a third-party certificate. Use Cert (SSL) mode if you have an internal Certificate Authority (CA) for processing server certificates. In Cert mode, communication between WebGate and Access Server, and Identity Server and WebPass are encrypted using Transport Layer Security, RFC 2246 (TLS v1). Q.Explain The Architecture Of Oracle Access Manager? Ans: Oracle Access Manager architecture mainly consists for components such as Identity Server, WebPass, Policy Manager, Access Server and a WebGate. Identity Server is a standalone C++ server which communicates directly with LDAP. It also receives requests and sends response to Webpass. WebPass is a web server plugin that passes info between identity server and webserver. It redirects HTTP requests from browser to Access Server, and sends Identity XML SOAP requests to Identity Server. Policy Manager (PMP or PAP) is a web server plugin that communicates directly with user, configuration and policy repositories. Access Server is a stand alone C++ server and is also called PDP. It receives requests from & sends responses to WebGates/AccessGates. It also communicates with LDAP. It answers Access Server SDK requests. WebGate (PEP) is a web server plugin that passes info between webserver and access server. It passes user authentication data to access server for processing. Q.What Are The Obssocookie Contents? Ans: Cookie contains encrypted session token and non-encrypted data. This Encrypted Session Token consists of : DN of the authenticated user, level of auth scheme, ip address of client to which cookie was issued, time the cookie is issued, time the cookie was last updated. If the user is not idle, then cookie will get automatically updated at a fixed interval to prevent session timeout. The updated interval is the 1/4 th of idle session timeout of accessgate. The Unencrypted ObSSOCookie data contains cookie expiry time, domain in which cookie is valid, additional flag that determines if cookie can only be sent using SSL. Q.What Is The Key Used For Encrypting The Obssocookie? Ans: Shared Secret key. It is configured in the Identity Admin console and can be generated by the OAM administrator. Q.What Happens If The Obssocookie Is Tampered? Ans : When access system generates ObSSOCookie, MD-5 hash is taken from session token. So when the user is authenticated again using the cookie, the MD5 hash is compared with original cookie contents. MD-5 hash is a one-way hash, hence it cant be unencrypted. Access server compares the cookie contents with hash. If both are not same, then cookie is tampered in the interim. This cookie does not contain username and password. Q.What Is The Difference Between Webgate And Accessgate? Ans: WebGate is an out-of-the-box plug-in that intercepts Web resource (HTTP) requests and forwards them to the Access Server for authentication and authorization. An AccessGate is a custom webgate that can intercept requests of HTTP and non-HTTP resources. Q.What Are The Major Parameters Defined In An Authentication Scheme? Ans: The authentication scheme level which defines the level of the security defined for an application. Q.Explain The Flow When A User Requests For An Application Protected By Oracle Access Manager? Ans: The following steps describes the flow when a user makes a request to access a resource protected by the Oracle Access Manager: User requests for a resource through a web browser. The Webgate intercepts the requests and checks with the Access Server whether the resource is protected or not. If the resource is not protected, then the user will be shown the requested resource. If the resource is protected, then Access Server will check with policy manager the authentication scheme configured for that resource. User will be prompted to enter their credentials as per the auth scheme defined for the resource. Webgate will send the credentials to the Access Server to check it against the backend (LDAP server). Upon successful authentication, Access server checks whether the user is authorized to access the resource or not. If the user is authorized, then the Access Server will create the session id and passes it to the webgate. An ObSSOCookie is created and will be sent to the user browser and the user will be shown the requested resource. If the user is not authorized, then an error page (if its defined in policy domain) will be shown to the user. Q.Explain The Flow Of A Multi Domain Single Sign-on? Ans: Multi Domain SSO gives users the ability to access more than one protected resource (URL and Applications), which are scattered across multiple domains with one time authentication. For multi domain SSO to work, Access Servers in all domains must use same policy directory. Multi domain works only with web gates, not Access Gates. Within each individual domain, each web gate must have same “primary HTTP cookie domain”. In Multi Domain SSO environment, we should designate one web server (where web gate is installed) as “Primary Authentication Server”. Primary Authentication Server acts as a central server for all authentications in multi domain environment. In general the webgate installed in the domain where Access server resides will be designated as the primary authentication server. Lets assume that OAM components are installed in and we will designate as the primary authentication server. with web gate (ex: webgate2) installed. A resource, abc.html, is protected with Form base authentication on A resource, xyz.html, is protected with Basic over LDAP authentication on Following are the steps that explain how multi domain SSO works: User initiates a request for a Web page from a browser. For instance, the request could be for host2.mydomain2/xyz.html. Webgate2 (on sends the authentication request back through the user’s browser in search of primary authentication server. In this example you have designated to be the primary authentication server. The request for authentication is sent from the user’s browser to the primary authentication server, This request flows to the Access Server. The user logs in with the corresponding authentication scheme and the obSSO cookie is set for The Access Server also generates a session token with a URL that contains the obSSO Cookie. The session token and obSSOCookie are returned to the user’s browser. The session token and obSSOCookie are sent to The Web gate (webgate2) on sets the obSSOCookie for its own domain ( and satisfies the user’s original request for the resource User gets the resource. On the same browser if user accesses the page then resource will be presented without asking credentials as obSSOCookie is already available with (see step 3). Q.What Is An Access Server Sdk? Ans: The Access Manager Software Developer’s Kit (SDK) enables you to enhance the access management capabilities of the Access System. This SDK enables you to create a specialized AccessGate. The Access Manager SDK creates an environment for you to build a dynamic link library or a shared object to perform as an AccessGate. You also need the configureAccessGate.exe tool to verify that your client works correctly. Q.What Is An Identity Xml? Ans: IdentityXML provides a programmatic interface for carrying out the actions that a user can perform when accessing a COREid application from a browser. For instance, a program can send an IdentityXML request to find members of a group defined in the Group Manager application, or to add a user to the User Manager. IdentityXML enables you to process simple actions and multi-step workflows to change user, group, and organization object profiles. After creating the IdentityXML request, you construct a SOAP wrapper to send the IdentityXML request to WebPass using HTTP. The IdentityXML API uses XML over SOAP. We pass IdentityXML parameters to the COREid Server using an HTTP request.This HTTP request contains a SOAP envelope.When WebPass receives the HTTP request, the SOAP envelope indicates that it is an IdentityXML request rather than the usual browser request. The request is forwarded to the COREid Server, where the request is carried out and a response is returned. Alternatively, you can use WSDL to construct the SOAP request. The SOAP content looks like this, SOAP envelope (with oblix namespace defined), SOAP body (with authentication details), actual request (with application name and params). The application name can be userservcenter, groupservcenter or objservcenter (for organizations). Q.What Is An Sspi Connector And Its Role In Oracle Access Manager Integrations? Ans: The Security Provider for WebLogic SSPI (Security Provider) ensures that only appropriate users and groups can access Oracle Access Manager-protected WebLogic resources to perform specific operations. The Security Provider also enables you to configure single sign-on between Oracle Access Manager and WebLogic resources. The WebLogic security framework provides Security Service Provider Interfaces (SSPIs) to protect J2EE applications. The Security Provider takes advantage of these SSPIs, enabling you to use Oracle Access Manager to protect WebLogic resources via: User authentication User authorization Role mapping The Security Provider consists of several individual providers, each of which enables a specific Oracle Access Manager function for WebLogic users: Authenticator: This security provider uses Oracle Access Manager authentication services to authenticate users who access WebLogic applications. Users are authenticated based on their credentials, such as user name and password. The security provider also offers user and group management functions. It enables the creation and deletion of users and groups from the BEA WebLogic Server. It also provides single sign-on between WebGates and portals. Identity Asserter: Like the Authenticator, this security provider uses Oracle Access Manager authentication services to validate already-authenticated Oracle Access Manager users using the ObSSOCookie and to create a WebLogic-authenticated session. Authorizer: This security provider uses Oracle Access Manager authorization services to authorize users who are accessing a protected resource. The authorization is based on Oracle Access Manager policies. Role Mapper: This security provider returns security roles for a user. These roles are defined in Oracle Access Manager, and they are provided by Oracle Access Mana ger using return actions on a special authentication policy. This authentication policy contains a resource with a URL prefix of /Authen/Roles. Role Mapper maps these roles to predefined security roles in WebLogic. Q.Explain The Integration And Architecture Of Oam-oaam Integration? Ans: Using these products in combination will allow you fine control over the authentication process and full capabilities of pre-/post- authentication checking against Adaptive Risk Manager models. The OAAM’s ASA-OAM integration involves two Oracle Access Manager AccessGates: one for fronting the Web server (a traditional WebGate) to Adaptive Strong Authenticator and one for the embedded AccessGate. The access server SDK to be installed and configureAccessGate tool to be run. The ASA bharosa files to updated with ASDK location. An application to be protected using ASA authentication scheme and to be tested for ASA landing page for login. Here is how the flow goes: User requests for a resource. Webgate acting in the front end for ASA application will intercept the request and will redirect to the ASA application. The user enter credentials and the Access SDK setup in the ASA application will contact the Access gate which inturn contacts the access server for validating the credentials. Upon successful authentication, access server will generate obSSOCookie and will forwards it to the browser. Then the user will be shown the requested resource. Q.Explain Iwa Mechanism In Oracle Access Manager? Ans: The OAM has a feature which enables Microsoft Internet Explorer users to automatically authenticate to their Web applications using their desktop credentials. This is known as Windows Native Authentication. user logs in to the desktop machine, and local authentication is completed using the Windows Domain Administrator authentication scheme. The user opens an Internet Explorer (IE) browser and requests an Access System-protected Web resource. The browser notes the local authentication and sends a token to the IIS Web server. The IIS Web server uses the token to authenticate the user and set up the REMOTE_USER HTTP header variable that specifies the user name supplied by the client and authenticated by the server. The WebGate installed on the IIS Web server uses the hidden feature of external authentication to get the REMOTE_USER header variable value and map it to a DN for the ObSSOCookie generation and authorization. The WebGate creates an ObSSOCookie and sends it back to the browser. The Access System authorization and other processes proceed as usual. The maximum session timeout period configured for the WebGate is applicable to the generated ObSSOCookie. Q.Explain Various Major Params Defined In Webgate Instance Profile? Ans: Hostname: name of the machine hosting the access gate. Maximum User Session Time: Maximum amount of time in seconds that a user’s authentication session is valid, regardless of their activity. At the expiration of this session time, the user is re-challenged for authentication. This is a forced logout. Default = 3600. A value of 0 disables this timeout setting. Idle Session Time (seconds): Amount of time in seconds that a user’s authentication session remains valid without accessing any AccessGate protected resources. Maximum Connections: Maximum number of connections this AccessGate can establish. This parameter is based on how many Access Server connections are defined to each individual Access Server. This number may be greater than the number allocated at any given time. IPValidationException: IPValidationException is specific to WebGates. This is a list of IP addresses that are excluded from IP address validation. It is often used for excluding IP addresses that are set by proxies. Maximum Client Session Time :Connection maintained to the Access Server by the AccessGate. If you are deploying a firewall (or another device) between the AccessGate and the Access Server, this value should be smaller than the timeout setting for the firewall. Failover Threshold: Number representing the point when this AccessGate opens connections to Secondary Access Servers. If you type 30 in this field, and the number of connections to primary Access Servers falls to 29, this AccessGate opens connections to secondary Access Servers. Preferred HTTP Host : Defines how the host name appears in all HTTP requests as they attempt to access the protected Web server. The host name in the HTTP request is translated into the value entered into this field regardless of the way it was defined in a user’s HTTP request. Primary HTTP Cookie Domain: This parameter describes the Web server domain on which the AccessGate is deployed, for instance, IPValidation: IP address validation is specific to WebGates and is used to determine whether a client’s IP address is the same as the IP address stored in the ObSSOCookie generated for single sign-on. Q.What Is Policy Manager Api? Ans: The Policy Manager API provides an interface which enables custom applications to access the authentication, authorization, and auditing services of the Access Server to create and modify Access System policy domains and their contents. Q.When Do You Need An Access Gate? Ans: An access gate is required instead of a standard webgate when you need to control access to a resource where OAM doesnot provide OOTB solution. These might include: protection for non-http resources (EJB, JNDI etc.,) Implementation of SSO to protect a combination of http and non-http resources. A file called obAccessClient.xml is stored in the server where access gate is installed. this file contains config params entered through the configureAccessGate tool. Q.Explain The Flow When A User Makes A Request Protected By An Access Gate (not Webgate)? Ans: The flow is shown below: The application or servlet containing the access gate code receives resource request from the user. The access gate code constructs ObResourceRequest structure and access gate contacts Access server to find whether resource is protected or not. The access server responds. If the resource is not protected, access gate allows user to access the resource. Otherwise.., Access Gate constructs ObAuthenticationScheme structure to ask Access Server what credentials the user needs to supply. The access server responds. The application uses a form or some other means to fetch the credentials. The AccessGate constructs ObUserSession structure which presents user details to Acc Server. If credentials are proven valid, access gate creates a session token for the user and then sends an authorization request to the access server. Access server validates if the user is authz to access that resource. Access gate allows user to access the requested resource. Q.Explain How Form Login Works If The Form Login Page Is Present In Different Domain From Oam? Ans : The mechanism here is same as how the multi domain SSO works. Importantly, all of the activities for form authentication are carried out between the browser and one web server. Now, suppose you want to access a resource but still be authenticated by the login form on The authentication scheme required by pageB needs to have a redirect URL set to The WebGate at redirects you to the NetPoint URL obrareq.cgi on, with a query string that contains the original request (wu and wh). The WebGate on will determine that you need to do a form login for that resource, so it will set the ObFormLoginCookie with the wu and wh values from the query string, but will set the ru field to /obrareq.cgi. WebGate on A then redirects your browser to the login form on A. When you post your credentials back to A, the ObFormLoginCookie is set back. WebGate on A authenticates your userid and password, sets the ObSSOCookie for the domain and redirects you back to the ru value from the ObFormLoginCookie, which is /obrareq.cgi. This time when your browser requests, it will pass the ObSSOCookie. WebGate will then redirect your browser back to the B webserver,, with the cookie value and the original URL in the query string. The WebGate on will extract the cookie value and set the ObSSOCookie for domain, and finally redirect you to that you originally requested. Contact for more on OAM Online Training

    oracle apps scm interview questions

    Q.What is Oracle ADF? Ans: Oracle ADF is an commercial java/j2ee framework, which is used to build enterprise applications. It is one of the most comprehensive and advanced framework in market for J2EE Q.What are the advantages of using ADF? Ans: Following are the advantages of using: It supports Rapid Application Development. It is based on MVC architecture Declarative Approach (XML Driven) Secure Reduces maintenance cost and time SOA Enabled Q.What are various components in ADF? Ans: Oracle ADF has following components ADF Business Components(Model) ADF Faces (View) ADF Task flows(Controller) Q.What is the return type of Service Methods? Ans: Service Methods can return Scalar or Primitive Data types. Q.Can Service Methods return type Void? Ans: Yes, Service Methods can Return type Void Q.Can Service Methods return Complex Data types? Ans: No, service methods can return only primitive/scalar data types. Q.Which component in ADF BC manages transaction ? Ans: Application Module, manages transaction. Q.Can an entity object be based on two Database Objects(tables/views) or two Web services ? Ans: No entity objects will always have one to one relationship with a database object or web service. Q.Where is that we write business rules/validations in ADF and why? Ans: We should be writing validations at Entity Object level, because they provide highest degree of reuse. Q.What is Managed Bean? Ans: Managed bean is a java class, which is initialized by JSF framework. It is primarily used to hold view and controller logic. It is also used to execute java code to be executed on a user action like Button Click. Q.What are Backing Bean? Ans: Backing beans are those managed beans which have 1:1 mapping with a page. They have getters and setters for all the components in the related page. Q.What is difference between managed and backing beans? Ans: Backing bean has 1:1 relation with page whereas managed beans can be used in multiple pages. Backing beans scope is limited to the page whereas managed beans can have other scopes too. Q.What is a Task flow? Ans: Task flow is the controller of an ADF application, it provides us an declarative approach to define the control flow. It is used to define the navigation between pages and various task flow activites. Q.What are the different types/categories of Task flows ? Ans: Task flows are of two categories: Bounded and Unbounded. Q.What is the difference between Bounded and Unbounded task flows? Ans: Differences between Bounded and Unbounded task flows : Bounded task flows can be secured but Unbounded can’t. Bounded taskflows can accept parameter and return values but unbounded taskflows don’t support parameters Bounded taskflows has a single entry point or a default activity but unbounded taskflows have multiple entry points. Bounded taskflows can be called from other bounded/unbounded taskflows but unbounded cannot be called or reused. Bounded taskflows support transactions unbounded don’t Q.What are the various access scopes supported by ADF? Ans: ADF Faces supports the following scopes Application Scope Session Scope PageFlow Scope Request Scope Backing Bean Scope. Q.Describe life cycle of a ADF Page? Ans: ADF page is an extension of JSF and has following phases in its lifecycle Initialize Context: In this phase the adf page initializes the LifecycleContext with information that will be used during the Lifecycle. Prepare Model: In this phase ui model is prepared and initialized. In this phase page parameters are set and methods in the executable section of the page definition of the ADF page are executed. Apply Input Values: This phase handles the request parameters. The values from the HTML are sent to the server and applied to the page binding in page definitions. Validate Input Values: This phase validates the values that were built in the Apply input values phase Update Model: Validated values supplied from user are sent to ADF business components data model Validate Model Updates: In this phase the business components will validate user supplied values. Invoke Application: This phase will process the ui events stack built during the life cycle of page and also fire navigational events Prepare Render: This is the final phase where HTML code is generated from the view tree. Q.What is PPR and how do you enable Partial Page Rendering (PPR)? Ans: PPR is a feature supported by ADF Faces, using which we can render a small portion of a HTML Page, without refreshing the complete page. It is enabled by. Setting AutoSubmitproperty to true on the triggering element. Setting the PartialTriggersproperty of target component to refer to component id of the triggering element. Q.What is Action Listener? Ans: An action listener is a class that wants to be notified when a command component Fires an action event. An action listener contains an action listener method that Processes the action event object passed to it by the command component Q.What are businesses Component In ADF. Describe them? Ans: All of these features can be summarized by saying that using ADF Business Components for your J2EE business service layer makes your life a lot easier. The key ADF Business Components that cooperate to provide the business service Implementations are: ■ Entity Object An entity object represents a row in a database table and simplifies modifying its data by handling all DML operations for you. It can encapsulate business logic for the row to ensure your business rules are consistently enforced. You associate an entity object with others to reflect relationships in the underlying database schema to create a layer of business domain objects to reuse in multiple applications. ■ Application Module An application module is the transactional component that UI clients use to work with application data. It defines an up datable data model and top-level Procedures and functions (called service methods) related to a logical unit of work Related to an end-user task. ■ View Object A view object represents a SQL query and simplifies working with its results. You use the full power of the familiar SQL language to join, project, filter, sort, and Aggregate data into exactly the “shape” required by the end-user task at hand. This Includes the ability to link a view object with others to create master/detail Hierarchies of any complexity. When end users modify data in the user interface, Your view objects collaborate with entity objects to consistently validate and save The changes Q.What is Top Link? Ans: Top Link is an Object-Relational Mapping layer that provides a map between the Java objects that the model uses and the database that is the source of their data. By default, a session is created named default. In the following steps, you create a new session Q.What is Managed Bean? Ans: JavaBean objects managed by a JSF implementation are called managed beans. A managed bean describes how a bean is created and managed. It has nothing to do with the bean’s functionality. Managed bean is about how the bean is created and initialized. As you know, jsf uses the lazy initialization model. It means that the bean in the particular scope is created and initialized not at the moment when the scope is started, but on-demand, i.e. when the bean is first time required. Q.What is Backing Bean? Ans: Backing beans are JavaBeans components associated with UI components used in a page. Backing-bean management separates the definition of UI component objects from objects that perform application-specific processing and hold data. Backing bean is about the role a particular managed bean plays. This is a role to be a server-side representation of the components located on the page. Usually, the backing beans have a request scope, but it is not a restriction. The backing bean defines properties and handling-logics associated with the UI components used on the page. Each backing-bean property is bound to either a component instance or its value. A backing bean also defines a set of methods that perform functions for the component, such as validating the component’s data, handling events that the component fires and performing processing associated with navigation when the component activates. Q.What is view object? Ans :A view object is a model object used specifically in the presentation tier. It contains the data that must display in the view layer and the logic to validate user input, handle events, and interact with the business-logic tier. The backing bean is the view object in a JSF-based application. Backing bean and view object are interchangeable terms Q.Difference between Backing Bean and Managed Bean? Backing Beans Managed Beans A backing bean is any bean that is referenced by a form. A managed bean is a backing bean that has been registered with JSF (in faces-config.xml) and it automatically created (and optionally initialized) by JSF when it is needed. The advantage of managed beans is that the JSF framework will automatically create these beans, optionally initialize them with parameters you specify in faces-config.xml, Backing Beans should be defined only in the request scope The managed beans that are created by JSF can be stored within the request, session, or application scopes Q.What do you mean by Bean Scope? Ans; Bean Scope typically holds beans and other objects that need to be available in the different components of a web application. Q.What are the different kinds of Bean Scopes in JSF? Ans: JSF supports three Bean Scopes. viz., Request Scope: The request scope is short-lived. It starts when an HTTP request is submitted and ends when the response is sent back to the client. Session Scope: The session scope persists from the time that a session is established until session termination. Application Scope: The application scope persists for the entire duration of the web application. This scope is shared among all the requests and sessions. Q.What is the difference between JSP-EL and JSF-EL? JSP-EL JSF-EL In JSP-EL the value expressions are delimited by ${…}. In JSf-EL the value expressions are delimited by #{…}. The ${…} delimiter denotes the immediate evaluation of the expressions, at the time that the application server processes the page. The #{…} delimiter denotes deferred evaluation. With deferred evaluation, the application server retains the expression and evaluates it whenever a value is needed. Q.How to declare the page navigation (navigation rules) in faces-config.xml file in ADF 10g? Ans: Navigation rules tells JSF implementation which page to send back to the browser after a form has been submitted. We can declare the page navigation as follows: /index.jsp login /welcome.jsp This declaration states that the login action navigates to /welcome.jsp, if it occurred inside /index.jsp. Q.Setting the range of table Ans: Q.Which component in ADF BC manages transaction ? Ans: Application Module, manages transaction. Q.Can an entity object be based on two Database Objects(tables/views) or two Web services ? Ans: No entity objects will always have one to one relationship with a database object or web service Q.Where is that we write business rules/validations in ADF and why? Ans: We should ideally be writing validations at Entity Object level, because they provide highest degree of reuse. Q.What are the JSF life-cycle phases? Ans: The six phases of the JSF application lifecycle are as follows (note the event processing at each phase): Restore view 2.Apply request values; process events 3. Process validations; process events 4. Update model values; process events 5. Invoke application; process events 6. Render response Q.Explain briefly the life-cycle phases of JSF? Ans: Restore View: A request comes through the FacesServlet controller. The controller examines the request and extracts the view ID, which is determined by the name of the JSP page. 2. Apply request values: The purpose of the apply request values phase is for each component to retrieve its current state. The components must first be retrieved or created from the FacesContext object, followed by their values. 3. Process validations: In this phase, each component will have its values validated against the application’s validation rules. 4. Update model values: In this phase JSF updates the actual values of the server-side model ,by updating the properties of your backing beans. 5. Invoke application: In this phase the JSF controller invokes the application to handle Form submissions. 6. Render response: In this phase JSF displays the view with all of its components in their current state. Q.What is setActionListener? Ans: SetActionListener – The setActionListener tag is a declarative way to allow an action source ( , , etc.) to set a value before navigation. It is perhaps most useful in conjunction with the “process Scope” EL scope provided b ADF Faces, as it makes it possible to pass details from one page to another without writing any Java code. This tag can be used both with ADF Faces commands and JSF standard tags. Example of this can be as follows. Suppose we have a table “employee”. We want to fetch the salary of an employee of some particular row and want to send this salary in Next page in process scope or request scope etc.So using this we can do this. It have two attributes: From – the source of the value; can be an EL expression or a constant value To – the target for the value; must be an EL expression 1 2 to=”#{processScope.salary1}”/> This setActionListener will pick value of salary of that row and store this value into salary1 variable.So anyone can use this salary As processScope.salary1 . It is very simple to use. And very useful. contact for more on Oracle ADF Online Taining

    oracle apps scm interview questions

    Q.What Is Level 0, Level 1 Backup? Ans: A level 0 incremental backup, which is the base for subsequent incremental backups, copies all blocks containing data, backing the data file up into a backup set just as a full backup would. A level 1 incremental backup can be either of the following types: A differential backup, which backs up all blocks changed after the most recent incremental backup at level 1 or 0 A cumulative backup, which backs up all blocks changed after the most recent incremental backup at level 0 Q.How Do You Setup The Rman Tape Backups? Ans: Configure channel as SBT_TAPE and use “ENV” parameter to set the tape configurations. Q.What Is The Init Parameter Specify The Minimum Number Of Days That Oracle Keeps Backup Information In The Control File? Ans: You can use the CONTROL_FILE_RECORD_KEEP_TIME parameter to specify the minimum number of days that Oracle keeps this information in the control file. Q.What Is The Difference Between Validate And Crosscheck ? Ans: The restore/validate and validate backupset commands test whether you can restore backups or copies. You should use: restore : validate when you want RMAN to choose which backups or copies should be tested. validate backupset when you want to specify which backup sets should be tested. Q.How Do I Go About Backing Up My Online Redo Logs? Ans : Online redo logs should never, ever be included in a backup, regardless of whether that backup is performed hot or cold. The reasons for this are two-fold. First, you physically cannot backup a hot online redo log, and second there is precisely zero need to do so in the first place because an archive redo log is, by definition, a backup copy of a formerly on-line log. There is, however, a more practical reason: backing up the online logs yourself increases the risk that you will lose. Q.What Is Backup Set? Ans : RMAN can store backup data in a logical structure called a backup set, which is the smallest unit of an RMAN backup. A backup set contains the data from one or more data files, archived redo logs, or control files or server parameter file. Q.What Is Channel? How Do You Enable The Parallel Backups With Rman? Ans: Use the ALLOCATE CHANNEL command to manually allocate a channel, which is a connection between RMAN and a database instance. To enable the parallel backups, allocate multiple manual channels in the run block or configure parallelism CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET; Q.What Is Auxiliary Channel In Rman? When Do You Need This? Ans: An auxiliary channel is a link to auxiliary instance. If you do not have automatic channels configured, then before issuing the DUPLICATE command, manually allocate at least one auxiliary channel within the same RUN command. When a Duplicate Database created or table space point in time recovery is performed Auxiliary database is used. This database can either on the same host or a different host. Q.Is It Possible To Specific Tables When Using Rman Duplicate Feature? If Yes, How? Ans: No, table based recovery not possible in RMAN duplicate command. Q.Outline The Steps Involved In Cancel Based Recovery From The Full Database From Hot Backup? Ans : RMAN doesn’t support cancel-based recovery like SQL*plus does. Q.Outline The Steps Involved In Scn Based Recovery From The Full Database From Hot Backup? Ans: startup mount; restore database UNTIL SCN 233545; recover database UNTIL SCN 233545; alter database open resetlogs; Q.How Do You Verify The Integrity Of The Copy In Rman Environment? Ans: Use below commands : rman> catalog datafilecopy ‘f:testsystem.dbf’; rman> backup validate check logical datafile ‘f:testsystem.dbf’; SQL> SELECT * FROM v$database_block_corruption; Q.Is It Possible To Take Catalog Database Backup Using Rman? If Yes, How? Ans: Recovery catalog is a schema stored in a database that tracks backups and stores of target databases. So better to take a export backup.How Do You Identify The Expired, Active, Obsolete Backups? Which Rman Command You Use? Ans : Obsolete backups: RMAN> report obsolete; expired backup: RMAN> list expired backup; Active database: RMAN> list backup; Q.Outline The Steps Involved In Time Based Recovery From The Full Database From Hot Backup? Ans: startup mount; restore database UNTIL TIME “TO_DATE(’28/12/2012 18:00:00′, ‘DD/MM/YYYY HH24:MI:SS’)”; recover database UNTIL TIME “TO_DATE(’28/12/2012 18:00:00′, ‘DD/MM/YYYY HH24:MI:SS’)”; alter database open resetlogs; Q.Explain The Steps To Perform The Point In Time Recovery With A Backup Which Is Taken Before The Resetlogs Of The Db? Ans: We need to list the database incarnations by using list incarnation command. shutdown the database startup mount the database Issue reset database to incarnation to reset the incarnation. Restore the database using restore command (e.g restore until scn 23243) recover database Open the database using resetlogs command RMAN> list incarnation of database; RMAN>reset database to incarnation 5; run { set until scn 234345; restore database; rec …. Q.Outline The Steps For Changing The Dbid In A Cloned Environment? Ans: shutdown Immediate startup mount Then, run the the DBNEWID utility from command line. nid target =/ SQL> alter database open resetlogs; Q.How Do You Install The Rman Recovery Catalog? Or List The Steps Required To Enable The Rman . Backup For A Target Database? Ans: Steps to be followed: Create connection string at catalog database. At catalog database create one new user or use existing user and give that user a recovery_catalog_owner privilege. Login into RMAN with connection string export ORACLE_SID rman target catalog @connection string rman&g …. Q.List Some Of The Rman Catalog View Names Which Contain The Catalog Information? Ans: RC_DATABASE_INCARNATION, RC_BACKUP_COPY_DETAILS, RC_BACKUP_CORRUPTION, RC_BACKUP_DATAFILE_SUMMARY to name a few Q.What Is The Difference Between Obsolete Rman Backups And Expired Rman Backups? Ans: The term obsolete does not mean the same as expired. In short obsolete means “not needed ” whereas expired means “not found.” A status of “expired” means that the backup piece or backup set is not found in the backup destination. A status of “obsolete” means the backup piece is still available, but it is no longer needed. The backup piece is no longer needed since RMAN has been configured to no longer need this piece after so many days have elapsed, or so many backups have been performed. Q.When Do You Use Crosscheck Command? Ans: Crosscheck will be useful to check whether the catalog information is intact with OS level information. Q.If Some Of The Blocks Are Corrupted Due To System Crash, How Will You Recover? Ans: Using RMAN BLOCK RECOVER command Q.You Have Taken A Manual Backup Of A Datafile Using O/s. How Rman Will Know About It? Or How To Put Manual/user-managed Backup In Rman (recovery Catalog)? Ans: By using catalog command.You have to catalog that manual backup in RMAN’s repository by command RMAN> catalog datafilecopy ‘/DB01/BACKUP/users01.dbf’; or RMAN> CATALOG START WITH ‘/tmp/backup.ctl’; Restrictions: > Accessible on disk A complete copy of a single file Q.Where Rman Keeps Information Of Backups If You Are Using Rman Without Catalog? Ans: RMAN keeps information of backups in the control file. Q.What Is The Diff Between Catalog And Nocatalog? Ans: The difference is only who maintains the backup records like when is the last successful backup incremental differential etc. In CATALOG mode another database (TARGET database) stores all the information. In NO CATALOG mode controlfile of Target database is responsible. Q.How Do You See Information About Backups In Rman? Ans: RMAN> List Backup; Q.How Do You Monitor Rman Backup Job Status? Ans: Use this SQL to check SQL> SELECT sid totalwork sofar FROM v$session_longops WHERE sid 153; Here give SID when back start it will show SID Q.How Rman Improves Backup Time? Ans: RMAN backup time consumption is very less than compared to regular online backup as RMAN copies only modified blocks. Q.What Is The Difference Between Cumulative Incremental And Differential Incremental Backups? Ans: Differential backup: This is the default type of incremental backup which backs up all blocks changed after the most recent backup at level n or lower. Cumulative backup: Backup all blocks changed after the most recent backup at level n-1 or lower. Q.How Do You Enable The Autobackup For The Controlfile Using Rman? Ans: issue command at rman prompt….. RMAN> configure controlfile autobackup on; also we can configure controlfile backup format…… RMAN> configure controlfile autobackup format for device type disk to ‘$HOME/BACKUP/RMAN/ F.bkp’; — $HOME/BACKUP/RMAN/ this can be any desired location. Contact for more On Oracle BPM Online Training

    oracle apps scm interview questions

    What is the formula for calculating annual costs?

    Ans: We can calculate the total annual costs using this formula.

    TC = DC +(D/Q)*S + (Q/2)*H

    C – Cost per unit

    S – Cost incurred for placing an order

    H – Annual holding and storage cost per unit of inventory

    Get ahead in your career by learning Oracle Fusion SCM through hkrtrainings Oracle Fusion SCM Training.

    Ans: The following are the seven key Flexfields available in inventory:

  • Account Alias
  • Item Catalogue
  • Stock Locator
  • Item
  • Item Category
  • Sales Order
  • Service Items
  • Ans: The picking rules define the sort criteria for items stored in the sub inventory, lot, locator, revision. It will automatically allocate quantity moving process manufacturing batches or sales orders.We can assign a picking rule to an item through the Order Management tab.

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning
  • Ans: It is essentially a file providing data on both the buyer and the seller, along with the address of both parties. There are also directions for transporting the shipment so that it meets the customer in the original position. The total quantity on the date of shipment, the actual value of the shipment, the exact weight, as well as the description of the item, are the other items listed in the bill of lading.

    Ans: It is simply an arrangement between the transport company and the company that provides the commodity to the customer. Basically, this is to make sure that both the buyers and the shipper do not have to pay a lot of money for the shipment. Rather than anything else the price of the shipment is determined on the basis of factors such as the weight of the commodity to be shipped, the mileage on the chosen lane and a few other factors.

    Ans: Below are the five planning methods in Oracle Inventory.

  • Re-order point planning
  • Kanban Planning
  • Sub Inventory Replenishment Planning
  • Periodic Automatic Replenishment
  • Min Max Planning
  • Ans: The steps for defining an item are,

  • Create an item in the item master form.
  • Copy the template from the tools menu, assign attributes to the item, and save it.
  • Assign a category to the item and save it.
  • Choose the organization assignment, assign inventory organizations to the item by checking the checkbox, and save it.
  • Related Posts

    Leave a Reply

    Your email address will not be published.