Order

This tab can be used in relation to pegged Requirements or requirements without an order reference, purchase request or an ordering offer for the selected entry in tab "Inflow and Outflow".

PATH: MRP > MRP Wizard > Select a scenario > click the Order recommendation button.

Field

Description

Supplier

Supplier, for which you want to create a purchase order,-quotation or -request

Delivery date

Determined from the

Field	Description
Delivery date customer order	Delivery date stored in the customer order, prognosis, or another requirement originator.
Average delivery time	Average delivery time in work days, defined in the Configuration Wizard.
Lead time according to item master	Lead time in working days according to the item master, given lead time for planning.
Calculated lead time	For an assembly (storage-related production): Using a backward scheduling simulation (routing of the assembly) the latest possible start date is calculated. Lot size is the requirement quantity. Order multiples are not taken into account here. For order related production: Using a backward scheduling simulation (routing of the assembly) the latest possible start date is calculated for the complete order related item structure. This corresponds to the start date of the sub-assembly which must be produced first. Lot size is the requirement quantity. Important: The order multiples, lot size, existing time reservations on resources are not taken into account during calculation. If calculation of the lead time was disabled, the item lead time is used as reference. The lead time is the sum of a single lead times of the order related sub-assemblies. Example 1: Lot size and setup time. Assembly A with operation sequence A1, 10 days setup time, lot size is 10. Company calendar: Every day is a working day. Customer order, delivery date 30.12. Pos 1 100 pieces: Calculated: 10 days, start 20.12. Pos 2 100 pieces: Calculated: 10 days, start 20.12. Pos 3 200 pieces: Calculated: 10 days, start 20.12. Example 2: Lot size and time for processing. Assembly A with operation sequence A1, time for processing 1 hr/piece, lot size is 10. Company calendar: Every day is a working day. Resource has 1x10 hrs/day. 100 pieces = 10 days Customer order, delivery date 30.12. Pos 1 100 pieces: Calculated: 10 days, start 20.12. Pos 2 100 pieces: Calculated: 10 days, start 20.12. Pos 3 200 pieces: Calculated: 20 days, start 10.12 Apparently, there is a problem, there is only one single resource, capacity limits and time reservations are not taken into consideration. This problem can only be avoided by the production orders being created as planned orders. Using APS, planned orders can be correctly scheduled and necessary resource times can be reserved.
Requirement date according to the forecast	The planned requirement date that is defined in the forecast. In a monthly forecast, it is the beginning of a month, in weekly forecasts, the Monday of the respective week. In case of an assembly, the required date of the sub-assembly is earlier.
Pre call time for prognoses	In the Configuration Wizard MRP > Calculation > Forecast > Pre call time for prognoses in calendar days.

Determining the date, depending on pegging

Field

Description

Customer order purchase part

Delivery date according to the customer order, average delivery time. Lead time according to the item master, period needed for replacement.

Customer order anonymous and order related production

Delivery date according to the customer order, average delivery time. Lead time according to the item master, period needed for replacement.

Forecast purchase part

Requirement date pre call time for prognoses, lead time according to the item master, period needed for replacement.

Production BOM position

If the BOM is assigned to a routing position, its Processing time – Start time is as follows:

•	With the Issue material with first operation setting the Processing time – Start time is the first reportable, active routing position.

•	With the Issue material later setting, the Processing time – Start time is the last reportable, active routing position.

•	If there is no reportable routing position, the delivery date is used as reference. If in the MRP wizard Consideration of link to routing was disabled, the start time of the work order position is used. If this was not set, the delivery date is used.

From the date computed this way, the first working day is determined according to factory calendar.

Then the Item – lead time is subtracted in calendar days, then the lead time – safety days as per configuration wizard is subtracted in work days.

If dealing with a purchase part, the Goods receipt – Idle time is also subtracted.

If the resulting date is in the past, the order recommendation date is the next work day starting from the current day.

See Order recommendation – Requirement.

and from the current selected row of the pegging.

Single / daily / weekly / monthly

Select "single" for single delivery, the order is created for one date.

For multiple delivery enter the date and quantities.

Beas suggests the delivery date and the necessary purchase dates, depending on the selected view

daily

weekly

2-week

and monthly

mrp_multidelivery

This view refers to the required date and, unlike the top list, not the "latest possible date of order."

Dates are proposed considering the factory calendar and the quantity is calculated with consideration of order multiples.

Result:

Even if a weekly order is selected according to the forecast, it is possible that other than a weekly request is presented. As the delivery date is suggested as the beginning of a time range, it takes account of the factory calendar. In the monthly view, this appears clearly.

Quantity

Quantity purchase UoM.

Note: Unit groups are not supported!

Price

Beas calculates the price if you change supplier, delivery date or quantity.

If you change the price manually, Beas overwrites the price when changing one of these fields.

Quantity

Quantity warehouse units.

Item

Item ID.

I-Version

I-Version number used from item master. If in pegging (sales order, production – BOM position) an I-Version was stored, it is used.

Designation

Item designation.

Drawing number

Drawing number from item master is used.

If a version number was stored, the Drawing number according to item version is used.

If in pegging a drawing number was stored, it is used.

Info

Free text.

Project

Link to project.

Warehouse

Current item warehouse.

Link

Order can be linked to a pegging.

Link is only possible to a pegging with same item number.

Note: Receipt reservations for purchase orders are currently not supported. Link serves only as information

Contract

You can see all entries

- if today is between Start/End date of the purchase blanket agreement

- if blanket agreement is approved and not closed or canceled

- if defined Item Version number is same as in current entry or item Version Number is empty in current entry or blanket agreement

if you choose a blanket agreement, the system inserts price, currency, item version (if defined) and supplier from blanket agreement.

Note:

This is designed for SAP B1 9.3 PL 3. If SAP inserts additional rules, it is currently not supported in the dropdown list.

Note: The Contract field always shows information related to the post-in date, that is the day of creating the Purchase order/

request, and NOT related to the Delivery date.

Gross price

Use price as Gross price

Allow to define the price as gross price.

Appears only if you have selected the check box "Enable Separate Net and Gross Price Mode" in Administration > System Initialization > Company Details > Basic Initialization tab.

Determine whether it is a gross price list or net price list.

•	Gross: All prices defined in the window are base prices and gross prices.

•	Net: All prices defined in the window are base prices and net prices.

Distribution rule

The distribution rule can be used as reference to a cost center. It is transferred to the purchase order.

Length, width height

Item properties.