Subcontract Orders

• Order site (field POHFCY)

Code of the site issuing the order (request for quote, purchase request, order, subcontract order etc.).
This field is mandatory. It is initialized by default by the purchase site associated with your function profile.
You can modify this code by selecting a code from the list of authorized sites.

There is no requirement for the order site to be a storage site. When it is a storage site, it loads, by default, the receiving site of the ordered subcontracted products as well as the storage site of the materials to be shipped to the subcontractor.

• Subcontract order (field SCONUM)

The subcontract order reference enables the latter to be identified in a unique manner.
Entering this reference is optional: it can be generated automatically upon each creation or copy of subcontract orders, depending on the setup assigned to the counter associated with the document type:  Sub-contract order.

• Description (field SCODES)

Description of the subcontract order.

• Product (field ITMREF)

On creation it is mandatory to enter a product reference. The category of the product must be: subcontracted, managed in stock and active.

• Supplier (field BPRNUM)

This field is mandatory. Choosing a supplier determines whether it is an inter-site/inter-company subcontract order.

The supplier is initialized as follows:

• When the version of the supplier is not managed:
  The supplier is initialized with the default supplier defined in the Products-Sites record. If there is no supplier listed in the Products–Sites record, the default supplier listed in the Products-Suppliers record will be used, except if the ITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group) specifies that the product-supplier must be listed at site level. In that case, you must define it at Products-Sites level.

• When the product version is managed, only one subcontract BOM code is activated and associated with the major version of the product. Consequently, it is possible to only select those suppliers of the product having the same subcontract BOM code (mentioned in the Products-Suppliers record).

• For those Products-Suppliers records mentioning this code:
  The default supplier, that has priority and is not blocked, and that is mentioned in the Products-Sites-Suppliers record, is the one that is considered. Otherwise, the supplier, that has priority and is not blocked, and that is associated with the BOM code in the Products-Suppliers record, is the one that is considered.
• If no subcontract BOM code is entered on any Products-Suppliers record, the supplier is not initialized.

When entering or modifying a supplier, several controls are performed and various messages can be displayed, according to the situations:

• The supplier is declared to be in dispute. This can be a blocking message or a simple warning according to the value given to the dispute code in the supplier record.
• The product is not listed by this supplier. This can be a blocking message or a simple warning according to the value of the ITMBPS - Supplier referencing (ACH chapter, REF group) parameter.
• The product is not listed by this supplier for this receiving site.This can be a blocking message or a simple warning according to the value of the ITMBPSFCY - Supplier site referencing (ACH chapter, REF group) parameter..

• Intersite (field BETFCY)

This indicator, which cannot be entered, is automatically activated to point out that the order corresponds to an inter-site subcontracting operation ("Inter-sites" is checked for the defined supplier, who is linked to a site in the BP record).

• Intercompany (field BETCPY)

This indicator, which cannot be entered, is automatically activated to point out that the order corresponds to a subcontracting operation between different legal companies belonging to the same group.

• BOM code (field BOMALT)

Several BOMs can be defined for a single product reference. They are identified by the use of the code, entered using two digits.
The BOM codes can be used to manage different structures of subcontracted products.
In this screen, only one subcontract BOM can be used; it is not mandatory.
If a default BOM code has been entered for the specified product and supplier, it is automatically suggested when accessing the field in entry mode.
After selecting the BOM code, the subcontract order is automatically populated with:

• The receiving site associated with the code if it is specified; a consistency check is performed to make sure it belongs to the same company as the purchase site;
• The material list and subcontract BOM service.

If the product-site is not listed by the supplier, a blocking or warning message can be displayed based on the value of the ITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group).

• Major version (field ECCVALMAJ)

Use this field to indicate which major version of this product applies. Major versions might be used where there have been increased or significant changes to the original or previous version, that is the 'form, fit or function' has changed.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the product code defined in the Product field is not version managed.

• Minor version (field ECCVALMIN)

Use this field to indicate which minor version of this product applies. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

Type in, or select a version code from the list of version codes displayed. This field is not available for entry if the product code defined in the Product field is not version managed.

• Status (field SCOSTA)

This field is used to specify the status of the subcontract order:

• Planned: no action (Allocation, Order) can be carried out from this order
• Firm: allocations and orders relating to this order are possible.

• field CLODAT

This field indicates the date on which the closing has been performed.
This field can only be viewed when the status of the subcontract order is "Closed".

• Start date (field ORDDAT)

The start date of the subcontract order is initialized with the current date and cannot be modified.
It is based on the receipt date and calculated with respect to the subcontract lead time of the released product.
It can be adjusted when the planned receipt date of the purchase order linked to the subcontract order is modified: a message is displayed suggesting that you adjust the subcontract order start date. If you answer 'Yes', the start date is updated based on the order date. In the case of several purchase orders associated with the subcontract order, this message is not displayed: The start date cannot be updated based on the orders.
This field is managed depending on the setup of the entry transaction of the subcontract order.

• Receipt date (field RETDAT)

It is mandatory to enter the receipt date.
This date corresponds to the requirement date of the released product and automatically loads the start date of the subcontract order as well as the end date of the subcontract service.
In the case of multiple partial orders linked to the subcontract order, the latest receipt date is systematically considered to load the end date. If the partial order whose receipt date was used to load the end date is deleted, the end date still applies.

• Lead time (field LTI)

This is the service lead time of the released product, expressed in number of calendar days.
This lead time is loaded, in order of priority, as follows:

• the lead time on the subcontract fee of the service associated to the supplier
• the service subcontract lead time in the selected subcontract BOM
• the subcontract lead time specified in the Product-supplier record of the Service
• - the purchase lead-time specified in the Product-site record of the Service
• the reorder lead time specified in the Product record of the Service.

If no lead time is associated to the service, the lead time of the subcontracted product is used, in the following priority order:

• the subcontract lead time specified in the Product-supplier record
• - the purchase lead time specified in the Product - Site record
• the reorder lead time specified in the Product record.

This field is managed depending on the setup of the entry transaction of the subcontract order.

• Subcontractor site (field MFGFCY)

This field is managed depending on the setup of the entry transaction of the subcontract order.
This field is entered only in the event of an inter-site/inter-company operation.

• Inter-site: the field takes the value of the site defined at the BP or supplier record.
• Inter-company: the value of this field depends on the default delivery address of the purchase site customer.

• If the receipt site defined for the delivery address belongs to the same company as the purchase site, the subcontract site takes the value of the shipping site if it belongs to the same company as the supplier site. The subcontract receipt site is the receipt site defined for the delivery address.
• If the receipt site defined for the delivery address does not belong to the same company as the purchase site, the subcontract site corresponds to the supplier site if it is a storage site.

• Subcontract address (field BPAADD)

This field corresponds, in order of priority, to:

• the default ship-to customer address of the subcontract site in the event of an inter-site/inter-company operation. If the receiving site of this delivery address is also the receiving site of the subcontract order, this address is not suggested: in this case, it is the first active delivery address in alphabetical order that is suggested.
• Otherwise, the field corresponds to the default address of the ship-to customer or of the client associated to the supplier. If the address is not active, the system suggests the first active delivery address in alphabetical order.

In case of modification of the subcontract address, a message suggests to modify the site and location of the components involved too. If the answer is ‘Yes’, the storage site and location for which the allocation of the components to be supplied to the supplier is to be performed are also modified.
A consistency check is performed to make sure the receiving site and order site belong to the same company.

• Receiving site (field PRHFCY)

This field is managed based on the setup of the entry transaction of the subcontract order.

It displays the site where the goods must be delivered by the supplier. This site is initialized, in order of priority by:

• the order site if it is also a storage site,
• the user storage site if it belongs to the same company as the purchase site.
• the first storage site in alphabetical order of the company to which the order site belongs.

In an inter-site/inter-company context, the receiving site is initialized as follows:

• by the receiving site of the default delivery address of the purchase site customer,
• by the site associated to the chosen BOM code. If the site belongs to the same company as the purchase site, it will be used as a priority.

This receipt site must belong to the same legal company as the order site.

In case of modification of the receiving site, a message suggests to modify the site and location of the components concerned. If the answer is ‘Yes’, the receiving site specified in the service line, as well as the storage site and location for which the allocation of the components to be supplied to the supplier is to be performed are also modified.

When choosing the receiving site, a message can be displayed if the (receiving) product-site is not referenced by the supplier. This message can be blocking or a simple warning according to the choice made at the level of the ITMBPSFCY - Supplier-site referencing (ACH chapter, REF group) general parameter.

• Receipt address (field PRHADD)

Address code of the receipt site.

• field PRHADDDES

Non-enterable field displaying the code of the receipt address.

• Project (field PJT)

This field is used to specify the reference of the project to which the subcontract order is allocated.
This field is managed depending on the setup of the entry transaction of the subcontract order. The management of this code also depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter - MIS group).

• When the value is No, it may be a code selected freely.
• When its value is Yes, an existence check is systematically applies to the entered project code.
  You can use the Selection icon to display the list of available project codes.

If you do not enter a project code but the conditions are met for the automatic opening of the requirements window, then this window will display all the requirements that match the entered criteria. The requirements can relate to various project codes. If you click Include all, the project code of the first line is used to load the released product project code: only the lines having the same project code as the first line are selected.

If you enter a project code, the requirements window only displays the requirements related to this project code and that match the specified criteria.

When generating an order, the project code used on the released product will be used on the order header and on all the lines generated on the purchase order.

In creation and modification mode, modifying the Project code triggers the display of the message 'Update dimension types?'.

• If you answer Yes, analytical dimensions are updated on the released product, the service product and on materials, with respect to the default dimensions setup.
• If you answer No, only the analytical dimension of the dimension type used for project management tracking is updated. This update applies to the released product, service product and to the materials.

• Purchase unit (field PUU)

This is the purchase unit defined for the product-supplier pair or for the products that do not exist in the Product-supplier record.
The product has two purchase units:

• purchase unit defined at the level of the unit product record,
• purchase unit linked to the supplier.

• PUR quantity (field QTYPUU)

This mandatory field is used to specify the quantity in purchase unit.

When entering a subcontract order and depending on the entry transaction used, a window can automatically open to suggest taking into account the requirements. A date can be entered to limit the suggestions in time. This date will be applied by default to the requirement end date, but it can be applied to the requirement start date according to the Requirement selection section.
Click Criteria to specify sorting criteria and additional selection criteria, including the entry of ranges related to the project code, document or original document.
Click Include all to automatically preload the quantity taken into account on each line.
Click Exclude all to reset the selected quantity to zero. If there is a minimum quantity in the product-supplier record for the considered product, this quantity is suggested for the selected quantity, even if it is greater than the requirement quantity. A blocking message prohibits the entry of a quantity inferior to this minimum quantity.

If you do not want to take into account the requirements, exit this window to return to the line entry.

• PUR-STK conversion (field PUUSTUCOE)

Conversion factor used to calculate the quantity in stock units from a quantity entered in purchase units: Quantity in STK = Qty in PUR * conversion factor.

This conversion factor can be accessed if the Purchase unit field (PUU) has been entered, and has a value different from the stock unit. It can be initialized using the conversion factor table if the combination exists.

• Stock unit (field STU)

This field indicates the product management unit in which are expressed:

• The stock
• The standard price
• The BOM link quantity, etc.

This information is always displayed, regardless of the transaction used. It cannot be modified.

• STK quantity (field EXTQTY)

This field contains the quantity of the released product, expressed in stock unit.

• Priority (field PIO)

This field is used to assign a priority level to the released product. It only serves an information purpose.

This field is managed depending on the setup of the entry transaction of the subcontract order.

• Released product (field ITMSTA)

This non modifiable field shows the product status: Pending, In progress, Ordered, Received or Closed.
The detailed situation is displayed in a window that can be accessed via the menu Option/Released product situation.

• Allocation (field ALLSTA)

This non modifiable field shows the product situation with respect to the allocation: Partial, Complete, Partial/Shortage, Complete/Shortage, Not allocated.

• Released product tracking (field SCITRKFLG)

This non-modifiable field states the current phase of the product: Pending, Under study, Printed, In progress, Closed, Calculated cost price.

• Dimension type (field DIE)

This field is used to enter or select any dimension view set up in the database.

This grid is used to enter or display the analytical dimension types based on the setup of the entry transaction of the subcontract order.

• Dimension (field CCE)

These are the analytical dimensions initialized according to the setup of the default dimensions (SCI dimension code). These dimension codes can be modified manually if it is authorized by the transaction.

If you modify the dimension on a dimension type, a message is displayed, asking you to update the dimension types of the service and materials. If you answer ‘Yes’ to this message, the analytical dimensions of the service and materials will be reinitialized according to the setup of the dimensions entered for the released product.

These are the analytical dimensions initialized based on the setup of default dimensions (SCI dimension code). These dimension codes can be modified manually if authorized by the transaction.

In creation and modification mode, analytical dimensions are re-initialized with respect to the setup of default dimensions if, when modifying the project code, you answer Yesto the message: 'Update dimension types?'

• Subcontracted prod. (field SRVITMREF)

Service reference required for the manufacturing of the product.
In creation, this reference is initialized with the reference of the first corresponding service in terms of validity (among those recorded in the BOM). Depending on the value of parameter DEFEORTYP - Default EO management mode (chapter ACH, group EOM), this reference can be replaced by any other service corresponding to a product associated with the Service category. This product must be Received.

Click the Selection icon to display the list of services related to the subcontract bill of materials.

Inter-company specificities:

On an inter-site or inter-company subcontract order, you can only enter products of the Received / Deliverable type.

• Receiving site (field PRHFCY)

This non-modifiable field displays the receipt site of the released product:

• Start date (field OPESTR)

By default, the start date of the subcontract service is determined as follows:
End date - Lead time.
Its modification leads to the update of the end date. If the calculated end date is later than the receipt date of the released product, the latter is modified.
It can be adjusted when the planned receipt date of the purchase order linked to the subcontract order is modified: a message is displayed suggesting that you adjust the subcontract order start date. If you answer 'Yes', the start date is updated based on the order date. In the case of several purchase orders associated with the subcontract order, this message is not displayed: The start date cannot be updated based on the orders.

This field is managed depending on the setup of the entry transaction of the subcontract order.

• End date (field OPEEND)

The end date of the subcontract service is automatically loaded with the receipt date of the released product.
Modifying this date updates:

• the start date according to the service lead time,
• the start and end dates of the released product,
• the delivery date of the materials.

In the case of multiple partial orders linked to the subcontract order, the latest receipt date is systematically considered to load the end date. If the partial order whose receipt date was used to load the end date is deleted, the end date still applies.

This field is managed depending on the setup of the entry transaction of the subcontract order.

• Subcontract LT (field SCOLTI)

This is the service lead time of the released product, expressed in number of calendar days.
This lead time is loaded, in order of priority, as follows:

• the lead time on the subcontract fee of the service associated to the supplier
• the service subcontract lead time in the selected subcontract BOM
• the subcontract lead time specified in the Product-supplier record of the Service
• - the purchase lead-time specified in the Product-site record of the Service
• the reorder lead time specified in the Product record of the Service.

If no lead time is associated to the service, the lead time of the subcontracted product is used, in the following priority order:

• the subcontract lead time specified in the Product-supplier record
• - the purchase lead time specified in the Product - Site record
• the reorder lead time specified in the Product record.

This field is managed depending on the setup of the entry transaction of the subcontract order.

• Non-financial unit (field SCOPUU)

The unit of the subcontract service is initialized with the operation unit of the service entered in the subcontract BOM.

• OPE qty. (field EXTSTRQTY)

This field is used to specify the quantity, expressed in the operation unit of the service.

• Link quantity code (field STRQTYCOD)

This field is initialized with the link quantity code of the subcontract BOM.
Two values are possible:

• Proportional:
  The operation unit quantity of the service is equal to: quantity of the released product * UOM link quantity of the BOM.
• Fixed:
  The operation unit quantity of the service is fixed, regardless of the quantity of the released product.

• STK-OPE conversion (field OPESTUCOE)

This is the conversion coefficient between the released product quantity expressed in stock unit and the necessary service quantity expressed in OPE.

• Service status (field OPESTA)

This non-modifiable field displays the service status: Pending, In progress, Ordered, Received or Closed.

• Service situation (field SCSTRKFLG)

This non-modifiable field states the current phase of the product: Pending, Under study, Printed, In progress, Closed, Calculated cost price.

• Dimension type (field DIE)

This field is used to enter or select any dimension view set up in the database.

This grid is used to enter or display the analytical dimension types based on the setup of the entry transaction of the subcontract order.

• Dimension (field CCE)

These are the analytical dimensions initialized based on the setup of default dimensions (SCS dimension code). These dimension codes can be modified manually if authorized by the transaction.
They can also be reinitialized following the modification of the dimension for the released product, and the validation of a message asking you to update the dimension types of the service and materials.

These are the analytical dimensions initialized based on the setup of default dimensions (SCI dimension code). These dimension codes can be modified manually if authorized by the transaction.

In creation and modification mode, analytical dimensions are re-initialized with respect to the setup of default dimensions if, when modifying the project code, you answer Yesto the message: 'Update dimension types?'

• Gross price (field GROPRI)

This is the unit gross price of the service, expressed tax excl. It comes from a price list search, or from the product standard cost if the price list search did not return any result.
It can be modified.

• field CUR

This code makes it possible to identify the currency of a site, a BP, etc. It is controlled in the currency table.
 It is recommended to use the ISO coding during the creation of a new currency.

• Net price (field NETPRI)

• Amt. - tax (field LINAMT)

• Price reason (field PRIREN)

Reason associated with this price list rule.
Parameter UPDPRIPUR - Default price reason - base (chapter ACH, group PRI) is used to define a default value for the reasons when the price is modified manually.

• Reference price (field REFPRI)

This field, which cannot be modified, is loaded with the gross price when creating the subcontract order.
Once the subcontract order is created, this price is not impacted by the modification of the gross price: it is used to see the price trends.

• field CURL

• Total excl. tax (co currency) (field LINAMTL)

• Material (field CPNITMREF)

This table contains the list of product-materials necessary for the manufacturing of the released product.
The list of these products is initialized from the subcontract BOM.
The ability to add or exclude materials depends on the value of parameter DEFEORTYP - Default EO management mode (ACH chapter, EOM group). If the modification of materials is authorized, you can perform the following actions using the Actions icon:

• Remove a material by clicking Exclude. The excluded material remains displayed in the grid, but with the Excluded status. You can Reactivate it from the Actions icon.
• Add a material by clicking Add a non-planned material from the last empty line in the grid.
  You cannot add an unexpected material to the subcontract BOM when the version management is active on the released product.

In inter-site management, if the material is:

• Supplied by the subcontractor: it must belong to the category Purchased, so that the order can be generated.
• Made available to the subcontractor: the product must be managed in stock and belong to the category Sold if the supplier is identified as a Customer, so that the materials can be transferred to the subcontractor.

• Type of supply (field SCOFLG)

This field enables the replenishment mode of the component to be specified:

• made available to the subcontractor,
• supplied by the subcontractor.

• Material status (field MATSTA)

This display-only field indicates the line status (Pending, LateClosed).

Click the Actions icon to display a window summarizing the various characteristics of the component status.

• Requirement quantity (field RETQTY)

It represents the quantity calculated from the ordered quantity and the quantity provided by the material BOM link. This value can be modified.

• Stock unit (field STU)

This field indicates the product management unit in which are expressed:

• The stock
• The standard price
• The BOM link quantity, etc.

This information is always displayed, regardless of the transaction used. It cannot be modified.

• Delivery date (field DLVDAT)

This field is only specified in the event of a material product To be sent to the subcontractor.
It contains the expected delivery date at the subcontractor's premises. This date is defined automatically as follows: Subcontract operation start date - Lead time to obtain the materials (information entered in the window displayed by clicking Material details from the Actions icon).

It can be modified as long as the material has not be consumed yet, even partially.

During the modification of this date, the system controls that this date does not correspond to a non-working day or an unavailable day for the delivery date. If this is a non-working day, the date is automatically postponed, otherwise a warning message is displayed.

• Storage site (field STOFCY)

This is the storage site for which the allocation of the materials to be shipped to the subcontractor is made. It is loaded from the receiving site of the released product.
This field is managed depending on the setup of the entry transaction of the subcontract order.

• Location (field LOC)

This is the location associated with the subcontractor. It is automatically loaded, in order of priority, with the location specified in:

• The address of the ship-to customer associated with the receiving site of the subcontract order;
• The location specified in the supplier record (Commercial section).

This field is managed based on the setup of the entry transaction of the subcontract order.

• Preferred lot (field LOT)

This is the lot for which the movement is done.

• Major version (field ECCVALMAJ)

This field indicates which version of this component (material) applies. Major versions might be used where there have been increased or significant changes to the original or previous version, that is the "form, fit or function" has changed.

This field is not populated if the component code defined in the Component or Material field is not version managed.

• Minor version (field ECCVALMIN)

This field indicates which minor version of this component (material) applies. Minor versions might be used where there have been minor features or changes in functionality, or significant fixes applied to a specific major version.

This field is not populated if the component code defined in the Component or Material field is not version managed.

• Production site (field MFGFCY)

This field is managed depending on the setup of the entry transaction of the subcontract order.
This field is entered only in the event of an inter-site/inter-company operation.

• Inter-site: the field takes the value of the site defined at the BP or supplier record.
• Inter-company: the value of this field depends on the default delivery address of the purchase site customer.

• If the receipt site defined for the delivery address belongs to the same company as the purchase site, the subcontract site takes the value of the shipping site if it belongs to the same company as the supplier site. The subcontract receipt site is the receipt site defined for the delivery address.
• If the receipt site defined for the delivery address does not belong to the same company as the purchase site, the subcontract site corresponds to the supplier site if it is a storage site.

• Scrap factor % (field SCA)

The Scrap percentage can be used to increase the requirement quantity in order to take into consideration the losses generated by the manufacturing process.
Its value is initialized with the one specified at BOM level.

• Shrinkage considered (field RELSCATIA)

This parameter is used to manage two management modes for losses upon subcontract release.
It applies to the parent product. When it takes the value: No, the loss percentages of the components defined in the BOM are ignored.

• UOM (field BOMUOM)

This field, which cannot be modified, displays the operation unit of the product specified in the BOM link.

• UOM-STK factor (field BOMSTUCOE)

This is the conversion coefficient between the operation unit of the component and the storage unit.
It is initialized from the value specified at BOM level.

• UOM link quantity (field BOMQTY)

Use this field to define the quantity of this component in the selected unit (field BOMUOM) that is needed to make the parent product.

The sum of the quantity of each component must equal '100' if the defined management unit (field QTYCOD) for this BOM is 'Percentage'.

 By-products are excluded from the total percentage calculations.

• Consumed quantity (field USEQTY)

Consumed quantity. This non-modifiable information is calculated upon receipt of the subcontracted product.

• Allocated quantity (field ALLQTY)

Already allocated quantity. Non modifiable information.

• Allocation status (field ALLSTA)

This non modifiable field shows the product situation with respect to the allocation: Partial, Complete, Partial/Shortage, Complete/Shortage, Not allocated.

• Shortage (field SHTQTY)

It represents the stocked-out quantity.

• Available qty. (field AVAQTY)

This field displays the available quantity expressed in the stock unit of the components.

• Delivered qty. (field DLVQTY)

It represents the quantity supplied to the subcontractor, expressed in stock unit.

• Invoiced qty. (field INVQTY)

It is the invoiced quantity, expressed in stock unit.

• Gross price (field GROPRI)

When the component is supplied to the subcontractor, no information is loaded in this field.
When the component is supplied by the subcontractor, the gross price comes from a price list search, or from the product standard cost if the price list search did not return any result. It can be modified.

• Status (field SCMTRKFLG)

This non-modifiable field states the current phase of the product: Pending, Under study, Printed, In progress, Closed, Calculated cost price.

• Line (field SCMLIN)

• BOM sequence (field BOMSEQ)

BOM sequence number.

• field CCE1

These are the analytical dimensions initialized based on the setup of default dimensions (SCM dimension code). These dimension codes can be modified manually if authorized by the transaction.
They can also be reinitialized following the modification of the dimension for the released product, and the validation of a message asking you to update the dimension types of the service and materials.

These are the analytical dimensions initialized based on the setup of default dimensions (SCI dimension code). These dimension codes can be modified manually if authorized by the transaction.

In creation and modification mode, analytical dimensions are re-initialized with respect to the setup of default dimensions if, when modifying the project code, you answer Yesto the message: 'Update dimension types?'