Reviewing the detail settings of a manual approval rule

Effective from Date

This field defines the start date of the valid period for the configuration.

When editing, click the Calendar button to select the start date from a calendar.

Effective to Date

This field defines the end date of the valid period for the configuration.

When editing, click the Calendar button to select the end date from a calendar.

Message Type

The message type is a Shipment Schedule or a Planning Schedule.

Message Subtype

These options are available for the message subtype:

• Default: This is the default configuration that is used for the replacement or combination of requirements in the combined plan.
• RAN: This configuration is used for the replacement or combination of requirements from RAN messages of a customer.
• GPI: This message subtype is used for the message type Shipment Schedule in the Renault process GPI. GPI is an integrated production control system that is used by Renault assembly plants. In the GPI process, suppliers receive release orders with a unique transport ID on requirement line level and a consumption point on plan level. Shipments are grouped by transport ID.
• L3P: This message subtype is used for the message type Shipment Schedule in the Renault process L3P. In the L3P process, suppliers receive release orders with a transport ID, a consumption point, and a distribution zone on requirement line level. Shipments are structured by distribution zone, transport ID, and consumption point. Each shipper has a unique transport ID. Consequently, shipments are grouped by transport ID, if more than one shipment is contained in a shipper.
• CINDI: This message subtype is used for the message type Shipment Schedule in the Renault process CINDI. The CINDI process works with GPI or L3P. In this process, suppliers receive a shipment schedule with RAN or Kanban number. The expected arrival date is included in the message in addition to the fields that are known from GPI and L3P. The RAN or Kanban number is unique for release orders on requirement line level. The transport ID is unique per shipper. Multiple shipments per shipper/transport ID are possible. Multiple RAN or Kanban numbers per shipment and per item in a shipment are possible. The message subtype CINDI is used for the LISA process as well.
• Pick-up Sheet: This configuration is used for the replacement or combination of requirements from Pick-up Sheet messages of a customer.
• Manifest: This configuration is used for the replacement or combination of requirements from Manifest messages of a customer.
• Kanban: This configuration is used for the replacement or combination of requirements from Kanban messages of a customer.
• Sequenced: This message subtype is selected for the message type Shipment Schedule. The message subtype is used to process shipment schedules that require sequential information, for example, production-synchronous release orders. If you use the message subtype Sequenced, the Calculation Base in the CUM adjustment rules configuration must be Referenced. The Reference Number 1 is Key check box must be selected.
• Sequenced with Shipping Window: This message subtype is selected for the message type Shipment Schedule. If Release Management receives a ShipmentSchedule BOD, the Message Processing Rules page is checked for a sequenced call-off with message subtype Sequenced with Shipping Window. This message subtype is also expected from the customer. In this case, the ShipmentSchedule BOD is merged with the current single plan of type Shipment Schedule into a new single plan. The new single plan contains the sequenced requirements. This feature is especially used by trading partner A0061 Ford North America.
• Loading Sequence: This message subtype is selected for the message type Shipment Schedule and is used for Honda when lot sequence information is sent. In this case, the reference field consists of the Schedule Order Number and the Lot Sequence to load the truck as requested by Honda.

Remark

Review or provide a short description that clarifies the purpose of the configuration.

Customer

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.

When editing, click the Lookup button of the field. Select the customer from the list that is displayed in the dialog box.

Customer Name

The field shows the name of the customer who holds the contract.

When you select a customer, the name of the customer is automatically displayed.

Ship To

Review or specify the ship to location of the contract line. This field indicates the location code that is used with the ship to location to identify where the goods are shipped.

When editing, click the Lookup button of the field. Select the ship to location of the customer from the list that is displayed in the dialog box. The ship to locations that are displayed are valid for the selected customer.

Ship To Name

View the name of the location that is used with the Ship To location identifier to identify where goods are shipped to.

Internal Item

Review or specify the internal item number of the contract line that is used by the supplier and identifies the item.

When editing, click the Lookup button of the field. Select the item that is used by the supplier from the list that is displayed in the dialog box. The items that are displayed are valid for the selected customer and ship to.

Item Description

The field shows the internal item description.

Accounting Entity

The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations.

Always Require Manual Approval

If this check box is selected, the requirements of release orders that are filtered out must be approved manually on the Unprocessed Plans page. For example, use this option in the test phase with a new trading partner.

Manual Approval Required for First-Time Schedule

The first requirement of a release order for a contract line without existing plan must be approved manually on the Unprocessed Plans page.

Manual Approval Required for No Demand

If this check box is selected, the release orders without requirements must be approved manually on the Unprocessed Plans page. Release orders without requirements indicate that the associated contract currently must not be supplied. A check of the trading partner's requirement situation is recommended.

Manual Approval Required for Immediate Requirement

If this check box is selected, the immediate requirements of release orders that are filtered out must be approved manually on the Unprocessed Plans page. A check of the trading partner's requirement situation is recommended.

Manual Approval Required on Backorder Requirement

If this check box is selected, the backorder requirements of release orders that are filtered must be approved manually on the Unprocessed Plans page. A check of the trading partner's requirement situation is recommended.

Manual Approval Required on Difference

If this check box is selected, differences between the requirements of the current and the previous release order must be approved manually. The release orders must have the same message type. In addition, a start date comparison condition must be selected from the Release Comparison Start Date drop-down field. The release orders are compared according to the settings in the Release Comparison Lines table. A check of the trading partner's requirement situation is recommended.

Check Customer Alert

If this check box is selected, Release Management checks whether the incoming release order includes an alert message for the supplier. For example, in case of trading partner Renault an incoming release order includes the message "ALERTE". If alerting is configured correctly, an alert message is sent per email to the responsible user. The user is informed about the incoming release order.

Block Processing on Customer Alert

If this check box is selected, Release Management checks whether the incoming release order includes an alert message for the supplier. For example, in case of trading partner Renault an incoming release order includes the message "ALERTE". The release order is blocked and must be approved manually on the Unprocessed Plans page. If alerting is configured correctly, an alert message that informs about the blocked release order is sent per email to the responsible user.

Release Comparison Start Date

This field provides the condition for which to compare release orders. These are the options:

• Use Date of First Requirement - The comparison starts at the first demands demand date.
• Use Processing Date - The comparison starts on the day the new plan is processed.
• Use Release Date - The comparison starts on the plan's release date as defined in the delivery instructions of the BOD. If there are no delivery instructions, the Date of First Requirement option is employed.

The release comparison check is activated, if the Manual Approval Required on Difference check box in the Approval Settings field set is selected. The lines of the Release Comparison Lines table define how the requirements of the current release order are compared with the previous release order. For example, the current planning schedule is compared with the previous planning schedule. If deviations occur by comparison, the filtered out planning schedule must be checked on the Unprocessed Plans page.

Line

This field indicates the line number for specified requirement tolerance limits on the release order.

Description

This field provides a description for the line.

Note: For example, for an initial time period in which the requirement quantity must remain unchanged (in other words, tolerance values are defined as zero), then a description such as "Frozen" would be appropriate. As another example, a description of "Raw Material Release" or a more generic description of "Additional Period" would be applicable for a number of days in which a specified range of quantity tolerance (in percent and quantity) is allowed.

Comparison Mode

The field defines how the requirements of the current release order are compared with the previous release order of the same message type:

• Day: The requirements of a day are summed up. Daily requirements of the current and the previous release order are compared. This method allows an immediate reaction of the requirement manager, because the comparison is exact for an extreme short period. For example, if the requirement of a release order is delayed for one day, the release order is filtered out. It must be checked on the Unprocessed Plans page.
• Week: The requirements of a week are summed up. Weekly requirements of the current and the previous release order are compared. This method allows a reaction of the requirement manager in a relatively short period. For example, if the requirement of a release order is delayed for one week, the release order is filtered out. It must be checked on the Unprocessed Plans page. A delayed requirement of one day has no consequences unless the requirement is scheduled in another week.
• Summarized for Selected Time Range: The sum of requirements of the current and the previous release order are compared for a selected time period in days.

Time Period Days

The field defines the time period in days that is considered to compare the requirements of the current and the previous release order. Frequently, a short period is even selected if requirements that are scheduled far later are changing often. A short period can be considered, if these requirements do not lead to problems in the manufacturing of goods.

(%) Tolerance Limit Increase

The field defines the tolerance limit in percent that the current release order may exceed the requirement quantity of the previous release order. If the requirement quantity exceeds this limit, the current release order is posted to the Unprocessed Plans page. In most cases requirement quantities are summarized over a short period and then compared. The calculated differences must not exceed the specified tolerance limit in percent. The advantage is that you realize massive changes of release order quantities in the short-term.

(%) Tolerance Limit Decrease

The field defines the tolerance limit in percent that the current release order may fall below the requirement quantity of the previous release order. If the requirement quantity falls below this limit, the current release order is posted to the Unprocessed Plans page.

(Qty) Tolerance Limit Increase

The field defines the total tolerance limit in number of items. The current release order may exceed the requirement quantity of the previous release order up to this limit. If the requirement quantity exceeds this limit, the current release order is posted to the Unprocessed Plans page.

(Qty) Tolerance Limit Decrease

The field defines the total tolerance limit in number of items. The current release order may fall below the requirement quantity of the previous release order down to this limit. If the requirement quantity falls below this limit, the current release order is posted to the Unprocessed Plans page.

Switch Off Alert

This setting is selected if you wish to disable the alert for the comparison requirement conditions defined on this line for the release order.

The Minimum Order Quantity (MOQ) value for an item is set in the ERP system, for example LN. The MOQ value is published in the Contract BOD to Release Management. You can review the MOQ value of a contract line for an item on the Contracts page. Based on the rules defined in the MOQ Settings field set, the requirement quantity of release orders is checked. It is detected whether the requirement quantity falls below, meets, or exceeds the specified MOQ.

MOQ Alert

An alert is issued during the processing of an incoming release order, if the requirement quantity is lower than the MOQ value. The user receives the message SRM-1011:

Alert for new plan below MOQ value

MOQ Block on Alert

When the MOQ Alert check box is selected, you can also select the MOQ Block on Alert check box. An incoming release order is blocked in the event the requirement quantity is lower than the MOQ. An alert is issued and the user receives the message SRM-1012:

Approval required for new plan below MOQ value

An unprocessed plan is created on the Unprocessed Plans page. The unprocessed plan must be approved manually.

Level of Commitment

This field determines which requirements of release orders must be validated against the MOQ. These options are available:

• Firmed: Firmed requirements (these items must be produced and shipped) of a release order must be validated against the MOQ.
• Planned: Planned requirements of a release order must be considered in the MOQ validation.

Note: You can select both options.

Evaluation Window (Days)

This field defines the period of days, during which the requirements of release orders are considered in the MOQ validation. The period starts with the requirement date of the first order line of an incoming single plan, shipment schedule or planning schedule.

For example, the evaluation window is defined as 30 days and the first order line's requirement date is June 1. The evaluation window in this case would be June 1 + 29 more days to equal June 30. Therefore, any date before July 1 falls in the MOQ evaluation time window.

With each new release order, a new start date is set for the evaluation window.

If no value is entered for this field, each release order is checked against the MOQ value, regardless of date.

Frequency

The field defines how often the MOQ validation process occurs. These options are available:

• Daily
• Weekly
• Monthly

Note: You can select all options.