APPS.RCV_TRANSACTIONS_SV dependencies on STANDARD

Line 10: of what is does. To use this for standard

6:
7: DESCRIPTION: Validates the receiving controls for express. There
8: are restrictions for this function since express
9: doesn't validate all controls. Here is a description
10: of what is does. To use this for standard
11: functionality, we'll have to add the quantity
12: tolerances and the ship-to-location and add a parameter
13: for express/standard receiving.
14:

Line 13: for express/standard receiving.

9: doesn't validate all controls. Here is a description
10: of what is does. To use this for standard
11: functionality, we'll have to add the quantity
12: tolerances and the ship-to-location and add a parameter
13: for express/standard receiving.
14:
15:
16: 1. Receiving controls are only checked for vendor receipts. Intransit
17: shipments cannot be rejected and we have not way to define org->org

Line 22: 4. Standard receipts will be created for the ship-to location

18: receiving controls.
19: 2. Controls are only checked if the exception level is 'REJECT'
20: 3. Quantity tolerances are not checked. It is not possible to
21: over-receive an express receipt.
22: 4. Standard receipts will be created for the ship-to location
23: specified on the PO so the 'enforce ship-to location' control
24: is not tested.
25: 5. Routing controls are checked for both Vendor sourced and
26: intransit receipts.

Line 44: 1 = Standard Receipt

40:
41: X_expected_receipt_date IN DATE What is the promised/need by date
42: X_transaction_date IN DATE When was this transaction processed
43: X_routing_header_id IN NUMBER What is the routing for this trans
44: 1 = Standard Receipt
45: 2 = Inspection Required
46: 3 = Direct Receipt
47: X_po_line_location_id IN NUMBER What is the ling location to get
48: the receiving controls