Creating order lines

You create order lines for a single plan in the detail view of the Manage Planning Schedules or Manage Shipment Schedules pages.

You can use two methods to create order lines for the single plan:

  • Specify the field information of an order line in the New Planning Schedule Requirement or New Shipment Schedule Requirement dialog boxes. To use this method, perform the steps 1–6.
  • Use the fast entry facility. To use this method, perform the steps 7–8.

To create an order line:

  1. On the Planning Schedule or Shipment Schedule tab, click Create.
    The New Planning Schedule Requirement or New Shipment Schedule Requirement dialog box opens.
  2. Specify this information:
    Arrival Date
    Specify the date at which the ordered goods must be available at the customer's location. Select a date from the calendar. You can specify the required time of the release order in a separate field here. Select a time from the drop-down list. When you manually specify requirements, consider the difference between your local user time zone and the customers time zone.
    See Time zone support.
    Requirement Quantity
    Specify the requirement quantity of the release order.
    Frequency

    Select the frequency of the requirement from the drop-down list. 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.
    Level of Commitment

    Select the level of commitment of the order line from the drop-down list. 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.
    Type of Requirement

    Select the requirement type of the order line from the drop-down list. The requirement type 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: This is the default setting for scheduled requirements that have a specified requirement date.
    • Backorder: Backorder requirement that is scheduled on the current date. The commitment level of a backorder requirement is Firmed, that is, a firm requirement.
    • Immediate Requirement: Immediate requirement that is scheduled on the current date. The commitment level 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 commitment level 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.

    1. Reference Number
    Specify the first document reference number, for example, a PUS number or a RAN number. This field entry is only relevant for referenced schedules. The first document reference number of a release order is specified for referenced shipment schedules that have an appropriate message subtype. The first document reference number must be defined as key field in the CUM adjustment rule.
    2. Reference Number
    Specify the second document reference number, for example, a PUS number or a RAN number. This field entry is only relevant for referenced schedules. The second document reference number of a release order is specified for referenced shipment schedules that have an appropriate message subtype. The second document reference number must be defined as key field in the CUM adjustment rule.
    3. Reference Number
    Specify the third document reference number, for example, a PUS number or a RAN number. This field entry is only relevant for referenced schedules. The third document reference number of a release order is specified for referenced shipment schedules that have an appropriate message subtype. The third document reference number must be defined as key field in the CUM adjustment rule.
    Expected Delivery Date
    Select the expected delivery date and time from the drop-down lists. The field is used for trading partner A0230 Renault Europe.
    Dock Code
    Specify the dock code of the release order. The dock code defines the receiving location of a customer or the shipping location of an organization, for example, a gate number for trucks.
    Routing Code
    Specify the routing code of the release order. The routing code defines the route for the transportation of goods. For example, the trading partner PSA sends the routing code in a DELJIT message on requirement level. In the Alternative Logistics process of the trading partner, the routing code is unique per transport handling unit.
    Consumption Point
    Specify the consumption point of the release order. From the drop zone, an item may be distributed on multiple consumption points.
    Customer Storage Location
    Specify the customer's 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
    Specify the delivery point from which the delivery is distributed to the consumption points. This field is used by French trading partners.
    Transport ID
    Specify the 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
    Specify the Release Authorization Number (RAN). The RAN number that is assigned by the customer uniquely identifies a firm requirement. 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
    Specify the project number of the release order.
    Dispatch Call-off Number (VAB)
    Specify the dispatch call-off number of the release order. The dispatch call-off is the binding schedule and 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
    Specify the model year in which the release order 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
    Specify the number of the binding delivery instruction. Suppliers and forwarders must fulfill these customer's requirements for the manufacturing, transportation, and delivery of goods.
    Delivery Instruction Revision
    Specify the revision level of the valid delivery specification.
  3. If you create an order line for a shipment schedule that has the message subtype Sequenced or Sequenced with Shipping Window, then specify additional sequencing information as required:
    Line Feed Location
    Specify the line feed location. The line feed location is a customer defined delivery location that is transferred by release orders of 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
    Specify the Vehicle Identification Number (VIN). The VIN consists of a structured combination of characters that are 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
    Specify 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 finalized and a sequential call-off message is processed, this field 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
    Specify 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
    Specify the additional vehicle specification of the manufacturer.
    Pilot Run Identification
    Specify the pilot run identification number of the manufacturer.
    Manufacturing Reference Number
    Specify the Manufacturing Reference Number. The Manufacturing Reference Number is a unique 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
    Specify the model identification number of the manufacturer.
    Item Group Identifier
    Specify the item group identification number of the manufacturer.
    Systems Sequence Reference
    Specify the manufacturer's number of the systems sequence reference.
    Additional Call-Off
    Specify an additional call-off number of the customer.
    Change Sequence
    Specify the change sequence number of the manufacturer. The trading partner BMW / Rolls Royce uses a double-digit change sequence number. The number indicates that the sequence of vehicles on the assembly line has been changed.
    Supply Group
    Specify the supply group of the release order item.
    Item Family
    Specify the item family of the release order item.
    Label Number
    Specify the label number that is used for the release order item.
    Line Feed Location Side
    Specify the feed side of the assembly line.
    Production Area Key
    Specify the production area key.
    Production Area Date/Time
    Specify the production area date and time.
    Purpose Code

    Select the Purpose Code that is used for the sequence schedule from the drop-down list. 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 Manage 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 Manage 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 requirement. If alerting is configured correctly, then an alert message is sent to ION Pulse. The responsible users are informed in 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. Specify the requirement quantity, requirement date, and the 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 combined plan as regular open requirements. They are published with purpose code Reactivate to the ERP system. If alerting is configured correctly, then an alert message is sent to ION Pulse. The responsible users are informed in Infor Ming.le. In addition, a log entry is added to the Release Management server log.
    Sequence Data
    Select this check box to mark the sequence schedule as completed by the required sequencing data. The sequencing data determine the exact sequence and time of vehicles that are manufactured on the assembly line.
  4. To save the order line, click OK.
    The new order line is displayed at the bottom of the Planning Schedule or Shipment Schedule tab. The line number of the order line is automatically created by requirement date. The order lines are sorted by requirement date.
  5. To add the next order lines, repeat the steps 1–4.
  6. To delete an order line, select the order line and click Delete.
  7. Click New Requirement Fast Entry, to use the fast entry facility.
    A new order line is created.
  8. Click the Drill down button of the new order line and specify the required information.
    The fields are described in the previous steps.