Verity Solutions

SAP SRM Training material

Key Features

  • 24 Hrs Instructor-led Training
  • 48 Hrs Self-paced Videos
  • 48 Hrs Project Work & Exercises
  • Flexible Schedule
  • 24 x 7 Lifetime Support & Access
  • Certification and Job Assistance

Overview

My SAP SRM is a purchasing platform that delivers sustainable savings and value generated for world-class supply management. SRM covers the full supply cycle, from strategic sourcing to operational procurement and supplier enablement, leveraging consolidated content and master data. With mySAP SRM, you can collaborate with all suppliers for all purchased goods and services. This means you constantly optimize supplier selection, compress cycle times, and device focused sourcing and procurement strategies.

Step by Step instructions below on how to configure SRM.

TABLE OF CONTENTS

1.       Introduction.. 1

2.       Technical Basic Settings.. 1

2.1.        Create RFC Connection. 1

2.1.1. Step 1: Create RFC User for connection in EBP.. 1

2.1.2. Step 2: Create RFC User for connection in R/3. 2

2.1.3. Step 3: Create RFC connection in EBP.. 3

2.1.4. Step 4: Create RFC connection in R/3. 5

2.2.        Create ALE Connection. 6

2.2.1. Step 1: Define logical system in EBP.. 6

2.2.2. Step 2: Define logical system in R/3. 7

2.2.3. Step 3: Assign logical system to client in EBP.. 8

2.2.4. Step 4 : Create distribution model 9

2.2.5. Step 5: Generate partner profiles. 10

2.2.6. Step 6: Distribute distribution model 11

2.2.7. Step 7: Generate partner profiles in R/3. 12

2.3.        Define Backend System.. 12

2.3.1. Step 1: Define backend system.. 12

2.3.2. Step 2: Define backend system for product category. 13

2.4.        Jobs. 14

2.4.1. Step 1: Set parameters for controlling the required jobs. 14

2.4.2. Step 2: Create Job User in EBP.. 15

2.4.3. Step 3: Define Jobs in EBP.. 16

2.5.        Publish HTML. 17

2.5.1. Step 1: Maintain required data for publishing. 17

2.5.2. Step 2: Select target for publishing. 22

2.5.3. Step 3: Publish. 23

3.       Master Data.. 23

3.1.        Catalogs. 23

3.1.1. Step 1 : Define Web Service. 23

3.1.2. Step 2: Define call structure for Web Service. 24

4.       Cross-Application Basic Settings.. 26

4.1.        Roles. 26

4.2.        Organizational Management. 26

4.3.        Number Ranges. 27

4.3.1. Step 1: Set the number range. 27

4.3.2. Step 2: Use the number range. 28

4.3.3. Step 3: Define transaction types. 29

4.4.        Workflow.. 30

4.5.        Tax. 30

4.6.        Account Assignment. 31

4.6.1. Step 1: Define account assignment category. 31

4.6.2. Step 2: Define automatic g/l account determination according to product category and account assignment category. 32

4.7.        Objects in Backend System.. 32

4.8.        Application Monitors. 34

4.9.        Business Partner Number Range. 34

4.9.1. Step 1: Define number range. 34

4.9.2. Step 2: Define grouping. 35

5.       Middleware Settings.. 36

5.1.        R/3 Backend. 37

5.2.        SRM.. 37

5.2.1. Maintain Middleware Settings. 37

5.2.2. Maintain Industry Settings. 37

5.2.3. Maintain Middleware Site. 39

5.2.4. Set Middleware Settings. 39

5.2.5. Upload Data From Backend. 40

6.       Appendix I: Multi Backend Capabilities of EBP.. 42

7.       Appendix II: Remarks On system copy.. 43

7.1.        Copy of EBP.. 43

7.2.        Copy of R/3. 43

  1. Introduction

This document contains the set-up / configuration of mySAP SRM  , classic deployment, self-service procurement scenario as used for procurement of indirect material in the EADS TRIO project. The document is intended for process owners and system administrators involved.

  1. Technical Basic Settings

2.1.   Create RFC Connection

As the EBP is a separate SAP system beside the SAP R/3 backend system, the EBP has to be connected to the SAP R/3 backend.

2.1.1. Step 1: Create RFC User for connection in EBP

Path 
SRM IMG 
T CodeSU01

 

Settings 
User NameRFC_Z60_100
User TypeCommunications
ProfileSAP_ALL

 

 
 

 

2.1.2. Step 2: Create RFC User for connection in R/3

Path 
R/3 IMG 
T CodeSU01

 

Settings 
User NameRFC_F40_100
User TypeCommunications
ProfileSAP_ALL

 

Screenshots
 

 

2.1.3. Step 3: Create RFC connection in EBP

Note: Logon language for connection was intentionally left blank. By doing so, the system takes the logon language of the EBP user for the connection. This is important for displaying system messages from the backend system in the user logon language.

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® Define RFC Destinations
T CodeSM59

 

Settings 
RFC DestinationF40_100
Connection Type3 – R/3 Connection
Target Host172.29.65.151
UserRFC_F40_100

 

Screenshots
 

 

2.1.4. Step 4: Create RFC connection in R/3

Path 
R/3 IMGBasis Components ® Application Link Enabling (ALE) ® Sending and Receiving Systems ® Systems in Network ® Define Target Systems for RFC Calls
T CodeSM59

 

Settings 
RFC DestinationZ60_100
Connection Type3 – R/3 Connection
Target Host172.29.65.152
UserRFC_Z60_100

 

Screenshots
 

 

2.2.   Create ALE Connection

Some communication between EBP and SAP R/3 is done by ALE. Therefore the ALE connection has to be configured as well.

2.2.1. Step 1: Define logical system in EBP

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® ALE Settings (Logical System) ® Distribution (ALE) ® Basic Settings ® Logical Systems ® Define Logical System
T CodeSALE

 

Settings 
Logical SystemZ60_100
NameEBP PROD
Logical SystemF40_100
NameTrIO R/3 PROD Productive Client

 

Screenshots
 

 

2.2.2. Step 2: Define logical system in R/3

Path 
R/3 IMGBasis Components ® Application Link Enabling (ALE) ® Sending and Receiving Systems ® Logical Systems ® Define Logical System
T CodeSALE

 

Settings 
Logical SystemZ60_100
NameEBP PROD

 

Screenshots
 

 

2.2.3. Step 3: Assign logical system to client in EBP

Path 
SRM IMGSALE ® Basic Settings ® Logical Systems ® Assign Logical System to Client
T CodeSALE

 

Settings 
Client100
NamePROD

 

Screenshots
 

 

2.2.4. Step 4 : Create distribution model

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® ALE Settings (Logical System) ® Distribution (ALE) ® Modelling and Implementing Business Processes ® Maintain Distribution Model and Distribute Views
T CodeBD64

 

Settings 
Model ViewEBP
SenderZ60_100
ReceiverF40_100
Message TypeACC_GOODS_MOVEMENT
Model ViewEBP
SenderZ60_100
ReceiverF40_100
Message TypeACLPAY
Model ViewEBP
SenderZ60_100
ReceiverF40_100
Message TypeBBPCO
Model ViewEBP
SenderZ60_100
ReceiverF40_100
Message TypeBBPIV
Model ViewEBP
SenderZ60_100
ReceiverF40_100
Message TypeMBGMCR

 

Screenshots
 

 

2.2.5. Step 5: Generate partner profiles

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® ALE Settings (Logical System) ® Distribution (ALE) ® Modelling and Implementing Business Processes ® Maintain Distribution Model and Distribute Views
T CodeBD64 ® Environment ® Generate Partner Profiles

 

Settings 
Model ViewEBP
Partner SystemF40_100
Output ModeTransfer Idocs immediately
ProcessingTrigger immediately

 

Screenshots
 
  

 

2.2.6. Step 6: Distribute distribution model

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® ALE Settings (Logical System) ® Distribution (ALE) ® Modelling and Implementing Business Processes ® Maintain Distribution Model and Distribute Views
T CodeBD64 ® Menue ® Edit ® Model View ® Distribute

 

Settings 
Logical systemF40_100

 

2.2.7. Step 7: Generate partner profiles in R/3

Path 
R/3 IMGBasis Components ® Application Link Enabling (ALE) ® Modelling and Implementing Business Processes ® Maintain Distribution Model and Distribute Views
T CodeBD64 ® Environment ® Generate Partner Profiles

 

Settings 
Model viewEBP
Partner systemZ60_100
Output ModeTransfer Idocs immediately
ProcessingTrigger immediately

 

2.3.   Define Backend System

2.3.1. Step 1: Define backend system

Relevant backend systems have to be defined in EBP.

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® Define Backend Systems
T Code

 

Settings 
Logical SystemF40_100
RFC DestinationF40_100
System TypeR/3 System 4.6c
RFCYes
LocalNo
FI validReal time backend validation of FI data

 

Screenshots
 

 

2.3.2. Step 2: Define backend system for product category

Backend system that the documents are posted in, depending on the product category have to be specified.

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® Define Backend System for Product Category
T Code

 

Settings 
Category ID*
Source SystemF40_100
Target SystemF40_100

 

Screenshots
 

 

2.4.   Jobs

As material management documents (purchase orders, goods receipts) are to be created in the backend system, relevant information about the spooler and the update frequency has to be defined.

2.4.1. Step 1: Set parameters for controlling the required jobs

Path 
SRM IMGSupplier Relationship Management ® SRM Server ® Technical Basic Settings ® Set Control Parameters
T CodeSBBPCONF

 

Settings 
Key control recordCLEANER_INTERVAL
Value control record<blank>
Key control recordCLEANER_JOB_– USER
Value control recordEBP_JOB
Key control recordSPOOL_JOB_– USER
Value control recordEBP_JOB
Key control recordSPOOL_LEAD_INTERVALL
Value control record60
Key control recordSPOOL_MAX_RETRY
Value control record5

 

Screenshots
 

 

2.4.2. Step 2: Create Job User in EBP

Path 
SRM IMG
T CodeSU01

 

Settings 
NameEBP_JOB
User TypeSystem
ProfilesSAP_ALL, SAP_NEW

 

Screenshots
 

 

2.4.3. Step 3: Define Jobs in EBP

Path 
SRM IMGSystem ® Services ® Jobs ® Define Job
T Code

 

Settings 
Job NameEBP_CLEANER
UserEBP_JOB
Abap Programm to startCLEAN_REQREQ_UP
Start Conditionimmediate, Periodic Minutes = 1
Job NameEBP_GET_STATUS
UserEBP_JOB
Abap Programm to startBBP_GET_STATUS_
Start Conditionimmediate, Periodic Minutes = 1

 

Screenshots
N/a

 

2.5.   Publish HTML

The EBP is accessed by the web browser using HTML pages. These HTML files have first to be published to the ITS (for this system the internal ITS of the WebAS is used).

2.5.1. Step 1: Maintain required data for publishing

Path 
SRM IMG
T CodeSE80 → Internet Service → GLOBAL → Display → Maintain Service File GLOBAL.SRVC

 

Settings 
~EXITURLhttp://intra.ds.corp/
~APPSERVERZFRSAP02.fr.ds.corp
~CLIENT100
~HOSTUNSECUREzfrsap02.fr.ds.corp
~PORTUNSECURE8000
~SYSTEMNAMEZ60
~SYSTEMNUMBER00

 

Screenshots
 

 

Path 
SRM IMG
T CodeSE80 → Internet Service → BBPSTART → Display → Maintain HTML Template BBPSTART

 

Settings 
~CLIENT100

 

Screenshots
 

 

Path 
SRM IMG
T CodeSE80 → Internet Service → BBPVENDOR → Display → Maintain HTML Template BBPVENDOR

 

Settings 
~CLIENT100

 

Screenshots
 

 

Path 
SRM IMG
T CodeSE80 → Internet Service → BBPAT03→ Display → Maintain HTML Template BBPAT03

 

Settings 
~CLIENT100

 

Screenshots
 

 

Path 
SRM IMG
T CodeSE80 → Internet Service → BBPAT04→ Display → Maintain HTML Template BBPAT04

 

Settings 
~CLIENT100

 

Screenshots
 

 

Path 
SRM IMG
T CodeSE80 → Internet Service → BBPMAINNEW → Display → Maintain HTML Template BBPMAINNEW

 

Settings 
~CLIENT100

 

Screenshots
 

 

Path 
SRM IMG
T CodeSM30 → TWPURLSVR

 

Settings 
Web serverZFRSAP02.FR.DS.CORP:8000
Web protocolHTTP
GUI start serverZFRSAP02.FR.DS.CORP:8000
GUI start protocolHTTP

 

Screenshots
 

 

2.5.2. Step 2: Select target for publishing

Path 
SRM IMG
T CodeSE80 → Internet Service → Utilities → Settings → Internet Transaction Server

 

Settings 
PublishOn selected site internal

 

Screenshots
 

 

2.5.3. Step 3: Publish

Path 
SRM IMG
T CodeSE38 → W3_PUBLISH_SERVICES → Select relevant templates → click “publish”

 

Settings 
Templates to selectAll headers beginning with “bbp”

 

Screenshots
N/a

 

Modifications on HTML Templates

To cover the requirements of EADS DS several modifications were made to the HTML Templates. Please refer to document TrIO_TDD_EBP 2006-01-23 HTML Spec v1-6.doc for further details.

 

  1. Master Data

3.1.   Catalogs

In the implemented scenarios demands are covered from catalogs. In order to use catalogs, they have to be defined in EBP.

3.1.1. Step 1 : Define Web Service

Path 
SRM IMGSupplier Relationship Management → SRM Server → Master Data → Define External Web Services  (Catalogs, Vendor Lists etc.)
T Code

 

Settings 
Web Service IDECC_PROD
DescriptionEADS DS Catalogs
Business TypeProduct Catalog
Do Not Check ProductYes
Use Error LogYes
Use HTTP Get to call Web ServiceYes
Technical Type of ServiceHTML

 

Screenshots
 

 

3.1.2. Step 2: Define call structure for Web Service

Path 
SRM IMGSupplier Relationship Management → SRM Server → Master Data → Define External Web Services  (Catalogs, Vendor Lists etc.) → Standard Call Structure
T Code

 

Settings 
Seq.10
Parameter Name<blank>
Parameter Valuehttp://eccprodclus.intra.corp/EnterpriseCatalog/jsp/clus_root.jsp
TypeURL
Seq.20
Parameter Namelan
Parameter ValueSY-LANGU
TypeSAP Field
Seq.30
Parameter Name— USERNAME
Parameter Valueds_all
TypeFixed Value
Seq.40
Parameter NamePASSWORD
Parameter Valueds_all2001
TypeFixed Value
Seq.50
Parameter NameHOOK_URL
Parameter Value<blank>
TypeReturn URL
Seq.60
Parameter Name~OkCode
Parameter ValueADDI
TypeFixed Value
Seq.70
Parameter Name~TARGET
Parameter Value_top
TypeFixed Value
Seq.80
Parameter Name~CALLER
Parameter ValueCTLG
TypeFixed Value

 

Screenshots
 

 

  1. Cross-Application Basic Settings

4.1.   Roles

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Roles → Define Roles
T CodePFCG

 

Following Roles have been created:

Role

Type

Copy of Standard Role

Transactions

YTF_EBP_EMPLOYEESingle RoleSAP_EC_BBP_EMPLOYEEShop, Check Status
YTF_EBP_MANAGERSingle RoleSAP_EC_BBP_MANAGERApprove

Note:

  • The role YTF_EBP_EMPLOYEE is designed for requestor users, who are supposed to create shopping carts.
  • The role YTF_EBP_MANAGER is designed for approver users, who are supposed to approve shopping carts.
  • In order to enable changes to the shopping cart during approval and to have the workflow react properly, the workflow security settings have to be set to “Medium”
    (Transaction PFCG -> choose role -> maintain -> personalization -> personalization key object = BBP_WFL_SECURITY set to “medium”).

4.2.   Organizational Management

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Organizational Management → Change Organizational Plan
T CodePPOMA_BBP

 

 
  


For details on the specification please refer to the attached PowerPoint file:

 

 

 
  


For details on the realization please refer to the attached Excel sheet:

 

Notes:

  • The responsible purchasing group is determined by the commodity group
  • As the attributes “CAT” and “CNT” are maintained on user level, they must be maintained manually after creating new users
  • The delivery address is defined on county division level (DS FR) and inherited to business units → users, default address must be flagged for user
  • Based on current requirements the only currency set up in the system is Euro. By adding additional currencies to the respective level (country node) in the organizational model, every currency can be handled by the EBP system.

4.3.   Number Ranges

Number ranges have to defined for the documents created by EBP (shopping cart, purchase order). The po number range is assigned to a transaction type (= document type in backend).

4.3.1. Step 1: Set the number range

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Number Ranges → SRM Server Number Ranges → Define Number Ranges for Shopping Carts and Follow-on Documents
T CodeBBNU

 

Settings 
No01
From number0010000000
To number0019999999
Extno
NoPO
From number0047000000
To number0047999999
Extno
NoPR
From number0090000000
To number0099999999
Extno

 

Screenshots
 

 

4.3.2. Step 2: Use the number range

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Number Ranges → SRM Server Number Ranges → Define Number Ranges per Backend System for Follow-on Documents
T Code

 

Settings 
Log SystemF40_100
Number range POPO
Number range PReqsPR

 

Screenshots
 

 

4.3.3. Step 3: Define transaction types

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Number Ranges → Define Transaction Types
T Code

 

Settings 
Transaction TypeEC
Int. Number RangePO
Trans. Cat.BUS2201

 

Screenshots
 

 

4.4.   Workflow

For workflow related customizing and development please refer to TrIO_TDD_EBP Workflow – Technical & Customizing_v3.doc

4.5.   Tax

The tax calculation like all financial processes will take place in the backend.

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Tax Calculation → Determine System for Tax Calculation
T Code

 

Settings 
Tax calculation occurs in R/3yes

 

Screenshots
 

 

4.6.   Account Assignment

Accounting data is suggested by EBP. Therefore several settings have to be made.

4.6.1. Step 1: Define account assignment category

Based on requirements the only account assignment type set up in the system is cost center. Every SAP account assignment category (i.e. assets, wbs elements, …) can be added later on if required.

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Account Assignment → Define Account Assignment Categories
T Code

 

Settings 
Account assignment cat.CC
DescriptionCost Center
ActiveYes
Backend acct. ass. Cat.K

 

Screenshots
 

 

4.6.2. Step 2: Define automatic g/l account determination according to product category and account assignment category

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Account Assignment → Define G/L Account for Product Category and Account Assignment Category
T Code


For details regarding the g/l account determination please refer to the attached Excel sheet.

 

Screenshots
N/a

 

4.7.   Objects in Backend System

The creation of follow on documents is defined per purchasing group

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders)
T Code

 

Settings 
Purch. Grp50000613
Category ID*
Int. Proc.Always external procurement
Ext. proc.Purchase order if item data complete, otherwise purch. req.
Purch. Grp50000614
Category ID*
Int. Proc.Always external procurement
Ext. proc.Purchase order if item data complete, otherwise purch. req.
Purch. Grp50000615
Category ID*
Int. Proc.Always external procurement
Ext. proc.Purchase order if item data complete, otherwise purch. req.
Purch. Grp50000616
Category ID*
Int. Proc.Always external procurement
Ext. proc.Purchase order if item data complete, otherwise purch. req.

 

Screenshots
 

 

4.8.   Application Monitors

In order to have application monitors available for administration usage, the monitors have to be activated.

Path 
SRM IMGSupplier Relationship Management → SRM Server → Cross-Application Basic Settings → Start Application Monitors
T Code

 

Settings 
N/aN/a

 

Screenshots
N/a

 

4.9.   Business Partner Number Range

Vendors are uploaded from the backend system. In order to enable the same vendor id like in the backend system, the number ranges have to be aligned.

4.9.1. Step 1: Define number range

Path 
SRM IMGCross-application components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Number Ranges
T CodeBUCF

Set number range F1 to comprise backend number ranges F1 and F2

 

Settings 
No01
From number0000000001
To number0000099999
ExtNo
NoF1
From number0000100000
To number0000199999
Extyes

 

Screenshots
 

 

4.9.2. Step 2: Define grouping

Path 
SRM IMGCross-application components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Groupings and Assign Number Ranges
T CodeBUCF

 

Settings 
GroupingEVEN
Short nameExt (BE) Vendor
DescriptionExternal Backend Vendors (FVEN-F1)
Number rangeF1
Ext.Yes
Ext. Std. Grp.yes

 

Screenshots
 

 

 

  1. Middleware Settings

Certain master data is uploaded from the backend system using the CRM middleware solution. Therefore the middleware has to be configured to enable the upload.

5.1.   R/3 Backend

Check SAP note 720819

Path 
SRM IMG
T CodeSM30

Check the following tables / entries

Settings 
CRMSUBTAB 
CRMRFCPAR 
CRMPAROLTP 

 

Screenshots
N/a

 

5.2.   SRM

5.2.1. Maintain Middleware Settings

Check SAP note 720819

Path 
SRM IMG
T CodeSM30

Check the following tables / entries

Settings 
SMOFPARSFA 

 

Screenshots
N/a

5.2.2. Maintain Industry Settings

Path 
SRM IMGCross-application components → SAP Business Partner → Business Partner → Organizations → Maintain Industry Systems and Industries
T Code

 

Settings 
Industry Systemebp
Standard SystemX

 

Screenshots
 

 

 

 

 

5.2.3. Maintain Middleware Site

Path 
SRM IMG
T CodeSMOEAC

 

Settings 
Nameoltp
Descriptionoltp
TypeR/3
Site Attributes RFCF40_100

 

Screenshots
 

 

5.2.4. Set Middleware Settings

Path 
SRM IMG
T CodeSE38 → BBP_PRODUCT_SETTINGS_MW

 

Settings 
UserEBP
Service Product ActiveX

 

Screenshots
 
  

 

5.2.5. Upload Data From Backend

Path 
SRM IMGSAPCRM_MENUE → Middleware → R/3 Data Exchange → Initial Download → Start
T CodeR3AS

 

Settings 
Load ObjectDNL_CUST_BASIS3
Source Siteoltp
Destination SiteCRM
Load ObjectDNL_CUST_PROD0
Source Siteoltp
Destination SiteCRM
Load ObjectDNL_CUST_PROD1
Source Siteoltp
Destination SiteCRM

 

Screenshots
 
  

 

  1. Appendix I: Multi Backend Capabilities of EBP

The mySAP SRM EBP solution is basically multi backend capable according to SAP. Nevertheless there are some limiting factors in the standard solution, which can easily overcome by standard enhancements using BADIs.

Based on the requirements for the EBP implementation at EADS DCS France the current EBP implementation is designed for France but can be easily enhanced for further countries.

  • Additional organizations can be easily added to the organizational model as it is already designed to encapsulate organization / country specific settings.
  • Additional languages will require additional maintenance of customer specific system messages in the respective language
  • Additional currencies can easily added in the organizational model
  • Additional backend systems can easily be connected to the EBP system on the standard way

However enhancements have to be checked before enhancing the EBP and eventually will have to be adapted. Known limitations from enhancements are:

  • Approver determination in approval workflow

 

 

 

  1. Appendix II: Remarks On system copy

7.1.   Copy of EBP

Some special factors have to be taken into account when copying EBP. Therefore the copy of an EBP system should be carefully considered.

Please refer to the Excel task list attached. In addition please refer to the official SAP guide how to copy and transport EBP systems.

 

7.2.   Copy of R/3

Connection between R/3 and EBP has to be checked and eventually corrected

  • RFC-connection (see above chapter 2.1)
  • ALE-connection (see above chapter 2.2)

Special attentions has to be given to the number range. When copying the backend on a periodic basis without the EBP, the number range for purchase documents will deviate between the two systems and will have to be remaintained according to chapter 4.3.

Talk to Us

1-419-408-3178

1-419-408-3178

Fees

$500.00

Curriculum

Topics for this course

Free Career Counselling



    Training Review

    Add testimonial description here. Edit and place your own text.

    John Doe

    Codetic

    Training FAQ