Bookmark and Share Subscribe You may face visibility problem if http://docs.google.com is blocked on your network

Wednesday, December 3, 2008

Min-Max Planning

*For better visibility open pictures in new window.
Item DEV001 is min-max planned item with minimum quantity 20
If the quantity of DEV001 goes below 20 in FG subinventory then, user is going to take DEV001 from RM subinventory where huge stock for this item is maintained..
For this create an item in the Item Master. In the General Planning tab, selects the Inventory Planning Method as Min-Max. and source type as Sub-inventory.
In the Planning tab for the FG subinventory, specifies that the item DEV001 is Min-Max driven whenever it resides in FG. And whenever the quantity falls below the Min Qty of 20 in FG, it will be time for Min-Max to trigger replenishment.
The quantity of 400 is just the suggested quantity to maintain as the maximum on hand balance



In the Order Modifiers tab an opportunity is there to specify a Fixed Lot Multiple of 15. This implies that the quantity for replenishment will be suggested (calculated by the Min-Max algorithm) in multiples of 15. Minimum 30 items has to be ordered and maximum of 150 at a time.
There can be multiple order lines to reach Max Qty 400 (say 150+150+100). But the Fixed lot Multiple is 15, so order can’t be of 100 qty (100 is not a multiple of 15). Hence max level of 400 can be reached by orders of 150 +150+105 qty (Total 405).


Finally, in the Sourcing tab, mention that RM will be the sourcing subinventory.


Now checkout the on-hand for DEV001 in FG.


As the on-hand in FG for DEV001 is just 5 i.e. below minimum level of 20, it’s time to trigger replenishment.
The only task that is left is to run the Min-Max Planning report. This report serves to highlight items that need replenishment and also suggests the replenishment quantity based on the setup.
Unlike most reports, the Min-Max Planning report can also trigger the replenishment process. This means creating Pre-Approved Move Orders to fulfill the suggested replenishment quantity.
To launch the replenishment process, run the Min-Max Planning report with the parameter Restock set to Yes


The O/P of this report shows that Reorder Quantity as 405. This figure matches with the calculation given above. That indicates we are on the right track so far. As the report has Restock=Yes it must have generated pre-approved Move Order.




Search for the Move order created:


Here again above calculation proves it self. There lines got created to reach max qty level of 400.


Now just allocate (click on Allocate button) material for the lines and simply transact the same. If the item on line is serial/lot controlled the allocation must be done by clicking button View/Update Allocation button.
After Transact Move Order material must have reached to destination i.e. in FG sub-inventory.
Just checkout this:


Here the cycle gets completed….
Now user can consume material form FG sub-inventory and the replenishment will keep happening whenever stock comes below the specified level.
Similarly we can follow the cycle for the items which are purchased by selecting supply type as Supplier and so on….

Another wonder full article on Min Max planning is ... https://www.apps2fusion.com/apps/apps-training/801-min-max-plan-r12 and here example is of replenishing from different inventory organization

Keep practicing…. Keep blogging….

Sunday, November 23, 2008

Miscellaneous Transactions - Overview

Types of Miscellaneous Transactions

There are six types:

  • Miscellaneous receipt
  • Miscellaneous issue
  • Account receipt
  • Account issue
  • Account alias receipt
  • Account alias issue

Use of Miscellaneous Transactions
  1. With a miscellaneous transaction you can issue material to or receive material from general ledger accounts in your current organization. 
  2. This allows you to issue material to groups that are not inventory, receiving, or work in process such as a R&D group or an accounting department. 
  3. You can also make manual adjustments to the general ledger by receiving material from one account to inventory, and then issuing that material from inventory to another account.
  4. You can use your user-defined transaction types. You can use this feature to issue items to individuals, departments, or projects; or to issue damaged items to expense accounts such as scrap Inventory.
  5. You can perform the receipts for items that were acquired by means other than a purchase order from a supplier.
  6. You can also use this feature to load all item on-hand quantities when you start implementing Oracle
The list given above is not complete.... reader are requested to add other point in comment section...

Monday, October 20, 2008

Monday, October 13, 2008

Drop - ship Order Demo




Please visit Drop-ship Order Flow for details.

One more good article on Drop Ship is at below link
http://www.oracleappshub.com/beginner/understand-drop-shipment-in-order-management/

Friday, October 3, 2008

Workflow diagram for manufactured ATO item.


Blue line is main workflow.
Flow shown in Purple box is an explored flow.
Green line is the flow which is followed by a manufactured ATO




Please download the picture or open it in new window for better visibility.

Monday, September 8, 2008

Oracle Inventory Terminology

Terms used in the conventional Inventory system and as referred in Oracle Inventory may be different. A brief explanation of the ‘Oracle Inventory’ term’s vis-à-vis the existing terminology is provided the following paragraphs. These terms are extensively used in documenting the ‘Inventory - To Be’ flows and it is recommended that the various users of this system get acquainted with the same.


Item Validation Organization: The organization that contains your master list of items. You define it by setting the OE: Item Validation Organization profile option.


Logical organization: A business unit that tracks items for accounting purposes but does not physically exist.


Organization: A business unit such as a plant, warehouse, division, department, and so on. Order Management refers to organizations as warehouses on all Order Management windows and reports.


Destination organization: An inventory organization that receives item shipments from a given Organization.


Workday calendar: A calendar that identifies available workdays for one or more organizations. Master Scheduling/MRP, Inventory, Work in Process, and Capacity plan and schedule activities based on a calendar’s available workdays.


Workday exception set: An entity that defines mutually exclusive sets of workday exceptions. For each organization, you can specify a workday calendar and exception set.


Primary unit of measure: The stocking unit of measure for an item in a particular organization.


Unit of measure: The unit that the quantity of an item is expressed.


Unit of measure class: A group of units of measure and their corresponding base unit of measure. The standard unit classes are Length, Weight, Volume, Area, Time, and Pack.


Unit of measure conversions: Numerical factors that enable you to perform transactions in units other than the primary unit of the item being transacted.


Category: Code used to group items with similar characteristics, such as plastics, metals, or glass items.


Category set A feature in Inventory where users may define their own group of categories. Typical category sets include purchasing, materials, costing, and planning.


Purchased item: An item that you buy and receive. If an item is also an inventory item, you may also be able to stock it.


Standard item: Any item that can have a bill or be a component on a bill except planning items, option classes, or models. Standard items include purchased items, subassemblies, and finished products.


Substitute item: An item that can be used in place of a component. Master Scheduling/MRP suggests substitutes items on some reports.


Inventory item: Items you stock in inventory. You control inventory for inventory items by quantity and value. Typically, the inventory item remains an asset until you consume it. You recognize the cost of an inventory item as an expense when you consume it or sell it. You generally value the inventory for an item by multiplying the item standard cost by the quantity on hand.


Item attribute control level: To maintain item attributes at the item master attribute level or the Organization specific level by defining item attribute control consistent with your company policies. For example, if your company determines serial number control at headquarters regardless of where items are used, you define and maintain serial number attribute control at the item master level. If each organization maintains serial number control locally, they maintain those attributes at the organization specific level.


Item attributes: Specific characteristics of an item, such as order cost, item status, revision control, COGS account, etc.


Item master level attribute: An item attribute you control at the item master level as opposed to controlling at the organization level.


Item status: Code used to control the transaction activity of an item.


Deletion constraint: A business rule that restricts the entities you can delete. A deletion constraint is a test that must succeed before an item, bill, or routing can be deleted.


Current on–hand quantity: Total quantity of the item on–hand before a transaction is processed.


On–hand quantity: The physical quantity of an item existing in inventory.


Subinventory: Subdivision of an organization, representing either a physical area or a logical grouping of items, such as a storeroom or receiving dock.


Locator: Physical area within a subinventory where you store material, such as a row, aisle, bin, or shelf.


Locator control: An Oracle manufacturing technique for enforcing use of locators during a material transaction.


Revision A particular version of an item, bill of material, or routing.


Revision control: An inventory control option that tracks inventory by item revision and forces you to specify a revision for each material transaction.


Lot: A specific batch of an item identified by a number.


Lot control: An Oracle Manufacturing technique for enforcing use of lot numbers during material transactions thus enabling the tracking of batches of items throughout their movement in and out of inventory.


Serial number: A number assigned to each unit of an item and used to track the item.


Serial numbers control: A manufacturing technique for enforcing use of serial numbers during a material transaction.


Min–max planning: An inventory planning method used to determine when and how much to order based on a fixed user–entered minimum and maximum inventory levels.


Reorder point planning: An inventory planning method used to determine when and how much to order based on customer service level, safety stock, carrying cost, order setup cost, lead time and average demand.


Safety stock: Quantity of stock planned to have in inventory to protect against fluctuations in demand and/or supply.


ABC classification: A method of classifying items in decreasing order of importance, such as annual dollar volume or your company’s transaction history.


Cycle counting: An inventory accuracy analysis technique where inventory is counted on a cyclic schedule rather than once a year.


Physicals inventory: A periodic reconciliation of item counts with system on–hand quantities.


Account alias: An easily recognized name or label representing an account charged on miscellaneous transactions. You may view, report, and reserve against an account alias.


Inter–organization transfer: Transfer of items from one inventory organization to another You can have freight charges and transfer credits associated with inter–organization transfer. You can choose to ship items directly or have them go through intransit inventory.


Material transaction: Transfer between, issue from, receipt to, or adjustment to an inventory organization, subinventory, or locator. Receipt of completed assemblies into inventory from a job or repetitive schedule. Issue of component items from inventory to work in process.


Transaction cost: The cost per unit at which the transaction quantity is valued.


Transaction interface: An open interface table through which you can import transactions.


Transaction manager: A concurrent program that controls your manufacturing transactions.


Receipt: A shipment from one supplier that can include many items ordered on many purchase orders.


Return to supplier: A transaction that allows you to return to the supplier items from a fully or partially received purchase order and receive credit for them.


Supplier: Provider of goods or services.


Accounting period: The fiscal period a company uses to report financial results, such as a calendar month or fiscal period.


Average costing: A costing method which can be used to cost transactions in both inventory only and manufacturing (inventory and work in process) environments. As you perform transactions, the system uses the transaction price or cost and automatically recalculates the average unit cost of your items.


Standard costing: A costing method where a predetermined standard cost is used for charging material, resource, overhead, period close, job close, and cost update transactions and valuing inventory. Any deviation in actual costs from the predetermined standard is recorded as a variance

Friday, August 29, 2008

Purchasing Overview

PURCHASE ORDER

What are the main tables associated with Purchase Order?

There are four main tables associated with Purchase Order.

1. PO_HEADERS_ALL

2. PO_LINES_ALL

3. PO_LINE_LOCATIONS_ALL

4. PO_DISTRIBUTIONS_ALL

1. It contains the Header information for the Purchasing documents. We require one row for each document we create.

Six types of documents that use PO_HEADERS_ALL are

a. RFQ

b. Quotation

c. Standard PO

d. Planned PO

e. Blanket PO

f. Contracts

Important data that are populated in this table are

· Buyer Information

· Supplier Information

· Brief Notes

· Terms and Conditions

· Status of the document

PO number is Segment1 of PO_HEADERS_ALL

Important columns: PO_HEADER_ID

2. It stores information about each PO lines. We need one row for each line we attach to a document.

Each row includes

a. LINE NUMBER

b. ITEM NUMBER

c. UNIT

d. PRICE

e. U.O.M

f. QUANTITY

3. It contains the information about PO shipment schedules and Blanket Agreement Price Breaks.

We need one row for each schedule or price break we attach to a document

Each row includes

· Destination Type

· Requestor Id

· Quantity Ordered and Delivered to Destination

Ø If the distribution corresponds to a Blanket PO release, PO_RELEASE_ID column identifies this release

Ø We enter distribution information in distribution window accessible through PO window

­CLOSING THE PURCHASE ORDER

The CLOSED_CODE column exists in the following three tables

1. PO_HEADERS_ALL

2. PO_LINES_ALL

3. PO_LINE_LOCATIONS_ALL


IMPORTANT COLUMNS OF PURCHASING TABLES

PO_HEADERS_ALL

PO_LINES_ALL

PO_LINE_LOCATIONS_ALL

PO_HEADER_ID

SEGMENT1

VENDOR_ID

VENDOR_SITE_ID

SHIP_TO_LOCATION_ID

CURRENCY_CODE

CLOSED CODE

1. OPEN

2. CLOSED

3. FINALLY CLOSED

4. HOLD

5. FREEZE

PO_LINE_ID

CATEGORY_ID

ITEM_ID

PO_HEADER_ID

QUANTITY

CLOSED_CODE

1. OPEN

2. CLOSED

LINE_LOCATION_ID

SHIP­_TO_LOCATION_ID

PO_HEADER_ID

PO_LINE_ID

QUANTITY_RECEIVED

QUANTITY_ACCEPTED

QUANTITY_REJECTED

CLOSED_CODE

1. OPEN

2. CLOSED FOR INVOICE

3. CLOSED FOR RECEIVING

4. FINALLY CLOSED

RECEIVING

What are the different Purchasing modes in Receiving?

There are three modes

1. ONLINE

2. IMMEDIATE

3. BATCH

1. ONLINE: Receipts are processed Online. If there are any errors, they are shown on the FORM itself, and don’t let you IGNORE and PROCEED.

2. IMMEDIATE: Receipts are processed immediately, but no errors are shown. Errors are recorded in REC_TRANSACTION_INTERFACE table.

3. BATCH: Receipts are processed in batch, but no errors are shown. Errors are recorded in REC_TRANSACTION_INTERFACE table.

Note: In all the above two cases, it requires Receiving Transaction Processor to be run periodically.

When you SAVE a Received Data in FORM, which tables are UPDATED?

Ø RCV_SHIPMENT_HEADERS: It contains SUPPLIER shipment header data like Shipment Date, Supplier Name

Ø RCV_TRANSACTIONS_INTERFACE: It contains RECEIVED data like Item Name, Quantity, and Receiving location

Ø RCV_SHIPMENT_LINES

Ø MTL_MATERIAL_TRANSACTIONS_TEMP

Ø PO_LINE_LOCATIONS_ALL

Ø PO_DISTRIBUTIONS_ALL

What are the major transactions in RECEIVING?

Ø Purchase Order Receipts

Ø Internal Requisition Receipts

Ø Inventory Inter-Org Transfer Receipts

Ø Customer Return Receipts

What are the different types of Receiving Routing?

Ø Standard Receipt

Ø Inspection Required

Ø Direct Delivery

Note: The Receipt form is used as Receiving materials against PO on Ordered receipts, Internal Requisitions, Inventory Inter-Org Transport and Customer Reports.

RECEIVING OPEN INTERFACE

Ø ROI is a gateway to IMPORT data from Oracle as well as Non-Oracle applications.

Ø The Receipts done through ROI should be processed in Batch mode only.

Ø In ROI, the table which are updated are

1. RCV_HEADER_INTERFACE

2. RCV_TRANSACTION_INTERFACE

Note: Transactions in ROI

Receipts can be done by Direct Delivery or by two steps namely RECEIVED and DELIVER.

This can be determined through AUTO_TRANSACT_CODE_FLAG.

If the value is DELIVERED, the system does a direct delivery into Sub-Inventory and if the value is RECEIVED, the system only receives the material and the delivery is done by the Receiving Transaction Form.

IMPORTANT COLUMNS OF RECEIVING TABLES

RCV_HEADERS_INTERFACE

RCV_TRANSACTIONS_INTERFACE

RCV_SHIPMENT_HEADERS

Ø HEADER_INTERFACE_ID

Ø GROUP_ID

Ø RECEIPT_SOURCE_CODE

Ø PROCESSING_STATUS_CODE

Ø TRANSACTION_TYPE

Ø ASN_TYPE

Ø INTERFACE_TRANSACTION_ID

Ø GROUP_ID

Ø PROCESSING_STATUS_CODE

Ø TRANSACTION_STATUS_CODE

Ø PROCESSING_MODE_CODE

Ø HEADER-INTERFACE_ID

Ø ASN_STATUS

Ø ASN_TYPE

Ø EDI_CONTROL_NUM

NON-SUPPORTED FEATURES OF ROI

Ø Transactions with LOT controls

Ø Transactions with SERIAL controls

Ø Internal Transfer & Sales order

Ø Un-Ordered Receipts

Through which you will be able to see ERROR reports in ROI?

Receiving Interface Errors Report

Data can be loaded into ROI either through flat files or direct SELECT statement. You can see details of errors from PO_INTERFACE_ERRORS table by joining with RCV_TRANSACTIONS_INTERFACE table using Interface_id.

What do you mean by PO requisition?

Ø PO requisition is a request to purchase materials for individual requirements. Normally Purchase requisitions are raised by employees or departments.

Ø Requisitions need approvals. It can be manually created or imported from other system like Inventory, WIP, MRP, OM etc

TABLES USED WITH REQUISITIONS

PO_REQUISITIONS_HEADERS_ALL

PO_REQUISITIONS_LINES_ALL

PO_REQ_DISTRIBUTIONS_ALL

The description is the same as PO

OTHER IMPORTANT TABLES USED WITH REQUISITIONS

Ø PO_VENDORS

Ø PO_LOOKUP_CODES

Ø PO_VENDOR_SITES_ALL

Ø PO_AGENTS

Ø PO_DOCUMENT_TYPES_ALL_B

Ø PO_RESCHEDULE_INTERFACE

Ø MTL_SUPPLY

IMPORTANT FIELDS OF REQUISITION

Ø REQUISITION_TYPE

Ø PREPARE

Ø TOTAL_CURRENCY

Ø LINE_TYPE

Ø CATEGORY

Ø SOURCE DESTINATION TYPE AND ORGANIZATION

ACTIONS PERFORMED WITH REQUISITION

Ø SAVE

Ø APPROVE

If you SAVE requisition, the above three tables are populated, while if you APPROVE a requisition, major tables updated are

Ø PO_REQUISITION_HEADER

Ø PO_APPROVAL_LIST_HEADERS

Ø PO_DOCUMENT_TYPES

CLOSING STATUS OF REQUISITION

Ø CANCEL

Ø FINALLY CLOSED

What do you mean by Auto Create?

Auto Create is a standard functionality provided by Oracle to create PO directly from Requisitions.

REQUISITIONS IMPORT PROGRAM (RIP)

Ø It is a concurrent program, which is used to import requisition from Oracle or Non-Oracle system.

Ø Data is first loaded in PO_REQUISITION_ALL table. The RIP can then be run, to import the records from the interface table as requisition in Oracle Processing.

Ø RIP creates a requisition line and one or more requisition distribution for each row it finds in the interface table. It then groups these lines on Requisitions according to parameters defined.

IMPORTANT TABLES

Ø PO_REQUISITION_INTERFACE_ALL

Ø PO_REQ_DIST_INTERFACE_ALL

Ø PO_INTERFACE_ERRORS

IMPORTANT PARAMETERS OF REQUISITION IMPORT PROCESS

a. Import Source

b. Import Batch Id

c. Group By

d. Initiate Approval after Import

REPORTS ASSOCIATED WITH REQUISITIONS IMPORT PROCESS

a. REQUISITION IMPORT RUN REPORT

We are able to view number of requisitions created and number of records in error from this report.

b. REQUISITION IMPORT EXCEPTIONS REPORT

We can see all rows that fail validation from this report

What do we mean by Sourcing Rule?

Ø It defines Inventory Replenishment method for either a Single Organization or for all Organizations.

Ø Sourcing rule is used to specify preferred Suppliers, Distributors and manufacturers.

Ø Use allocation percentage and ranking for multiple sources.

INTERNAL REQUISITIONS

Ø It is used to obtain materials within the same Organization or different Organization but within the same set of books.

Tuesday, May 27, 2008

Serial Number Generation in Oracle Apps

Serial generation in Oracle Apps is based on the parameters defined for an Organization:

  • Serial Uniqueness
    • Within organization: Enforce unique serial numbers within the current organization
    • Within inventory model and items: Enforce unique serial numbers for inventory items
    • Across organizations: Enforce unique serial numbers throughout all organizations
  • Serial Generation
    • At organization level: Define the starting prefix and serial number information for items using the information you enter in the following fields of this window
    • At item level: Define the starting serial number prefix and the starting serial number when you define the item
  • Prefix
  • Starting Serial Number Parameter
  • Allocate Serial Number: Indicate whether the system will suggest serial numbers as part of the move order line allocating process. If you do not select this option, you must manually enter the serial numbers in order to transact the move order.

Case-1 In organization parameters Serial Generation='At organization level' and Uniqueness='Within inventory model and items'

INVENTORY> On-hand Availability> Generate Serial Number

Select Organization and generate serial number for different items.

The serial number value gets incremented for each serial generation irrespective of item

e.g.

  1. INVENTORY> Setups> Organizations> Parameters
  2. Define ‘Prefix= MFG’ and ‘Starting Serial Number Parameter= 0001’ in MFG organization parameters
  3. Define ‘Prefix= SER’ and ‘Starting Serial Number Parameter= 0001’ in SER organization parameters
  4. Select MFG organization
  5. INVENTORY> On-hand Availability> Generate Serial Number
  6. Run Serial Generation program for ABC with quantity=5
  7. Run Serial Generation program for XYZ with quantity=5
  8. Serial number ‘MFG0001 to MFG0005’ will be assigned to ABC
  9. Serial number ‘MFG0006 to MFG0010’ will be assigned to XYZ
  10. Select SER organization
  11. INVENTORY> On-hand Availability> Generate Serial Number
  12. Run Serial Generation program for ABC with quantity=5
  13. Run Serial Generation program for XYZ with quantity=5
  14. Serial number ‘SER0001 to SER0005’ will be assigned to ABC
  15. Serial number ‘SER0006 to SER0010’ will be assigned to XYZ

Case-2 In organization parameters Serial Generation=’At Item Level’ and Uniqueness='Within inventory model and items'

  1. INVENTORY> Items> Organization items Query the item and go to Inventory tab
  2. Define Serial ‘Prefix= Item-MFG’ and ‘Starting Number= 0001’ for ABC and XYZ item in MFG organization
  3. Define Serial ‘Prefix= Item-SER’ and ‘Starting Number= 0001’ for ABC and XYZ item in SER organization
  4. Select MFG organization
  5. INVENTORY> On-hand Availability> Generate Serial Number
  6. Run Serial Generation program for ABC with quantity=5
  7. Run Serial Generation program for XYZ with quantity=5
  8. Serial number ‘Item-MFG0001 to Item-MFG0005’ will be assigned to ABC
  9. Serial number ‘Item-MFG0001 to Item-MFG0005’ will be assigned to XYZ
  10. Select SER organization
  11. INVENTORY> On-hand Availability> Generate Serial Number
  12. Run Serial Generation program for ABC with quantity=5
  13. Run Serial Generation program for XYZ with quantity=5
  14. Serial number ‘Item-SER0001 to Item-SER0005’ will be assigned to ABC
  15. Serial number ‘Item-SER0001 to Item-SER0005’ will be assigned to XYZ

Tuesday, May 20, 2008

Oracle Pricing.... (Qualifier and Modifier)

Oracle Pricing (Qualifier & Modifier)

Oracle Advanced Pricing provides a logical, flexible setup framework to handle complex pricing scenarios. It enables to break price creation into simple elements: define pricing rules, assign rules to create specific pricing actions, and designate pricing controls. Oracle Advanced Pricing also supports tailored pricing with built-in extensibility features.
Oracle Advance Pricing is part of Oracle Order Management, and integrates seamlessly with other Order Management applications, including Configurator and Order Management.
REQUIRMENT: For customer Bigmart (Customer Number 1168) give 10% discount on the unit price of the items present on sales order.
To fulfill this requirement one Qualifier and one Modifier need to be defined.
Pricing qualifiers controls, who is eligible for certain prices (price lists) and benefits.
The modifier provides price adjustments such as discounts, price breaks, surcharges, coupons, item and term substitutions, and other item discounts. Discount and surcharges modifiers affect the selling price; freight charge modifiers do not affect the selling price.
Now first qualifier needs to be defined and at time of defining modifier this qualifier needs to be attached to the modifier. Qualifier qualifies the pricing request and modifier modifies that.
Define Qualifier: Bigmart Disc.





As this qualifier is newly defined we need to run one concurrent request “Build Attribute Mapping Rules”. This request needs to be run on defining new qualifier, it is always recommended to run the same after doing change in the qualifier.







Defined Modifier: Disc. Bigmart


The requirement is to give 10% to all the line. So select Level as ‘Line’ to apply modifier at line level. Even though it is for all the lines there is a difference in giving 10% discount at all lines level and giving discount at header level. If it would be at Header level 10% will be given to charges also along with items. Also provide all other values relevant to the requirement as shown.



>

Attach Qualifier to the modifier: Click on ‘Line Qualifiers’ button to attach “Bigmart Disc.” to “Disc. Bigmart”.





Sales Order 56771 is entered before creating the Modifier:





Sales Order 56772 is entered after creating the Modifier:




See the difference in prices at line level on two Orders. On sales order 56772 unit price is 1,439.10, which came after 10% discount on the real price (i.e. 10% discount on 1599.00) and on Sales Order 56772 unit price is 1,599.00

Please add your valuable feedback / comments

Declaimer:

This blog is purely personal and the thoughts expressed here represent only me. The purpose of this blog is to share information and knowledge about Oracle's product which I have come across with my exposure to the product, practice and observations. The blog has been created keeping only one intention of sharing knowledge and for learning purpose. The blog has been created solely as a educational, for storing portions of the vast Oracle knowledge world. Oracle EBS is an Oracle Corp. product and you should contact Oracle directly for any specific fact or issue.

*NOTE: Few articles on this blog are not completely prepared by me, content is edited and complied after referring various sites to make visitor's job easy