FlexMFGAccountingCache

Flex MFG Accounting Cache

Minor Business Rule

Object Name: B3101370

Parent DLL: CMFGBASE

Location: Client/Server

Language: C

1.Functional Description
This function is used to maintain Flex MFG Accounting CACHE

1.1Purpose
Use this function to maintain the Flexible MFG Accounting cache.  This cache is used by the MFG
Accounting Update process to pass Key fields to the "Build Flexible Account" Business Function.  You can
use this function to add, update, inquire, and delete cache records. The records will be keyed by Job
Number since there will only be one MFG detail record passed from the MFG Update process at a time.

1.2Setup Notes and Prerequisites
         None.

1.3Special Logic

None.

2.Technical Specifications
2.4Processing
You can call this business function with four different actions (EV01):

1 = Retrieve
2 = Add / Update
3 = Delete
8 = Terminate CACHE

If the Action Code EV01 = '1' (Retrieve), fetch a record from the cache (using JOBS - Job Number as
the key). If error, return "Action Invalid" (0001) error message.

If the Action Code EV01 = '2' (Add/Update), will add a record to the cache with all the database
fields from the passed parameters if element does not exist (using JOBS - Job Number as the key).
Otherwise, fetch a record from the cache (using JOBS - Job Number as the key) and update the record in the
cache with all the database fields from the passed parameters.  If error, return "Action Invalid" (0001)
error message.

If the Action Code ='3' (delete), delete all matching records from the cache (using JOBS - Job Number
as the key). If error, return "Action Invalid" (0001) error message.

If the Action Code ='8' (Terminate), terminate CACHE from memory (using JOBS - Job Number as the
key).
If error, return "Action Invalid" (0001) error message.

Data Structure

D3101370 - Flex MFG Accounting Cache Data Structure

Parameter Name Data Item Data Type Req/Opt I/O/Both

cSuppressErrorMessage SUPPS char NONE NONE

A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function.        0 = allow
runtime error message handling.        1 = suppress runtime error message handling.

szDataItem 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.

cMode EV01 char NONE NONE

An option that specifies the type of processing for an event.

mnJobnumberA JOBS MATH_NUMERIC NONE NONE

The job number (work station ID) which executed the particular job.

szBranchPlant 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.

szCostCenter MCU char NONE NONE

An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units
for which you have no authority.

mnDocumentOrderInvoiceE DOCO MATH_NUMERIC NONE NONE

A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on.

szOrderType DCTO char NONE NONE

A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and
should not be changed: P Accounts Payable documents   R Accounts Receivable documents   T Payroll documents   I Inventory documents
O Purchase Order Processing documents   J General Accounting/Joint Interest Billing documents   S Sales Order Processing documents

mnSequenceNoOperations 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.

mnIdentifierShortItem ITM MATH_NUMERIC NONE NONE

An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:   o Item Number (short) - An eight-digit, computer-assigned item number     o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number     o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number

szTypeOperationCode OPSC char NONE NONE

A user defined code (30/OT) that indicates the type of operation. Valid values include: A Alternate routing   TT Travel time   IT Idle time   T Text

mnUniqueKeyIDInternal UKID MATH_NUMERIC NONE NONE

This field is a unique number used to identify a record in a file.

mnComponentNumber CPNB MATH_NUMERIC OPT NONE

A number that specifies how the system displays the sequence of components on a single-level bill of material. This number initially
indicates the sequence in which a component was added to the bill of material. You can modify this number to change the sequence in which the
components appear.

cParentChildRelationshi PART char OPT NONE

An option that specifies whether the system displays parent records or child records. If you turn on this option, the system displays parent
records for the address book number entered. Also a field that indicates whether a record is a parent or child. For the field, valid values
are: P Parent   C Child

szCostType COST char OPT 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.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cSuppressErrorMessage	SUPPS	char	NONE	NONE
A flag indicating whether or not runtime error messaging will occur when an error message is issued from a business function. 0 = allow runtime error message handling. 1 = suppress runtime error message handling.
szDataItem	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.
cMode	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
mnJobnumberA	JOBS	MATH_NUMERIC	NONE	NONE
The job number (work station ID) which executed the particular job.
szBranchPlant	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.
szCostCenter	MCU	char	NONE	NONE
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority.
mnDocumentOrderInvoiceE	DOCO	MATH_NUMERIC	NONE	NONE
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry, and so on.
szOrderType	DCTO	char	NONE	NONE
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and should not be changed: P Accounts Payable documents R Accounts Receivable documents T Payroll documents I Inventory documents O Purchase Order Processing documents J General Accounting/Joint Interest Billing documents S Sales Order Processing documents
mnSequenceNoOperations	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.
mnIdentifierShortItem	ITM	MATH_NUMERIC	NONE	NONE
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and so forth. The item numbers are as follows: o Item Number (short) - An eight-digit, computer-assigned item number o 2nd Item Number - The 25-digit, free-form, user defined alphanumeric item number o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item number
szTypeOperationCode	OPSC	char	NONE	NONE
A user defined code (30/OT) that indicates the type of operation. Valid values include: A Alternate routing TT Travel time IT Idle time T Text
mnUniqueKeyIDInternal	UKID	MATH_NUMERIC	NONE	NONE
This field is a unique number used to identify a record in a file.
mnComponentNumber	CPNB	MATH_NUMERIC	OPT	NONE
A number that specifies how the system displays the sequence of components on a single-level bill of material. This number initially indicates the sequence in which a component was added to the bill of material. You can modify this number to change the sequence in which the components appear.
cParentChildRelationshi	PART	char	OPT	NONE
An option that specifies whether the system displays parent records or child records. If you turn on this option, the system displays parent records for the address book number entered. Also a field that indicates whether a record is a parent or child. For the field, valid values are: P Parent C Child
szCostType	COST	char	OPT	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.