Reviewing an unprocessed plan

In the detail view of the Unprocessed Plans page, the details of an unprocessed plan are displayed.

To review an unprocessed plan:

  1. Select Release Management > Unprocessed Plans.
  2. Click the Drill down button of an unprocessed plan.
  3. On the Single Plan tab, review the header information of the single plan:
    Customer
    The customer of the unprocessed plan. The customer is an arbitrary set of characters that is used to uniquely identify a customer in an accounting entity. The customer is taken from the ERP system.
    Customer Order Number
    This field shows the customer's identity number that is assigned to a specific order.
    Current Received CUM
    The current cumulative quantity of goods that is received and confirmed by the customer. The current received cumulative quantity is based on the last reset date.
    New Release Number
    The new release order number.
    New Release Date
    The new release order date.
    Calculation Date
    If a new plan is imported and does not contain a calculation date, it is imported to the Unprocessed Plans page. Edit the calculation date to enable the plan to be re-validated. After being re-validated, it is imported as a new plan. The calculation date logic applies only to single plans for which the calculation date setting has been defined as Delete all Requirements before Calculation Date on the Requirement Consolidation Rules page.
    Note: When a new plan arrives, all requirements from the current plan dated prior to the Calculation Date value of the new plan are removed. Next, the requirements from the current plan are copied into the new plan. Lastly, every requirement from the new plan is loaded even if there are items before the start date in the new plan.
    Ship To
    The ship to of the customer. This field indicates the location code that is used with the ship to location to identify where the goods are shipped.
    Last Received Date
    The last received release order date.
    Last Received Quantity
    The last received release order quantity from the customer.
    Old Release Number
    The previous release order number.
    Old Release Date
    The previous release order date.
    Customer Item
    The customer item identifier of the single plan that is used by the supplier.
    CUM Reset Date
    The reset date of the cumulative quantities.
    CUM on Reset Date
    The field shows the total cumulative quantity on the CUM reset date.
    Release Horizon Start Date
    The field shows the start date of the time horizon for the release order.
    Release Horizon End Date
    The field shows the end date of the time horizon for the release order.
  4. On the Single Plan tab, review the field sets CUM Information, EDI CUM Information, Release Information, and Trading Partner Information.
    The field sets show details of the cumulative quantities, the release order, and the trading partner. The CUM information that is shown in this context is a comparison of the current values and the new values of the unprocessed plan. The EDI CUM information includes the details from the BOD (such as LoadPlanningSchedule and LoadShipmentSchedule). Old and new values of the total shipped CUM, current shipped CUM, total shipped CUM of LSP, and current shipped CUM of LSP are shown.
  5. Expand the Flex Fields field set to review the fields.
    See Viewing Flex Fields in Release Management.
  6. In the Requirements section, the order lines of the unprocessed plan show the specific customer releases per message type. Click the Drill down button of an order line to review the information in the New Schedule Requirement dialog box:
    Line
    The line number of the order line. The order lines are sorted by requirement date. Earlier requirements have lower line numbers.
    Requirement Date
    The requirement date indicates the date at which the ordered goods must be available at the customer's location.
    Requirement Quantity
    The requirement quantity of the order line.
    Level of Commitment
    The level of commitment of the order line. The level of commitment determines the degree to which a requirement of the release order is binding. These options are available for the level of commitment:
    • Firmed: Firm requirement.
    • Fabrication Release: Serves as an information about the production release of the ordered items that must be manufactured and shipped by the supplier.
    • Raw Material Release: Serves as an information about the release of raw material that must be ordered by the supplier.
    • Planned: Planned requirement.
    Frequency

    The frequency of the requirement. These options are available for the frequency:

    • Day and Time: Daily requirements that have a specified time.
    • Day: Daily requirements.
    • Cancel Daily Reqmt.: Cancellation or reduction of daily requirements. A planning schedule of frequency type Cancel Daily Reqmt. removes or reduces the previously published requirement, if the trading partner sends negative requirement quantities.
    • Day Range: Day range requirements.
    • Week: Weekly requirements.
    • Week Range: Week range requirements.
    • Month: Monthly requirements.
    • Flexible: The requirements of frequency type Flexible are monthly requirements. These requirements are distributed over weeks whereby the new requirements start with the end date of the previous requirements. In consequence, the requirements are continuously ongoing scheduled.
    Type of Requirement
    This field classifies requirements without concrete requirement dates. These requirements are assigned requirement dates according to their priorities. Usually, this is the current date or in case of remaining requirements a requirement date after the time horizon of the last scheduled requirement. These options are available:
    • Standard Requirement: This is the default setting for scheduled requirements that have a specified requirement date.
    • Backorder Requirement: Backorder requirement that is scheduled on the current date. The level of commitment of a backorder requirement is Firmed, that is, a firm requirement.
    • Immediate Requirement: Immediate requirement that is scheduled on the current date. The level of commitment of an immediate requirement is Firmed, that is, a firm requirement.
    • Remaining Requirement: Remaining requirement that is scheduled after the time horizon of the last scheduled requirement. The level of commitment of a remaining requirement is Planned, that is, a planned requirement.

    In combination with the Frequency and Level of Commitment fields, the Type of Requirement field allows a unique classification and handling of these requirements.

    Shipped Quantity
    The shipped quantity of the order line.
    Net Quantity
    The calculated net quantity of the order line.
    1. Reference Number
    This field shows the first document reference number of the order line. The incoming release order must be a referenced requirement. The first reference number must be defined as the referenced key field in the CUM adjustment rule.
    2. Reference Number
    This field shows the second document reference number of the order line. The incoming release order must be a referenced requirement. The second reference number must be defined as the referenced key field in the CUM adjustment rule.
    3. Reference Number
    This field shows the third document reference number of the order line. The incoming release order must be a referenced requirement. The third reference number must be defined as the referenced key field in the CUM adjustment rule. The third reference number is only displayed in the order lines of the Shipment Schedule tab in the detail view of the Plans page.
    Expected Delivery Date
    The expected delivery date and time. The field is used for trading partner A0230 Renault Europe.
    Dock Code
    The receiving location of a customer or the shipping location of an organization, for example, a gate number for trucks.
    Routing Code
    The routing code defines the route for the transportation of goods. For example, the routing code is sent in DELJIT message on requirement level by the trading partner PSA. In the Alternative Logistics process of the trading partner, the routing code is unique per transport handling unit.
    Consumption Point
    From the drop zone, an item may be distributed on multiple consumption points.
    Customer Storage Location
    The field shows a location within the plant or warehouse where the goods are stored after receipt. A location indicates an organizational unit that is used to differentiate the item from other items that belong to different organizational units.
    Distribution Zone
    This field shows the delivery point from which the delivery is distributed to the consumption points. This field is used by French trading partners.
    Transport ID
    Transport ID of the forwarder for the transportation, which is predefined by the customer. The transport ID is similar to a shipper number of a customer or a pick-up sheet number that combines deliveries into one shipment.
    RAN
    Release Authorization Number of the customer that uniquely identifies a firm requirement. Abbreviation: RAN. The RAN number is used instead of CUMs to synchronize release orders. A RAN number is unique per pick-up date/time, arrival date/time, transport ID, and ship to location. In consequence, the same RAN number can be valid for different distribution zones and consumption points.
    Project Number
    This field shows the project number of the release order.
    Dispatch Call-off Number (VAB)
    The binding schedule that is sent to the supplier one day before picking up the material at the supplier's location. Dispatch call-offs that are especially used by VW and Audi are sent to the supplier in the format GLOBAL DELJIT.
    Model Year
    The year in which the item was manufactured. Some Original Equipment Manufacturers (OEMs) send their schedules per model year. For example, the trading partner Chrysler sends EDI planning schedules per model year. The model change happens once in a year. Schedules for the old and new model year are sent to the suppliers for a short overlapping time horizon. To support this process in Release Management, the Standard Planning Schedule field mapping provides the field Model Year on requirement level.
    Delivery Instruction Number
    The field shows the number of the binding delivery specification. It must be met by suppliers and forwarders to fulfill the customer's requirements for the manufacturing, transportation, and delivery of goods.
    Delivery Instruction Revision
    The field shows the revision level of the valid delivery specification.
  7. Review the information that is shown for sequenced requirements in the Sequencing Information field set:
    Line Feed Location
    The line feed location is a delivery location that is defined by the customer. It is transferred by release orders that have the message subtype Sequenced. The line feed location indicates the place on the assembly line. If there are several assembly lines such as in a large plant, then the line feed location indicates which assembly line.
    Vehicle Identification Number
    The vehicle identification number (VIN) consists of a structured combination of characters that is assigned to each vehicle by its manufacturer. The VIN is used by some OEMs to identify a vehicle on the assembly line for which an item is required. If, for example, the item is an assembly part of a car, then the number in the current field is the number of the car.
    Job Sequence Number
    The sequence number of the job for which the items are required. For example, in the sequencing process of the trading partner Smart a sequential forecast message is processed. When the message is processed, this field contains the planned job sequence of a vehicle. When the production sequence is completed, a sequential call-off message is processed. This field then contains the final job sequence of the vehicle. This is the job sequence on the assembly line for which the items are required.
    Logical Sequence Reference
    The logical sequence reference number of the manufacturer. For example, in the sequencing process of the trading partner Smart a sequential forecast message is processed. When the message is processed, this field contains the planned job sequence of a vehicle.
    Additional Vehicle Specification
    The additional vehicle specification of the manufacturer.
    Pilot Run Identification
    The field shows the identification number of the pilot run from the manufacturer.
    Manufacturing Reference Number
    This field shows a unique reference number that identifies a particular assembly or another manufacturing process. Some Original Equipment Manufacturers (OEMs) use the Logical Sequence Reference, the Job Sequence Number, or the Vehicle Identification Number as an equivalent for the Manufacturing Reference Number.
    Model Identification
    The model identification number of the manufacturer.
    Item Group Identifier
    The item group identifier that is defined by the manufacturer.
    Systems Sequence Reference
    The field shows the reference number of the systems sequence from the manufacturer.
    Additional Call-Off
    The field shows the additional call-off number of the manufacturer.
    Change Sequence
    The double-digit change sequence number that is used by trading partner BMW / Rolls Royce. It indicates that the sequence of vehicles on the assembly line has been changed.
    Supply Group
    The supply group that is defined by the manufacturer.
    Item Family
    The item family that is defined by the manufacturer.
    Label Number
    The label number that is used for the release order item.
    Line Feed Location Side
    The feed side of the assembly line.
    Production Area Key
    The field shows the key of the production area from the manufacturer.
    Production Area Date/Time
    Items must be available at this date and time in the production area.
    Purpose Code
    Sequence schedules and sequential call-offs are sent with different purpose codes to the supplier. Purpose codes control how requirements and sequencing data of incoming sequence schedules and sequential call-offs are processed. As a prerequisite, a generic reference field must be available in the sequence schedules, which makes a requirement unique per item. The field mapping of a sequence schedule stores this generic reference field in the 1. Reference Number field of the sequence schedule's order line. The field mapping of the sequential call-off stores this generic reference field in the Sequence field.

    These purpose codes are supported:

    • Insert: Release Management checks whether another order line with the same generic reference number exists. If the generic reference number is unique per plan, then a new order line is added. If the generic reference number already exists, then the new requirement and sequencing data replace the existing data of the order line.
    • Update: The order line that must be updated is evaluated by comparing the generic reference numbers of the existing requirements and the new requirement. The reference numbers of the order line and the new requirement must be unique. If a matching order line is found, then the order line is updated with the available field information. If no matching order line is found, then the new requirement is added to the existing order lines.
    • Delete: The order line that must be deleted is evaluated by comparing the generic reference numbers of the existing requirements and the new requirement. The reference numbers of the order line and the new requirement must be unique. If a matching order line is found, then the order line is deleted. If no matching requirement is found, then the sequence schedule revision is stored as an unprocessed plan. If alerting is configured correctly, then an alert message is sent per email to the responsible user. The user is informed that the unprocessed plan must be deleted on the Unprocessed Plans page.
    • Deactivate: This purpose code is used to set a sequenced requirement with message subtype Sequenced With Shipping Window to Shipped. Individual requirements can be deactivated when a new schedule revision is created. The deactivation indicates that it is not necessary to ship the requirement to the customer. This is required, for example, in case of an item revision cutover. Multiple items are ordered for one vehicle whereby only one of the items must be shipped to the customer. In this case, it is up to the supplier to decide, which item must be shipped. When you select the purpose code and submit the single plan on the Shipment Schedule page, the shipped quantity is set to the requirement quantity. The net quantity is set to zero on the Shipment Schedule tab and the Combined Plan tab. The deactivated requirements are published in the SequenceSchedule BOD to the ERP system with net quantity zero to remove these requirements. If alerting is configured correctly, then an alert message is sent to ION Pulse. The responsible users are informed in Infor OS Portal or Infor Ming.le. In addition, a log entry is added to the Release Management server log.
    • Reactivate: This purpose code is used to create a new regular open requirement that can be shipped to the customer. If the purpose code Deactivate was set by mistake, then a new sequenced requirement must be specified. The requirement must be specified with requirement quantity, requirement date, and purpose code Reactivate. You must specify the vehicle identification number in the fields 1. Reference Number and Vehicle Identification Number. The sequence is identified by the job sequence number that must be specified in the Job Sequence Number field. The requirements with a matching vehicle identification number and job sequence number of the same plan are treated as if they were not shipped. The manually entered requirements are added to the combined plan as regular open requirements with purpose code Reactivate and published to the ERP system. If alerting is configured correctly, then an alert message is sent to ION Pulse so that the defined users are informed in Infor OS Portal or Infor Ming.le. In addition, a log entry is added to the Release Management server log.
    Sequence Data
    This check box indicates whether the order line's item and requirement data have been completed with sequencing data. The sequencing data determine the exact sequence and time of vehicles that are manufactured on the assembly line.