Configure production control for unified manufacturing
Before starting, you need to set up production parameters and journal names in the Production control module.
- Parameters - Set up basic production parameters to define how the application must handle and process production orders. Define how they are created, estimated, scheduled, and consumed. You can also select what kind of feedback you want and how cost accounting must be conducted.
- Journal names - Identify the production journal names that you want to use to record and post ongoing transactions.
Production order journals record the different item transactions that occur when you work with production orders. These item transactions have a direct effect on a company's financial records.
When you post a production journal, all item transactions are automatically transferred to the general ledger. The General ledger module is the centralized location for financial data and information in Supply Chain Management.
The four types of production journals in Supply Chain Management are:
- Picking list – Issue raw materials to the WIP.
- Route card – Report labor as totals.
- Job card – Report labor as details with start and stop times.
- Report as finished – Receive finished goods into inventory and report good and bad quantities.
Several components of journal headers that you can consider include:
- Journal (header):
- Type – Controls the type of journal.
- Name – Controls the voucher, number, and behavior.
- Number – Provides a unique identifier.
Journal lines have different distinct features. They can differ by journal type, and can be used to record the following:
- Materials and quantities
- Operations and time spent
- Good and bad quantities
In addition to setting up the production control parameters at the company level, you can configure the production control parameters uniquely by site. If a site does not specifically have parameters assigned to it, Supply Chain Management uses the company configured parameters for that site.
Allocation keys
If an employee starts more than one job on the Job registration page, it is referred to as a bundle.
Allocation keys are used to define how, and which, bundled jobs or bundled registrations work within a specific area. The time spent on bundled jobs can be allocated to the individual jobs in different ways by using those allocation keys.
Allocation keys consist of the following components:
- Sites
- Production units
- Resources
- Resource types
- Bundle type
If you bundle jobs, you need to define and determine how the total registered time for all jobs should be allocated for each job. You can define the allocation by selecting one of the following options in the Bundle type field on the Allocation keys page:
- Estimation – Time is divided between the jobs based on the estimated time for the jobs.
- Jobs – Time is divided according to total jobs that are bundled and how much time was spent finishing all the jobs.
- Net time – Time is divided equally between the jobs that are in the bundle at any time.
- Real time – Actual job time is allocated. The cost can be calculated based on the actual payroll cost.
Production pools
Production pools group production orders into categories with shared characteristics. A production order can be assigned to a production pool. When you create a production order, you can assign it to a specific production pool. You can also assign a production pool to a Released product and since all products are required to have their posting profile by the item group, it will post transactions to the orders for the pool.
The following are example scenarios where production pools can be used to group:
- Orders that are ready to be produced
- Subcontracted orders that are missing deliveries
- Regular productions
- Orders that are missing materials
- Orders that are delayed because of machine failure
- Orders that are ready for release, start, or scheduling
Example 1
You can group subcontracted orders that are missing deliveries, production runs, orders that are missing materials, orders that are delayed because of some kind of machine failure, or orders that are ready for release, start, or for scheduling.
Example 2
You can create production pools for orders that are top priority or that have one production status. You can also assign a production pool to a Released product to define the method that is used to post transactions for the orders in the pool.
Example 3
A production pool can be used if you want to assign people who are specifically skilled for an operation of a production order, such as those who can get the job done in difficult situations.