OE-TYP: Order Types - FAQ

OE-TYP: Order Types - FAQ

FREQUENTLY ASKED QUESTIONS
-----------------------------
 
1.  Why can't I apply a discount to an order line when using a specific Order
    Type?

    If the 'Enforce List Price' flag is enabled for the Order Type, you cannot
    apply discounts to the order line.  Users cannot override the selling
    price, unless the profile option, OE: Discounting Privilege is set at the
    appropriate level.

2.  You have order types that are continuing to use an old order
    sequence while new order types are using the new sequence. 
    For example, you have an order number source defined as STANDARD,  
    which has an end date of 27-NOV-97, but the system seems to have not
    recognized the end date and keeps generating the numbers for any orders
    created to this point of time.

3.  In Oracle Order Entry, you are trying to define Order Types.  When
    you SAVE the order type, you get the following error message:

    APP-01016  Routine fdfrks unknown structure id 0 for
    flexfield code gl# with application id =101

4.  When you are renewing service in Oracle Service, you open the form
    Renew Service.  Under the new order zone, you select the order type by
    clicking on the list of values.  You then see a list of values which
    includes Maintenance Service (an existing order type) but when you query
    by entering Maintenance Service you see
    the following message:

    APP-03020 Invalid Order Type

    You expect to be able to select an existing order type without
    receiving an error.

    Please see Note 1080615.6 for the solution.

5. Creating a new order, choosing an order type returns message:
   NOTE: oe_invalid_order_type
   Press [OK] to continue but note keeps appearing in endless loop

   Please see Note 120100.1 for the solution.

6. When using a particular sales order type the list of values is not
   available in the sales tax field in the  sales oder form.

7. You are trying to create an Order Type in a new Operating Unit.

   The Navigation Path used is
   Setup --&gt Orders --&gt Types
   from the Order Entry Super User responsibility.

   When you try to save the order type, you get the following
   error message:

   "APP-01206: This record already exists. You entered a duplicate
   value or sequence of values that must be unique for every record."
   You cannot save the new order type as a result of the above error.

   Please see Note 132187.1 for the solution.

8.  If you change the order type,  will it effect open orders?

    If you change the order type for a order,  it will not effect open
    orders,but you cannot change the order type once an order is booked .
    You will have to close the order that are open and the newly created
    order type can be used for all newly created orders.

9.  When defining an order type name in a new organization, you receive
    an error message that states "This name already exists".

    The primary key to a sales order is segment 1 = Order Number, segment 2
    = Order Type, and segment 3 = Order Source. It does not include
    organization as the key. Define a unique Order Type Name accross all
    organizations to avoid conflict.

10. You have created your order number sources.
    For example,

    Name Description Starting number Last Assigned number
    Regular Customer Orders 100000 861761
    Returns All Returns 900000 1014398

    What will happen when the  regular customer orders reach 900000? Will
    the system start over and go back to 100000 or will 900000 be duplicated
    or will returns and orders work simultaneously in the 1000000 range?

    No, the system does not loop back when 'Regular - Customer Orders' reach
    900000. It continues, and does NOT clash with 'Returns - All Returns'.

    Why? This is because:

    1) System takes (Order Number, Order Type, Order Source [=ORDER ENTERY])
    for unique identification of an order. (eg: when SO is demanded,
    these three values are populated in mtl_sales_orders, mtl_demand tables)

    2) An Order Source is assigned to an Order Type
    3) Thus, (1) & (2) can be interpreted as that unique identification is
    for order_number and order_source.

    What is the implication of this?

    1) When you query, eg: order number = 900578, in the 'Orders,
    Returns'(note the form. name which is self explanatory), you would get
    two orders. One of them would be a Regular order, while the other is a
    Return order.

11. If you have an order number sequence, for example, that starts from 1000
    and ends with order number is 86584. The Order Number Source Name is
    REGULAR and due to a change in the business flow, an adjustment is needed
    to use the order numer sequence starting with 1000000.
   
    What is the procedure to make this change and allow the existing order type
    to use the new Order Number source?

    You cannot change an order number source once the record has been saved. 
    This is designed functionality to maintain data integrity.  You must
    define a new order type for the new order number source.

转载 http://space.itpub.net/spacecp.php?action=spaceblogs&op=add&openwindow=1

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/7434747/viewspace-677282/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/7434747/viewspace-677282/