FINAL OM2

ORDER MANAGEMENT

BY

Annu Malik Zameer(432) Gopi Swaroop Sai Kumar(442)

Madhuri Uppala ( 445)Madhuri Dangeti(446)

Murali Chanda (447) Pallavi Pulluri (450)

Sai Kumar Konduru(460)Sathish Barapati (461)

Vijjy Arre (449)Vijay Atmakur (468)

1

Table of Contents1)OM Overview............................................................................................4

2)Standard OM Cycle...................................................................................52.1)OM Cycle Flow Chart...................................................................52.2)Steps..............................................................................................5

2.2.1)Quotations.........................................................................52.2.2)Placing Order....................................................................62.2.3)Booking Order...................................................................62.2.4)Delivery.............................................................................62.2.5)Invoice...............................................................................62.2.6)Receipt...............................................................................6

3)Defining Item Attributes & Price List.......................................................73.1)Item Attributes for Order Management.........................................7

3.1.1)Inventory Attributes...........................................................73.1.2)Purchasing Attributes......................................................123.1.3)Order Management Attributes.........................................13

3.2)Adding Item in the Price List......................................................16

4)Fulfillment Methods................................................................................184.1)Ship From Stock..........................................................................184.2)Make to Order.............................................................................204.3)Configure to Order......................................................................22

4.3.1)Assemble to Order(ATO)...............................................224.3.2)Pick to Order(PTO).........................................................22

4.4)Back to Back Order.....................................................................234.5)Drop Shipment............................................................................254.6)IR-ISO.........................................................................................26

5)Functional Part Of the Modules..............................................................275.1)Ship From Stock..........................................................................275.2)Back-to-Back Order....................................................................455.3)Drop Shipment Order..................................................................635.4)IR-ISO.........................................................................................76

2

6)Trading Committee Architecture(TCA)..................................................93

7)Defaulting Rules...................................................................................1027.1)Customer Specific Default Rules..............................................102

8)Technical of O.M..................................................................................107

3

1.OM OVERVIEW Oracle Order Management (OM) is the most popular among all modules due to its much improved functionality in last 5 years and heavy demand for Oracle Management knowledgeable resources.

Order Management provides you with the tools to manage your sales orders and control your operations. Orders for your organization can be managed through Order organizer/workbench which is a one place stop for any orders that you have with facility to Find Orders, Order Organizer,Sales Orders, Order Mass Change, and Line Mass Change windows. These windows enable you to enter, update and find your existing Orders and Returns. They also provide you access to a variety of operations you can perform on Orders and Returns.

To fulfill an order line in Oracle Order Management means to satisfy the requirements for completion. Order Management provides the functionality required to recognize fulfillment of an order line, and to cause some order lines to wait until other related order lines have been fulfilled before processing can continue.Order Management's fulfillment functionality provides a simple way to synchronize line workflows for multiple order lines. It allows you to prevent invoicing of lines within a fulfillment set until all lines are ready for invoicing. Seeded workflow processes and activities can be used to provide baseline functionality for sales order, drop ship and return lines. The functionality is also designed to allow you the flexibility to define other activities as fulfillment methods so that you can model your unique business processes.Order Management allows you to group lines into a fulfillment set and to establish a gate activity in your workflow process. Lines in a fulfillment set will wait until all lines in the set have been fulfilled to proceed through the gate. This gate is known as the fulfillment activity. The fulfillment feature is primarily designed to allow the grouping of related lines and to keep any lines in the group from being invoiced until all lines have been fulfilled. You may find additional uses for the fulfillment functionality in your business.

4

2.STANDARD OM STEPS➢ 2.1.OM CYCLE FLOW CHART

➢ 2.2.STEPS

➢ 2.2.1)QUOTATIONS :

A formal statement of promise (submitted usually in response to a request for a quotation) by potential supplier to supply the goods or services required by a buyer at specified prices and within a specified period.A quotation may also contain terms of sale and payment and warranties. Acceptance of quotation by the buyer constitutes an agreement binding on both parties.

5

QUOTATION

PLACING ORDER

ORDER BOOKING

DELIVERY

INVOICE

RECEIPT

➢ 2.2.2 PLACING ORDER :

Entering the quotation details and customer's details into the “ORDER ENTRY” form.

➢ 2.2.3 ORDER BOOKING :

A customer's order is booked in this step. The order can be booked manually or online by the customer.

➢ 2.2.4 DELIVERY :

The order booked in the ABOVE STEP is delivered to the customer to fulfill the promise of the customer's need.

➢ 2.2.5 INVOICE :

A written account of the particulars of merchandise shipped or sent to a purchaser with the prices and charges annexed.

➢ 2.2.6 RECEIPT:

A receipt is a written acknowledgment that a specified article or sum of money has been received as an exchange for goods or services.

6

3. Defining Item Attributes & Price List

3.1)Item Attributes

3.1.1) Inventory Attributes

Following are the Inventory attributes and their possible values. You have to set these attributes when defining or updating items.

7

Inventory ItemIndicate whether to stock and transact this item in Oracle Inventory. You must turn this option on if you want to enable the following item attributes: Stockable, BOM Allowed, Transactable, and Build in WIP.

StockableIndicate whether to stock this item in Inventory. You can set this attribute only when you turn on the Inventory Item option. Turning this option on enables you to set the Transactable item attribute.

TransactableIndicate whether to allow Inventory transactions. You can set this attribute only when you turn on the Stockable option.

Revision ControlIndicate whether to track inventory balances by revision. If you turn this option on you must specify an existing revision number for issues and receipts. Attention: You cannot change revision control when an item has quantity on hand. If Revision Control is controlled at the Master Item level, the check for on-hand quantity is against the sum of on-hand quantities in all child organizations.

Reservable

Indicate whether you can create material reservations. You can reserve an item only when you have sufficient inventory. Attention: You cannot turn reservation control off if reservations exist.

Lot Control

No control Do not establish lot control for the item. Full control

Track inventory balances by lot number. You must specify a lot number for issues and receipts.

You can establish lot number control only for an item that has no quantity on hand. If Lot Control is controlled at the Master Item level, the check for on-hand quantity is against the sum of on-hand quantities in all child organizations.

8

Starting Lot PrefixEnter a starting prefix for all lot numbers you define for this item. When Lot Number Generation is At item level in the organization parameters, this prefix is used when you define a lot number.

Starting Lot NumberEnter a starting numeric suffix for this item only. When Lot Number Generation is At item level in the organization parameters, this starting numeric suffix is used when you create a lot number.

Lot Expiration (Shelf Life) ControlLot Expiration control governs how long items in a given lot remain available.

Shelf life days

Specify a number of days for all lots of an item, beginning on the day you create the lot by receiving the item. You receive a warning message that the lot expires after the specified number of days.

No control Shelf life control not established for this item User-defined

Specify an expiration date as you receive each lot. You receive a warning but are not prevented from using the lot after expiration.

Attention: You cannot change lot expiration control when an item has quantity on hand. If Lot Expiration is controlled at the Item level, the check for on-hand quantity is against the sum of on-hand quantities in all child organizations.

Shelf Life DaysEnter the number of days each lot is active. At receipt, the expiration date is determined by adding the shelf life days to the system date (includes the day you define the lot). This is used only when you choose Shelf life days for Lot Expiration Control.

9

Serial Generation

At inventory receipt

Create and assign serial numbers when you receive the item. Thereafter, for any material transaction, you must provide a serial number for each unit.

At sales order issue

Create and assign serial numbers when you issue (ship) the item against a customer sales order. (Internal requisition orders do not require a serial number when you ship the item.) If you receive an item on an RMA (return material authorization), you must specify the same serial numbers you created at sales order issue. All other material transactions for this item bypass serial number information.

No control Serial number control not established for this item. All material transactions involving this item bypass serial number information.

Predefined Assign predefined serial numbers when you receive the item. Thereafter, for any material transaction, you must provide a serial number for each unit.

You can change back and forth between certain options under the following conditions:

Change back and forth between When Dynamic entry at inventory receipt

Predefined serial numbers Any time

Dynamic entry at sales order issue

No serial number control Any time

Dynamic entry at inventory receipt

No serial number control Item has no on-hand quantity


Predefined serial numbers Item has no on-hand quantity

Predefined serial numbers No serial number control Item has no on-hand quantity

Dynamic entry at inventory receipt


Item has no on-hand quantity

10

Starting Serial PrefixEnter a starting alpha prefix for all serial numbers you define. You must enter a value when you choose Predefined and when Serial Generation is At item level in the organization parameters. This prefix is used when you define your serialized units.

Starting Serial NumberEnter a starting numeric suffix for all serial numbers for this item only. You must enter a value when you choose Predefined and when Serial Number Generation is At item level in the organization parameters. This starting numeric suffix is used when you define your serialized units. Thereafter, this number is incremented for each succeeding serial number.

Locator Control

Dynamic entry

Define locators when you use them, either as you receive or ship items.

No control Locator control not established. Prespecified Define locators before you use them.

Attention: You cannot change locator control when an item has quantity on hand.

11

3.1.2) Purchasing Attributes

Following are the Purchasing attributes and their possible values. You set these attributes when defining or updating items.

PurchasedIndicate whether to purchase and receive an item. Turning this option on allows you to set the Purchasable attribute.PurchasableIndicate whether to order an item on a purchase order. You can set this only when Purchased is turned on. Turning Purchasable off allows you to temporarily restrict the ability to buy.

List PriceEnter the value that Oracle Purchasing uses as the default price on a purchase order,

12

requisition, RFQ, or quotation. Oracle Receivables uses this value as the default unit selling price on a transaction. Note that this is the original inventory item price used by Purchasing and therefore should be used as a guide only.

3.1.3) Order Management Attributes

Following are the Order Management attributes and their possible values. You have to set these attributes when defining or updating items.

Customer OrderedIndicate whether to allow an item to be ordered by external customers. You can add any customer orderable items to price lists in Oracle Order Management. This attribute must be turned off if the BOM Item Type attribute is set to Planning.

13

If you turn this attribute on, you can temporarily exclude an item from being ordered by turning Customer Orders Enabled off. This is an item defining attribute. If you turn this attribute on, the item is automatically assigned to the default category set for the Oracle Order Management functional area.

Customer Orders EnabledIndicate whether an item is currently customer orderable. If you turn this attribute on you can specify the item in the Enter Orders window in Oracle Order Management.You can initially define an item with Customer Ordered Item turned on and Customer Orders Enabled turned off. This means prices can be defined for the item, but no orders can be placed for it.Internal OrderedIndicate whether to allow an item to be ordered on an internal requisition.If you turn this attribute on, you can temporarily exclude an item from being ordered on an internal requisition by turning Internal Orders Enabled off. This is an item defining attribute. If you turn this attribute on, the item is automatically assigned to the default category set for the Oracle Purchasing functional area.Internal Orders EnabledIndicate whether you can currently order an item internally. If you turn this attribute on, you can specify the item on an internal requisition, if Internal Ordered Item is also on.If you turn Internal Ordered Item on, you can temporarily exclude an item from being ordered on an internal requisition by turning this attribute off.ShippableIndicate whether to ship an item to a customer. Shippable items are released by Oracle Shipping Execution’s Pick Release program, creating confirmable shipping lines, and are printed on the pick slip. A warning is issued if you change the value of this attribute when open sales order lines exist.This attribute must be turned off if the BOM Item Type attribute is set to Planning.

OE TransactableIndicate whether demand can be placed for an item by Oracle Order Management, and whether shipment transactions are interfaced to Oracle Inventory. Most items with Shippable turned on also have OE Transactable turned on. For items you do not

14

ship, you may still want OE Transactable turned on if you use the items in forecasting or planning.If you also want to reserve the item, turn Reservable on. A warning is issued if you change the value of this attribute when open sales order lines exist. You cannot turn this attribute off if demand exits.

ReturnableIndicate whether to allow customers to return an item. If an item is returnable, you can enter it on the Returns window in Oracle Order Management. Order Management uses this attribute along with Stockable and Transactable to determine which authorized returned itemsyou can physically receive into inventory.Check ATPSelect Check Material Only, Check Material and Resources, Check Resources Only, or None to indicate whether to check available to promise and/or capable to promise information when placing demand.

ATP RuleEnter a user–defined available to promise rule. ATP rules define supply and demand sources, time–fence parameters, and available–to–promise calculation methods. You can give ATP rules meaningful names, such as ATO ATP Rule.If there is no ATP rule for the item, the organization’s default ATP rule is used.

Default SO Source TypeThis item attribute determines if an item is to be drop–shipped. If the value is internal, the item will not be drop–shipped. If the value is external, the item will be drop–shipped.

15

3.2)Adding Item in the Price List

Following are the steps used to define the cost price for the defined items.Go to ->Order Management Responsibility

->Pricing->Price Lists->Price List SetupQuery for Name:CorporateAdd the defined item in List Lines tab and give the required price in the value column

16

4.FULLFILLMENT METHODS

4.1.SHIP FROM STOCK

You have sufficient inventory items in stock and the order is directly fullfilled from inventory.

➢ SHIP FROM STOCK CYCLE :

18

➢ ORDER ENTRY : In this step we enter the details of the customer and the details of the quotation including the terms and conditions between the supplier and the customer.

➢ ORDER BOOKING: A customer's order is booked in this step. The order can be booked manually or online by the customer.

➢ PICK RELEASE : In this step items are picked from the inventory and shipped to staging sub-inventory.

➢ SHIP CONFIRM:

In this step the items are shipped from the staging sub-inventory to customer shipping location.

➢ AR INVOICE GENERATION:

In this step an invoice is generated for the corresponding sales order made in the order entry.

➢ AR RECEIPT: Receiving the cash from the customer for the corresponding invoice.

19

4.2.MAKE TO ORDER:

Whenever the item is not readily available in the inventory to deliver to the customer then the supplier makes an order for that item which can be manufactured or purchased from other supplier to fulfill the customer's need.

➢ MAKE TO ORDER CYCLE:

➢ ORDER ENTRY : In this step we enter the details of the customer and the details of the quotation including the terms and conditions between the supplier and the customer.

➢ ORDER BOOKING: A customer's order is booked in this step. The order can be booked manually or online by the customer.

20

➢ PROCUREMENT((PO)/WIP JOB):

When the ordered item is not available in the inventory then the supplier makes an order to the manufacturer depending upon the demand and capacity of the manufacturing unit the manufacturing unit can manufacture the item or can purchase the item from other manufacturing unit inorder to fulfill the customer's need.

➢ PICK RELEASE : In this step items are picked from the inventory and shipped to staging sub-inventory.

➢ SHIP CONFIRM:

In this step the items are shipped from the staging sub-inventory to customer shipping location.

➢ AR INVOICE GENERATION:

In this step an invoice is generated for the corresponding sales order made in the order entry.

➢ AR RECEIPT: Receiving the cash from the customer for the corresponding invoice.

21

4.3.CONFIGURE TO ORDER

This order is made on views of the customer to fulfill their needs. Customer is given priority to make his own choice on the item (configuration of the item).

4.3.1.ASSEMBLE TO ORDER: This order is made on the needs of the customer. This order takes time to deliver to the customer. Because the components of the item should be manufactured and assembled so as to fulfill the customer's need.

4.3.2.PICK TO ORDER: This order is also made on the need of the customer. In this order the item ordered by the customer is readily present. Which can be delivered to the customer immediately.

22

4.4.BACK-TO-BACK ORDER CYCLE In this cycle we create purchase order to another supplier for the goods or items which are not available with us.

ORDER ENTRY : In this step we enter the details of the customer and the details of the quotation including the terms and conditions between the supplier and the customer.

ORDER BOOKING : A customer's order is booked in this step. The order can be booked manually or online by the customer.

PURCHASE ORDER CYCLE : Here we create purchase order to another supplier and we collect the items or goods into our storage area.

23

PICK RELEASE: The items present in the storage area are being transferred into the staging area.

SHIP CONFORM: The items are being transferred from staging area to the customer shipping location.

AR INVOICE GENERATION: Goods or items are transferred to the customer along with the invoice.

AR RECEIPT: A Receipt is generated after the customer pays the amount to the supplier.

24

4.5)DROP SHIPMENT

Drop shipment is the process by which an organization takes orders from their customer and gets it fulfilled by a 3rd party. The selling organization places a purchase order to the 3rd party (supplier) who ships the ordered products to the end customer directly.

ORDER ENTRY : In this step we enter the details of the customer and the details of the quotation including the terms and conditions between the supplier and the customer.

ORDER BOOKING: A customer's order is booked in this step. The order can be booked manually or online by the customer.

PURCHASING ORDER: In this step we generate purchase order and after receiving the logical receipt which conforms that the items have been transferred to the customer.

AR INVOICE:AR INVOICE GENERATION: Goods or items are transferred to the customer along with the invoice.

AR RECEIPT: A Receipt is generated after the customer pays the amount to the supplier

25

4.6)IR-ISO: Internal sales orders are those that are ordered from another organization within your own company. The organization that fulfills the order is the selling organization, while the organization with the purchase requisition is the buying organization.

CREATE & APPROVE INTERNAL REQUISITION: In this step we create an internal requisition between two organizations which are under one operating unit.

CREATE INTERNAL ORDER: In this we will run the Create Internal Order Program to create an internal order.

ORDER IMPORT: In this we will run the order import program to create the sales order for the requisition we created in the above step.

PICK RELEASE: In this process we will transfer the items to the

organization staging area.

SHIP CONFIRM: In this process we will transfer the items to the

destination organization.

RECEIVE AGAINST IR: In this process we will receive the items in destination

organization.

26

5.FUNCTIONAL PART OF THE MODULES

5.1)SHIP FROM STOCK:

Case 1: Step-1: ORDER ENTRY & ORDER BOOKING

NAVIGATION : Orders,Returns=>Sales Orders

TO BOOK THE ORDER:

Give The Customer Details in the Order Information. Then Go To The Line Items tab.

27

IN THE LINE DETAILS: Give Your Item Details( Quantity,Price)

Check The Status :ENTERED

Then Save .

Now check the status at header level: ENTERED

Until the status at the header level is ENTERED,You can add the items.

Click on the book order. Then the order will be BOOKED.

28

The Note:Order has been booked

This will show that the order has been booked successfully...

Now check the Status :Awaiting Shipping

Step-2: PICK RELEASE

NAVIGATION : Shipping=>Release Sales Orders=>Release Sales Orders

29

Then Go to Inventory Tab.

30

Then Select Pick From : Sub inventory and Default Stage : Sub inventory

Check whether Auto Allocate is enabled or not.

Go To Shipping Tab:

Check whether Auto create Delivery ,Auto Pick Confirm is enabled or Not.

31

Then perform execute now.

Then check the status at line level in sales order form :Picked

32

Go to Actions=>Additional line information,Click the delivery tab, check the delivery status:Open

by check the both status ,it ensures that items are transferred to the sub inventory and yet to transfer to the customer location.

Step3: SHIP CONFIRM : NAVIGATION: Shipping=>Transactions

33

Give the order number to find the transaction details

Check the line status and next step to do.

34

Then check the deliver lines and click on ship confirm

Then check the Sales Order status :Picked

Then Go to additional line information and check the delivery lines ,so that to verify all quantity is successfully delivered or not.

35

Step4:WORK FLOW BACKGROUND ENGINEsetup=>work flow back ground engineThen run the work flow back ground engine.

Then check the status of your sales order:Closed

36

Then Go to Additional line information:check the Invoice/credit Memos

This is the invoice generated against the sales order

37

Case 2:Now in this case, we will disables the auto allocate flag while doing the Pick release activityGenerate a sales order

38

Then pick release the item, now check that the auto allocate flag is disabled.

In this case a move order has been generated , but the items are not allocated and not transferred to sub inventory, give the sales order number and order type,order source and click on Find ,to get the move order details

39

Here check the allocate button is enabled which means the items yet to be allocated,then click on the allocate to allocate the items.

Now items are allocated ,Then click on view/update allocations to check the allocation detailsand click on lot/serial to check the which items are allocated(the serial numbers)

Now check the status in sales order form,it will be Picked,after that do the

40

Ship Confirm, The Work Flow Background Engine activities as shown in the above example.

Case 3:In this case ,we disables the auto pick confirm field and enables auto allocate field.

Generate a sales order

Then do pick release activity, Check that the auto allocate field is enabled and auto pick confirm field disabled

41

Check the status should be:Awaiting Shipping ,in Sales Order form because here the move order is generated and

Items are allocated but the items are not transferred to the sub inventory

Then Go to move orders =>transact move orders to find the move order details

42

Check the allocate button is disabled ,it means the items are allocated and transact button is enabled which means the items are yet to be Transferred.

Click on view/update allocations to check the allocation details and click on lot/serial to check the items allocated( along with their serial numbers)

43

By checking the start serial number and end serial number , check the items allocated and their Serial Numbers also

Pick the item having different serial number by editing the start serial number fieldafter this transact the items and do the remaining Ship confirm and run the Work Flow Background Engine as shown in the first example..

44

5.2)BACK-TO-BACK ORDER:

Before using item in sales order , we have to ensure some item attributes at Master item level.

At General tab,Make sure that ( Make or Buy) attribute is set to "Buy"

And also Make sure that "Internal Ordered" and "Assemble to Order" attributes are enabled at Order Management Tab.

45

To create Back To Back Cycle,first of all we need to create one Sales Order.For that the navigation is:

Orders,Returns--->Sales Orders

Enter the customer number.

46

After giving the customer number ,go to "line Items" .Here you have to give the item details.

Press Crt+s , now the line_status will change to "Entered" Then press "Book Order" button. Sales order line_status is changed to "Supply Eligible". Note down Sales Order number for futher reference

47

Go to "Action" button and select Progress Order-> Create Supply then click "ok"

Now the line_status will change to "PO-ReqRequested"

After this we need to do Purchase release. For that the navigation is:

Order,Returns--->Purchase Release In this screen we have to enter the sales order number twice, as shown below.

48

Click "Ok" button and click on "submit" button .

Here It runs the Background Program which will gather information from OM module tables into interface table.

After this process,we need to do Requisition Import. For that the navigation is: Orders,Returns--->Requisition Import

49

Click the "submit" button. Here it imports sales order information from interface table to Purchase Module tables.

Here it will generate Requisition number to know that number we need to change responsibility to "Purchasing,Vision operations(USA) . For that the navigation is:

Requisitions--->Requisition Summary There we need to enter our sales order item name then only we will get requisition number for our sales order item.

50

Click on "Find" button

We need to check the status of sales order item.For that we need to enter sales order number .Then we find changed status of sales order item . Now the status is "PO-Req Created.”

After this process we need to generate one purchase order number for our sales order item by using auto create.For that we need to chage the responsibility to "Purchasung,Vision Operations(USA)".The navigation is:

51

Purchase Orders--->Auto create

Now, Enter Your Requisition Number. Then Click on "Find" Button.

Here we have to click on "Manual" Button.

Enter the "Supplier Name" and then click on "Create" Button.

52

Click on "Add To Document" Button and in "Document Builder" click on "Create " Button.

After this it will generate the "Po,Rev" number.It navigates to PO form which is in incomplete status. Click "Approve" button for status "Approved"

53

Generate Receipt for purchase order.

54

Navigation: Receiving--->Receipts Change the organization to "M1"

Enter Purchase Order Number:4997 and click "Find" Button

55

Click on "Lot-Serial" button and provide lot serial number and click on "Done" button

Check status at sales order line in OM responsibility Status changed to "Awaiting Shipping"

56

For Pick release, Navigation :

Shipping--->Release Sales Orders---> Release Sales Orders Provide Sales Order number

In Inventory tab, Enter warehouse as "M1" and set Auto Allocate status to "Yes" Click on "Execute Now" button

57

Now check the Status at Sales order line changed to "Picked".

58

For Ship Confirm, Navigation : Shipping--->Transactions Enter Sales Order Number and Click on "Find" button

Go to "Delivery" tab and click on "Ship Confirm"

59

Check the Status at sales order line changed to "Shipped".

Run The Program : Work Flow Background EngineNavigation : Inventory-> Work Flow Background Engine Purpose : Invoice Generation

60

Check the status at sales order line changed to "Closed"

To view Invoice Details,Go to "Actions" button and select "Additional line Information" It will navigate to below screen

In below screen, select "Invoices/Credit Memos" tab . click on "Invoice Details" buttonHere we can view Invoice Details of our sales order

61

5.3)DROP SHIPMENT:

Step-1: ORDER ENTRY & ORDER BOOKING

➢ NAVIGATION : Responsibility : Order management super user,vision operations(USA) Orders,returns => Sales orders

Here we have to enter the Customer Details ( For Example give the customer no as 1143 and press tab)

➢ Go to the Line Items tab and enter the Item , Quantity , Price . Then save .

63

➢ Go to Shipping Tab enter the value in source type field as <External> ( As the supplier will not ship the product we have to give the source as external )

Save the form Click on 'Book Order' Button Then check the status at status field in main tab it should be booked

64

Step-2 : RUN THE PROGRAM : WORK FLOW BACKGROUND ENGINE

➢ Navigation : Inventory-> Work Flow Background Engine In Parameters window give values as specified below... Item type : OM Order Line Process Deferred : Yes Process Timeout : No Then Click on Ok button

65

➢ Now Check the Line status in Sales Order Form : Awaiting Receipt

66

Step-3 : PURCHASING

➢ Creating purchasing requisitiona) Run the program : Purchase Release

Navigation : Orders,Returns → Purchase Release In Parameters window give values as specified below... Order Number Low : Give your sales order number Order Number High :Give your sales order number Then click on Submit (view-> requests->find->refresh ).

Reason for running this program :

The Purchase Release concurrent program processes eligible lines with a source type of External and passes information to Oracle Purchasing(PO Interface Table ) .

b) Run the program : Requisition Import

67

Navigation : Orders,Returns → Requisition Import Don't give any parameters in the parameters window

Click on OK-> Submit. (view->request->find->refresh)

Now the Requisition is created for the Sales Order . Lines Status will not be changed in the Sales Orders Form

(C) You can find the requisition number generated for the requisition at below mentioned navigation

Navigation : orders,returns-> sales orders query for your sales order number , then go to line items tab click on Actions button ->Additional Line Information ->OK->go to 'Drop Ship' tab here note the requisition number available at Number Field .

68

➢ Creating purchase order using 'PO requisition'

Navigation : Purchasing->Auto Create->give requisition number ->click on find button.

69

Check the check box ->click on automatic button ->provide supplier name and supplier site details ->click on create button.

70

Then it is navigated to below shown screen.......

Check the details and click on Approve button .

Click on OK .

Note the PO number generated here .

71

➢ Logical Receipt

Purchasing->Receiving->Receipts

Give the Purchase Order number → click on Find button.

Check the check box beside Quantity field-> Give field value as 'Drop Ship' for the field Sub-Inventory->click on Lot-Serial button

72

Give any value at Start Serial Number field + Tab → click on Done button.

Now check the status at line items of sales order : Shipped.

73

Step-4: AR INVOICE GENERATION

Run The Program : Work Flow Background EngineNavigation : Inventory-> Work Flow Background Engine Purpose : Invoice GenerationGive the parameters Item Type: OM Order Line Process Deferred :Yes Process Timeout : NoThen Click Ok.

Check the Line status in Sales Order Form : Closed.

74

Click on Actions → select 'Additional Line Information '→ go to 'Invoices/Credit Memos.

“ Here the invoice number gets generated for the PO at Number field.”

75

5.4)IR-ISO: STEP 1) : Create an internal requisition in M2 organization

➢ Path : Responsibility : Purchasing Change Organization => M2 Requisitions => Requisitions

76

In Requisition In Header part make sure that Type is Internal Requisitions Type : Internal Requisitions In Lines Enter the Item , Quantity , Need-by-date for ex: Item : Test_Dell_Desktop

Give destination Organization as M2 and location as M2-Boston Give source Organization as M1

In Distributions enter the value for Charge Account Save it and Click on Approve then note down the Requisition number

77

➢ Check whether the Requisition has been approved or not Path : Requisitions = > Requisition Summary

Enter the Requisition Number and check the status whether it has been Approved or not ..

If not then make sure that it has been Approved.

Step 2) To Create an Internal Order from requisition

➢ Run Create Internal Orders Program to generate Internal Order for that requisition.

Path : Requests => Submit New Request => Single Request Name : Create Internal Orders Then click on Submit

78

➢ Switch to Order Management Responsibility Run Order Import Program Path : Orders ,Returns => Import Orders => Order Import Request Order Source : Internal Order Reference : Give your requisition number Then Click on Ok and then submit

80

➢ Run the Order Organizer Program Path: Order .Returns => Order Organizer

Order Source : Internal Requisition number : Give your requisition number Click on Find We will get the Sales Order number ,which was generated from the created internal requisitions.

81

Step3 ) Check the sales order status... it should be Awaiting Shipment

➢ Path : Orders ,Returns =>Sales Orders Query your sales order by giving the sales order number..

83

Step 4 ) Now Items should be transferred from manufacturing Sub-Inventory to Staging sub-inventory

➢ Path : Shipping =>Release Sales Orders =>Release Sales Orders

In Order tab give Sales Order Number

84

In Inventory tab give the warehouse as M1

Then click on Execute Now

➢ Now the Status should be as PICKED in the sales order form

85

Step 5) Now we should ship the item to the requested organization (M2)

➢ Path : Shipping => Transactions Enter your Sales Order Number in Form Order Number Field and then click on find

86

➢ Now click on 1. Delivery 2. Ship Confirm3. Ok

87

➢ Now the line status should be as Shipped in the Sales Order Form

➢ Now run the Work Flow Background Engine Path : Inventory =>Work Flow Background Engine Give Parameters as : Item Type : OM Order Line Process Deferred : Yes Process Time Out : No

Then click on Ok

88

➢ Now the Line Status Should be as CLOSED in the Sales Order Form

Step 6) Now we have to receive the items into M2 organization ➢ Change Organization to M2

89

➢ Now Receive the Item Path : Inventory=>Transactions=>Receiving=>Receipts Enter your Requisition Number In Requisition field

➢ Check the Check box , then Save

90

➢ Now Receive the item into the Sub inventory Path :

Inventory=>Transactions=>Receiving=>Receiving Transactions Give the Requisition Number

➢ Check the Check box and save........

91

Step 7) Check in Onhand Quantity for the corresponding item

Path : On Hand Availability => Onhand Quantity

92

6.TRADING COMMITTEE ARCHITECTURE(TCA):

Oracle Trading Community Architecture (TCA) is a data model that allows you to manage complex information about the parties, or customers, who belong to our commercial community, including organizations, locations, and the network of hierarchical relationships among them. This information is maintained in the TCA Registry, which is the single source of trading community information for Oracle E-Business Suite applications. These applications, as well as TCA itself, provide user interfaces, batch data entry functionality, and other features for you to view, create, and update Registry information.

TCA is an architecture and a model..not a module

TRADING COMMUNITY USAGE WITHIN ORDER

MANAGEMENT:

In general, previous releases of Order Applications and initial releases of Oracle CRM products utilized the Oracle Receivables Customer Model for storing and retrieving customer information.With release 11i, a new way of internally modeling customers and customer details was introduced; Oracle’s Trading Community model. Oracle’s Trading Community customer model is a powerful customer architectural design building on the Receivables Customer model, enabling users to now define and maintain customer hierarchies and relationships between customers and sites. If a CRM or ERP application maintains customer information, the application is using the Trading Community customer model.

Trading Community enables you to:➢ Separate entities you enter into a relationship with from the business

relationship itself.➢ Provide a common location entity that can be shared, enabling greater

optimization for distributed planning.➢ Maintain businesses and people as different entity types.➢ Enables multiple customer relationships to be established for one common

entity.

93

TERMINOLOGY

➢ TRADING COMMUNITY

• PARTY - This is a generic term for any entity which can have any type of relationship with your company.

The three primary party types are:• PERSON - This party type is typically used when you are creating an entity

that operates within a business to customer environment.• Organization - This party type is typically used when you are creating an

entity that operates within a business to business environment.

• PARTY RELATIONSHIP - This party type represents a binary relationship between two parties such as a partnership. Party relationship types can be seeded or user-defined. A party relationship is optionally a party itself, meaning certain party relationships can enter into relationships themselves (currently not supported within Order Management).

• PARTY SITE - Part Site represents the link between a party and a location (a valid location for the party. Typically, your organizational hierarchy is used when modeling using party relationships.

• ACCOUNT - An account represents a relationship between your company and a party in the Trading Community model who is your customer. Accounts contain the attributes of the selling relationship between your organization and a party. Account attributes do not describe a party; they only exist when a selling relationship is present between the your organization and a party. The information which is used for processing orders and receivables transactions is part of the account information.

• ACCOUNT SITE - a party site address that is used within the context of an account.

94

• ACCOUNT SITE USAGE - an account site created for specific usage; for example,

billing or shipping purposes.

MAPPING ORDER MANAGEMENT TERMINOLOGY TO TRADING COMMUNITY TERMINOLOGY

➢ Customer Site, Customer Location, Customer Address - These terms, within Order Management equate to Trading Community Account Sites.

➢ Bill To, Ship To, Deliver To - These terms, within Order Management, equate to Trading Community Account Sites Usages. Within Order Management, each account belongs to a party. These parties may have additional relationships and details defined, but Order Management currently only utilizes a limited subset of the party data (accounts, addresses, and sites usages). The Trading Community model includes all the information which was previously stored in the Receivables customer model. This includes information such as:

➢ Customers➢ Customer addresses and site uses➢ Profile amounts➢ Customer relationships.

In order to maintain backward compatibility for the Oracle Receivables customer model, Order Management currently accesses data stored in Trading Community database tables via Order Management database views. Future development projects are in progress to update Order Management applications code to retrieve Trading Community details directly from Trading Community base tables rather than utilizing OrderManagement views.As OrderManagement adds new features and additional functionality to its core application, users will begin to see Trading Community terminology incorporated into Order Management Forms (windows), Reports, Concurrent Programs, and product documentation. Until these project are completed, Order Management forms will continue to use names of entities as they existed in the Receivables customer database tables. The following table provides a mapping of these field names.

esens the link between a party and a location (a valid

95

TCA STRUCTURE

DIFFERENCE BETWEEN PARTY AND CUSTOMER:

Marketing is the process of identifying, creating and retaining a customer. CRM tools essentially deal with that process. It is used by companies to identify potential customers, make them buy something from the company, maintain effective relationships with them to retain them for repeat purchases as well. This is what CRM does.

96

But an ERP like oracle does not have any relationship with a person unless he buys something from the company. A customer is someone who has a buying relationship with the company. So how do we distinguish between a person who has bought something and someone who hasnt purchased anything from you? This is where the party definition comes into picture. A party is anybody that exists. He/She/It does not have to have bought something from the company earlier. In fact, they do not have any relationship whatsoever with the company. So how does the company make them buy something? This is where CRM helps. It helps the company in identifying such people, create some marketing campaigns to make them buy something and convert them into the company’s customers, and keep maintaining relationships with them so that they will keep buying from them in the future as well.

Oracle purchased SIEBEL CRM to target these companies which require CRM tools to create, maintain and retain new customers. Prior to 11i, Oracle had the customer tables only. It did not have to deal with non-customers. Anyone who purchases becomes a customer and is stored in the AR customer tables. When Oracle bought CRM, it needed to incorporate the concept of a ‘potential” and “repeat” customer into the existing data model. It could not have had separate schemas or databases for CRM tools and ERP tools. Since CRM and ERP have to talk to each other, they wanted one single model to incorporate customers who bought and people who have not purchased. So they created a layer over the customer definition called party and said “Anyone who exists is a party”. Once this party buys something, it becomes a customer. Kindly note that it is still a party. It is both a party and customer as well after the purchase is made. So for a person to become a customer, he has to exist first. Only then he can make the purchase and become a customer.

KEY FEATURES OF TCA:

➢ Provides a foundation for a single source for customer information.

➢ Ability to represent all business entities as a “Party” (organizations, people, groups, relationships) and to handle them the same way. This approach provides flexibility to accommodate all B2B, B2C and hybrid models in the same repository.

➢ Many-to-many relationships between Parties and Locations, that allows for less duplication and easier updating.

97

➢ Capability for advanced relationship modeling between entities within the trading community. Any party can figure in any number of Party Relationships even within matrix hierarchies (relationship networks).

➢ Ability to setup and maintain any number of party classifications which can be used for reporting and assignment purposes.

➢ Extensible data model to enable various business data requirements.

➢ In reality , three entities Drive in the TCA model , which are Party, Account, and Relationships.

PARTIES VS ACCOUNTS

➢ Parties represent person or organizations who may,or may not have purchased from the implementing organization.

➢ Accounts should be created once a party makes a purchase or establishes a financial agreement.

➢ The combination of a party and its account(s) is considered a customer.

➢ The party layer captures intrinsic truths about a person or organization.

➢ The Account layer captures the detail describing the party's finacial relationship with the implementing organization.

➢ The account layer cannot exist without the party layer.

➢ ACCOUNT-CONCEPT:

The financial roll_up point to track the monetary portion of a customer's purchases and payments. Stores details about a customer relationship between a party and your business.

A party may have one or more customer accounts.

➢ ACCOUNT ROLE

98

The relationship that a party has in regard to controlling or using an account.

➢ CUSTOMER ACCOUNT SITES

A customer account site is a party site that is used within the context of a customer account(e.g.,for billing or shipping purpose).

➢ CUSTOMER ACCOUNT CONTACTS

Acustomer account contact is a party contact that is used in the context of a customer account

A Ting AaCommunity ArchitectureCA is an Architecture and a Model…Not a module

ACCOUNT LAYER-COMPONENTS

➢ ACCOUNT: The attributes of the implementing organization's financial relationship with a party,cannot exist without a party.

➢ ACCOUNT SITE: A party site that is used within the context of an account.

➢ ACCOUNT SITE USE: Use of an account site(e.g.billing,shipping)

➢ ACCOUNTING RELATIONSHIPS: Established between accounts to allow sharing of billing,shipping,and pricing information

99

BENEFITS OF TCA:

➢ Single source for customer data across.

➢ Model all kinds of relationships and mixed models.

➢ Relationships:any type,any number,matrix,hierarchical and non-hierarchical.

➢ Process all business entites the same way:Organizations,People,Groups,Relationships.

➢ Multiple business relationships for each party.

100

➢ Each data is defined only once-Avoid multiple updates.

➢ Support current and historical relationships.

➢ Support complex,multi-tiered,multi-org relationships that are found in the real world.

LIMITATIONS AND COMPLICATIONS:

➢ Old customer model

➢ Data duplications

➢ Multiple sites

➢ Multiple parties

➢ Complex party relationships

101

7. DEFAULTING RULES 7.1)CREATING CUSTOMER SPECIFIC DEFAULT

RULES:

To create customer's with some fields as default fields,first move into ORDER MANAGEMENT responsibility and then follow the steps given below,

1. Navigate to Customers -> Standard

Enter a new customer name in the Name field, and press Find. Press the 'New' button when you get the below decision window. If the customer name already exists, go back and enter a name that does not exists.

2.In the Addresses tab, click on New.

3. Enter the following information in the Customer Addresses screen.Address : Enter the required fields (they will appear in yellow).<Business Purposes tab>Usage = Bill To :Usage = Ship To :

102

Select the Bill to Location created above from the LOV. Save.

4. Notice the 'Open' button in the screen shot above. This is where you can enter additional details specific to the business purpose. So, if the cursor is on the 'Ship To' row as seen here, clicking on Open will allow to enter information specific to the Ship To Location. This can be examined further in the Defaulting Rules section.

Defaulting rules determine the values that you want to get defaulted into a sales order to reduce the amount of information you need to enter manually.

In this test flow, however, we will only look at an existing seeded defaulting rule for the field Order Type. Based on that, we will set up a default value for the Order Type at the customer's Invoice To location level.

103

1. Navigate to Setup -->> Rules -->> Defaulting.

-press f11 key(enter into query mode) and then query for

Application: Order Management

Entity : Order Header and then press ctrl + f11.

In the Attributes section place the cursor on the Order Type Attribute and then click on the Defaulting Rules Button.

104

from default sourcing rules that the first preference for the Order Type when entering it in a sales order is given to the Invoice To i.e.. Bill To level and then at Ship To level and then finally at the Customer level.

For attribute as ship to:

105

For attribute as bill to:

For attribute type as warehouse:

106

8.TECHNICAL OF O.M

----------------------------------------Entered

oe_order_headers_all 1 record created in header table

oe_order_lines_all Lines for particular records

oe_order_holds_all If any hold applied for order like credit check etc.----------------------------------------------

Bookedoe_order_headers_all Booked_flag=Y Order booked.

wsh_delivery_details Released_status Ready to release--------------------------------------------------Pick Released

wsh_delivery_details Released_status=Y Released to Warehouse

wsh_new_deliveries if Auto-Create is Yes then data populated.

wsh_delivery_assignments deliveries get assigned---------------------------------------------------------Pick Confirmed

wsh_delivery_details Released_status=Y Hard Reservations. Picked the stock. Physical movement of stock-----------------------------------------------------------Ship Confirmed

wsh_delivery_details Released_status=C Y To C:Shipped -------------------------------------------------------------------Autoinvoice

wsh_delivery_details Released_status=I Need to run workflow background process.ra_interface_lines_all Data will be populated after wkfw process.

107

ra_customer_trx_all After running Autoinvoice Master Program forra_customer_trx_lines_all specific batch transaction tables get populated

Price Detailsqp_list_headers_b To Get Item Price Details.qp_list_lines

Items On Hand Qtymtl_onhand_quantities TO check On Hand Qty Items.

Payment Termsra_terms Payment terms

Customer Informationhz_parties Get Customer information include name,contacts,Address and Phonehz_party_siteshz_locationshz_cust_accountshz_cust_account_sites_allhz_cust_site_uses_allra_customers

108

FINAL OM2

Documents

Transcript of FINAL OM2