Enter the initial system defaults during the installation process, and enter and change program parameters and defaults. The program displays definitions and explanations for each field that must be entered. You can only enter information for the enterprises and plants to which your user log-in is assigned in program SPDM, System User Default Maintenance, if you run this program from the menu.
Some parameter entry and maintenance programs allow you to access program NAWZ, The Wizard of NDS, with the drill down button. The information entered in the fields in the program from which you are running the wizard is carried over to the wizard for you to change.
Every Oracle user must have their actual schema and tenant name identified in this program.
Every Oracle user must have specific authorization to use a financial enterprise. This authorization is granted on page two of program SPUM, System Authorization Maintenance. The system is equipped with an initial financial enterprise, defined by the user during installation, which is authorized to the specified Oracle user. Each system installation will probably have a different Oracle user. Any new financial enterprise created must be authorized for the Oracle user before being allowed access to most financial programs.
Create or update financial enterprises. The system is installed with an initial financial enterprise, defined by the user during installation. Program GMEM, Enterprise Maintenance, is not required if you are running only inventory and manufacturing programs. However, if you are running any financial applications, it is required.
Financial enterprises can be organized hierarchically.
Determine the numbering structure of your enterprises and create the appropriate enterprises, in addition to the initial financial enterprise defined by the user during installation. Only one local enterprise must exist at startup. Any additional enterprises must be created but can be set up later as they are required.
When making the determination as to whether to have one database with multiple companies or to have companies in separate databases, the following are some of the criteria to consider.
* If multiple companies (enterprises) will be required to consolidate their financials, they should be within the same database.
* Vendors and customers are shared between all enterprises on a database but must be 'authorized' for each financial enterprise.
* Banks are specific to a single financial enterprise.
* Item Masters (inventory items) are shared between companies (enterprises) on a database.
Define the general ledger account number structure for each enterprise. This includes defining the segments of the account numbers. Account numbers are alphanumeric and can be up to fifty characters long, including the account separator.
There are four types for segments, Defined, Undefined, Automatic Undefined, and Soft-defined.
Defined segment values must be created in program GMSM, Maintain Segment Values, before they are used in program GLTM, Account Maintenance, to create accounts.
Undefined segment values are not created in program GMSM, Maintain Segment Values, but are created on the fly in program GLTM, Account Maintenance. Undefined segment values can only be created in program GLTM, Account Maintenance.
Automatic Undefined segment values can be entered in any of the sub ledger programs before the account has been created in program GLTM, Account Maintenance. However, a template account with the default information for the account and the default fill characters must exist in program GLTM, Account Maintenance, for the automatic undefined segment. For example, if the automatic undefined segment of an account number consists of the last three characters in the account number, the account number 200-10000-00-342 must have a template account such as 200-10000-00-000. When the sub ledger posts to the general ledger, the account is created.
Restructuring the chart of accounts can cause problems when a segment with the type of automatic undefined exists because data can be lost if existing journals have not been posted. To prevent this from occurring, you can use program GLTM, Account Maintenance, to create the accounts that exist in journals but have not yet been added to the chart of accounts. Pressing the [Automatic Accts] button will cause program GLTM, Account Maintenance, to search for account numbers with automatic undefined segments that have not yet been added to the chart of accounts. The accounts are displayed and can be added to the chart of accounts by pressing the [Create Accounts] button. This does not post the journal information, but the accounts are added to the chart of accounts and the journal information will not be lost.
Soft-defined segment types can be entered in program GLTM, Account Maintenance, before they are assigned a value in program GMSM, Maintain Segment Values. Once accounts with soft-defined segments are created, the user must define the entered values in program GMSM, Maintain Segment Values.
Enter and maintain segment values for defined and soft-defined segment types. Defined segment values must be entered before the accounts are created in program GLTM, Account Maintenance. Soft-defined values can be entered after the accounts have been created in program GLTM, Account Maintenance. Account segments are created with program GMDS, Define GL Structure, when the general ledger account number structure is created.
Create manufacturing enterprises. At least one manufacturing enterprise must exist. Any additional enterprises can be set up when they are required. Manufacturing enterprises are used to group plants for planning purposes. Planning parameters can be set for an item at the manufacturing enterprise level with optional local overrides for individual plants. In Master Scheduling, demand can be included from multiple plant codes within a manufacturing enterprise to the required manufacturing plant. This is done by making planned orders in other plants' demand in the manufacturing plant.
The system comes loaded with one manufacturing enterprise defined by the user during installation.
Create plant codes. At least one plant for each manufacturing enterprise previously created must exist. Plant codes must be linked to financial enterprises because they control access to the financial enterprise for sales order processing. Default stock area location, bin locations, and master scheduling parameters are included in the plant information.
The plant code can represent a factory, distribution center, remote warehouse, or store (for Point of Sale). Work orders, production schedules, material requirements planning (MRP), costing, and inventory are all specific to a plant. Postings for a single plant to general ledger from manufacturing and inventory are made to the financial enterprise specified in the plant master record. Financial enterprises can receive postings from more than one plant.
Defaults for batch shipping are also set up in this program.
The system comes loaded with one plant code defined by the user during installation.
Enter each Oracle user and specify their default financial enterprises, manufacturing enterprises, and plant in page one. You can specify allowed access to centralized purchasing and centralized sales order entry on page one and Point of Sale Supervisor Authority on page two. You can also create new user records. You cannot create new user records in program SPDM, System User Default Maintenance.
Set the following system level rules and defaults.
The code entered here is used for the installation and upgrades of the system, but is not validated against valid manufacturing enterprise codes. Codes are not validated at this stage because the default manufacturing enterprise is set up before the codes are. Therefore, there is nothing with which to compare it. After system installation, the manufacturing enterprise code entered in program SPUM, System Authorization Maintenance, for your user log-in is used instead of the entry here.
The code entered here is used for system installation and upgrades. After system installation, the plant code entered in program SPUM, System Authorization Maintenance, for your user log-in is used instead of the entry here.
This is the stock area that is used as the system level default when creating new plant records in program ILPM, Plant Code Maintenance. It is defined by the user during installation. The stock area you enter in program ILPM, Plant Code Maintenance, is the default in program ICMM, Inventory Master Maintenance. Stock areas are the major area definition. Bins are defined within the stock area using program ILMM, Location Master Maintenance.
Changes to the default area do not affect existing inventory items.
This is the bin location that is used as the system level default when creating new plant records in program ILPM, Plant Code Maintenance. It is defined by the user during installation. The bin location you enter in program ILPM, Plant Code Maintenance, is the default in program ICMM, Inventory Master Maintenance. Stock areas are the major stocking area definition. Bins are defined as detailed locations within the stock area using program ILMM, Location Master Maintenance
Changes to the bin location do not affect existing inventory items.
This is the control type that is displayed as the default for new item entries in program ICMM, Inventory Master Maintenance. The pop-list selections are as follows:
* Non-Controlled (the default in this program)
* Lot Control
* Serial Control
This is the control number generation rule that is the default for the automatic generation of control numbers. New items default to this rule when created in program ICMM, Inventory Master Maintenance. The default for that item can be changed in program ICEM, Item/Plant Maintenance. The system values are as follows:
* A Next Numeric Control Number. Generate the next control number as the next sequential numeric number. The program will look at the each character starting from the end of the last control number used, find the numeric part, and add a 1 to it. For example, if the last control number used was 900000G, the next control number will be 900001G.
* C Date + Sequence Number. Generate the control number using the date and sequence number. The system will create the control number according to the system date and put a three-digit sequence number at the end in the form YYMMDD-NNN. If more than one control number is created on the same day, the system will find the highest control number with the same date and add a one to the sequence number. For example, if two control numbers were created on the same day, the first might be 961230-001 and the second might be 961230-002.
* D First Available Unused. Generate the control numbers according to unused control numbers that have been set up previously in program ITCM, Item Control Number Maintenance. In order to use this rule, you must have previously set up control numbers in program ITCM, Item Control Number Maintenance. The program chooses the control number by looking at the First Rpt field. It will find the lowest control number that has the First Rpt field blank.
* M Manual entry. You manually enter the control numbers for this item. In order for this option to work, the generate rule must be set to Manual entry, and the Auto Create Ok flag must be set to on.
This is the automatic picking rule which is the default for automatic picking that is used as the default when creating new item or plant control records in program ICMM, Inventory Master Maintenance. It can be overridden in program ICEM, Item/Plant Maintenance. The system values are as follows:
* A Ascending Control Number. Pick control numbers by sequence, the lowest control numbers are picked first. If the item is lot controlled and the lots are split, the control numbers will be picked according to the bin sequence within the lot. This is providing that the bins are in a logical sequence.
* B Ascending On Hand Quantity. Pick control numbers according to the on hand quantity. The control numbers with the lowest on hand quantity will be picked first. If control numbers have the same on hand quantity, the program will pick the lowest control number first.
* C Smallest Lot. Pick control numbers from the smallest lot with a quantity that will satisfy the demand. This prevents the program from picking control numbers from more than one lot.
* D Lot Expiry Date Sequence. Pick control numbers according to the lot expiration date.
* E Date of First Receipt Sequence. Pick control numbers according to the date of first receipt. The control numbers received first are picked first.
* M Manual entry. Manually pick the control numbers.
Default Manufacturing Method: is a pop-list with the selection of Work Orders or Schedule. This default causes planned orders for an item to be automatically released as a Work Order or Production Schedule item by program WOAR, Automatic Work Order Release. Released Production Schedule orders are visible in program SRMM, Production Schedule Maintenance. Released Work Orders are visible in program WOEM, Work Order Entry/Maintenance.
This default defines the quantity that defaults into program SRFE's Quantity Received. This quantity is established by item in program ICPM, Inventory Planning Data Maintenance. It is established by the manufacturing enterprise on the Default ME Tab, and be the plant in on the Plant Tab. The options are Order Quantity or Case Quantity. The Case Quantity is a conversion used in production line receiving. It is defined as any number other than the total order quantity.
Scrap reporting rules are used to define what inventory values should be reported when a scrap transaction is entered for a particular type of transaction.
* SRFE - Scheduled Production Finished Goods Receiving Options:
Backflushed Components - Scrap only backflushed components
End Item - Scrap complete end item including labor
Nothing - Scrap nothing
* SRLE - Scheduled Production Labor Reporting options:
Backflushed Components - Scrap only backflushed components
End Item - Scrap complete end item including labor
Nothing - Scrap nothing.
* LREM/LRQE -Work Order Labor Reporting options
Backflushed - Components - Scrap only backflushed components
End Item - Scrap complete end item including labor
Nothing - Scrap nothing.
All Components - Scrap all components required to make an assembly when an assembly is reported as scrapped
Program SCEM, Scrap Entry Maintenance, requires the entry of the type of item being reported and uses the above rules for the appropriate type. Scrap entered in all programs is displayed in program SCEM, Scrap Entry/Maintenance.
The order number to be used for the next work order released by program WOAR, Automatic Work Order Release.
Checkbox set to on or off indicates whether requisitions will be generated automatically by the system. The Purchasing (PO) Module must be active (see program SPAP, System Parameters/Accounting Parameters) before you can set this checkbox to on. When set to on, it permits the automatic generation of two types of requisitions, material and service.
* Material These are requisitions for Purchase items (Make/Buy flag set to Purchase in program ICPM, Inventory Planning Data Maintenance). They are generated only during the automatic release of planned orders for these items by program WOAR, Automatic Work Order Release.
* Service These are requisitions for routing operations designated as type Outside Service in the routing master records. They are generated during both manual release, in program WOEM, Work Order Entry/Maintenance, and automatic release, in program WOAR, Automatic Work Order Release, for work orders which contain an outside service operation.
In any case, purchase requisitions can always be entered manually in program PORE, Requisition Entry/Maintenance.
This is a pop-list that indicates the type of scheduling, either forward or backward, that is to be used in Work Order and Production Schedule Releases.
In Forward Scheduling, for the initial operation scheduling, the first operation due date is scheduled as the work order due date minus the production lead time (lead time entered in program ICPM, Inventory Planning Data Maintenance) plus the manufacturing lead time. Each following operation is calculated as the due date of the preceding operation plus the manufacturing lead time.
In Backward Scheduling, the last operation start date is scheduled backward from the work order due date minus the manufacturing lead time (calculated from the routing operations) for that operation. Each preceding operation's start date is calculated backward from the start of its following operation.
This checkbox set to on or off indicates whether the firm flag default in program WOEM, Work Order Entry/Maintenance, and program WORP, Work Order Release Preparation, will be yes or no. If it is set to on, released work orders will default to firm due dates, and Master Scheduling and material requirements planning (MRP) will only advise rescheduling requirements. If it is set to off, released work orders will be generated with the default of non-firm which will allow the planning programs to automatically reschedule the released orders in the same manner as a planned order as determined by the program.
This checkbox on or off indicates whether the work order system will create the records required to track work order costs in the Manufacturing Costing Application. If it is set to off, the system will not create these records.
This checkbox set to on or off indicates whether the WIP Material Movement system is active. If this flag is set to on, the work order system will create the records needed to track the movement of material as it proceeds from one production operation to the next. If the flag is set to off, the system will not create these records, and material movement will not be tracked.
This is the WIP status code from program WPSM, WIP Status Codes Maintenance, which will be used as the default in the status field in work in process programs. The default in this program is "A". However, this code is not a yet valid code. You must create a definition for the code in program WPSM, WIP Status Codes Maintenance, or you will have invalid status codes in work in process programs.
This is a pop-list with the selection of Quantity Ordered or Quantity Reported. Backflush occurs when labor is first reported to an order.
Quantity Ordered The quantity required to do the entire job will be backflushed.
Quantity Reported The quantity backflushed will be the quantity required to equal the quantity reported as good and the quantity reported as scrapped.
This checkbox set to on or off indicates whether purchase order line quantities will be compared with the receiver line quantities. If this flag is set to on, you will not be able to enter a receiver line quantity in program REEM, Receiver Entry/Maintenance, which varies from the purchase order quantity by more than the tolerable receiver quantity variance percentage set in the Tolerable Receiver Quantity Variance Percentage field.
This is the purchase order vs. receiver line variance percentage that cannot be exceeded in program REEM, Receiver Entry/Maintenance.
The checkbox set to on or off indicates whether invoice line quantities will be compared with purchase order quantities. If this flag is set to on, and an invoice line quantity varies from the purchase order quantity by more than the tolerable invoice quantity variance percentage set in the Tolerable Invoice Quantity Variance Percentage field, then program APVM, Voucher Entry/Maintenance, will display a warning message and put the voucher on hold.
This is the invoice line quantity vs. purchase order quantity variance percentage outside of which program APVM, Voucher Entry/Maintenance, will display a warning message and put the voucher on hold.
The checkbox set to on or off indicates whether invoice line dollar amounts will be compared with purchase order unit costs. If this flag is set to on, and the invoice unit price varies from the purchase order unit cost by more than the tolerable invoice line dollar variance percentage set in the Tolerable Invoice Line Dollar Variance Percentage field, then program APVM, Voucher Entry/Maintenance, will display a warning message and put the voucher on hold.
This is the invoice line dollar amount vs. purchase order unit cost variance percentage outside of which program APVM, Voucher Entry/Maintenance, will display a warning message and put the voucher on hold.
The checkbox set to on or off indicates whether invoice total amounts will be compared with purchase order total amounts. If this flag is set to on, and the invoice total amount varies from the purchase order total amount by more than the tolerable invoice total dollar variance percentage set in the Tolerable Invoice Total Dollar Variance Percentage field, then program APVM, Voucher Entry/Maintenance, will display a warning message and put the voucher on hold.
This is the invoice total dollar amount vs. purchase order total amount variance percentage outside of which program APVM, Voucher Entry/Maintenance, will display a warning message and put the voucher on hold.
Enter and maintain the default company name, address, state, ZIP code, and country code. Verify that the following modules are activated:
General Ledger (GL)
Accounts Payable (AP)
Accounts Receivable (AR)
Purchasing (PO)
Master Scheduling (MS)
Establish the interface for automatic posting between the Accounts Receivable (AR) and General Ledger (GL) modules.
Enter material move parameters.
Use program SPAN, Auto Number Control, to enter automatic numbering for customers, purchase orders, item masters, receivers, transfer orders, prospects, audits, checkpoints, general ledger journals, general ledger posting templates, model releases, product costing, service accounts payable batch, service line number, and service master. These numbers can be manual or automatic. If the number is left blank, record type for which the number is left blank will be numbered automatically based on the numbers specified in program SPAN, Auto Number Control. The Starting Value and Maximum Value for the field allow 20 characters but must not exceed the number of characters for the specific data type it is controlling.
Data Type & Maximum Field Sizes
Audit transaction numbers - 20 characters
Checkpoint - 16 characters
Customer number - 10 characters
General Ledger journal numbers - 12 characters
General Ledger Posting Template - 10 characters
Item Number - 20 characters
Model Release number - 10 characters
Program Change Request number - 6 characters
Purchase order number - 10 characters
Prospect number - 10 characters
Receiver number - 10 characters
Service AP batch number - 10 characters
Service Line number - 10 characters
Service transaction number - 10 characters
Transfer Order number - 9 characters
Purchase orders and receivers were previously controlled by program POPM, PO / Receiving Parameter Maintenance. Item masters allowed auto numbering and creation of 12 digit UPC codes but any special prefix had to be set by the installer. Transfer Order numbers were previously established in program IXPM, Stock Transfer Parameter Maintenance.
To create the item numbers as United States standard 12 digit UPC codes, set the first 6 digits as the company, the next 5 digits as the product code and do not enter the twelfth digit. The program will calculate a twelfth digit as the check digit according to UPC rules.
To activate the feature, check active. To change sequence numbers, enter new values and press [Re-Create Sequence] button. Users are responsible for possible overlap of sequence numbers. This program does not check for possible future duplicates. Setting the cache size to 0 eliminates gaps in sequence numbers; any other value will cause gaps. Check cycle to have sequence number restart at the starting value when the max value is reached.
Establish sales order and invoice numbering parameters. Define the source for order numbers and invoice numbers. The options are by sales location, by financial enterprise, globally, and to derive invoice numbers from sales order numbers.
Assign programs to user menus on the menu screen for each user. This creates custom mini-menus by user for quick access to programs. This program can be run and re-run at any time.
Change the financial enterprise, manufacturing enterprise, and plant that you are accessing.
Set up the configuration for the floating toolbar and drill down depth gage.
If you are using the fulfillment house features, you must run this program to designate the schemas for the fulfillment house database master and fulfillment house customers. Enter the schemas and then set the pop-list to the desired setting. Shared tables are displayed on the right side of the screen.
Define the relationship between single database table and text file by importing and exporting data to and from text files.