This functionality allows you to copy the product structure of a customized item to a standard item.

Note: When a customized structure is copied to a standard structure, the Customized check box in the Items session (tcibd0501m000) is cleared.

Item Types:

• Standard Items: Identified by a regular item code.

• Segmented Items: Consist of a project code segment and an item base segment (i.e., the customized item’s item code). Segments are defined in the Item Code Segmentation session (tcibd0500m000).

Only components valid for the specified Effectivity Unit will be copied.

Copy Options:

• Target Routing Code
  Enter the code of the standard routing to which the customized structure should be copied.

• Copy Product Structure
  Choose whether to:

  • Copy the entire structure

  • Copy only the first level

  • Perform the copy interactively

• Reference Date
  Only parts of the product structure valid on this date will be copied.

• Copy E-Item Relationships
  If selected, related E-item records will be copied.

• Copy All Components and Effectivity Statements
  If selected, unit effectivity is copied to the standard structure. You can specify the unit.
  Exceptions related to routings and operations (that meet date effectivity) are also copied.

• Alternative Material
  If selected, alternative BOM components are included in the copy.

• Use-Up Material
  If selected, use-up materials from BOM components are included.

Enhances purchase order efficiency by automatically calculating the Vendor Delivery Date based on user input.

• When a purchase order line is created, the user enters the item, order quantity, and Due Date.

• LX automatically calculates the Vendor Delivery Date, adding buffer time for quality control, testing, and inspection activities.

• If the Due Date is revised, an informational message prompts the user to review and potentially update the Vendor Delivery Date.

Enhancements:

• A new PUR820 system parameter enables automatic recalculation of the Vendor Delivery Date.

• Instead of a manual reminder, PUR500 now issues a message: “Vendor Delivery Date recalculated,” showing the updated date.

Benefits:

• Eliminates the need to manually review and update the Vendor Delivery Date.

• Removes the need to delete and recreate PO lines to trigger automatic date calculation.

• If Finances is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
• When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.

You cannot delete a purchase order (line) if:

• The linked warehouse order is closed but cannot be removed.
• The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
• A consignment replenishment order is not yet consumed completely.
• The invoice is yet to be completely matched and approved.
• The invoice amount is not yet inserted as turnover history.
• The sales order or service order that is linked to the purchase order line, and for which an internal invoice must be sent from the purchase office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

• When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

To create a purchase order (with subcontracting) third party outsourcing from purchase order, execute these steps:

1. Create a purchase order using the same data set defined in the Subcontracting Models (tisub1100m000) session.
2. In the Purchase Order Intake Workbench (tdpur4601m200) session, click New. The Purchase Order (tdpur4100m900) session is displayed.
3. ...

This enhancement provides additional views, additional order and line details, improved navigation, and additional capabilities to the IDF Customer Order Inquiry cards and to customer order-related business objects such as Allocations, Customer Invoices, Inventory Transaction History, Promotions, Drop Shipments.

Enhanced Order views based on user roles such as customer service, warehouse/logistics, salesperson/commission, data analysis/management reporting

• Improved sort, select and filter capabilities
• Enhanced navigation, data organization and data display
• Improved customer service access to all transactions throughout the entire customer order life cycle – from quote to order, related invoices, and any RMAs, return orders, related credit memos
• Improved grouping of related fields
• New cards to present additional order and order line details
• Consolidation of cards and card details when appropriate
• Enhanced Display and Maintain capabilities for drillback to related customer, ship-to, item, carrier, terms, and other master file details
• Improved display of dates, times and applicable time zones when Region Code time zone support is implemented
• Multi language Description, Name and Address fields displayed in user’s language, if defined, else in base language

For purchase orders, information about the COO allows you to track the related import duties, tariffs, and compliance with sourcing requirements. You can maintain the COO of an item when creating an order or the release level of a purchase order.

When you create a purchase order line in the Purchase Order Lines (tdpur4101m000) session, the COO related details are defaulted based on the item-purchase data defined in the Items - Purchase (tdipu0101m000) session. To view this data, you can use the Country of Origin option from the References menu in the Purchase Order Lines (tdpur4101m000) session.

After the order line is released to Warehousing, an inbound line is created in the Inbound Order Lines (whinh2110m000) session with the COO information. A receipt line is created in the Warehouse Receipt Lines (whinh3512m100) session when the inbound order line is received. To view the actual COO for the item specified on the receipt line, you can use the Country of Origin option from the References menu in this session.

You can view the country of origin (COO) data for the inventory received in a warehouse in the Item - Country of Origin Inventory (tcitu6600m000) session based on the data specified in the header section such as, warehouse, item, and so on.

In the Inventory Tracking Receipt (tcitu2610m000) session, you can view the information related to the purchase order, inventory quantity, and actual COO of the item. You can use the Intrastat Transactions (tccom7171m000) session to view the COO that is reported for an order line and is used for the Intrastat declaration.

You can block a warehouse for inbound procedures, outbound procedures, or both. For example, you can block inbound and outbound procedures for a warehouse if the warehouse must be closed temporarily for inspection.

You can impose these types of blockings:

• Full block: Full block on warehousing procedures.

• Interactive block: Override blocking allowed except blocks on confirm shipment or confirm receipt.

If you impose a full block on inbound procedures...