SRM 7 - Centralised Contract Management SAP XI inbound/outbound interfaces

Hi there,
We are busy implementing SRM 7 and I would like to get "centralised contract management" working between SRM 7 and the ECC backend/s (via SAP PI).
Could you please let me know what the correct SAP PI CONTENT to load is? And what the correct service interfaces I need to use for this scenario as well as what "software component version" and "namespace" I can find them in?
Any guide on the details of this specific scenario?
Thanks for the help, much appreciated
Lynton

Note 1268821 - SRM 7.0 / ERP 6.04: Config. of Central Contract Management
Settings in PI
=================
For CCM scenario to work, PI set up is required for the following asynchronous enterprise services.
(Namespace; Software Component Version; Interface:)
http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchasingContractSRMReplicationRequest_Out
http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchasingContractSRMReplicationRequest_In
http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchasingContractSRMReplicationConfirmation_Out
http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchasingContractSRMReplicationConfirmation_In
http://sap.com/xi/APPL/Global2; SAP APPL 6.04; PurchaseOrderERPContractReleaseNotification_Out
http://sap.com/xi/SRM/SE/Global; SRM SERVER 7.0; PurchaseOrderERPContractReleaseNotification_In
Settings in SAP Enterprise Portal
=================
Please refer to paragraph Settings in the Enterprise Portal in note 1263876.
Notes to be implemented
=================
Notes 1262480, 1252865, 1263470, 1260829

Similar Messages

BPCA - Portal Changes and Inbound/Outbound Interfaces

Hello Solman 7.1 Experts,
Currently involved in a BPCA implementation and have a question regarding that. In an SAP landscape Can BPCA be used to detect changes made in Portal and Inbound/Outbound Interfaces.
Most of the SAP documentation that I have come across so far speak to the functionality but hasnt covered scope. I would really appreciate your input.
Thanks,
-Anshul

Hi Thorsten,
I faced the same problem while i was trying to select the interfaces while configuring the scenario in ID.
I could not found any interfaces after i selected my Business System for the sender.
Solution: Go to the SLD.
In the technical system Go to the
Technical System------> Installed Software (TAB) and add the Product name under this tab as it appears in the IR.
After this you need to go to the corresponding business system
Business System-----> Installed Software (TAB) check the installed products under this tab.
This has done the solution for me.
Hope this will help.
Thanks
Ajay

Oracle EBS Inbound/Outbound Interface build using Oracle SOA 11g

Hi SOA Guru's,
I am very much new to SOA 11g, could you guy's help me in understanding "How I can build any Oracle EBS Inbound/Outbound interface using Oracle SOA 11g"
It will be great if anybody explain me with any example script/screen shot/document.
Thanks in advance.
Regards
Pankaj

I don't have any experience with ebs, but i assume it works like this.
In the composite editor you will find a list adapters at the right..over here you will also find the oracle applications (ebs) adapter.
This will be the component for you which will communicate with the ebs packages.
you need to drag this adapter on the swim lane, and after that you should create the composite application like the way it's described in the tutorials Oracle supplies, put a mediator component in the middle and expose this interface (drag the line to the left swim line)
Hope it's a bit clear like this ?
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/fod_intro2.htm
this should make a few things clear too

Need sample programs for inbound & outbound interfaces in abap hr?

hi friends
i need sample programs for inbound & outbound interface programs in hr abap . any one send me pls
thanks & regards
deepurd

&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Report ZPROG65_11 *
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
REPORT zprog65_11 .
TABLES : lfa1.
TYPES : BEGIN OF ven ,
lifnr LIKE rf02k-lifnr,
bukrs LIKE rf02k-bukrs ,
ekorg LIKE rf02k-ekorg,
ktokk LIKE rf02k-ktokk,
name1 LIKE lfa1-name1,
sortl LIKE lfa1-sortl,
land1 LIKE lfa1-land1,
spars LIKE lfa1-spras,
akont LIKE lfb1-akont,
fdgrv LIKE lfb1-fdgrv,
waers LIKE lfm1-waers,
anred LIKE lfa1-anred ,
END OF ven .
DATA : t_ven TYPE TABLE OF ven WITH HEADER LINE ,
t_bdc LIKE TABLE OF bdcdata WITH HEADER LINE .
DATA : v_file TYPE string ,
v_temp TYPE i ,
v_lifnr(10) TYPE n,
v_hdate LIKE sy-datum.
DATA : c_tcode LIKE sy-tcode .u201Dvalue u2018XK01u2032.
PARAMETERS : p_file(30) DEFAULT u2018c:\vendor1_11.txtu2019,
p_group LIKE apqi-groupid.
START-OF-SELECTION .
MOVE p_file TO v_file .
PERFORM file_upload TABLES t_ven USING v_file .
v_hdate = sy-datum - 1.
CALL FUNCTION u2018BDC_OPEN_GROUPu2019
EXPORTING
client = sy-mandt
DEST = FILLER8
group = p_group
holddate = v_hdate
keep = u2018Xu2019
user = sy-uname
IMPORTING
QID =
EXCEPTIONS
client_invalid = 1
destination_invalid = 2
group_invalid = 3
OTHERS = 11
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT t_ven .
clear lfa1.
v_temp = 0.
MOVE t_ven-lifnr TO v_lifnr.
SELECT SINGLE * FROM lfa1 INTO lfa1 WHERE lifnr =
v_lifnr.
IF sy-subrc = 0.
WRITE :/ u2018foundu2019.
v_temp = 1.
else.
write: / u2018not foundu2019.
ENDIF.
IF v_temp = 0.
c_tcode = u2018xk01u2032.
PERFORM fill_ddc_table .
ELSEIF v_temp = 1.
c_tcode = u2018xk02u2032.
PERFORM fill_bdc_table .
ENDIF.
CALL FUNCTION u2018BDC_INSERTu2019
EXPORTING
tcode = c_tcode
TABLES
dynprotab = t_bdc
EXCEPTIONS
internal_error = 1
OTHERS = 7.
REFRESH t_bdc .
ENDLOOP .
CALL FUNCTION u2018BDC_CLOSE_GROUPu2019
EXCEPTIONS
not_open = 1
queue_error = 2
OTHERS = 3.
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form file_upload
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013>P_T_VEN text
u2013>P_V_FILE text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM file_upload TABLES p_tven STRUCTURE t_ven
USING p_vfile.
CALL FUNCTION u2018GUI_UPLOADu2019
EXPORTING
filename = p_vfile
filetype = u2018ASCu2019
has_field_separator = u2018Xu2019
IMPORTING
FILELENGTH =
HEADER =
TABLES
data_tab = p_tven
EXCEPTIONS
file_open_error = 1
file_read_error = 2
OTHERS = 17
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. u201D file_upload
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form FILL_DDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013> p1 text
<u2013 p2 text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM fill_ddc_table .
SCREN 100
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180100u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-LIFNRu2019.
t_bdc-fval = t_ven-lifnr .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-BUKRSu2019.
t_bdc-fval = t_ven-bukrs.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-EKORGu2019.
t_bdc-fval = t_ven-ekorg.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-KTOKKu2019.
t_bdc-fval = t_ven-ktokk.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
110
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180110u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-NAME1u2032.
t_bdc-fval = t_ven-name1 .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SORTLu2019.
t_bdc-fval = t_ven-sortl.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-LAND1u2032.
t_bdc-fval = t_ven-land1.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SPRASu2019.
t_bdc-fval = t_ven-spars.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
120
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180120u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
130
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180130u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=ENTRu2019.
APPEND t_bdc. CLEAR t_bdc.
210
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180210u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFB1-AKONTu2019.
t_bdc-fval = t_ven-akont .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFB1-FDGRVu2019.
t_bdc-fval = t_ven-fdgrv.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
215
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180215u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
220
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180220u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
310
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180310u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFM1-WAERSu2019.
t_bdc-fval = t_ven-waers .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
320
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180320u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=UPDAu2019.
APPEND t_bdc. CLEAR t_bdc.
ENDFORM. u201CFILL_DDC_TABLE
u201D FILL_DDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
*& Form FILL_BDC_TABLE
&u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014
text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
u2013> p1 text
<u2013 p2 text
u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014u2014-
FORM fill_bdc_table .
SCREN 101
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180101u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-LIFNRu2019.
t_bdc-fval = t_ven-lifnr .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-BUKRSu2019.
t_bdc-fval = t_ven-bukrs.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018RF02K-EKORGu2019.
t_bdc-fval = t_ven-ekorg.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
110
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180110u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018lfa1-anredu2019.
t_bdc-fval = t_ven-anred .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-NAME1u2032.
t_bdc-fval = t_ven-name1 .
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SORTLu2019.
t_bdc-fval = t_ven-sortl.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-LAND1u2032.
t_bdc-fval = t_ven-land1.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018LFA1-SPRASu2019.
t_bdc-fval = t_ven-spars.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018/00u2032.
APPEND t_bdc. CLEAR t_bdc.
300
t_bdc-program = u2018SAPMF02Ku2019.
t_bdc-dynpro = u20180300u2032.
t_bdc-dynbegin = u2018Xu2019.
APPEND t_bdc. CLEAR t_bdc.
t_bdc-fnam = u2018BDC_OKCODEu2019.
t_bdc-fval = u2018=YESu2019.
APPEND t_bdc. CLEAR t_bdc.
ENDFORM. u201D FILL_BDC_TABLE
Best Regards

Customizing Master Contract Management - SAP Banking 6.0

Hello,
i am customizing the Master Contract Management in Banking 6.0 - especially the Effective Cash Pooling Feature.
On defining the restriction rules i have a problem:
How do i define the methods and the rule-id's for Cash Pooling.
Where is the connection between the methods and the rule-id's ?
The SAP documentation is very unclear in this special topic.
Tnx
Sebastian

Francesco Martire wrote:
> - install EHP4 without installing any Java stack
Yes, it is, as informed above;
> - activate (for example) HCM_TMC_CI_1, HCM_TM_ANALYTICS_1, HCM_OSA_CI_1 and CA_HAP_CI_1
They're ABAP, right? So, YES, you can activate them;
> - customizing Performance Management though its transactions
This is mostly an application question, so you need to refer to their documentation or on their forum;
> - use BAPIs and BADIs from custom presentation logic
Same as above;
> ...or is some business logic affected by not installing Java and EP?
From a technical point of view, there's no interdependency between ABAP <-> Java regarding the functionality of the system. This means in you can install/uninstall (or have/don't have) them apart that each components/transactions will work w/o problems. However, you should check with Application about potentially limitations/problems on this matter.
I hope this information clarifies.
Best regards,
Tomas Black

SRM Central Contract Management with Service Hierarchy

Hello Gurus !
Is it possible to use the export/import functionality (with the business function SRM_CONT_IMPR_2) for changing/adding the service hierarchies in SRM Central Contract? I see the SAP note that the hierarchies are not supported for Purchase Order.
Any idea?
Thanks in advance
Regards
Raj

Hi Raj,
it's not supported for contracts either.
Regards,
Zsofi

No inbound/outbound interfaces for Business Systems

Hi,
after upgrading from XI 3.0 to PI 7.1 there are no inbound and outbound interfaces in the Communication Component definition for our Business Systems any more.
We didn't change anything in SLD.
Does anybody know why these entries are lost in 7.1?
Regards
Thorsten

Hi Thorsten,
I faced the same problem while i was trying to select the interfaces while configuring the scenario in ID.
I could not found any interfaces after i selected my Business System for the sender.
Solution: Go to the SLD.
In the technical system Go to the
Technical System------> Installed Software (TAB) and add the Product name under this tab as it appears in the IR.
After this you need to go to the corresponding business system
Business System-----> Installed Software (TAB) check the installed products under this tab.
This has done the solution for me.
Hope this will help.
Thanks
Ajay

Contract Renewal - Entire Contract - Service Contract Management - SAP Library

To add a comment, please log in or register on the top of this page and choose Reply. Please write your comment in English.
You can also go back to the SAP help page.

Hi
Renewal of contract.
Suppose for the line item 1, the contract is expired...then enter the same item as line item 2 and then GOTO - - > ITEM --> Contract Data...and enter the contract date
Bala

Contract Renewal - One Item Only - Service Contract Management - SAP Library

To add a comment, please log in or register on the top of this page and choose Reply. Please write your comment in English.
You can also go back to the SAP help page.

They might be doing you a favour. Many people are having problems with HH3 and the smart money is on keeping version 2.
By the way, I think the cooling-off period ends as soon as you start using the service, which probably means that there effectively isn't one.
You can click the white star next to this message if you think it was helpful.

What is Outbound Interface

Hi Experts,
Could one explain to me
What is outbound Interface,what is the purpose of Outbound interface and what is the use
Thanks & Regards
Vikas Raj

Hi,
The interface through which data comes inside SAP is inbound interface on the other hand the interface through which data goes out of SAP is called outbound interface.
Rgds
Mayank

ABAP-HR OUTBOUND INTERFACE

HELLO EXPERTS,
Plz provide me with any sample code for outbound interfaces in abap-hr as i'm new to this concept.
Thanks,
Naveen Sharma

Dear Naveen,
would you mind checking this site? Perhaps you find some useful information.
<a href="http://erpgenie.com/abaptips/content/view/302/62/">ABAP Inbound/Outbound interfaces iDoc - User Exits</a>
Kind regards,
Zsolt

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

Using SRM for very large contracts and contract management

We are doing an SRM 7.01 implementation project. SRM will be used primarily for outsourced contract management. The contracts are all services associated with facilitites (plant) maintenance and also support services like cleaning or catering.
They have very large numbers of items priced individually (e.g. 10,000) per contract. The items price depends on the location the work is expected to be performed. The location is represented in SAP RE-FX architectual object. The price can be priced at any level of the hierarchy e.g. service A is priced the same across the whole state but service B is priced per campus.
q1. SAP advises that there are performance limitations on SRM contracts >2000 lines. Has anyone experience in a solution to provide very large contracts in SRM? How did you do it please?
q2. SAP advises to use the plant to represent the location for pricing purposes, but this would result in a very large number of plants. Has any one experience in alternative solutions to for variable location pricing in SRM contracts please? I.e. like integrating the RE-FX architectural object or similar into contract and PO line items.
thanks very much

Hi Prakash,
SRM does provide the facility of contract management with the help of Purchase Contracts and Global Outline Agreements but it is used as part of the sourcing for materials and services. The materials or services have contracts against some given target value against which PO is released. The contract is based on a material number ( eithe material or a service) which will be used as a source of supply during the creation of the Shopping Cart. It might not really fit in the scenario of carrier and freight forwarders but still can be customized for this kind of use.
The contract management functionalities in the R/3 space can also be looked on for this purpose.
Reg
Sachin

SRM 7.0 / ERP 6.04: Config. of Central Contract Management

Hello,
I want to configure the newly introduced integrated Procure-to-Pay Scenario Central Contract Management.
I found SAP Note number 1268821 where all tasks are described in order to implement the previous scenario.
For correct implementation, business function "Purchasing - SAP SRM Integration" (LOG_MM_P2PSE_1) activation is required in the ERP Systems.
When I run SFW5 t-code in order to activate the previous business function, SAP system gives an alert message.
What are the consequences of this business function activation ??
Thank you
Michele

Hi Michele,
I don't think there will be any consequences, we had certain warning messages aswell when we activated the business functions in ECC 6. Reading the warning messages we could conclude it wasn't any serious problem.
Details on functionalities included in a business function can be viewed here: [http://help.sap.com/erp2005_ehp_04_sp/helpdata/en/42/fbded750e61febe10000000a422035/frameset.htm] -> Business Functions (SAP Enhancement Package 4 for SAP ERP 6.0) -> Business Functions in SAP ERP -> Logistics -> Materials Management -> Procurement - SRM Integration
Kind regards,
Tim

SRM addon with Contract Management

SRM Gurus,
We are in the verge of installing SAP SRM system. Our main focus will be on :
1. SSP
2. Contract Management
3. Catalog Management
Please clarify what are the pros and cons of using SRM as ADD-on or SRM as seperate instrance.
If we can use contract management with SRM addon as a leading contract system without creating them in ECC6.0
Kaushik

The SRM AddOn is targeting on customers that are aiming on a simple procurement scenario, do not yet use mySAP SRM, are using only one Backend (ECC) system and aim to install SRM with a low TCO.
The following scenarios are released within the SRM AddOn:
Service Procurement (local deployment)
Self-Service Procurement (classic deployment)
SUS in connection with both scenarios mentioned above
Catalog Content Management
This also includes:
operational usage of contracts (e.g. for the assignment of sources of supply)
RFP - as far as known from the Temporary Labor scenario
Please be aware that the following deployment and migration constraints apply:
ERP 2005 with SRM as an add-on does not support any multiple-backend functions or hub deployment for procurement
Upgrade or migration from an existing SRM system to ERP 2005 with SRM as an add-on is not supported.
SAP does not offer migration paths from an SRM AddOn deployment to a deployment with a standalone SRM system.
The extended classic deployment is not supported.
The SRM as an add-on is only supported in the release combination ERP 6.0 and SRM 5.0. Other release combinations are not supported. Also future SRM releases will not run as an add-on on ERP 6.0
for more info
Read note 963000
and thread
SRM as an add-on to ERP 2005
BR
Dinesh

SRM 7 - Centralised Contract Management SAP XI inbound/outbound interfaces

Similar Messages

Maybe you are looking for