Quality Control and Receipt Adjustment - Calculations

PO230E

A. Housekeeping

1. See Common Processing Routines - Housekeeping of this manual for a general discussion of the Housekeeping subroutine. Processing specific to this program is described below.

2. A parameter list is set up for the fast path and help screen parameters.

3. Key lists are defined for each file retrieved by the program.

4. Workfields are defined and program constants are initialized. The Mode parameter is checked to determine whether Quality Control processing or Receipt Adjustment processing is to be performed; an indicator is set to display the appropriate screens.

5. The following records are retrieved from the Reference file (REFERP):

a. The date format record (category 049) is retrieved. If this record is not found, the date format defaults to MMDDYY.

b. The default company/warehouse is retrieved from the workstation assignment record (category 428). This company/warehouse is validated against the array of authorized company/warehouses for the user.

c. The decimal field precision record (category 446) is retrieved.

d. All company/warehouses to which the user is authorized are retrieved from the user company/warehouse authorization record (category 409) and loaded into an array. If no records are found for the user, a flag is set authorizing the user to all company/warehouses.

e. The JIT system defaults record (C11) is retrieved to determine if the JIT Time Reporting application is in effect.

f. The applications installed record (category 012) is retrieved to determine if the Shop Floor Control, Product Costing, Inventory Accounting, Job Control, Expert Configurator, and Order Processing modules are installed. If Job Control is installed, the job/group number will be displayed for job-controlled parts (as long as the purchase order is not a phantom order). If the Expert Configurator module is installed, the configuration code will be displayed for configured parts, as long as the Purchase Order is not a phantom order.

g. The Inventory Accounting system defaults record (category 436) is retrieved for the positive and negative adjustment codes used in system-generated adjustments.

h. If the Inventory Accounting Application is installed, the Inventory Accounting close grace period record (category 456) is retrieved.

i. The following categories are retrieved and stored in arrays for access during processing:

· Approval status codes (category 499)

· Quantity control status codes (category 466)

· Quality control status codes (category 467)

· Order types (category 401)

· Purchase order types (category 437)

j. The purchasing defaults record (category D32) is retrieved and the Dispute Tolerance Amount is saved.

k. The current purchasing calendar record (category 490) and the previous year purchasing calendar record (category 471) are retrieved. The Purchasing statistics posting periods record (category 488) is also retrieved. The Current Period End Date and Last Period End Date are calculated and formatted.

l. The system options record (category 133) is retrieved and checked for both multi-currency environment and address format.

m. The multiple/location priority code default is retrieved (category Y34) when new multiple location records for a part are being created.

6. The following records are retrieved from the System Control file (CT100M):

a. The Lot Option is retrieved from the first Inventory Control control record (ICCTL1).

b. The valid balance types are retrieved from the second Inventory Control control record (ICCTL2).

c. If the Shop Floor Control application is installed, the Automatic Move/Receive Option is retrieved from the Shop Floor Control control record (SFCTL1). The Shop Floor Audit Trail, Manufacturing Order, and Labor Requirements files are opened.

7. All valid company/warehouse combinations, plant name and plant flag are retrieved from the Warehouse Description file (IC170M) and stored in an array. The default company/warehouse retrieved in step 5.b. above is validated against this array.

B. Mainline

The Receipt Quality Control and Receipt Adjustment program consists of two conversations with similar processing: the Receipt Quality Control conversation, which is used to add and change quality control data, and the Receipt Adjustment conversation, which is used to update inventory balances. Which conversation will be processed is determined by the parameter passed from the Purchasing Control Application Menu.

Processing within each conversation is determined by the screen flow. The user is given a great deal of flexibility, through the use of function keys, to move from one screen to another. Therefore, the remainder of this program description will discuss the processing by screen. Screens in the two conversations that are processed similarly are grouped together.

Receipt Quality Control Function Select screen (PO230S01)
Receipt Adjustment Function Select screen (PO235S01)

The Function Select screen allows the user to choose the receipt he/she wishes to process. The following processing is performed:

1. The Function Select screen is formatted and displayed.

2. The Function Select screen is validated. See the Purchasing User Manual, File Maintenance Screens-Purchasing Control, for validation rules.

3. If all entries are valid, the Purchase Order Header file (PO180M1) and Purchase Order Receipt Header file (PO210M1) are logically locked. The Purchase Order Receipt Line file (PO210M2) is accessed to retrieve the receipt records that are eligible for quality control or receipt adjustment. These records are then loaded into the recap screen subfile.

a. If a receipt line is closed, invoiced, has a quantity control status of not complete, or has a counted quantity of zero, the line is not eligible for quality control processing.

b. If a receipt line is closed, invoiced, has a quantity control status of not complete, has a counted quantity of zero, or has a quality control status of waiting control, the line is not eligible for receipt adjustment processing.

4. If a valid Receipt Line Number was entered on the Function Select screen, the detail screen is displayed directly. If only a Receipt Number was entered, however, the recap screen is displayed.

5. In a multi-currency environment, the appropriate exchange rate is set. The exchange rate equals 1 in a single currency environment.

Receipt Quality Control Header Screen (PO230S02)

The Header screen is displayed only for Receipt Quality Control processing. It displays data pertaining to the entire receipt. The following processing is performed:

1. The header screen is formatted and displayed. If comment records exist for the header on the Purchase Order Receipt Comment file (PO210M4), the Comments Flag is set to Y.

2. The header screen is validated. See the Purchasing User Manual, File Maintenance Screens-Purchasing Control, for validation rules.

3. The following conditions determine which screen is displayed next if the ENTER key is pressed:

Conditions		Screen Displayed
The Comments Flag equals Y		Comment screen (PO230S05)
The previous screen was the detail screen and the Comments Flag equals N		Detail screen (PO230S03)
The previous screen was the recap screen and the Comments Flag equals N		Detail screen (PO230S03)

4. F10 - Prompt displays the Function Select screen (PO230S01).

5. If this is a receipt for multiple orders, the function key F18 allows the user to call the Multiple Purchase Order Window (PORCTWIN). This window displays all purchase orders for the receipt.

Receipt Quality Control Detail screen (PO230S03) (non-phantom orders)

Receipt Adjustment Detail screen (PO235S02) (non-phantom orders)

The detail screen allows the modification of receipt line records and the update of stock balances and purchasing statistics. The following processing is performed:

1. The detail screen is initialized for display using receipt line values. If comment records exist for the receipt on the Purchase Order Receipt Comment file (PO210M4), the Comments Flag is set to Y.

2. The detail screen is displayed.

3. Function keys are available to display the previous or next receipt line. If any errors are found in the detail screen, all function keys are disabled except F15 - Rekey Data.

4. The part on the purchase order line, for location-controlled parts, can be received into a specific location using F21 - Display Stock Location.

5. The detail screen is validated. See the Purchasing User Manual, File Maintenance Screens-Purchasing Control, for validation rules.

6. The Receiving Type Code is used to access the Reference File (category 475) for the value of the Quality Control Location Utilized Flag. If the Quality Control Location utilized value is Y and it was not already retrieved in a previous line transaction, the quality control location is retrieved from the Reference File (category 481).

7. The Transaction Quantity Workfield is calculated as follows:

a. The Transaction Quantity is moved to the Transaction Quantity Workfield.

b. If the Adjustment Type is not equal to Accepted, the Transaction Quantity Workfield is multiplied by -1. If the Reversal Code equals R, the Transaction Quantity Workfield is multiplied by -1. Subsequent discussion of the Transaction Quantity is in reference to the Transaction Quantity Workfield.

8. The files to be updated are determined based on the Receipt Adjustment Code, Receiving Type, Part Type, and Order Type (direct ship or warehouse ship). If a file is to be updated, its update flag workfield is set to Y. Files to be updated that were not previously locked during validation are locked.

9. Calculations are performed. During all calculations, overflow is monitored and causes a critical error.

a. If a stock transfer is being processed from the quality control stock location to a regular stocking location or vice versa, calculations are performed on the logical "from" Multiple Location file (IC130ML5).

(1) If the Transaction Quantity is negative, the Transaction Quantity is subtracted from the Activity Since Last Cycle Count (ACTSLC).

(2) The Transaction Quantity is subtracted from the appropriate balance quantity workfield.

(3) If a balance quantity is driven negative, a warning message is written to the Inventory Control Transaction Error file (IC505AP).

b. If the Multiple Location "From" Update Flag equals Y, calculations are performed on the "to" Multiple Location file (IC130M). This record is updated even if a stock transfer is not being processed.

(1) If the Transaction Quantity is positive, it is added to the Activity Since Last Cycle Count (LLSLAC).

(2) The Transaction Quantity is added to the appropriate balance quantity workfield.

(3) If a balance quantity is driven negative, a warning message is written to the Inventory Control Transaction Error file (IC505AP).

c. If the Warehouse Balance "From" Update Flag equals Y, calculations are performed to back out quantities from the quality control balance type (or to add quantities if the Transaction Quantity is negative).

(1) The Transaction Quantity is subtracted from the appropriate balance quantity.

(2) A warning message is written if a balance quantity is driven negative.

d. If the Warehouse Balance "To" Update Flag equals Y, calculations are performed to update the Warehouse Balance file. This record is updated even if a stock transfer is not being processed.

(1) The Transaction Quantity is added to the appropriate balance quantity.

(2) A warning message is written if a balance quantity is driven negative.

e. If the Release Update Flag equals Y (that is, a return with replacement is being processed), calculations are performed on the balance due and received quantity of the purchase order release.

(1) If the Transaction Quantity is positive (a reversal of a return with replacement transaction is being processed), the file is positioned on the release with the oldest Due Date. If the transaction quantity is negative, the file is positioned on the release with the most recent Due Date. The absolute value of the Transaction Quantity is moved to the Release Quantity to be Updated (RELQTY).

(a) If the Transaction Quantity is positive, the Balance Due (PLBDSK) is greater than zero, and the Release Status is not closed, the release is processed:

(2) If the Transaction Quantity is positive, the Release Quantity to be Updated (RELQTY) and Balance Due (PDBDSK) are used to determine if the release should be updated. If the Balance Due is greater than zero and the Release Status is not closed, the New Balance calculations are performed.

(a) If the Release Quantity to be Updated equals the Balance Due (PDBDSK):

(i) The Release Quantity to be Updated is added to the Received Quantity.

(ii) The Balance Due is set to zero.

(iii) The Release Quantity to be Updated is set to zero.

(b) If the Release Quantity to be Updated is less than the Balance Due:

(i) The Release Quantity to be Updated is added to the Received Quantity.

(ii) The Release Quantity to be Updated is subtracted from the Balance Due.

(iii) The Release Quantity to be Updated is set to zero.

(i) The Received Quantity is set to the Release Quantity.

(ii) The Balance Due is subtracted from the Release Quantity to be Updated.

(iii) The Balance Due is set to zero.

(3) If the Transaction Quantity is negative, the Release Quantity to be Updated (RELQTY), Received Quantity (PDRCSK) and Release Quantity (PDQTSK) are used to determine how the balance calculations should be performed. The release is not processed if it is closed.

(a) If the Release Quantity to be Updated is greater than or equal to the Received Quantity:

(i) The Balance Due is set to the Release Quantity.

(ii) The Received Quantity is subtracted from the Release Quantity to be Updated.

(iii) The Received Quantity is set to zero.

(b) If the Release Quantity to be Updated is less than the Received Quantity, the Release Quantity to be Updated is subtracted from the Received Quantity.

(i) If the Release Quantity is greater than or equal to the new Received Quantity, the Received Quantity is subtracted from the Release Quantity to give the Balance Due, and the Release Quantity to be Updated is set to zero.

(ii) If the Release Quantity is less than the new Received Quantity, the Release Quantity to be Updated is set to zero.

f. The Transaction Quantity is added to the Purchase Order Line Received Quantity.

g. An overshipment may be processed if the Quantity Received is greater than the Quantity Ordered. If an overshipment transaction is being processed, calculations are performed on the purchase order line, purchase order release, and parcel file quantities.

(1) The Transaction Quantity is added to the purchase order release line Received Quantity and the record is updated.

(2) The file pointer is positioned on the purchase order release record with the oldest due date. The Transaction Quantity is then added to the Received Quantity and the record is updated.

(3) Parcel file calculations are then performed:

(a) The absolute value of the Transaction Quantity is moved to the Parcel Quantity to be Updated.

(b) The file pointer is positioned on the last parcel file record.

(c) An extended Quantity per Parcel Line is calculated by multiplying the Number of Parcels by the Counted Quantity per Parcel.

(d) If the Transaction Quantity is less than zero, the following processing is performed:

(i) If the Parcel Quantity to be Updated is less than the Extended Quantity per Parcel Line, the Parcel Quantity to be Updated is subtracted from the Extended Quantity per Parcel Line. The Parcel Quantity to be Updated is set to zero. The Number of Parcels is set to 1 and the Extended Quantity per Parcel Line is moved to Counted Quantity per Parcel. The parcel record is updated.

(ii) If the Parcel Quantity to be Updated is greater than the Extended Quantity per Parcel Line, the Extended Quantity per Parcel is subtracted from the Parcel Quantity to be Updated. One is added to the Number of Parcel Records Deleted counter. The parcel record is deleted.

(e) If the Transaction Quantity is greater than zero, the following processing is performed:

(i) The Parcel Quantity to be Updated is added to the Counted Quantity per Parcel. The Number of Parcels is set to 1. The Parcel Quantity to be Updated is set to zero. The parcel record is updated.

(ii) If the Parcel Quantity to be Updated is not equal to zero, the next parcel record is processed in the same manner.

10. Table 230-1 below illustrates the file updates when processing Adjustment Type A (accepted) transactions.

CONDITIONS		UPDATES
Transaction Description	QC Location Used	Accepted Quantity	Rework Quantity	Reject Quantity	Non-Disp Quantity	QC Location Quantity	Stock Location Quantity
Accept Inventory	Yes or No	+		-			+
Rework Inventory	Yes or No		+
Non-dispositioned Inventory Accepted	Yes	+			-	-	+
Non-dispositioned Inventory Rework	Yes	+	+		-	-	+
Non-dispositioned Inventory Accepted	No	+			-
Non-dispositioned Inventory Rework	No	+	+		-

+ = Increased by Transaction Quantity

- = Decreased by Transaction Quantity

Table 230-1: "Accepted" Inventory Updates

11. Table 230-2 below illustrates the file updates when processing Adjustment Type R (reject) transactions.

CONDITIONS			UPDATES
Transaction Description	QC Location Used	Accepted Quantity		Rejected Quantity	Return Quantity	Non-Disp Quantity	QC Location Quantity	Stock Location Quantity	Balance Due	Received Quantity
Scrap Inventory	Yes or No	-		+				-
Return Inventory, No Replacement	Yes or No	-			+			-
Return Inventory, For Replacement	Yes or No	-			+			-	+	-
Non-dispositioned Inventory Scrap	Yes			+		-	-
Non-dispositioned Inventory Returned, No Replacement	Yes				+	-	-
Non-dispositioned Inventory Returned, For Replacement	Yes				+	-	-		+	-
Non-dispositioned Inventory Scrap	No			+		-		-
Non-dispositioned, Inventory Returned, No Replacement	No				+	-		-
Non-dispositioned Inventory Returned, For Replacement	No				+	-		-	+	-

+ = Increased by Transaction Quantity

- = Decreased by Transaction Quantity

Table 230-2: "Rejected" Inventory Updates

12. Table 230-3 below illustrates the file updates when processing Overshipment transactions.

CONDITIONS		UPDATES
Transaction Description	QC Location Used	Accepted Quantity	Non-Disp Quantity	Counted Quantity	QC Location Quantity	Stock Location Quantity	Received Quantity
Overshipment	Yes or No	-		-		-	-
Non-dispositioned Inventory Overshipment	Yes		-	-	-		-
Non-dispositioned Inventory Overshipment	No		-	-		-	-

- = Decreased by Transaction Quantity

Table 230-3: "Overshipment" Inventory Updates

13. Other files are updated as appropriate.

a. The Purchase Order Receipt Line file (PO210M2) is updated with the new quantities.

b. The recap screen subfile is updated with new display values.

c. The Vendor Purchase History file (PO290M) is updated.

d. Statistics updates are performed on the Item/Vendor Statistics file (PO280M) and the Item/Buyer Statistics file (PO260M). If a previous purchasing period is being processed (the Receipt Date is less than or equal to the Last Purchasing Period Posted Ending Date), the Item/Vendor Analysis file (PO270M) and Item/Buyer Analysis file (PO300M) are also updated.

e. Audit trail records are formatted and written as follows:

(1) Records are written to the Purchase Order Receipt Line Audit Trail file (PO210BP2).

(2) If any inventory left or entered the warehouse as a result of the transaction, records are written to the Purchase Order Receipt Audit Trail file (IC140BP) and Purchase Order Receipt Transaction Register file (IC140CP).

(3) If a transfer between stocking locations was processed, records are written to the Stock Transfer "From" Audit Trail file (IC120BP2), Stock Transfer "From" Transaction Register file (IC120CP2), Stock Transfer "To" Audit Trail file (IC120BP3), and Stock Transfer "To" Transaction Register file (IC120CP3).

(4) If a system-controlled adjustment was detected in the warehouse balance moving average calculation, records are written to the Inventory Adjustment Audit Trail file (IC120BP1) and Inventory Adjustment Transaction Register file (IC120CP1). Warning messages are written to the Inventory Control Transaction Error file (IC505AP).

14. The following conditions determine which screen is displayed next if the ENTER key is pressed:

Conditions		Screen Displayed
The Comments Flag equals Y (Quality Control only)		Comment screen (PO230S05)
The Comments Flag equals N		Recap screen (PO230S04 or PO235S03)

Receipt Quality Control Detail screen (Phantom Order) (PO230S3A)
Receipt Adjustment Detail screen (Phantom Order) (PO235S2A)

The phantom order detail screen allows the modification of receipt line records and the update of purchasing statistics. The specific phantom order release to be updated is selected by the user by placing an X in the Select field of the parcel subfile. The following processing is performed:

1. The phantom order detail screen is initialized for display using receipt line values and parcel file records.

a. If comment records exist for the receipt on the Purchase Order Receipt Comment file (PO210M4), the Comments Flag is set to Y (Receipt Quality Control only).

b. The Purchase Order Receipt Parcel file (PO210M3) is accessed and subfile fields are formatted from file field values. The Purchase Order Release Detail file (PO180M3) and the Labor Requirements file (IC125ML2) are accessed for the Due Date, Release Status, and Last Operation Flag. The record is then written to the subfile and the process continues until all of the Parcel File records have been written to the subfile.

2. The phantom order detail screen is displayed.

3. Function keys are available to display the previous or next receipt line. If any errors are found in the detail screen, all function keys are disabled except F15 - Rekey Data.

4. The part on the purchase order line, for location-controlled parts, can be received into a specific location using F21 - Display Stock Location.

5. The detail screen is validated. See the Purchasing User Manual, File Maintenance Screens-Purchasing Control, for validation rules.

6. The files to be updated are determined based on the Receipt Adjustment Code and Receiving Type. If a file is to be updated, its update flag workfield is set to Y. Files to be updated that were not previously locked are locked. A logical locking record is written to the Manufacturing Order Receipt Transaction file (IC130DP) to lock the labor requirements records of the manufacturing order being processed.

7. Calculations are performed. During all calculations, overflow is monitored and causes a critical error.

a. If the Release Update Flag equals Y (that is, a return with replacement is being processed), new quantities are calculated for the purchase order line and release. The absolute value of the Transaction Quantity is moved to the Release Quantity to be Updated. The purchase order release balance due and received quantities are updated as follows:

(1) If the Transaction Quantity is negative, the Release Quantity to be Updated is added to the Balance Due. If the Balance Due is greater than the Release Quantity, the Balance Due is set to the Release Quantity. The Release Quantity to be Updated is subtracted from the Received Quantity.

(2) If the Transaction Quantity is positive, the Release Quantity to be Updated is subtracted from the Balance Due. If the Balance Due is negative, the Balance Due is set to zero. The Release Quantity to be Updated is added to the Received Quantity. The Transaction Quantity is added to the Purchase Order Line Received Quantity.

b. An overshipment transaction may be processed if the Quantity Received on the release is greater than the Release Quantity. If an overshipment transaction is being processed, calculations are performed on the purchase order line, purchase order release, and parcel line quantities.

(1) The Transaction Quantity is added to the purchase order line Received Quantity, and the record is updated.

(2) The file pointer is positioned on the purchase order release record with the oldest due date. The Transaction Quantity is then added to the Received Quantity and the record is updated.

(3) The parcel file quantity is calculated. An Extended Quantity per Parcel Line is calculated by multiplying the Number of Parcels by Counted Quantity per Parcel. The Transaction Quantity is added to the Extended Quantity per Parcel Line. The Number of Parcels is set to 1 and the Extended Quantity per Parcel Line is moved to Counted Quantity per Parcel. The parcel record is updated.

8. If processing a purchase order for a part that had a production type of MRP at the time of the phantom order creation, and the Shop Floor Control application is installed, the Labor Requirements file (IC125M) is updated for a non-stock transfer and non-rework transaction.

a. The Transaction Quantity is added to the Quantity Complete. If a scrap transaction is being processed, the Transaction Quantity is added to the Quantity Scrap and Cumulative Quantity Scrap.

b. In addition, if the Automatic Move/Receive Option on the System Control file (CT100M) has been specified and the last operation is not being processed, the Transaction Quantity is added to the Quantity Available for the Next Operation.

c. Activity is checked and, if no activity has been reported, the Activity Reported Flag (LRACTR) is set to N and the Actual Start Date is set to zero. Otherwise, the Activity Reported Flag is set to Y and the Actual Start Date is set to the Transaction Date.

d. If activity has been reported and the Actual Start Date is greater than the Transaction Date, the Actual Start Date is set to the Transaction Date.

e. If the Automatic Move/Receive Option has been specified and if not the last operation of the order, the Quantity Available for the Next Operation is updated.

f. The Activity Reported Flag and Actual Start Date are updated for the next operation in the same manner as for the previous operation.

g. If a scrap transaction is being processed, the Cumulative Scrap Quantities on subsequent labor requirement records for the same manufacturing order are updated. The Order Reschedule Flag is set and the Cumulative Scrap Quantity is updated on the Manufacturing Order file (IC100ML1).

9. If processing a purchase order for a part that had a production type of JIT at the time of the phantom order creation, and JIT time reporting is in effect, an audit trail record is formatted and written to the JIT Shop Reporting Audit Trail file (JT200BP1) for each phantom order release processed.

10. Table 230-4 illustrates the file updates when processing Adjustment Type A (accepted) transactions.

CONDITIONS		UPDATES
Transaction Description	QC Location Used	Accepted Quantity	Rework Quantity	Reject Quantity	Non-Disp Quantity	QC Location Quantity	Stock Location Quantity	Quantity Complete
Accept Inventory	Yes or No	+		-			+(2)	+(1)
Rework Inventory	Yes or No		+
Non-dispositioned Inventory Accepted	Yes	+			-	-(2)	+(2)
Non-dispositioned Inventory Rework	Yes	+	+		-	-(2)	+
Non-dispositioned Inventory Accepted	No	+			-
Non-dispositioned Inventory Rework	No	+	+		-

+ = Increased by Transaction Quantity

- = Decreased by Transaction Quantity

Table: 230-4: “Accepted” Inventory Updates (Phantom Orders)

11. Table 230-5 below illustrates the file updates when processing Adjustment Type R (reject) transactions.

CONDITIONS

UPDATES

Transaction Description

QC
Location
Used

Accepted Quantity

Rejected Quantity

Return Quantity

Non-Disp
Quantity

QC Location Quantity

Stock Location Quantity

Balance Due

Received Quantity

Scrap Inventory

Yes or No

-(2)

-(1)

Return Inventory, No Replacement

Yes or No

-(2)

-(1)

Return Inventory, For Replacement

Yes or No

-(2)

-(1)

Non-dispositioned Inventory Scrap

Yes

-(2)

-(1)

Non-dispositioned Inventory Returned, No Replacement

Yes

-(2)

-(1)

Non-dispositioned Inventory Returned, For Replacement

Yes

-(2)

-(1)

Non-dispositioned Inventory Scrap

-(2)

-(1)

Non-dispositioned, Inventory Returned, No Replacement

-(2)

-(1)

Non-dispositioned Inventory Returned, For Replacement

-(2)

-(1)

+ = Increased by Transaction Quantity

- = Decreased by Transaction Quantity

Table 230-5: “Rejected” Inventory Updates (Phantom Orders)

12. Table 230-6 below illustrates the file updates when processing overshipment transactions.

CONDITIONS		UPDATES
Transaction Description	QC Location Used	Accepted Quantity	Rework Quantity	Reject Quantity	Non-Disp Quantity	QC Location Quantity	Stock Location Quantity	Quantity Complete
Overshipment	Yes or No	-		-		-	-	-(1)
Non-dispositioned Quantity-Overshipment	Yes		-	-	-		-	-(1)
Non-dispositioned Quantity- Overshipment	No		-	-		-	-	-(1)

- = Decreased by Transaction Quantity

Table 230-6: "Overshipment" Inventory Updates (Phantom Orders)

13. The Purchase Order Receipt Line file (PO210M2) is updated with the Transaction Quantity.

14. The Vendor Purchase History file (PO290M) is updated.

15. Purchasing statistics are updated on the Item/Vendor Statistics file (PO280M) and Item/Buyer Statistics file (PO260M). If a previous purchasing period is being processed (the Receipt Date is less than the Last Purchasing Period Posted Ending Date), the Item/Vendor Analysis file (PO270M) and Item/Buyer Analysis file (PO300M) are also updated.

16. Audit trail records are formatted and written for the following files:

a. A record is written to the Purchase Order Receipt Line Audit Trail file (PO210BP3).

b. If the Labor Requirements file (IC125M) was updated, a record is written to the Shop Floor Control Audit Trail file (SF120BP1).

c. If a phantom order for a part that had a production type of JIT at the time of the order creation, a record is written to the JIT Shop Reporting Control Audit Trail file (JT200BP1).

d. If any inventory left or entered the warehouse as a result of the transaction, records are written to the Purchase Order Receipt Audit Trail file (IC140BP) and Purchase Order Receipt Transaction Register file (IC140CP).

e. If a transfer between stocking locations was processed, records are written to the Stock Transfer "From" Audit Trail file (IC120BP2), Stock Transfer "From" Transaction Register file (IC120CP2), Stock Transfer "To" Audit Trail file (IC120BP3), and Stock Transfer "To" Transaction Register file (IC120CP3).

f. If a system-controlled adjustment was detected in the warehouse balance moving average calculation, records are written to the Inventory Adjustment Audit Trail file (IC120BP1) and Inventory Adjustment Transaction Register file (IC120CP1). Warning messages are written to the Inventory Control Transaction Error file (IC505AP).

g. If the last operation of the order is being processed and the stock location is not blank, a record is written to the Manufacturing Order Async Transaction file (IC130DP) and a message is sent. This initiates the asynchronous processing of a manufacturing order receipt by the Manufacturing Order Receipts/Component Issues program (IC130E). If a stock transfer is being processed from the Quality Control Stock Location to a regular stocking location, or vice versa, two Manufacturing Order Async Transaction File records and messages are processed.

17. The following conditions determine which screen is displayed next if the Enter key is pressed:

Conditions		Screen Displayed
The Comments Flag equals Y (Quality Control only)		Comment screen (PO230S05)
The Comments Flag equals N		Recap screen (PO230S04 or PO235S03)
The Enter QC Specs Flag is Y		QC Spec Entry screen (IC155S02)

Quality Control Recap Screen (PO230S04)
Receipt Adjustment Recap Screen (PO235S03)

The Recap screen displays the receipt lines for the Receipt Number entered on the Function Select screen. The following processing is performed:

1. The recap screen is initialized and displayed.

2. The screen is validated:

a. One X may be entered in the Select field. If more than one X is entered, an error message is displayed. Otherwise, the selected line record is saved for processing according to which function key is pressed.

b. If the ENTER key is pressed, an error message is displayed.

3. The following conditions determine which screen is displayed next:

Conditions		Screen Displayed
F4 - Display Detail is pressed		Detail screen (PO230S03 or PO230S3A or PO235S02 or PO235S2A)
F5 - Enter QC Specs is pressed and a line is selected		Quality Control Specification (IC155S02)
F10 - Display Prompt is pressed		Function Select screen (PO230S01 or PO235S01)
F12 - Display Comments is pressed		Comment screen (PO230S05) (Receipt Quality Control only)

4. If this is a receipt for multiple orders, the function key F18 allows the user to call the Multiple Purchase Order Window (PORCTWIN). This window displays all purchase orders for the receipt.

Quality Control Comment Screen (PO230S05)

The comment screen allows the addition or maintenance of comment records associated with a receipt header or a receipt line. Up to 99 comment records can be entered for a header record. In addition, up to 99 comment records can be entered for each line.

Each comment line has an associated Print Code, which determines if the comment should be printed and where. To delete a comment line, both the Print Code and Comment Text must be blanked out. The following processing is performed:

1. The screen is initialized and displayed.

2. The user's input is validated. See the Purchasing User Manual, File Maintenance Screens-Purchasing Control, for validation rules.

3. If the fields are valid, the comments are written to the Purchase Order Receipt Comment file (PO210M4) and an audit trail record is formatted and written to the Purchase Order Receipt Comment Audit Trail file (PO210BP4).

4. The following conditions determine which screen will be displayed next:

Conditions		Screen Displayed
The previous screen was the Header screen, which was displayed by pressing a function key from the Recap screen		Recap screen (PO230S04)
The previous screen was the header screen, which was displayed by pressing a function key from the detail screen		Detail screen (PO230S03)
The previous screen was the recap screen		Recap screen (PO230S04)
The previous screen was the detail screen		Recap screen (PO230S04)
F4 - Display Detail is pressed		Detail screen (PO230S03)
F11 - Display Recap is pressed		Recap screen (PO230S04)

Menu

Quality Control and Receipt Adjustment - Calculations

PO230E Program Menu