MAPICS

Integrated Outside Operations

 

Quick Reference Guide

 

SH62694

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

SH14754 – version 2

 

 


 

Quick Reference Guide. 1

Introduction. 3

Interaction with MAPICS Applications. 4

MAPICS Files for Integrated Outside Operations. 5

Overview of Integrated Outside Operations. 6

Preparing for Integrated Outside Operations. 6

Processing Outside Operations. 6

Setting up Integrated Outside Operations. 7

Creating and releasing the manufacturing order 7

Auto-Release Outside Operation Purchase Orders. 8

Purchase order comments. 8

Transactions - Processing Receipts for the Outside Operation Service Item.. 9

Purchase Receipt (RP) Transaction. 9

Other Receipt Transactions. 10

Processing the Invoice. 10

Closing and Purging the Manufacturing Order 11

User Exits. 11

Work With Outside Operations. 12

Work With Outside Operation Details. 14

Work With Outside Operations Cross Reference. 23

Work With Outside Operation Components. 33

Appendix A.  Manufacturing Order Release. 34

Appendix B.  Transaction Update Tables. 38

RP Transaction Update Table. 38

Appendix C.  Processing an Invoice for an Outside Operation. 43

PCC Outside Operation Transaction Update Tables. 43

Appendix D.  Order Closeout and Purge Update Tables. 45

Manufacturing Order Selected for Closeout and Purge. 45

Appendix E.  File Layouts. 46

Appendix F.  For Reference: Selected MAPICS Data Fields. 49

Appendix G.  For Reference: MAPICS Order Status Codes. 58

Appendix H.  Implementing the New Outside Operation Process. 60

 

 


Introduction

An outside operation in MAPICS is work performed on a manufacturing order (MO) by an outside service provider.  A routing operation identifies the activity, and a non-inventory item represents the services rendered.  An outside operation is not the same as a routing operation for in-house labor, and the purchased entity is a service, not a component item. 

 

The integration of outside operations in MAPICS provides the following additional functions.

 

The operations required to produce an end item are defined in the PDM or EPDM routing files.  When the manufacturing order is released, these records are used to create the open operations for the manufacturing order.  Additional files help identify, track and automate the handling of integrated outside operations. 

 

The Outside Operation Details file (OOPDTL) contains information for a specific site, item, and operation.  It designates the purchase order and processing options to be applied.  These include the option to automatically create a requisition, purchase order, or blanket purchase order for the outside operation at the time the manufacturing order is created, or at a later time.  Also, there is an option to specify that additional routing descriptions, if they exist for the outside operation, will be copied as comments to the purchase order or blanket when the PO is created.  These comments can be included on the printed purchase order using existing purchase order print functions.

 

The Outside Operations Cross Reference file (MOPORF) links the MO to the PO and provides status information.  When the manufacturing order is released, a record will be added to this file for each outside operation with a corresponding details file record.  The cross-reference record is updated as the requisition, purchase order, or blanket purchase order is created.  The user can also maintain the cross-reference file to manually link or unlink a PO to an MO.   

 

The Outside Operations Component Record file (MOPOCM) identifies and tracks components sent to the vendor for outside processing.  MAPICS does not currently add, maintain, or delete records in this file, but user exits are available to support this function.


 

Interaction with MAPICS Applications

Inventory Management (IM): Manufacturing orders are created, released, closed and purged in IM.  Purchase receipts are processed in IM.  Integrated outside operations will create the purchase order or requisition for the service item when the MO is released.  It will also maintain the cross-reference file between the MO and PO, update both the MO and PO from receipt transactions, and archive outside operation records to MO history files.  IM is required for integrated outside operations.    

 

Production Control and Costing (PCC): Operation detail and description records used by PCC can be created either when orders are released through IM or later through PC&C displays.  Operation detail records are automatically created in the manufacturing operations (MOROUT) file during manufacturing order release from PDM or EPDM standard routings.  Operations are designated as outside service operations when the time basis code is “C”.  Additional descriptions for operations are created in the open operations additional descriptions (MODESC) file from additional routing descriptions.  PCC is required for integrated outside operations.

 

Purchasing (PUR): Purchase orders and requisitions are created and processed in Purchasing.  Purchase receipts can be processed in either IM or Procurement Management, PM.  The cross-reference file contains the information to associate an MO with a PO for an outside operation.  Purchase order comment records can also be included for the outside operation.

 

Product Date Management (PDM) and Enterprise PDM (EPDM): Standard routings are created and maintained in the routing (ROUTNG for PDM, RTGOPR for EPDM) files.  Additional routing descriptions can be maintained in the routing descriptions (RTGODS or RTGDSC) files.  A routing is designated as an outside service operation if the Time Basis Code is “C”.

 

Material Requirements Planning (MRP): MRP allows the release of planned

manufacturing orders.  Integrated outside operations may also generate purchase orders and requisitions for MO’s released through MRP.  It does not currently provide the function to create requirements or planned orders in MRP for outside operation service items. 

 

Accounts Payable (AP) and International Financial Management (IFM): Invoices for outside operation purchase orders may be processed in AP or IFM and automatically create PCC transactions in a shop activity batch to update the MO routing operation’s cost, completed quantity and status.

 

Procurement Management (PM): Receipt transactions for outside operation purchase orders can be processed in PM rather than IM.  These receipts may also update the corresponding outside operation routing records.

 

Cross Application Support (CAS):  CAS provides support to other applications for tasks such as security and file backup.  The integrated outside operation functions include task-level security supported by menu maintenance records in the task definition file, TSKDEF.  These tasks include reviewing and releasing orders, and maintaining the outside operations files.  File management tasks such as file status listings, file reorganization, and file backup is also supported for the outside operations files (OOPDTL, MOPORF, MOPOCM, MOHPOR, MOHPOC).

MAPICS Files for Integrated Outside Operations

Several MAPICS files specifically support the integrated outside operations functions.

 

Outside Operation Details file (OOPDTL) – Records are optionally included in this file by item, warehouse and routing operation to specify the outside service operation functions for purchase document creation, receipts and invoice processing. 

 

Outside Operations Cross Reference file (MOPORF) – This file contains data and status information for a specific manufacturing order’s outside operation and its corresponding purchase order or requisition.  Records are created when the manufacturing order is released or added manually by the user.

 

Outside Operation Components file (MOPOCM) – The user can add and maintain records in this file to track the shipment of components to vendors for outside services.  MAPICS does not currently create or update records in this file.  However, the records are saved to a history file when the manufacturing order is purged.

 

Outside Operations Cross Reference History file (MOHPOR) – Contains manufacturing order history records from the MOPORF file.

 

Outside Operation Components History file (MOHPOC) – Contains manufacturing order history records from the MOPOCM file.

 


Overview of Integrated Outside Operations

Preparing for Integrated Outside Operations

The following steps are necessary in order to utilize the integrated outside service operation function in MAPICS.

Processing Outside Operations

The steps to process an outside operation include the following:

o       A cross reference record is created to associate the MO with a PO

·        Generate a purchase order for the service

o       A PO can be automatically created for the outside service

o       The required quantity of the service item is calculated

o       The cross reference record is updated with the new PO number

·        Process the PO and receive the service

o       Enter an RP to receive the service

o       Can automatically update the MO with receipt quantity and cost

·        Enter the invoice in AP or IFM with Charge Type = “O”

o       MO number and operation sequence identify the outside operation

o       Quantity and cost passed to PCC

·        Post the invoice quantity and/or cost to the MO

o       Shop activity update batch from AP or IFM

o       Completion Code = 2, operation complete

o       Can update MO operation with actual invoice quantity and/or cost

·        Close and purge the manufacturing order

o       Close the manufacturing order

o       Manufacturing order history includes outside operations

·        User Exits

o       User exits to create and update MOPOCM                                                            

 

 

 

 

 

 

 


Setting up Integrated Outside Operations

Note:  The end item bill of material (product structure) does NOT include the service item as a component.

Creating and releasing the manufacturing order

When a manufacturing order is released via IM, MRP or OBPM, open operation records are created in the manufacturing order operations (MOROUT) file from information in the standard routing (ROUTNG or RTGOPR) files.  If the Time Basis Code (TBC) is “C”, then the operation is designated as an outside operation.  The operation standard cost in MOROUT comes from the Routing file.  The scheduled operation due date is calculated when the manufacturing order is released.  The scheduling routine will automatically calculate the Start and Completion dates for the operation.  Move time is included in the scheduling calculations.

 

If an operation is designated as an outside operation (TBC = C) and there is a valid outside operations detail record (OOPDTL) for the item and operation, then an outside operation purchase order or requisition can be automatically created.  After order release is run, the user is responsible for maintaining the Outside Operations Cross Reference file (MOPORF) to associate an MO to a PO.

 

A user exit in manufacturing order release allows the user to update the Outside Operation Components file (MOPOCM).

Auto-Release Outside Operation Purchase Orders

If the integrated outside operations function is implemented, then outside operation purchase orders or requisitions can be automatically created and released when the manufacturing order is released.  The user controls whether purchase orders are created, and the type of purchase order to be created, based upon several factors in the Outside Operation Detail (OOPDTL) file.

 

When a manufacturing order is released (and after the scheduler is run to calculate the open operation due date), a purchase document can be automatically generated for its outside operation service items.  The system can generate a requisition, a regular purchase order, or a blanket purchase order, and the requisition or purchase order can be in either released or held status.  If the purchase order is not created at the time of manufacturing order release, it can be created manually later from a review screen.

 

 

 

Purchase order comments

When the purchase order is created, additional descriptions from the outside routing operation can be automatically added as comments to the PO or blanket release.  These comments are copied from open operations comment (MODESC) records to purchase order comment (POCOMT) records.  This is controlled by the outside operations PO comment (OOPC) field in the OOPDTL record.

Transactions - Processing Receipts for the Outside Operation Service Item

Receipts for the outside service operation purchase order can be entered as purchase receipt (RP) transactions in inventory management.  They can also be processed in the procurement management application.  These receipts are for the completion of a service, not the receipt of a component or raw material to inventory.  Since the service was designated as a non-inventory item, it does not require an item balance record and the RP transaction will not update the quantity on hand.  However, it will update the purchase order and may also update the outside operation quantity and cost for the manufacturing order.  Updating the operation quantity or costs can be deferred until the invoice is processed, based upon an update code in the cross-reference file.

 

Purchase Receipt (RP) Transaction

Receipts of purchased items are commonly entered using RP transactions in inventory management.  How these transactions are processed and the resulting record updates is dependent upon several factors related to the MAPICS environment and tailoring options, the current status and values in the master and order file records, and the data included as input on the transaction.  For outside operation receipts, some of these factors can normally be assumed as follows:

 

 

Other factors that affect an RP transaction are,

·        The quantity and cost in the MO outside operation routing record may be updated by the RP transaction or from the invoice.  The Outside Operation Quantity/Cost Update Code (OOUP) in the cross-reference file specifies how the quantity and cost are to be updated.

o       0 = Update both quantity and cost from the invoice (not the RP)

o       1 = Update both quantity and cost from the RP (not the invoice)

o       2 = Update the quantity from RP and the cost from the invoice

 

·        Tailoring question I32, Use the PO item cost as the default RP transaction amount.

o       Y = If no cost is entered on the RP, use the POITEM unit cost

o       N = If no cost is entered on the RP, then use the accounting cost (Std/Avg/Last, or Unit Cost Default).

 

The RP will update the PO files (POMAST, POITEM, POBLKT) with quantity, cost and status information.  If there is a MOPORF record corresponding to the PO, then it will update MOPORF and may also update the MO files (MOMAST, MOROUT)

 

Other Receipt Transactions

Receipt to Inspection (RI) Transaction

An RI transaction can be entered for the service item on the purchase order.  However, this transaction will only update the received-to-inspection quantity in the PO.  It will not update the location or warehouse quantity-on-hand, or the outside operations cross reference file.

 

Inspect-on-Receipt Approval (PQ) Transaction

The PQ transaction is not used with non-inventory items. 

 

The PQ is a generated transaction that is created when an inspect-on-receipt item is approved via quality control.  It completes the receiving process and updates the on-hand quantity.  Prior to approval, the item must have been received into a location.  The most common method to place an IOR item into a location is with an RI, Receipt to Inspection transaction.  However, since the Inspect-on-Receipt flag cannot be set to 1 in the item master file for a non-inventory item, an RI for a non-inventory item cannot update the quantity into a location.  If the item is not in a location in a waiting inspection status, then it cannot be approved, and no PQ can be generated.

 

Therefore, a PQ transaction is irrelevant for outside operations.

 

Miscellaneous Item Receipt transaction

Inventory management includes a separate menu option for receipts and issues of miscellaneous items.  Transactions entered using this option will not update the PO files, MO files, or data associated with outside operations.

 

Processing the Invoice

Invoice costs from Accounts Payable (AP) or International Financial Management (IFM) can be passed to the manufacturing order as outside operation costs.  When the invoice is entered, the user may also enter the manufacturing order number, operation sequence number, and a charge code of “O”, and MAPICS will create an outside operation (OOPER) transaction in a suspended PCC shop activity batch.

o       AP (or IFM) must be installed and interfaced to PCC

o       Enter Charge Type = “O” on the invoice

Integrated outside operations provide additional flexibility to determine how the outside operation transaction is processed in PCC.

 

When the PCC batch is processed, the outside operation quantity and costs can be posted to the manufacturing order’s outside operation to report quantities and to increase the total work in process costs of the MO.  The quantity/cost update flag from the cross-reference file determines whether the quantity and/or cost of the outside operation will be updated from the invoice, or if it can be assumed that they were previously updated by the RP, and should not be updated again by the invoice.

 

If the MO or operation is closed or cancelled (MOMAST status = 45, 50, 55, 99, or MOROUT status = 00, 40, 50), then the PCC transaction will generate a message and will be copied to a PCC errors batch.

 

Closing and Purging the Manufacturing Order

If manufacturing order history is active, then closing and purging the manufacturing order will copy the outside operation records (MOPORF and MOPOCM) to the outside operation history (MOHPOR and MOHPOC) files.  This is in addition to the other manufacturing order history file updates (MOHMST, MOHDTA, MOHRTG, MOHMSC, and MOHDSC).

 

User Exits

User exits are provided to facilitate the addition of other user-written functions such as the tracking of components as they are transferred to and from the service provider.  A user exit is available when the manufacturing order is released, and another is available when the purchase order receipt transaction is processed.

 

 

 

                                                                                                                                   

 

 


Work With Outside Operations

A new PCC menu option has been added to support outside operations.

 

New PCC menu option for Outside Operations

 

 

Option 10. Outside Operations – selecting this option will cause a secondary menu to appear for Outside Operations functions.

 

 


New PCC secondary menu for Outside Operations

 

The following secondary menu is displayed when the user selects Option 10) Outside Operations, from the PCC main menu.

 

 

Option 1. Work with Outside Operation Details – select this option to work with Outside Operation Details (OOPDTL) records.

 

Option 2. Work with Outside Operations Cross Reference – select this option to work with cross-reference (MOPORF) records for outside operations.

 

 


Work With Outside Operation Details

The following screen will appear if the user selects Option 1. Work With Outside Operation Details from the secondary menu for Outside Operations.  It allows the user to create, change, delete or display Outside Operation Details (OOPDTL) records. 

 

 

This is the main “Work With” screen for the Outside Operation Details file.   Starting from this screen, the user can Add, Change, Delete and Display Outside Operation Details records.  Up to nine pre-existing records are displayed on each screen.  The user can scroll up or down to see more records.  Also, there is a “position-to” feature, which will bring up all the Outside Operation Details records, starting with a particular vendor number.

 

Press F3 to Exit this screen

 

Press F5 to Refresh the data on this screen.

 

 

 

 


Create Outside Operations Detail (OOPDTL) file record

The following two screens will appear when the user selects option 1, Create, on the Work With Outside Operation Details screen

 

 

This is the first screen for Creating a new Outside Operation Details record.  The key fields are shown first (Vendor number, Warehouse ID, Item number, and Operation sequence).  Additional key fields (Site, Item revision, Routing ID and Routing version) are displayed if EPDM is installed.  When the fields on this screen have been populated and the user presses Enter, the second screen appears.

 

 


 

 

 

This is the second screen for creating a new Outside Operation Details record.  Edits of the entered data include the following:

If all the values entered pass all the edits, then a new record is written to the Outside Operation Details file.

 

 


 

Entry Fields in the Outside Operation Details file (OOPDTL)

 

Site ID (displays only if EPDM is installed) - The site associated with the end item

Vendor number– The vendor supplying the service item.

Warehouse ID – The warehouse where the end item is located.

Finished item number – The number of the manufactured end item.

Item revision (with EPDM) – The item revision number for the end item.

Operation sequence # – The outside routing operation sequence number.

Routing identifier (with EPDM) – The routing ID for the outside operation.

Routing version (with EPDM) – The routing version for the outside operation.

Service item number – The item number of the outside operation service item.

Qty / cost update – Specifies how the quantity and cost are to be updated in the MO

outside operation routing record:

0 = Update both quantity and cost from the invoice (not the RP)

1 = Update both quantity and cost from the RP (not the invoice)

2 = Update the quantity from RP and the cost from the invoice

Preferred vendor – A flag to designate which OOPDTL record is to be used for any specific combination of outside operation detail records.  For each end item (as specified by the other key field parameters), one and only one preferred vendor must be designated.

PO create at MO release - Specifies whether the PO or requisition for the outside operation will be automatically created when the MO is released.  0=No, 1=Yes.

Release time fence – Number of days in the future to search for start times of unreleased purchase orders.

Lead time purchase – The lead time required to receive a purchased item to the dock (similar to the sum of Review LT, Vendor LT, and Safety LT in an item balance record).

Lead time adjustment – Dock to stock lead time (similar to Adjusted Purchase LT in an item balance record).

Auto Release code – The auto release code specifies the type of purchase document to be created.

0 = Do not create a PO or requisition (even if PO create at MO release = 1, Yes)

1 = Create a requisition

2 = Held single purchase order

3 = Single purchase order

4 = Held blanket purchase order

5 = Blanket purchase order

6 = Held fixed blanket purchase order

7 = Fixed blanket purchase order

Operation status completed at cost update – Set operation status to complete at cost update.

Additional descriptions to PO comments – Print outside operation comments on the PO.  0 = No, 1 = Yes.

 

 

 


Change Outside Operation Details (OOPDTL) file record

The following two screens appear when the user selects option 2, Change, for a record on the Work With Outside Operations Details screen

 

 

This is the first screen to Change a pre-existing Outside Operation Details record.  Notice that the key field values are shown in white and CANNOT be changed, even in Change mode.  ONLY the non-key fields can be changed.

When the user presses Enter, the second screen appears.


 

 

This is the second screen to Change an Outside Operation Details record.  When the user presses Enter, if all the new values pass all the edits, the record is updated.

 


Delete Outside Operation Details (OOPDTL) file record

The following screen appears when the user selects option 4, Delete, on the Work With Outside Operation Details screen.

 

 

This screen allows the user to confirm that the record is to be deleted.  The user may enter F12 to return to the previous screen without deleting this record.  Or, the user may press Enter to delete the record.

 

 

 


Display Outside Operation Details

The following two screens appear when the user selects option 5, Display, on the Work With Outside Operation Details screen.

 

 

This is the first screen to display the data in the selected Outside Operation Details record.  Notice that all the fields are displayed in white and none of the fields can be updated while in Display mode.  When the user presses Enter, the second screen appears. 

 


 

 

 

This is the second screen to display an Outside Operation Details record.

 


Work With Outside Operations Cross Reference

The following screen appears when the user selects option 2, Work With Outside Operations Cross Reference, from the secondary menu for Outside Operations.  This option allows the user to work with Outside Operations Cross Reference (MOPORF) records, and also to release purchase orders for selected outside operations.

 

 

This is the main “Work With” screen for the Outside Operations Cross Reference file.  Starting from this screen, the user can Add, Change, Delete, and Display Outside Operations Cross Reference records.  The user can also Release a purchase order or requisition for a selected manufacturing order and routing operation.  Up to 10 pre-existing records are displayed on each screen.  The user can scroll up or down to see more records.  Also, there is a “position-to” feature, which will bring up all the Outside Operations Cross Reference records, beginning with a particular MO number.

 

Press F3 to Exit this screen.

Press F5 to Refresh the data on this screen.

Press F6 to Add a new record to the file.  System will advance to the “Add Outside Operations Cross Reference” screen.

 


Manual Selection for Release of Outside Operations

 

Option 11 on the previous screen allows the user to select orders for release.  Orders that require more immediate attention are highlighted (in white).  These orders were identified based upon lead times and the release time fence.

  

Specifically, when an outside operation cross-reference record is created, the start date is calculated as the scheduled completion date of the manufacturing operation minus the sum of the purchase and adjusted lead times from the outside operation details record.  The start date represents that date when activity to create the purchase order must begin in order to satisfy the requirement.    

 

The release time fence is added to the current system date to create a window of visibility into the future.  Outside operation cross-reference records without an assigned purchase order, and whose start dates fall within the time fence, will be highlighted as candidates for immediate release.  The user may then select these orders using option 11 to release them for processing.

 

 

 


Change Outside Operations Cross Reference

The following screen appears when the user selects option 2, Change, on the Work With Outside Operations Cross Reference screen

 

 

This screen allows the user to change a pre-existing Outside Operations Cross Reference record.  The manufacturing order and operation number cannot be changed on this screen, but the user may enter changes to the purchase order, line number, and release number.

 

 


Delete Outside Operations Cross Reference

The following screen appears when the user selects option 4, Delete, on the Work With Outside Operations Cross Reference screen.

 

 

This screen allows the user to confirm that the record is to be deleted.  The user may enter F12 to return to the previous screen without deleting this record.  Or, the user may press Enter to delete the record.

 

 


Display Outside Operations Cross Reference

The following screen appears when the user selects option 5, Display, on the Work With Outside Operations Cross Reference screen.

 

 

This screen displays the data in the selected Outside Operations Cross Reference record.  None of the fields can be updated while in Display mode.  Press Enter to advance to the next selected record.  Press F12 to return. 

 

 


 

Release Outside Operation

This display appears when the user selects option 11, Release, from the Outside Operations screen.  Use this option to automatically create and release an outside operation purchase order for the selected manufacturing order.  The type of purchase order or requisition to be released is determined by the Release Code in the Outside Operation Detail (OOPDTL) file.

 

 

This screen allows the user to select an outside operation service item for auto-release of the purchase order.  Enter a 1 to select the service item for auto-release.  Press F12 to return to the previous screen.

 


Release Outside Operation

The following screen appears when the user selects option 11 to Release, and then option 1 to Select a service item on the Work With Outside Operations screen.

 

 

This screen allows the user to confirm that the purchase order is to be auto-released for the selected outside operation service item.  Press Enter to create the purchase order or requisition.  Press F12 to return to the previous screen without releasing the PO.

 

 

 

 

           

 

 


Add Outside Operations Cross Reference

When the user presses F6=Add Outside Operation, the following screen appears.

 

 

 

This screen allows the user to manually add an Outside Operations Cross Reference (MOPORF) record.  Enter the data and press Enter to create the new record.  Press F12 to return to the previous screen without adding the record.

 

 


 

Entry Fields in the Outside Operations Cross Reference file (MOPORF)

 

Manufacturing order – The manufacturing order number.  The manufacturing order number cannot be changed.

Operation number – The MO routing operation for the outside service operation.  The operation number cannot be changed.  

Purchase order – The purchase order number for the outside service.  An MO and PO are “linked” and “unlinked” by changing the PO number from blank to an existing PO, and from an existing PO to blank.

Line number – The line number on the purchase order

Release number – The blanket PO release number     

 

 

 


Dates in the Outside Operations Cross Reference (MOPORF) record

There are several date fields in the MOPORF record.  They fall into the two general categories of Scheduling dates, and Activity Tracking Dates.

 

Scheduling Dates

q       Scheduled Completion Date – Date when the item must be available to the MO.

q       Date Due on Dock – Date the item must be received on-site.

q       Start Date – Date when activity must begin to order the service item.

 

Activity Tracking Dates

q       Create Date – Date the cross-reference record was created.

q       Change Date – Date the cross-reference record was last maintained.

q       Closeout Date – Date the order was closed.

 

The scheduling dates are determined based on dates in the outside operation routing record (MOROUT) and lead times in the outside operation detail record (OOPDTL).

 

MOROUT

q       Scheduled Start Date – Date the operation is planned to start.

q       Actual Start Date – Date the operation actually started.

q       Scheduled Completion Date – Date the operation is planned to complete.

 

OOPDTL

q       Lead Time, Purchase – Days for PO review, vendor activity, and buffer.

q       Lead Time, Purchase Adjustment – Days for dock to “available ” activity.

q       Authorized Time Fence – Days of visibility for review.

 


 

Work With Outside Operation Components

The Outside Operation Components file, MOPOCM, is included with integrated outside operations, but is not currently used by MAPICS.  It is designed to support the tracking of components sent to a vendor for an outside service operation.  Updates to this file must currently be performed by the user.

 

 

 

 


Note: Refer to separate appendices for additional information regarding the MAPICS files, and data fields associated with outside operation processing.

Appendix A.  Manufacturing Order Release

In IM or MRP, when an MO is released with an outside routing operation, if a corresponding outside operation detail record exists, then an Outside Operations Cross Reference (MOPORF) record is created.

 

IF TBCDE (in MOROUT) = C,

and IF an OOPDTL record exists for the item and operation sequence,

            THEN a MOPORF record is created

 

MOPORF

Field

Value

MONR

ORDNO from MOMAST / MOROUT

OPSQ

OPSEQ from OOPDTL

PONR

IF a PO is created, THEN PONR = ORDNO from POITEM

IF a Requisition is created, THEN PONR = REQNO from REQHDF

PISQ

IF a PO is created, THEN PISQ = POISQ from POITEM (po item seq)

LSEQ

IF a PO is created, THEN LSEQ = LINSQ from POITEM (misc / svc seq)

BKSQ

IF a blanket PO is created, THEN BKSQ = BLKSQ from POBLKT

OITM

OITM from OOPDTL

WHID

WHID from OOPDTL

STDT

STDT = SCODT from MOROUT - (LTPU + LTPA) from OOPDTL

DKDT

DKDT = SCODT from MOROUT – LTPA from OOPDTL

OOUP

OOUP from OOPDTL

GNPO

IF a PO or Requisition is created, THEN GNPO = 1

RLPO

IF a PO is created, THEN RLPO = 1

VNDR

VNDR from OOPDTL

SCDT

SCDT = SCODT from MOROUT

STTS

Set to 0.  Not used.

CLDT

Not updated

CRDT

Set to system date

CRTM

Set to system time

CRUS

Set to user ID

CRPG

Set to active program name

CHDE

Not updated

CHUS

Not updated

CHPG

Not updated

CHTE

Not updated

 


When the MO is released, and the MOPORF record is created, if the release code (RELC) is 1, then a purchase document can be automatically created.  The type of purchase document that is created is controlled by the auto release code (ATRL) as follows:

            0, no action is taken

            1, a requisition is created and released

            2, a held purchase order is created

            3, a released PO is created

            4, a held blanket PO is created

            5, a released blanket PO is created

            6, a held fixed blanket PO is created

            7, a released fixed blanket PO is created

If a purchase order or requisition is generated, then the purchase order files are updated as follows:

 

POMAST

Field

Value

ORDNO

Assigned as next in sequence

VNDNR

VNDR from MOPORF

INVFG

Leave blank

PSTTS

Set to 20 (or 10 if vendor acceptance is required)

 

 

 

POITEM

Field

Value

ITNBR

From OITEM in MOPORF

LINSQ

Assigned sequentially to non-inventory items

BLCOD

IF RELC = 4, 5, 6, 7, THEN BLCOD = B,

ELSE, BLCOD = 0

QTYOR

Calculated.  (see formula below)

DUEDT

SCDT from MOPORF

DOKDT

DKDT from MOPORF

VNDNR

VNDR from MOPORF

CURPR

From Purchasing application pricing hierarchy

FXBL

IF RELC = 6, 7, THEN FXBL = 1,

ELSE FXBL = 0

SMRQ

Sum of RELQT for all associated POBLKT records

REFNO

Set to blank

INVFG

From INVFG in ITEMASA (or ITMRVA)

INVDS

Set to blank

STAIC

Set to 10 (or 05 if vendor acceptance is required)

RECRQ

From RECRQ in ITEMASC (or ITMRVC)

PURUM

UNMSR from ITEMASA

UMCNV

UMCNV = 1.00

 

 

 

POBLKT

Field

Value

BLKSQ

Assigned sequentially

RELQT

Calculated.  See formula below

RELDT

SCDT from MOPORF

DOKDT

DKDT from MOPORF

 

Note: other fields are similar to the POITEM record

 

REQHDF

Field

Value

REQNO

Assigned as next in sequence

ITNBR

From OITEM in MOPORF

QTYOR

Calculated. (see formula below)

DATER

System date

DOKDT

DKDT from MOPORF

DUEDT

SCDT from MOPORF

ORDNO

Leave blank

INVFG

From INVFG in ITEMASA (or ITMRVA)

UNMSR

UNMSR from ITEMASA

PURUM

 UNMSR from ITEMASA

UMCNV

UMCNV = 1.00

REFNO

Leave blank

 

 

The requisition or purchase order quantity is calculated as follows:

            POQTY = (MOQTY) x (YF)

            Where,

            POQTY is the PO Quantity or Requisition Quantity

            MOQTY is the MO order quantity plus quantity deviation from MOMAST

                        MOQTY = (ORQTY) + (QTDEV)

            YF is the yield factor, calculated as follows:      

                        YF = CYCOP / CUMCY

            CYCOP = Cumulative yield through previous op (CYCOP in MOROUT)                    CUMCY = Cumulative yield all ops (CUMCY in MOMAST)

 


 

Purchase Order Comments

Additional operation descriptions can be added as comments to the outside operation purchase order.

IF a purchase order is created,

and IF the outside operation comment flag is 1 (OOPC field in OOPDTL file),

and IF additional descriptions exist in MODESC for the MO/Operation,

THEN copy additional descriptions to the PO Comments file, POCOMT

 

POCOMT

Field

Value

ORDNO

From ORDNO in POMAST / POITEM

ITNBR

From ITNBR in POITEM

HOUSE

From HOUSE in POMAST / POITEM

LINSQ

From LINSQ in POITEM

BLKSQ

From BLKSQ in POBLKT

CMSEQ

Sequentially assigned

MESSN

Leave blank

CMNT1

From ADDSC in 1st MODESC (odd-numbered MODESC records)

CMNT2

From ADDSC in 2nd MODESC (even-numbered MODESC records)

OPSEQ

From OPSEQ in MODESC

WKCTR

From WKCTR in MOROUT

WUFLG

Set = G

 

 

 

 

If a requisition or purchase order is created, then add a record to the MO Operation Descriptions (MODESC) file as follows.

MODESC

Field

Value

ORDNO

Mfg ORDNO from MOMAST / MOROUT / MOPORF

OPSEQ

OPSEQ from MOROUT / MOPORF

DSQNO

Assigned sequentially

ADDSC

Pur ORDNO from POMAST / POITEM / MOPORF

CLDT

Set = 0

 

 

 

 

User Exit

A user exit is provided at the end of order release.

 

 


 

 

Appendix B.  Transaction Update Tables

RP Transaction Update Table

The purchase order receipt (RP) transaction input fields include the purchase order number, item number, warehouse, quantity (positive or negative), and line item sequence number for miscellaneous and service items.  Other optional fields such as the completion code, blanket PO release number, amount, reference, reason, location, and batch/lot number may also be included as input and affect the processing of the RP.

 

Other factors which may affect how the RP is processed include:

·        Receipt Required? Y/N

·        Update Outside Ops Cost?

·        ITEMBL record exists? Y/N

·        Controlled warehouse? Y/N

·        I32 = Y/N

RP Transaction Amount

The RP Transaction Amount, TRAMT, is calculated as follows:

            IF amount is entered on the RP

            THEN TRAMT = entered amount

            ELSE, IF I32 = Y,

            THEN TRAMT = (RP trans qty) x (PO unit cost)

            ELSE, TRAMT = (RP trans qty) x (IM unit cost)

Where,

            PO unit cost = unit cost from POITEM

            IM unit cost is determined as follows:

            (Note: IM tailored cost (Std/Avg/Last) is specified by the questionnaire)

                        IF IM tailored cost in Item Balance is NOT = 0,

                        THEN IM unit cost = IM tailored cost from ITEMBL

                        Else, IF IM tailored cost = 0 in ITEMBL,

                        THEN IM unit cost = Unit Cost Default from item master         


Update Purchase files

The RP transaction updates the purchasing files, including the following fields.

 

POMAST

Field

Value

PSTTS

IF PSTTS = 20, THEN set PSTTS to 30

IF PSTTS = 10, 40, 50, 60, 99, THEN the RP is rejected as an error

 

 

 

POITEM

Field

Value

RECRQ

IF RECRQ = 0, THEN RP is rejected as an error

STAIC

IF STAIC = 10, 20, 30, THEN set STAIC = 40

IF STAIC = 5, 50, 99, THEN RP is rejected as an error

STKQT

IF RP trans qty is positive, THEN STKQT = STKQT + RP trans qty

STKQT

IF RP trans qty is negative,

And IF resulting STKQT would not be negative,

THEN STKQT = STKQT + RP trans qty

STKQT

Or, IF RP trans qty is negative

AND IF resulting STKQT would be negative,

THEN RP is rejected as an error

TRAMT

(TRAMT from POITEM) + (TRAMT from RP)

 RPAM

RPAM + (TRAMT from RP)

 

IF BLCOD in POITEM = 1, THEN also update order release records (POBLKT)

IF RP blanket release number is not blank, THEN update specific POBLKT record

IF RP blanket release number is blank, THEN autospread the quantity across releases

 

POBLKT

Field

Value

STAIC

IF STAIC = 10, 20, 30, THEN STAIC = 40

IF STAIC = 5, 50, 99, THEN RP is rejected as an error

STKQT

IF RP trans qty is positive,

THEN STKQT = STKQT + RP trans qty (or autospread qty)

STKQT

Or, IF RP trans qty is negative,

And IF resulting STKQT would not be negative,

THEN STKQT = STKQT + RP trans qty (or autospreqd qty)

STKQT

IF RP trans qty is negative

AND IF resulting STKQT would be negative,

THEN RP is rejected as an error

TRAMT

TRAMT + (TRAMT from RP)

Or, TRAMT + (autospread % of RP amount)

RPAM

RPAM + (TRAMT from RP),

Or, RPAM + (autospread % of RP amount)

 

 

 

Update Manufacturing Order Files

The RP transaction can also update the corresponding MO files, if a MOPORF record exists which corresponds to the purchase order entered on the RP.  The fields updated are dependent upon the OOUP field in MOPORF.

 

IF a MOPORF record exists for the PO, and: 

            IF OOUP = 0, THEN do not update the MO files from the RP.

            IF OOUP = 1, THEN update the MO files for both qty and cost from the RP.

            IF OOUP = 2, THEN update the MO files for qty, but not cost, from the RP.

 

MOMAST

 Field

Value

OSTAT

IF OSTAT = 10, THEN set OSTAT = 40

IF OSTAT = 50, 55, 99, THEN reject the RP as an error

ISSCO

IF OSCD is updated in MOROUT,

THEN ISSCO = ISSCO + TRAMT

 

 

CUROP

IF OPSQ from MOPORF is greater than CUROP,

THEN set CUROP = OPSQ

 

 

 

 

MOROUT

Field

Value

OPSTC

IF OPSTC = 00, 40, 50, THEN reject the RP as an error

OPSTC

Else, IF RP completion code = C,

Or IF new TQCTD is gt/= Qty Req’d,

And IF OPSTC = 10, 20, 30, THEN set OPSTC = 40

OPSTC

Else, IF OPSTC = 10, 20, THEN set OPSTC = 30

TQCTP

IF OOUP = 1, 2,

THEN TQCTP = TQCTP + RP trans qty  (negative result is ok)

TQCTD

IF OOUP = 1, 2,

THEN TQCTD = TQCTD + RP trans qty  (negative result is ok)

OSCP

IF OOUP = 1,

THEN OSCP = OSCP + RP trans amount  (negative not allowed)

OSCD

IF OOUP = 1,

THEN OSCD = OSCD + RP trans amount  (negative not allowed)

 

 

Note: See previous description for RP transaction amount calculation

 


 

If PCC history is active, then also create a MOTRAN record for each MOROUT updated by the RP.

MOTRAN (if tailored for labor costing)

Field

Value

TCODE

Set to RP

ORDNO

ORDNO from MOMAST / MOROUT / MOPORF

OPSEQ

OPSEQ from MOROUT / MOPORF

WKCTR

WKCTR from MOROUT

RUNCD

Set = blank

OCMPC

Set = blank

TCOST

TCOST = change to OSCD in MOROUT

QTCOM

QTCOM = change to TQCTD in MOROUT

RECD

Set to blank

RFNO

Set to blank

ITNBR

OITM from MOPORF (ITNBR from POITEM)

 

 

 

 

If PCC General Ledger Interface is active, and if the outside operation cost-to-date (OSCD) in MOROUT was updated, then also create GLI (PCCTXN) records.

PCCTXN

Field

Value

TRTP

Set to RP

ORDR

ORDNO from MOMAST / MOROUT / MOPORF

CJOB

Leave blank

FITM

FITEM from MOMAST

ITYP

ITTYP from ITEMASA (or ITMRVA)

PFID

WKCTR from MOROUT

TRAM

TRAM = change to OSCD in MOROUT

 

 

 

 

 

A User Exit is available in RP transaction processing to update the outside operation components tracking file, MOPOCM.

MOPOCM

Field

Value

 

 

 

User maintained and updated

 

 

 

The Item Balance file is not updated if there is no ITEMBL record for the item/warehouse.

            IF an ITEMBL record exists for the item,

            THEN update the ITEMBL record

ITEMBL

Field

Value

MOHTQ

MOHTQ + RP transaction quantity

MPUPQ

MPUPQ – RP transaction quantity

  (RP trans qty not to exceed PO open qty)

 

 

 

Receipt of a non-inventory item may update the location file, SLQNTY, if a location is entered on the RP.

            IF a valid location is entered on the RP,

THEN add or update an SLQNTY record as follows

SLQNTY

Field

Value

ITNBR

RP item number

HOUSE

RP warehouse

LLOCN

RP location

LBHNO

RP batch/lot

LQNTY

LQNTY + RP transaction quantity

 

 

 

 

IMHIST
Create an RP record in the IM history (IMHIST) file.

 

INVTXN

Note:  The GLI interface file (INVTXN) for IM is not updated by an RP transaction if the transaction amount is 0, or if the item is a non-inventory item

 


Appendix C.  Processing an Invoice for an Outside Operation

IF AP (or IFM) and PCC are installed and interfaced,

And IF the Charge Code is entered as “O” (letter o) on the invoice,

And IF an MO number and an operation number are entered on the invoice,

THEN an OOPER transaction is written to a suspended SHPACT batch in PCC

PCC Outside Operation Transaction Update Tables

When the outside operation transaction is processed in PCC Shop Activity update, the manufacturing order files will be updated.  The fields updated are dependent upon the OOUP field in MOPORF.

 

IF a MOPORF record exists for the manufacturing operation, and:

IF OOUP = 0, THEN update the MO files for both qty and cost.

            IF OOUP = 1, THEN do not update the MO files from the invoice.

            IF OOUP = 2, THEN update the MO for cost, but not qty, from the invoice.

 

MOROUT

Field

Value

OPSTC

IF OPSTC = 00, 40, 50,

THEN reject the transaction

OPSTC

IF OPSTC = 10, 20, 30

And IF OCMPC from SHPACT = 0,

THEN set OPSTC to 30

OPSTC

IF OPSTC = 10, 20, 30,

And IF OCMPC from SHPACT = 1,

THEN set OPSTC to 40 

TQCTP

IF OOUP = 0,

THEN TQCTP = TQCTP + invoice quantity

TQCTD

IF OOUP = 0,

THEN TQCTD = TQCTD + invoice quantity

OSCP

IF OOUP = 0, 2,

THEN OSCP = OSCP + invoice amount

OSCD

IF OOUP = 0, 2,

THEN OSCD = OSCD + invoice amount

 

 

 

MOMAST

Field

Value

OSTAT

IF OSTAT = 10,

THEN set OSTAT = 40

OSTAT

IF OSTAT = 50, 55, 99,

THEN reject the PCC transaction as an error

ISSCO

IF OSCD was updated in MOROUT,

THEN ISSCO = ISSCO + (change to OSCD in MOROUT)

 

 

 

 

MOTRAN       (if tailored for labor costing)

Field

Value

TCODE

Set to OOPER

ORDNO

ORDNO from MOMAST / MOROUT / MOPORF

OPSEQ

OPSEQ from MOROUT / MOPORF

WKCTR

WKCTR from MOROUT

RUNCD

Set = blank

OCMPC

Set = blank

TCOST

TCOST = change to OSCD in MOROUT

QTCOM

QTCOM = change to TQCTD in MOROUT

RECD

Set to blank

RFNO

Set to blank

ITNBR

OITM from MOPORF

 

 

 

 

Invoice data variables

            Charge Type = O, or not = O

            PO entered, or not entered

            MO entered, or not entered

            Service item entered, or not

            Quantity entered, or not, or negative

            Amount entered, or not, or negative

 

 


Appendix D.  Order Closeout and Purge Update Tables

Manufacturing Order Selected for Closeout and Purge

Mfg Order is Complete (Status = 55)

Mfg Order is Selected for Closeout

 

A warning message will be issued if an MO is selected for closeout and purge prior to updating the cost information.

 

Manufacturing order closeout selection

If MOMAST status = 10, 40 or 45,

And if a MOROUT record exists with both TBC = C,

And IF Operation Status is NOT equal to 00, 40, or 50,

And IF a MOPORF record exists

Then issue WAMnnnn  “Open PO for Outside Operation exists”

 

Manufacturing Order Close and Purge

 

At Mfg Order purge,

IF a MOPORF record for the MO exists (with PO no = blank ??),

THEN copy MOPORF records to MOHPOR,

And copy MOPOCM records to MOHPOC

And delete the MOPORF records


 

Appendix E.  File Layouts

 

Outside Operation Details File (OOPDTL)

Field

Name

Type

Length

Dec

Buffer

Offset

Text

STID

A

3

 

1

Site identifier

VNDR

A

6

 

4

Vendor number

WHID

A

3

 

10

Warehouse code

ITNO

A

15

 

13

Item number

ITRV

A

6

 

28

Item revision

OPSQ

A

4

 

34

Operation Seq. No.

RTID

A

15

 

38

Routing Identifier

RTVR

A

6

 

53

Routing version

OOUP

A

1

 

59

Qty / cost update code

RELC

A

1

 

60

Release code

ATRL

S

1

0

61

Auto release code

ATIM

P

3

0

62

Auto release time fence

OITM

A

15

 

64

Outside service item number

LTPU

P

4

1

79

Lead time purchase

LTPA

P

2

0

82

Lead time purchase adjustment

ARCI

A

1

 

84

Contract use in auto release item

OOPC

A

1

 

85

Outside op PO comment

UOST

A

1

 

86

Update operation status

PVND

A

1

 

87

Preferred vendor

CRDT

P

7

0

88

Create date

CRTM

P

6

0

92

Create time

CRUS

A

10

 

96

Create user

CRPG

A

10

 

106

Create program

CHDE

P

7

0

116

Change date

CHUS

A

10

 

120

Change user

CHPG

A

10

 

130

Change program

CHTE

P

6

0

140

Change time

UUSA

A

1

 

144

User field switch A

UUCA

A

5

 

145

User field code A

UUQ1

P

11

3

150

User field quantity 1

UUA1

P

15

2

156

User field amount 1

UUD1

S

7

0

164

User field date 1

UU40

A

40

 

171

User field text – 40 characters

 

 

 

 

 

 

 

 


 

Outside Operations Cross Reference File (MOPORF)

Field

Name

Type

Length

Dec

Buffer

Offset

Text

MONR

A

7

 

1

Manufacturing order number

OPSQ

A

4

 

8

Operation sequence number

PONR

A

7

 

12

Purchase order number

PISQ

P

5

0

19

PO item sequence

LSEQ

S

3

0

22

Misc/service item sequence

BKSQ

P

4

0

25

Blanket release sequence

OITM

A

15

 

28

Outside service item number

WHID

A

3

 

43

Warehouse code

STDT

P

7

0

46

Start date

DKDT

P

7

0

50

Date due on dock

OOUP

A

1

 

54

Qty / cost update code

GNPO

A

1

 

55

PO generated

RLPO

A

1

 

56

PO released

VNDR

A

6

 

57

Vendor number

SCDT

P

7

0

63

Scheduled completion date

STTS

S

2

0

67

Status

CLDT

P

7

0

69

Closeout date

CRDT

P

7

0

73

Create date

CRTM

P

6

0

77

Create time

CRUS

A

10

 

81

Create user

CRPG

A

10

 

91

Create program

CHDE

P

7

0

101

Change date

CHUS

A

10

 

105

Change user

CHPG

A

10

 

115

Change program

CHTE

P

6

0

125

Change time

UUSA

A

1

 

129

User field – switch A

UUCA

A

5

 

130

User field – code A

UUQ1

P

11

3

135

User field – quantity 1

UUA1

P

15

2

141

User field – amount 1

UUD1

S

7

0

149

User field – date 1

UU40

A

40

 

156

User field – text 40

 

 

 

 

 

 

 


 

Outside Operation Components File (MOPOCM)

Field

Name

Type

Length

Dec

Buffer

Offset

Text

MONR

A

7

 

1

Manufacturing order number

OPSQ

A

4

 

8

Operation sequence number

CITM

A

15

 

12

Component item number

CITR

A

6

 

27

Component item revision

CIWH

A

3

 

33

Component item warehouse

QTEQ

P

10

3

36

Total quantity required

REQT

P

7

0

42

Required date

QYSH

P

10

3

46

Quantity shipped

SHDT

P

7

0

52

Shipment date

SHTP

A

1

 

56

Shipment type

SHDC

A

1

 

57

Shipment documentation

STTS

S

2

0

58

Status

CLDT

P

7

0

60

Closeout date

CRDT

P

7

0

64

Create date

CRTM

P

6

0

68

Create time

CRUS

A

10

 

72

Create user

CRPG

A

10

 

82

Create program

CHDE

P

7

0

92

Change date

CHUS

A

10

 

96

Change user

CHPG

A

10

 

106

Change program

CHTE

P

6

0

116

Change time

UUSA

A

1

 

120

User field – switch A

UUCA

A

5

 

121

User field – code A

UUQ1

P

11

3

126

User field – quantity 1

UUA1

P

15

2

132

User field – amount 1

UUD1

S

7

0

140

User field – date 1

UU40

A

40

 

147

User field – text 40

 

 

 

 

 

 

 


Appendix F.  For Reference: Selected MAPICS Data Fields

Miscellaneous files and fields associated with outside operations

The following existing MAPICS files and selected data fields may also be involved when processing outside operations.  For convenience, they are listed here as a reference.

 

MOMAST

Field

Description

ORDNO

Order number

CUROP

Current operation

OSTAT

Mfg order status code

REFNO

Reference number

NCOPS

Number of complete operations

QCPRV

Qty complete, previous operation

QCCUR

Qty complete, current operation

OPCUR

Current operation

WCCUR

Current operation workcenter

FITEM

Finished item number

FITWH

Finished item warehouse

ISSCO

Issue cost (includes outside op cost)

NODET

Number of additional routing descriptions

OPSNS

Number of active operations not started

ODUDT

Order due date

CUMCY

Current cumulative yield all operations

ORQTY

Order quantity

QTDEV

Quantity deviation

 

 

 

 


 

MOROUT

Field

Description

ORDNO

Order number

OPSEQ

Operation sequence number

DESSQ

Description sequence number

WKCTR

Production facility ID (workcenter)

TBCDE

Time basis code

OPSTC

Operation status code

TQCTP

Total qty complete this period

TQCTD

Total qty complete to date

SSTDT

Scheduled start date

ASTDT

Actual start date

SCODT

Scheduled completion date

OPCST

Std labor and overhead cost at release

NODES

Number of additional routing descriptions

CYCOP

Cum current yield through previous

CYTOP

Operation yield current

SOCS 

Std outside operation cost

OSCP 

Outside operation cost this period

OSCD

Outside operation cost to date

 

 

 

MODESC

Field

Description

ORDNO

Order number

OPSEQ

Operation sequence number

DSQNO

Operation description sequence number

ADDSC

Additional operation description

CLDT

Closeout date

 

 

 


 

MOTRAN

Field

Description

TCODE

Transaction code

ORDNO

Order number

OPSEQ

Operation sequence number

WKCTR

Production facility ID

NOPSQ

Next operation for move

NXLOC

Next location for move

DPTNO

Department number

SATYP

Shop activity transaction type

RUNCD

Run code (S, R, M)

OCMPC

Operation completion code (0, 1, 2, 3)

LBTIM

Labor time

MATIM

Machine time

TCOST

Transaction cost

QTCOM

Quantity complete

RECD

Reason code

RFNO

Reference number

ITNBR

Item number

 

PCCTXN

Field

Value

TRTP

Transaction type

ORDR

Manufacturing order number

CJOB

Job number

FITM

Finished item number

ITYP

Item type

PFID

Production facility ID (workcenter)

TRAM

Transaction amount

 

 

 

 

 

POMAST

Field

Description

ORDNO

Order number

VNDNR

Vendor number

INVFG

Inventory flag

VALIN

Invoice amount

PSTTS

PO status

HOUSE

Warehouse

PORCD

PO code

 

 

 


 

POITEM

Field

Description

ORDNO

Order number

ITNBR

Item number

HOUSE

Warehouse

LINSQ

Misc / service item sequence

QTYOR

Original order quantity

BLCOD

Blanket item code

REFNO

Reference number

INVFG

Inventory flag

DKQTY

Quantity received at dock

INSQT

Inspection qty

QTSCP

Scrap quantity

STKQT

Quantity received to stock

QTDEV

Quantity deviation

ACTPR

Actual price for order

ACTQY

Actual quantity for order

INVDS

Invoice flag

STAIC

Item order status code

RECRQ

Receipt required flag

TRAMT

Transaction amount

PURUM

Purchase unit of measure

UMCNV

Unit of measure conversion

DUEDT

Due date

DOKDT

Date due on dock

VNDNR

Vendor number

CURPR

Current unit price

FXBL

Fixed blanket code

SMRQ

Sum of releases

RPAM

RP cost amounts

 

POBLKT

Field

Description

ORDNO

Order number

ITNBR

Item number

HOUSE

Warehouse

LINSQ

Misc / service item sequence

BLKSQ

Blanket PO sequence number

INVFG

Inventory flag

RELQT

Quantity this release

STKPR

Stocking unit price

RELDT

Due Date this release

DOKDT

Date due on dock

DKQTY

Quantity received at dock

INSQT

Inspection qty

QTSCP

Scrap quantity

STKQT

Quantity received to stock

RECRQ

Receipt required flag

TRAMT

Transaction amount

STAIC

Item order status code

ACTQY

Actual quantity for order

INVDS

Invoice flag

OPNDV

Blanket release deviation qty

RPAM

RP cost amounts

 

 

 

POCOMT

Field

Description

ORDNO

Order number

ITNBR

Item number

HOUSE

Warehouse

LINSQ

Misc / service item sequence

BLKSQ

Blanket PO sequence number

CMSEQ

Comment sequence number

MESSN

Standard message number

CMNT1

PO comment (pos. 1-40)

CMNT2

PO comment (pos. 41-80)

OPSEQ

Operation sequence number

WKCTR

Production facility ID

WUFLG

Comment where used flag (A, P, G, T, R, C)

 

 

 

REQHDF

Field

Value

REQNO

Requisition number

ITNBR

Item number

QTYOR

Original order quantity

DATER

Requisition date

DOKDT

Date due on dock

DUEDT

Due date

ORDNO

Order number

INVFG

Inventory flag

UNMSR

Unit of measure

PURUM

Purchase unit of measure

UMCNV

Unit of measure conversion

REFNO

Reference number

 

 

ITEMASA (or ITMRVA)

Field

Description

STID

Site ID (ITMRVA only)

ITNBR

Item number

ITRV

Item revision (ITMRVA only)

INVFG

Inventory flag (1=inventory, 2=miscellaneous, 3=service)

  Note: 2 & 3 are non-inventory items

ITTYP

Item type code

UCDEF

Unit cost default

VNDNR

Vendor number

CUMCY

Current cumulative yield all operations (ITEMASA only)

 

ITEMASC (or ITMRVC)

Field

Description

RECRQ

Receipt required flag (0=no, 1=yes)

 

 

 

 

ITEMBL

Field

Description

ITNBR

Item number

HOUSE

Warehouse

RECMO

Quantity received this period

MOHTQ

On-hand total quantity

MPRPQ

On-order production quantity

MPUPQ

On-order purchase quantity

PURUM

Purchase unit of measure

UMCNV

Unit of measure conversion

 

 

 

ITMPLN

Field

Description

WHID

Warehouse

ITNB

Item number

ATRL

Auto release code

FTIM

Firm time fence

ATIM

Authorized time fence

ARCI

Contract use in auto release

 

 

 


 

SLQNTY

Field

Description

ITNBR

Item number

HOUSE

Warehouse

LLOCN

Location in warehouse

LBHNO

Batch / lot number

LQNTY

Location quantity

LPQC1

QC indicator no. 1

LCQC2

QC indicator no. 2

 

 

 

IMHIST

Field

Description

TCODE

Transaction code

ORDNO

Order number

ITNBR

Item number

HOUSE

Warehouse

TRQTY

Transaction quantity

TRAMT

Transaction amount

PRQOH

Previous quantity on hand

PRQOO

Previous quantity on order

STPCS

Current STP cost

PCOST

Previous STP cost

ENTUM

Entry unit of measure

VNDNR

Vendor number

REFNO

Reference number

NUQOH

New quantity on hand

INVFG

Inventory flag

BLKSQ

Blanket PO sequence number

REASN

Reason code

AVCST

Average unit cost

LBHNO

Batch / lot number

LLOCN

Location in warehouse

QCFLG

Quality control flag

ODUDT

Order due date

OPSEQ

Operation sequence number

PRLQ

Previous location quantity

LQNTY

Location quantity

 

INVTXN

Field

Description

TRTP

Transaction type

WHID

Warehouse

ITNO

Item number

ORDR

Order number

RECD

Reason code

CHGM

Charge amount

OFFM

Offset amount

VAAM

Variance amount

 

 

 

ROUTNG (with PDM)

Field

Description

ITNBR

Item number

OPSEQ

Operation sequence number

WKCTR

Production facility ID (workcenter)

TBCOD

Time basis code

MOVTM

Move time

PRTFG

Routing print flag

CYCOP

Cumulative current yield through previous operation

OSCS

Outside operation cost

NODES

Additional routing descriptions count

 

RTGHDR (with EPDM)

Field

Description

STID

Site ID

RTID

Routing ID

RTVR

Routing version

CUMCY

Current cumulative yield for all operations

 

 

 


 

RTGOPR (with EPDM)

Field

Description

STID

Site ID

RTID

Routing ID

RTVR

Routing version

 

 

 

(refer to ROUTNG for additional fields)

 

 

 

 

 

 


Appendix G.  For Reference: MAPICS Order Status Codes

The following status codes may affect the processing of outside operations.  For convenience, they are listed here as a reference.

 

PO / MO Cross-Reference Status Codes (STTS in MOPORF)

Status Code

Description

00

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Manufacturing Order Status Codes (OSTAT in MOMAST)

Status Code

Description

00

Not yet released

10

Released, but no activity reported

40

Activity started

45

Material complete.  Labor not complete.

50

Labor complete.  Material not complete.

55

Order complete

99

Order cancelled, no activity reported

 

Manufacturing Operation Status Codes (OPSTC in MOROUT)

Status Code

Description

00

Inactive

10

Active, no activity reported

20

Material moved to this operation

30

Activity reported

40

Operation complete

50

Material moved to next operation

 


 

Purchase Order Master Status Codes (PSTTS in POMAST)

Status Code

Description

10

Vendor acceptance required

20

Released, no activity

30

Activity reported

35

Invoiced complete.  Not received complete.

40

Received complete.  Not invoiced complete.

50

Order complete

60

Order selected for close

99

Order cancelled

 

PO Item and Blanket Release Status Codes (STAIC in POITEM & POBLKT)

Status Code

Description

05

Vendor acceptance required

10

Released, no activity

20

Received at dock

30

Received in inspection

40

Received to stock

50

Item complete

99

Item cancelled

 

 


Appendix H.  Implementing the New Outside Operation Process

Integrated Outside Operations is supported for MAPICS Release 6.  Download SH62694 for the application code, and refer to the cover letter for installation instructions.  Set the implementation flag (position 106 in the PCOPS2 record in SYSCTL) equal to 1 to activate the integrated outside operations function.

 

This user documentation is available via informational download SH14754.