fas srm documentationv5

IBM Business Consulting Services

1 (64) Author: Frerk Hopf June 2005 © Copyright IBM Corporation 2005

Implementation FAS SAP SRM e-procurement Implementation Document Testsystem (QA) and Productive System (PRD)



Table of Contents

1 Introduction and Overview ........................................ 5

2 URLs ........................................................................ 5

3 Login Data ................................................................ 6

4 Publishing Templates ............................................... 6

5 Component System .................................................. 8

6 RFC Destionations ................................................... 9

6.1 RFC Destination in EBP...................................................................... 10

6.1.1 RFC for EBP System ................................................................... 11

6.1.2 RFC for Backend System............................................................. 12

6.2 RFC in Backend.................................................................................. 14

7 Logical System Settings ......................................... 15

7.1 Logical System in EBP........................................................................ 15

7.2 Logical System in R/3 ......................................................................... 17

7.3 Assign Client to logical System in EBP ............................................... 19

8 Maintain Distribution Model .................................... 20

8.1 Distribution the Model ......................................................................... 23

8.2 Generate Partner Profiles in Backend................................................. 23

9 ALE for FI/CO in Backend ...................................... 24

9.1 Define Process Code “IV01” and “CO01” in Backend.......................... 24

9.2 Characteristics of inbound function modules ....................................... 25

9.3 Maintain inbound process code........................................................... 26

9.4 Maintain Partner Profile Manually ....................................................... 29

10 Define Backend System in EBP.............................. 30

11 Define Backend System for Product Category........ 32

12 Jobs........................................................................ 33

12.1 Set Control Parameter for Cleaner .................................................. 33

12.2 Schedule bbp_get_status_2 ............................................................ 33



12.3 Schedule Reorganization jobs (Backend) ........................................ 34

13 Pricing .................................................................... 35

14 SAP EBP mail notification....................................... 35

15 Roles ...................................................................... 39

16 Maintain Organizational Units................................. 41

16.1 Create root organizational unit......................................................... 41

16.2 Attributes Maintained....................................................................... 42

16.3 Create users.................................................................................... 44

17 Number Ranges ..................................................... 46

17.1 Number Ranges in EBP .................................................................. 46

17.2 Number Ranges for Transaction Types ........................................... 46

17.3 Configure Number Ranges in Backend System............................... 47

17.3.1 Requisition................................................................................... 47

17.3.2 Purchase Order ........................................................................... 48

18 Workflow................................................................. 49

18.1 Maintain Standard Settings for SAP Business Workflow.................. 49

18.2 Activate Event Linkage .................................................................... 49

18.3 Defining Starting Conditions ............................................................ 51

18.4 Important Transaction in the area of workflows................................ 52

19 Tax Calculation....................................................... 52

20 Payment Conditions ............................................... 53

21 Define Objects to be created Acc. to Purch. Group & Categorie ID ................................................................. 54

22 Define Transaction Types....................................... 54

23 Master Data Replication ......................................... 55

23.1 Required Customizing in the Backend............................................. 56

CRMPAROLTP.......................................................................................... 56

23.2 Units of Measurement ..................................................................... 56

23.3 Required Customizing in EBP ......................................................... 57

23.3.1 Switching CRM off ....................................................................... 57

23.3.2 Output format of product ID.......................................................... 57

23.3.3 Logical systems & Flow trace (table SMOFPARSFA) .................. 57



23.3.4 Business objects to be replicated................................................. 58

23.3.5 Customizing entries to be replicated ............................................ 58

23.4 Initial Replication ............................................................................. 59

23.4.1 Replication of Customizing........................................................... 59

23.5 Vendor Master Data Take Over....................................................... 60

23.5.1 Adopt Customizing Data ............................................................. 61

23.5.2 Adopt Vendor Master Records..................................................... 61

Appendix: Remove Special Request Link ..................... 64



1 Introduction and Overview

This implementation guide covers the customizing steps and values for FAS EBP Test system (EBP QA) and FAS EBP Productive system (EBP PRD).

SAP SRM is running in Classic Scenario. No invoicing and goods receiving is done within the system.

FAS will use one punch-out catalog (DATAPAC) and one internal catalog (Requisite).

Important: Screenshots are from QA System AND Productive System.

2 URLs

System URL

EBP QA http://sapits.fasoffice.com:90/scripts/wgate/bbpstart/!

EBP PRD http://sapitspwg.fasoffice.com:91/scripts/wgate/bbpstart/!

BugsEye QA http://10.1.11.32/bugseyeqa/login.htm

BugsEye PRD http://10.1.11.38/bugseyeprd/login.htm

eMerge QA http://10.1.11.32/emergeqa/login.htm

eMerge PRD http://10.1.11.35/emergeprd/login.htm



3 Login Data

System Client User Password

R/3 Backend Productive

400 ibmsrm welcome

EBP Productive 400 ibmsrm welcome

BugsEye Productive

eMerge Productive

standard user (administrator, author, guest)

(administrator, author, guest)

R/3 Backend QA 100 Ibmsrm welcome

EBP QA 100 Ibmsrm welcome

BugsEye QA

eMerge QA

standard user (administrator, author, guest)

(administrator, author, guest)

4 Publishing Templates

This is used to published all web files from the component system to the ITS server.

TCode Input

SE38 W3_PUBLISH_SERVICES

Prerequisites:

Start the publishing by pressing F8.



On the following page select all entries and press the publish button.



5 Component System

TCode Input

SM30 TWPURLSVR

QA Parameter QA Input

Web Server SAPITS.FASOFFICE.COM:90

Web protocol HTTP

GUI start server SAPITS.FASOFFICE.COM:90

GUI start protocol HTTP

KW Web Server SAPITS.FASOFFICE.COM:90

KW Web protocol HTTP

PRD Parameter PRD Input

Web Server SAPITSPWG.FASOFFICE.COM:91

Web protocol HTTP

GUI start server SAPITSPWG.FASOFFICE.COM:91

GUI start protocol HTTP

KW Web Server SAPITSPWG.FASOFFICE.COM:91

KW Web protocol HTTP



6 RFC Destionations

The following configuration is needed to establish communication between the core R/3 System and the Enterprise Buyer component system. This is needed to replicate master data and to transfer the data between the shopping cart and backend procurement documents.

Attention: It is very important, that RFC destinations are named the same as the logical systems!



6.1 RFC Destination in EBP

TCode Input

SM59 Create R/3 Connection



6.1.1 RFC for EBP System

QA Parameter Input

RFC Destination EBQ_100

Connection type 3

Description EBQ_100

PRD Parameter Input

RFC Destination LOG_PRD400

Connection type 3

Description LOG_PRD400



6.1.2 RFC for Backend System

QA Parameter Input

RFC Destination LOG400

Connection type 3

Description LOG400

Target host Sapserv1.fasoffice.com

System Number 00

Client 100

User SAPRFC

Password welcome

PRD Parameter Input

RFC Destination LOG_PRD400

Connection type 3

Description LOG_PRD400

Target host Sapserv1.fasoffice.com

System Number 00

Client 400

User SAPRFC

Password welcome



6.2 RFC in Backend

Create RFC destinations in the R/3 backend system accordingly.



7 Logical System Settings

7.1 Logical System in EBP

TCode Input

SALE ALE Menu

BD54 Logical Systems

QA: Create Entries for the both logical systems EBQ_100 and LOG400

PRD: Create Entries for the both logical systems EBP_400 and LOG_PRD400



7.2 Logical System in R/3

TCode Input

SALE ALE Menu

BD54 Logical Systems



QA: Create Entries for the both logical systems EBQ_100 and LOG400

PRD: Create Entries for the both logical systems EBP_400 and LOG_PRD400



7.3 Assign Client to logical System in EBP

IMG: Enterprise Buyer professional edition -> Technical Basic Settings -> Assign RFC Destinations

Create an entry in the client assignment table to a logical system. In the detail screen maintain the logical system created before.



8 Maintain Distribution Model

The applications that are communicating with each other in your distributed systems are specified in the distribution model. The distribution model consists of separate model views where you can define system-wide message flows.

IMG: Enterprise Buyer professional edition ->Technical Basic Settings ->ALE Settings (Logical System) ->Distribution ALE -> Modeling and Implementing Business Processes -> Maintain

Distribution Model and Distribute Views Alternatively, select transaction <BD64> and switch to ‘change mode’.

TCode Input

BD64

In change modus create first a new model view.

Select the just created view and add the following message types:

Message Type Backend System

Goods receipt (mat.doc.) MBGMCR

Goods receipt (acc.doc.) ACC_GOODS_MOVEMENT

Procurement Card ACLPAY

Invoice (CO) BBPCO

Invoice BBPIV



Use the following Parameters for each message type

QA Parameter Value

Model View B2B

Sender EBQ_100 (Local EBP System)

Receiver LOG400 (Backend System)

PRD Parameter Value

Model View B2B

Sender EBP_400 (Local EBP System)

Receiver LOG_PRD400 (Backend System)

After creating all message types the partner profiles have to be generated. Select the model view, and go via menu: Environment � Generate partner profiles. Maintain backend as Partner system, and IDOC Version 3. Choose Transfer IDOC immediately and Trigger immediately for demo and test system. For productive system, it is recommended to use Collect Idocs and transfer and Trigger by background program. Then execute!



On the next screen the generated profiles are listed. Everything should be on ok (green). The profiles can be regenerated anytime.



8.1 Distribution the Model

Return to the distribution model overview and click once upon the model name. Choose Edit � Model view � Distribute

8.2 Generate Partner Profiles in Backend

TCode Input

BD64

Check in BD64 if the Distribution Model was created according to the one which was maintained in EBP. Click upon the model and Environment � Generate Partner Profiles. Execute



9 ALE for FI/CO in Backend

9.1 Define Process Code “IV01” and “CO01” in Backend

TCode Input

WE57

Maintain if not existent: For invoicing and commitment create:

Save entries and create new entry again. For commitment posting



Save entries

9.2 Characteristics of inbound function modules

TCode Input

BD51

If the following entries do not exist create new entries and maintain.



Save

9.3 Maintain inbound process code

TCode Input

WE42

Save. You will automatically be led into the details screen. Maintain the following fields:



Save. Maintain for the code IV01:

Save.



If the following entries do not exist, create new entries and maintain:

Save



9.4 Maintain Partner Profile Manually

TCode Input

WE20

The following entries should have been generated automatically from the distribution model. If not, you can maintain values manually. Please refer to the cookbook!



10 Define Backend System in EBP

Navigate to the following menu entry:

QA System:

EBQ_100 EBP Component, set local

LOG400 Enterprise Backend

PRD System:

EBP_400 EBP Component, set local

LOG_PRD400 Enterprise Backend



You must also indicate here whether FI data will be validated, and if so, whether this validation takes place in the backend or local system. In this case, validation takes in backend place.



11 Define Backend System for Product Category

Here you specify the backend system that documents are to be posted in, depending on the product category.

Supplier Relationship Management � Technical Basis Settings � Define Backend System for Product Category



12 Jobs

12.1 Set Control Parameter for Cleaner

The requirement request can only be processed further in the backend system after the corresponding documents have been created there. The spooler transfers the shopping cart data to the backend system. The cleaner is a report that checks whether all data has been transferred correctly to the backend system and if so it will delete obsolete table entries in EBP and maintain the number of the created documents.

Supplier Relationship Management � Technical Basis Settings � Set Control Parameters

To start the cleanjob, execute report START_CLEANER in SA38. This report schedules the job clean_reqreq_up in the time interval you entered in the control parameter in customizing. Stop the cleanjob with a report called STOP_CLEANER.

12.2 Schedule bbp_get_status_2

TCode Input

SM36



The program bbp_get_status_2 retrieves new information from the backend system, such as the purchase order number after conversion from the purchase requisition. The program has to be scheduled at least as a daily job in EBP. For demonstration purposes, schedule it every five minutes to ensure up-to-date information.

1. Start transation 38 2. Create job as Enter bbp_get_status_2 3. Create step 4. Set the job user defined in chapter above as responsible 5. Enter the program name bbp_get_status_2 6. Save you entries 7. Schedule job: Choose start condition 8. Click on immediate, flag “Periodic job”, and choose period values.

12.3 Schedule Reorganization jobs (Backend)

There are number of jobs that must periodically run in a live R/3 installation. Select transaction SM36 and choose standard jobs.



13 Pricing

IMG --> Supplier Relationship Management --> SRM Server --> Business Add-Ins for SRM Server (BAdIs) --> Pricing --> Switch On Simplified Pricing (Classic Scenario)

see also oss note 673372

14 SAP EBP mail notification

TCode Input

SCOT



Activate SMTP and add SMTP connections.



TCode Input

RZ10 Add new Parameter (Port=SMTP,Port=25)

Edit Profile: Default

Mark Extended maintenance and change.



TCode Input

SICF

Activate SAPconnect (left mouse-button -> activate



15 Roles

Tcode Input

PFCG

Always use composite Roles which are built up from different single roles. By using them you will avoid having the same menu entry several times in you browser launch pad.

You must regenerate the authorization for each role that you intend to use. This ensures that the profiles belonging to these roles are assigned to all of the required authorizations.

Roles assigned to users are:

ZFAS_SAP_BBP_STAL_SECRETARY (for HO Buyers)

ZFAS_SAP_BBP_STAL_MANAGER (for Manager)

ZFAS_SAP_BBP_STAL_EMPLOYEE (for virtuell HO Buyer- buy on behalf of))

Select the name of the role to be generated

Choose Display

Choose Authorizations

Choose Display Authorization Data

Choose Generate



16 Maintain Organizational Units

16.1 Create root organizational unit

TCode Input

PPOCA_BBP Create Root Organization

PPOMA_BBP Maintain Organizational Plan

PPOSA_BBP Display Organizational Plan

Use this transaction to create only root organizations. Once created, use PPOMA_BBP for additional configuration of sub-departments! For merely displaying the Organizational Plan, use transaction PPOSA_BBP.

Every organizational unit must have an address!



16.2 Attributes Maintained

Object Attribute Value Default

Root ACS QA System: LOG400

PRD System: LOG_PRD400

BSA QA System: LOG400\ECPO

PRD System: LOG_PRD400\ECPO

BWA QA System: LOG400\101

PRD System: LOG_PRD400\101

CAT DATAPAC

CAT REQ

CUR EUR X

EXT_ITS http://sapits.fasoffice.com:81/scripts/wgate/

FORWARD_WI X

ITS_DEST QA System: http://sapits.fasoffice.com:81/scripts/wgate/

PRD System: http://sapitspwg.fasoffice.com:91/scripts/wgate/

KNT AS

KNT CC X

KNT OR

SYS QA System: EBQ_100


X

VENDOR_ACS QA System: LOG400




VENDOR_SYS QA System: LOG400


FAS Company

COMPANY QA System: Company Code FAS, LOG400 Backend

PRD System: Company Code FAS, LOG-PRD400 Backend

BUK QA System: LOG400\FAS

PRD System: LOG_PRD400\FAS

X

FAS HO

CNT QA System: LOG400\FS012

PRD System: LOG_PRD400\FS012

Choose one as default

CNT QA System: LOG400\FS024

PRD System: LOG_PRD400\FS024


CNT QA System: LOG400\PL168

PRD System: LOG_PRD400\PL168


ANR QA System: LOG400\AT005

PRD System: LOG_PRD400\AT005


Requestor EXAMPLE: USHO_DONEGAL

(buy on behalf of). Important: no ”blank” between “US” AND “HO”.

FAS div Plants

CNT QA System: LOG400\PL168

PRD System: LOG_PRD400\PL168


ANR QA System: LOG400\AT005

PRD System: LOG_PRD400\AT005


FASPU PURCH_ORG Entries are coming from top



level

Purchasing Group

Extended Attributes

Product Categories: “*” for product category

SRC. System: R/3 Backend system

Locations: Plnt Number Backend

PURCH_GRP 004, LOG400 Backend

RESP_PRCAT 06* - 9*, LOG400 Backend

RESP_PGRP 50000611

USER LEVEL

Role ZFAS_SAP_BBP_STAL_SECRETARY

SLAPPROVER USDORE_M

Important: no “blanks”

16.3 Create users

TCode Input

SU01

First create an initial administrator user ID using transaction SU01. Assign profile SAP_ALL and user role SAP_BBP_STAL_ADMINISTRATOR. This user should only be used for user administration. Users created this way can never be used to create or approve shopping carts!

Web users can now be created using this administrator user ID. To create new web users, logon to the web using the administration user previously created. In the browser, select Manager User Data � Create User



17 Number Ranges

17.1 Number Ranges in EBP

Supplier Relationship Management � SRM Server � Cross Application Settings � Number Ranges � Define Number Ranges for Shopping Carts and Backend Documents

The interval number entered for shopping carts must exactly match that specified in the Int.No column in IMG activity Define Transaction Type. You must also populate the number range for internal purchase orders if these are to be used.

17.2 Number Ranges for Transaction Types

If goods receipts and invoice is done via the EBP, maintain type CONF and the corresponding number range.

Supplier Relationship Management � SRM Server � Cross Application Settings � Number Ranges � Define Number Range for Local Confirmation of Services and Goods Receipts



Supplier Relationship Management � SRM Server � Cross Application Settings � Number Ranges � Define Number Range for Local Invoices

17.3 Configure Number Ranges in Backend System

17.3.1 Requisition

IMG: Materials Management � Purchasing � Purchase Requisition � Define Number Ranges

No From number To number Current number Ext

RQ 4000000000 4009999999 x

IMG: Materials Management � Purchasing � Purchase Requisition � Define Document Types

1. Select type NB and copy 2. Overwrite NB with “EC” and Nr.mg.ext. with “RQ” and press ENTER 3. Choose copy all 4. Save

Type Doc. Type description Item Nr. Int.as Nr.mg.ext Field sel.

EC EC Pur Req 10 01 RQ NBB



17.3.2 Purchase Order

IMG: Materials Management � Purchasing � Purchase Order � Define Number Ranges

No From number To number Current number Ext

PO 3000000000 3009999999 x

IMG: Materials Management � Purchasing � Purchase Order � Define Document Types

5. Select type NB and copy 6. Overwrite NB with “EC” and Nr.mg.ext. with “PO” and press ENTER 7. Choose copy all 8. Save

Type Doc. Type description Item Nr. Int.as Nr.mg.ext Field sel.

EC EC Pur Order 10 01 PO NBF



18 Workflow FAS will use the following workflows:

- Shopping cart under 500 Euro -> no approval required

- Shopping cart above 500 Euro -> one step approval with SL Approver

18.1 Maintain Standard Settings for SAP Business Workflow

TCode Input

SWU3

Chose generate to perform the automatic workflow customizing. The system will automatically maintain a minimum of required data. If all configuration is correct, and the workflow have been successfully tested, the screen should show only green jacks.

18.2 Activate Event Linkage

TCode Input

OCCU

You have to activate the different workflows you are going to use. These can be found in different parts of the tree in customizing.

Supplier Relationship Management � SRM Server � Cross Application Settings � SAP Business Workflow � Perform Task Specific Customizing

Open Tree SRM � SRM-EBP � SRM-EBP-WFL and double-click on Assign Agents



Task Assignment

TS1000

Activate event linkage for the following workflows:

Workflow Description

WS10000031 Two step approval of shopping cart

WS10000060 Workflow without approval shopping cart

WS10000129 One step approval of shopping cart

WS10000192 Approve new user workflow

WS10000209 Bidder or vendor registration

WS10000214 Triggers the deletion of objects

WS10000215 Resubmission of an Item by Administrator

WS10000223 Forgotten Password, Approve

WS10400010 Goods Receipt Workflow without Approval

WS10400016 Invoice Workflow without Approval

WS14000030 Vendor one step Approval

WS14000043 Null level approval of vendor

WS14000075 Workflow without approval for purchase Order

WS14000080 Workflow without approval for contract

WS79000002 One step approval for bid

Source: SAP Cookbook



18.3 Defining Starting Conditions

Supplier Relationship Management � SRM Server � Cross Application Settings � SAP Business Workflow � Define Conditions for Starting Workflows

Enter in Change mode. Select the Starting Condition you like to change by double clicking it. Here you can edit the conditions to you needs. Once the criteria have been put, press ENTER. If the light in front of the Starting Condition is red, click on it to activate it, the light should change to green. Save.



18.4 Important Transaction in the area of workflows

TCode Input

PFTC Maintain Tasks

SWU0 Event Simulation

SWEL Event Trace

SWI6

SWO1 Object Builder

19 Tax Calculation

In this section you define the settings for calculating tax, such as defining the tax codes, linking them to product categories and specifying the system in which tax is calculated.

Supplier Relationship Management � SRM Server � Cross-Application Basic Settings � Determine System for Tax Calculation

The delivered setting is shown below, the tax being calculated in the R/3 backend.

Supplier Relationship Management � SRM Server � Application-Specific Basic Settings � Enter Tax Code



Possible tax codes are specified in this table. Ideally they should match those in the backend system. If not the tax codes for the two system muss be corss-referenced. If a tax code is marked as default, this is the value that will be proposed during invoicing. The tax category field is only relevant where you have specified that taxes are calculated in an external system.

20 Payment Conditions

Supplier Relationship Management � SRM Server � Application-Specific Basic Settings � Create Payment Conditions

With this setting you define the rules that the Enterprise Buyer system uses automatically determine the payment terms. These are proposed in the header data by the system when creating purchase orders or invoice. None are delivered as standard but they can be replicated from the backend system, see Master Data Replication from Backend.



21 Define Objects to be created Acc. to Purch. Group & Categorie ID

Supplier Relationship Management � SRM Server � Cross-Application Basis Settings � Define Objects in Backend System (Purch Reqs, Reservations, Purch Orders)

In this step you determine which type of document will be created for each combination of purchasing group, product category and backend system.

22 Define Transaction Types

Supplier Relationship Management � SRM Server � Cross-Application Basis Settings � Define Transaction Types



23 Master Data Replication

TCode Remark

R3AC1 Filter for Business Objects

R3AC3 Filter for Customizing Objects

R3AC5 Filter for Conditions Object

R3AM1 Monitor Objects

SM58 Transactional RFC

R3AS Start initial Download

SMQ2 QRFC Monitor (Inbound Queue)

SMQ1 QRFC Monitor (Outbound Queue)

SLG1 System Log

The Middelware is the part of the software responsible for the replication of master data. On EBP it is called ‘Adapter’ and on backend side it is called ‘Plug-In’. The middelware will generate function modules in the backend according to the filters you define.



23.1 Required Customizing in the Backend

CRMPAROLTP

TCode Input

SM30 CRMPAROLTP

Adjust following values:

23.2 Units of Measurement

TCode Input

CUNI

The dimensions, ISO-codes and Units of measurement have to be identical in the Backend and in the EBP component. Every unit of measurement that is going to be used in the catalogue has to be defined as an ISO-code in the EBP component. The ISO-code will be assigned to a unit of measurement in the EBP. The EBP component will only display those units if measurement on the browser which have the indicator 'Commercial meas.

To automatically adjust the ISO codes form Backend start the transaction and choose ISO codes. In the menu you find Utilites � Adjust. Select the backend system form which you want to replicate ISO codes and press the green jack. The system will then display the difference between the two systems. Flag values to be updated or go via menu: Edit � Select � Select all. Choose Adjust and then All. Go back and Save.



23.3 Required Customizing in EBP

23.3.1 Switching CRM off

Supplier Relation Management � SRM Server � Master Data � Products� Deactivate / Reactivate CRM-specific Data in Enterprise Buyer

Flag ‘EBP without CRM’ and choose execute.

You will get a report with all tables that have been deactivated (tables to activate CRM can be switched on at any later time again).

23.3.2 Output format of product ID

Supplier Relation Management � SRM Server � Master Data � Products� Define output format and storage form of product IDs

Product ID length: 18 (mandatory!)

23.3.3 Logical systems & Flow trace (table SMOFPARSFA)

TCode Input

R3AC6



The flow trace is for later error tracing and monitoring. Check whether you have the following entries (if they don’t exist maintain the lines):

Key Paramname Value

CRMGENERAL LOG_LEVEL T

DEVSYSTEM DEVSYSTEM X

FLOW FLOWTRACE_ACTIVE X (needed for error trace)

R3A_COMMON CRM_DEFAULT_DESTINATION LOG400

R3A_COMMON CRM_DESTINATION_SFA_SERVER

EBP_210

R3A_COMMON CRM_CONVERT_ENDIAN ‘ ‘

23.3.4 Business objects to be replicated

TCode Input

R3AC6

<R3AC1> or easy access menu: Middleware � R/3 Adapter � Initial Download � Object Management � Business Objects

Press .

23.3.5 Customizing entries to be replicated

<R3AC3> or easy access menu: Middleware � R/3 Adapter � Initial Download � Object Management � Customizing Objects

Press . Set all lines but DNL_CUST_PROD0, DNL_CUST_PROD1, DNL_CUST_PROD2 and DNL_CUST_PROD3 to inactive.



Condition objects to be replicated. <R3AC5> or easy access menu: Middleware � R/3 Adapter � Initial Download � Object Management � Condition Objects

Press Set all lines to inactive.

Choose and save your entries.

23.4 Initial Replication

23.4.1 Replication of Customizing

The customizing that is required for a later product replication is replicated as described below. Changes in customizing are not replicated automatically. A new replication has to be started in this case.

<R3AS> or easy access menu: Middleware � R/3 Adapter � Initial Download � Object Management � Start

Object class CUSTOMIZING, Download Object:

DNL_CUST_PROD0 (Storage form of material numbers in sending system)

DNL_CUST_PROD1 (Material type, material group – only material groups with text – and product hierarchy... , table SMOT023T contains the data that was taken over)

DNL_CUST_PROD2 (Valuation area currencies)

DNL_CUST_PROD3



Click .

TIP:

If you want to see in which ‘Download Object’ a table is replicated go via <SE16>

Table: SMOFTABLES, press

Maintain the name of the table in the R3 in the field ‘R3TABNAME’ and press

.

You will see the OBJNAME (=Download Object)

23.5 Vendor Master Data Take Over

Vendors are needed in the BBP and the backend. They can be replicated from the backend with the transactions described below.

TIP

The following prerequisites must be met for vendor master take over:

• Backend system: The vendor must be assigned to a purchasing organization (vendors that only have accounting view cannot be replicated)

• SAP B2B Procurement system: The organizational plan must be set up. In the organizational plan:

- There must be an organizational unit that the vendor can be assigned to

- Each backend purchasing organization has to be related to an organizational unit in BBP

- ‘Object permitted for scenario’ in the tab attributes <PPOMA_CRM> must be on green.



23.5.1 Adopt Customizing Data

BBP: <BBPGETVC>

Maintain Backend-'System': BACKEND and choose

TIP

Customizingdata that has been replicated can be found under <SE16> tables BBP_T0* (terms of payment, payment methods and blocking reasons for automatic payment, document types, special G/L indicators), BBP_T6* (foreign trade and mode of transport) and BBP_T8*.

23.5.2 Adopt Vendor Master Records

BBP: <BBPGETVD>

• Maintain backend system: BACKEND • Maintain object ID: 5XXXXXXX (ID from the org unit in the org structure

(<PPOMA_CRM>), under which the vendor(s) shall be created – i.e. 'Vendor root')

• If you want to keep the vendor number from the backend: flag ‘Transfer only R/3 numbers’

• System will show all values that can be replicated. With 'Display list' you see the corresponding vendors that are not replicated, or the purchasing organisations that are not maintained in the BBP. Only vendors whom the correct purchasing org has been maintained will be replicated.

• Start replication with

With transaction <CRM_OM_BP_INTEGRATE> you can check, whether all

traffic lights are on green. Otherwise select line and choose .

System will automatically create dummy entries in the <PPOMA_CRM> with the name YYYYMMDD0000X. Up to 100 suppliers will be filled into one dummy if more than 100 suppliers are replicated at once.



TIP

Display the ‘take over’ log

• <SLG1> (Function module: APPL_LOG_DISPLAY) • Maintain object: BBPGETVD, check the date and time in the fields of the time

restriction and click on .

Lights should be on green. Double click on the lines to get additional information about incorrect transfers.

Logfiles can be deleted (i.e. after various replications) via transaction <SLG2>

Note: You cannot delete vendors that have been taken over.

An update of vendor master data is done via <BBPUPDVD>. Handling similar to BBPGETVD.

Catalogue Connection

Supplier Relation Management � SRM Server � Master Data � Define External Web Service



Product Hierarchies



Appendix: Remove Special Request Link

Transaction: Se80

Internet service bbpsc02

� Display Object list

choose SAPLBBP_SC_UI_ITS 110

Removed Code

��

�� !��

��""�"#��$%&$��''��"��"��"��

��"��#��(��"��

��

��"��#��

��"��

��!�

��"�(��!�

��)��*��(��++��+��,�*��,�*��-��-+��.��+�"��$!��

��-�"!��

��"��"��#��!��

��//01�(��+��/21��03456��37)3�2.��+��,� �"��/21��03456��37)3�2.8948:3��

�� ;�(��<��8 4�"��=�/21��03456��37)3�2.8948:3�=,=//0>��=,==,==,==�?��/21��03456��37)3�2.��+��(��=�=?��?��=�=?�!�/21��03456��37)3�2.��+��-�!��!�

��-�"!�

��

��-�!�

��"��

To reverse change enter code where you find the following line in the html page:

��5/@,��"+,�AB.AA.%$$C��(��!�

Save and publish!