procure 2 pay - donutsdocshare01.docshare.tips/files/24056/240560350.pdfprocure 2 pay: configuration...

SAP ECC 6.00

July 2006

English

Procure 2 Pay

SAP AGNeurottstr. 1669190 WalldorfGermany

Germany Baseline Configuration Guide

SAP Best Practices Building Block Title: Configuration Guide

Copyright

© Copyright 2005 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 be changed without prior notice.

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

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

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 IBM Corporation.

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 are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide 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 for technology 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 and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications 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, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 47


Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

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

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 47


Contents

Procure 2 Pay: Configuration Guide...............................................................................................7

1 Purpose................................................................................................................................... 7

2 Preparation.............................................................................................................................. 7

2.1 Prerequisites.................................................................................................................. 7

2.1.1 Building Blocks..........................................................................................................7

3 Configuration........................................................................................................................... 7

3.1 Technical Basic Settings................................................................................................7

3.1.1 Define RFC User.......................................................................................................7

3.1.2 Define RFC destinations............................................................................................8

3.1.3 Define logical system for SRM..................................................................................9

3.1.4 Maintain Distribution Model and View........................................................................9

3.1.5 Define Backend Systems........................................................................................10

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

3.1.7 Set Control Parameters...........................................................................................11

3.1.8 SLD Cache entry.....................................................................................................12

3.1.9 Table maintenance TWPURLSVR...........................................................................13

3.1.10 Internet Services Publishing....................................................................................13

3.2 Execution of Essential SRM Reports...........................................................................14

3.2.1 Reports Registration................................................................................................14

3.2.2 Report run – COM_HIERARCHY_DELETE_ALL....................................................15

3.2.3 Report run – COM_PRODUCT_DELETE_ALL.......................................................15

3.2.4 Report run - COM_PRODUCT_UPGRADE.............................................................15

3.3 Define External Web Services.....................................................................................16

3.3.1 Define External Catalog...........................................................................................16

3.4 Master Data Synchronization.......................................................................................17

3.4.1 Preparatory Steps for Master Data Synchronization...............................................22

3.4.2 Activate Creation of Postprocessing Orders............................................................22

3.4.3 Registrations of Queues for Background processing..............................................23

3.4.4 Activate Synchronization Options............................................................................24

3.4.5 Activate PPO Requests for Platform Objects in the Dialog......................................25

3.4.6 Define Number Assignment for Direction BP to Vendor...........................................25

3.4.7 Set BP Role Category for Direction BP to Vendor...................................................26

3.4.8 Define Number Assignment for Direction Vendor to BP..........................................26

3.4.9 Define BP Role for Direction Vendor to BP..............................................................27

© SAP AG of 47


3.4.10 Initial replication of customizing comparison: product.............................................28

3.4.11 Initial replication of Material type.............................................................................28

3.4.12 Initial replication of Material group...........................................................................29

3.4.13 Initial replication of Material data.............................................................................29

3.4.14 Initial replication of Vendor data..............................................................................30

3.4.15 Initial replication of Locations/Plant.........................................................................30

3.4.16 Initial replication of Payment terms..........................................................................30

3.5 Organizational Management........................................................................................17

3.5.1 Create root organization object...............................................................................17

3.5.2 Change Organization Plan......................................................................................17

3.5.3 Set up Integration with Organizational Management...............................................20

3.5.4 Match up Organizational Units and persons with Business partners.......................21

3.5.5 Schedule Periodic Comparison...............................................................................21

3.6 Cross-application Basic Settings.................................................................................31

3.6.1 Define Number Ranges for Shopping Carts and follow-on Documents...................31

3.6.2 Define Number Ranges per backend system for follow-on documents...................32

3.6.3 Define Number Range for Local Invoices................................................................32

3.6.4 Define Number Ranges for local confirmations of services and good receipts........33

3.6.5 Define G/L account for Product category and account assignment category..........33

3.6.6 Define system for Tax Calculation...........................................................................34

3.6.7 Enter Tax Code........................................................................................................34

3.6.8 Define objects in the backend system.....................................................................35

3.6.9 Start Application Monitors........................................................................................35

3.7 SAP Business Workflow..............................................................................................36

3.7.1 Maintain prefix numbers..........................................................................................36

3.7.2 Maintain standard setting for SAP Business workflow.............................................36

3.7.3 Set active plan version............................................................................................36

3.7.4 Activate standard tasks...........................................................................................37

3.7.5 Execute Report RHSOBJCH...................................................................................37

3.7.6 Perform Task Specific Customizing.........................................................................38

3.7.7 Define Conditions for Starting Workflows................................................................38

3.8 Periodic Reporting scheduling.....................................................................................39

3.8.1 Create Variant for Report BBP_GET_STATUS_2....................................................39

3.8.2 Schedule Report BBP_GET_STATUS_2.................................................................39

3.8.3 Create Variant for Report CLEAN_REQREQ_UP...................................................40

3.8.4 Schedule Report CLEAN_REQREQ_UP................................................................40

4 Master Data........................................................................................................................... 41

© SAP AG of 47


4.1 HR Personnel Events and Organizational User Creation............................................41

4.1.1 Create Users...........................................................................................................41

4.1.2 Personnel Actions....................................................................................................42

4.1.3 Maintain HR Master Data for Communication.........................................................43

4.2 Create Material Master GIGA_LAPTOP_01................................................................43

4.3 Maintain the Vendor Business Partner........................................................................44

4.4 Create MM Info Record for Catalog Purchasing as Source of Supply.........................45

4.4.1 Create Info Record 1 (UOM: PC) for Catalog Purchasing as Source of Supply......45

4.4.2 Create Info Record 2 (UOM: EA) for Catalog Purchasing as Source of Supply......46

© SAP AG of 47


Procure 2 Pay: Configuration Guide

1 PurposeThis configuration guide provides the information you need to set up the configuration of this building block manually.

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the installation guide of this building block.

2 Preparation

2.1 Prerequisites

2.1.1 Building BlocksBefore you start installing this building block, the installation of the following building blocks must have been completed:

Building Block Description

Layer 0 All Baseline Layer 0 building blocks

Note: To enable this Procure2Pay process, you must also install the SRM add-on package onto the ECC server. For details, please refer to the system installation guide.

3 Configuration

3.1 Technical Basic Settings

3.1.1 Define RFC User

UseThe purpose of this activity is to create a RFC user ID used for SM59 connection and one systemuser to execute spooling job.

Procedure 1. Access the activity using the following navigation option:

Transaction Code SU01

2. Enter a user name RFC_{system name}, for example RFC_RS5

© SAP AG of 47


3. Choose Create.

4. Maintain the first name, last name and password of this user.

5. Choose the Logon data tab page and set the system indicator in the User Type screen area.

6. Choose the Profiles tab page and assign the following objects:

SAP_ALL

SAP_NEW

7. Choose Save (Ctrl+S).

8. Access the activity using the following navigation option:


9. Enter a user name RFC_{system name}, for example EBP_JOB

10. Choose Create.

11. Maintain the first name, last name and password of this user.

12. Choose the Logon data tab page and set the system indicator in the User Type screen area.

13. Choose the Profiles tab page and assign the following objects:

SAP_ALL

SAP_NEW


3.1.2 Define RFC destinations

UseThe purpose of this activity is to define a RFC destination.

Procedure1. Access the activity using one of the following navigation options:

Transaction Code SM59

IMG Menu Supplier Relationship Management SRM Server Technical basic settings Define RFC Destinations

2. Choose Create a RFC Destination

3. Enter the RFC Destination and the Connection Type

RFC Destination {system name}CLNT{client number}

e.g. BSXCLNT100

Connection Type 3 ABAP Connection

The system-name is a three-letter word. This is the second part of the underscore-separated server name.

The client-number is the 3-digit SAP client number.

© SAP AG of 47


4. Choose tab Logon & Security and enter a Client: {client number}, User: RFC_{system name} and Password: initial


6. Choose Back (F3).

3.1.3 Define logical system for SRM

UseThe purpose of this activity is to define the logical systems.

Procedure 1. Access the activity using one of the following navigation options:

Transaction Code SPRO

IMG Menu Supplier Relationship Management SRM Server Technical basic settings ALE Settings (Logical System) Distribution (ALE) Basic settings Logical systems Define logical systems

2. Choose New Entries

3. Enter the Following logical systems

Logical System Name

{system name}CLNT{client number} SAP Best Practices

ONECLNTERP One Client ERP System

ONECLNTSUS One Client SUS System

ONECLNTEBP One Client EBP System



Example: BSXCLNT100

Using the installation assistant, one of the logical system has been created with the name ‘NONE’. You must replace it to your system logical system.



3.1.4 Maintain Distribution Model and View

UseThe purpose of this activity is to define the logical systems.

Procedure

© SAP AG of 47


1. Access the activity using one of the following navigation options:


IMG Menu Supplier Relationship Management SRM Server Technical Basic Settings ALESettings (Logical System) Distribution (ALE) Modelling and Implementing BusinessProcesses Maintain Distribution Model and Distribute Views

2. Switch to Change mode by clicking on the ‘Switch between display and edit mode’ button.

3. Choose Create model view

4. Enter, Short Text: {Building Block ID, e.g. S60}; Technical name: {system name}CLNT{client number} and continue.

5. Select the newly model view node.

6. Choose Add message type

7. Enter, Sender: {system name}CLNT{client number}, Receiver: ONECLNTERP and MessageType: BBPCO

8. Repeat point 5 and 6 changing Message Type: BBPIV and ACLPAY.



3.1.5 Define Backend Systems

UseThe purpose of this activity is to define Backend Systems.



IMG Menu Supplier Relationship Management SRM Server Technical Basic Settings Define Backend Systems


3. Enter following data

Logical system Description

RFC Destination Sys. Type RFC

Local

FIvalid

CiConnent.

SystemLandscape

Directory Name

RFC (Dialog)

{system-name}CLNT {client-number}



LOCAL X X Real time …

SRM_SERVER_{system-name}_{client-number}


ONECLNTEBP One Client EBP


EBP_ONE Real time …

SRM_SERVER_{system-name}_{client-

{system-name}CLNT {client-

© SAP AG of 47


number} number}

ONECLNTERP One Client ERP


ERP_2.0_1C

X Real time …



ONECLNTSUS One Client SUS


SUS_ONE Real time …





3.1.6 Define Backend System for Product Category

UseThe purpose of this activity is to define Backend Systems for Product Category.



IMG Menu Supplier Relationship Management SRM Server Technical Basic Settings Define Backend System for Product Category



Category ID Source System Target System

* {system-name}CLNT{client-number} ONECLNTERP



Example: BSXCLNT100


5. Choose Back (F3)

3.1.7 Set Control Parameters

UseThe purpose of this activity is to set Control Parameters.



© SAP AG of 47


IMG Menu Supplier Relationship Management SRM Server Technical Basic Settings Set Control Parameters



Key control record Configuration key description Value controlrecord

SPOOL_JOB_USER User that executes spool job. EBP_JOB

SPOOL_LEAD_INTERVALL interval by which the retry time incr. 60

SPOOL_MAX_RETRY Max. number of retrys for writing BAPIS

5



3.1.8 SLD Cache entry

Use The purpose of this activity is SLD Cache entry. If you have a Exchange Infrastructure System Landscape Directory, you just need to add a business system (example BS_RS5201) and it should automatically update this entry in the SLD Cache table when you run SLDCHECK transaction.


SAP Menu Tools ABAP Workbench Overview Data Browser

Transaction Code SE16

2. Enter the following data for table name: LCRT_CLNTCACHE

3. Choose Table Contents. If the table is empty, please proceed as below.

4. Choose Create Entries (F5) and create a entry as below:

SRTFD {system-name}{client-number}

AEDAT Current date

BS_KEY_NAME {system-name} _{client-number}

BS_ROLE LOC

BS_CAPTION {system-name} _{client-number}



Example: BSXCLNT100


© SAP AG of 47


3.1.9 Table maintenance TWPURLSVR

Use The purpose of this activity is make entry for web servers for logical systems.

Procedure 1. Access the activity using following navigation option:


2. Enter the following data for view name: TWPURLSVR

3. Choose Maintain

4. Continue (Enter) the Information


6. Type in web server, web protocol, Gui start server, Gui start protocol for logical systems (example) for the 2 logical systems as below:

Logical sys. Web server Webprotocol

GUI start Server GUI startprotocol

{system-name}{CLNT client-number}

e.g. LDCIBSX.WDF.SAP.CORP:50071

HTTPe.g. LDCIBSX.WDF.SAP.CORP:50071

HTTP

ONECLNTEBPe.g. LDCIBSX.WDF.SAP.CORP:50071

HTTPe.g. LDCIBSX.WDF.SAP.CORP:50071

HTTP

You can use transaction SMICM, under menu Goto -> Services (Shift+F1) to find out the

server and port value

7. Protocol entries are typically HTTP

3.1.10 Internet Services Publishing

Use The purpose of this activity is to publish the HTML templates to the Internet Transaction Server (ITS).

Procedure 1. Access the activity using following navigation option:


2. Enter the following data for view name: W3_PUBLISH_SERVICES

3. Choose Execute (F8).

4. On the WAB: Publish Services Chosen, choose Execute (F8).

5. Select the following components by double clicking on it:

Component

© SAP AG of 47


Vendor List

Sourcing

Integration of Catalogs, Partner Directories (OCI, OPI)

Enterprise Buyer

Shopping Cart

Enterprise/Business Partner Management

Invoicing

Workflow

Contract Management

Content Management

Cross-Application Functions

SAP GUI for HTML

6. Adjust the Workbench settings F8 for your publishing.

7. Click Publish (F7).

3.2 Execution of Essential SRM Reports

3.2.1 Reports Registration

ProcedureYou need SAP_ALL authorization and to register the reports that need to be executed.

1. Access the activity using the following navigation option:


2. Enter COMC_PR_TOOL_REG for Table Name.

3. Choose New Entries.

PROGRAM_NAME - Name of the program/report you want to run as below:

COM_HIERARCHY_DELETE_ALL

USER_NAME - User with which you are logged on

EXEC_DATE - Date on which you would like to run this report

4. Click Save (Ctrl+S) for each program entry made.

5. Repeat steps 3 to 4 for the reports below as well:

COM_PRODUCT_DELETE_ALL

COM_PRODUCT_UPGRADE

© SAP AG of 47


3.2.2 Report run – COM_HIERARCHY_DELETE_ALL

UseThe purpose of this activity is to run report COM_HIERARCHY_DELETE_ALL.


SAP Menu Tools ABAP Workbench Development ABAP Editor


2. Enter the following data at program: COM_HIERARCHY_DELETE_ALL

3. Click Execute (F8).

4. Answer the question to delete all hierarchies with YES and Execute.

3.2.3 Report run – COM_PRODUCT_DELETE_ALL

UseThe purpose of this activity is to run report COM_PRODUCT_DELETE_ALL.




2. Enter the following data at program: COM_PRODUCT_DELETE_ALL


4. Answer the question to delete all products with YES, unchecked Simulation – No deletion andExecute.

3.2.4 Report run - COM_PRODUCT_UPGRADE

UseThe purpose of this activity is to run report COMM_PRODUCT_UPGRADE.




2. Enter the following data at program: COM_PRODUCT_UPGRADE


© SAP AG of 47


3.3 Define External Web Services

3.3.1 Define External Catalog

Use The purpose of this activity is to define an external Web Catalog (e.g. Corporate Express) to allowpurchasing of descriptive item directly from an external service provider catalog.



IMG Menu Supplier Relationship Management SRM Server Master Data Define External Web Services (Catalogs, Vendor Lists etc.)

2. Click on the New Entries button.

3. Enter ‘CORPEXPRESS’ as the Web Service ID.

4. Enter ‘CORPORATE EXPRESS Catalog’ as the Description.

5. Select ‘01 Product Catalog’ as the Bus. Type of a WebService.

6. Click Enter.

7. Enter the <vendor for P2P scenario> e.g. C5205 for Germany baseline, BLACKWOODS for Australia Baseline, etc. in the Business Partner field.

If you have personalized the vendor number, please replace it with the personalized

value.

8. Flag the Use Error Log checkbox.

9. Double click on the Standard Call Structure node.

10. Click on the New Entries button.

11. Enter the following line entries:

Seq. Parameter Name Parameter Value Type

10 https://order.corporateexpress.at URL

20/easyorder.oci/isapv1?OCI_VERSION=2.0

URL

30 username SAPOCIDEMO Fixed Value

40 password DEMO777OCI Fixed Value

50 HOOK_URL Return URL

60 ~OkCode ADDI Fixed Value

70 ~target _top Fixed Value

80 ~caller CTLG Fixed Value

12. Click the Save (Ctrl+S) button.

© SAP AG of 47


3.4 Organizational Management

3.4.1 Create root organization object

Use The purpose of this activity is to create the organization root.

Procedure 1. Access the activity using the following navigation options:

Transaction Code SPRO / PPOCA_BBP

IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings Organizational Management Create Organizational Plan

2. Enter the Valid from and Valid to Date

3. Enter your Organization unit name and description, e.g. BPROOT for name and Best Practices Root Organization for description text.

4. Choose Save (Ctrl+S) to save the organizational object.

3.4.2 Change Organization Plan

Use The purpose of this activity is to maintain the organization structure.


Transaction Code SPRO / PPOMA_BBP

IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings Organizational Management Change Organizational Plan

2. Search for newly created root organizational unit.

3. Choose Create and click on Is line supervisor of.

4. Enter the following data in the Basic Data tab.

New org unit New organizational unit

BP01 SAP Best Practices(Company Code)

5. Change the tab to function. Tick company and type in Company code (example BP01) and Company Code (example ONECLNTERP).

6. Click on the created Company Code level and choose Create and click on Is line supervisor of.

7. Enter the following data in the Basic data tab.


BP01_DEPT SAP Best Practices (Department)

© SAP AG of 47


8. Click on the created Company Code level and choose Create and click on Is line supervisor of.



BP01_PROG SAP Best Practices (Purchasing Org)

10. Change the tab to function. Tick Purchasing Organization and type in CorrespondsTo (example BP01) and Company Code (example ONECLNTERP).

11. Click on the created Purchasing Org and choose Create and click on Is line supervisor of.



BP01_PGRP SAP Best Practices (Purchasing Grp)

13. Change the tab to function. Tick Purchasing Group and type in CorrespondsTo (example 001)and Company Code (example ONECLNTERP).

14. Go to SAP Best Practices (Department), right click and create a position. Choose incorporate a position.

New Position ID New Position

Manager Manager

Employee Employee

For the Manager position, please also flag the Head of own organization unit checkbox

under the Basic data tab.

15. For each of the organizational unit objects you have created, click on the Address tab and maintain the complete address data. An example as below:

Address suppl SAP Best Practices

House no/street SAP Best Practices

City SAP Best Practices

Country SAP Best Practices Country Baseline

Postal Code Enter a postal Code

16. Under Attributes tab at the company code level, choose Chg. Attribute and select the specific

attribute as below entry to maintain. Use icon to add more lines when needed.

Attribute Name Attribute Id Attribute Value Default Source System

Account Assignment Category

KNT CC X


KNT FI


KNT GL

Account Assignment KNT NET

© SAP AG of 47


CategoryAccount Assignment Category

KNT OR


KNT WBS


KNT SO

Accounting system for Vendor

VENDOR_ACS

{system name}CLNT{client number}

Catalog ID CAT CORPEXPRESS

Company Code BUK BP01 (example) ONECLNTERP

Cost center CNT 1201 (example) ONECLNTERP

Delivery address ADDR_SHIPT

{select for the address number in table ADRC}

Document Type in R/3 BSA NB (example) ONECLNTERP

Invoice Recipient Address

ADDR_BILLT

{select for the address number in table ADRC}

Local Currency CUR EUR

Movement Type BWA 201 (example) ONECLNTERP

System Alias SYS ONECLNTERP

System Alias for accounting systems

ACS ONECLNTERP

System alias for vendor VENDOR_SYS

ONECLNTERP

User role ROLE SAP_BBP_STAL_EMPLOYEE

Current ITS of User ITS_DEST ITS URL*

*The ITS URL is build up like following definition: [protocol]://[server]:[port]/sap/bc/gui/sap/its/bbpstart/

protocol will usually be httpsserver Hostname of the application server.

This is the first part of the underscore-separated server name.This argument is not case-sensitive.

port Port on which the J2EE server is installed

For example: https://ldcibsx.wdf.sap.corp:44371/sap/bc/gui/sap/its/bbpstart/

You can use transaction SMICM, under menu Goto -> Services (Shift+F1) to find out the server and port value

You must also ensure that the required virtual host and services are activated using the SICF transaction. For details, please refer to the OSS note 517484.

© SAP AG of 47


17. Enter the following under the Extended Attributes tab

18. Select Product Categories radio button,

a. Enter * in the product category field and {system name}CLNT{client number} as the source system.

b. Select product category 01 ‘Material group 1’ and {system name}CLNT{client number} as the source system.

Select the Default checkbox to indicate that 01 material group will always be

used as the default product category if not specify when creating shopping cart in system.

19. Select Locations radio button and make entries for the locations (i.e. Plant) like an example below. You should select the Plant under your defined Company code.

Partner ID Plant Compn Code Description Src. System

0000000112 BP01 BP01 Production Plant One Client ERP

0000000113 BP02 BP01 Distribution Center One Client ERP

0000000114 BP03 BP01 Regional Warehouse One Client ERP

0000000115 BP0X BP0X Inter Company Processing Plant

One Client ERP

20. Select Storage Locations radio button and make entries for the storage locations like an example below: You should select the Storage Location under your defined Plant.

Stor. Loc. Description Src. System

0002 production One Client ERP

0003 finished product One Client ERP

0004 raw material One Client ERP

0005 lean WM&HU One Client ERP

0010 std. warehouse One Client ERP

3.4.3 Set up Integration with Organizational Management

Use The purpose of this activity is to setup integration between HR and SRM organizational structure objects.



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings Organizational Management Integration Business Partner-Organizational Management

© SAP AG of 47


Set Up Integration with Organizational Management

2. Ensure the following entries are made:

Group Sem. Abbr. Value abbr.

HRALX HRAC X

HRALX OADRE X

HRALX OBPON ON

PLOGI PLOGI 01

3. Click Save (Ctrl-S) key if changes are being made.

3.4.4 Match up Organizational Units and persons with Business partners

Use The purpose of this activity is to repair any inconsistency between the Organizational Units and persons with the business partner data.



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings Organizational Management Integration Business Partner-Organizational Management Match Up Organizational Units and Persons with Business Partners

2. Click the Branch from Organizational Unit checkbox.

3. Enter or search for all the organizational units that you would need to perform the matching.

4. Select the Include all Object Types radio button.

5. Flag the Run Attribute Check checkbox.

6. Click Save as Variant (Ctrl+S) button to save the setting into a variant (e.g. ORG-MATCH) first.

7. Click Execute (F8) to run the report now.

8. If any error occurs on any of the organizational roots, select the node and choose the Start Repair button.

3.4.5 Schedule Periodic Comparison

UseThe purpose of this activity is to plan a periodic check and update for business partner addressesfrom organizational units

Procedure

© SAP AG of 47


1. Access the activity using the following navigation options:


IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings Organizational Management Integration Business Partner-Organizational Management Schedule Periodic Comparison

2. Enter a job name (e.g. OM-BP Comparison).

3. Click Enter Key.

4. Enter ABAB program name with HRALXSYNC with the variant (e.g. ORG-MATCH) you created in step 3.5.4.

5. Click Save (Ctrl+S) button.

6. Click Back (F3) button.

7. Click Start condition (F5) button to define the start time and date as you required and ensuring that it is scheduled as a periodic daily job. Click Save (Ctrl-S) button to save the condition.

8. Click Save (Ctrl+S) button again to save the scheduled job.

3.5 Master Data Synchronization

3.5.1 Preparatory Steps for Master Data Synchronization

UseThe purposes of this activity are the Preparatory Steps for Master Data Synchronization



IMG Menu Cross-Application Components Master Data Synchronization Preparatory Steps for Master Data Synchronization

2. Click on the IMG activity documentation to read and follow the activities.

As a developer in the system, you are likely to be granted with all the necessary

authorization objects from the SAP_ALL profile

3.5.2 Activate Creation of Postprocessing Orders

UseThe purpose of this activity is to activate creation of postprocessing orders.

Procedure

© SAP AG of 47




IMG Menu Cross-Application Components General Application Functions Postprocessing Office Business Processes Activate Creation of Postprocessing Orders

2. Enter the following data: AP-MD and press continue


4. Enter the following data:

Business Process Act.

CVI_01 X

CVI_02 X

CVI_03 X

CVI_04 X

PROD_01 X

PROD_02 X

PROD_03 X

PROD_04 X

PROD_05 X

PROD_06 X

PROD_07 X

PROD_11 X

PROD_12 X


3.5.3 Registrations of Queues for Background processing

UseThe purpose of this activity is the Registration of Queues for Background processing.



IMG Menu Cross-Application Components Master Data Synchronization Synchronization Control Preparatory Steps for Synchronization Control

© SAP AG of 47


2. Click on the IMG activity documentation.

3. Click on synchronization processes hyperlink.

4. Enter table/view name MDSV_CTRL_OPT.

5. Choose Display.

6. Copy the first queue name and go back to the IMG activity documentation and select queue processing hyperlink.

7. Choose Registration and type in the first copied queue name and add a * to the end of each queue name for Queue Name field.

8. Repeat steps 3 – 7 until all the queues are registered.

It is also possible to open 2 SAP sessions with one running the SM30 (table

MDSV_CTRL_OPT) and the other running the SMQR transaction to refer and complete the queue registration processes.

3.5.4 Activate Synchronization Options

Use The purpose of this activity is to activate objects for Master Data Synchronization.



IMG Menu Cross-Application Components Master Data Synchronization Synchronization Control Synchronization Control Activate Synchronization Options


3. Enter the following data if the following entries are not in the table:

Source Object Target Object Act. Ind.

BP CUSTOMER X

BP VENDOR X

CUSTOMER BP X

ECCMAT PRODMAT X

ECCMATGRP PRODCAT X

ECCMATTYP PRODCAT X

ECCPINFREC PRODMAT

ECCSERV PRODSERV X

ECCSERVTYP PRODCAT X

PRODMAT ECCMAT X

PRODMAT ECCPINFREC

PRODSERV ECCSERV X

© SAP AG of 47


VENDOR BP X


3.5.5 Activate PPO Requests for Platform Objects in the Dialog

Use The purpose of this activity is to activate objects for Master Data Synchronization.



IMG Menu Cross-Application Components Master Data Synchronization Synchronization Control Synchronization Control Activate PPO Requests for Platform Objects in the Dialog


3. Enter the following data:

Szn. Object PPO Active

PRODMAT X

BP X


3.5.6 Define Number Assignment for Direction BP to Vendor

Use The purpose of this activity is to assign the business partner groupings to the account groups for the vendor master records to ensure that when you process vendors as part of vendor integrationthe system also updates the business partner at the same time. With this assignment you can choose whether the vendor master record is to be created with an account group with internal or external number assignment.



IMG Menu Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner Settings Settings for Vendor Integration Field Assignment for Vendor Integration Assign Keys Define Number Assignment for Direction BP to Vendor

2. Check that the following entries exist in table. If not click on the New Entries (F5) button to create it:

Group Grp. Same No

© SAP AG of 47


0001 KRED

0002 LIEF X

Note: If you are not using the standard setting, you need to make your own assignment

for the Business Partner Grouping and Vendor Account Group.


3.5.7 Set BP Role Category for Direction BP to Vendor

UseThe purpose of this activity is to define which BP role categories enable vendor integration in the direction from the business partner to the vendor. You can determine how the system creates a corresponding vendor in Financial Accounting when you process a business partner.



IMG Menu Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner Settings Settings for Vendor Integration Set BP Role Category for Direction BP to Vendor


Role Cat. Description

BBP000 Vendor

BBP001 Bidder

BBP006 Invoicing Party

FLVN00 Business Partner FI Vendor (FS: BP)

FLVN01 Business Partner Vendor (FS: BP)


3.5.8 Define Number Assignment for Direction Vendor to BP

UseThe purpose of this activity is to assign the business partner groupings to the account groups for the vendor master records to ensure that when you process vendors as part of vendor integrationthe system also updates the business partner at the same time. With this assignment you can choose whether the vendor master record is to be created with an account group with internal or external number assignment.



© SAP AG of 47


IMG Menu Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner Settings Settings for Vendor Integration Field Assignment for Vendor Integration Assign Keys Define Number Assignment for Direction Vendor to BP

2. Check that the following entries exist in table. If not click on the New Entries (F5) button to create it.

Group Grp. Same No

0001 0001

KRED 0001

LIEF 0002 X

If you are not using the standard setting, you need to make your own assignment for the

Vendor Account Group and Business Partner Group.


3.5.9 Define BP Role for Direction Vendor to BP

Use The purpose of this activity is to assign BP roles to the account group for the vendor master record in which the business partner is to be created when processing the vendor.



IMG Menu Cross-Application Components Master Data Synchronization Customer/Vendor Integration Business Partner Settings Settings for Vendor Integration Define BP Role for Direction Vendor to BP


Group BP Role

0001 BBP000

0001 BBP001

0001 BBP006

0001 FLVN00

0001 FLVN01

KRED BBP000

KRED BBP001

KRED BBP006

© SAP AG of 47


KRED FLVN00

KRED FLVN01

LIEF BBP000

LIEF BBP001

LIEF BBP006

LIEF FLVN00

LIEF FLVN01

If you are not using the standard setting, you need to make your own assignment for the

Vendor Account Group and BP Role.


3.5.10 Initial replication of customizing comparison: product

Use The purpose of this activity is the initial replication of customizing for product replication.



IMG Menu Cross-Application Components Master Data Synchronization Synchronization of Mass Data Execute Synchronization Cockpit

2. In the “Customizing Synchronization” window, choose the Report title: Customizing Comparison: Product with the Program Name: MSI_MAPPING_PRODUCT_CUST and double click it.

3. Select both Number-ID Conversion & Message Control checkboxes.

4. Choose Execute (F8).

3.5.11 Initial replication of Material type

Use The purpose of this activity is the initial replication of material type.




© SAP AG of 47


2. In the “Synchronization Process” window, choose for Source Object: Material Type and for

Target Object: Product Category and double click on the entry.

3. Press Start Synchronization (F8).

You can check the replication status by clicking on the 'Monitor' tab and you should see the progress status in green. If this is not the case for whatever reason, please execute transaction SMQ2 (qRFC Monitor - Inbound queue) to check if the queues are indeed held in Ready Status. To release the queue, double-click on the queue name and click on the 'Activate Queue (F6)' iconto release it.

3.5.12 Initial replication of Material group

Use The purpose of this activity is the initial replication of master group.




2. In the “Synchronization Process” window, choose for Source Object: Material Group and for Target Object: Product Category and double click on the entry.



3.5.13 Initial replication of Material data

Use The purpose of this activity is the initial replication of Master data.




2. In the “Synchronization Process” window, choose for Source Object: Material and for Target Object: Product: Material and double click on the entry.

3. In selection criteria, select the material which you would like to replicate:

© SAP AG of 47


Field Name Incl/Excl Option Lower Limit Upper Limit

MaterialI Select specified values

EQ: Equal Single Values

* *



3.5.14 Initial replication of Vendor data

Use The purpose of this activity is the initial replication of Vendor data.




2. In the “Synchronization Process” window choose for Source Object: Vendor and for Target Object: Business Partner and double click on the entry.

3. In selection criteria, select the vendor which you would like to replicate:

Field Name Incl/Excl Option Lower Limit Upper Limit

Vendor I Select specified values

EQ: Equal Single Values

* *


3.5.15 Initial replication of Locations/Plant

Use The purpose of this activity is the initial replication of locations




2. Enter the following data at program: BBP_LOCATIONS_GET_ALL


Run transaction SLG1 to check for any application error during the replication.

© SAP AG of 47


3.5.16 Initial replication of Payment terms

Use The purpose of this activity is the initial replication of payment terms.




2. In the “customizing synchronization” choose program BBP_UPLOAD_PAYMENT_TERMS and double click

3. In the next screen enter data transfer system as ONECLNTERP

4. Execute the program by Pressing (F8).

Run transaction SLG1 to check for any application error during the replication.

3.6 Cross-application Basic Settings

3.6.1 Define Number Ranges for Shopping Carts and follow-on Documents

Use The purpose of this activity is to maintain number ranges for purchasing documents



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings Number Ranges SRM server number ranges Define Number Ranges for Shopping Carts and follow-on Documents

2. Choose change intervals

3. Choose Insert Interval (Shift + F1) and maintain following entries using your required number ranges. An example below:

NO From Number To Number CurrentNumber

Ext Description

(not in the table)

01 0010000000 0019999999 Shopping cart

LO 0020000000 0029999999 Faulty local PO

© SAP AG of 47


PO 4100000000 4199999999 Backend PO

RQ 0090000000 0099999999Backend Purchase requisition

RS 9600000000 9999999999 Backend Reservation

SE 0200000000 0209999999 Backend Service PO

4. Press Enter


If you have make adjustment to the external number ranges for the various MM

documents in backend, you must adapt the number range in SRM accordingly.

3.6.2 Define Number Ranges per backend system for follow-on documents

Use The purpose of this activity is to maintain number ranges for follow on documents



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings Number Ranges SRM server number ranges Define Number Ranges per backend system for follow-on documents

2. Choose New entries (F5) maintain the following entries.

Logical System NumberRange PO

NumberRange PReqs

Number RangeReservation

{system name}CLNT{client number}

Example (ONECLNTERP)

PO RQ RS




3.6.3 Define Number Range for Local Invoices

Use The purpose of this activity is to maintain number ranges for invoices

Procedure

© SAP AG of 47




IMG Menu Supplier Relationship Management SRM server Cross-application Basic Settings Number Ranges SRM server number ranges Define Number Range for Local Invoices


3. Choose Insert Intervall (Shift + F1) and maintain following entries:


Ext Description

(not in the table)

01 1000000000 1999999999 Invoices

4. Press Enter


3.6.4 Define Number Ranges for local confirmations of services and good receipts

Use The purpose of this activity is to maintain number ranges for confirmations



IMG Menu Supplier Relationship Management SRM server Cross-application Basic Settings Number Ranges SRM server number ranges Define Number Range for Local Confirmations of Services and Goods Receipts


3. Choose Insert Interval (Shift + F1) and maintain following entries:


Ext Description

(not in the table)

01 1000000000 1999999999 Proc.Confirmation

4. Press Enter


3.6.5 Define G/L account for Product category and account assignment category

Use The purpose of this activity is to define accounting assignment

© SAP AG of 47




IMG Menu Supplier Relationship Management SRM Server Cross-Application Basic Settings Account Assignment Define G/L account for Product Category and Account Assignment Category



4. Maintain the following entries as an example:

Category id Source System Account AssignmentCategory

G/L account

* {system name}CLNT{client number}

CC 616100




3.6.6 Define system for Tax Calculation

Use The purpose of this activity is to define the system for Tax calculation



IMG Menu Supplier Relationship Management SRM Server Cross-Application Basic Settings Tax Calculation Determine system for Tax calculation

2. Choose the option required.



The default configuration is No Tax Calculation. To change it, please replace it manually.

3.6.7 Enter Tax Code

Use

© SAP AG of 47


The purpose of this activity is to define the tax codes



IMG Menu Supplier Relationship Management SRM Server Cross-Application Basic Settings Tax Calculation Enter Tax code

2. Enter the necessary tax codes which you have used for procurement.



The default configuration is tax code P0 (No Tax). Depending on your system setup, you

must include the other tax codes manually or even to replace the default one.

3.6.8 Define objects in the backend system

Use The purpose of this activity is to define objects in the backend system



IMG Menu Supplier Relationship Management SRM Server Cross-Application Basic Settings Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)


3. Make the following entries (Example)

PurchasingGrp

CategoryId

Source System Int. Proc ExternalProcurement

Purchasing groups you have defined (Example 50000056)

* {system name}CLNT{clientnumber}

Choose Option ‘Always External procurement’

Choose option ‘Purchase order if itemdata complete else purchase req’




© SAP AG of 47


3.6.9 Start Application Monitors

Use The purpose of this activity is to start the application monitor



IMG Menu Supplier Relationship Management SRM Server Cross-Application Basic Settings Start Application Monitors

2. Execute the activity.

3.7 SAP Business Workflow

3.7.1 Maintain prefix numbers

Use The purpose of this activity is to maintain internal number assignment for tasks and workflows



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings SAP Business Workflow Maintain prefix numbers

2. Switch to Change mode.

3. Choose create and maintain the following entries

Prefix Number SAP System Client

3 digit number for example ‘999’

{system name}example ‘BSX’

Client for example ‘100’


4. Save Local.

3.7.2 Maintain standard setting for SAP Business workflow

Use The purpose of this activity is to set all standard settings necessary for the workflow management

Procedure

© SAP AG of 47




IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings SAP Business workflow Maintain Standard Settings for SAP Business Workflow

2. Execute by pressing button icon for Perform automatic workflow customizing on each of the node.

3.7.3 Set active plan version

Use The purpose of this activity is to set all standard settings necessary for the workflow management



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings SAP Business workflow Set active plan version

2. Maintain the following entry if not already maintained.

Group Sem. abbr Value. abbr

PLOGI PLOGI 01


3.7.4 Activate standard tasks

Use The purpose of this activity is to activate the standard tasks



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings SAP Business workflow Activate standard tasks

2. Type in you request and continue.

3. It may be necessary to press continue quite often.

3.7.5 Execute Report RHSOBJCH

Use

© SAP AG of 47


The purpose of this activity is to run report if SOBJ is inconsistency. It is necessary if “Activate standard tasks” is displaying error messages.




2. Enter the following data at program: RHSOBJCH and Execute.

3. Select all of the objects.

4. Perform a reconciliation by choosing List -> Update selection

5. After the object list has been reconciled, table OBJS is consistent

3.7.6 Perform Task Specific Customizing

Use The purpose of this activity is to do the event linkage for different tasks



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings SAP Business workflow Perform task specific customizing

2. Expand the SRM folder.

If the SRM folder does not exist, run the program RS_APPL_REFRESH using the transaction se38.

3. Expand the SRM-EBP folder.

4. Go to SRM-EBP-WFL folder and click on Activate event linkage.

5. Locate the following workflows in the table below and carry out step 6 to 8 for each of them:

Business Object

Trigerringevents

Workflows (tasks / events)belonging to Business object

Event linkage activated

BUS2121 SAVED WS10000060 Active





© SAP AG of 47



6. Click on Detail view.

7. Select Event linkage activated checkbox and click Save data (F5).

8. Choose Continue and go on in the list.

3.7.7 Define Conditions for Starting Workflows

Use The purpose of this activity is to define the workflow starting conditions



IMG Menu Supplier Relationship Management SRM Server Cross-application Basic Settings SAP Business workflow Define conditions for starting workflows

2. Select the business object above. For example BUS2121 EC Requirement Coverage

Request in case of shopping cart. You can search for the objects using the icon.

3. Click on the Change start conditions (F5) button.

4. Activate the start condition for the required workflow for example WS10000060 and WS10000129 in the case for Shopping carts business object. Click on the red dot on the left side of the screen to turn it to green representing activation of the start condition. For other workflow start condition that you do not want to activate, please ensure that the dot remains as red.

5. You can either keep the standard start conditions delivered or change it.

6. Continue with the other Business objects listed in step 3.7.6.

3.8 Periodic Reporting scheduling

3.8.1 Create Variant for Report BBP_GET_STATUS_2

Use The purpose of this activity is to create a variant for report BBP_GET_STATUS_2.

Procedure 1. Access the activity using the following options:

Transaction Code SA38

© SAP AG of 47


2. Type in program name (example BBP_GET_STATUS_2), then Execute (F8).

3. Type in logical system ONECLNTERP.

4. Click on the menu: Goto Variants Save As Variant.

5. Type in Variant Name and Meaning and Save.

3.8.2 Schedule Report BBP_GET_STATUS_2

Use The purpose of this activity is to schedule report BBP_GET_STATUS_2 periodically to update the status of the document created. We create a variant first before scheduling the reports periodically.


SAP Menu Tools CCMS Background Processing Define Job


2. Type in Job Name and choose Start condition.

3. Choose immediate.

4. Tick periodic Job and Period values (F5).

5. Choose other period. Typ in 2 minutes and save and save and save.

6. Choose Define steps (F6) and ABAP program. Typ in Name: BBP_GET_STATUS_2.

7. Select to choose the Variants and then Save (Ctrl+S).

8. Choose Back (F3) and then Save (Ctrl+S).

3.8.3 Create Variant for Report CLEAN_REQREQ_UP

UseThe purpose of this activity is to create a variant for report CLEAN_REQREQ_UP.

Procedure 1. Access the activity using the following options:

Transaction Code SA38

2. Type in program name (example CLEAN_REQREQ_UP), then Execute (F8).

3. Type in logical system ONECLNTERP.

4. Click on the menu: Goto Variants Save As Variant.

5. Type in Variant Name and Meaning and Save.

3.8.4 Schedule Report CLEAN_REQREQ_UP

Use

© SAP AG of 47


The purpose of this activity is to schedule report CLEAN_REQREQ_UP periodically to check whether the documents have been created in the backend. We create a variant first before scheduling the reports periodically.


SAP Menu Tools CCMS Background Processing Define Job


2. Type in Job Name and choose Start condition.

3. Choose immediate.

4. Tick periodic Job and Period values (F5).

5. Choose other period. Typ in 2 minutes and save and save and save.

6. Choose Define steps (F6) and ABAP program. Typ in Name: CLEAN_REQREQ_UP.

7. Select to choose the Variants and then Save (Ctrl+S).

8. Choose Back (F3) and then Save (Ctrl+S).

4 Master Data

4.1 HR Personnel Events and Organizational User Creation

4.1.1 Create Users

UseThe purpose of this activity is to create user ID. In this case for two users: EMPLOYEE and MANAGER.

Procedure


SAP Menu Tools Administration User Maintenance Users


2. On the User Maintenance: Initial screen enter EMPLOYEE in the User field and choose Create.

3. On the Maintain User screen, Address tab make following entries:

Field name Description

Last name Employee

First name BP Demo User

© SAP AG of 47


Function BP Demo User Employee

Department BP Demo User

Company BP Company

4. Choose Enter.

5. On the Logon data tab, enter the initial password initial twice.

6. Save your entries.

7. Repeat step 2 to 6, changing EMPLOYEE for MANAGER. At the end you created 2 new Users.

Now that you have created the user, you can test it by logging on with your initial

password. When you do this, you will be prompted to enter a new password.

8. Go to transaction PFCG to generate the single role assigned within the composite role:

SAP_EC_BBP_EMPLOYEE

SAP_EC_BBP_MANAGER

SAP_EC_BBP_ADMINISTRATOR

9. Assign the following composite roles to the users:

User Roles Profile

Employee SAP_BBP_STAL_EMPLOYEE <Generated Profile>

Manager SAP_BBP_STAL_MANAGER

SAP_BBP_STAL_ADMINISTRATOR

<Generated Profile>

The standard roles have to be activated for assignment

4.1.2 Personnel Actions

UseThe purpose of this activity is to perform a hiring personnel action for the HR user.


SAP Menu Human Resources Personnel Management Administration HR Master Data Personnel Actions

Transaction Code PA40

2. Enter a Personal No. mark the Hiding line (Hiring Action Services) and choose Execute.

© SAP AG of 47


3. Create Actions: Enter starting date, Position (Example Manager), Personal area, Employee

group, Employee subgroup and choose Save and select next record.

4. Complete the fields required in the HR infotypes as prompted on screen. Some of the infotypes are Organizational Assignment, Personnel Data, Addresses, Planned Working Time, Basic Pay, Bank Details, Travel Privileges, Time Sheet Defaults, etc depending on the configuration you have made in system.

5. The most important infotype which you need to take care is the Organizational Assignment which is required for the personnel assignment to the SRM organizational structure. In the Position field, select the organizational object (i.e. Position) you have created earlier in step 3.5.2.

6. For each infotype, please also remember to click Save (Ctrl+S) after entry to save the record.

7. Repeat step 1 to 6 for creating the rest of the personnel action (e.g. EMPLOYEE, etc.)

Use transaction PPOSA_BBP to display the organization structure and you should be

able to see the HR person being assigned each of the position in the organization structure.

4.1.3 Maintain HR Master Data for Communication

UseThe purpose of this activity is to maintain the HR master data for communication in system for thelogon User-ID.

Procedure1. Access the activity using the following navigation option:

Transaction Code PA30

2. Key in employee Personal Number.

3. Enter Infotype: 0105 (Communication), Sty : 0001

4. Click Create (F5).

5. Enter the User-ID (e.g. MANAGER) created in step 4.1.1 in the ID/number field. You may adjust the Start date if required.

6. Choose Save.

7. Repeat step 1 to 6 for assigning the all the created user-id.

4.2 Create Material Master GIGA_LAPTOP_01

UseThe purpose of this activity is to create the material GIGA_LAPTOP_01 (using external number assignment). If you have performed personalization on the master data setup, please remember to replace the default field value with your own value.

Procedure

© SAP AG of 47



SAP Menu Logistics Materials Management Material Master Material Create (General) Immediately

Transaction Code MM01

2. On the Create Material (Initial screen) make following entries.

Material GIGA_LAPTOP_01

Industry sector Plant engine./construction

Material Type Packaging

3. Choose Enter

4. Select View(s): Basic data 1; Basic Data 2; Purchasing; Purchase Order Text; Accounting 1; Accounting 2. For each tab enter as follow.

5. First enter Plant: BP01, choose enter

6. Enter the following in the Basic data 1 tab:

Material: GIGA TravelMate Laptop

Base Unit of Measure: PC

Material Group: YG10110

Division: 01

7. Select the Purchasing tab and enter the following:

Purchasing Group: 001

8. Select the Accounting 1 tab and enter the following:

Price control: V

Moving price: 1000

9. Choose Save (Ctrl+S) to create the material.

4.3 Maintain the Vendor Business Partner

UseThe purpose of this activity is maintained the vendor business partner mapping the logical systemto the vendor code which has been replicated into the SRM server.

Procedure

1. Logon the SRM server using the MANAGER UserID using the web interface.

For the logon, the path will be http://<web server>:<port>/sap/bc/gui/sap/its/bbpstart

(e.g. http:// LDCIBSX.WDF.SAP.CORP:50071/sap/bc/gui/sap/its/bbpstart).

© SAP AG of 47

http://d4atdc00.wdf.sap.corp:55000/sap/bc/gui/sap/its/bbpstart


2. From the menu, select Manage Business Partners.

3. Search for your vendor business partner using the binocular icon beside the field Business Partner Data and click on the Edit button.

4. Select on the Vendor Data tab.

5. Switch to Change mode by clicking on the Display / Change button.

6. Under the section Link to Backend System, enter the mapping of logical system to the vendorcode as an example below:

Logical system Vendor Code

ONECLNTERP C5205

If you have personalized the vendor number, please replace it with the personalized

value.

7. Choose Save.

4.4 Create MM Info Record for Catalog Purchasing as Source of Supply

UseThe purpose of this activity is to create two info records for use during the purchasing of item fromthe external catalog purchasing. Since we are not using contract document for this Procure2Pay scenario setup, the shopping cart will result in a Purchase Requisition (PR) created directly in the R/3 system. See also OSS Note 787045.

We can then use this info. Record to convert the PR into a PO directly.

If you have performed personalization on the master data setup, please remember to replace the default vendor field value with your own value.

4.4.1 Create Info Record 1 (UOM: PC) for Catalog Purchasing as Source of Supply


SAP Menu Logistics Materials Management Purchasing MasterData Info Record Create

Transaction Code ME11

2. Enter the following fields:

Vendor <vendor for P2P scenario> e.g. C5205 for Germany, BLACKWOODS for Australia, etc.

Purchasing Org BP01

Plant BP01

© SAP AG of 47


Info category Standard

3. Choose Enter.

4. Enter the following fields on the General Data tab:

Info Record Description Info. Record for Catalog (UOM : PC)

Material Group 01

Order Unit PC

Sort Term P2P-1

5. Choose Enter.

6. Enter the following fields on the Purch. Org. Data 1 tab:

PI Deliv. Time 1

Purch Group 001

Standard Qty 1

Net Price 1

GR-Bsd IV X

Tax Code V1


If you have personalized the system setup, please replace the purchasing group and tax

code with the personalized value.

4.4.2 Create Info Record 2 (UOM: EA) for Catalog Purchasing as Source of Supply


SAP Menu Logistics Materials Management Purchasing MasterData Info Record Create

Transaction Code ME11

2. Enter the following fields:

Vendor <vendor for P2P scenario> e.g. C5205 for Germany, BLACKWOODS for Australia, etc.

Purchasing Org BP01

Plant BP01

© SAP AG of 47


Info category Standard

3. Choose Enter.

4. Enter the following fields on the General Data tab:

Info Record Description Info. Record for Catalog (UOM : EA)

Material Group 01

Order Unit EA

Sort Term P2P-2

5. Choose Enter.

6. Enter the following fields on the Purch. Org. Data 1 tab:

PI Deliv. Time 1

Purch Group 001

Standard Qty 1

Net Price 1

GR-Bsd IV X

Tax Code V1


If you have personalized the system setup, please replace the purchasing group and tax

code with the personalized value.

© SAP AG of 47