1

General SCP

Release Overview

GENERAL SCP

RELEASE OVERVIEW

2

General SCP

Release Overview

General Supply Chain Platform 1.8 Release Notes Available: May 20, 2013 In anticipation of all customers migrating off of GSCP in various stages, Exostar will provide visibility to the supplier base as to which orders have been “sunsetted” in the GSCP application and “migrated” to their new enterprise application (buyer hub). Once an order has been sunsetted in GSCP, it can no longer be acted upon in GSCP, but will be accessible in a read-only mode for a period of time. To facilitate this change, Exostar will make the following change to GSCP.

1.1 Creation of Migrated State

A new line and header state of ‘Migrated’ will be created in the GSCP system.

Any order with a schedule line in ‘Migrated’ will have an Order State of ‘Migrated’ regardless of the states of the other schedules (i.e. Migrated is the highest priority state).

A Purchase Order Response will not be generated when the order transitions to the ‘Migrated’ state.

The Purchase Order Change Queue will not be impacted. If a given order has 5 orders in Queue, the order will continue to show ‘5’ after moving to ‘Migrated’. However, the user will not be able to action the order and reduce the queue.

The audit trail history shall be updated to indicate that the system has updated the state of the order line to ‘Migrated’.

1.2 GSCP Sunset Suppliers

Exostar will create a script that will take a buyer and/or buyer account and supplier combination and move all open orders with schedule lines in a ‘New’, ‘New Change’ or ‘In Process’ state to ‘Migrated’ in accordance with each Buyer’s hub migration schedule

This script can be executed during each customer’s Go-Live waves and the timing will vary by customer

3

General SCP

Release Overview

General Supply Chain Platform 1.6

Release Notes Available: May 2, 2011

PURCHASE ORDERS

(TD 2852, 3067, 3219) ‘Supplier Code’ is available to search for purchase orders

The data field ‘Supplier Code’ is now available for searching on the Orders search and summary pages in GSCP. Note: Even if a buyer’s orders have historically included ‘Supplier Code’ data, the search results for ‘Supplier Code’ will only apply to orders and change orders that are added or updated after the GSCP 1.6 release date (May 2, 2011).

The search results on the Order list page include the ‘Supplier Code’ (by default it is located to the right of the ‘Seller Name’). If ‘Supplier Code’ does not appear on the list page, the user should change the

configuration of the page to add the ‘Supplier Code’ column of data. This is done by clicking on the icon.

For buying organizations that want to send ‘Supplier Code’ data for POs and POCs into GSCP, the following file pathnames are to be used:

/Order/OrderHeader/OrderReferences/OtherOrderReferences/ListOfReferenceCoded/ReferenceCoded/ReferenceTypeCoded<VendorIDNumber>

/Order/OrderHeader/OrderReferences/OtherOrderReferences/ListOfReferenceCoded/ReferenceCoded/PrimaryReference/Reference/RefNum<026260-02>

(TD 3472) ‘Change Order Issue Date’ is available to search for purchase orders

The data field ‘Change Order Issue Date’ is now available for searching on the Orders search and summary pages in GSCP. The search field uses a ‘To’ and ‘From’ date range and has a calendar pop-up window for date selection.

‘Number of Queued POCs’ is renamed to ‘Queued POCS’ on the Order details page, and ‘Queued POCS’ is added to the Order list page

The data field ‘Number of Queued POCs’ on the Order details page is renamed to ‘Queued POCS’. This field represents the number of POCs for that order that are waiting to be processed, once the supplier has processed the order version that is currently being displayed in the user interface.

‘Queued POCS’ is also now displayed on the Order list page. This allows a user to quickly view the number of outstanding PO changes for an entire list of orders. If the ‘Queued POCS’ field is not displayed, the user needs to update their screen layout by using the configurator.

For PO Responses to the Buyer, provide the email address of the responding user

The user name and email address of the supplier that responds to a PO/POC are now included in the PO/POC response transactions and passed through to the Buyer’s backend system.

Notes:

4

General SCP

Release Overview

The user data is not shown in the user interface. It is only available on the outbound PO/POC response.

Data mapping on the the buyer side has to be set up to include the user’s name and email address.

File pathname for the user name and email address:

OrderResponse/OrderResponseHeader/ListOfStructuredNote/StructuredNote/GeneralNote

OrderResponse/OrderResponseHeader/ListOfStructuredNote/StructuredNote/NoteID

(TD 3430) On the Order list page, improved the wording of the error message that occurs when a user cannot apply batch processing

When the Orders list page contains one or more orders with lines that cannot be ‘Accepted’ or ‘Acknowledged with Exceptions’, there is a small red icon that appears next to the order line. The message that appears when a user hovers over the red icon has been updated.

Old Message: “Batch Status not allowed. All lines must be Accepted or Processing.”

New Message: “Batch option is not available. All schedule lines within each PO on this list page must be Accepted or Processing.”

(TD 3670) Replaying a PO with a cancelled line no longer applies the ‘Cancelled’ status to all of the subsequent lines in the order

For purchase orders that get replayed back into the active part of the system from the Historical Document Manager (HDM), the following fix has been applied:

PRIOR TO THIS RELEASE:

If any line in the replayed order had a status of ‘Cancelled’, then all PO lines after that cancelled line were automatically changing to a status of ‘Cancelled’ on the reactivated order.

AFTER RELEASE 1.6:

All lines (not schedule lines*) of the replayed PO shall maintain the same status that they had when they were archived out of the active part of GSCP.

*Note: For the schedule lines of a PO/POC that gets replayed, the state at the line level is automatically applied to all of the schedule lines within each PO/POC line. The line level state is determined by the schedule state that has the highest priority (see training materials for more information on state priorities). This is current functionality and does not change with the 1.6 release.

5

General SCP

Release Overview

ADVANCE SHIP NOTICES

Added an ‘ASN Upload’ feature

The system supports a new workflow that allows a Supplier user to manually upload an Excel file containing one or more ASNs. The upload is done within the GSCP user interface and the uploaded ASNs are stored in the same section of GSCP as the ASNs created in the user interface. Any supplier that uses the upload feature can still create or edit ASNs in the user interface, with no changes to that current process.

In order to take advantage of this new functionality, a supplier needs access to the template of the Excel upload file. There are also training materials posted to www.myexostar.com.

Added the ability to search for ASNs by the ‘Last Modified Date’

A user can now search for a set of ASNs that were last modified (created, or updated and saved) within a specified date range.

Note: This can be used in conjunction with the ‘batch print’ feature, for ease of use in creating shipping labels.

(TD 2852, 3067, 3219) ‘Vendor Site Code’ is renamed to ‘Supplier Code’, and ‘Supplier Code’ is now available to search for ASNs

For Advance Ship Notices (ASNs), the field called ‘Vendor Site Code’ is now renamed to ‘Supplier Code’. This creates consistency across the Order Management document types. However, this field name change is only applicable for the user interface. Any references to ‘Vendor Site Code’ for export or download files, or print PDF files, are not changed with this release.

The data field ‘Supplier Code’ is now available for searching on the ‘Create ASN’, ASN search, advance search, and summary pages in GSCP. Any ASNs that included data in the ‘Vendor Site Code’ field, prior to the GSCP 1.6 release, will be included in the ‘Supplier Code’ search results.

The search results on the ASN list page include the ‘Supplier Code’ (by default it is located to the right of the ‘Seller Name’). If ‘Supplier Code’ does not appear on the list page, the user should change the configuration

of the page to add the ‘Supplier Code’ column of data. This is done by clicking on the icon.

For buying organizations that want to send ‘Supplier Code’ data for ASNs into GSCP, the following file pathnames are to be used:

/AdvanceShipmentNotice/ASNDetail/ListOfASNItemDetail/ASNItemDetail/ASNBaseItemDetail/ASNLineItemReferences/ASNReferences/OtherASNReferences/ListOfReferenceCoded/ReferenceCoded/ReferenceTypeCoded<VendorIDNumber>

/AdvanceShipmentNotice/ASNDetail/ListOfASNItemDetail/ASNItemDetail/ASNBaseItemDetail/ASNLineItemReferences/ASNReferences/OtherASNReferences/ListOfReferenceCoded/ReferenceCoded/PrimaryReference/Reference/RefNum<026260-02>

‘Country Code’ information no longer appears in the ‘Region’ data field on ASN shipping labels

GSCP no longer displays the country information in the ‘Region’ data field on the ASN shipping label. The ‘Region’ field only represents the region (used for ‘state’ in the US).

6

General SCP

Release Overview

Note: This only applies to the ASN shipping label, and not to other locations in GSCP where ‘Region’ is displayed.

(TD 3633, 3616) The ‘Transport Carrier ID’ list of values is updated

For creating or editing an ASN, the drop down list of values that are provided for the ‘Transport Carrier ID’ field have been updated. The new list reflects values that were the most frequently selected or entered. Note: A user can still choose to enter a value by selecting ‘Other’ from the drop down list.

The revised list of carriers that is available in the user interface is as follows:

Carrier Entry

Other Local Transportation

ABF Freight Systems (ABFS) Midnite Express (MNX)

BAX Global (BNON) MOD Transport - UK (MOD)

BAX/Schenker (SCNK) N/A - Documentation/Services (NA)

Bennett Motor Express, LLC (BNMX) Old Dominion Freight Line, Inc. (ODFL)

Boeing Licensed Transportation (BLT) Panther (PTWT)

Canadian Freightways Ltd (CFBC) Parcelforce - UK (Other)

CEVA Logistics (CEVA) PEI Incorporated (PEIC)

City Link - UK (CITY) Pilot Air Frt (PAAF)

Continental Airlines (COAI) RDF Logistics, Inc. (RDFG)

Con Way Freight (CNWY) Sameday Worldwide (CAN) (RIWC)

CRST Van Expedited, Inc. (CRPS) Schenker Inc. (SIFF)

CRST- Malone (C282) Sebang Express (Other)

Danzas AEI Drawback Services (AEIW) Smokey Point Distributing, Inc. (SMPD)

DHL (DHLA) Southeastern Freight Lines (SEFL)

DSDA - UK (DSDA) Supplier's Own Truck (STRK)

Dynamic Transit Company (DYCT) System Transport, Inc. (SYTP)

Fed Ex National LTL (FXNL) TNT (Other)

Federal Express Corporation (FEDE) United Parcel Service, Inc. (UPSS)

FedEx Air (FDE) UPS Air (UPSA)

FedEx Custom Critical (FDCC) UPS Freight Inc. (UPGF)

FedEx Freight System, Inc. (FXFE) UPS Ground (UPSN)

FedEx Ground (FDEG) UPS Supply Chain Solutions (UPSF)

FedEx Ground Package System, Inc. (RPSI) USF Best Way (UFSB)

Hand Carry (HAND) USF Holland Inc. (HMES)

Inter Urban Delivery Service, Ltd. (IDSE) USF Reddaway (REDD)

Jet Delivery (JEDE) Westwood Shipping Lines (WWSU)

Kintetsu World Express (U.S.A.), Inc (KINX) YRC, Inc. (RDWY)

Landstar Inway, Inc. (INFY) Yusen Air and Sea Service, Inc. (YASS)

Landstar Ranger (LRGR)

7

General SCP

Release Overview

(TD 3546) Changed the ‘Shipper’ Role option to allow for ASN creation

For the ‘Supp_ASN_Group’ role group, the system now provides the capability to ‘Create ASNs’. Any supplier user that is assigned a role that includes this role group will only have access to the ASN workflow. The ‘Shipper’ user can perform all actions available in the ASN workflow (create, send and print ASNs and shipping labels).

Any user that already has a role which includes this role group is now able to create and edit ASNs.

Note: For more information on how to set up a ‘Shipper’ user role, refer to the very last sentence and link on the ‘SCP – Getting Started’ page on the www.MyExostar.com website.

Related to ASN creation, improved the display of data on the ‘Order Line Selection’ page

In the Create ASN workflow, the columns that display on the list page, which are used to select PO schedule lines for the ASN, have been updated to improve the selection process.

The following fields were added to the page:

Schedule Line ID

Schedule Qty

Requested Delivery Date

Ship-To Party Address (lines) 2 and 3

The following fields were removed from the page:

Change Order Sequence

Seller Agency

Ship-To Party Name (line) 3

INVOICES

(TD 2852, 3067, 3219) ‘Vendor Site Code’ is renamed to ‘Supplier Code’, and ‘Supplier Code’ is now available to search for Invoices

For Invoices, the field called ‘Vendor Site Code’ is now renamed to ‘Supplier Code’. This creates consistency across the Order Management document types. However, this field name change is only applicable for the user interface. Any references to ‘Vendor Site Code’ for export or download files, or print PDF files, will not be changed in this release.

The data field ‘Supplier Code’ is now available for searching on the ‘Create Invoice, Invoice search, advance search and summary pages in GSCP. Any Invoices that included data in the ‘Vendor Site Code’ field, prior to the GSCP 1.6 release, will be included in the ‘Supplier Code’ search results.

The search results on the Invoice list page include the ‘Supplier Code’ (by default it is located to the right of the ‘Seller Name’). If ‘Supplier Code’ does not appear on the list page, the user should change the

8

General SCP

Release Overview

configuration of the page to add the ‘Supplier Code’ column of data. This is done by clicking on the icon.

For buying organizations that want to send ‘Supplier Code’ data for Invoices into GSCP, the following file pathname is to be used:

/Invoice/InvoiceHeader/InvoiceParty/SellerParty/Party/NameAddress/ExternalAddressID<026260-02>

(TD 3318, 3600) ‘Total Amount’ displays on the Invoice list page

The 'Total Amount' data field that is currently shown on the Invoice details page is now also displayed on the Invoice list page. ‘Total Amount’ is a calculated field and it displays the same value on the details page and the list page.

(TD 3227, 3681) ‘Invoice Type’ displays on the Invoice Printout

The ’Invoice Type’ data field that is currently available on the Invoice details page is now also displayed at the top of the Invoice print document. Note: This field is a drop down list of values used to indicate if the invoice is for a debit or credit transaction.

The ‘Bill To Address’ fields on Invoices are no longer mandatory

For invoices, the following ‘Bill to Address’ fields (and file pathnames back to the buyer) can now be left unpopulated by the supplier:

Field Name Xpath

Bill To Company /Invoice/InvoiceHeader/InvoiceParty/BillToParty/Party/NameAddress/Name1

Bill To Address 1 /Invoice/InvoiceHeader/InvoiceParty/BillToParty/Party/NameAddress/Street

Bill To City /Invoice/InvoiceHeader/InvoiceParty/BillToParty/Party/NameAddress/City

Bill To County /Invoice/InvoiceHeader/InvoiceParty/BillToParty/Party/NameAddress/County

Bill To State /Invoice/InvoiceHeader/InvoiceParty/BillToParty/Party/NameAddress/Region/RegionCoded

Bill To Country /Invoice/InvoiceHeader/InvoiceParty/BillToParty/Party/NameAddress/Country/CountryCoded

Bill To Zip /Invoice/InvoiceHeader/InvoiceParty/BillToParty/Party/NameAddress/PostalCode

PLANNING SCHEDULES

(TD 3111) Added ‘Vendor Code’ as a filter parameter for PS and LTPS workflows

When using the filter functionality to locate standard or long-term planning schedules, a new filter parameter has been added for ‘Vendor Code’. This filter occurs after the three parameters that were previously available.

The data field of ‘Vendor Code’ has also been added to the list pages for planning schedules. Note: If a user has configured their list page, then the user needs to manually add the ‘Vendor Code’ using the configurator.

9

General SCP

Release Overview

(TD 1867) Updated one drop down value for ‘Reason Code’

One of the ‘Reason Code’ values on the drop down list is revised from ‘I-Schedule Line Change’ to ‘I-Customer Rqmt Change’. This is applicable for uploaded planning schedule responses and for the responses created from within the user interface.

For any planning schedule that has already applied the ‘old’ reason code, that value will remain in place on the user interface and in any downloaded versions of that planning schedule. However, the selection list will only allow for selection of the new reason code. If an uploaded planning schedule response contains the ‘old’ reason code after this GSCP 1.6 release is in place, then the uploaded file will receive an error message.

(TD 2588) PS Responses to include the Schedule Line Notes

For planning schedule responses, GSCP allows for notes to be posted against the schedule lines. These schedule line notes are being sent out with the PS responses in two ways:

1. All ‘schedule level’ notes for a line are concatenated to the ‘line level’ and sent out as a set of notes that gets associated to all the schedule lines. The file pathname is:

RollsRoycePlanningScheduleResponse/PlanningScheduleResponseDetail/ListOfAgreementScheduleResponseDetail/AgreementScheduleResponseDetail/ListOfScheduleResponseItemDetail/ScheduleResponseItemDetail/BaseResponseDetail/LineItemNote

2. Each ‘schedule level’ note is also sent out individually at the schedule line level using this file pathname:

RollsRoycePlanningScheduleResponse/PlanningScheduleResponseDetail/ListOfAgreementScheduleResponseDetail/AgreementScheduleResponseDetail/ListOfScheduleResponseItemDetail/ScheduleResponseItemDetail/ListOfCommitmentResponseDetail/CommitmentResponseDetail/NewCommitmentNote

Note: The buyer would need to determine which of these two methods should be mapped (line or schedule level) into their backend systems.

ADMINISTRATIVE

(TD 3734) The batch export limit for orders is changed to 40

On the Order list pages, the maximum number of orders that can be selected at one time for a batch export has been increased from 25 to 40 orders.

Also, the number of orders that can be viewed per list page has been changed to 40. This change allows a user to click the ‘Select All’ checkbox at the top of the page and then to export all 40 orders at once. To export the next 40 orders, the user arrows forward to the next list page and repeats the ‘Select All’ and ‘Export’ process.

(TD 3358, 3602) Error messages for failed document transmissions have been improved to provide more information

10

General SCP

Release Overview

For documents that are inbound to GSCP from the buyer (PO, POC, GR, PS, LTPS), the functional acknowledgements have been improved for issues related to the receiving supplier’s account. A general note is included in the functional acknowledgement for the following two scenarios:

1. Supplier’s account has been suspended

General Note: Account suspended for Supplier MPID <supplier’s MPID>

2. Supplier’s account cannot be located in GSCP

General Note: Account not found for Supplier MPID <supplier’s MPID>

(TD 3543) Purging criteria for POs and PO Changes is extended so that these documents remain active in the system for a longer period of time

A summary of the new purging criteria is provided below. For more details, refer to the ‘Data Management Design Document V2.2’.

POs and POCs are purged out of the active part of the system (but still available in the Historical Document Manager) under the following conditions:

‘Cancelled’ or ‘Deleted’ PO/POCs – it has been more than 21 days since the ‘Last Modified Date’

PO/POCs in all other states – it has been more than 180 days since the latest delivery date on the order AND it has been more than 180 days since the order’s issue date (date created in GSCP) AND it has been more than 30 days since the ‘Last Modified Date’.

Note: Legacy orders follow the same purging criteria as normal orders. Legacy orders with ‘LegacyStatus’ in the NoteID field but no value for legacy order status in the GeneralNote field are treated as normal orders. Legacy orders with a status of ‘Completed’ or ‘Not Accepted’ are treated as Completed or Cancelled orders.

‘Last Modified Date’ is populated by the system and will update when any data on the PO/POC is edited and saved, including state changes. For new PO/POCs, the ‘Last Modified Date’ also updates when a PO/POC is received into GSCP or replayed out of HDM.

Increased the ‘User Timeout’ setting

The setting for a user to be timed out of the system due to inactivity has been changed from 30 minutes to 90 minutes.

Note: This does not change the timeout setting for Exostar’s login application (Managed Access Gateway – MAG). Once a user has logged into GSCP through the MAG portal, the timeout controls for the two applications work independently.

11

General SCP

Release Overview

Supply Chain Platform 1.4

Maintenance Release – November 24, 2008

(TD 1988/3097/3168/3230) Provided a Pop-Up Reminder to ‘Send’ Documents If a user tries to navigate away from the PO/POC/ASN/Invoice pages and the document is ready to send, SCP will display a pop-up reminder: “This document has not been sent. Would you like to send it now?” User clicks ‘OK’ or ‘Cancel’. (TD 1887) Added ‘Event Type’ Data to Email Alerts for Stale Orders On the stale order email alerts, for buyers and suppliers, there will be a table format. New and processing orders will be counted in the first column of the table. The second column will give a count for ‘Actioned – Not Sent’ documents, meaning orders with a Status other than ‘New’ or ‘Processing’ and the Event Type is still ‘Viewed’ (not ‘Sent’). NOTE: Items that are ‘Actioned – Not Sent’ can be found by searching for orders in SCP with an Event Type of ‘Viewed’. More recent versions of change orders will remain in a queue until previous versions are actioned and sent. (TD 3264) For Orders, ASNs and Invoices, the ‘Send’ Button Is Now Red (TD 2945) Planning Schedule (Excel) Sheet for Responding Offline Is Changed Summary of the changes:

· Added (3) new columns – see details below · Renamed (4) columns – see table below

· Moved columns – resorted data so that references used in a response are closer to the

response columns · General format changes – improved width of columns, wrapped column names

The following columns were added: · Demand Change – if a row has an ‘X’ in this column then there was a demand change

for that item · Past Due – if a row has an ‘X’ in this column then the item is past due · Schedule Date – this represents the date as shown on the ‘Schedule’ data measure on the

MCV page

12

General SCP

Release Overview

The following columns were renamed:

Current Name as of SCP 1.3 New Name for SCP 1.4

Previous Reference Demand Prior Demand Quantity

Previous Reference Schedule Prior Schedule Quantity

Reference Demand Date Demand Date

Reference Demand Demand Quantity

Reference Schedule Schedule Quantity

(TD 1749/2247) Planning Schedule Download – Reduced Number of Clicks/Pages in the Process The new process is as follows:

1. navigation tree

2. Search screen appears - enter search criteria and click ‘Search’ 3. Inbox Status screen with the Job List appears 4. Click on File Name to download the PS items

NOTE: The ‘Comments’ field was moved to the Search page and is now called ‘Job Name’. Use the job name field to identify a download job on the Inbox list. (TD 3265) Added a ‘7-Day Run Date’ Filter to Search and Download for Planning Schedules, Long Term Planning Schedules and Inventory Status When searching or downloading a PS, LTPS or IS, it is now possible to select a check box that says “View Items with Run Date in the Past 7 Days”. This will allow for a quick filter by Run Dates in the past week. NOTE: If a date is entered in the ‘Run Date’ search field, it will override the selection checkbox for this new filter. (TD 2015) Searching for Demand Planning Documents No Longer Requires a “*” or Run Time When searching by Run Date for Planning Schedules or other Demand Planning documents, it is no longer necessary to follow the ‘Mmm/DD/YYYY*’ format. Run Time is no longer being captured for the searching function. Wildcard is still possible – for example ‘Sep*’ will still bring up all records that start with Sep for September.

13

General SCP

Release Overview

NOTE: Run Date and Run Time will still appear together on the search results and MCV pages. (TD 2886/3039) ‘POC Sequence’ Added to Order Search and List Pages The purchase order change sequence number (called ‘POC Sequence’) has been added to

· Order list pages – search results · Order line selection pages for ASNs and Invoices · HDM search results pages for POs, POCs and POCRs

NOTE: POC sequence will only populate in HDM search results for documents that get added to SCP after this release goes live. (TD 97/2115/2596) Labels on the SCP Navigation Tree Are Improved

The labels that are used on the left-side navigation tree in SCP have been shortened.

Example of previous labels: Order Management

Invoices

Invoice Summary Invoice Search Advance Invoice Search Invoice Create…

Example of NEW labels: Order Management

Invoices Summary Search Advance Search Create Invoice…

14

General SCP

Release Overview

Supply Chain Platform 1.5

Release Notes - July 20, 2009

(TD 2976) Aggregating Invoice Tax Segments

When an invoice is created in SCP that has multiple types of taxes applied at the line item level, the taxes will be aggregated to a summary level for the outbound document (no changes to the SCP user interface). Each summary line will be a total of the taxes by ‘tax type’ and ‘tax percent’.

Example:

If a user creates an Invoice SYSINV1234 with 20 lines and applies,

Tax Type = “VAT” with Tax Percent of 20% to 10 lines

and Tax Type = “VAT” with Tax Percent = 10% to the remaining 10 lines.

At the line level, the Invoice will contain 20 lines with the appropriate Tax Type and Tax Percent.

At the summary level, the outbound Invoice document will contain 2 lines,

One with 10 lines aggregated under Tax Type =”VAT” with Tax Percent = 20%

The other with 10 lines aggregated under Tax Type =”VAT” with Tax Percent = 10%

(TD 3186) ‘Tax Code’ and ‘Tax Code Description’ Added to Invoice Status

Two data fields (Tax Code and Tax Code Description) were added to the Invoice Status document. These are optional fields that appear on the Invoice Status details page at the line level. They can also be exported using the extended CSV format.

(TD 3429) Buyer View – No Longer See the ‘Unsent Warning’ Popup

For a user logging in with a buyer user role, the warning pop-up that asks if a user wants to send an unsent document no longer appears (this is a warning message intended for suppliers only).

(TD 3438) Buyer View – Able to Print ASN Shipping Labels

For a user logging in with a buyer user role, it is now possible to print a shipping label for any ASN that is visible to that user. The ability to print labels is not impacted by the status of the ASN or the estimated arrival date for the ASN.

(TD 3446) Invoice – Outbound XML Document: Default Values Applied to Data Fields Related to Tax

15

General SCP

Release Overview

For ‘Tax Type’, ‘’Tax Category’ and ‘Tax Payment Method’, if a user does not enter a value in these fields on an invoice, then the system will apply the default values that were designated for that supplier account.

Note: Default data values can be created by an admin user for each supplier account (under ‘Administration’ – ‘Supplier Preferences’ on the navigation tree).

(TD 3481) Invoice Status: Export Process and Line Limits Have Been Changed

Using the ‘Export’ button on the Invoice Status list page will export a maximum total of 20,000 lines (rows of data) for one or more Invoice Status documents.

The process steps to export an invoice status have been slightly changed. The new process is as follows:

From the Invoice Status list page, click the ‘Export’ button

Select a file format

Click ‘Proceed’, the system will display the Job List pop-up window

Click on the refresh icon (top right corner) until the Status changes to ‘Completed’

Select the file name

Choose to open or save the file

The export button that was previously located on the Invoice Status details page has been removed, and exporting from the details page is no longer available. Although, it is still possible to export the line level details in a .csv format using the export icon in the top right corner of the lines section of the page.

(TD 3499) ‘International Services’ Added as a Value for ‘Tax Category’ Data Field on Invoices

‘International Services’ has been added as a value for selection on the data field called ‘Tax Category’ on Invoices. This value would be available on the Invoice creation page, on the Invoice details page and in the Tax Details section of the details page.

(TD 3501) Change Sort Order on the Planning Schedule Download

For the Standard Planning Schedule download (Excel format), the sort order of the columns has been changed as follows:

Customer

Schedule Agreement Number

Item Number

Material Number

Period Type

MRP Requirement Number

Schedule Date

16

General SCP

Release Overview

(TD 3518) *Improve Ability to Track ‘Unsent’ Invoices and ASNs

Two changes were made that give users better visibility into ASNs and Invoices that have been created in SCP but have not been sent by the supplier (documents with a ‘Pending’ status).

1. Buyer users (that have access through their user role to see ASNs and Invoices) now have visibility to ASNs with a ‘Planned Pending’ or ‘Actual Pending’ status, and Invoices with a ‘Pending’ status.

2. Email alerts that show stale ASNs and Invoices can be sent to buyer and supplier users. A user can subscribe to these alerts under ‘My Profile – User Preferences’ on the navigation tree. The alerts summarize the number of stale documents per account number and supplier/buyer name.

a. Stale ASN alert – sent out daily, covers ASNs with a pending status and an ‘Estimated Arrival Date’ of today, tomorrow or the next day

b. Stale Invoice alert – sent out weekly, covers Invoices with a pending status and an ‘Issue Date’ that is 2 to 30 days from today.

*Note: The stale ASN and Invoice email alerts are available to all buyer users and supplier users. However, for suppliers, they will only have visibility in the alerts to documents that were created for Boeing MPIDs (accounts).

(TD 3535) System Checking Date Format on Invoices - ‘Issue Date’ and ‘Tax Point Date’ Fields

On Invoices, the date fields of ‘Issue Date’ and ‘Tax Point Date’ are being validated to make sure that the year is 2000 or later. This is being done to manage a constraint on outbound xCBL documents.