DEFINE TRANSACTION TYPES Define Sales Order Line Type The Enter - Line sub process verifies that lines on an order are booked before Proceeding with the line flow. Nag:- Setup↔Transactiontypes↔Define
Enter Operating Unit Transaction Type Sales document type: Sales Order Order Category : Order Transaction Type code: Line DefineTransactionOrder Oracle Order Management includes the concept of an order header. A header can contain one or many lines. The OM Order Header item type identifies all Oracle Order Management order header process available. Nag:- Setup↔Transactiontypes↔Define
Enter Operating Unit Transaction Type Sales document type: Sales Order Order Category : Mixed Transaction Type code: Order Fulfillment Flow: Order flow – Generic Order flow – Generic: The Order Flow - Generic workflow process is the most often used workflow in Oracle Order Management. The Order Flow - Generic process contains sub processes to verify that an order is booked and closed properly. Order Flow - Generic is initiated if it is assigned to the transaction type for the Order. Transaction types determine which processes are attached to an order.
Attached line type to your Order
Go to Assign Line flows:
Select line Type what you define in your order line type. Line Flow- Generic: The Line Flow - Generic process is a workflow process that is initiated when you save a sales order line in Oracle Order Management. The Line - Flow Generic process contains several sub processes to ensure that an order line is properly entered, scheduled, created, invoiced, fulfilled, shipped, and closed. If you use several different line flows in your business, the Line Flow - Generic workflow can act as a default; it initiates when no other flow is determined necessary for a line. When you save an order line in Oracle Order Management, the process verifies that the order is booked before proceeding. Once booking is verified, the process continues with scheduling, supply creation, invoicing, fulfillment, shipping and closing. Several of these actions are performed in the following workflow subprocesses contained in Line Flow – Generic.
Then Click Validate Workflow
Go to Shipping Tab
Enter your Warehouse name Shipment Priority Shipping Method Auto schedule: Cheak this box automatically created schedules your shipment lines. Fulfillment Set: 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. Line Set: Order Management allows for the creation and usage of Line Sets based upon common order line attributes. Ship sets ensure that at the time of ship confirm, all lines within the set are picked and shipped together, and not individually. With Oracle Order Management, the concept of creating sets for shipment has been expanded to include additional set functionality based upon ship, arrival and fulfillment. In general, grouping order lines within sets.
Go to Finance Tab
Invoicing Rule: This Rule is used for how to recognize the Receivables at the time of invoice Importing. Accounting Rule: when you recognized the receivables how to allocate revenue each and every period. Source: An imported transaction source means that transactions were automatically entered from a file or another accounting system using Auto Invoice. Receivables Transaction type: Invoice Enter tax event Cost of goods sold A/C then save information and close.
Define Shipping Parameters: You define the default values for basic shipping information such as units of measurement, pick release rules, weight and volume calculations, and delivery grouping rules. Shipping parameters are organization specific. The parameters are arranged into the following tabbed regions in the Shipping Parameters window. Nag: Setup↔Shipping↔Shipping Parameters
GENERAL TAB: You define weight and volume unit of measure (UOM) class parameters and select the criteria for percent fill basis calculations. The unit of measure classes are used to restrict the UOMs for weight and volume to include only those UOMs defined under the selected class. Select the default Weight UOM Class from the valid UOM classes. Select the Volume UOM Class from the valid UOM classes.
PICK RELEASE TAB: Pick Release finds and releases eligible delivery lines that meet the release criteria, and creates move orders. You can pick release by order, trip, stop, container, delivery, warehouse, and customer, scheduled, or requested dates, shipment priority or combinations of the above criteria. The default release criteria is set up in Shipping Parameters, but you can override the default criteria in the Release Sales Order window at pick release. The process of transacting move orders creates a reservation, determine the inventory source subinventory. Pick Slips can be created after the detailing process completes, and the quantity and source can be manually verified at pick confirm. Detailing and pick confirmation can be manually transacted through Oracle Inventory or set up in Shipping Parameters to occur automatically at pick release. You can run one or more releases and customize release criteria to meet your requirements. Release Rules to specify your picking criteria and set the default Release Rule through Shipping Parameters Pick Release tab. Release Sequence Rules to specify the order in which eligible delivery lines are allocated during pick release. Pick Slip Grouping Rules to determine how released move order lines are grouped onto pick slips.
Release Sequence Rule: You can define release sequence rules to specify the order in which eligible picking lines are allocated to Inventory during pick release. You can release the picking lines. •
Order number
•
Outstanding Invoice Value
•
Scheduled Date
•
Departure Date
•
Shipment Priority
You can assign a priority level to one or more attributes with 1 being the highest priority and 5 being the lowest. You can also define whether you want the picking lines released in ascending or descending order. Nag: Setup↔Shipping↔Pickking↔Release Sequence Rule
Example: if you select the Ascending button for Order, picking lines are released by ascending order number--Order 1 is released first, then Order 2, Order 3, and so on. If the Descending button is selected, the picking lines are released by descending Order number from highest to lowest--Order 4 is released first, then Order 3, Order 2, and Order 1.
Note: You can define either the Outstanding Invoice Value attribute or the Order attribute for the Release Sequence Rule, but you cannot select both for the same rule. No two attributes can be given the same priority. You can edit existing release sequence rules, but you cannot change the name of an existing release sequence rule. Pick Slip Grouping Rule: You can create grouping rules to organize how picking lines for released sales orders and manufacturing tasks are grouped on pick slips. For example, if you select Delivery as a grouping criteria, all picking lines for the same delivery are grouped together on a pick slip. Nag: Setup↔Shipping↔Pickking↔Pick Slip Grouping rule
Order Number: Items assigned to this order number are assigned to the same pick slip number. Customer: Orders for this customer are assigned to the same pick slip number. Ship To: Orders addressed to the ship to address are assigned to the same pick slip number. Carrier: Orders for a particular freight carrier are assigned the same pick slip number. Trip Stop: Orders within a shipping group of deliveries are assigned to the same pick slip number. Delivery: Orders within a particular delivery are assigned to the same pick slip number.
Shipment Priority: Orders with the same shipment priority are assigned to the same pick slip number. Source Subinventory: Items with the same source subinventory are assigned to the same pick slip number. Source Locator: Items with the same source locator are assigned to the same pick slip number. Item: Items with the same part number are assigned to the same pick slip number. Revision: Items with the same revision number are assigned to the same pick slip number. Job / Schedule: All tasks you create for a job or schedule are assigned the same pick slip number. Department: All tasks from the same department are assigned the same task type regardless of whether or not you select Job / Schedule. Push versus Pull: All push tasks are assigned the same pick slip number, and all pull tasks are assigned the same pick slip number regardless of whether or not you select Job / Schedule. Supply Subinventory: All tasks that have the same destination subinventory are assigned the same pick slip number. Shipping Documents Set: Nag: Setup↔Shipping↔Pickking↔Documentset↔shipping document set You can define default picking criteria that is used at pick release. You can also select the default settings for auto-detailing and auto-creating deliveries.
All Pick Release documents: You can set the default Pick Release Document Set in the Pick Release tab of the Shipping Parameters window Enter your Default sub inventory Auto create Deliveries: Select the Autocreate Deliveries option to specify your preference for delivery creation. You can override this preference at pick release execution. If you are selected: Pick release automatically creates deliveries based on the Delivery Grouping Rules and assigns delivery lines to them. When pick releasing, the Autocreate Deliveries check box in the pick release form defaults to this parameter setting if you enter a warehouse. If you do not enter a warehouse, pick release uses this parameter setting from the organization of the warehouse on each sales order line. If you are not selected: Pick release does not automatically create deliveries. Auto Allacate: Select the Auto Allocate option to specify how you want order lines allocated. Selected: Pick release creates move orders and allocates them. Cleared: Pick release creates move orders. You must manually allocate the order lines using the Inventory Transact Move Orders window.
SHIPPING TRANSACTION TAB You can define parameters for your shipping transactions such as default ship confirm document set, ship confirm rule, auto-pack options, goods dispatched account and whether to enforce packing into containers.
Ship Confirm Document Set You can group related shipping documents and other reports in a set that can be printed at pick release or ship confirm. You can include a variety of shipping documents in a set such as a Bill of Lading and Packing Slip Report and determine the print sequence. Shipping Execution provides three pre-defined (seeded) document sets. Nag: Setup↔Shipping↔Pickking↔Documentset↔shipping document set
Ship Confirm documents: You can set the default in the Document Set field of the ship confirm window. You can create additional document sets based on your business needs. Ship Confirm Rule Automated Ship Confirm enables you to automatically ship confirm all deliveries that have all lines at status of staged. Automated Ship Confirm can be executed as a concurrent program (set to run at specific intervals) or it can be launched manually. Each method of executing Automated Ship Confirm has its advantages. You can utilize either or both processes depending on your business needs. Concurrent Submission: If you use a Ship Confirm Rule within the Ship Confirm SRS program and schedule this concurrent program to run periodically, you will not have to manually ship confirm each delivery. It is designed to support delivery selection based on range of parameters. Ad Hoc (or one-time) Submission: Submitting the Ship Confirm SRS program on an ad hoc basis enables you to control when each ship confirm process will be executed by invoking the process manually. You can disable Automated Ship Confirm for any delivery by utilizing the Enable Auto Ship Confirm flag at the Delivery tab. If the check box is selected, the delivery will be considered for Automated Ship Confirm. If it is not selected the delivery will not be considered. You can view the deliveries included in an Automated Ship Confirm batch by utilizing the Query Manager Window to search for Deliveries. In the Ship Confirm Batch field, find the batch number in the list of values.
Nag: Setup↔Shipping↔Ship Confirm Rule
Auto Pack Option: Select your Auto pack Options. From the list of values, select either No, Yes, or Autopack Master. No: Autopack will not be enabled Yes: Auto pack will be enabled and delivery line items will be systematically packed into LPNs based on container-item relationships.
DELIVERY TAB
Delivery parameters enable you to define how to group delivery lines for a delivery. The mandatory default attributes are Ship from Location and Ship to Location; however, you can select additional optional grouping parameters that include: •
Customer
•
Freight Terms
•
FOB Code
•
Intermediate Ship To location
•
Ship Method
The delivery attributes determine how delivery lines are grouped into deliveries when auto-creating deliveries. For example, if the grouping attribute Customer is selected, the delivery lines are grouped into deliveries by customer: for example, deliveries for Customer A are grouped into Delivery A, deliveries for Customer B are grouped into Delivery B. You can select more than one grouping attribute to refine your grouping criteria further: for example, if you select Customer and Ship Method as grouping criteria, delivery lines with the same customer and carrier criteria are grouped into deliveries.
If each optional grouping attribute is checked, the delivery's corresponding field cannot be updated if delivery lines are assigned to the delivery. This ensures that the delivery lines' grouping criteria is not broken by a different attribute value: for example, if someone tries to select a different ship method. If each optional grouping attribute is unchecked, its field in the delivery record can be updated until the ship confirm stage. For example, if you want to change the Ship Method in the delivery and do not need to enforce it as a grouping attribute, you can unselect Ship Method. Do not change these options if you have deliveries that are not ship confirmed.
DOCUMENT SEQUENCE: Name a new document sequence and define how the sequence numbers each document. Nag: Setup↔Documents↔Define
Name: Once entered, sequence names cannot be changed. Application: Once selected, the application associated with your sequence cannot be changed. Type: Once defined, you cannot change the type of document numbering sequence. Automatic Sequentially assigns, by date and time of creation, a unique number to each document as it is generated. Manual Manual numbering requires a user to assign a number to each document before it is generated. You must enter unique values. However, please note that numerical ordering and completeness is not enforced. Message: Check the Message check box if you want each document to display a message (in the message line near the bottom of the screen) informing the user of the sequence name and value. This check box only applies to sequences with the automatic type of numbering. Messages appear only on form displays, and are not written to a request's log file.
Initial Value: Enter a value for the first document in your sequence. This field only applies to sequences with automatic or gapless numbering type. If you leave this field blank, the first document is automatically assigned a value of "1". ASSIGN DOCUMENT: Define which documents a document sequence can number, and then assign the document sequence to your definition. Nag: Setup↔Documents↔Define
Specify documents by the application that generates them and the category of the document (table where the documents are stored). You can also include in your document definition the set of books they affect, and the method by which the document is entered. Once a document definition is entered, you select a sequence to assign it to, and if you wish, enter effective dates for the assignment. There can only be one active sequence assigned to each unique combination of Application, Category, Set of Books, and Method. The last two criterions are optional, and are set in the Document Flexfield. However, the same sequence, the same numbering scheme, and initial value can be assigned to more than one combination of Application, Category, Set of Books, and Method as long as the Application and Category remain the same.
Application Select the application that generates the documents you wish to number. For example, to number sales invoices, you select Oracle Receivables. Category Select a document category to identify a logical subset of documents. For example, if you do not want to number all invoices in Oracle Receivables, you can choose to number only the category of sales invoices. Set of Books Select the chart of accounts for your business that is affected by the documents you wish to number. Method Select the method that your documents are entered, automatic or manual. Automatic is when a concurrent process (e.g., an external program) enters transaction data into an Oracle Application, which generates documents. Null: Null means you can use both Automatic & Manual. Go to Assignment Tab
Start Date/End Date Enter the dates on which the sequence assignment to your document definition takes effect/is no longer enabled. The Start Date field automatically defaults to the current date, and once a sequence assignment is defined, the start date cannot be changed. If you leave the End Date field blank, your sequence assignment does not expire; and if you enter an end date and define your sequence assignment, the end date cannot be modified later.
If there is no end date defined and there are no active assignments for a sequence, you can disable the sequence assignment by entering the current date as the end date. Once disabled, a sequence assignment cannot be reactivated. Sequence Select a sequence to assign to your document definition. The sequence's application and the document's application must be the same. Once you define a sequence assignment, the sequence name cannot be updated later. If you want to disable the sequence assignment and assign a new sequence to the document definition (Document Flexfield combination), you must first, enter an End Date to disable the current sequence assignment, then, second, create a new record (row) for the new assignment. PRICE LIST Price lists are essential to ordering products because each item entered on an order must have a price. Each price list contains basic list information and one or more pricing lines that define item and/or item category prices. Basic information includes the price list name, effective dates, currency, pricing controls, and shipping defaults such as freight terms and freight carrier. For a price list, you can define price breaks, pricing attributes, qualifiers, and secondary price lists. Nag: Pricing ↔Price Lists↔Price List setup
Note: You can only view or update a price list for your pricing transaction entity. The profile QP: Pricing Transaction Entity must match the pricing transaction entity of the price list. You can only view or update a price list in your source system. The profile QP: Source System Code must match the source system of The price list. Otherwise, the price list is view-only. The profile option QP: Selling Price Rounding Options affects the rounding of adjustments. For more information on this and other profile options, Oracle Advanced Pricing Implementation. Go to Secondary Price List tab The pricing engine uses secondary price lists when it cannot determine the price for an item using the price list assigned to an order. Primary and secondary price lists have the same currency.
Note: You can only add a secondary price list one you enter the currency for the primary price list. This ensures that the secondary price list has the same currency as the primary price list. If the item you are ordering is not in the primary price list, the pricing engine looks for the price on any attached secondary price list. If the item is found, the pricing engine uses the highest precedence secondary price list (the secondary price list (with the lowest value in the precedence field). If an item appears in both the primary and a secondary price list with the same effective dates, the pricing engine uses the primary price list to price the item. If an item appears on the primary price list but is not active (the effective end date has passed), the pricing engine uses the price on the secondary price list. QP: Qualify Secondary Price Lists to Yes
GRANTS AND ROLES You can grant a user a role in one organization or all organizations for a period of time. The role is assigned to a user by a grant. The grant is specific to a particular user and defines the role(s) assigned to the user, the organization where the grant is effective, the start date and optionally, an end date. More than one grant can be assigned if the user requires different access controls to more than one organization. The start and end dates for grants can overlap. Nag: Setup↔shipping↔shipping grants and roles
Go to edit role what ever modification you want you can do. For example, if a user requires full-access privileges to three organizations and view-only access to a fourth, the user must be assigned four grants--one for each respective organization (three full-access and one viewonly grant). However, if only one grant is assigned, that grant becomes the default grant for the user. In addition, the grant has the following requirements: •
A grant may or may not have one inventory organization selected.
•
Many grants can be assigned for each role.
•
A user can have one or more grants. If the user does not have any grant (expired, effective, or future), the default is view-only access to all organizations. If the user has grants, the user's access is controlled by the effective grants. If there are overlapping grants in the same organization or an intersection of grant date ranges, the union of grant privileges controls the user's access.
•
A grant cannot be designated as the default grant.
A role can be assigned to a user that spans all organizations instead of granting a unique grant per organization. If an organization is not specified, the grant is applicable to all organizations. A grant can have one or all inventory organizations. If an organization is not specified, the grant is applicable to all organizations. For example, you can use grants to prevent a shipping clerk from assigning freight costs or planning a delivery in one or all organizations. Note: Use caution when creating grants for all organizations (when no specific organization is selected). For example, if a user has a grant to view all organizations and a grant to perform actions on one organization, the union of these grants will enable the user to perform actions in all organizations.
ENTERING SALES ORDERS AND BOOKING ORDERS You can enter, view, and update sales orders using the Sales Orders window. You can also enter returns using the Sales Orders window. You can order standard items, both shippable and non-shippable, and configurations using this window. You can also adjust pricing, assign sales credits, record payment information, attach notes, schedule shipments, query item availability, and make reservations, including selection of subinventories. You can enter information in the Sales Orders window as you receive it. Order Management validates individual fields as they are entered. When you book an order, Order Management validates to ensure that all required fields have values, that configurations are complete, and so on. After an order has been booked, it becomes eligible for the next step in its workflow. For orders that you intend to source externally (drop shipments), you can use all aspects of standard sales order functionality. The source type at order entry determines whether an order will be fulfilled from inventory or by an external supplier. Nag: Orders-Returns↔Salesorder
You can enter header information for a sales order as you receive it, not necessarily in the sequence followed by the window’s tabbed regions. The only fields you must enter before proceeding to the lines block are Order Type and Currency in the Main tabbed region in the Sales Orders window.
Navigate to the Sales Orders window and select the Main tabbed region.
1. Select the customer name or customer number you must enter a customer to be able to book an order. This is the Sold To customer for the order. ■ Customers are visible across all organizations and customer addresses are organization specific. The value of the profile option OM: Sales Order Form: Restrict Customers controls the LOV display for this field. If you use the Find Customer window, the Customer field LOV will always display all customers. ■ The ship to and bill to customer names may be different, depending on how you define your customer information. The profile option OM: Sales Order Form: Restrict Customers controls the LOV display for this field also. ■ If you have not previously defined the customer for this order, you can define a new customer within the Add Customer window, provided your system settings enable this functionality. 2. Select an order type for the order or accept the defaulted value. 3. Order type can be used as a data source for defaulting rules and additionally determines both the order and line workflow processes your orders will flow within. 4. Define the Customer Purchase Order Number for the order, or accept the default. This information is for reference and reporting. You must enter a value here if the order type you specified requires a purchase order number. You can set up a default for a PO number from an Agreement using
defaulting rules. Order Management notifies you if you enter a purchase order number that already exists on another order for the same customer but will not prevent you from continued processing of the order. 5. Define the Date Ordered or accept the default. 6. Enter a Customer Contact name for the order or accept the default. If you have not previously defined a customer contact or wish to define a new contact for this order, define the contact within the Add Customer window provided your system settings enable this functionality. 7. Select a Price List for the order. The Price List you select must be an active price list. If a price list is inactivate, The price list does not appear in the LOV for the Price List field. If you enter an order, then inactivate the price list used in that order, and then requery your order, you will receive an error message box: Validation fails at the field Price List. Depending on the value of the profile option QP: Selling Price Rounding Options, you price list prices may be rounded when entering order lines. 8. Enter the Ship To customer information. You can enter Ship To information using several different methods. You can choose to enter either ■ the Sold To customer and the Ship To location, which provides the Ship To customer name and customer address details. ■ the Sold To customer and Ship To customer (name or number) and the Ship To (site) using the Ship To or Ship To address1 list of values. ■ Ship To Location: The list of value for this field shows the Customer name, customer number, and business purpose address information for all Ship To locations for the Sold To customer and it’s related customers. You can select the Ship To Location field prior to selecting the Ship To customer. Selecting the Ship To location enables you to have the Ship To field default from the Ship To location chosen. The list of values long list has been enabled for this field, and you are limited to searching by Ship To Location. ■ Ship To: Select the Ship To customer and then the Ship To (site), not the Ship To Location. The list of value for this field shows the Ship To locations of the Ship To customer only. Ship To customer details are present if the Ship To Location field has a value. The list of values long list has not been enabled for this field, and you can search on ant column within the LOV. Ship To Address details are currently displayed within the following fields. ■ Ship To Address1 ■ Ship To Address2 ■ Ship To Address3 ■ Ship To Address4 ■ Ship To Address5 (concatenation of city, state, zip, and country)
9. Select the Salesperson for the order. By default, the primary salesperson receives 100 percent of the sales credits for an order. You can apportion sales credits to multiple individuals in the Sales Credit window. 10. Select a currency for the order. Your price list’s currency must match the currency you entered for this order. 11. Enter the Bill To (Invoice To) customer information. You can enter Bill To information using several different methods. You can choose to enter either. a. the Sold To customer and the Bill To location, which provides the Bill To customer name and customer address details. b. the Sold To customer and Bill To customer (name or number) and the Bill To (site) using the Bill To or Bill To address1 list of values. ■ Bill To Location: The list of value for this field shows the Customer name, customer number, and business purpose address information for all Bill To locations for the Sold To customer and it’s related customers. You can select the Bill To Location field prior to selecting the Bill To customer. Selecting the Bill To location enables you to have the Bill To field default from the Bill To location chosen. Bill To: Select the Bill To customer and then the Bill To (site), not the Bill To Location. The list of value for this field shows the Bill To locations of the Bill To customer only. Bill To customer details are present if the Bill To Location field has a value. The list of values long list has not been enabled for this field, and you can search on any column within the LOV. Bill To Address details are currently displayed within the following fields. ■ Bill To (Invoice To Address1) ■ Bill To (Invoice To Address2) ■ Bill To (Invoice To Address3) ■ Bill To (Invoice To Address4) ■ Bill To (Invoice To Address5; concatenation of city, state, zip, and country) Save your work. NOTE: Depending upon how your defaulting values are set up, choosing an order type before you define a Bill To, Ship To, or Deliver To address for the order, may default information within the Bill To, Ship To, or Deliver To address fields.
Go to OTHER TAB
1. Navigate to the Others tabbed region in the Sales Orders window. 2. Select the Payment Terms for the order. Payment terms are defined in Oracle Receivable and used during interface Order Management APIs to Oracle Receivables for invoicing. You can define payment terms using the Payment Terms window. 3. Select the Sales Channel for the order. You can use a sales channel to classify orders for reporting purposes. 4. Select a Warehouse (organization) from which to ship the order line. 5. Select a Shipment Method. Shipment method determines how your shipment will be shipped to your customer. 6. In the Line Set field, choose whether you want to group lines to ship together or if you want to group lines to arrival together or get fulfilled together. All lines in this order that have the same ship set or arrival set number will be shipped or arrive together, respectively. All lines in a ship set must have the same Ship From (warehouse), line scheduled shipment date, and Ship To. ■ All lines within an arrival must have the same Scheduled Arrival Date and Line Ship To Organization.
■ All lines in a fulfillment set must complete the Fulfill workflow activity before invoicing. When you indicate ship set or arrival set, the order entry process schedules the line regardless of the profile option OM: AutoSchedule. 7. Select the Freight Terms. The freight terms record who is responsible for the freight charges for the order. You can define additional freight terms by using the Order Management QuickCodes window. 8. Select an FOB point. You can define additional FOB choices in the Receivables Lookups window. Select a Shipment Priority. Shipment priority enables you to group shipments into different categories of urgency, and can be used as a parameter for Pick Release. You can define additional shipment priorities in the Order Management Lookups window. 10. Define Shipping Instructions. Shipping instructions are printed on the pick slip and are intended for internal use only. 11. Define Packing Instructions. Packing instructions are printed on the pack slip and are intended for external shipping personnel. 12. Select a Tax Handling Status. You can select from the following: Exempt--Indicates that this order is exempt for a normally taxable customer site and/or item. If you select Exempt, you must enter a reason for exemption. Require--Indicates that this order is taxable for a normally non-taxable customer and/or item. Standard--Indicates that taxation should be based on existing exemption rules. If the customer has a tax exemption defined, Order Management displays any certificate number and reason for the exemption in the corresponding fields. 13. Select an existing Certificate number (if you chose Exempt in the Tax Handling field) for the ship to customer, or enter a new, unapproved exemption certificate number. Unapproved exemption certificate numbers can be approved using the Tax Exemptions window. If you chose Standard in the Tax field, an existing exemption rule may display a certificate number in this field. . 14. Select a reason (if you chose Exempt in the Tax Handling field) before booking the order. You can define tax exemption reasons in the Receivables QuickCodes window. If you chose Standard in the Tax field, an existing exemption rule may display a reason in this field. 15. Select a Payment Type. Choose from--Cash, check, or credit card. If the customer has a primary credit card on file, the Credit Card payment type automatically defaults. Payment type within Order Management is a Quick code. Although you can add new values for the quick code, they are not supported, and you cannot disable seeded payment types. 16. Define the Amount of the payment. This value can be either the full amount owed or a partial amount, such as a deposit or down payment. 17. If you select the payment type of check, enter the Check Number.
18. If you select the credit card payment type, enter the Credit Card Name and Number. The credit card name and number fields automatically default if a primary credit card is on file. a. Enter the Credit Card Holder’s name as it appears on the card. The credit card holder’s name field automatically defaults if a primary credit card is on file. b. Enter the Credit Card Expiration Date. The credit card expiration date field automatically defaults 19. Enter an Approval Code for the credit card transaction for manual transactions. 20. The field Prepaid Amount represents the total amount currently collected for an order. 21. Select the Order Source for the order. 22. Save your work. GO TO LINE ITEMS If you want to search on customer item description, use the Customer Items Summary, Customer Items Detail, and Customer Item Cross References windows to define and update customer item descriptions. If you want to search on generic item description, use the Cross-Reference Types window to define new item identifier types and then assign the types to inventory items. If you wish to sort order lines, use the Sort Data function available from the Folder menu. See: Sorting Order Lines within the Sales Order window, Lines Tab. If you wish to go to a specific order line number, use the Go to Line feature available from the Actions Menu. The Go to Line pop up window enables you to enter a specific line number for display; the line number entered will be displayed within the Sales Order Line. Main Tab. You can enter a partial line quintuplet number. Attention The following fields currently can contain rounded amounts within the Sales Order Lines window.
Navigate to the Line Items tabbed region in the Sales Orders window. Define the Line Number. This field automatically defaults to 1.1 if this is the first line entered on the order. This field is for display purposes and cannot be updated. Order Lines Numbers are displayed in the Sales Order window as a line quintuplet. Line Number, Shipment Number, Option Number, Component Number, Service Number. For example, if order line number appears as 1.1.2.3.1. Line Number -1 ■ Shipment Number -1 ■ Option Number - 2 ■ Component Number -3 ■ Service Number-1 You may choose to display additional fields within the Sales Order Header Main window by enabling the fields for display within a custom folder. For example, you can choose to display the Line number & shipment number fields.
Select the list of values your item
Select the item for this order line. The List of Values for this field is controlled by the value of the hidden field, Item Identifier Type. Select or enter a value for either. Ordered Item (the item number); item description displays. Item Description and Type; Ordered Item displays. You can search for item descriptions by entering the search criteria into the field and tabbing out of the field to start the search. The search is not sensitive to case. You can search on different types of item descriptions. To search. For internal item descriptions, within the Item Identifier Type field, select INT or Internal Item. For customer item descriptions, within the Item Identifier Type field, select CUST For generic item descriptions, within the Item Identifier Type field, select any Item Identifier Type you have defined. To search on all types of item descriptions, leave the Item Identifier Type field blank. For orders, the list of values displays descriptions of active and inactive items; for returns, the list of values displays descriptions of active and inactive items.
Order Management validates the item against inventory items you define in the warehouse (organization) specified by the Order Management parameter Item Validation Organization. You can only choose items that have the Customer Orders Enabled item attribute set to Yes. If you have setup customer or generic cross-references for these items, you can also enter the order line using the cross-reference. If you intend to source this line externally, you must also ensure that the item you select has the Purchasable item attribute indicated. This attribute enables an item to be ordered on a purchase order.
Define the item's order quantity for this line. The quantity field appears on all tabbed regions even though it is in the scrollable region. Select the Unit of Measure. You can enter only predefined units of measure in the same class as the item's primary unit of measure. The units of measure for models and kits are restricted to the item's primary unit of measure. Unit Selling Price: Unit Selling Price is derived from the selected price list, and may contain a rounded value. The value of the unit selling price is affected by the current value of the profile option QP: Selling Price Rounding Options. Enter, select, or accept the default for the Request Date field. Select the Schedule Ship Date from the calendar.
Status: This field displays the current status of the order line, and can only be updated via a system action. On Hold ATO check box. Cascaded Hold ATO check box. ATO check box: The field is non updateable. If the check box is selected, the order line contains an ATO item. Select or accept the default for Line Type. Qty Cancelled: this field will display a value only if an order line’s quantity was changed as a result of a cancellation. Qty Shipped: this field will display a value only if an order line has been shipped, either partially or completely. Reason: This field is non updateable except when adding to, or reducing, the existing order line quantity. Values entered in this field are only visible at the time of entry; once a successful save has been completed, the value of the Reason field displayed is NULL. Order Management does not display the current value for this field since you can perform multiple updates to an order line that require you to enter a reason. You can view Reason values entered within the Additional Line Information window, available via the Action button. You can view Reason values entered within the Additional Line Information window, available via the Action button. Order Source: The value for this field is determined by the creating application when a sales order is created. This field is non updateable, and valid values are: ■ Internal ■ External If you have copied an order, the order lines for the copy to order will display COPY. Order Source Line Reference: If you create an order line within the Sales Order window, or create an order where order_source_id=0, the system will generate a value for Order Source Line Reference. The value generated is the source table name, concatenated within the line_id. This value is stored in the source table (OE_ORDER_LINES_ALL) within the column ORIG_SYS_DOCUMENT_REF. If you have copied an order, the order lines for the copy to order will display the source order number. Select the Tax Code, if not defaulted. You are only able to select a Tax code if the profile option Tax: Allow Override of Tax Code is set to Yes.
Book the Order.
Click OK (order has been booked) Order number generated in Header
SHIPPING ORDER & CREATE DELIVERIES & TRIPS. The Release Sales Orders for Picking window specifies the criteria for releasing one or more order lines. You can select order lines based on a number of criteria such as warehouse, shipment request date, and item. Shipping Execution only releases delivery lines that have been booked and have met the prerequisites for Pick Release. Nag: Shipping ↔Release Sales Order↔Release Sales Order
There are three tabs, containing multiple fields, within the Release Sales Orders for Picking window, including the following. o
Orders
o
Order Number
o
Prior Reservations Only
o
Destination Type
o
Customer
o
Order Type
o
Ship Set
o
Ship To
o
Item Category Set
o
Item Number
o
Item Category
o
Scheduled Ship Dates To and From
o
Requested Dates To and From
When you enter the order number Order Type & Customer came by default. Go to Inventory Tab
o
Warehouse (the organization code)
o
Subinventory (sales order lines booked and scheduled with this particular subinventory specified will be selected for pick released)
o
Project (used if Oracle Project Manufacturing is enabled)
o
Task (used if Oracle Project Manufacturing is enabled)
o
Pick Slip Grouping Rule
o
Auto Allocate
o
Plan Tasks (used if Oracle Warehouse Management is enabled)
o
Pick From Subinventory and Locator (if the item is not in the specified Pick From Subinventory or Locator, the system will not specify another location)
o
Default Stage Subinventory and Locator
When you select your Warehouse automatically came Inventory Information and Shipping information. Based up on your Shipping Parameters. Go to Shipping Tab
o
Trip
o
Delivery
o
Ship Method
o
Line/Container
o
Release Sequence Rule
o
Autocreate Delivery
o
Auto Pick Confirm
o
Ship Confirm Rule
o
Stop
o
Ship From
o
Shipment Priority
o
Include Assigned Lines
o
Autocreate Delivery Criteria
o
Autopack Delivery
o
Append Deliveries
Then click Concurrent
Click OK Then go to Transaction window
SHIPPING TRANSACTION The Shipping Transactions form provides a consolidated workbench. It enables you to plan and manage trips, stops, deliveries, delivery lines, and LPNs (containers).
When you navigate to the Shipping Transactions form, the Query Manager window opens on top of the Shipping Transactions form automatically, enabling you to search for trips, deliveries, delivery lines, LPNs, and stops. You can either move the Query Manager window to view the Shipping Transactions form that is behind it, or close the Query Manager window to view the Shipping Transactions form. With the Shipping Transactions form, you manage information about shipping entities, and complete the following tasks. Plan trips, stops, deliveries, and delivery lines/containers. Ship confirm a delivery or trip Track shipments Track shipping containers Handle over and under shipments
Initiate Intrastate (European) transactions Pick release trip, stop, delivery, delivery lines, and container Run reports Enter details about a shipment, such as, weights, waybill numbers, and tracking Numbers, serial numbers and freight costs The Shipping Transactions form is right-click enabled. You can perform actions by right-clicking on the window and selecting the desired action. Although buttons are active when no data exists on the Shipping Transactions form, if you attempt to use the buttons no action will be performed and a warning message will be displayed. This is also the case when buttons are active when the action of that button is not possible. For example, when a delivery line is assigned to a delivery, the Autocreate Deliveries button is active, and if you click that button a warning message will be displayed stating that the delivery line is already assigned to a delivery. After that Click Find.
Then Create Trips
TRIPS: A trip is an instance of a specific freight carrier departing from a particular location containing deliveries. A trip is carrier specific and contains at least two stops such as a stop to pick up goods and another stop to drop off goods, and may include intermediate stops. Trip stops are displayed in sequence on the Stops tab within the Shipping Transactions form once you have queried your trip. The Stop sequence will not resequence if a stop is removed. For example, if you have two stops, each with an arrival and departure date and time, and you remove one, the remaining stops will stay in the same sequence as they were originally. Trips can be created automatically or manually. CREATE TRIP Automatic. Trips are required for all deliveries and can be created automatically as part of Ship Confirmation transparent to the user for those not interested. If your shipping process does not require advanced planning, you may prefer to automatically create trips. ■ Auto-creating a trip for a delivery: You can find the delivery you want to ship, and auto-create a trip and related trip stops. ■ Auto-creating a trip for containers and lines: You can find the lines and containers you want to ship and auto-create a trip which creates a trip, related deliveries, and trip stops. Manual You can manually create a trip and later assign delivery lines or find the delivery lines and create a trip. For example, for a regular trip scheduled to depart every Friday, you can manually set up a trip ahead of time and then assign delivery lines. When you manually create a trip, you can manually assign stops, deliveries, and Delivery lines to that trip.
If more than one delivery displays, select the deliveries. From the Actions menu, select Auto-create Trip. Click Go. At least one trip and its related stops are created based on the deliveries Shipped From and Shipped To locations. You can view information about the trip by choosing the Detail button, the Path by Stop tab, or the Path by Trip tab. Save your work.
Trip Created
Then Ship Confirm go to actions select Ship Confirm Click GO.
Navigate to the Query Manager window, and find the delivery. The delivery displays in the Shipping Transactions form. From the Actions menu, select Ship Confirm to display the Confirm Delivery window. If you select a ship confirm rule that meets your business needs, then you can skip the remaining steps, and click OK. In the Ship Options region, select one of the following ship confirm options Ship Entered Quantities, Unspecified Quantities Ship: Ship confirms the quantity of items specified in the Shipped Quantity field and treats blank values as full quantity (shipped quantity = requested quantity). For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values entered), the full quantity (10) is shipped and displays in the Shipped Quantity field. ■ Ship Entered Quantities, Unspecified Quantities Backorder: Ship confirms the quantity of items specified in the Shipped Quantity field and treats blank quantities as full backorders (backorder quantity = requested quantity). For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values), the full quantity (10) is backordered and displays in the backordered Quantity field. Ship All: Ship confirms the entire quantity regardless of what was entered in the Shipped Quantity field (shipped quantity = requested quantity). For example, if the Requested Quantity is 10 and the Shipped Quantity field is 5, the full requested quantity is shipped (10) and displays in the Shipped Quantity field.
Backorder All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0, backorder quantity = requested quantity). Cycle Count All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0, backorder quantity = requested quantity) and transfers the backorder reservation to cycle counting. You can also transfer delivery quantities to cycle count prior to ship confirm by using the Shipping Transactions form, Cycle Count action. Enable the Create Delivery for Staged Quantities box (default setting), if you want all staged delivery lines grouped together in a new delivery. If you do not want to create a trip for the delivery, click Go to ship confirm and save your work In the Trip Options region, select or update the Ship Method and the Actual Departure Date. This enables you to specify the stop departure date which is the date Order Management Inventory interface will occur. One way to ship confirm one or more deliveries is to enable the Set Delivery in-Transit and Close Trip fields in the Confirm Delivery window. Set Delivery In-transit: Creates a trip and stops for the delivery. Closes the first stop of the delivery, but leaves second stop open. Sets status of delivery to In-transit and initiates Order Management (OM) and Inventory interfaces. Close Trip: Creates a trip and stops for the delivery. Closes trip, all stops, and the delivery. You can enter a future Actual Departure Date. If Allow Future Ship Date in the Shipping Parameters form, Shipping Transactions tabbed region, is cleared, do not do so as you receive an error. If Allow Future Ship Date is selected, you receive a warning and the Inventory Interface concurrent process does not process the transaction until the actual departure date. After that Click OK. Massage shows Delivery was Successfully Created
Click OK.
