CheckForOutsideOperation

Check For Outside Operation

Major Business Rule

Object Name: B3000770

Parent DLL: CMFGBASE

Location: Client/Server

Language: C

1.Functional Description

1.1Purpose
Check for an outside operation in a Routing.

1.2Setup Notes and Prerequisites

• Setup for Cost Rollup - file Reset - Determines if the Cost Component Add-on recrod should be reset
for outside operations.  The Branche, Item Number, Routing Type, and Cost Component are passed in to
determine if the Cost Component Add-on record represents an outside operation.

1.3Special Logic

2.Technical Specifications

2.4Processing
1.0.  Initialize DS Outside Operation Exists = 0.

2.0.  Set Selection Where MMCU = DS Branch and KIT = DS Parent Item.

3.0.  If DS Routing Type is not equal to '*' or blank, set selection append_last TRT = DS Routing
Type.

4.0.  If DS Select Batch Quantity is equal to '1', set select append_last BQTY = DS Batch Quantity.

5.0.  If DS Operation Sequence is not equal to 0, set selection append_last OPSQ = Operation
Sequence.

5.0.  If DS Cost Component is not equal to '* or blank, set selection append_last COST = DS Cost
Component.

6.0.  Fetch record from the Routing Master Table until valid record is found or fetch fails.

6.1.  If fetch is successful and DS As of Date is not equal to NULL, check routing is ewithin date
effectivity range.  If no within date effectivity range, read next record.

6.2.  If fetch valid record found, process valid record.

6.2.1.Assign Ds Outside Operation Exists = '1'.
6.2.2. If DS return pointer is equal to '1', return pointer to data structure.

Data Structure

D3000770 - CheckForOutsideOperation

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szBranch	MMCU	char	NONE	NONE
A code that represents a high-level business unit. Use this code to refer to a branch or plant that might have departments or jobs, which represent lower-level business units, subordinate to it. For example: o Branch/Plant (MMCU) o Dept A (MCU) o Dept B (MCU) o Job 123 (MCU) Business unit security is based on the higher-level business unit.
mnParentItem	KIT	MATH_NUMERIC	NONE	NONE
The system provides for three separate item numbers. 1. Item Number (short) - An eight-digit, computer assigned, completely non-significant item number. 2. 2nd Item Number - The 25-digit, free form, user defined alphanumeric item number. 3. 3rd Item Number - Another 25-digit, free form, user defined alphanumeric item number.
szTypeRouting	TRT	char	NONE	NONE
A user defined code (40/TR) that indicates the type of routing. You can define different types of routing instructions for different uses. For example: M Standard Manufacturing Routing RWK Rework Routing RSH Rush Routing You define the routing type on the work order header. The system then uses the specific type of routing that you define in the work order routing. Product Costing and Capacity Planning systems use only M type routings.
mnBatchQuantity	BQTY	MATH_NUMERIC	NONE	NONE
The quantity of finished units that you expect this bill of material or routing to produce. You can specify varying quantities of components based on the amount of finished goods produced. For example, 1 ounce of solvent is required per unit up to 100 units of finished product. However, if 200 units of finished product is produced, 2 ounces of solvent are required per finished unit. In this example, you would set up batch quantities for 100 and 200 units of finished product, specifying the proper amount of solvent per unit.
cSelectBatchQuantity	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
mnOperationSequence	OPSQ	MATH_NUMERIC	NONE	NONE
A number used to indicate an order of succession. In routing instructions, a number that sequences the fabrication or assembly steps in the manufacture of an item. You can track costs and charge time by operation. In bills of material, a number that designates the routing step in the fabrication or assembly process that requires a specified component part. You define the operation sequence after you create the routing instructions for the item. The Shop Floor Management system uses this number in the backflush/preflush by operation process. In engineering change orders, a number that sequences the assembly steps for the engineering change. For repetitive manufacturing, a number that identifies the sequence in which an item is scheduled to be produced. Skip To fields allow you to enter an operation sequence that you want to begin the display of information. You can use decimals to add steps between existing steps. For example, use 12.5 to add a step between steps 12 and 13.
jdAsOfDate	ASDE1	JDEDATE	NONE	NONE
The date used for effectivity checking. Enter a specific date to display documents (orders, bills of material, routings, as applicable) that are effective on or after that date. The current system date is the default, but you can enter any future or past date.
szCostComponent	COST	char	NONE	NONE
A code that designates each element of cost for an item. Examples of the cost object types are: o A1 Purchased raw material o B1 Direct labor routing rollup o B2 Setup labor routing rollup o C1 Variable burden routing rollup o C2 Fixed burden routing rollup o Dx Outside operation routing rollup o Xx Extra add-ons, such as electricity and water The optional add-on computations usually operate with the type Xx extra add-ons. This cost structure allows you to use an unlimited number of cost components to calculate alternative cost rollups. The system then associates these cost components with one of six user defined summary cost buckets.
cReturnPointer	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cSuppressErrorMessages	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cOutsideOperationExists	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
idF3003Pointer	GENLNG	ID	NONE	NONE
General purpose ID variable.
szErrorMessageID	DTAI	char	NONE	NONE
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.

Related Functions

None

Related Tables

F3003 Routing Master File