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

This enhancement provides search capabilities on segment value description in Segment Value List window (WINGSVD).

Segment Value List (WINGSVD):

• Converted to a standard subfile
• New action code 10=Search

This makes it easier to locate segment values when defining segment values in Model Account Builder or Alias definition. In addition, WINGSVD has been redesigned as a subfile to enable WebTop grid capabilities.

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.

Use this session to remap Posted transactions that were mapped incorrectly.

To remap integration transactions successfully, several conditions must be fulfilled. For details, refer to To remap integration transactions.

Enter the ranges of selection criteria for the integration transaction or range of integration transactions to be remapped. You can select the integration transactions of a range of business objects or of a specific business object.

You must select a specific integration document type or an integration document type group.

To evaluate the remapping before you perform the actual remapping, you can select the Simulate check box and the Error Report check box. After you solve the errors, you can run the session again and clear the Simulate check box.

After remapping the integration transactions, you can use the Post Integration Transactions (tfgld4282m000) session to create the postings in the General Ledger.