supplier enablement

8/11/2019 Supplier Enablement

http://slidepdf.com/reader/full/supplier-enablement 1/22

Supp l ie r Enab lement Us i ngSup p l ie r Por t al 6 .0 – Repo r t in g

Re leas e 500 A D D O N . S R M_

B W

C O N F I G



28.09.2004

Supplier Enablement Using Supplier Portal 6.0 – Reporting 2

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice. These materials are provided by SAP

AG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.



28.09.2004


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of

information at a glance. For more information, see Help on Help → General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,

and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Exampl e t ext Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



28.09.2004


Supplier Enablement Using Supplier Portal 6.0 – Reporting .................................................... 5

Documentation Landscape for SAP Solutions and Business Scenarios............................... 7

SAP Notes.............................................................................................................................. 9

Business Customizing............................................................................................................ 9

Preparation of the Operational System............................................................................ 10

Activation of DataSources ............................................................................................ 10

Preparing the Activation of DataSources.................................................................. 10

Installing DataSources .............................................................................................. 11

Configuration of SAP Business Information Warehouse ................................................. 12

Defining Source Systems and Connecting SAP BW to OLTP Systems ...................... 13

Transferring Global Settings......................................................................................... 14

Installing Business Content (Reporting Side)............................................................... 14

Installing Business Content for Supplier Reporting...................................................... 15

Enabling Web Reporting............................................................................................... 16

Generating a Profile for the Supplier Role.................................................................... 16

Data Load......................................................................................................................... 17

Maintaining System IDs................................................................................................ 17

Setting Up and Scheduling the Profile Generation Process ............................................ 18

Preparing the Assignment of the BW Supplier Portal User to a Business Partner ID.. 18

Preparing BW to Receive Authorization Data from Supplier Portal.............................. 19

Preparing BW to Generate the Supplier Portal Authorization ...................................... 20

Generating Authorization Profiles Using a Process Chain ........................................... 21



28.09.2004


Supplier Enablement Using Supplier Portal 6.0 –Reporting

Business ScenarioSupplier Enablement is a key functional area of mySAP Supplier Relationship Management(SRM). It uses Supplier Portal to drive supplier participation and increase responsiveness byenabling suppliers of all sizes to process orders, generate invoices and update specifications.

Reporting for Supplier Enablement includes reporting on purchase orders, confirmations,invoices and supplier consignment stocks originating in one of the following systems:

• SRM Server

• R/3 Materials Management

Reporting for Supplier Enablement uses the existing Business Content for SRM. It analyzesdata originating in SRM and/or Materials Management and provides suppliers with their own

analytic view on this data.

You can report on the following data depending on your backend system ( SRM Server and/orR/3 Materials Management):Purchaseorder history (SRMServer and/or Materials Management)Currentdelivery transactions(SRMServer and/or Materials Management)Contracts(SRMServer and/or MaterialsManagement)Vendor Evaluation (SRMServer and/orBW Myself )Consignmentstocks(MaterialsManagement)

For more information, see the BI Content documentation in the SAP Help Portal

at help.sap.com under SAP NetWeaver → Information Integration → BIContent.

This business scenario configuration guide applies to the following components:

Business Scenario mySAP.com application component with minimumrelease

Reporting for SupplierPortal

SAP Business Information Warehouse 3.5 SP 03

SAP BI Content 3.5.2 Add-On SP01

SRM Server 5.0 (optional)

Materials Management 3.1I (optional)

SAP Enterprise Portal 6.0 (Business Package SupplierPortal)

Use

This business scenario configuration guide contains all the steps required to implement thisbusiness scenario. The guide specifies the sequence of the configuration activities and theirdependencies.

It includes information about the following topics:

• Preparation of the Operational System [Seite 10]

DataSource activation and replication in SRM and Materials Management, seeInstalling DataSources [Seite 11].

• Configuration of SAP Business Information Warehouse [Seite 12]

Defining Source Systems and Connecting SAP BW to OLTP Systems [Extern]

Transferring Global Settings [Seite 14]

Installation of Business Content (Reporting Side) [Seite 14]



28.09.2004


Enabling of Web Reporting [Seite 16]

Generating a Profile for the Supplier Role [Seite 16]

Data Load [Seite 17]

Maintaining System IDs [Extern]

Setting Up and Scheduling the Profile Generation Process [Seite 18]

For more information about the prerequisites for the installation of SAP Business Information

Warehouse, see SAP Service Marketplace at service.sap.com/ibc → mySAP Business

Intelligence.

For more information about the prerequisites for the installation of SAP Enterprise Buyer , see

SAP Service Marketplace at service.sap.com/ibc → mySAP Supplier Relationship

Management.

For more information about the prerequisites for the installation of SAP Supplier Portal, seethe iViewstudio at www.iviewstudio.com ; search for Business Package for Supplier

Collaboration.

Target GroupThis Configuration Guide is intended to be used by both Basis and Application consultants.

Before starting to work with this guide, consultants must have completed all therelevant training classes.

Process Description

You have to set up the connection between SAP BW and Supplier Portal and define various

settings in the SRM Server and/or Materials Management system.More specifically, this means:

• You define the connections between SAP BW and SRM Server and/or between SAPBW and R/3 Materials Management for loading data.

• You load data from SRM Server into Business Information Warehouse (SAP BW) todisplay data on Supplier Portal. If you have integrated R/3 Materials Management (MM)with Supplier Portal you load data from MM into SAP BW.

• You upload authorization data from Supplier Portal into BW to access the supplier viewon BW reporting from Supplier Portal.

The following figure illustrates the connections between the systems:



28.09.2004


Supplier Portal

BW

SRM MM

Supplier

authorization data

Only access to

display reports

Transaction data

and master data

This guide describes the following:

1. How to set up mySAP SRM and Materials Management in order to use Reporting for Supplier Portal.

2. How to configure the Business Information Warehouse system and BI Content Add-On to receive authorization data and to enable reporting.

In this documentation, we do not distinguish between SAP Business InformationWarehouse and BI Content but use SAP BW meaning both.

Documentation Landscape for SAP Solutions andBusiness Scenarios

Purpose

This documentation gives you an overview of the major sources of information available toyou on SAP solutions and business scenarios. Always use the current documents in yourimplementation.

Current documents

Document Quick Link on the SAP Service Marketplace(service.sap.com )

Master Guide, Installation and Upgrade Guides instguides

ibc

Business-Scenario Configuration Guide ibc

Implementation Guide (IMG) Note: This is in the SAP System, not in SAPService Marketplace



28.09.2004


Business Scenario Description ibc

SAP Library helpportal with all releases of a SAP

component

Note: Available in the SAP System under Help

→ SAP Library

The following information supplements the individual documents:

Current supplementary information

Information Quick Link on the SAP Service Marketplace(service.sap.com )

SAP notes notes to the note search

instguides listed by installation and upgrade

guide

Technical infrastructure (for example hardware

sizing, platforms, network security)

ti

Features

The following documents are available for a SAP solution.

Master Guide, Installation and Upgrade Guides

These documents describe how you install or upgrade the system landscape required by abusiness scenario. The central initial access document for each SAP solution is the MasterGuide. It lists the SAP application components and third-party applications required by eachbusiness scenario, and refers to their installation and upgrade guides. These are componentinstallation guides, business scenario upgrade guides and component upgrade guides.

Business-Scenario Configuration GuideThis document describes the settings you use to configure the SAP application componentsand third-party applications required for a business scenario. It contains information specificto business scenarios for the particular IMG activity. It does not reiterate the IMGdocumentation but makes reference to particular IMG texts.

Implementation Guide (IMG)

This tool adjusts SAP systems to customer requirements. The IMG contains the IMG activitiesfor all SAP components, and general documentation. The structure is component oriented,without reference to a business scenario. The Business-Scenario Configuration Guideestablishes the link between the IMG and the various business scenarios.

Business Scenario DescriptionThis document describes how a business scenario runs once all components have beeninstalled and configured. All the business processes of a business scenario are representedgraphically in the component view, which illustrates the process steps of each SAPcomponent.

SAP Library

This contains the entire documentation of SAP components and business scenarios. TheBusiness Scenario description is part of the SAP Library.



28.09.2004


SAP Notes

Use

Before you start to configure this business scenario, consult the following SAP Notes. This

summary only contains central SAP Notes, to give you an initial overview.

Central SAP Notes for Reporting for Supplier Portal

Support Package SAP Note Title of SAP Note

150315 BW Authorizations forRemote User in BW andOLTP

161570 User ALEREMOTE in theBW: Dialog user or system

179602 BW Source SystemConnection

187479 Assigning several sourcesystems to the same ID

397208 BW: Authorizations for HRdata extraction

528435 Content transfer containsunexpected objects

To get a comprehensive and up-to-date overview of the SAP Notes about abusiness scenario and its mySAP.com application components, use the note

search function under service.sap.com/notes in the SAP ServiceMarketplace.

Business Customizing

Purpose

This section contains information about the customizing settings in each system. Businesscustomizing adjusts the company-neutral delivered functionality to the specific requirementsof the company.

This involves, e.g.:

• Organizational Unit Customizing

• Master Data Customizing

• Process Customizing

Procedure

Perform the steps in these guidelines in the sequence in which they appear.



28.09.2004


Preparation of the Operational System

Purpose

In the operational system (transactional system, OLTP system) all data and transactions are

created that are later passed to SAP Business Information Warehouse (SAP BW) foranalysis. You have to prepare the operational system to send the correct data to SAP BW.

Process Flow

Perform the steps in these guidelines in the sequence in which they appear.

Activation of DataSources

Preparing the Activation of DataSources

UseBusiness Content includes the meta models that hold the data and the reports for yourscenario. In the transactional system (SRM Server and Materials Management), DataSourcesdefine the structures and the data that are provided for reporting.There is also one DataSource in the SAP BW system. This receives the data extracted fromSupplier Portal using XML format.You must activate these DataSources.

Procedure...

1. Create a background user in your system (for example, ALEREMOTE) with at leastthese profiles:

a. S_BI-WX_RFC (Business Information Warehouse: RFC users in extraction)

b. P_PLAN_ALL (to extract master data for 0ORGUNIT – organizational unit).

For more information on:

Creating ALEREMOTE as an interactive user or Common ProgrammingInterface – Communication (CPIC) user, see SAP Note 161570.

BW authorizations for remote users, see SAP Note 150315.

Authorizations for HR data extraction, see SAP Note 397208.

2. Create permissions for repository changes and cross-client customizing. In transactionSM30, table T000 (cross-client object changes) you can permit the repository changesand cross-client customizing for your SRM Server, Materials Management and BW client.

3. Transfer the application component hierarchy using transaction SBIW or RSA9.



28.09.2004


Installing DataSources

Use

Reports on Supplier Portal analyze data from SRM Server (A) and/or Materials Management,

the R/3 logistic system (B). Authorization values extracted from Supplier Portal (C) filter thevisibility of reported data for individual suppliers.

A. To load transaction and master data from Supplier Relationship Management into theBW system, you have to activate the relevant DataSources in the SRM Serversystem.

B. To load transaction and master data from Materials Management into the BW system,you have to activate the relevant DataSources in the logistic system.

C. To extract authorization data from Supplier Portal into the BW system, you have toactivate the corresponding DataSource in the BW system.

Prerequisites

A. The SRM Server client has been maintained.

System changes are permitted in the SRM Server system.

B. The logistic client has been maintained.

System changes are permitted in the logistic system.

C. The BW client has been maintained.

System changes are permitted in the BW system.

Procedure

A. Installing DataSources in SRM Server .

1. In transaction SBIW, choose Business Content Datasources →Transfer BusinessContent Datasources. Alternatively, you may use transaction RSA5. Theprocedure is the same.

2. Select and activate the relevant DataSources assigned to the followingapplication components:

• 0SRM-IO

• 0PI_BASIS → 0CA_PR

• 0PI_BASIS → 0CA_BP

• PI_BASIS → 0CA_GD → 0CA_GD-IO for master data

• 0SRM_EBP

• 0SRM_CTR for transaction data

If you also use Vendor Evaluation in SRM, activate the following DataSources:

• 0SRM_VEGUID_ATTR ( Attributes for Vendor Evaluation) for transactiondata

• all DataSources of application component 0PI_BASIS → 0CA_SUR(WebSurvey master data and transactional data)

If you use Vendor Evaluation in BW, you have to activate the DataSources listedin the Configuration Guide for Vendor Evaluation.



28.09.2004


B. Installing DataSources in the logistic system (MM)...


2. Select and activate the relevant DataSources assigned to the applicationcomponents MM-IO and LO-IO for master data and MM for transaction data.

C. Installing DataSources in the BW system...


2. Select and activate DataSource 0SRM_SUPO_AUTH_1 which is assigned to the

application component BW → QUEUE for transaction data.

4.

Configuration of SAP Business InformationWarehouse

Purpose

SAP Business Information Warehouse allows you to analyze data from operative SAP applications as well as all other business applications and external data sources, such asdatabases, online services, and the Internet. SAP Business Information Warehouse providesflexible reporting and analysis tools for analyses and decision-making support in yourenterprise.

Prerequisites

You have installed BI 3.5.2 Content Add-On. For installation information, see the installationand upgrade guides for mySAP Business Intelligence at service.sap.com.

Process Flow

BI Content includes the meta models that hold the data and the reports for your scenario.Since customers can extend, modify, or just use the delivered structures as they stand, BIContent has to be actively installed.

To do this, you have to perform the following steps:......

1. Define your source systems in SAP BW

2. Transfer global settings to SAP BW

3. Install BI Content

4. Enable Web reporting

5. Generate role profile for supplier role

6. Load data and maintain system Ids

7. Set and schedule the profile generation process

All these steps are explained in more detail in the following sections.



28.09.2004


Defining Source Systems and Connecting SAP BWto OLTP Systems

Use

Source systems are the systems in which the original data is created. Data is uploaded fromthe source system into SAP BW. The connections to these systems have to be created inSAP BW.

Procedure...

1. Create a background user in SAP BW (BWREMOTE, for example) with at least theprofile S_BI-WHM_RFC (Business Information Warehouse: RFC users in SAP BW).

2. Assign profile S_USER_ALL to the BW background user.

3. Create a background user in the operational system (ALEREMOTE, for example) withat least the following profiles:

a. S_BI-WHM_RFC (Business Information Warehouse: RFC users in extraction)

b. P_PLAN_ALL (to extract master data for 0ORGUNIT – organizational unit)

For information on creating ALEREMOTE as interactive user or CommonProgramming Interface – Communication (CPIC) user, see SAP note 161570.

For information on BW authorizations for remote users, see SAP note 150315.

For information on authorizations for HR data extraction, see SAP note 397208.

4. Define the logical system that you want to extract data from. For more information, see

the Implementation Guide (IMG) for Business Information Warehouse → Links to

Other Systems → General Connection Settings → Define Logical System.

5. Define the RFC connections for your logical systems in transaction SM59.

6. Use transaction RSA1. Choose Modeling → Source Systems.

7. Choose Create in the context menu.

8. If you choose Automatic Creation, the DataSources are created automatically. Fortroubleshooting information, see SAP note 179602.

9. To create a two-character ID, use transaction RSA1. Choose Tools → Assing SourceSystem to Source System ID.

This two-character ID is used to distinguish between identical master data IDs inthe source systems. For example, if purchaser 1 sends a purchase order (PO)referring to a product 1000, and purchaser 2 (in a different purchasing system)sends a purchase order (PO) referring to his product 1000 – a different one -these different products can be distinguished by adding the two-character ID ofeach purchasing system to the key of the product identifier. If two sourcesystems have homogenized master data (such as product IDs, productcategories and supplier IDs), you may use the same two-character ID for bothsource systems. However, we recommend that you create a new two-characterID for every source system. Refer to SAP note 187479 for further information onthat topic.



28.09.2004


Transferring Global Settings

UseGlobal settings include the calendar settings and units of measurement, and can be used in

the reports. If you do not maintain these settings, the reports will still work. However, units ofmeasure and dates may not appear the way you might expect them to.

Procedure

The procedure you follow depends on your specific business process:

• In many cases, BW extracts data from other source systems directly. In such cases,you can transfer the global settings from these systems. In the Administrator

Workbench in the SAP BW system (transaction RSA1), choose Modeling → SourceSystems. Select your source system and then choose Transfer Global Settings in thecontext menu.

• If you use fiscal year variants, you can transfer these from your FI system. Alternatively, you can maintain the fiscal year variant manually in the Implementation

Guide for SAP BW by choosing Business Information Warehouse → General BW

Settings → Maintain fiscal year variant.

Installing Business Content (Reporting Side)

Use

This section shows you how to install Business Content using the Administrator Workbench.

PrerequisitesYou have set up the SAP BW system and activated the DataSources in thesource systems.

Procedure

1. Open the Administrator Workbench (transaction RSA1).

2. Choose Source Systems from the tree on the left.

3. Right-click the BW system and choose Replicate datasources

4. Withdraw the permission for repository changes and cross-client Customizing in tableT000 in your transactional system, using transaction SM30. You had permitted such

changes in order to install the DataSources and replicate them.5. Install the Business Content as shown below.

Menu path in BW system Transaction code

Administrator Workbench→ Business

Content → Installing Business Content

RSOR

We recommend that you select the content roles and activate In data flowbefore. Make sure that there is a check mark behind your transactional



28.09.2004


system in the source system icon (Shi f t F7). This is necessary to activate

the transfer routines.

Installing Business Content for Supplier Reporting

Use...

1. Activate the following content roles choosing the option In Data Flow Before and After :

BW Role Descript ion and Remarks

SAP_BW_SRM_SUPPLIER

SAP_BW_SRM_ACT_SUPPLIER

SAP_BW_SRM_VARIOUS_ITEMS

Supplier

Supplier - Activation

SRM Object Collector - Not for End Users

The role SAP_BW_SRM_VARIOUS_ITEMS contains Web templates that areshipped for technical reasons. This role is not intended for assignment to a useror a user group.

When you activate a selected role, all BW objects (InfoObjects, InfoObjectCatalogues,ODS Objects, InfoCubes, update rules, InfoSources, transfer rules, Queries,Workbooks, and Web templates) belonging to this role are also activated.

For more information, see the BW documentation in the SAP Help Portal athttp://help.sap.com under Administrator Workbench→ Business Content → InstallingBusiness Content.

This collection collects a lot of BW Business Content objects. For moreinformation, see SAP Note 528435 - Content transfer contains unexpectedobjects.

2. Activate the following ODS object, choosing the option In Data Flow Before:

BW ODS Object Descript ion and Remarks

0SRSA_DS1 Supplier Authorization

3. Activate the following InfoSet choosing the option In Data Flow Before and After :

BW InfoSet Descript ion and Remarks

0SRSA_IS1 Relation SUS Vendor to Generic Vendor

4. You must also activate the standard definitions of report/report interfaces (RRI) that are

provided in BI Content. Activate the following objects of object type report/reportinterface, choosing the option Only Necessary Objects. Select the following objects inthe RRI Query Receiver per long description:



28.09.2004


BW RRI Query Receiver Descript ion and Remarks

0BBP_PO_SP_Q003 SUS: Contract History

0BBP_INV_SP_Q002 SUS EBP: Overview of Incoming Payments

0BBP_DS1_SP_Q003 SUS: Open Invoices

0BBP_DS1_SP_Q002 SUS: Open Deliveries

0BBP_DS1_SP_Q001 SUS: Purchase Order History

0BBP_C01_SP_Q002 SUS: Procurement Values for Contracts

0BBP_C01_SP_Q001 SUS: Procurement Values

0SR_VE_C1_SUS_Q001 SUS: Vendor Evaluation

0IC_C03_Q0019 SUS: Consignment Stocks

Enabling Web Reporting

Use

You need to maintain the Web Applications Server entry in the SAP BW system.

Prerequisites

You have maintained the SAP BW client.

Procedure

Refer to the guide How to... Customize BW 3.0 after an Upgrade from 2.0B/2.1C. This guide

is available in SAPNet, Quick Link BW → Service&Implementation → How To Guides → Guide 3.0.

The settings required for BW 3.0B or higher Web Applications are available in

the IMG: SAP Reference IMG → BW Customizing Implementation Guide →

Business Information Warehouse → Reporting-Relevant Settings → Web-Based Settings.

Navigation

Menu Path Transaction Code

SAP Reference IMG/BW CustomizingImplementation Guide BusinessInformation Warehouse Reporting-Relevant Settings Web-Based Settings

SPRO

Generating a Profi le for the Supplier Role

Use

To get the authorization to access the BW queries for supplier reporting, you have to generatea profile for the activated role SAP_BWC_SRM_SUPPLIER in SAP BW.



28.09.2004


Prerequisites

You have activated the role SAP_BW_SRM_SUPPLIER in SAP BW.

Procedure...

1. Use transaction PFCG in the BW system. Enter the role SAP_BW_SRM_SUPPLIER. 2. Click on tab page Authorization.

3. Under Information about Authorization Profile, click on Propose Profile Name.

4. Under Maintain Authorization Data and Generate Profiles, click on Change Authorization Data.

5. On the screen Change Role: Authorization, click on Generate to generate a new profile.Use the Back button and save the role.

Data Load

Purpose

Before you load data into the BW system from SRM Server or from the MM system, you haveto maintain the system Ids in SAP BW.

Maintaining System IDs

UseThe system name and the system ID enable SAP BW reporting to uniquely identify objects.Therefore, you have to maintain these system names and the system IDs in SAP BW.

ProcedureFor Supplier Portal Reporting, you must connect your SRM Server and/or Materials Management system to SAP BW as described in Defining Source Systems and ConnectingSAP BW to OLTP Systems [Extern] and maintain its system ID using the AdministratorWorkbench (transaction code RSA1).

To maintain system IDs, you have to perform the following steps in SAP BW:...


2. Choose Assignment of Source System to Source System ID from the Tools menu.

3. Enter the two-digit ID for your operational system.

Master data may also carry system IDs. To support reporting on different kinds of systems(SRM Server or Materials Management), products, materials, product categories, materialgroups, business partners and vendors include system IDs. These refer to the originalsystems the data was replicated from when SRM Server or Materials Management was setup. Usually, these are the R/3 backend systems where the original material group wascreated and replicated into SRM Server . The logical systems and the system IDs are alreadypublished in SAP BW, if these systems are connected to SAP BW as well. If this is not thecase, perform the following steps:...


2. Choose Assignment of Source System to Source System ID from the Tools menu.

3. Create a new entry for the logical system of the backend system.

4. Enter the two-character ID for your operational system.



28.09.2004


We recommend that you create a unique entry for every logical system of yourlandscape and enter a two-character ID for it.

Setting Up and Scheduling the Profile GenerationProcess

Use

The following sections describe the steps that are necessary to set up and schedule theprofile generation process:

• Preparing the assignment of the Supplier Portal user to a Business Partner ID

• Preparing BW to receive authorization data from Supplier Portal

• Preparing SAP BW to generate the Supplier Portal authorization

• Generating authorization profiles using a process chain

Prerequisites

• The ALEREMOTE user has the profile S_USER_ALL.

• Transaction data has been loaded into ODS object 0BBP_PO.

• To be able to use the SAP BW Web reports for Supplier Portal, you must load thetransaction and master data into the relevant InfoProviders (0BBP_PO, 0BBP_CON,0BBP_INV, 0BBP_DS1, 0BBP_C01 and 0IC_C03).

If you use SRM Vendor Evaluation, you have to load data into 0SR_VE and0SR_VE_C1.

Preparing the Assignment of the BW SupplierPortal User to a Business Partner ID

Use

When a new user is created in Supplier Portal, it is automatically created in SAP BW, too.

At the same time, an internal table (SRM_USER_SUPBPID) is filled automatically. The tablecontains the assignment between the automatically created SAP BW user and thecorresponding Business Partner ID of the supplier company.

ProcedureMakesu...



28.09.2004


1. Make sure that the BAdI SMUM_USR_CREATE_POST has been transported into yourSAP BW system and has been activated. This BAdI is required for the automaticcreation of a BW user.

Menu Path in the BW System Transaction Code

Business Add-Ins: Initial Definition

Maintenance Screen

SE18

2. Make sure that the implementation RSSBR_SMUM_CRM_SUS for the BAdISMUM_USR_CREATE_POST is activated in your SAP BW system. To activate it, usetransaction SE19, enter RSSBR_SMUM_CRM_SUS and click on Change. Then choose

Activate. This implementation is necessary for the assignment of the SAP BW user to abusiness partner in the internal table.

Menu Path in the BW System Transaction Code

Business Add-Ins: Initial ImplementationMaintenance Screen

SE19

3. Make sure that the table SMUM_BSAPP is maintained correctly. Set Application Name (APPL_NAME) to BBP_SRM (“EBP for SRM”) and Business Service ID to the valuemaintained in UME.

The value of Application Name is identical to the one in implementationRSSBR_SMUM_CRM_SUS.

Preparing BW to Receive Authorization Data fromSupplier Portal

Use

For BW to receive the authorization data from Supplier Portal, you must first enable the SOAPWSDL service in BW. This service allows Supplier Portal to access BW using the HTTPSOAP protocol. Since the data is extracted to the delta queue in BW, you must initialize thedelta queue.

Prerequisites

You have activated the DataSource 0SRM_SUPO_AUTH_1 in SAP BW.

Procedure...

Preparing the delta queue in the SAP BW system

1. In transaction RSA1, choose Modelling → InfoSources.

2. Click the InfoSource 0SR_SUPPLIER_AUTH_1 with the secondary mouse button,choose Assign DataSource and select SAP BW Myself System as the source system.

3. Create a new InfoPackage. Set the update mode to Initialize Delta Process and selectthe Initialize without Data Transfer checkbox. Then start the schedule.

4. After the delta queue initialization has successfully run, call transaction RSA7 for BW

Delta Queue Maintenance. DataSource 0SRM_SUPO_AUTH_1 should be listed in theview.



28.09.2004


Activating service SOAP WSDL in BW

Supplier Portal uses an XML formatted file to extract authorization profile data into BW.To support this type of extraction you have to enable the SOAP WSDL service in theSAP BW system.

5. In transaction SICF Http Service Hierarchy Maintenance, choose SAP → BC and

activate the SOAP service and all the subservices (RFC, WSDL, WSDL11).

6. Go to SAP → BW and activate the SML service and the SOAP subservice.

Preparing BW to Generate the Supplier Portal Authorization

Use

To ensure that Supplier Portal users can only access their own data in SAP BW you must

define the authorization values for each SAP BW user.

This is done by a scheduled process (see Generating Authorization Profiles Using a ProcessChain [Seite 21]). You have to perform the following steps in SAP BW before you can defineand schedule this process.

ProcedureSet...

1. Set InfoObject 0SR_SUSVD to Authorization relevant.

a. In transaction RSD1, open the characteristic 0SR_SUSVD in edit mode.

b. Click on the Business Explorer tab page and select Authorization relevant.

2. Create an authorization object and assign it to InfoObject 0SRM_SUSVD.

a. In transaction RSSM, choose Authorization Object → Object.

b. Create a new authorization object ZSUSVD.

c. Select the InfoObject 0SR_SUSVD from the Authorization Relevant IObjects list.

d. Assign it to the authorization object.

3. Assign InfoProvider 0SRSA_IS1 to the authorization object.

a. In transaction RSSM, choose Authorization Object → Check for InfoCubes.

b. Edit the authorization object ZSUSVD.

c. For the InfoProvider 0SRSA_IS1, select Switched On.

4. Assign the authorization profiles S_BW_RFC and S_USER_ALL to the admin user whoschedules the process chain.

a. In transaction SU01, click on the Profiles tab page.

b. Assign the values S_BW_RFC and S_USER_ALL.

c. Save the user.

5. Define the source system IDs and the system classes.

To load the authorization-relevant Supplier Portal data, you have to define the sourcesystem IDs and system classes of the backend systems connected to Supplier Portal.

a. In transaction SE16, enter table RSSOURSYSTEM.

b. For each backend system, enter the two-digit system ID under SOURSYSID andEBP or R/3 under SR_SYCLASS.



28.09.2004


Generating Authorization Profiles Using a ProcessChain

Procedure...

1. Create an InfoPackage.

To load the authorization-relevant data from Supplier Portal into the authorization ODSobject (0SRSA_DS1) in SAP BW, you must create a new InfoPackage for theInfoSource 0SR_SUPPLIER_AUTH_1.

a. In transaction RSA1, choose InfoSources in the side menu and find InfoSource0SR_SUPPL_AUTH_1 .

b. Create a new InfoPackage Supplier Data Delta for this InfoSource and theMySelf SAP BW System.

c. Choose Delta-Upload for the InfoPackage.

d. Save the InfoPackage.

2. Define a variant for the program RSSB_GENERATE_AUTHORIZATIONS.

a. In transaction SE38, enter RSSB_GENERATE_AUTHORIZATIONS, select Variants under Subobjects, and click on Change.

b. Enter a variant name and click on Create.

c. Define the variant parameters. For the parameter Value, enter 0SRSA_DS1.

d. Save the program variant.

3. Define a process chain.

a. In transaction RSA1, choose Edit → Process Chains.

b. Create a new process chain.

Start Process

You are prompted to enter a start process. Create a new process variant.Optionally, you can define a schedule for the generating process. Choose DirectScheduling and click on change selections.

Info Package

i. Click on the Data targets icon.

ii. Select the Supplier Data Delta InfoPackage you created for InfoSource0SR_SUPPLIER_AUTH_1 and move it to the process maintenancescreen using drag and drop.

iii. Connect the InfoPackage item with the start process item in themaintenance screen.

To connect two processes, click on the variant name (bottom line of the item

box) of one process item and drag it onto another process item.



28.09.2004

Execution of the program RSSB_GENERATE_AUTHORIZATIONS

iv. Choose Process types → General Services.

v. Select ABAP Program and move it to the process maintenance screenusing drag and drop.

vi. Create a new process variant.

vii. Under Program to call, use the input help to select theRSSB_GENERATE_AUTHORIZATIONS program with the programvariant you defined.

viii. Connect the program item with the ODSO Data item.

4. Activate the process chain.

5. Start the process schedule by clicking on Activate and Schedule.

To monitor the profile generation, use transaction SLG1.

supplier enablement

Documents