Adding a Buyer
You need to be setup as a buyer in the system to raise purchasing orders. To add yourself as a buyer go to responsibility equivalent to Purchasing, Vision Operations (USA).
Go to menu setup –> personnel –> Buyers
Click on add buyers button in new browse window
Click on the search button and search for the user by the name select the username and click select button.
Now click on save button to save the buyer.
Now you can raise the purchasing orders
What is SUPPLY-TO-ORDER?
‘supply-to-order’ includes both the familiar ‘assemble-to-order’ process in which a specific work order is created to build the item and ‘procure-to-order’ (or back-to-back orders) whereby a specific purchase order is created to fulfill the sales order demand. ‘Supply-to-order’ items are either standard items or (with OM Family Pack H) models that have the ‘assemble-to-order’ item attribute turned on. It is this attribute that launches the ATO workflows that deliver this feature. PTO models by definition cannot be ‘supply-to-order’, since turning on the ‘assemble-to-order’ attribute would make them an ATO model. But you can have the shippable options of a PTO model be fulfilled via back-to-back orders by checking the ‘assemble-to-order’ item attribute of those components.
REGISTERING A CONCURRENT PROGRAM
Concurrent programs can be scheduled to run or manually run in oracle applications. In Oracle Applications, concurrent processing simultaneously executes programs running in the background with online operations to fully utilize your hardware capacity, hence the name ‘Concurrent Processing’. You can write a program (called a ”concurrent program”) that runs as a concurrent process. Typically, you create concurrent programs for long running, data intensive tasks, such as posting a journal or generating a report. A concurrent program is an instance of an execution file, along with parameter definitions and incompatibilities. Concurrent programs use concurrent program executable to locate the correct execution file. Several concurrent programs may use the same execution file to perform their specific tasks, each having different parameter defaults and incompatibilities.
CONCURRENT PROGRAM EXECUTABLE
A concurrent program executable links an execution file or and the method used to execute it with a defined concurrent program. Under Concurrent Processing, an execution method may be a program written in a standard language, a reporting tool, or an operating system language. An execution method can be a PL/SQL Stored Procedure, an Oracle Tool such as Oracle Reports or SQL*Plus, a spawned process, or an operating system host language.
CONCURRENT PROGRAM EXECUTION FILE
A concurrent program execution file is an operating system file or database stored procedure which contains your application logic and can be executed by either invoking it directly on the command line or by invoking a program which acts upon it. For example, you run a Pro*C program by invoking it on the command line. You run a SQL script by running SQL*Plus and passing the name of the SQL script without the .sql extension.
STEPS TO CREATE A CONCURRENT PROGRAM
EXECUTABLE :
The first step in creating a concurrent program in oracle applications is to create the concurrent program
executable. To do this, navigate to Application Developer responsibility after you login to Oracle Applications.
To open the Executable form follow the below mentioned navigation path. Application Developer -> Concurrent ->Executable.
1.Executable - Enter executable name here. Enter any user friendly name.
2.Short Name - Enter short name for your executable. This is used for mapping the executable with the concurrent program. Usually executable name are of 8 characters.
3.Application - Give the application to which the executable belongs to. E.g. you want some program to run from oracle payables then account payables should be entered as application name.
4.Description - Give the brief description of the executable in this field.
5.Execution Method - Here you need to choose the appropriate execution method for your executable. Following are the possible execution methods which are commonly used in oracle applications.
–Oracle Reports – used for the RDF reports
–Host – used for shell scripts, basically the language of the host operating system
–PL/SQL Stored procedure – used to run the stored procedure through oracle applications
–SQL*Loader – used to run the sql loader programs
–SQL*Plus - used to run the anonymous PL/SQL blocks. It will get executed in the same fashion as you are running on SQL Plus.
–Java Stored Procedure – The execution file is a Java stored procedure.
–Java Concurrent Program – Used for program written in Java.
–Spawned – used for c or pro*c Program. Mainly used by standard oracle interfaces.
–Perl Concurrent Program – used for programs written in CGI Perl.
–Request Set Stage Function – PL/SQL stored function that can be used to calculate the completion statuses of request set stages.
–Immediate – execution file is a program written to run as subroutine of the concurrent manager. Oracle doesn’t recommend use of this executable type.
–Multi-Language function – execution file is an MLS function that supports running concurrent program in multiple languages.
PL/SQL Stored Procedure, Oracle Reports, Host, SQL*loader, SQL*Plus are the most commonly used executable types.
6. Executable File name – This should contain the name of the executable file. In case of PL/SQL Stored procedure or Java Stored Procedure it should be the fully defined name of the stored procedure.
7. Subroutine Name – This field is only used when executable type is spawned or immediate.
8. Execution File Path –
9. The Stage Function Parameters button opens a window that allows you to enter parameters for the Request Set Stage Function. This button is only enabled when you select Request Set Stage Function as your Execution Method.
DEFINING THE CONCURRENT PROGRAM
Once you have defined the executable, the second step is to define the concurrent program. To define a concurrent program, you need to open the form using the navigation path below.
Navigation – Application Developer -> Concurrent ->Program
Field Description
1.Program – Give user friendly name for your concurrent program. This name will be displayed in Requests submission screen while submitting the requests.
2.Short Name – Give short name for concurrent program. This is used within the database tables in oracle applications. It’s a common practice to have the Short name same for the executable and the concurrent program.
3.Application – Give the application to which the concurrent program belongs to. E.g you want some program to run from oracle payables then account payables should be entered as application name.
4.Description - Give the brief description of the concurrent program.
5.Executable - Enter the short name of the executable (Defined in Executables Screen) you want to attach to this concurrent program.
6.Method - will be defaulted once you enter executable short name
7.Options - will be defaulted once you enter executable short name Normally default values are given for the other fields. Following is the significance of these fields.
8.Request Type – Concurrent program can be associated to a predefined request type so that only few concurrent managers can run the program.
9.Incrementor – To be used by Oracle only.
10.MLS Function - This feature allows the program to be submitted once by the user but runs it in the multiple languages.
11.Use In SRS – Only when this check box is checked the Concurrent Program would be available in Standard Request Submission (SRS) through the request group.
12.Allow Disable Value – This will allow the disabled values in the value sets to be used while entering the values of the parameters in the Concurrent Program.
13. Run Alone – Indicates that program is incompatible with all other concurrent programs and should be run alone.
14.Enable Trace – This will enable the SQL trace for the concurrent program and will generate
the trace file when concurrent program is run. Only used in development environments to check the performance of the concurrent program.
15. Restart on system Failure – This option is used to indicate that concurrent program should automatically be started when concurrent manager is restored after the system failure.
16.NLS Compliant – This box is checked if the program allows for a user to submit request of the program that will reflect a language and territory that are different from the language and territory that the users are operating in.
17.Output Format – Format in which output should be printed. Possible format values are
HTML / PDF TEXT / PS (Post Script) / PCL(HP’s Printer Control Language)
18.SAVE – Check to indicate that output should be automatically saved in an operating system file.
19.PRINT – Whether you want the output to be sent to printer for printing.
20.Column / Rows – Column and Row length of the concurrent program output. Oracle Applications uses this information to decide the print style.
21.Style Required – Print Style
22.Printer – A particular printer on which output should be sent.
Save the data that you have entered using Ctrl+S or File -> Save.
The 3rd step in defining concurrent program is to define the parameters. To do this, click on the
Parameters button as shown at the bottom the form.
Field Description
1.Program – will be defaulted from Concurrent Program
2.Application – will be defaulted from Concurrent Program
3.Conflicts Domain - Enter the parameter which will hold the value of the conflict domain of the program.
4.Security Group - This field is for HRMS security only.
5.Seq – Enter sequence number for the parameter
6.Parameter – name of the parameter, will be displayed in parameter entry screen
7.Description – description about the usage of the parameter
8.Enabled – check box to enable or disable the parameter. Disable a parameter when you don’t want to use it.
9.Value set – enter the name of the value set which you want to use to validate the value enter in the parameter field.
10.Description – will be defaulted from value set definition
11.Default Type – choose the default type for the default value of the parameter. Possible default types are
–Constant : The default value can be any literal value.
–Profile : The default value is the current value in the user profile option defined in the Default Value field. Use the profile option name, not the end–user name. You do not need to include $PROFILE$.
–SQL Statement : The default value is determined by the SQL statement you defined in the Default Value field.
–Segment : The default value is the value entered in a prior segment of the same parameter window.
12.Display size – Enter the field length in characters for this parameter. The user sees and fills in the field in the Parameters window of the Submit Requests window.
13.Token - For a parameter in an Oracle Reports program, the keyword or parameter appears here. The value is case insensitive. For other types of programs, you can skip this field.
Create a Customer
Use Order Management Super User, Vision Operations (USA)
(N) Order Management > Customers > Standard
1. (B) Create.
2. Organization Name: XX-Big City. Leave Alias, D-U-N-S Number, URL, and Context Value.
3. Account Description: Enter a description for your customer.
4. Profile Class: Default.
5. Account Type: External. Leave all other fields, in the Account Information region, blank.
6. Country: United States.
7. Address Line 1: 102 N. LaSalle.
8. City: Chicago.
9. County: Cook
10. State: Illinois.
11. Postal Code: 60610. Leave all other fields, in the Account Site Address region, blank.
12. In the Business Purpose region, set Purpose to Bill To and check the Primary check box.
13. (B) Apply.
14. (B) Create Site.
15. Country: United States.
16. Purpose: Deliver To.
17. (B) Create Address.
18. Address Line 1: 487 Beverly.
19. City: Palo Alto.
20. County: San Mateo.
21. State: California.
22. Postal Code: 94301.
Leave all other fields, in the Account Site Address region, blank.
23. In the Business Purpose region, set Purpose to Deliver To and leave the Primary check box unchecked.
24. (B) Apply.
Defining Release Rules
Select Order Management Super User, Vision Operations (USA) Responsibility
Create Release Rule
1. (N) Shipping > Setup > Picking > Define Release Rules Form > (T) Order
- XX-Seattle’s Rule
- All
2. (T) Inventory
- M1
- XX-Subinventory
- Yes
3. (T) Shipping
- M1-Seattle
- XX-Oldest First
- All Pick Release Document
- Yes
- Yes
4. (M) File > Save.
Manually Updating a Price List
Use responsibility, Oracle Management Super User, Vision Operations
1. Navigate to the Price Lists window, and find your price list named XX-Price List 4.
-
(N) Pricing > Price Lists > Price Lists window
2. Enter an End Date for the item AS54888.
3. Add a new line for the same item and uom with a future start date and a Unit Price of $1699. This preserves the pricing history of an item.
4. For item AS92888, change the selling price to $2500 without maintaining the pricing history of the item.
5. (I) Save.
Oracle HRMS Defining Jobs
Change the below variables like dates & name depending on your organization.
Log in as ouhrms/welcome and use the OU HRMS Manager responsibility.
Navigate to the Job window.
1 (N) Work Structures > Job > Description
2. Click in the Name field to display the Job flexfield.
3. Enter the job names given under the Tasks section.
4. Enter the start date for each job as 01-JAN-2004.
5. Save your work.
Entering Evaluation System Details
6. Select the Evaluation button to enter the evaluation information for this job.
7. Select Custom as the evaluation system.
8. Enter 10 as the overall score, Points units of measurement.
9. Select 1-JUN-2004 as the date of evaluation.
10. Enter the additional evaluation system details. Select Meets Expectations for performance and P1 for problem solving ability.
11. Save your work.
Entering Requirements
12. If you have any Special Information Types enabled, you can select the Requirements button to enter the special requirements needed for this job.
13. Click in the Special Information Type field and select Professional Licenses window.
14. Click in the Job Requirement field and enter the license details.
15. Save your work.
Entering Grades
16. Enter the grade information for this job using the Valid Grades window.
17. Select MGMT.1 as a grade for the job.
18. Save your work.
Entering Work Preferences
19. Enter the work preferences for this job.
20. Select the Relocation Required and Passport boxes.
21. Select the length of time such as five years.
22. Select Mon to Fri as the work schedule.
23. Select 1 as the proportion of full time hours required.
24. Select One year as the minimum length of service.
Entering Extra Job Information
25. Enter the extra job information if required.
Entering Salary Survey Information
26. Enter Vg Cons Sal Survey as the name of the market salary survey and Vickery and Gibson as the salary survey company.
27. Enter the salary survey identifier.
28. Enter Annual Survey as the survey type.
29. Enter National Averages as the Base Region.
Note: Once you have set up all your salary survey details, making changes to the survey type and base region information may invalidate your survey. Oracle HRMS enables you to change this information so you can correct any mistakes, however you should not change this information to update an existing survey.
30. Save your work.
31. Enter the default start and end date for your salary survey lines.
32. These dates will be used for every salary survey line. However, you can amend the default dates when you enter the salary survey line.
33. Enter the Pound Sterling as the currency for your salary survey lines.
34. Enter a job name, start date and currency for the salary survey line. If required, enter an end date for the salary survey line.
35. Enter a definition of your salary survey lines such as Region the survey includes, Seniority of the survey, Company size of the survey, Industry of the survey, and Age of the survey.
36. Enter a start and end date to create a history of salary survey information. Ensure that the job and salary definition information is never the same for two salary survey lines on the same date.
37. Enter the salary details for the line. You can enter details such as the minimum pay, mean pay, percentage change, and first quartile.
38. Enter all the salary survey lines you require for the salary survey.
39. Save your salary survey lines.
What is CRP / Conference Room Piloting?
CRP Stands for Conference Room Piloting
The CRP Sessions are conducted to transform Oracle Applications knowledge to the customer before conducting UAT (User Acceptance Test) and End User Training
The No.of CRP you need to have and when it needs to be conducted depends on Client Industry, Size of Implementation and client knowledge in general about ERP applications.
I have implemented ERP solutions where customer migrate from one ERP to another. In those cases two CRP sessions are enough.
If client does not have any idea about ERP, then it is better to have it three
CRP 1: Generally it is conduted at initial phase after you finish RD010 and RD020 - Basically to provide an overview of Oracle ERP after understanding client Business
CRP2: Conducted after BP080 (Future Business Model) - Configure the system as per client Future Business Model and Demonstrate. This will help you to identify the client expectation and prepare BR010 Gap Analysis Document
CRP3: Develop workaround or customization for the Gaps identified in the CRP2 and fix them and demonstrate a full fledged solution suitable to Client Business
Recent Posts
- Oracle Nukes ETRM
- Urgent Required- IT MNC- Oracle Apps SCM Professionals-Bangalore,Pune,Chennai,Hyderabad
- Account Receivables Tables list oracle r12.2
- General Ledger tables
- Account Payables Tables
Recent Comments
Archives
- April 2021
- June 2015
- April 2015
- March 2015
- July 2014
- April 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- August 2013
- January 2013
- June 2012
- May 2012
Categories
- Account Payables
- Advanced Pricing
- General Ledger
- implementation
- Inventory
- jobs
- Multi Org
- Oracle apps general
- oracle fnd
- oracle forms
- oracle hrms
- Order Management
- Purchasing
- Receivables
- Uncategorized
- vision instances