Kontakt

Ansicht
Dokumentation

Supplier Self-Services (SUS) ( RELNSP_35_GENEROVERVIEW )

Supplier Self-Services (SUS) ( RELNSP_35_GENEROVERVIEW )

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Supplier Self-Services (SUS)

Use

Background/Focus

Supplier Self-Services

  • Integrates smaller/medium-sized service providers and vendors into the procurement, service, and supply process of large purchasing organizations
  • Supports smaller vendors and service providers in procurement of goods and services (automated document flow, user-friendly user interfaces, limited technical requirements for implementation)

Advantages

Purchaser side (purchaser):

  • Increased security
Vendors do not log on to the Enterprise Buyer (EBP) system, but rather to SUS
  • Lower transaction costs
  • Accelerated procurement process
  • Reduced administration expense
Only one user must be created for each vendor.
  • Closer vendor relationship
  • Avoidance of errors through electronic communication

Vendor side (supplier):

  • No separate system required
Functionality is provided via the SUS system, with access via the browser.
  • Reporting
Comprehensive reporting functionality.
  • Cost-effective promotion of own products
Addresses target purchaser group directly (via Home page).

Technical Implementation Scenarios

  • Enterprise Buyer 3.5 (Stand-Alone Scenario)

  • SUS 1.0 (based on CRM 3.0)

  • Communication between EBP and SUS via XML directly via XI infrastructure.

  • EBP-side installation behind the firewall

  • Vendor logs on to the SUS system via the browser

Complete Business Process

This method is used for high-value sales orders and in those cases where there is a greater need for monitoring and evaluation over the entire validity period of the order.

  1. The requirement is generated in EBP either by creating a
  • shopping cart (SC) (manually) or as an external requirement from

  • material requirements planning (MRP), plant maintenance (PM) or project system (PS).

  1. As a result, a purchase order (PO) is created in EBP.
  2. The vendor recieves the PO as a sales order (SO) in the SUS system.
  3. The vendor sends an order confirmation (OR) to the purchaser. The purchaser accepts it or sends an update of the OR.
    This process is repeated if necessary until both parties are agreed on the content of the order.
  4. The vendor generates one or more SES service entry sheets or GR goods receipts in SUS. In the case of blanket purchase orders, he can add items to the confirmation via a catalog. The confirmation is sent to EBP.
  5. As a result, an ERS is created and sent to SUS.

Variations in the Business Process

  • Process without service entry/good receipt (confirmation)
This simplified (and therefore cheaper) variation consists exclusively of purchase orders (PO), sales orders (SO), and invoices (IV) and is used mainly for accelerated sales order processing where the amounts concerned are relatively small. This process is triggered by setting the indicator No confirmation expected in the PO.
  • Process with automatic invoice creation
This variation has as a prerequisite the manual creation of the PO (on the EBP side) and the confirmation (on the SUS side). The IV is generated in EBP via Evaluated Receipt Settlement (ERS) based on the confirmation (CF). This process is triggered by setting the indicator Automatic settlement in the PO.
  • Process with invoice creation only
The IV can be generated completely without either PO, SO, or confirmation. However, a contract must exist which can be entered in the IV either manually or via a catalog.
  • Third party order-processing
This process runs when a vendor cannot fulfill a customer's order himself and therefore passes the order on to an external vendor. After the goods have been delivered or the services provided, the external vendor sends an invoice to the original vendor. This invoice is modified before being passed on to the customer. A charge is added to the original amount for passing on the order.
System view:
The original vendor's system consists of an EBP system and one (or more) SD backend(s). The external vendor uses the SUS system that is linked to EBP.

Target Group

  • Larger purchasing organizations that wish to integrate smaller vendors in their procurement process.
  • Smaller vendors without the appropriate IT infrastruture.
    These vendors need only a Web browser for access to SUS.

Roles

  • Purchase-side
Professional purchaser, employee, technician, manager, project leader, invoice recipient
  • Vendor-side
Service provider, manager, invoicing department

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

Release information:
Supplier Self-Services

SAP Library:
Enterprise Buyer → Integration → Integration of Applications → Supplier Self-Services






General Data in Customer Master   General Material Data  
This documentation is copyright by SAP AG.

Length: 6979 Date: 20240523 Time: 065126     sap01-206 ( 92 ms )