SNC User Roles

These are the user roles that can be assigned to the Internet User

• SAP_SCM_ICH_ADM_CUS Supplier Collaboration: Administrator (Customer)
• SAP_SCM_ICH_ALRT_TYP SAP SNC: Alert Display
• SAP_SCM_ICH_AMON SAP SNC: Alert Monitor Maintenance
• SAP_SCM_ICH_ASN_SUP ASN Maintenance (Supplier)
• SAP_SCM_ICH_DISPLAY SAP SNC: Display User
• SAP_SCM_ICH_DR_SUP Dynamic Replenishment (Supplier)
• SAP_SCM_ICH_FCS_CUS Forecast Collaboration (Customer)
• SAP_SCM_ICH_FCS_SUP Forecast Collaboration (Supplier)
• SAP_SCM_ICH_IV_SUP Invoice Maintenance (Supplier)
• SAP_SCM_ICH_OMO_CUS Outsourced Manufacturing: Order Processing (Customer)
• SAP_SCM_ICH_OMO_SUP Outsourced Manufacturing: Order Processing (Supplier)
• SAP_SCM_ICH_OMP_CUS Outsourced Manufacturing: Planning (Customer)
• SAP_SCM_ICH_OMP_SUP Outsourced Manufacturing: Planning (Supplier)
• SAP_SCM_ICH_PO_SUP Purchase Order Processing (Supplier)
• SAP_SCM_ICH_RK_SUP Release and Kanban Processing (Supplier)
• SAP_SCM_ICH_RP_SUP Replenishment Processing (Supplier)
• SAP_SCM_ICH_SU_CUS Supplier Collaboration: Superuser (Customer)
• SAP_SCM_ICH_SU_SUP Supplier Collaboration: Superuser and Admin. (Supplier)

Number ranges

SNC Number ranges can be set from the Supplier WebUI.

ASN number range intervals:

• ASN number range is set from Master Data  → Number Ranges → ASN Number Range Intervals: You define the interval from and the interval to for  the business partner. Separate number range intervals can be maintained for each customer/ supplier.
• Number Range Interval Attributes: Master Data  → Number Ranges → Number Range Attributes: Here you can define prefixes or suffixes for your number range interval. For eg. “ZASN” can be defined as the prefix for the ASN number range – Interval Type: ASN
• Similarly Invoice Number range interval and Number range attributes can be set

SAP SNC Master Data

SNC Master Data primarily consists of the following:

1. Product
2. Location
3. Business Partner
4. Transportation Lane

Master Data can be created in SNC or transferred over from the back-end system (SAP ECC). Master data is transferred over from SNC using the Core Integration Framework (CIF).

Product:

• Material Data from ECC is CIF’ed to SNC.
• You can set material master changes to be transferred to SNC immediately by the following setting:
• CFC9 –> Material Master Change Transfer –> 2 (BTE Transfer, Immediate)
• You can Activate change pointers for Products (BD52) to allow transfer of changes to Material Master

Location:

• A Location needs to be created for every vendor and customer plant in scope.
• When you CIF over the customer’s plants, it creates a location of type 1001 – Production Plant
• Every vendor will be created as a location of type 1011 – Vendor in SNC by default

Business Partner:

• A business partner needs to be created for the following:

• Every organizational entity in scope
  • The BP of type Organization is then assigned to the corresponding locations.
  • A single business partner can be created for various locations. For e.g. when one business partner representing one vendor needs to be assigned to various vendor ship points created as separate locations.
  • When a vendor is Cif’ed across from ECC you can set the Create Loc./BP to 2 – Create both. This will create the vendor both as a location and a business partner in SNC and will also assign the business partner to the vendor location.

• Every person/user who will access the SNC WebUI needs to be created as a separate BP.
  • The “Person” type BP needs to be created as an Internet User
  • The views in the SNC WebUI that can be accessed by the person are assigned to the “Internet User”
  • A relationship also needs to be defined for the business partner. The relationship “Is SNC user of” is defined in order to specify the vendor/ customer business partner for which the person is a SNC user.

Transportation Lane:

• A transportation lane is used to define a means of transport between a source location and a customer location
• The Purchase Inforecord or Scheduling Agreement (+Source List) is CIF’ed over from ECC to create a transportation lane
• The Means of transport need to be created manually
• The means of transport define whether it is a Truck, train, Ship etc and the HRS and KMS between the source and destination location

PO Collaboration for Text Item POs

This is regarding Po with text item – having no material numbers. These type of POs are normally used for non-stock materials

POs having no material numbers fail in SNC since SNC validations find the material missing.

There are 2 ways to deal with this:

Make the following checks invalid for validation profile:

1. PO_PRODUCT_ID INVALID
2. PO PRODUCT_ID_MISSING

The issue with this solution is that you effectively increase the risk of POs for stock materials  successfully transferring to/processing in SNC even if those materials are not maintained in SNC for that vendor

Using a dummy product code in SNC

1. Create a dummy material code in SNC
2. Change mapping to PI to replace blank material field in the PO with this dummy material code while transferring the PO to SNC

Change Profiles and Approval Profiles

Change Profiles:

If SNC does not allow the supplier logged in to go into change mode in the Purchase Order it means no Change Profile has been assigned to that vendor.

Change profiles are assigned here: SAP Supply Network Collaboration –> Supply Network Collaboration –> Purchase Order –> Current Settings –> Assign Change Profiles for Purchase and Replenishment Order Items

A change profile can be assigned for a combination of Customer & Supplier. It can be assigned for a Customer alone – thereby making it applicable for all suppliers.

While defining a Change profile ( SAP Supply Network Collaboration –> Supply Network Collaboration –> Purchase Order –> Current Settings –> Create Change Profiles for Purchase and Replenishment Order Items) – you basically define whether the profile has Display only access or not for the following parameters:

• Order Document Type
• Distribution Status
• Distribution Status for Changes
• Item Status

Approval Profiles

Approval Profiles define the rules for manual or automatic approval requirement for a customer/ supplier or product.

Approval Profiles are created to define the rule for:

• Approve Confirmations Automatically or Manually
• Approve Components for Subcontracting scenario – Approve Deviation Manually/ Approve Automatically/ Approve New component Manually
• Rule for MPN Confirmations
• Rule for Price Confirmation

These profiles are assigned to a Customer, Supplier, Product or any combination of these

Vendor Hierarchy in SNC

Assigning a single business partner (BP) to multiple Locations can be used to replicate the “multiple vendor ship from points to a single Invoicing party” relationship