Release Management

These code lists can only be used in an automotive environment.

JobCUMImporter

You can manually import shipped CUM data for active plans in Release Management. This code list is used to configure the CUM import. The import functionality reads a .csv file that contains shipped CUM data and plan fields. The plan fields are used to retrieve the current single plan. The shipped CUM data are used to update the single plan and to publish a new plan.

Ensure that the data of the import file corresponds with the current schedule situation of the imported plans.

Note: We recommend that you activate the test mode to check the CUM import for errors. When you activate the test mode, the CUM import does not change the plan data in Release Management.
  • Name: Defines the name of the CUM import configuration. The JobCUMImporter entry that has the name "parameter" is used as the default configuration. This entry can be used by customers to configure and test the CUM import.
  • Active: Activates the CUM import. By default, the CUM import is deactivated.
  • Field List: Specifies the list of fields for which CUM data and plan data are imported from the .csv import file. The fields must be separated by commas. The field names are case-sensitive. Example of a field list without LSP and without total shipped CUM: PlanAE,PlanLocation,CustomerID,ShipToID,ItemID,ShippedCurrent
  • Skip Errors: If activated, the import skips the plans that cause an error and updates the other correct plans. If deactivated, the import stops when an error is detected and the update of plans is canceled. By default, the check box is cleared.
  • Test Mode: If you select the check box, the plan data is not changed in Release Management. By default, the check box is cleared. We recommend that you activate the test mode and check the import for errors before the data is imported.

PhaseOutItemsActivation

You can implement this code list for items that are used in assigning release order requirements to contract lines based on the effective dates of the items and associated internal items. You must activate this new code list to enable the requirement date functionality at the accounting entity (company) level and location level. Select the Active check box to enable phase out item effective dates to be applied to all items at the accounting entity level.

PlanAdditionalContractSearch

This code list is for ship to locations that are used in Just-In-Time and other business processes. Different items are shipped to the same plant respectively ship to location in this scenario. Thus, Transformation cannot retrieve different ship to IDs from the incoming EDI messages. Different ship to IDs enable Release Management and Shipping to differentiate between Just-In-Time and other business processes. This is required, for example, to support the BMW JIT KANBAN process.

The code list PlanAdditionalContractSearch includes the additional ship to information. This information enables the Release Management area to retrieve the corresponding contract lines. To support different trading partners that are linked to different ship to IDs, Release Management uses this method to search for a matching contract:

  1. Release Management uses these search criteria to search for a contract: customer, ship to, customer item number, customer order number, and effective date.
  2. If a matching contract line cannot be determined, Release Management searches the code list PlanAdditionalContractSearch for an additional ship to ID. Release Management uses the ship to ID from the BOD that is published by Transformation.
  3. If the ship to ID is in the code list, the additional ship to ID is retrieved from it.
  4. Release Management uses these search criteria to search a second time for a matching contract: customer, additional ship to ID from the code list, customer item number, customer order number, and effective date.
  5. If a contract line cannot be identified, an unprocessed plan is created in the Release Management area. The unprocessed plan includes the additional ship to ID from the code list.

If more than two different logistic business processes for one ship to must be supported, the code list PlanAdditionalContractSearch can be enhanced:

  • Name: Defines the ship to ID used to evaluate a contract line based on the incoming EDI messages.
  • Accounting Entity: Specifies the accounting entity for which the additional ship to ID is used. If left empty, the additional ship to is valid for all accounting entities in the tenant to which you are logged on to.
  • Short Description: Specifies a short description of the additional ship to and the business process for which it is used. The short description can consist of a maximum of 512 characters.
  • Description: Specifies a description of the additional ship to.
  • Effective from Date: Specifies the start date of the additional ship to.
  • Effective to Date: Specifies the end date of the additional ship to.
  • Additional Ship To: Specifies the additional ship to that is used for the special business process.

PlanCUMHandlerTestMode

You can use this code list to activate a test mode of the Release Management area. In test mode, CUMs are balanced before you go live with the new system. You can import release orders in the new system and work in parallel with the legacy system. It is not required to import shipments from the ERP system (shipped CUM = received CUM). You can define the test mode on accounting entity level.

By default, the test mode is deactivated.

PlanFilterCustomerItems

The Name field defines a customer item number that is filtered by the plan import. Used for importing PlanningSchedules, ShipmentSchedules, and SequenceSchedules that are filtered by customer items. You can specify up to three combinations of customer and accounting entity for one customer item number.

SequenceAcceptImpulseWithoutForecast

Standard behavior of Release Management is to stop a Sequential Impulse message without a corresponding Sequential Forecast message. These schedules are shown as unprocessed plans with the exception status Failed on the Unprocessed Plans page.

To process a Sequential Impulse message without a corresponding Sequential Forecast message, this code list has been introduced.

By default, the parameter is deactivated. The Sequential Impulse message is shown as unprocessed plan with the exception status Failed on the Unprocessed Plans page. If the parameter is activated, the Sequential Impulse message is processed without errors.

SequenceNetChange

A Sequential Impulse message normally contains information about one vehicle. When Release Management publishes the SequenceSchedule BOD, all sequenced requirements are published independent of whether they are changed or not. To reduce the number of lines in the SequenceSchedule BOD to be published, Release Management can be configured in a way that only changed requirements are published.

You can use this code list to specify customers, for which the net changes are published.

During plan adjustment, the field Purpose Code is set on requirement level. Supported values are Insert, Update, and Delete. If the Net Change functionality is activated, the Purpose Code is published for requirements of type "Sequential Impulse" per reference RequirementPurposeCode.

In addition, the entire SequenceSchedule is marked as being a NetChange schedule.

If the Net Change functionality is not activated, all requirements are published.

SequenceNewPlanRevisionImportingShipment

After importing shipments or inventory consumption that have an effect on the shipped CUM, the combined plan and a referenced single plan are updated. The requirements are reduced by the shipped quantity and a new plan revision is created. To reduce the data to be processed in sequencing processes, deactivate the creation of new plan revisions after importing shipments with this code list.

By default, the parameter is activated.

SequencePartlySequencedAutomaticProcessing

If this code entry is activated, partially sequenced plans are automatically re-validated and sequential call-offs are processed.

SequencePartlySequencedWaitTime

You can specify a delay, to avoid the revalidation of partially sequenced pending plans on the Unprocessed Plans page in Release Management when these plans are processed. The default value is 10 minutes delay.

SequencePlanningScheduleFastProcess

Release Management publishes all BODs according to the BOD separation rule after importing a new schedule. If you import a PlanningSchedule, you do not require to publish a SequenceSchedule.

This code list has been introduced to suppress the publishing of a SequenceSchedule after importing a PlanningSchedule for a customer and accounting entity.

By default, the parameter is deactivated. The SequenceSchedule is published. If the parameter is activated, the publishing of a SequenceSchedule is suppressed when a PlanningSchedule is imported.

SequencePublishPlanningSchedule

Release Management publishes all BODs according to the BOD separation rule after importing a new schedule. If you import a SequenceSchedule, you do not require to publish a PlanningSchedule.

This code list has been introduced to suppress the publishing of a PlanningSchedule after importing a SequenceSchedule.

By default, the parameter is deactivated. The PlanningSchedule is published. If the parameter is activated, the publishing of a PlanningSchedule is suppressed when a SequenceSchedule is imported.

ShipmentIgnoreDuplicateReference1Keys

If this code list is activated, Release Management checks the referenced requirements from the combined plan. If the 1. Reference Number of an incoming shipment has already been used as key for a shipped requirement, the requirement is filtered out.

ShipmentPublishPlanAfterImport

You can use this code list to publish plans after importing the shipments. For inventory consumption, the publishing is only active if the Update Shipped Quantity by Inventory Consumption check box in the CUM Adjustment Rules is selected. You should only configure this code list if no shipments are imported for an LSP process.

  • Active: Activates the publishing of plans. The publishing is activated by default.
  • Publish Pick-Up Sheets: If you select this check box, a new plan revision is published after importing pick-up sheet shipments from the ERP system.