Working with Demand Setup

This chapter provides overviews of demand records, demand rules, preferences, and net variance, and discusses how to:

• Set up demand rules for demand scheduling.

• Cross reference demand.

• Set up demand scheduling workflow.

• Run the Launch Demand Net Variance Workflow (R40R1110).

• Set up a product cumulative model.

• Set up a carton cumulative model.

• Set up item cross-references

Understanding Demand Records

A demand record stores the information that you use to maintain the requirements, scheduling information, rules, and other default information that is relevant to suppliers and customers. This information describes the components of a demand record.

Demand Rules

Includes settings to determine processing for demand cumulative quantities, and defines how requirements are updated during the shipping process.

Preferences

Includes scheduling fence dates, forecast dates, tolerances, pack rounding, and so forth. You can manage business requirements and link all of the preferences to one schedule.

Demand Header

Contains the default information that is relevant to a specific branch/plant, Sold To, Ship To, and item number for a demand requirement. Typically, information for demand records is created automatically using electronic data interchange (EDI).

Demand Detail

Includes the schedule information for firm demand (sales orders) and planned demand (forecasts), including quantities, dates, and the customer purchase order number.

Demand Packaging

Contains packaging information that is associated with a demand record.

Demand Addresses and Contacts

Contains addresses, contact names, and phones.

Demand History

Contains a snapshot of demand detail and demand address information, and distinguishes this information based on the date and time the snapshot was created.

Supplemental Demand

Stores information that is not included in the standard master tables. Examples of supplemental data include remarks, amounts, dates, codes, and times.

Demand Inactivity Analysis

Identifies items that have been inactive for a specified period of time, or are obsolete, or which may have errors that prevent processing.

The system uses these tables when processing demand records:

• F40R10

• F40R11

• F40R13

• F40R14

• F40R143

• F40R141

• F40R142

• F40R41

Understanding Demand Rules

Demand rules affect how the system processes demand data and cumulative quantities, as well as how requirements are updated during the shipping process. For example, demand rules enable you to:

• Specify the day on which a customer's week begins, allowing you to determine whether a demand record is associated with the current week or the prior week.

• Adjust shipment dates for nonworking days.

• Increase or decrease cumulative quantities when updating the cumulative quantity shipped.

• Replace the existing demand with the new demand that is associated with a particular Ship To record.

• Calculate ahead or behind values to adjust the demand before you create the sales order.

• Establish shipment and delivery times based on the branch/plant, Ship To, or Sold To time zones.

You set up demand rules at the customer or ship to level, and needs to occur only once for each customer.

The system uses these tables when processing demand rules:

• F40R11

• F40R12

• F40R41

• F40R42

• F40R12WF

• F40R20

• F40R23

• F40R24

Understanding Preferences for Demand Scheduling

You can set up preferences to handle different business requirements and link all of the preferences to one schedule. This information describes the preferences you can set up for demand scheduling.

Scheduling Fences (Preference Type 27)

You can set up two fences when creating sales orders and forecasts. You set up the firm shipment fence to specify the number of demand days for which you create sales orders. You set up the planned forecast fence to specify the number of days for which you create forecasts. The criteria that you use is Sold To, Ship To, and item.

Forecast Dates (Preference Type 28)

Usually, customers send only a single date when dealing with planned demand. To generate the forecast record, you can set up a preference that specifies how a customer sends their planning demand. The system uses these values for this purpose:

• Month Calculation

• Month Begin/End

• Week Begin/End

• Anchor Day of Week

Net Variance Tolerance (Preference Type 31)

When you set up net variance, you specify how the system processes these types of information:

• Tolerance level

• Notification level

• Critical indicator

This information helps you determine when the variance is considered significant and whether to issue a notification. For example, if the net variance setting is greater than the notification level, the system can send a notification message. You use the critical indicator to attach a ranking significance to the percentage amount.

Round to Standard Pack (Preference Type 32)

Most customers want their suppliers to ship items in a standard pack quantity. For example, if a standard pack is 100 pieces in a carton, and the customer orders 75, the supplier must ship 100 pieces. You can specify whether the Round to Standard Pack option is active when you create a demand header record. You set up this preference based on the Sold To, Ship To, and item values.

Acknowledgment Notification (Preference Type 33)

The EDI acknowledgment message indicates acceptance or rejection of a previously sent EDI message, such as the Advanced Ship Notice or the invoice. This preference returns an address book number of a person to be notified. You set up this preference using the Sold To, Ship To, Acknowledgment Code, and Message Being Acknowledged values.

ASN Tracking Workflow (Preference Type 34)

Typically, when the customer receives the ASN, they send back an EDI Acknowledgment to the supplier indicating acceptance or rejection of the ASN. You set up this preference to specify how long to wait for the returning ASN before sending a message indicating that an EDI Acknowledgment message has not been received. The system sends the message to the appropriate address book number. You set this preference up based on the Sold To and Ship To values.

Message Notification (Preference Type 35)

You use this preference to specify which address book number to use for sending notifications. You can set up this preference based on these criteria:

• Branch/Plant

• Sold To/Ship To

• Notification Field:

• 00 = Net Variance

• 01 = Sales Orders

• 02 = Forecast/Planning

• 03 = INVRPT (Inventory Advisement)

• 04 = ASN

• 05 = CUM

• 06 = Adjust Demand

• 07 = Inbound Demand

• 08 = Acknowledgments

• 09 = EDI Maintenance

EDI Advance Ship Notice (Preference Type 36)

You use this preference to specify whether workflow runs and to whom the system sends the message. This preference is based on these values:

• Ship To and Sold To

• Acknowledgment Code

• Message Being Acknowledged

For example, you set up preferences to run workflow for all Sold To and Ship To values, but only for Advance Ship Notices that are rejected. If the system receives an acknowledgment with an R (rejected) acknowledgment code for an 856 Message Being Acknowledged, the system sends you a workflow message that contains a link to the appropriate record on the Work with EDI Acknowledgments form (W47191A).

Label Processing (Preference Type 37)

You use this preference to activate label processing at the branch/plant level. You specify the party ID (values for Party Type 1 and 2) in the F40R14 table to retrieve for outbound label data. An example of a party ID is the supplier code or plant code.

For inbound label data, you specify the version for Carton Reorganization (P4620), and specify whether to automatically allocate sales order quantity to cartons. You must also specify the name of the third-party that processes the XAPI response.

Label Serial Numbers (Preference Type 38)

You use this preference to specify the label next number for outbound and inbound labels, as well as UCC128 information for inbound labels, including:

• Company UCC code

• SSCC document company

• SSCC document type

• Label generation function

• Label validation function

• Electronic product codes (EPC)

Carton Label (Preference Type 39)

You use this preference to specify whether a carton code should be assigned a label serial number. Label numbers creation must be on in either the Label Serial Number (38) preference or the version for Carton Reorganization (P4620). This preference is useful when items are packaged in multiple cartons but only outer cartons are labeled.

For example, if packaging for an item consists of a box, carton and pallet, you can specify whether to generate a label number for the pallet, for the pallet and carton, or for the pallet, carton and box.

Understanding Demand Net Variance

Net variance is the percent variation between current and previous order quantities for an item. You can specify net variance information at the item or customer level and use it to prepare for unexpected demand changes. For example, you can specify whether to alert a supplier if requirements change significantly as the supplier's ship date approaches, regardless of whether the change is an increase or decrease in order quantities.

You set up how the system processes net variances on the Net Variance tab in the Demand Maintenance (P40R10) processing options. You specify how the system processes these types of information:

• Tolerance level

• Notification level

• Critical indicator

When you set up net variance, you determine net variance days from the requested ship date, demand period, and demand processing type. This information helps you determine when the variance is considered significant and whether to issue a notification. For example, if the net variance setting is greater than the tolerance level, the system considers this difference as a significant change and displays net variance and critical ID information on the Work with Demand Detail form and on the Shipment tab on the Demand Detail Revisions form.

If the net variance setting is greater than the notification level, the system can send a notification message to an address book to alert you of the change. You can use the critical indicator to attach a ranking significance to the percentage amount.

Setting Up Demand Rules for Demand Scheduling

This section discusses the forms and processing options for demand rules and set up:

Forms Used for Setting Up Demand Rules

Setting Processing Options for Demand Rules (P40R20)

Processing options enable you to specify the default processing for programs and reports.

Default Values

This processing option enables you to specify how the system processes information when you add demand rules.

Setting Up Demand Rules

Access the Demand Rules Revisions form.

Branch Plant	Enter 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.
Sold To	(Optional) Enter a user-defined name or number that identifies an address book record. You can use this number to locate and enter information about the address book record. If you enter a value other than the address book number, such as the long address or tax ID, you must precede it with the special character that is defined in the Address Book constants. When the system locates the record, it returns the address book number to the field. For example, if address book number 4100 has a long address TOTAL and an * distinguishes it from other entries, you could type *TOTAL into the field, and the system would return 4100.
Ship To	(Optional). If you complete the Ship To field, you must also complete the Sold To field.
Weekly Start Day	Enter a user-defined code (UDC) (42/DW) that represents the day on which the customer's week begins. When the system removes outdated demand records, the system uses this code to determine whether a demand record is associated with the current week or the prior week.
CUM Adjustment Code for Shipments (cumulative adjustment code for shipments)	Enter a UDC (40R/CA) that identifies the type of adjustment that results from the shipment process.
Replace by Ship To	Select this option to determine whether the system replaces the existing demand with the new demand that is associated with a particular ship to record. If you do not select this option, then the system does not replace the existing demand.
Calculate Ahead and Behind Firm	Select this option to determine whether you can adjust the demand by modifying either the quantity that you have already shipped (also known as ahead amount) or the quantity that you need to ship (also known as behind amount) in relation to the customer's requirements. If you select this option, then you can adjust the demand before you create the sales order.
Calculate Ahead and Behind Plan	Select this option to determine whether you can adjust the demand by modifying either the quantity that you have already shipped (also known as ahead amount) or the quantity that you need to ship (also known as behind amount) in relation to the customer's requirements. If you select this option, then you can adjust the demand before you create forecast records.
Put Sales Order on Hold	Select this option to determine whether the system places a sales order on hold when the cumulative quantity shipped has reached zero. If you do not select this option, then the system does not place the sales order on hold. Note. Placing a sales order on hold when the cumulative quantity shipped has reached zero creates a difference in the actual quantity shipped versus the contract amount to be shipped.
Remove Partial Shipped Demand	Select this option to determine whether the system removes a demand detail record when only a partial quantity of the required shipping quantity has been shipped. Some customers allow their suppliers to ship only part of the requirement and then consider the shipment complete. However, if the customer wants the remainder of the quantity, the customer adjusts for the quantity in the next EDI transmission. Customers who want the requirement to remain open until it is fully shipped also use adjustment processing, they access from the ship confirm EDI message.
Partial Shipment Indicator	Indicate whether demand will be identified as a partial shipment upon the release of backordered demand. This is based on an appended value of "S" to the pull signal on the sales order (F4211). Values are: Blank: Do not populate the pull signal on the sales order (F4211) with the value S. 1: Populate the pull signal on the sales order (F4211) with the value S.
Quantity of One Container Definition	This flag determines whether or not the quantity of one will be converted into the standard pack quantity for the current item. Values are: Blank: No conversion into Standard Pack. The inbound quantity and UOM will be processed. 1: Convert quantity and UOM into the standard pack for the current item. If no definition is found, a workflow message will be generated. You define standard pack recommendations for an item through the Item Standard Pack (P460131).
Add Old Demand to CUM Required (add old demand to cumulative required)	Select this option to determine whether the system adds the quantity of the demand detail that was removed to the value in the CUM Required Priorfield when you run the Purge Demand History Record program (R40R094). If you do not select this option, then the system does not add the quantity of the demand detail that was removed to the value in the CUM Required Prior field.
Replace CUM Required (replace cumulative required)	Select this option to allow the supplier to override the cumulative quantity of an item that the customer requires. If you select this option, the supplier can override the cumulative quantity.
Use Prior Day CUM Shipped (use prior day cumulative shipped)	Select this option to determine whether the system displays the previous day's CUM quantity shipped on the bill of lading and the advanced shipping notice (ASN). If you do not select this option, then the system displays the CUM quantity shipped for only the current day.
Add Line to CUM Shipped (add line to cumulative shipped)	Select this option to specify whether the system includes the quantity of the current line item when it calculates the cumulative total of items that were shipped. The system uses this option for the bill of lading and Advanced Ship Notice (ASN).
Don't Adjust	Select this option to specify whether the system adjusts the ship date for non work days when you run the schedule creation process. Values are: Blank: The system does not adjust the ship date. 1: Changes the ship date to an earlier date. 2: Changes the ship date to a later date.
Increment	Select this option to specify whether the system increases or decreases CUM quantities when updating the CUM quantity shipped. If you do not select this option, the system increases CUM quantities.
Decrement	Select this option to specify whether the system increases or decreases CUM quantities when updating the CUM quantity shipped. If you do not select this option, the system increases CUM quantities.

Time Zones

Select Time Zones

Versions

Select Versions

Cross Referencing Demand

This section provides an overview of and discusses cross references and how to cross reference EDI codes to the demand type.

Understanding EDI Cross References

When EDI data enters the system, the codes are used to identify the type and the frequency of the requirement. Requirement codes are standard within the EDI system, but their uses can vary, depending on each customer's business practices, as described in the table:

In order to handle these differences, you must set up a cross reference record for each requirement type and requirement frequency combination. This record specifies the demand type (firm or plan) and the frequency of demand (such as daily). The system processes theDemand Type and the Demand Period fields to determine the requirement.

You can set up cross references for all Branch/Plant and Sold To records, all Sold To records for a Branch/Plant, or for a specific Sold To record.

Prerequisites

Before you complete the tasks in this section:

• Set up UDC 40R/DT for the demand type and period.

• Set up UDC 40R/PD for the demand period.

Forms Used for Cross Reference EDI Codes to the Demand Type

Cross Referencing EDI Codes

Access the Demand Processing Cross Reference Revisions form.

Requirement Type and Requirement Frequency	Enter a code from the EDI transaction set/message that indicates the type of demand and the frequency of demand.
Demand Type	Enter a UDC (40R/DT) that specifies whether the demand is firm or planned. The demand type is used to determine how the system processes demand.
Demand Period	Enter a UDC (40R/PD) that identifies the period of time for a demand record.

Setting Up Demand Scheduling Workflow

This section provides an overview of and discusses demand scheduling workflow and setup.

Understanding Demand Scheduling Workflow

You can set up workflow to run during the inbound demand process of editing and updating records. You can use a default workflow process that contains all the possible business functions that can be run during inbound demand processing. The default workflow process contains a list of all the possible business functions that can be run during the inbound demand process. If you do not need any of these business functions, you must duplicate the workflow process and then use the new workflow process to add or remove unnecessary business functions.

The system does not allow you to create or duplicate workflow processes in the Demand Workflow Maintenance program (P40R22). The workflow process you specify must be an existing workflow process in the F98800 table. However, information regarding the workflow process, such as workflow activities, is handled by the Process Master program (P98800) and is stored in other database tables.

The system stores demand workflow information in the F40R22 table.

Forms Used for Setting Up Demand Scheduling Workflow

Setting Up Workflow

Access the Demand Workflow Revisions form.

Process Name

(Optional). Enter the unique identifier for a process. If no value is entered, a next number is assigned. Once assigned, the value cannot be changed. If you do not want to run a workflow for a specific Branch/Plant, Sold To, and Ship To combination, leave the Process Name field blank. Otherwise, the Process Name must be a valid workflow process name in the F98800 table.

Note. Although the Branch/Plant, Sold To, and Ship To fields are optional, if you enter a Ship To value, the Branch/Plant and Sold To must be completed. The same is true that if you enter a Sold To value, the Branch/Plant must also have a value.

Running the Launch Demand Net Variance Workflow (R40R1110)

You run this report automatically by specifying the version in the Launch Net Variance Workflow (R40R1110) processing option on the Versions tab in the processing options for Demand Maintenance (P40R10). You can run this report over specific batches of demand records to review net variance amounts that exceed the notification level for each record. If the system does not find matching Demand Detail records, the system will not launch the batch program.

Note. If you want to run the Create Demand Schedule batch program (R40R010) in addition to manually running the Launch Demand Net Variance Workflow batch application, you should run R40R1110 first. Depending on settings, the Create Demand Schedule program may delete demand detail records.

The system uses the F40R11 table for processing net variance workflow information.

Setting Up Product Cumulative Models

This section provides an overview of and discusses product cumulative models.

Understanding a Product Cumulative Model

Because each customer may wish to track this information differently for each branch/plant record, you can specify whether to track by Branch/Plant, Branch/Plant and Sold To, or Branch/Plant, Sold To, and Ship To. You can then specify whether the customer tracks information specific to a Ship To, Customer PO, or any combination of three defined fields.

For example, a customer may track cumulative quantities at a Ship To and Model Year level. To set up this type of model, you would use the Ship To option and enter the user-defined code (UDC) associated with Model Year in User Field 1.

You can associate each cumulative model combination with multiple cumulative records, each distinguished by a different customer item number, which you set up using the CUM Maintenance program (P40R12).

This table indicates the differences between four example models, followed by examples of how you can set up each model to track cumulative information:

An infinite number of model combinations exist that you can set up using any combination of the Sold To, Ship To, Customer PO, and user-defined fields.

Model 1

In the this model, the cumulative information is tracked for GM using only the Sold To and Model year values. Each record with the Sold To, User Defined Field Type, and Model Year value combination is referred to as the cumulative model combination. Each row indicates a separate cumulative model combination for which information is tracked.

Model 2

This model is set up for GM using Sold To, Ship To, and Customer PO specifically where the Ship To is Livonia.

Model 3

This model tracks cumulative records by using Sold To and Ship To values. Unlike Model 2, however, no Ship To is specified. This model is useful for tracking each distinct Sold To/Ship To model combination.

Note. Models that you set up for a specific Ship To address override the model that you set up for a wide range of Ship To addresses.

Model 4

This model indicates that Ford Wixom can track cumulative information using a model that is distinct from the model used by most of Ford's Ship To addresses, as detailed in Model 3. Ford Wixom can track by Sold To, Ship To, Model Year, and Dock. The model combinations are as follows:

Forms Used for Setting Up a Product Cumulative Model

Setting Up a Product CUM Model

Access the Product CUM Model Revisions form.

CUM Tracking (cumulative tracking)	Select this option to determine whether the system tracks cumulative quantities of an item. If you do not select this option, then the system does not track cumulative quantities. Note. You must setup a Product CUM model whether tracking CUM or not.
Ship To	(Optional) Select this option to determine whether the system tracks CUM quantities at the Ship To level. If you do not select this option, then the system does not track CUM quantities at the Ship To level.
Customer PO (customer purchase order)	Select this option to determine whether the system tracks CUM quantities by customer purchase order. If you do not select this option, the system does not track CUM quantities by customer purchase order.
Field Type	(Optional) Enter a UDC (40R/UF) that the system uses for tracking CUM records.

Setting Up Carton Cumulative Models

This section provides an overview of and discusses carton cumulative models.

Understanding Carton Cumulative Models

You can set up carton cumulative models to help you track and identify the carton elements that are specific to a product being shipped. Carton cumulative models are limited to using Sold To and Ship To values to differentiate the models.

You can associate each cumulative model combination with multiple cumulative records, each distinguished by a different customer item number, which you set up using the CUM Maintenance program (P40R12).

You can track cumulative information at the carton level using either the Sold To or Ship To values as these models describe:

Model 1

In one model you can specify that GM tracks carton cumulative information by the Sold To address. For each combination of Sold To and carton, the system tracks a separate record.

Model 2

In this model, the system tracks information separately for GM Livonia from all others.

Model 3

In this model, the system tracks information by the Sold To and Ship To addresses. For each Sold To, Ship To, and carton combination, the system creates a new record.

Prerequisite

Ensure that you have set up the carton as an item.

Forms Used for Setting Up a Carton Cumulative Model

Setting Up a Carton CUM Model

Access the Carton CUM Model Revisions form.

CUM Tracking (cumulative tracking)	Select this option to determine whether the system tracks cumulative quantities of an item. If you do not select this option, then the system does not track cumulative quantities.
Ship To	(Optional) Select this option to determine whether the system tracks CUM quantities at the Ship To level. If you do not select this option, then the system does not track CUM quantities at the Ship To level.

Setting Up Item Cross-References

This section provides an overview of item cross-references and discusses how to maintain cross-references.

Understanding Item Cross-References

As part of inventory management, you can define relationships between the company's item information and the item information of a supplier or customer. Additionally, you can set up substitute items, replacement items, and bar codes that are associated with an item. Cross-references associate the internal item numbers with those from other trading partners. The Item Cross Reference program (P4104) enables you to manage these relationships in the JD Edwards EnterpriseOne Inventory Management system. For example, suppose that a customer orders items using the customer's item numbers. If you have the Item Cross Reference program set up for the customer, you can easily convert those item numbers into the company's equivalent numbers.

Examples of cross-referenced items are:

• Vendor item numbers.

  Use when you are required to use vendor part numbers on orders or communications.

• Customer item numbers.

  Use so that customers can order with their part numbers.

• Substitute items.

  Use when the ordered item is out of stock.

• Replacement items.

  Use when you or vendors discontinue an item and replace it with a new item.

• Bar codes.

  Use to associate bar code input with a specific item.

• Associated items.

  Use to recommend other, associated items as part of the sale.

When setting up cross-references for EDI, you need to cross-reference every possible number that the trading partners might transmit.

Prerequisite

Before setting up item cross-references, set up UDC table 41/DT for the cross-reference types that you define.

Forms Used to Set Up Item Cross-References

Maintaining Cross-References

Access the Item Cross Reference Revisions By Address form or the Item Cross Reference Revisions By Item form.