Oracle Purchasing: Step by step creation. 1. Log On and go to system administrator2. Go to Application – Menu3. Create a new menu ( RA_MENU1)4. Give the following table and commit.

5. Now create Request Group.

6. Create 4 Responsibilities and attach request group and menus to the responsibilities (ra_resp1, 2, 3, 4). For these responsibilities the application will be manufacturing and the Data group Name will be standard and application will be manufacturing again. For menu and request group give the menu and request group name created earlier.

Create another resp as ra_hrms_resp1. For finding menu and request group query for UK HRMS Navigator and copy the name of menu and request group. Use the menu and request group for ra_hrms_resp1. The data group will be same as standard and manufacturing.

7. Create a new user (RA_USER1) and attach ra_resp1, ra_hrms_resp1 and system administrator as the responsibilities. U can also give more users as user2, 3 and 4. Attach corresponding responsibilities and system administrator in each case.

8. Log out and Log in again as ra_user1. U needs to change your password.

9. Now create accounting calendar (ra_acc_cal1):

(Shift + F6 will copy the previous record)

Points to remember: Choose “Month”, not “MONTH” as the type. Create 13 months, 1 for adjustment. Year means the ending year For adjusting period give tab on “Adjustment”. After validating the calendar, check the output.

There should be no violation found in all the cases.

10. Now create SOB (ra_sob1). Give a short name. The charts of accounts will be operations accounting flex. It will be easier if we use the Vision operations Chart of accounts. The retained earning account is 01-000-3310-0000-000.

11. Assign SOB to responsibility – ra_resp1. In the profile option name search for GL: Set of books name and then assign ra_sob1 as the SOB.

Also assign HR: User Type in the profile option. The option HR with payroll user can be given. Assign this for both the responsibilities – ra_resp1 and ra_hrms_resp1. This profile is needed for creating Location and organization in a particular responsibility and hence we need to assign this profile.

12. Switch responsibility, go to gl and open accounting period. Open only the first period of the calendar. If u open any period other than 1st then the initial periods cannot be opened later.

13. Now create location – ra_loc0 and ra_loc1. Loc0 will have BG, OU, and IMO while loc1 will have all other inventory organizations.

14. Now create a new calendar – ra_cal1. For testing purpose give all dates as working. Before coming out, commit and then built the calendar (tools/built).

15. Now we have to create business group. For this the method is same as making an organization. Go for new organization (ra_bg1). In the type give corporate head quarter. However this may vary later.

Commit after giving location. Then go to classification give as Business group, enable it and commit.

Then go to “others” and give business group info. This will ask for following details, give as per the slide below.

Now attach HR organization to the Business group also. This is needed for creation of positions, jobs, etc in our Business group.

16. Now change the responsibility to system administrator. We have to attach HR security profile to our business group. Once the HR security profile is attached the HR business group profile will be have the same data copied into it. So no need to give HR Business group.

Apart from this we need to attach the business group (ra_bg1) to our hrms responsibility also (ra_hrms_resp1) or else we wont be able to create positions.

Switch responsibility to Sys admin. Go to profile, system. Check for resp - ra_hrms_resp1. In profile give name as HR: Security Profile and then query. Then attach ra_bg1.

17. Switch responsibility back to ra_resp1. Create a Legal entity. The process is same as that of creating organization. Commit before going to classification. Then give classification as GRE/Legal Entity. Commit. Then go to others. Here we have to give a link between LE and SOB. Go to Legal entity accounting in others. Give r_sob1 (short name) as your SOB. Commit.

18. Now we have to create the operating unit. Go to organization creation. Make a new org (ra_ou1). Commit after giving location as ra_loc0.

Now give the classification as Operating unit. Commit. Go to others and click on Operating unit information. Here we have to give the OU information and Legal entity and SOB. If we give LE only it will take SOB automatically. Give LE as ra_le1. Commit.

Creation of an OU needs 3 parameters: Links (Here LE and SOB are already given Profile creation (through sys admin) Replicate seed data concurrent.

Now switch resp to system admin and attach profile MO: Operating unit to ra_ou1. Commit.

19. Now in order to run and link all the programs we need to run concurrent “replicate seed data”. Before running the concurrent we need to have the concurrent attached to our responsibility. This will bring all the needed data structure needed.

Switch responsibility to system administrator and go to security – responsibility – request.

Search for the group you have created in step 5 (ra_req_group1).

In the application it will be manufacturing. Now go to request, give a new request. The type will be Program and name will be Replicate seed data. Commit.

No come back to your responsibility (ra_resp1). Give a new concurrent (Alt, V, R). Give the name of the concurrent as “replicate seed data”. Then give parameter as your OU – ra_ou1. Run the concurrent.

20. Now create Master organization and child organization. Go to inv and make a new organization (ra_imo1). This will be our Item master organization. This will not be used for transaction but only for keeping items and other such functionalities. The location will be ra_loc0.

Give the type as plant and classify as Inventory.

Now commit and give others details. First give accounting information – SOB (r_sob1), LE (ra_le1), OU (ra_ou1). Remember the system will ask for short name of SOB. Give and commit.

Then give inventory information. Give org code as R01. The item master organization should be same as ra_imo1. give the calendar ra_cal1.Give locator control at sub inventory level. Give the accounting details. (here we will copy the Vision operation organization, so that all accounting info will be copied). Costing method should be standard. Give revision as A. Give serial and Lot controls. Now commit.

Now give the receiving information. Give some values for days early, late, etc. These will discuss in detail later.

21. Now make a child organization of the same IMO. Go to new org. Make a new org (ra_io1). Give type as plant and classification as inventory. In accounting info, Inventory info and receiving information give same details as IMO. Only thing to be remembered is that in the inventory information the IMO should be entered as ra_imo1, which is the actual imo and the location will be ra_loc1.

Give org code as R02 and commit. The accounts in the receiving option will be – 01-000-1410-0000-000. copy and paste in all the accounts.

22. Now change org to R02 and open accounting period. One cannot open the accounting periods in IMO since IMO is not for transactions. Hence this works as a fool proof.

23. Creating JOB, Post code, Name, Employment, Post Hierarchy.

JobCode

Job Name Position Code

Name Employee Position hierarchy

100 Jm 1001 Jmm (junior manager – mech)

Emp 1 Top – 1

200 Am 2001 Amm Emp2 2300 Dm 3001 Dmm Emp3 3400 Mgr 4001 Mgrm Emp4 4We will now create a hierarchy position based on above table. There are 4 jobs – jm, am, dm and mgr. Jobs are generic in nature but positions are specific. The 4 positions are jm mech, am mech, dm mech, mgr mech.

We are assuming Full time employee = 1 (FTE) and Head count = 1. For creating jobs, position, etc HRMS resp should point to operating unit. Check this is profile option.

Change responsibility to ra_hrms_resp1. Go to NP – workstructure – job – description. Give a new job. Do not touch the job group given by system. Give a tab and then give job code and job name as per the table.

Four jobs – 100.jm, 200.am, 300.dm, 400.mgrm.

24. Now make the 4 positions as per the table. These positions are for mechanical maintenance dept (for ex).

In the date effective name region give the position code and position name (like 1001.jmm), in ‘type’ give – single incumbent.

In org give your business group (ra_bg1). If you have not attached the HR: security profile and bg to your hrms responsibility then in this field the organization will not appear. Now attach the job description with this particular position (100.jm). Give hiring status as active.

In the Hiring information tab, give FTE and Head count as 1.

Similarly create positions 2001.am, 3001.dm, 4001.mgrm and link with respective jobs.

25. Now we have to create employment for these positions. Use the same hrms responsibility.

Go for new employments. Give the last name as emp1. The following details are mandatory birth date (02-09-81), Gender, Action (create employment) and then commit. The person types will come out as employee automatically.

Then click on assignment tab. It will open a new window. Go to position tab and give the position for this particular employee i.e. 1001.jmm. The system will ask to update or correct. Always go for correction. The system will automatically take the job.

Similarly create for emp2, emp3 and emp4 and assign the respective positions.

26. Now we have to create hierarchy.

Go to the form as per the navigation. Give a new name – ra_hie1. Commit. Here we have to remember that after every entry we have to save the data. In the date column give today’s date. Commit.

Now click on position, give the position of the topmost person (i.e. here 4001.mgrm). Then commit. The ‘Exist in hierarchy’ will automatically become ticked. Now go to subordinate field. Give name as 3001.dmm, the direct sub-ordinate of the 4001.mgrm.

Now click on down arrow and then u will see that the position is now changed to 3001.dmm. Here we again go to subordinate form and give 2001.amm as the subordinate. And so on.

27. Now switch responsibility to your responsibility. Go to purchase module and choose SOB and commit.

28. Now go to purchasing options (in Pur module).

Here in the receipt accounting tab, give the accrual expense account no (01-000-2210-0000-000). In control tab, give details (Enforce full lot qty as mandatory, receipt close point as delivered, cancel requisition on close of PO as always.

In default tab, give price break type as cumulative.

In numbering, give automatic for all RFQ, Quotation, PO and requisition number. Give some no also for the 4 fields, which will end up in being starting of our documents.

In tax detail tab, give only items as ticked and the hierarchy as 1.

29. Then go to financial options and give financial options

In accounting tab give different account nos (take help of LOV).

In Supplier entry tab – give the supplier code which you want to start with.

In supplier purchasing tab – site to, bill to locations and Inventory org are compulsory. Here in inventory org give your IMO since purchasing is global for the org.

In HR tab give use approval hierarchy as checked.

30. Then give the receiving options. .

31. Now we have to link the user with employee. Go to system administrator and then to sys-user-define.

Query for our user name – ra_user1. in the ‘Person’ region enter emp1. Commit.

Similarly for other users like ra_user2, user3, user4.

32. Now go to requisitions. If it is opening the purchasing options have been correct.