Creating Outsource Operation Details for Style Items

Access the Style Item Outsource Operation Details form.

To create outsource operation details for style items:

Enter a branch/plant in the Target Branch/Plant field.
Enter a code in the Outsource Operation Code field.
Enter a value in the Style Item Root Level 0 field.
To create bills of material for outsource operations, complete the following fields:
- Component Branch/Plant
- Issue Type Code
To create routings for outsource operations, complete the following fields:
- Supplier Number
- Work Center
- Queue Hours
To create price and cost for outsource operations, complete the following fields:
- Operation Price
- Currency Code
- Effective Date
- Expiration Date
Click OK.

Target Branch/Plant

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.

Outsource Operation Code

A user-defined code (06/G) that identifies the jobs within your organization. You can associate pay and benefit information with a job type and apply that information to the employees who are linked to that job type.

For JD Edwards EnterpriseOne Apparel Management, the system compares the code in the Outsource Operation Code field to the code in the Job Type field of the outside operation routing step for the source branch/plant. The system verifies that the job type codes in the Outsource Operation Code and Job Type fields match during the outsource operation process.

Component Branch/Plant

A secondary or lower-level business unit. The system uses the value that you enter to indicate that a branch or plant contains several subordinate departments or jobs. For example, assume that the component branch is named MMCU. The structure of MMCU might be:

Branch/Plant - (MMCU)

Dept A - (MCU)

Dept B - (MCU)

Job 123 - (MCU)

Issue Type Code

A code that indicates how the system issues each component in the bill of material from stock. In JD Edwards EnterpriseOne Shop Floor Management, it indicates how the system issues a part to a work order. Values are:

I: Manual issue

F: Floor stock (no part is issued)

B: Backflush (when the part is reported as complete)

P: Preflush (when the parts list is generated)

U: Super backflush (at the pay-point operation)

S: Sub-contract item (send to supplier)

Blank: Shippable end item

You can issue a component in more than one way within a specific branch/plant by using different codes on the bill of material and the work order parts list. The bill of material code overrides the branch/plant value.

Supplier Number

The address book number of the preferred provider of this item.

Work Center

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 that represent lower-level business units subordinate to it. For example:

Branch/Plant (MMCU)

Dept A (MCU)

Dept B (MCU)

Job 123 (MCU)

Business unit security is based on the higher-level business unit.

Queue Hours

The total hours that an order is expected to be in queue at work centers and moving between work centers. The system stores this value in the Item Branch table (F4102). You can calculate this value using the Leadtime Rollup program or you can enter it manually. When you run the Leadtime Rollup program, the system overrides manual entries and populates the table with calculated values.

Operation Price

The unit cost of one item, as purchased from the supplier, excluding freight, taxes, discounts, and other factors that might modify the actual unit cost that you record when you receive the item.