This is intended for all audiences using the Receiving Module.
Processing Mode values:
On-line:
This is the most commonly used processing mode. When the user saves a transaction, no other application activity can be performed until the process completes. Either the number of records saved will be indicated for a successful transaction or an error message will be displayed. Uses Receiving Transaction Manager (executable RCVOLTM, located in $PO_TOP/bin).
Immediate:
When the user saves a transaction, the Receiving Transaction Processor concurrent program will automatically start and process the data in the RCV_TRANSACTIONS_INTERFACE table that was created for the Receipt. Control of the form is returned to the User who may then perform other application activity. Transaction errors that occur are written to the PO_INTERFACE_ERRORS table and can be viewed from the Transaction Status Summary. Additional information may be available in the log file for the Receiving Transaction Processor concurrent request (View/Requests). Uses Receiving Transaction Processor (executable RVCTP, located in $PO_TOP/bin).
Batch:
When the user saves a transaction, the data remains in the RCV_TRANSACTIONS_INTERFACE table until the Receiving Transaction Processor concurrent program is run via report submission. Control of the form is returned to the User who may then perform other application activity. When the Receiving Transaction Processor runs, it will process all PENDING records for PROCESSING_MODE=BATCH. Transaction errors that occur are written to the PO_INTERFACE_ERRORS table and can be viewed from the Transaction Status Summary Form.
It is standard functionality to allow Receipt Headers to be saved without existing Lines. The existence of RCV_SHIPMENT_HEADERS records without corresponding RCV_SHIPMENT_LINES do not cause any problems and should not be of concern to the users. Note: 301694.1 - Why Do Receipts Exist Without Receipt Lines/Transactions?
The Receipts form and its associated libraries also perform some validations prior to writing to the RCV_TRANSACTIONS_INTERFACE table. These validation errors will be displayed on the form regardless of the processing mode being used.
The Receiving Transaction Summary and Transaction Status Summary forms should be used to confirm the success or failure of a transaction. In addition to errors, the Receiving Transaction Summary will also display transactions that have Status=PENDING. Although transactions saved with RCV: Processing Mode ON-LINE should not remain in the RCV_TRANSACTIONS_INTERFACE table with Status=PENDING, this can happen on occasion. These transactions may be deleted from this form (using Delete/X Icon, then Save) and processed again. It is possible to see Status=PENDING for transactions save with RCV: Processing Mode IMMEDIATE if the Receiving Transaction Processor has not yet processed the transaction. Typically, they will be processed within a short period of time. On occasion, these records will remain in the RCV_TRANSACTIONS_INTERFACE table with Status=PENDING.
Refer to Note: 303544.1 - How To Remove Pending and Error Transactions from Transaction Status Summary
Unprocessed transactions may affect subsequent processing of transactions for the same document. For example, if a return or correction transaction against a receipt is stuck as PENDING (or RUNNING) in the RCV_TRANSACTIONS_INTERFACE table (form: Transaction Status Summary), corrections and returns may not be allowed for that Purchase Order receipt. If either of the following error messages is displayed on the correction or returns form, then there may be no quantity to correct/return or there are one or more records stuck in RCV_TRANSACTIONS_INTERFACE table (form: Transaction Status Summary):
1. APP-PO-14886 Please enter a quantity less than or equal to the available quantity.
2. APP-PO-14094: No records meet your search criteria
PENDING and RUNNING transactions should be reviewed and removed so as not to affect subsequent transaction processing.
Similarly, if Quantity=10 have been Received for PO Shipment which has Ordered Quantity=100 and there is an unprocessed transaction with Quantity=35 for the same PO Shipment, the Expected Receipts form will show Quantity=55 even though only 10 have been Received:
100 (Ordered Quantity)
-10 (Received Quantity)
-35 (Pending Receive Quantity)
-0 (Canceled Quantity)
__
55
Users should be encouraged to check the Transaction Status Summary form routinely and the technical group should monitor the table RCV_TRANSACTIONS_INTERFACE. Or run scripts in the following note and review results: Note: 263368.1 - Additional Data Gathering Scripts For Records Stuck in RTI.
Destination Type:
The Destination Type column in the Receipt form and the Receiving Transactions form show where the receipt will need to go next to be processed. When the destination type shows Expense, Shop Floor or Inventory, the transaction being entered will be the final transaction or the deliver transaction needed to complete the receiving process. When the destination type shows receiving then the receipt routing is either Standard or Inspection Required, meaning more than one step is needed before the items are delivered.
Destination Type Values:
Receiving: Value displayed when Receipt Routing is Standard Receipt or Inspection Required. The Receiving Transaction form must be used for goods to be delivered.
Expense: Value displayed for an Expense Item or a One-Time Expense Item. Subinventory, Locator, Lot Number and Serial Number entries are not appropriate, therefore not allowed.
Inventory: Value displayed for an Item which will have quantity tracked in Inventory.
Shop Floor: Value displayed for an Outside Processing Item which will be delivered to the shop floor for completion of a wip job.
Explanation of RCV: Processing Modes, Pending Transactions and Destination Types
When receiving transactions are performed, data is written to the RCV_TRANSACTIONS_INTERFACE table (Status=PENDING) for subsequent processing based on the value of Profile RCV: Processing Mode (ON-LINE, IMMEDIATE or BATCH). Although this profile is typically set at the System Level, Users may change this value via Personal Profiles.Processing Mode values:
On-line:
This is the most commonly used processing mode. When the user saves a transaction, no other application activity can be performed until the process completes. Either the number of records saved will be indicated for a successful transaction or an error message will be displayed. Uses Receiving Transaction Manager (executable RCVOLTM, located in $PO_TOP/bin).
Immediate:
When the user saves a transaction, the Receiving Transaction Processor concurrent program will automatically start and process the data in the RCV_TRANSACTIONS_INTERFACE table that was created for the Receipt. Control of the form is returned to the User who may then perform other application activity. Transaction errors that occur are written to the PO_INTERFACE_ERRORS table and can be viewed from the Transaction Status Summary. Additional information may be available in the log file for the Receiving Transaction Processor concurrent request (View/Requests). Uses Receiving Transaction Processor (executable RVCTP, located in $PO_TOP/bin).
Batch:
When the user saves a transaction, the data remains in the RCV_TRANSACTIONS_INTERFACE table until the Receiving Transaction Processor concurrent program is run via report submission. Control of the form is returned to the User who may then perform other application activity. When the Receiving Transaction Processor runs, it will process all PENDING records for PROCESSING_MODE=BATCH. Transaction errors that occur are written to the PO_INTERFACE_ERRORS table and can be viewed from the Transaction Status Summary Form.
It is standard functionality to allow Receipt Headers to be saved without existing Lines. The existence of RCV_SHIPMENT_HEADERS records without corresponding RCV_SHIPMENT_LINES do not cause any problems and should not be of concern to the users. Note: 301694.1 - Why Do Receipts Exist Without Receipt Lines/Transactions?
The Receipts form and its associated libraries also perform some validations prior to writing to the RCV_TRANSACTIONS_INTERFACE table. These validation errors will be displayed on the form regardless of the processing mode being used.
The Receiving Transaction Summary and Transaction Status Summary forms should be used to confirm the success or failure of a transaction. In addition to errors, the Receiving Transaction Summary will also display transactions that have Status=PENDING. Although transactions saved with RCV: Processing Mode ON-LINE should not remain in the RCV_TRANSACTIONS_INTERFACE table with Status=PENDING, this can happen on occasion. These transactions may be deleted from this form (using Delete/X Icon, then Save) and processed again. It is possible to see Status=PENDING for transactions save with RCV: Processing Mode IMMEDIATE if the Receiving Transaction Processor has not yet processed the transaction. Typically, they will be processed within a short period of time. On occasion, these records will remain in the RCV_TRANSACTIONS_INTERFACE table with Status=PENDING.
Refer to Note: 303544.1 - How To Remove Pending and Error Transactions from Transaction Status Summary
Unprocessed transactions may affect subsequent processing of transactions for the same document. For example, if a return or correction transaction against a receipt is stuck as PENDING (or RUNNING) in the RCV_TRANSACTIONS_INTERFACE table (form: Transaction Status Summary), corrections and returns may not be allowed for that Purchase Order receipt. If either of the following error messages is displayed on the correction or returns form, then there may be no quantity to correct/return or there are one or more records stuck in RCV_TRANSACTIONS_INTERFACE table (form: Transaction Status Summary):
1. APP-PO-14886 Please enter a quantity less than or equal to the available quantity.
2. APP-PO-14094: No records meet your search criteria
PENDING and RUNNING transactions should be reviewed and removed so as not to affect subsequent transaction processing.
Similarly, if Quantity=10 have been Received for PO Shipment which has Ordered Quantity=100 and there is an unprocessed transaction with Quantity=35 for the same PO Shipment, the Expected Receipts form will show Quantity=55 even though only 10 have been Received:
100 (Ordered Quantity)
-10 (Received Quantity)
-35 (Pending Receive Quantity)
-0 (Canceled Quantity)
__
55
Users should be encouraged to check the Transaction Status Summary form routinely and the technical group should monitor the table RCV_TRANSACTIONS_INTERFACE. Or run scripts in the following note and review results: Note: 263368.1 - Additional Data Gathering Scripts For Records Stuck in RTI.
Please note that Receipt Numbers (Receipt Headers) exist for these Transactions. Refer to Note: 301694.1 - Why Do Receipts Exist Without Receipt Lines/Transactions?
Destination Type:
The Destination Type column in the Receipt form and the Receiving Transactions form show where the receipt will need to go next to be processed. When the destination type shows Expense, Shop Floor or Inventory, the transaction being entered will be the final transaction or the deliver transaction needed to complete the receiving process. When the destination type shows receiving then the receipt routing is either Standard or Inspection Required, meaning more than one step is needed before the items are delivered.
Destination Type Values:
Receiving: Value displayed when Receipt Routing is Standard Receipt or Inspection Required. The Receiving Transaction form must be used for goods to be delivered.
Expense: Value displayed for an Expense Item or a One-Time Expense Item. Subinventory, Locator, Lot Number and Serial Number entries are not appropriate, therefore not allowed.
Inventory: Value displayed for an Item which will have quantity tracked in Inventory.
Shop Floor: Value displayed for an Outside Processing Item which will be delivered to the shop floor for completion of a wip job.
Note: the Destination Type can be changed if the following profile is set to Yes: 'RCV: Allow routing override'
Comments
Post a Comment