ERP Backend release with SRM 7.0

Hello
Is there a requirement on the ERP backend release when implementing SRM 7.0?
Thanks!
Christa

Hello
Thanks for your reply, but what I meant, is that can SRM 7.0 be used together with ERP 2004, or does it have to be ECC 6.0 with EhP4?
Best Regards,
Christa

Similar Messages

ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

"Backend systems with Release 701 are not supported " - ECC 6.0 to SRM 5.0

Hi ,
I have 2 doubts .
1. We are getting Error "Backend systems with Release 701 are not supported " while replicating vendors from ECC 6.0 backend system to SRM 5.0 system.
There are some notes on simillar topic but are not for SRM 5.0 ,suggested on SDN. an anyone please suggest what need to be done for the same.
2. Can we replicate Vendor Master Data with Contact Person from SRM to ECC system ? if yes, How ?
Regards
Narendra

answer 1:-
Note 1372175 - BBP_VENDOR_GET_DATA_JOB "Back-End Systems Not Supported"
On recent upgrade of the ECC back-end system to release '701' the program BBP_VENDOR_GET_DATA_JOB is getting errored out. If you are using SRM 5.0 , SRM_SERVER 550 with ECC backend Release 701 you encounter the above reported problem
Other terms
Vendor Replication Job, Release 701, Backend not supported, BBP_VENDOR_GET_DATA_JOB
Reason and Prerequisites
The program does not consider the release 701
remote_release EQ '700' OR remote_release EQ '701'.
OR
bbp_vendor_get_data - DEBUG what ois the remote_release 700 or 701?
Muhtu

Creation of multiple contracts in ERP backend from 1 GOA in SRM

Hello fellow SRM'ers, we are on SRM 5.5 and we have a scenario where we create a GOA in SRM and it get's created as a contract in the ERP backend system. This is working fine. Now our client would like to have multiple contracts created in the backend, one for each company when the GOA is saved. I found OSS note 646903, statement #2 that explains how to code the badi bbp_ctr, but is this all that is required to do this? It seems to me that the code in BBP_CTR will only create 1 contract/idoc. Can anyone tell me how we generate an idoc/contract that we want to create in ERP backend? Or is this how it's done?
Points will be rewarded for usefull answers. I have read most of the posts on this forum and have not found any answers yet.
Thanks,
Marty

Hi,
Please go through the below explanation from SAP documentation which says the no of contracts that would be created in the backend depends on
--If you activate grouping logic for locations in GOA from SPRO under cross aplication settings, items belonging to the same release-authorized purchasing organization, but different locations, can be grouped together into one backend contract. This requires a 1:1:1 relationship between an item, the release-authorized purchasing organization, and the location. This means that for each item, you can only assign one release-authorized purchasing organization, and one location, in order to release the GOA.
If you do not select this indicator to activate the grouping logic for location, a separate backend contract is created for each item belonging to the same release-authorized purchasing organization, but with different locations. Only items referring to the same release-authorized purchasing organization and location can be combined into one backend contract.---
So the bottomline is by default, when we distribute one separate contract is created for each location.
Hope this clarifies.
Regards,
RRK

Backend System with Release 701 are not supported

SRM 5.0
Extended Classic Scenario
CCM 2.0
When updating the vendors in SRM system using TC - BBPUPDVD getting the below error message :-
Backend System with Release 701 are not supported
Have checked in table - BBP_BACKEND_DEST, the backend entry is properly maintained.
Can any one advice.
Regards,
Jayoti
Edited by: SAP jayoti on Dec 7, 2010 1:11 PM

The problem is resolved for vendor relication after applying the below notes 1313972 and 1372175.
ECC sandbox seems to be in 701 release. When the backend system ECC is in release 701, vendor replication fails with the error message that 'Backend system release 701 not supported'. We need to apply notes 1313972 and 1372175 to fix this issue. I have applied them in Sandbox and the issue is resolved now.

BBPGETVD - error:backend systems with release 700 are not supported

Hi,
When I am trying to replicate vendor data from EEC to crm 4.0 via BBPGETVD.
I get the error message"backend systems with release 700 are not supported"
Is anyone have Idea what is wrong? and how can fix it?
Thanks,
Rachel

Yossi,
I believe that standard transaction does not work with ECC 6.0. The standard response would be to upgrade your CRM system to 5.0 so that you can download vendors from ECC 6.0.
Bascially the vendor replication programs in CRM below 5.0 aren't really that reliable for delta downloads(one error will cause an entire load to fail). So you probably at best should copy the SAP standards to generate custom load programs as a starting point.
It is not too difficult and overcomes some of the restrictions that SAP puts in place(i.e. you can only use one number range for vendors downloaded, etc.). This is definitely one of the weak points of CRM 4.0 that was fixed in CRM 5.0.
If you have more questions on this let me know.
Take care,
Stephen

'Backend systems with Release 701 are not supported'

while BBPGETVD transaction is run below error is seen,
'Backend systems with Release 701 are not supported'
Please help to resolve it.

Hi
What is your backend system ECC version?
What is the configuaration in Define back end system?
Note 1313972 - BBPGETVD: Backend system latest release not supported
br
muthu

BBPGETVD throwing an error -Backend system with release 701 are not support

Experts,
After changing the Backend connection from R3 4.6c to ECC6 sysem in our BBPCRM4.0,
the transaction "BBPGETVD" is not working, which is throwing an error as
"Backend system with release 701 are not supported".
Already we have applied some of the notes (822883 &862290)
Thanks
Ahamed

Are you able to replicate other data like plants, product categories from the same backend system or are you facing the same error?
Also please check the logical system and see if they are assigned to the client correctly. (in SPRO settings)
Thanks,
Prashanth

Vendor replication in One client ERP, with SRM 5.0 version

Hi Guys,
Can anyone suggest me how to do the vendor replication in the One client ERP i.e SRM is being on the same stack of the SAP R/3 system. which is set as a one of the node in the SAP R/3 SPRO path. this is in Version 5.0.
Please suggest how to do the Vendor replication in this, whether are there any prerquisties for doing this replication?
The VenMap Table is not getting updated with entries.
Please help me soon.
Regards
Srujan K

Hi
no ranges you need to take care of this if you want to transfer same no range as ECC no range.
slg1 - you can see logs
bucf - no range for vendors
+SAP Implementation Guide
++Cross-application components
+++SAP Business Partner
++++Business Partner
+++++Basic Settings
++++++Number Ranges and Groupings
+++++++Define Number Ranges
+++++++Define Groupings and Assign Number Ranges
sorry. do you want Suggestion ECC as well as SRM in one client?
Master Data Synchronization in mySAP ERP
Purpose
In order for the Supplier Relationship Management (SRM) application to run as add-on in a mySAP ERP environment, it is necessary to synchronize master data objects within this platform, that are similar from a business point of view, yet technically different.
Master data objects on ERP and SRM side that need to be synchronized
ERP (SAP ECC*)
Corresponding object in SRM
Vendor
Business partner
Material/service
Product
Material type/service type
Product category
ECC: Enterprise Core Component
Integration
Master data synchronization in ERP is carried out centrally.
For more information, see: Master Data Synchronization
Once you have set up master data synchronization for your objects using the Synchronization Cockpit, and after initial data synchronization and key mapping has been completed, delta reports that run in the background ensure that master data is always matched.
The individual configuration steps are described in the IMG:
Supplier Relationship Management ® SRM Server ® Master Data ® Master Data Synchronization in mySAP ERP (One Client)
Features
This function ensures that changes (create, change, delete) that are made to objects on one side cause immediate (bidirectional) update to the same objects on the other side. In this way, SRM and ECC data is permanently synchronized.
·         Purchasing organizations are not included in the automatic bidirectional master data synchronization and, as is also the case with mySAP SRM, have to be matched manually or via an update report (ECC -> SRM).
Replication (and the updates) from plant (MM) to business partner location (SRM) only occurs in one direction with the report BBP_LOCATIONS_GET_FROM_SYSTEM that is executed manually.
·         Where SAP Supplier Self-Services (SUS) runs together with mySAP SRM on one ERP platform, master data synchronization occurs as described above. If SUS runs separately of ERP, SAP NetWeaver XI is used to synchronize master data with SRM.
Master Data Synchronization
Purpose
Master data synchronization synchronizes master data objects in an SAP system that are similar from a business, but not from a technical, point of view, and in this way allows you to integrate different SAP applications seamlessly in your business processes.
You can use master data synchronization, for example, to set up integration of the SAP Business Partner with the customer master. This allows you to integrate SAP applications that make technical use of the Business Partner in their user interface, and use the customer master as a technical basis in subsequent business processes.
Implementation Considerations
In order to be able to use master data synchronization, you must have defined and activated Synchronization Control as well as Customer/Vendor Integration and/or Material/Service Integration in Customizing of the Cross-Application Components under Master Data Synchronization.
Pay attention to the following note on master data synchronization terminology:
The paired terms, customer/debtor and supplier/creditor/vendor, are used with the same meaning in master data synchronization, and one term can be substituted synonymously when the documentation is read.
Integration
Master data synchronization is based in particular on the two master data objects SAP Business Partner and SAP Product, and makes it possible for the following synchronization processes, among others, to be carried out:
·        Synchronization of the business partner with the customer/debtor master
·        Synchronization of the business partner with the supplier/creditor master
·        Synchronization of the product with the material master
·        Synchronization of the product with the service master
For a complete list of all synchronization processes that are defined and active in an SAP system, see the synchronization cockpit under Synchronization Processes.
Master data synchronization replaces the current technical solutions for Customer/Vendor Integration and complements some business processes that are based on integration between the product master and the material or service master (Material/Service Integration).
Master data synchronization also has an effect on the archiving processes of the master data objects business partner/customer master /vendor master and product/material master /service master.
For more information on activating/deactivating synchronization processes, see the IMG of the Cross-Application Components under Master Data Synchronization ® Synchronization Control.
Features
Synchronization Directions
A synchronization process is always defined as a one-way synchronization between a source object type and a target object type, meaning that the synchronization is only ever active in one direction, from the source object type to the target object type. If the data of an object instance of the source object type is changed, the corresponding data in the corresponding object instance of the target object type is changed at the same time. Both synchronization directions must be activated in the SAP system in order to allow the undirected synchronization of two master data object types.
Synchronization Scenarios
There are two synchronization scenarios in master data synchronization:
·        Synchronization from the master data maintenance
When you create and save new master data, the system carries out initial synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and creates the corresponding master data.
If you change existing master data that has already been synchronized, the system locks this master data, and all the corresponding master data of the source object type and the target object type during maintenance. When you save the changed master data, the system generally carries out a delta synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and changes the corresponding master data. In some cases, changing existing master data can lead to a delta synchronization having to be carried out.
·        Synchronization using the synchronization cockpit
You use the synchronization cockpit to prepare, perform and check the initial synchronization of master data objects in an SAP system.
Constraints
Master data synchronization can neither synchronize master data objects across systems, nor can it transfer master data objects from external or legacy systems. You can use the SAP external data transfer to transfer legacy or external data.
Synchronization Cockpit
Definition
User interface for master data synchronization in an SAP system.
Use
Using the synchronization cockpit, you can carry out all the steps for master data synchronization in an SAP system These are as follows:
·        Customizing synchronization
·        Selection, preparation and starting of synchronization runs.
·        Monitoring of synchronization runs
·        Postprocessingof synchronization errors
·        You can start the synchronization cockpit in Customizing of the Cross-Application Components under Master Data Synchronization ® Synchronization of Mass Data ® Execute Synchronization Cockpit.
Before you can work with the synchronization cockpit, the following prerequisites must be fulfilled:
·        There are data records for at least one source object in the SAP system.
·        You are authorized to carry out synchronization.
·        You are authorized to start the Postprocessing Office (PPO).
·        You have carried out the Customizing of the master data synchronization.
·        You have carried out the general Customizing for the PPO.
For more information, see the Implementation Guide (IMG) of the Cross Application Components under General Application Functions ® Postprocessing Office.
·        You have activated the writing of PPO orders for the master data objects in Customizing of the master data synchronization.
For more information see the Implementation Guide (IMG) of the Cross-Application Components under Master Data Synchronization ® Synchronization Control ® Activate PPO Orders for Platform Objects in the Dialog.
Structure
The synchronization cockpit is divided into three work areas:
·        Synchronization processes work area
This work area contains a list of the synchronization processes. The list displays only the active synchronization processes, or all the synchronization processes. You can change between the two views at any time.
·        Customizing synchronization work area
This work area contains an overview of all the reports that you can use for the Customizing synchronization.
·        Synchronization work area
This work area contains the tab pages Processing and Monitor, which you can use to prepare or monitor synchronization runs.
Integration
The Postprocessing Office (PPO) is integrated in the synchronization cockpit, so that it can be used to postprocess synchronization errors. If the PPO has not been activated, the synchronization cockpit does not start synchronization in the case of an error, and issues the relevant error message.
br
Muthu

External requirement with SRM 7.0 & ERP 6.0 enhancement package 4

hi experts
we are using SRM classic scenario with SRM version 7.0 & ECC 6 EHP 5.
PR with document type NB is updating on SRM successfully.
but when I try with service PR with item category "D" is not updating.
i have few query.
like.
by this scenario can we transfer PR with item category D with service line?
please suggest anyone .
Regards
Vijay Patil

Hi,
Refer to below threads (these are not answered threads, but it may help you).
http://scn.sap.com/thread/3579279
http://scn.sap.com/thread/3611581
Ganapathi

Creation of backend contract from SRM system?

Dear Experts,
I am bit confused with the scenario of creation of backend contract from SAP SRM system? It says in few cases, based on the BAdi 'BBP_DETERMINE_Logsys', the system creates a backned contract directly in a backend ERP system. Why do we need when we have central contract?
We can meet the same requirement through central contract where we will authorize only purchasing organizations of a backend system and block the contract for local sourcing in SRM?
Secondly, How to find a contract / scheduling agreement created in a backend system when a central contract is distributed to the backend system?
Thanks and regards,
Ranjan

Hello Ranjan
question on contracts?
Note 1476307 - Importing parameter not filled in BADI BBP_DETERMINE_LOGSYS
in classic scenario , The Business wanted to create a contract from cockpit or via BID
this BADI helps
Symptom
You have implemented BAdi BBP_DETERMINE_LOGSYS to control the system in which contract is created in following scenarios:
1. Creation of contract from an accepted quote / bid.
2. Creation of contract from a requisition in SOCO.
In the method IF_EX_BBP_DETERMINE_LOGSYS~CONTRACT_LOGSYS_DETERMINE of the BAdi implementation, importing parameter IT_ORG doesnot have any values.
Other terms
Backend contract
Reason and Prerequisites
some business wants to create a backend contract from SRM . see some Dinesh Powale / Claude threads for more understanding.
Muthu

System copy (backend and/or SRM)

Hi
we have more than one backend connected to SRM. Sometimes our Q-system is copied (refreshed) from the productive system. If we do a alligned copy (all systems SRM and ERPs) the new Q-landscape is of course fine.
In future, we'd like to decouple the system refreshments. Meaning: only one backend will be refreshed without SRM, or only SRM will be refreshed without the backends.
Does anybody have experienc with that? What do you do to reconstruct testable data (mainly POs) in both cases?
Info: We're using the extended classic scenario.
br,
Richard

my understanding is that you need to copy the connected system ( ECC) along with SRM. If only one system is refreshed, then the material master replication and other similar configuration whcih are based on GUIDs may not work properly. I have never tried /worked on system whcih are refreshed the way you have mentioned.
Pl let me know your views.
Thanks
velu

Open Shopping Cart from ERP Backend

Hi,
we are on SRM 7.01 and ECC 6.0 as ERP Backend.
How can i open a shopping cart with the shopping cart number?. Can i open the shopping cart per URL?
We have the shopping cart number in ERP Backend.
Best regards,
Benjamin Herzig

Hi,
erp users should be able to open the shopping cart with one click from sap gui me53n.
At the moment, they have to copy the shopping cart number and then open the SAP Portal and search for the shopping cart. This is not very userfriendly.
Can i use any remote function in srm calling from the erp?
I´m surprised that nobody else needs such as feature!
Best regards,
Ben

Transfer the PR from ERP 6.0 to SRM for

Hi SRM profis,
we are using SRM 7.02 (AddOn) classic scenario. Can someone explain how to transfer the PR from ERP 6.0 to SRM for
approving only.

Hi,
I think this could not be explained in one post.
We are using the same above scenario for transferring PS or PM requisition to SRM for approval only.
Lot of conditions are set.
1.     Landscape
2.     Process -
3. Criteria for transferring and approving PReq’s in SRM should be defined in ECC
for example - The criteria which PReq’s should be transferred to SRM should be defined in a local customizing table XXXXX with the field purchasing organisation, plan account assignment type and update date of PReq.
4.   1st approver selection criteria should be setup in the ECC
5.     When creating or updating a PReq item a workflow event will be triggered to start the transfer workflow. The trigger is implemented in the PM and PS BADI workorder_update while saving the PM order or the PS network order. The same event cancels an eventually transfer workflow which just transfers a previous version of the PReq, or waits for the approval result of a previous version.
6.     The Release Strategy has to be maintained in the productive systems. Only the release codes will be defined and distributed centrally. The name of the Release Strategy can be chosen locally. It’s very important that a release strategy fits to the values of the purchase requisitions that come from SRM and that go to SRM. It doesn’t matter which release strategy. If no existing release strategy fits to the values of the purchase requisitions a classification of the new release strategies is necessary. Otherwise no classification for the new release strategies is needed.
7.     Also need to do MM specific customization , PI related and SRM related.
I think it would be too much to tell everything through a post.
Please ask a specific question then i would be able to help you more.
Thanks.
from RBEI
Snehal

Finding ERP Purchasing organisation using SRM Purchasing organisation

Hi Experts,
I have a requirement in which i need to know ERP Backend Purchasing organisation using SRM Purchasing organisation or Business partner.
Can anybody tell me any sap table or function module that i can refer to fulfill this requirement.
We are using SRM 5.0
Thx in adv,
Tirumala

HI,
Please execute FM BBP_PDH_PO_DET_BE_PUR_ORGS (SE37) only by passing BP number, you would get the ECC purchasing
organisation value.
Or
Try try with this BBP_OM_READ_PURCH_ORG_BE by passing Org. Id of EBP Purchasing Organisation.
Did you try any of the above in SE37 ?
I tried in my system and i got the same in both the cases.
Thanks
Rajesh K

ERP Backend release with SRM 7.0

Similar Messages

Maybe you are looking for