Oracle® Fusion
Applications Materials Management and Logistics Implementation Guide 11g Release 1 (11.1.2) Part Number E20385-02 |
Contents |
Previous |
Next |
This chapter contains the following:
Receiving parameters define receiving preferences at the organization level. General receiving parameters must be set up before you can use Oracle Fusion Receiving for recording and transacting receipts.
This table describes the general receiving parameters.
Receiving Parameter Display Name |
Effect |
---|---|
Ship-to Exception Action |
Determines whether the supplier can put away to a receiving location that differs from the ship-to location. Select one of the following options:
|
ASN Control Action |
Determines the action if receiving against purchase order shipments for which an advance shipment notice (ASN) exists. Select one of the following options:
|
Early Receipt Tolerance in Days |
Sets the maximum acceptable days early for a receipt. |
Late Receipt Tolerance in Days |
Sets the maximum acceptable days late for a receipt. |
Receipt Days Exceed Action |
Determines the action for when receipts are earlier or later than the allowed number of days. Select one of the following options:
|
Over-Receipt Tolerance |
Determines how the application handles receipts that exceed the quantity received tolerance. Select one of the following options:
Note You can also set up quantity tolerances for the item at the purchase order level during purchase order creation. If tolerances are set up at both the purchase order level and the organization level, the tolerance settings at the purchase order level override the tolerance settings at the organization level. |
Receipt Routing |
Sets the default receipt routing that you assign goods. You can override this option at receipt time by changing the destination type for specific suppliers, items, and orders if the Allow Routing Override user profile is enabled. Select one of the following options:
|
Allow substitute receipts |
If enabled, allows the receipt of defined substitutes in place of ordered items. You must define substitute items on the Item Relationships page before you can receive them. You can override this option for specific suppliers, items, and orders. |
Allow unordered receipts |
If enabled, allows receipt of an item without documentation. If you select this option, you can later match the unordered receipt to the appropriate document number. If you enable this option, you can override it for specific suppliers and items. |
Enforce blind receiving |
If enabled, the quantity due or quantity ordered for each shipment is not visible on the receipt. Blind receiving helps you ensure that receivers record the exact amount they receive. Oracle Fusion Receiving ignores all quantity receipt tolerances to help ensure that you can receive the exact amount that the supplier shipped. |
Print receipt traveler |
If enabled, allows automatic printing of summary reports of receipt performance. |
Include closed purchase orders for receipts |
If enabled, allows receiving of closed purchase orders. |
Allow routing override |
If enabled, allows overriding the receipt routing at receipt time. You can override this option at receipt time by changing the destination type for specific suppliers, items, and orders. |
Process all lines together |
If enabled, ensures that individual lines are processed if all expected lines do not arrive. |
Receiving parameters define receiving preferences at the organization level. Receipt number receiving parameters must be set up before you can use Oracle Fusion Receiving for recording and transacting receipts.
This table describes the receipt number receiving parameters.
Receiving Parameter Display Name |
Effect |
---|---|
Generation |
Defines the receipt number generation method for receipt numbers. Choices include Automatic and Manual. |
Type |
Defines the receipt number type that you want to use for receipt numbers. Options include Numeric or Alphanumeric. If you choose the manual receipt number generation option, you can choose numeric or alphanumeric numbers. You can change the receipt number type from numeric to alphanumeric at any time. You can change the receipt number type from alphanumeric to numeric only if all of your current receipt numbers are numeric. Note If you choose automatic receipt number generation, you can generate only numeric receipt numbers, but you can still import either numeric or alphanumeric values from another system. Note If you have any alphanumeric documents in your system, you must choose the alphanumeric option as your number type, regardless of your numbering method. Note The ordering of numeric values in lists of values can appear random when you use the alphanumeric number type. If you are using alphanumeric numbering, consider entering all numeric values with the same number of digits. For example, if you can assume all numeric values contain six digits, you should enter the first value as 000001. |
Next Number |
Sets the starting value that you want to use for generating unique sequential receipt numbers if you choose the automatic receipt number generation method. The application displays the next receipt number that will be used for a new receipt creation. You cannot enter this field if you choose the manual receipt generation method. |
Receiving parameters define receiving preferences at the organization level. Receiving parameters for return material authorizations (RMAs) must be set up before you can use Oracle Fusion Receiving for recording and transacting receipts.
This table describes the RMA receiving parameters.
Receiving Parameter Display Name |
Effect |
---|---|
Receipt Routing |
Defines the default RMA receipt routing that you assign goods. Choices include Direct Delivery, Standard Receipt, or Inspection Required. |
RMA Validate Lots |
Determines restriction level for RMA. Choices include:
|
Validate Serial Numbers |
If enabled, restricts the list of serial numbers displayed for an RMA line to valid serial numbers only. |
Use these scenarios to understand how early and late receipt tolerances work for receiving items.
You enter 3 days as the early receipt tolerance. The promise date is Friday. Therefore, you can receive the item on Tuesday.
You enter 3 days as the early receipt tolerance. You set the Receipt Days Exceed Action parameter to None. You try to receive a receipt 5 days before the promise date, and the application lets you receive the receipt because no receipt date action is enforced.
You enter 3 days as the early receipt tolerance. You set the Receipt Days Exceed Action parameter to Reject. You try to receive a receipt 5 days before the promise date, and the application rejects the receipt and displays an error.
You enter 3 days as the early receipt tolerance. You set the Receipt Days Exceed Action parameter to Warning. You try to receive a receipt 5 days before the promise date, and you receive a warning message, but you are permitted to receive the receipt.
Note
Oracle Fusion Receiving uses regular calendar days (including weekends and holidays) in this calculation. If the promise date does not exist, the application uses the need-by date.
You enter 2 days as the late receipt tolerance. The promise date is a Monday. Therefore, you can receive the item on Wednesday.
You enter 2 days as the late receipt tolerance. You set the Receipt Days Exceed Action parameter to None. You try to receive a receipt 5 days after the promise date, and the application lets you receive the receipt because no receipt date action is enforced.
You enter 2 days as the late receipt tolerance. You set the Receipt Days Exceed Action parameter to Reject. You try to receive a receipt 5 days after the promise date, and the application rejects the receipt and displays an error.
You enter 2 days as the late receipt tolerance. You set the Receipt Days Exceed Action parameter to Warning. You try to receive a receipt 5 days after the promise date, and you receive a warning message, but you are permitted to receive the receipt.
Note
Oracle Fusion Receiving uses regular calendar days (including weekends and holidays) in this calculation. If the promise date does not exist, the application uses the need-by date.