Supply Network Collaboration 1
Technical Name of the Business Function |
|
Type of Business Function |
Enterprise Business Function |
Available From |
SAP enhancement package 1 for SAP Supply Network Collaboration (SAP SNC) 7.0 |
Technical Usage |
Standalone installation: SCM server installation: |
Application Component |
|
Required Business Function |
None |
Incompatible Business Function |
None |
You can use this business function to enhance supplier collaboration, outsourced manufacturing, and customer collaboration in SAP SNC. The business function provides extensive functional and usability enhancements for these areas. In addition, various new features support a more efficient onboarding of external partners to SAP SNC.
The enhancements include the following new and enhanced features:
Improved visibility and collaboration across the network through the grouping of purchase orders and work orders
Support for quality-issues collaboration between suppliers and customers using quality notifications
Improved collaborative planning functions between SAP Advanced Planning and Optimization (SAP APO) and SAP SNC
Improved supplier connectivity
Enhanced user administration via integration with SAP NetWeaver Identity Management
Improved visibility and decision support through quick view enhancements
Improved engineering collaboration for the sharing of documents (now including sales orders and production orders)
Improved usability through the consolidation of advanced shipping notifications into one shipment in SAP SNC
Enhancements for promotion collaboration
Miscellaneous other enhancements for replenishment, release processing, Supply Network Inventory, ASN processing, file transfer, alert management, and BI
The new Shipment Collaboration
component allows suppliers to group individual advanced shipping notifications (ASNs) in a shipment. A shipment is a grouping of goods that are transported together from one location to another. As of SAP ERP 6.0, customers can transfer shipments from SAP SNC to SAP ERP systems as follows:
Transfer published shipments to the ERP system and automatically create inbound shipments in SAP ERP
Transfer canceled shipments to the ERP system and automatically cancel associated inbound shipments in SAP ERP
For more information, see Integration of Shipment Collaboration with SAP ERP.
Suppliers and customers can use the new Quality Collaboration
component in SAP SNC to notify each other of quality problems or other issues with products or subcontracting components during the manufacturing process or after delivery, so that the customer or supplier can react to the complaint. Quality collaboration is integrated with other applications as follows:
Integration with an SAP ERP back-end system
SAP SNC supports the integration of quality collaboration with an SAP customer back-end system as of enhancement package 5 for SAP ERP 6.0 that has the Quality Management: Extensions in FMEA and Q-Notifications
(OPS_QM_EXTENSION_2
) business function activated. You can use QualityIssueNotificationSUITENotification
XML messages to transfer quality notifications between SAP SNC and the customer back-end system.
Integration of SAP ERP master data for quality notifications with SAP SNC
You can transfer the Customizing data from SAP ERP to SAP SNC using the Customizing Distribution function in SAP Solution Manager. For more information, see Integration of Quality Collaboration with SAP ERP.
Integration with other SAP SNC Applications
A customer or supplier can use quality collaboration with ASN processing, purchase order processing, and work order processing. The customer and supplier can reference an ASN, purchase order, sales order or work order in a quality notification. The customer and supplier can view quality notifications related to purchase orders, work orders and ASNs directly from the respective details screens and from the purchase order and ASN overview screens for these order document types. In addition, a supplier can create a quality notification for a purchase order item or a component directly from the purchase order details screen as well as for a work order input and output component on the work order details screen.
Integration with Collaboration Folders (cFolders)
A supplier and customer can use cFolders to store and share additional files that are relevant to a quality notification.
In SAP SNC, you can now exchange the following document types using cFolders:
WBS element
Sales orders
Production order
The corresponding document IDs can be transmitted from SAP ERP 6.0 to SAP SNC.
To send document IDs from SAP ERP to SAP SNC with the services PurchaseOrderERPReplenishmentOrderCollaborationNotification_In
and ReplenishmentOrderNotification_In
and enable a collaboration on documents between users of the SAP SNC system and users of SAP ERP, you must activate the LOG_MM_OM_2
business function in the SAP ERP system. To enable a transfer of document IDs, the services were enhanced as follows:
The PurchaseOrderERPReplenishmentOrderCollaborationNotification_In
service now includes the following elements:
WBS element
Sales order number
Sales order item number
Production order number and operation number
The ReplenishmentOrderNotification_In
service now includes the purchase requisition number and purchase requisition item number.
For more information, see Calling Collaboration Folders.
Note
The enhancements for the integration of cFolders in SAP SNC support the Collaborative Manufacturing for Complex Products
business scenario. The business scenario uses the business processes Engineering (MTO) IM&C with cFolders
and Engineering (ETO) IM&C with cFolders
to transfer order BOMs or WBS BOMs from SAP ERP 6.0 to cFolders. If you want to transfer order BOMs to cFolders, you must activate the PLM_CFO_ORDWBSBOM
business function in the SAP ERP system.
If you want to transmit 2-character revision levels from SAP ERP to SAP SNC, you must implement a user exit in SAP ERP. For more information, see Revision Level
in the Features
section and Revision Level.
In a Supplier-Managed Inventory
(SMI) scenario or in a Dynamic Replenishment
(DR) scenario, you can integrate planned receipts with the customer’s SAP APO system. A customer with SAP APO can send demand forecast data (DR scenario) or inventory and demand data (SMI scenario) to SAP SNC and request that the supplier send planned receipts back to him or her based on the data. The customer can consider the planned receipts in Capable-To-Match-Planning in SAP APO.
If you want to integrate the planned receipts that the supplier creates in SAP SNC with SAP APO, you must make the following settings:
In SAP APO, you must activate the business function SCM-APO, Planning with SNC-Planned Receipts in APO
(SCM_APO_DISTR_REC
). Only then you can send demand forecast and inventory and demand data from SAP APO to SAP SNC. (Based on this data, the supplier creates the planned receipts.) The business function also enables the key figure Distribution receipt (SNC-planned)
that allows SAP APO to process planned receipts received from SAP SNC.
In SAP SNC, you must make settings in Customizing for Supply Network Collaboration
after the activation of the business function Supply Network Collaboration 1
(SCM_SNC_GEN_1
).
For more information, see the Features section.
You have installed the components listed in the following table:
Type of Component |
Component |
Required for the Following Features Only |
|---|---|---|
Software Component |
SCMSNC 701 |
Standalone installation only |
Software Component |
SCM 701 |
SCM server installation only |
Software Component |
SCM_BASIS 701 |
Not applicable |
Software Component |
SCMBPLUS 701 |
Not applicable |
XI Content |
XI CONTENT SNC 7.01 |
Required for the integration of order documents, such as shipments or quality notifications |
BI Content |
BI Content 7.05 |
Not applicable |
cFolders |
cFolders 5.00 |
Not applicable |
If you want to use the ASN-based due quantity for scheduling agreement releases (SA releases) and you have previously used SA releases in SAP SNC, you must run the Due Quantity Computing and Setting Change Status Flag in SA Releases
(/SCA/REL_DUE_CHG_SET
) upgrade report after you have activated the business function Supply Network Collaboration 1
(SCM_SNC_GEN_1)
. The report calculates the ASN-based due quantity for existing scheduling agreement releases. For more information, see the Features
section and the report documentation.
If you want to integrate shipment collaboration in SAP SNC with SAP ERP, you need the following additional components:
XI Content: SNC 7.01 or higher
SAP ERP 6.0 or higher
For more information about shipment collaboration, see the Features section.
If you want to integrate quality collaboration in SAP SNC with SAP ERP, you need the following additional components:
XI Content: SNC 7.01
SAP ERP 6.0 with enhancement package 5
For more information about quality collaboration, see the Features section.
If you want to use identity management, the following prerequisites must be met:
You need SAP NetWeaver Identity Management as an additional component.
You must set up a system connection from SAP SNC to SAP NetWeaver Identity Management. For more information, see Master Data and Settings for Identity Management with SAP SNC.
Enhancements are available for the following functions in promotion collaboration.
The creation and update of multiple promotions was enhanced as follows:
A customer can send a DemandInfluencingEventNotification
XML message (promotion message) to SAP SNC with promotion data for multiple promotions (location products, promotion quantities, and time buckets). SAP SNC can use the promotion data from the promotion message to create new promotions or update existing ones. However, the promotion message can only contain one promotion ID on the header level of the promotion message. To create new promotions or update existing ones, SAP SNC must first determine if there are existing promotions in SAP SNC that are relevant to the customer's promotion data.
SAP SNC can automatically search for promotions to determine if a promotion must be updated or if SAP SNC needs to create a new promotion. To search for promotions, you list all of your existing promotions in SAP SNC so that SAP SNC can compare the promotion data in the promotion message to these promotions. Once SAP SNC has determined which promotion data in the promotion message is related to a new promotion and which promotion data is relevant for an update of existing promotions, SAP SNC can automatically assign the time buckets from the promotion message to the existing promotions in SAP SNC for an update or to the new promotions it needs to create.
For more information, see Creating Promotions from Promotion Messages with Multiple Promotions.
SAP SNC can determine promotion attributes (event type, promotion description) for the promotions in promotion messages with multiple promotions. For more information, see Creating Promotions from Promotion Messages with Multiple Promotions.
When assigning time buckets to a promotion, you can determine whether SAP SNC uses the promotion sales forecast data or promotion order forecast data that the customer sends for a location product. For more information, see Creating Promotions from Promotion Messages with Multiple Promotions.
You can define an offset value in days that allows SAP SNC to calculate promotion start dates from the time buckets in the DemandInfluencingEventNotification
XML message. SAP SNC can use the start dates to determine unknown promotion IDs before it applies the promotion offset profile to calculate relevant promotion dates.
If SAP SNC receives a DemandInfluencingEventNotification
XML message with promotion data for one promotion or for multiple promotions, SAP SNC can aggregate the quantities from the daily time buckets of a promotion in the DemandInfluencingEventNotification
XML message to calculate a total promotion quantity. Based on the total promotion quantity of a promotion, SAP SNC can use the sales and distribution pattern from the promotion profile for the creation of the promotion. For more information, see Determination of Sales and Distribution Patterns from Promotion.
SAP SNC can automatically determine the promotion uplift based on the promotion data from the promotion message (DemandInfluencingEventNotification
XML message). To determine the promotion uplift, SAP SNC calculates the sum of the short-term forecast values for the sales period of the promotion. SAP SNC then subtracts this number from the promotion quantity that the customer has maintained and sent in the promotion message. The result gives the supplier the promotion uplift. For more information, see Calculating the Promotion Uplift.
The customer can send in partial updates of promotions. Partial updates are promotion updates where only some of the location products have been changed. For more information, see Creating and Updating Promotions from Promotion Messages.
After the supplier has manually changed a promotion on the SAP SNC Web UI, SAP SNC can now automatically delete a promotion item from the promotion if the customer has removed a promotion item in his or her back-end system and sent a corresponding promotion update (using a DemandInfluencingEventNotification
XML message to SAP SNC. Previously, SAP SNC could not remove the promotion item.
If you want to use the automatic deletion, you must make settings in Customizing for Supply Network Collaboration
under .
The following new or enhanced Business Add-Ins (BAdIs) are available:
To use the brand number, size number, or pack number for a product instead of the product hierarchy in the Determine Promotion IDs
Customizing activity, you can use the new method DETERMINE_BSP
from the existing BAdI Maintain Settings for Promotion Planning
(/SAPAPO/ICH_PROM_EXT
).
To change or extend the search parameters for the determination of promotion IDs, you can use the new BAdI Determine Promotion IDs
(/SAPAPO/ICH_PROMID_DET
).
To change or extend the search parameters for the determination of promotion attributes, you can use the new BAdI Determine Promotion Attributes
(/SAPAPO/ICH_PROM_ATTR
).
On the overview screen of the Responsive Replenishment Monitor (RR Monitor), you can call up the Product Activity Message
screen for a location product.
If the customer back-end system or the supplier back-end system does not support multiple items for the same location product within an order document (for example, to perform follow-up processes that require single items such as an ATP check for a sales order), SAP SNC can merge promotion and baseline items of a replenishment order before sending them to an ERP back-end system. If the confirmed quantity for a merged item is different from the requested quantity, the quantity can be split across the items of the replenishment order when the confirmation is received in SAP SNC according to different rules. SAP SNC also merges and splits the items of ASNs that reference such a replenishment order. For more information, see Merging and Splitting Items.
A new planning service is provided on the Web UI and in the planning service manager. This planning service publishes replenishment orders. You use this service if you have created firm receipts or TLB shipments, but not yet published the related replenishment orders. You can call up the new planning service in the Responsive Replenishment Monitor and in the Min/Max Replenishment Monitor. For more information, see Planning Functions in the Replenishment Monitor.
A supplier can now save and publish a replenishment order in one step when manually creating a replenishment order.
By using the location product prefilter, you can improve the performance of transport load builder (TLB) runs in the Planning Service Manager (PSM), provided that all of the following conditions are met:
A selection that you use for a TLB run (selection type PE_LANE
) meets the following conditions:
In the selection, you have specified no products.
The All Products
option is selected for all transportation lanes.
All Products
means a relatively high number of products.
For only a few products in the transportation lanes, planned receipts or unpublished replenishment orders exist in the system.
If these prerequisites are not met, we recommend you do not switch on the location product prefilter.
You activate the location product prefilter in Customizing for Supply Network Collaboration
under . Note that this setting is client-dependent.
For release processing, the following enhancements are available:
ASN-based due quantity
When you publish an ASN for a scheduling agreement release, the system automatically updates the ASN-based due quantities in the schedule lines of the scheduling agreement release. The due quantities are displayed on the Due List for Purchasing Documents
screen. For more information, see the Prerequisites section.
New ASN alerts for release processing
New alert types inform about deviations between the ASN item data (quantity and delivery date/time) and the corresponding data in the request schedule lines or in the confirmation schedule lines of the current scheduling agreement release. For more information, see ASN Processing
in the Features
section.
The following enhancements are available for purchase order collaboration.
In SAP SNC, the customer can group purchase order items (PO items) manually or automatically. PO item groups enable customers and suppliers to consider dependencies between different purchase orders or purchase order items in SAP SNC. Using groups, customer and supplier can also consider dependencies between work orders that are related to the grouped PO items.
SAP SNC can automatically group purchase order items that refer to the same ERP document (sales order, purchase requisition, production order, or WBS element). In addition to automatic grouping, the customer can create and maintain groups manually on the Web UI of SAP SNC. The work orders associated to the PO items of a PO item group automatically make up a group. Based on groups, you can easily identify related purchase order items on the Web UI of SAP SNC. Since PO items of a group can be linked with predecessor-successor relationships, you can analyze the impact of issues for one PO item on the successor PO items.
PO item grouping supports complex outsourced manufacturing processes where certain or all operations of a manufacturing process are outsourced to subcontractors. Multiple subcontractors may be involved to complete the production, increasing the complexity in the monitoring and management of the supply chain. ERP documents, such as purchase requisition, sales order, WBS element, and production order, naturally group the material and manufacturing requirements of a specific demand. For more information, see Purchase Order Item Group.
Purchase order item (POI) exceptions and new PO alerts are available that inform about delivery-relevant issues for a purchase order item. From the business perspective, POI exceptions are similar to the POI alerts. Both objects inform you about exceptional situations. However, a POI exception is a different technical object (a status at the PO item level) that allows – in contrast to PO item alerts – to select PO items that are affected by issues for the PO worklist. For more information, see Purchase Order Item Exception.
Previously, a customer had to accept deviations and update the request schedule line of a purchase order in two steps. A new option on the Web UI allows a customer to accept deviations and update request schedule line in one step. For more information, see Manual Approval.
The following enhancements are available for the purchase order worklist:
A supplier can display and confirm subcontracting components for subcontract orders in the purchase order worklist. If a schedule line contains subcontracting components, the Confirm
popup contains an additional table displaying the component data.
The following additional data is available in the Confirm
popup:
Confirmation status of the item
Approval status of subcontracting components
Approval status on the confirmation schedule line.
This status is the aggregated approval status of the subcontracting components.
Approval status of the item
Customer batch in the item
For the supplier, the new query object type Purchase Order Items Where I Am Goods Recipient
is available. A query based on this query object type displays purchase order items for which the supplier is the goods recipient. The supplier can use the query to find purchase orders upon which he or she depends. If necessary, the supplier can adjust the confirmations for the purchase orders for which he or she is the supplier. For more information, see Selecting Purchase Order Items with Special Features.
Previously, the length of a note was restricted to 1000 characters when sending a purchase order from SAP ERP to SAP SNC using the ReplenishmentOrderNotification
XML message. If a customer uses the ReplenishmentOrderNotification
XML message to send purchase orders to SAP SNC, he or she can now transfer notes without length restriction.
Previously, if a supplier sent a purchase order confirmation to SAP ERP using a ReplenishmentOrderConfirmation
XML message, not all data was transferred in the confirmation. A supplier can now send purchase order confirmations directly to the customer back-end system using a PurchaseOrderERPConfirmationRequest
XML message.
The message sends manufacturer part number data to a customer SAP back-end system of enhancement package 5 for SAP ERP 6.0. For more information, see XML Messages for Purchase Order Collaboration.
If you want the supplier to use only certain customer batches and to enter only numbers of allowed customer batches in a purchase order confirmation, you can use batch validation. For more information, see Batches and Configuration in Purchase Order Collaboration.
You can manually change inventory data on the supplier view of the Inventory Overview
screen for Supply Network Inventory. You can only modify inventory data if the business partner to which you are assigned is the business partner providing that inventory data (data-providing partner). For more information, see Manual Change of Inventory Data.
The new Shipment Collaboration
component allows suppliers to group individual advanced shipping notifications (ASNs) in a shipment. A shipment is a grouping of goods that are transported together from one location to another. The Shipment Collaboration
component comprises customer-specific and supplier-specific screens for various tasks, including the creation, update and printing of shipment documents. For more information, see Shipment Collaboration.
Existing roles have been enhanced to include authorizations for the new shipment screens. For more information, see the documentation for the following roles:
The following enhancements are available for ASN processing:
Redesign of ASN overview
The ASN Overview
screen has been redesigned with the personal objects worklist (POWL) technology.
New fields
The following new fields are available:
Supplier batch number, customer batch number, and last publication date (see ASN Data)
Fields for the integration with the new Shipment Collaboration
component (see Shipment Assignment Status of Advanced Shipping Notifications)
Fields for the integration with the new Quality Collaboration
component (see ASN Processing)
New ASN alerts for release processing
New ASN alerts types are available (alert types 7437 to 7444) that are relevant for release processing. The alert types inform about deviations between the ASN item data (quantity and delivery date/time) and the corresponding data in the request schedule lines or in the confirmation schedule lines of the current scheduling agreement release. For more information, see ASN Alerts and Generation of Alerts for Non-Matching ASNs in Release Processing.
Generation of alerts for overdue and unassigned ASNs
The Generate Alerts for Overdue and Unassigned ASNs
(/SCA/ASN_PASTDUE_ALERTWRITE
) report has been enhanced as follows:
Instead of generating alerts based on the delivery date, you can now also generate alerts based on the shipping date.
The report can now also create alerts for overdue ASNs that are not yet assigned to a shipment.
For more information, see Generation of Alerts for Overdue and Unassigned ASNs.
Calculation of total weights and volumes of an ASN
For more information, see Calculation of Total Weight and Volume of an ASN.
Copy of ASN items
On the Create ASN
screen and the ASN Details (Supplier)
screen, in change mode, you can use the new Copy Item
pushbutton to create a new item based on a selected item. For more information, see Copy of ASN Items.
Processing goods receipt messages
The number goods receipt document was added to the XML message type ReceivedDeliveryNotification
(RDN) and to the message interface type ReceivedDeliveryNotification_In
at item level (new element GoodsReceiptReference
).
A goods receipt document is a document that an ERP system creates when posting a goods receipt (called “material document” in an ERP system by SAP). The number of the goods receipt document is relevant for posting goods receipts with respect to an ASN item. In addition to the ASN number and the ASN item number, the enhanced RDN message can now transmit the goods receipt document to SAP SNC, which supports the correct processing of partial goods receipts in SAP SNC: When receiving an RDN, SAP SNC automatically checks whether it has already received the same goods receipt document for a particular ASN item previously. If yes, SAP SNC ignores the goods receipt quantity transmitted for this goods receipt document in the RDN message under consideration.
You can navigate from the receipts/requirements list to the relevant detail screen of a receipt/requirement element. This feature is available for the following types of order documents:
Forecast delivery schedule
JIT delivery schedule
Purchase order
Purchase order confirmation
SA confirmation
Replenishment order
ASN
You can navigate from the due list for purchasing documents using a link to the respective order document type details screen, which, depending on the document type is either the purchase order details screen, the replenishment order details screen, or the release details screen.
Suppliers and customers can use the new Quality Collaboration
component in SAP SNC to notify each other of quality problems or other issues with products or subcontracting components during the manufacturing process or after delivery, so that the customer or supplier can react to the complaint.
The central object for quality collaboration in SAP SNC is the quality notification. A supplier can create quality notifications on the SAP SNC Web UI. He or she can save and publish them so that they are sent to a customer back-end system. SAP SNC can also receive quality notifications created by a customer in his or her back-end system.
Suppliers and customers can use statuses to record the current stage of processing. Changes to quality notifications can be transferred back and forth between SAP SNC and a customer back-end system. Suppliers and customers can use subject codes to classify a quality notification according to the defects or problems being reported. On item level, suppliers and customers can use defect type codes to identify the type of problem being reported in the item. For more information, see Quality Collaboration.
You can use the branding function to maintain a logo for a business partner on the SAP SNC Web user interface (Web UI). For more information, see Branding the SAP SNC Web UI.
The integration of SAP SNC with SAP NetWeaver Identity Management allows you to perform a stricter governance, risk and compliance management of user administration activities than before, such as the following:
Authorization requests can be validated at a central instance.
In critical cases, for example, SAP NetWeaver Identity Management can trigger workflows before it grants authorizations automatically.
Activities of a user administrator in SAP SNC user administration can be transferred from SAP SNC as requests to SAP NetWeaver Identity Management. SAP NetWeaver Identity Management then distributes the new user or changed user data across an entire system landscape. For more information, see Identity Management for SAP SNC: Distribution of Local Users.
For the user administration, the following enhancements are available:
On the User Administration (Own Data)
Web screen, a user can maintain basic personal data such as the name, e-mail address, or telephone number.
For a hosting scenario, you can determine that only the hosting business partner (the business partner who runs SAP SNC) has the power user authorization and can maintain the users for the customer and the supplier. For more information, see User Administration.
If SAP SNC is to check whether a user name entered on the User Administration
Web screen adheres to a naming convention, you can implement the Business Add-In Checking the Naming Convention of the User Name
(/SCA/PUM_USERCHECK
). For more information, see Settings for User Administration.
You can use the following new monitors in the predefined monitor set SNC Monitor Templates
for SAP SNC to monitor a system landscape or the performance of background planning processes:
Availability
monitor
The Availability
monitor allows you to monitor which systems are available and running by using the CCMSPING agent. For more information, see Availability Monitor in CCMS
Connectivity
monitor
The Connectivity
monitor allows you to monitor inbound and outbound queues for the SAP Core Interface (CIF) and for SAP NetWeaver Process Integration (SAP NetWeaver PI 7.1). It displays faulty queue entries in the inbound and outbound queues in CIF or PI. For more information, see Connectivity Monitor in CCMS.
Transaction Performance
monitor
The Transaction Performance
monitor allows you to monitor the performance of the planning runs. You can monitor the following planning runs:
Replenishment planning run
TLB run
Forecast run
For more information, see Transaction Performance Monitor in CCMS.
The following monitors have been renamed:
The monitor CIF Master Data Queue Monitor
has been renamed to Connectivity
.
The monitor SNC Monitor
has been renamed to XML Message Processing
. For more information, see XML Message Processing Monitor in CCMS.
For more information, see SAP SNC Monitoring with CCMS.
The following new features are available:
You can use the microblog to post short messages to other users and business partners for information purposes. You can ask for an acknowledgment of a message or a yes or no response to it. For more information, see Microblog.
New building blocks for application-specific key figures have been added to the standard delivery of the quick view.
In the quick view, you can include alert building blocks that display alerts related to SAP SNC applications.
In the quick view, you can create tabs to organize and group building blocks.
You can personalize data visualization in a building block and the chart scale of a building block.
You can configure the following in the quick view configuration:
You can configure the scale of a chart.
You can configure the navigation in a split profile.
You can determine the text of the x-axis label of a chart.
You can overwrite the color of the first segment of a key figure bar that has a split profile or the whole key figure if it has no key figure profile.
You can access the quick view configuration in Customizing for Supply Network Collaboration
under or on the SAP Easy Access
screen under .
For more information, see Quick View.
For file transfer, the following enhancements are available:
New files
The following new files are available:
File for Invoice
File for Work Order Actuals
File for Supply Network Inventory
Enhanced files
The following files were enhanced:
File for Purchase Order
Using the File for Purchase Order
file, a supplier can now also confirm subcontracting components of subcontract orders.
File for Supplier-Managed Inventory
The CSV file now includes stock-on-hand information.
File for Due List for Purchasing Documents
The CSV file now includes the revision level.
Extension of files with customer-specific fields and columns
The document-based file transfer plug-ins now enable customers to extend the files for file transfer with customer-specific fields and columns. To enhance the plug-ins, you can use the following BAdIs:
BAdI: Purchase Order Interface
(/SCA/FTR_FILE_PO
)
BAdI: Due List for Purchasing Documents
(/SCA/FTR_FILE_ASNDLPD
)
BAdI: Due List for Planned Receipts
(/SCA/FTR_FILE_ASNDLPR
)
BAdI: Work Order Interface
(/SCA/FTR_FILE_WO
)
BAdI: Invoice Interface
(/SCA/FTR_FILE_INVOICE
)
You call up the BAdIs in Customizing for Supply Network Collaboration
under .
Scheduling jobs
You can define your own job schedules for the downloading of files in Customizing for Supply Network Collaboration
under .
For more information, see File Transfer.
For alert management, the following enhancements are available:
You can determine the type of link (URL) you want to include in the alert notification e-mails. You can choose between the following URLs:
URL that groups all alert types that match the selection of the notification profile and navigates the recipient to the Alert Monitor
Alert-specific URL that navigates the recipient either to the Alert Monitor or to an application screen relevant to the alert
For more information, see Sending URLs Using Alert Notification E-Mails.
You can determine that SAP SNC automatically deletes validation alerts once SAP SNC receives an XML message that updates and resolves the issue that caused the exception. For more information, see Display and Deletion of Alert Data in the SAP SNC System.
You can change the priority of alert types. For example, if an alert type has the standard alert priority Warning
, you can set the alert priority to Information
.
You can change the alert priority in Customizing for SCM Basis
under .
You can define the sequence in which the system retrieves data from the database when processing the alerts. For more information, see Alert Monitor.
A Smart Form is now available for each PDF-based print form.
The revision level is displayed in the following document types:
Purchase order
Work order
Scheduling agreement release
Advanced shipping notification (ASN)
For more information, see the Prerequisites
section and Revision Level.
The purchasing group is now available as a selection parameter on the following screens in the customer view:
Overview screens for PO, ASN, invoice, and releases
Worklists for PO as described in the Additional Selection Parameters section
Due list for purchasing documents as described below (see Additional Selection Parameters) and the receipts and requirements list
In the supplier view of the due list for purchasing documents, the following additional selection parameters are available:
Confirmation status
Approval status
Order document type
In the customer view of the due list for purchasing documents, the following additional selection parameters are available:
Confirmation status
Approval status
Order document type
Purchasing group
On the purchase order worklist, additional selection parameters are available for the following worklist object types:
In the Confirm & Publish Purchase Order Items (Supplier)
worklist object type the following additional selection parameters are available:
Customer batch
Item change date (relative to today)
Item change date
Seller
Original sales order number
WBS element
Approval status
Exception
Group indicator
In the Canceled / Blocked Purchase Order Items (Supplier)
worklist object type the following additional selection parameters are available:
Product group
Product group type
Customer batch
Item change date (relative to today)
Item change date
Seller
Original sales order number
WBS element
Approval status
Group indicator
In the Purchase Order Items (Supplier)
worklist object type the following additional selection parameters are available:
Customer batch
Item change date (relative to today)
Item change date
Seller
Original sales order number
WBS element
Approval status
Exception
Group indicator
In the Rejected Purchase Order Items
worklist object type the following additional selection parameters are available:
Customer batch
Item change date (relative to today)
Item change date
Group indicator
Purchasing group
In the Purchase Order Items (Customer)
worklist object type the following additional selection parameters are available:
Customer batch
Item change date (relative to today)
Item change date
Seller
Original sales order number
WBS element
Approval status
Exception
Group indicator
Purchasing group
On the Documents Requiring Invoices
screen, the shipping date is available as a selection parameter.
The following enhancements are available:
New extractors
There are two new BI extractors for SAP SNC, an extractor for shipments (see Extractor for Shipments) and an extractor for quality notifications (see Extractor for Quality Notifications).
Enhanced extractors
The following existing BI extractors have been enhanced:
Extractor of purchase orders
This extractor now extracts the following data:
Actual delivered quantity
Unit of measure
Delivery date confirmed by the supplier
For more information, see Extractor for Purchase Orders.
Extractor for the lead time of work order phase
This extractor now extracts data the following data:
Phase completion indicator
Shipping completion indicator
Date/time on which the phase or the shipping was completed
For more information, see Extractor for Work Order Phase Lead Time.
In a Supplier-Managed Inventory
(SMI) scenario or in a Dynamic Replenishment
(DR) scenario, you can integrate planned receipts created by the supplier with the customer’s SAP APO system. A customer with SAP APO can send demand forecast data (DR scenario) or inventory and demand data (SMI scenario) to SAP SNC and request that the supplier send planned receipts back to him or her based on the data. The customer can consider the planned receipts in Capable-To-Match-Planning in SAP APO.
To integrate the planned receipts with SAP APO the following enhancements are available in SAP SNC:
The supplier can use new grid arrangements to create and send planned receipts to the customer.
In the order forecast monitor, which is used for the DR scenario, the supplier can create planned receipts by copying the customer planned requirements.
The supplier can trigger the sending of the planned receipts to SAP APO manually on the Web UI.
The customer can send the planned receipts to SAP APO using a report.
New alerts inform about exception situations for the integration of planned receipts with SAP APO.
New reports generate alerts that inform the supplier that new demand forecast data (DR) or new inventory and demand data (SMI) have been sent to SAP SNC.
For more information, see Integration of Planned Receipts with the Customer SAP APO System (DR) and Integration of Planned Receipts with the Customer SAP APO System (SMI).