SAP SRM 3.0 SP 11
December 2002
English
General Settings SRM
SAP AG
Neurottstr. 16
69190 Walldorf
GermanyBuilding Block Configuration Guide
DISCLAIMER OF WARRANTIES
SAP Best Practices is being provided to you free of charge. You agree that SAP has made no express warranties to you regarding SAP Best Practices and SAP Best Practices are being provided “as is” without a warranty of any kind. To the fullest extent permissible by law, SAP disclaims all warranties with respect to SAP Best Practices, express or implied including, but not limited to any implied warranties of fitness for a particular purpose, merchantability, and merchantable quality of any third party rights.
LIMITATION OF LIABILITY
To the maximum extent permitted by applicable law, in no event shall SAP or its licensors be liable for any special, incidental, indirect or consequential damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or any other pecuniary loss) arising out of the use of or inability to use SAP Best Practices, even if SAP has been advised of the possibility of such damages. Because some states and jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you.
Copyright
© Copyright 2002 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE® is a registered trademark of ORACLE Corporation.
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,
MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML 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.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP, mySAP.com, 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. All other product and service names mentioned are the trademarks of their respective owners.
Contents
General Settings SRM7
1Preparation7
1.1User Roles7
1.2Connectivity8
2Generation9
2.1Start Application Monitors9
2.2Generate Authorization Profiles9
2.3Generate Middleware10
2.4Initial/Total Generation10
3Configuration SAP R/312
3.1Define Number Ranges for Purchase Requisitions12
3.2Define Document Types for Purchase Requisitions12
3.3Define Number Ranges for Purchase Orders13
3.4Define Document Types for Purchase Orders14
3.5Define Number Ranges for the Service Entry Sheet15
3.6Define Number Ranges for Reservations15
3.7Define Parameters for Download16
3.8Prepare for Replication of Material Master Records17
3.9Prepare for Replication of Vendor Master Records17
4Configuration SAP SRM19
4.1Set Up Basic Configuration19
4.1.1Define Number Range for Business Partner19
4.1.2Define Business Partner Groupings19
4.1.3Set Control Parameters20
4.1.4Define Output Format of Product ID21
4.1.5Check Function Modules BBP_FUNCTION_MAP21
4.1.6Define Standard Industry Key22
4.1.7Define the Global Time Zone for the Condition Master23
4.2Set Up Business Processes23
4.2.1Define Number Ranges for Shopping Carts and Back-End Document23
4.2.2Define Objects in Back-End System24
4.2.3Define Transaction Types26
4.2.4Define G/L Account for Product Category and Account Assignment27
4.2.5Specify Tax Codes28
4.2.6Hide Buttons for Approval of Invoice29
4.2.7Define Reasons for Rejecting Vendor Invoices29
4.2.8Define Catalogs30
4.3Organizational Model31
4.3.1Create the Initial Root Organizational Unit31
4.3.2Change Existing Organizational Units32
4.3.3SAP Best Practices Root33
4.3.4APO Entry Channel33
4.3.5User RFC_APO (RFC APO)35
4.3.6Organization35
4.3.7Administration37
4.3.8Purchasing Organization37
4.3.9Department40
4.3.10General Explanation of Attributes40
4.3.11General Information for Creating Users44
4.3.12Create a System Administration User45
4.3.13Create an Administration User for Root Organizational Unit46
4.3.14Create Users for the Root Org Unit46
4.3.15Create a Manager with an Organizational Unit47
4.3.16Maintain Attributes for the Component Planner48
4.3.17Delete Users49
4.4Background Jobs49
4.4.1Start Cleaner Job49
4.4.2Schedule Background Job BBP_GET_STATUS_250
4.4.3Schedule Reorganization Jobs51
4.4.4Display Job Selection Overview51
4.5Workflow52
4.5.1Maintain Prefix Numbers52
4.5.2Automatic Workflow Customizing52
4.5.3Run Program RHSOBJCH53
4.5.4Activate Workflow EBP-WFL53
4.5.5Activate Workflow EBP54
4.5.6Set General Task55
4.5.7Assign Role to Task58
4.5.8Regenerate Organizational Environment for Workflow59
4.5.9Activate Start Conditions59
4.5.10Verify Workflow Customizing60
Icons
IconMeaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type StyleDescription
Example textWords 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 textEmphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXTNames 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 textScreen 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 TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example textExact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
General Settings SRM
Building Block Configuration Guide
This document describes the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.
The Configuration Guide describes how to set up the configuration of a building block manually, without the support of automated configuration tools. If you want to use BC Sets and CATT procedures for an automated installation process, refer to the Installation Guide in the General Settings SRM Building Block.
1Preparation
1.1User Roles
Use
SAP provides user roles for the installation and configuration of Best Practices for mySAP SRM to improve the access to the necessary tools.
Prerequisites
For detailed procedure how to apply user roles, please refer to the Essential Documentation guide.
Procedure
1.Upload the following roles:
Installation of Building Block General Settings SRM:
•B04_01I into your SAP R/3 System
•B04_04I into your SAP SRM System
Configuration of Building Block General Settings SRM:
•B04_01C into your SAP R/3 System
•B04_04C into your SAP SRM System
2.Assign the user roles to your user.
Result
The user roles for installation and/or configuration have been uploaded and assigned.
1.2Connectivity
Use
This activity checks whether the connections between different systems based on SRM scenario requirements has already been completed. This includes connections between
•SAP SRM and SAP R/3
•SAP SRM and ITS
•SAP SRM and Business Connector
Prerequisites
The generic Connectivity Building Block should be implemented as prerequisites, this activity refers only to the Connectivity Building Block. Detailed descriptions are available in this documentation as well as in the related Connectivity Installation/Configuration Guides.
Procedure
To make the General Settings SRM Building Block work properly, the following sections in the Connectivity Building Block should be activated:
Local Settings
•R/3 Local Settings
•SRM Local Settings
Cross Connectivity
•R/3 with SRM
•SRM Misc. Connections
For more details regarding required activities please refer to the related Scenario Installation/Configuration Guide.
Result
Necessary connections are available for future use.
2Generation
2.1Start Application Monitors
Use
This activity starts the application monitors in SRM. With this step, you guarantee that the errors that occur in Enterprise Buyer are displayed in the application monitors.
Procedure
Access the transaction using:
SAP SRM
Role MenuGeneration Start application monitors
Transaction codeBBPMONSTART
A message appears to inform you that the monitors have been started.
Result
The application monitors have been started.
2.2Generate Authorization Profiles
Use
In this activity, you generate the authorization profiles for all user roles.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuGeneration Generate Authorization Profiles
Transaction codePFCG
2.Choose Utilities Mass generation.
3.Select the following:
Radio Button or CheckboxSection
All rolesWhich roles do you want to output?
Generate automaticallyGenerate all profiles to be generated?
4.To create or update the authorization profiles for the selected roles, choose Execute.
5.Choose In the Background and Enter.
Result
A profile is created for all standard delivered roles. Without these profiles, you will not be able to logon using the WEB browser.
2.3Generate Middleware
Procedure
1.Access the transaction using:
SAP SRM
Role MenuGeneration Generate Middleware
Transaction codeSMOGGEN
You can also use transaction SMOGWB. This is similar to SMOGGEN, but it has more functionality.
2.Choose and maintain the following values on the Single Values tab:
Single Values
PRDCT_OBJECT
BBP_MATERIAL_WRT
3.Choose twice.
Result
Middleware objects have been generated.
2.4Initial/Total Generation
Use
This activity generates middleware function modules.
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Generation Initial/Total Generation
Transaction codeSMOGTOTAL
This step requires approximately 2 hours. The settings made are needed for the following steps within the Enterprise Buyer.
2.Choose Yes.
3.The Status of Generation Job appears to inform you that a background job has been generated.
4.To view the actual status, choose Refresh. Leave this screen open.
5.Do not proceed with the next steps in the Enterprise Buyer until the status of the report is finished. Nevertheless, you can proceed with the steps in the SAP R/3 back-end system up to the step Prepare for Replication of Vendor Master Records.
6.After you choose Refresh, if a message For more details see generation log is displayed, middleware generation is complete. This can take up to 2 hours.
7.To view the detailed generation report, access the transaction using
SAP SRM
Standard Menu Middleware Development Generation Generation Log Display Log
Transaction CodeSMOGLOG
Result
The necessary function modules have been generated.
3Configuration SAP R/3
3.1Define Number Ranges for Purchase Requisitions
Use
Shopping carts can be transferred to an SAP R/3 back-end system to create purchasing documents. The purchasing documents are created with an external number defined by the user. There is no automatic numbering by the SAP R/3 System. The external number range defined for purchase documents must match the number range defined in the SAP SRM System.
Procedure
1.Access the transaction using:
SAP R/3
Role MenuConfiguration SAP R/3 Define Number Ranges for Purchase Requisitions
Transaction CodeOMH7
IMG PathMaterials Management Purchasing Purchase Requisition Define Number Ranges
2.Choose Change Intervals and choose Insert Interval to add a line such as:
NoFrom numberTo numberCurrent numberExt
RQ40000000004009999999
3.Choose Insert (Enter).
4.Save your data.
5.Confirm the message with Enter.
6.Go back twice.
Result
The external number range for purchase requisitions is defined.
3.2Define Document Types for Purchase Requisitions
Use
Purchasing documents created as a result of adding items to a shopping cart should use their own document type. This activity describes how to define document types for purchase requisitions.
Procedure
1.Access the transaction using:
SAP R/3
Role MenuConfiguration SAP R/3 Define Document Types for Purchase Requisitions
Transaction CodeOMEB
IMG Path
Materials Management Purchasing Purchase Requisition Define Document Types
2.Select type NB and choose Copy.
3.Overwrite Type NB with EC and Nr.rng.ext. with RQ and overwrite the Doc. Type descript with a name of your choice.
4.Choose ENTER.
5.Choose Copy all.
6.Confirm the message in the dialog box by choosing Enter.
7.Choose Save.
Result
The following line item is created:
TypeDoc. Type descript.ItemNr.int.asNr.rng.extField sel....
ECEC Pur. requisition1001RQNBB...
3.3Define Number Ranges for Purchase Orders
Use
Shopping carts can be transferred to an SAP R/3 back-end system to create purchasing documents. Those purchasing documents will be created with an external number defined by the user. (There is no automatic numbering from the SAP R/3 System). The external number range defined for purchase documents must match the number range defined in the SAP SRM System.
Procedure
1.Access the transaction using:
SAP R/3
Role MenuConfiguration SAP R/3 Define Number Ranges for Purchase Orders
Transaction CodeOMH6
IMG PathMaterials Management Purchasing Purchase Order Define number ranges
2.Choose Change Intervals and add a line using Insert Interval such as:
NoFrom numberTo numberCurrent numberExt
PO30000000003009999999
DM40000000004009999999
3.Choose Insert.
4.Choose Save.
5.Confirm the message.
6.Go back twice.
Result
An external number range for purchase orders has been defined.
3.4Define Document Types for Purchase Orders
Use
The purpose of this activity is to define the document types for Purchase Orders that will be created in Back-End system (R/3).
Procedure
1.To carry out the activity, choose one of the following navigation options:
SAP R/3 Role MenuDefine Document Types for Purchase Orders
Transaction CodeOMEC
IMG PathMaterials Management Purchasing Purchase Order Define Document Types
2.Select Type NB and choose Copy.
3.Overwrite Type NB with EC and Nr.rng.ext. with PO and overwrite the Doc. Type descript with a name of your choice.
4.Choose ENTER and then Copy all.
The following new item line appears:
TypeDoc. Type descript.ItemNr.int.asNr.rng.extField sel....
ECEC Purchase Order1001PONBF...
Please note that number range intervals are only examples and can be different from your system.
5.Confirm the message.
6.Save your entries.
7.Select a transport request.
8.Go back.
3.5Define Number Ranges for the Service Entry Sheet
Use
Service entries created by SAP SRM must have an external number. Therefore an external number range has to be defined in the SAP R/3 System and match the number range defined in the SAP SRM System.
Procedure
1.Access the transaction using:
SAP R/3 – Role MenuConfiguration SAP R/3 Define Number Ranges for the Service Entry Sheet
Transaction CodeOMH9
IMG PathMaterials Management External Services Management Number ranges Define number ranges for service entry sheet
2.Choose Change Intervals and add the following line:
NoFrom numberTo numberCurrent numberExt
SE02000000000209999999X
3.Save the entries.
4.Confirm the message.
5.Go back twice.
Result
An external number range for service entry sheets has been defined.
3.6Define Number Ranges for Reservations
Use
The purpose of this activity is to define number ranges for Reservations that will be created in Back-End System(R/3)
Procedure
1.To carry out the activity, choose one of the following navigation options:
SAP R/3 Role MenuDefine Number Ranges for Reservations
Transaction CodeOMJK
IMG pathMaterials Management Inventory management and physical inventory Number assignment Define number assignment for reservations
2.Choose Intervals Change Intervals and add the following line:
NoFrom numberTo numberCurrent numberExt
RS00300000000039999999
3.Choose Save.
4.Confirm the message.
5.Go back twice.
3.7Define Parameters for Download
Use
This activity defines parameters for the CRM consumer.
Procedure
1.Access the transaction using:
SAP R/3 – Role Menu Configuration SAP R/3 Define Parameters for Download
Transaction CodeSM30
2.Enter CRMCONSUM in the Table/View field and choose Maintain.
3.Check whether the consumer CRM has been created and is active (‘X’ means it is active). This is delivered as a default. Go back.
4.Enter the table name CRMRFCPAR and choose Maintain.
5.Choose New entries and make entries in the following fields:
FieldEntry or User action
Consumer Applic.Enter: CRM (mandatory!)
Object nameEnter: *
DestinationType the logical system name of the Enterprise Buyer system, for example, CS8CLNT250 (F4-help is not possible!)
Downld typeEnter: Wildcard for D or I
InQueue flagEnter: X
Use XMLEnter: X
6.Save entries.
7.Go back.
Result
The CRM consumer and RFC destination have been defined.
3.8Prepare for Replication of Material Master Records
Use
This activity makes settings that prepare materials for replication into Enterprise Buyer.
Procedure
1.Access the transaction using:
SAP R/3 / SRM
Role Menu Configuration SAP R/3 Prepare for Replication of Material Master Records
Transaction CodeMM02
2.Enter the material number in the Material field and select the Purchasing view.
3.In the dialog box, select a valid plant and choose ENTER.
4.Check whether the following fields have been maintained:
•Purchasing group
•Tax ind. f. material
•Material group
If one or more of these fields have no entry, you should either find another product where an entry exists or create a new material and enter data in these fields.
Result
The material master records are prepared for replication.
3.9Prepare for Replication of Vendor Master Records
Use
This activity makes settings that prepare vendor master records for replication into Enterprise Buyer.
Procedure
1.Access the transaction using:
SAP R/3 / SRM
Role MenuConfiguration SAP R/3 Prepare for Replication of Vendor Master Records
Transaction CodeMK02
2.Enter a vendor in the Vendor field.
3.In the Purch. Organization field, choose a purchasing organization.
4.Deselect all checkboxes in the General data section of the screen.
5.Select Purchasing data, and choose ENTER.
6.In the Control data section, ensure that the checkbox in AutoEvalGRSetmt Del. is not activated.
Result
Vendor master records are prepared for replication.
4Configuration SAP SRM
4.1Set Up Basic Configuration
4.1.1Define Number Range for Business Partner
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Basic Configuration Define Number Range for Business Partner
Transaction CodeBUCF
IMGCross-Application Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define Number Ranges
2.Choose Insert Intervals.
3.Make the following entries:
NumberFrom NumberTo NumberCurrent NumberExt.
0100000000019999999999
02AZZZZZZZZZZX
The external number range has to correspond with your vendor’s number range in the back-end system. If necessary, adapt the interval.
Note that within the interval ZZZZZZ1001 to ZZZZZZ1012, numbers are reserved for Business Partners used by the Best Practices organizational model. If you do not use the Best Practices organizational structure, number ranges can be defined based on your requirements.
4.Save your entries.
5.Confirm the message that appears.
6.Choose Back.
4.1.2Define Business Partner Groupings
Procedure
To copy numbers from the back-end system, you need to define an “external grouping.” This activity defines business partner groupings.
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Basic Configuration Define Business Partner Groupings
Transaction CodeSPRO
IMG Menu
Enterprise Buyer Cross-Application Components SAP Business Partner Business Partner Basic Settings Number Ranges and Groupings Define Groupings and Assign Number Ranges
2.Maintain the following settings:
GroupingShort nameDescriptionNumber rangeExternalInt.std.grpingExt.std.grping
0001Int.no.assgnmntInternal
number assignment01O
0002Ext.no.assgnmntExternal number assignment02XO
3.Save your entries.
4.Choose or create transport request.
Result
Business Partner Groupings have been defined.
4.1.3Set Control Parameters
Use
The shopping cart can only be further processed in the back-end system after the corresponding documents have been created there. The spooler transfers the shopping cart data to the back-end system. This activity defines the cleaner and spooler control parameters.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Basic Configuration Set Control Parameters
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition Technical Basic Settings Set Control Parameters
Transaction CodeSBBPCONF
2. Maintain the following settings:
Key Control RecordConfiguration Key DescriptionValue Control Record
CLEANER_INTERVALInterval for cleaner restart
CLEANER_JOB_USERJob user for cleaner
SPOOL_JOB_USERUser that executes spool jobBBP_JOB
SPOOL_LEAD_INTERVALLInterval by which the retry time incr.60
SPOOL_MAX_RETRYMax. number of retries for writing5
3.Save your entries.
4.Choose or create a transport request.
4.1.4Define Output Format of Product ID
Use
The purpose of this activity is to define the output and storage format of product IDs.
Procedure
1.To carry out the activity, choose one of the following navigation options:
SAP SRM
Role MenuConfiguration SRM Setup Basic Configuration Define Output Format of Product ID
Transaction CodeCOMCPRFORMAT
IMG MenuEnterprise Buyer Professional Edition Master Data Products Define Output Format and Storage Form of Product ID
2.Choose New entries.
3.Enter 18 in the Product ID length field. This is mandatory.
4.Save your entries.
5.Choose or create a change request.
Result
The output and storage format has been defined.
4.1.5Check Function Modules BBP_FUNCTION_MAP
Use
The purpose of this activity is to check whether the right function modules are assigned to Business Object Methods depending on the SAP R/3 back-end system release.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Basic Configuration Check Function Modules BBP_FUNCTION_MAP
Transaction codeSM30
2.In the field Table/view, enter BBP_FUNCTION_MAP.
3.Check whether the following entries are maintained by choosing Display
4.If necessary, then choose Maintain to add the following lines:
Obj. typeMethodSys. TypeFunction module
BUS2012GetPOItemsInvoiceNON_SAP_1NOR3_PO_READ_ITEMS_INVOICE_BE
BUS2012GetPOItemsInvoiceR/3_3.1HB31I_PO_READ_ITEMS_INVOICE_BE
BUS2012GetPOItemsInvoiceR/3_3.1IB31I_PO_READ_ITEMS_INVOICE_BE
BUS2012GetPOItemsInvoiceR/3_4.0BB40B_INVOICE_MRM_ASSIGNMENT
BUS2012GetPOItemsInvoiceR/3_4.5BB45B_INVOICE_MRM_ASSIGNMENT
BUS2012GetPOItemsInvoiceR/3_4.6AB40B_INVOICE_MRM_ASSIGNMENT
BUS2012GetPOItemsInvoiceR/3_4.6BB40B_INVOICE_MRM_ASSIGNMENT
BUS2012GetPOItemsInvoiceR/3_4.6CB40B_INVOICE_MRM_ASSIGNMENT
Result
The assignment of function modules to methods of business objects have been checked.
4.1.6Define Standard Industry Key
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SRM Setup Basic Configuration Define Standard Industry Key
Transaction CodeSPRO
IMG PathCross Application Components SAP Business Partner Business Partner Organizations Maintain Industry Solution Systems and Industries
2.Maintain the following entries:
Industry Number SystemDescription
0001Retail
3.Save your entries.
4.Choose or create a transport request.
Result
A standard Industry Key has been defined.
4.1.7Define the Global Time Zone for the Condition Master
Procedure
1.Access the transaction using:
Menu
Enterprise Buyer IMGConfiguration SRM Setup Basic Configuration Define the Global Time Zone for the Condition Master
Transaction CodeSPRO
IMG PathCustomer Relationship Management Master data Condition Technique General Configuration Parameters
2.In the table that appears, set the value for parameter to a valid time zone (for example UTC, CET).
ParametersValue
TIMEZONE_MASTER_DATA_DBCET
3.Save the entry.
4.Choose or create transport request.
5.Choose Back.
Result
The Time Zone has been defined for the Condition Master.
4.2Set Up Business Processes
4.2.1Define Number Ranges for Shopping Carts and Back-End Document
Use
This task defines number ranges for shopping carts and the back-end documents that are created for items in a shopping cart.
Prerequisite
Check the already existing number ranges for
•Purchase Requisitions
•Purchase Orders
•Reservations
•Service Entry Sheets
Please ensure that the number ranges defined in your back-end system are defined as external. The external number ranges should be assigned to a document type of the related object (e.g. to document type EC for purchase requisitions).
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SRM Setup Business Process Define Number Ranges for Shopping Carts and Backend Documents
Transaction CodeBBNU
IMG Path Enterprise Buyer Professional Edition Application-Specific Basic Settings Number ranges Define number ranges for shopping carts and Backend documents
2.Choose Change Intervals.
3.Maintain the number range intervals as shown in the following table:
NoFrom NumberTo NumberCurrent NumberExt.
0100100000000019999999
LO00200000000029999999
PO30000000003009999999
RQ40000000004000999999
RS00300000000039999999
SE02000000000200999999
4.Save your entries.
5.Confirm the message that appears.
Result
The number ranges for shopping carts and backend documents have been defined in order to the number ranges for purchasing documents, reservations and service entry sheets in SAP R/3.
4.2.2Define Objects in Back-End System
Use
You need to define objects to be created based on their purchasing group and category ID.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SRM Setup Business Process Define Objects in Backend System
Transaction CodeSPRO
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition Application-Specific Basic Settings Define Objects in Backend System (Purch.Reqs, Reservations, Purch. Orders)
2.Confirm the message that appears.
3.Choose New entries.
4.Maintain entries as shown in the following table:
Purch.grpCategory IDInt. proc.Ext. Proc.
**2 reservations generated if stock available, otherwise ext. proc.Purchase order if item data complete, otherwise purch. req.
40000066*2 reservations generated if stock available, otherwise ext. proc.Purchase order if item data complete, otherwise purch. req.
40000067*2 reservations generated if stock available, otherwise ext. proc.Purchase order if item data complete, otherwise purch. req.
If you are not using the Best Practices organizational structure adapt the purchasing Group entries accordingly. If the organizational structure is build up manually, then, too, change the entries in the purchasing group.
You can use an asterisk ( * ) to include all purchase groups or all product categories.
If reservations should also be generated for available stock, in the entry for internal procurement, choose Reservation generated if stock available, otherwise external procurement.
5.Save your entries.
6.Choose or create a transport request.
Result
You have defined how products belonging to a specific product category have to be procured.
4.2.3Define Transaction Types
Use
You need to specify the transaction type for all materials management documents that are to be created in SRM. This controls the number range intervals that determine the document numbers.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SRM Setup Business Process Define Transaction Types
Transaction CodeSPRO
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition Application-Specific Basic Settings Define Transaction Types
2.Some of the following entries might already be as default in the system. If not, add the entries below:
Trans. TypeDescriptionInt. no.Ext. no.Object Type
BIDBid invitation0102Bid invitation
CONFConfirmation0102Confirmation
ECEC purchase order0102Purchase Order
INVInvoice0102Incoming invoice
POPurchase order0102Purchase Order
QUOTQuotation0102Vendor quotation
SHCShopping cart0102Shopping Cart
3.Save your entries.
4.Choose or create transport request.
Make sure that descriptions are maintained in all languages you will be using in the browser (log on to Customizing in the corresponding language).
4.2.4Define G/L Account for Product Category and Account Assignment
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SRM Setup Business Process Define G/L Account for Product Category and Account Assignment
Transaction CodeSPRO
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition Account Assignment Define G/L Account for Product Category and Account Assignment Category
2.Confirm the message that appears.
3.Choose New entries.
4.On the screen that appears, you need to maintain the Product cat., AcctAss., and G/L acct. fields. The following table is only an example:
Product cat.AcctAss.G/L acct.
*AS410000
*CC410000
*NET410000
*OR410000
*SO410000
*WBS410000
You should at least enter an asterisk ( * ) for each account assignment category. Otherwise, if the system does not find an account, the error message could be unclear.
Maintain the value “OR” and/or “WBS” for the attribute “KNT” belonging to the organizational unit that will be able to select the account assignment category “order” and/or “WBS element” when you create a shopping cart.
Do not copy the lines, because even if you overwrite the product category, the system will keep the original GUID in the background.
5.Save your entries.
6.Choose or create transport request.
4.2.5Specify Tax Codes
Use
This task helps you to specify tax codes so that goods receipts can be created.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Business Processes Specify Tax Codes
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition Application-Specific Basic Settings Tax Calculation Enter Tax Codes
Transaction CodeSPRO
2.Choose New entries.
3.Maintain the fields as shown below:
TaxTax DescriptionNo TaxDefaultTax category
U0A/P Use Tax, exX
U1A/P Use Tax, ta
V0No tax procedureXX
V115% domestic in
V27% domestic inp
V3Domestic input
V414% domestic in
V8Taxable/tax-exe
V9Taxable/tax-exe
Make sure that descriptions are maintained in all languages you will be using in the browser (log on to Customizing in the corresponding language).
4.Save your entries.
5.Choose or create a transport request.
4.2.6Hide Buttons for Approval of Invoice
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Business Processes Hide Buttons for Approval of Invoice
Transaction codeSWL1
IMG Menu Enterprise Buyer Professional Edition Application-Specific Basic Settings SAP Business Workflow Define Dynamic Columns for Integrated Inbox
2.Delete in column Expression (first attr.) entry EC_DECISION in the line of task TS10007950.
3.Save your entries.
4.Choose or create a transport request.
4.2.7Define Reasons for Rejecting Vendor Invoices
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Business Processes Define Reasons for Rejecting Vendor Invoices
Transaction codeSPRO
IMG Menu Enterprise Buyer Professional Edition Confirmation and Invoice Verification Define Reasons for Rejecting Vendor Invoices
2.Choose New entries
3.Define following reasons for rejecting vendor invoices:
ReasonText
0001Price difference
0002Invoice late
0003Quantity incorrect
4.Save your entries.
5.Choose or create a transport request.
4.2.8Define Catalogs
Use
This activity defines a catalog in your SRM System.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Setup Business Processes Define Catalogs
Transaction codeSPRO
IMG Menu Enterprise Buyer Professional Edition Master Data Define Catalogs
2.Choose New entries.
3.Enter a catalog ID and catalog description.
Catalog IDCat. Name
DUMMY
REQUISITERequisite
The Catalog ID must be entered in upper case letters. This applies to this transaction as well as when it is used in the organizational structure as an attribute.
SAP Note 400207 explains the reason for the catalog ID DUMMY.
The call structure for the Dummy-entry does not have to be maintained.
4.Select line of your catalog and choose Catalog Application Call Structure.
5.Enter the catalog specific call structure.
6.The call structure for a Requisite catalog is:
Seq. NumberNameContentsType
1Example: http://igreq0000.sap-ag.de:10/servlet/BugsEyeSAP
URL
20UsernameExample: guestFixed value
30PasswordExample: idesFixed value
40~languageENFixed value
50HOOK_URLReturn URL
60~OkCodeADDIFixed value
70~target_topFixed value
110~callerCTLGFixed value
7.Save your entries.
8.Select or create a transport request.
4.3Organizational Model
4.3.1Create the Initial Root Organizational Unit
Use
Use this procedure to create an organizational model and staff assignments starting with a root organizational unit.
Procedure
1.To create an organizational plan, access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Organizational Model Create the Initial Root Organizational Unit
Transaction CodePPOCA_BBP
2.Set the validity date from to 31.12.9999.
3.Choose Continue (ENTER).
The system creates the root organization.
4.On the Basic data tab in the Organizational unit field, enter a name for your company root.
5.On the Address tab, enter an address and telephone information.
6.Enter an E-mail address and save the data.
7.Repeat the steps above and create a VENDOR ROOT.
Since vendors cannot make purchases within your organization, you need to create one organizational unit for your company and one for the vendors.
Result
After you perform this procedure, you should have two organizational roots. These will both appear in the lower left quadrant of your screen.
4.3.2Change Existing Organizational Units
Use
The following procedure describes how to create an organizational unit in general. If you choose to use the organizational structure from Best Practices, the manual build up is described in the following.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM ® Organizational Model ® Change Existing Organizational Units
Transaction codePPOMA_BBP
IMG Menu
Enterprise BuyerEnterprise Buyer Professional Edition ® Application-Specific Basic Settings ® Organizational Management ® Change Organizational Plan
2.In the upper right quadrant of the screen, to create subordinate organizational units below the root, choose Create, enter the appropriate data, and then save your entries.
3.If you cannot see the details of this organizational unit choose the button: Details for Organizational unit Organization:
4.You will see 5 tabs: Basic Data, Address, Type, Attributes, and Extended attributes.
5.Enter address information.
6.Enter attributes for the organizational unit.
7.Choose Attribute maintenance scenario: Business-to-Business Procurement (for the entry below the root).
8.On the Attributes tab, enter the attribute values using the matchcode search (Possible entries F4).
All subordinate organizational units will automatically inherit the values you enter.
To see the Attribute codes move the column Attributes into the screen by scrolling to the far right in the lower right quadrant and drag and drop this column to the left.
9.Save your entries.
Maintain attributes using the matchcode search (enter *\* and choose F4 to show all possible entries).
The F4 (possible entries) should not be used against the BUK attribute in the organizational chart as this causes an ABAP short dump.
To specify whether the users assigned to a particular role are authorized to display or change an attribute or whether the attribute is to be hidden from view, from the Enterprise Buyer IMG choose Enterprise Buyer professional edition -> Application-Specific Basic Settings -> Roles -> Maintain attribute Access Rights by role.
To avoid the error message Attributes for purchasing group is missing when you create a shopping cart, when you execute transaction BBPPU99, see the hints in SAP Note 312058 and 185700.
10.Change Object permitted for scenario to green, and Save.
The values for each organization unit are described in the following sections:
4.3.3SAP Best Practices Root
No attributes need to be maintained in this node.
An Overview of the best practices organizational structure can be found in the section Users, Roles and the Organizational Structure.
4.3.4APO Entry Channel
Inherited entries from the ‘parent org.’ and additional:
Set flag for company. The ID of the Company will be set automatically.
NameAttributesValue
Logical systemACSLogical System of Back-End system (Example: DS7CLNT224)
Bill-to party addressADDR_BILLTAddress number automatically generated by the system (Example: 10612)
Delivery addressADDR_SHIPTAddress number automatically generated by the system (Example: 10612)
Purchasing doc. TypeBSA\EC
Company codeBUK\0100
Company codeBUK \0100
Movement typeBWA\201
Cost centerCNT\101006
Local CurrencyCURDEM
Local CurrencyCUREUR
Transaction type:
Direct materialDP_PROC_TYECDP
Acct assignment cat.KNTAS
Acct assignment cat.KNTCC
Acct assignment cat.KNTOR
PM Purchasing orPM_PUR_ORG\0100
RequisitionerREQUESTERPartner number for plant (Example: BP10)
Tasks of purchasingRESP_PGRPO 50000050
Logical systemSYSLogical System of Back End System (Example: DS7CLNT224)>
NameExtended AttributesIDSrc. System
PlantWRK0001Logical System of Back End System (Example: DS7CLNT224)
Material GroupPRCAT10020Logical System of Back End System (Example: DS7CLNT224)
The default flag for the attribute Account assignment category (KNT) for one of the entries must be set. Recommended is to choose the entry (Value) for CC (Cost Center).
Without this flag you will not be able to create a shopping cart.
4.3.5User RFC_APO (RFC APO)
Inherited entries from the ‘parent org.’ and additional:
4.3.6Organization
Inherited entries from the ‘parent org.’
Set the flag for the company. The ID of the Company will be set automatically.
NameAttributeValue
Logical systemACSLogical System of Back End System (Example: DS7CLNT224)
Bill-to party addressADDR_BILLTAddress number automatically generated by the system (Example: 10612)
Delivery addressADDR_SHIPTAddress number automatically generated by the system (Example: 10612)
Purchasing doc. typeBSA\EC
Purchasing doc. typeBSA\EC
Company codeBUK\0100
Company codeBUK\0100
Movement typeBWA\201
CatalogCATDUMMY
CatalogCATRequisite
Cost centerCNT\101006
Local CurrencyCURDEM
Local Currency CUREUR
Current ITS of UserITS_DESTURL of the ITS (Example: http://pgct8-252.wdf.sap-ag.de:1080/scripts/wgate/ )
Acct assignment cat.KNTAS
Acct assignment cat.KNTCC
Acct assignment cat.KNTOR
PM purchasing org.PM_PUR_ORG\0001
User roleROLESAP_BBP_STAL_EMPLOYEE
Logical systemSYSLogical System of Back End System (Example: DS7CLNT224)
Logical systemSYSLogical System of Enterprise Buyer System (Example: CS8CLNT250)
NameExtended AttributesIDSrc. System
Material GroupPRCAT99999Logical System of Back End System (Example: DS7CLNT224)
Material GroupPRCATLocal1Logical System of Enterprise Buyer System (Example: CS8CLNT250)
PlantWRK0001Logical System of Back End System (Example: DS7CLNT224)
4.3.7Administration
Inherited entries from the ‘parent org.’ and additional:
4.3.8Purchasing Organization
Inherited entries from the ‘parent org.' and additional:
Set the flag for Purch.Org. The ID of the purchase organization will be set automatically.
The Type tab is for company and purchasing organizational units. See SAP Note 438893 if purchasing group is not displayed on basic data screen of your shopping basket.
NameTypeValue
Purch. OrganizationOrganization ID (Example: O 50000053)
R/3 Purch. Org.\0001
NameAttr.Value
PhasePM_IPHAS0
Default PrinterPRI Printer name (Example: P264)
Tasks of purchasing groupRESP_PGRPOrganization ID (Example: O 50000051)
You will have re-visit this attribute after creating the purchasing group.
User roleROLESAP_BBP_STAL_PURCHASER
User roleROLESAP_BBP_STAL_PURCHASE_MANAGER
Purchasing Group 001 (Direct/Indirect Procurement)
Inherited entries from the ‘parent org.’ and additional:
Set the flag for Purchasing group. The ID of the purchasing group will be set automatically.
NameTypeValue
Purchasing groupOrganization ID (Example: O 50000066)
R/3 Purchasing group\201
NameAttributesValue
Transaction type:
Direct materialDP_PROC_TYECDP
RequisitionerREQUESTORPartner number for plant (Example: BP10)
Purchasing group tasks RESP_PGRPOrganization ID (Example: O 50000050)
Purchasing group tasks RESP_PGRPOrganization ID (Example: O 50000051)
Purchasing group tasks RESP_PGRPOrganization ID (Example: O 50000061)
NameExtended AttributesProduct Category IDSrc System
Responsible Product GroupRESP_PRCATExample: 10020Logical System of Back End System (Example: DS7CLNT224)
Responsible Product GroupRESP_PRCATExample: 99999Logical System of Back End System (Example: DS7CLNT224)
Purchasing Group 002 (Local Procurement)
Inherited entries from the ‘parent org.' and additional:
Set the flag for Purchasing group. The ID of the Purchasing group will be set automatically.
NameTypeValue
Purchasing groupO 50000067
NameAttr.Value
Tasks of purchasing groupRESP_PGRPO 50000051
Logical systemSYSCS8CLNT250
Logical systemSYSDS7CLNT224
NameExtended AttributesProduct Category IDSrc. System
Responsible Product GroupRESP_PRCATLocal1CS8CLNT250
4.3.9Department
Inherited entries from the ‘parent org.’ and additional:
NameAttr.Value
PhasePM_IPHAS0
R/3 purchasing groupPM_PUR_GRPDS7CLNT224\201
Maintain the attribute values for organization units only via the matchcode search (choose F4 to show all possible entries).
In the submenu enter an asterisk ( * ) in the field value to show all possible entries.
Scenario= BBP
Attribute= RESP_PGRP
Value (from)*
Maximum no. of hits500
4.3.10General Explanation of Attributes
AttributeExtended AttributesValueDescriptionMandatory
ACSBACKEND Key for the FI/CO back-end systemX
BSABACKEND\EC and/or SYSTEM\ECDocument type in back-end/local systemX
BUKBACKEND\1234 and/or SYSTEM\1234Company code in back-end system or localX
BWABACKEND\201Movement type in back-end system (for reservations in back end only)(X)
CATCatalog IDName of the catalog an organization/user is allowed to use
CNTBACKEND\12341 and/or SYSTEM\12341Account assignment object allowed to use
CUREURKey for the local currencyX
DP_PROC_TYECDPTransaction Type: Direct Materials
This attribute has to be maintained for the responsible purchasing group.
The specified transaction type must correspond to the document type used in the back-end system for direct material purchase order with external number assignment.
Path in the Implementation Guide (IMG): Enterprise Buyer Professional Edition ® Application-Specific Basic Settings ® Define Transaction Types
KNTCCAccount assignments allowed to useX
PM_ARWRKBACKEND \1000Performing plant in the selection screen (browser, component planning PM)
PM_IPHAS0 (open) or 2Order status in the selection screen (browser, component planning PM)(X)
PM_AUARTBACKEND\PM01Order type in the selection screen (browser, component planning PM)
PM_IWERKBACKEND \1000Planning plant in the selection screen (browser, component planning PM)
PM_SWERKBACKEND \1000Maintenance plant in the selection screen (browser, component planning PM)
PM_VAWRKBACKEND \1000Main plant for resp. work center in the selection screen (browser, component planning PM)
PM_WGRBACKEND\001Product category that will be available when adding components to a PM order
PM_WRKBACKEND \1000Plants that can be selected via matchcode at item level when ordering components
REQUISITIONERO 50000001Departments/users for which a user or Org unit will be allowed to create
RESP_PGRPO 50000001Only for purchasing departments:
Org unit for which unit is responsible
RESP_WGR123Only for purchasing departments:
Material (/product) group for which this dept. is responsible.
ROLESAP_BBP_STAL_EMPLOYEE All role(s) that can be adopted by a person belonging to this org unit.
Not relevant for vendors and bidders.
SYSBACKENDMM back-end system used (if back end is used)(X)
PRCAT123Material group that an org unit is allowed to orderX
WRKBACKEND\1234Plant (in the back-end system)(X)
DFT_PGRDefault responsible purchasing group (If there is more than one responsible purchasing org for this org unit)
VENDOR_ACSBACKENDVendor Root: Accounting system for the vendor
Specifies the back-end system where the accounting for the vendor is checked.X
VENDOR_SYSBACKEND and/or
SYSTEMVendor Root: System in which POs can be created for this vendor X
APPRV_LIMApproval limit and Output limit can be used for PO value limits
4.3.11General Information for Creating Users
Use
If you are creating initial users, you can deactivate the approval function.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Organizational Model General Information for Creating Users
Transaction codeO_BBP_USRCUS
Enterprise Buyer
IMG Menu Enterprise Buyer Professional Edition Application-Specific Basic Settings Create Users Set Approval Indicator
2.Deselect the flag in the box.
After you create initial users, do not forget to activate the approval function by selecting the flag again.
If you are going to use more languages than English when you create new users:
1.Access the transaction using:
Enterprise Buyer
IMG Menu Enterprise Buyer Professional Edition Application-Specific Basic Settings Create Users Change Text for Required Data Fields
Transaction CodeSPRO
2.Flag the two entries and choose Copy as.
3.Maintain the language key and the corresponding question and choose ENTER.
4.Save your entries.
Create a user for the batch-jobs (for example, control parameters) in Enterprise Buyer (transaction SU01), for example BBP_JOB or BBP_BATCH.
Create the user WFBATCH for the workflow functions.
4.3.12Create a System Administration User
Use
This task creates business partners, contact persons, and users that will be used in the Enterprise Buyer Demonstration Scenario.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Organizational Model Create a System Administration User
Transaction codeSU01
If you encounter an error message, you may have to run the program RSADRCK2. Whenever you have problems creating users with transaction SU01, run this program.
2.Create a User ID Admin (Nick Potter) with the role SAP_BBP_STAL_ADMINISTRATOR.
3.Start Enterprise Buyer using the Internet Browser and log on with an administration user. In the scenario, this is ADMIN with the initial password: INIT. Change it to hello.
4.From the LaunchPad, choose Administration EBR -> Manage User Data.
5.Choose User in own enterprise and Create users.
6.Make entries in at least all mandatory fields marked with “*”.
4.3.13Create an Administration User for Root Organizational Unit
Procedure
1.Log onto the Web as User Admin
2.In the Web, choose Administration Manage user data.
3.Choose Create users.
4.Include appropriate data. For the Organization unit field, choose Find and select the root organizational unit that you created earlier. Select the checkbox for Manager and choose Save.
Passwords are sent to the users via e-mail (this can be modified with transaction SU01).
For the e-mail functionality, you must install a message server.
The following users must be created:
User IDFirst NameLast NameOrg UnitManagerUser Role
ADMIN1MarkusMeierEnter the Org-unit ID of the Root OrganizationSAP_BBP_STAL_ADMINSTRATOR
To activate the administrator’s cockpit in the browser you have to go to Customizing for Enterprise Buyer.
5.In the Enterprise Buyer IMG, choose Enterprise Buyer Professional Edition Application-Specific Basic Settings Start Application Monitors and choose .
4.3.14Create Users for the Root Org Unit
Procedure
1.Log onto Enterprise Buyer in the Web as User Admin1.
2.In the Web, choose Administration Manage user data.
3.Choose Create users.
4.Include appropriate data. For the Organization unit field, choose Find and select the root organizational unit that you created earlier. Select the checkbox for Manager and choose Save.
5.Passwords are sent to the users via e-mail (this can be modified with transaction SU01).
For the e-mail functionality, you must install a message server.
The following users must be created:
User IDFirst NameLast NameOrg UnitManagerUser Role
RFC_APORFCAPOSAP_BBP_STAL_ADMINSTRATOR
EmployeeAmandaWinterExample: O 50000061
DepartmentSAP_BBP_STAL_EMPLOYEE
SAP_BBP_STAL_PLANNER
SECRETARYSally BaldwinExample: O 50000061
DepartmentSAP_BBP_STAL_EMPLOYEE
PURCHASER1Bill PalmerExample: O 50000066 Purchasing Group 001SAP_BBP_STAL_PURCHASER
PURCHASER2James StevensExample: O 50000067 Purchasing Group 002SAP_BBP_STAL_PURCHASER
4.3.15Create a Manager with an Organizational Unit
Procedure
Users must be created in the Web. Otherwise, the data is incomplete.
1.Log onto the Web as Admin1.
2.In Enterprise Buyer, choose Administration EBR ® Manage User Data ® Create Users.
3.As a minimum, enter data in the required fields.
The required fields are marked with an asterisk.
4.Enter the organizational unit (you can choose Find for assistance in matching the name).
5.Enter detailed data for the new organizational unit and save the data.
6.Create the following users:
User IDFirst NameLast nameOrg UnitMgrUser Role
MANAGERLindaSummerExample: O 50000051 OrganizationXSAP_BBP_STAL_MANAGER
MAN_OFFICESarahJonesExample: O 50000061
DepartmentXSAP_BBP_STAL_MANAGER
PURMANHenry ClarkExample: O 50000053 Purchasing OrganizationXSAP_BBP_STAL__PURCHASE_MANAGER
Once the authorization process has been activated, new users must be approved by the next higher manager.
4.3.16Maintain Attributes for the Component Planner
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SAP SRM ® Organizational Model ® Maintain Attributes for the Component Planner
Transaction CodePPOMA_BBP
2.Select the position Component Planner, for example, Amanda Winter.
3.Select tab Attributes
4.Check for Inherited entries from the ‘parent org.’
5.Enter additional attributes as shown in table below.
NameAttributeValue
Planning PlantPM_IWERKDS7CLNT270\0001
Maintenance plantPM_SWERKDS7CLNT270\0001
Responsible work space at plantPM_VAWRKDS7CLNT270\0001
PM Material GroupPM_WGRDS7CLNT270\99999
PM Plant of componentPM_WRKDS7CLNT270\0001
To check the attributes of a user
•In the Enterprise Buyer system, execute transaction SE37 and enter BBP_GET_ATTRIBUTES in the Function module field.
•Choose Single Test.
•Enter the User ID to be checked (such as SECRETARY) and choose Execute.
•Choose in the Value area in the bottom right corner of the screen.
4.3.17Delete Users
Use
This section is only for your information.
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SAP SRM ® Background Jobs ® Delete Users
Transaction CodePPOMA_BBP
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition ® Application-Specific Basic Settings ® Organizational Management ® Change Organizational Plan
2.Delete the user from the organizational structure.
3.Access another transaction using:
SAP Menu
Enterprise Buyer Basis Tools ® Administration ® User Maintenance ® Users
Transaction CodeSU01
4.Delete the user.
You can also repair users that have not been generated completely in Enterprise Buyer.
The user was generated with transaction SU01. Execute transaction SE37, enter BBP_CREATE_USER in the Function module field, and choose Single Test.
Enter the User ID, org unit where the user is or should be attached to, flag whether he is a manager, and modify the address if necessary.
4.4Background Jobs
4.4.1Start Cleaner Job
Use
The cleaner is a report that checks whether all data has been transferred correctly to the back-end system. If so, it will delete obsolete table entries in Enterprise Buyer and maintain the numbers of the created documents.
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SAP SRM ® Background Jobs ® Start Cleaner Job
Transaction CodeSBBPCONF
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition ® Technical Basic Settings ® Set Control Parameters
2.Make entries as follows:
Key Control RecordConfiguration Key DescriptionValue Control Record
Cleaner_IntervalInterval for cleaner restart
Cleaner_Job_UserJob user for cleaner
3.To start CLEANJOB, execute transaction SA38 and then execute the program START_CLEANER.
This report schedules the job CLEAN_REQREQ_UP in the time interval you enter in the control parameter in Customizing (time unit is seconds). Stop CLEANJOB with the report: STOP_CLEANER.
4.4.2Schedule Background Job BBP_GET_STATUS_2
Use
The program BBP_GET_STATUS retrieves new information from the back-end system, such as the purchase order number after conversion from the purchase requisition. This program has to be scheduled at least daily in Enterprise Buyer. For demonstration purposes, you can schedule it every 5 minutes for a more frequent update.
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SAP SRM ® Background Jobs ® Schedule Background Job BBP_GET_STATUS_2
Transaction CodeSM36
2.To create the job, enter BBP_GET_STATUS_2 in the Job name field.
3.Choose Step.
The Create Step screen appears.
4.Replace your user with the user: BBP_JOB.
5.Enter the program name BBP_GET_STATUS_2.
6.Save your entries.
7.To schedule the job, choose Start condition.
8.Choose Immediate, select Periodic job and choose Period values. Select one of the intervals (for example, Other period) and define the interval.
9.Save the entries (twice).
4.4.3Schedule Reorganization Jobs
Use
Several jobs must be run periodically in a live R/3 installation, for example, to delete outdated jobs or spool objects. You can easily schedule these jobs automatically.
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SAP SRM ® Background Jobs ® Schedule Reorganization Jobs
Transaction CodeSM36
2.Choose Goto ® Standard jobs from the menu bar.
See SAP Note 16083 for details and comments.
3.Choose Default scheduling.
4.4.4Display Job Selection Overview
Use
For this activity, you check the job scheduling for the following jobs:
•BBP_GET_STATUS_2
•CLEANJOB
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SAP SRM Background Jobs Display Job Selection Overview
Transaction CodeSM37
The Simple Job Selection screen appears.
2.Enter the Job name and the User name in the corresponding fields.
Enter an asterisk ( * ) for the Job name to display a list of all jobs for the specified user.
3.Select other appropriate entries on this screen and execute the transaction. Be sure you select at least one job status. The Job Overview screen appears and lists information about the job status, date, time, duration, and delays.
Result
This activity ensures that all jobs are running.
4.5Workflow
4.5.1Maintain Prefix Numbers
Use
The number of a task/workflow consists of eight digits (3 prefix + 5 internal numbers). This prefix is also used when you create your own workflows.
Procedure
1.Access the transaction using:
SAP SRM
Role Menu Configuration SAP SRM Workflow Maintain Prefix Numbers
Transaction CodeOOW4
2.Maintain the prefix numbers for standard object types and choose ENTER.
3.Choose Display Change and then Create.
FieldUser Entry
Prefix numberExample: 910
SAP System IDEnter your Enterprise Buyer System ID (Example: CS8)
Client numberEnter the client of your Enterprise Buyer System (Example: 250)
4.Save the entries.
5.Enter your development class in the Package field.
Example: ZZZZ or local object ($TMP)
6.Choose Save.
7.Choose Cancel.
Result
Prefix numbers for workflow development are created.
4.5.2Automatic Workflow Customizing
Use
In this activity, you maintain SAP Business Workflow standard settings.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Workflow Automatic Workflow Customizing
Transaction CodeSWU3
IMG MenuEnterprise Buyer Professional Edition Application-Specific Basic Settings SAP Business Workflow Maintain Standard Settings for SAP Business Workflow
2.Execute Perform Automatic Workflow Customizing.
3.Choose Back.
If you are configuring the workflow specifically for your needs, you can return to this activity again later.
4.5.3Run Program RHSOBJCH
Use
After you process Automatic Workflow Customizing, some settings are not marked with a green check mark. With this activity, settings that are not marked with a green check mark due to incorrect entries in the PD control tables will be changed to green.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM ® Workflow ® Run Program RHSOBJCH
Transaction CodeSE38
2.Run program RHSOBJCH.
If the program needs to be executed, a checkbox is displayed. Select all the checkboxes on the left and execute it. Ignore the error message.
4.5.4Activate Workflow EBP-WFL
Use
This activity activates the various workflows needed for your work. These are located in various branches in Customizing.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Workflow Activate Workflow EBP-WFL
Transaction CodeOOCU
IMG MenuEnterprise Buyer Professional Edition Application-Specific Basic Settings SAP Business Workflow Perform Task-Specific Customizing
2.From the navigation tree, choose SAP EBP EBP-WFL and then Activate event linking.
3.To activate a Workflow, open the single Workflow tree and choose Deactivated. The button then changes to Activated.
4.Activate the following workflows:
Workflow ObjectDescription
WS10000031Two Step Approval of shopping cart
WS10000060Workflow without approval
WS10000129Approval of shopping cart in one step
WS10000192(Approve new user)
WS10000197(Approve confirmation) has to be activated even if you are not using the approval strategy
WS10000209(Registration of bidder or vendor)
WS10000211(Approve invoice)
WS10000214(Triggers the deletion of an item by the administrator and dispatches an e-mail to the shopping cart owner)
WS10000215(Resubmission of an item from a shopping cart by an administrator)
WS10000223(Approve new password)
WS10000252No approval of invoice workflow
4.5.5Activate Workflow EBP
Use
You need to activate the workflows that you intend to use. These can be found in various branches in Customizing.
Procedure
1.Access the transaction using:
SAP SRM
Role MenuConfiguration SAP SRM Workflow Activate Workflow EBP
Transaction CodeOOCU
IMG Menu
Enterprise Buyer Professional Edition Application-Specific Basic Settings SAP Business Workflow Perform Task-Specific Customizing
2.From the navigation tree, choose SAP EBP EBP and then Activate event linking.
3.To activate a Workflow, open the single Workflow tree and choose Deactivated. The button then changes to Activated.
4.Activate the following workflows:
Workflow ObjectDescription
WS10000202PM requisition transfer
1) Check Event Linkage active
1.If a workflow is not running, to check whether it is really activated, execute transaction SWLD.
2.From the menu bar, choose Utilities Events Type linkages.
3.Select a workflow.
4.To activate a workflow choose Detail, mark Linkage Activated, and save the data.
5.Especially check whether the following type linkages are as described below:
Object typeEventRec.typeType linkage active
BUS2203SAVEDWS10000197X
BUS2205SAVEDWS10000211X
BUS2121PM_SENDWS10000202X
BUS4101SAVEDWS10000192X
2) Test Event linkage active
1.To check the event linkage for workflows, execute transaction SWUD.
2.Choose Test environment and then Simulate event.
3) Buffer check
If the workflow is not running well, you can initiate a buffer synchronization in the organizational environment.
1.Execute transaction PPWFBUF or SWU_OBUF.
2.Choose Runtime Buffer Synchronize from the menu bar.
Result
The EBP Workflows have been activated.
4.5.6Set General Task
Use
This activity allows you to assign agents to a task. Initially, you should choose General task. This allows everyone to receive the work item. If you want to restrict this, choose No general task and assign a role / user.
Procedure
1.Access the transaction using:
SAP SRMConfiguration SAP SRM Workflow Set General Task
Transaction CodeOOCU
IMG Menu
Enterprise Buyer Enterprise Buyer Professional Edition Application-Specific Basic Settings SAP Business Workflow Perform Task-Specific Customizing
2.Expand the Application Component EBP
3.Choose Assign Agents for EBP-WFL (Workflow).
4.Choose Task as mentioned in table be