SRM 4.0: distributing contracts to legacy backend

Hello!
I am programmer fairly new to SRM. At the moment I am trying to figure out how to distribute purchasing contracts from SRM to legacy via XI. There is apparently no XML ouput option in 4.0.
By reading docu I have found one possible way I think, and I just wanted to run it by you to see if it is doable at all.
I was thinking I can use the build in functionality to create the contract in a R/3 backend system. Using the BADI BBP_CTR_BE_CREATE, which actually just creates an IDoc (or?) and the BBP_DETERMINE_LOGSYS I could just route it to XI instead of R/3.
Do you experts see any reason why this would not work?
Any help appreciated!
Thanks
Nam

Hi Nam,
to replicate CTR from standlone SRM, you should use the BADI DOC SAVE to trigger the replication process.
In this BADI you can use contract transfer function (BBP_PD_CTR_TRANSFER), but you will get blocked by standard design:
- SRM local contracts are transfered to CCM via XI if the corresponding flag is set in contract header
- SRM global contracts are transfered to R/3 via IDOC (in fact an RFC call out of SRM, creating IDOCs directly in R/3: no outbound IDOCs in SRM) if they are global (normal...)
So you should develop your own transfer function, re-using parts of BBP_PD_CTR_TRANSFER (especially META_CTR_TRANSFER that could be a good starting point to pass data to XI via an RFC call).
Rgds
Christophe

Similar Messages

SRM 7.0 Central Contract- Distribution to backend failure

Hello experts,
We are implementing SRM 7.0 Central contracts scenario with PI.
The Contracts get created and Released but the problem is that the Distribution to backend fails. The Status in BBP_PD shows 'Distribution Incorrect' and the RZ20 gives an error 'Backend data cannot be read'.
We checked all the configuration settings (including the PI settings) and everything seems to be in order.
Would appreciate if someone could throw some light on the potential cause of the problem.
Thanks
Raman.

Message must have created . check all SRM outbound transactions .but PI could not catch them.
Note 1284369 - User attributes check in Contract distribution via services - what is your SP level in SRM 700.
The sap stratergy in earlier version
table in ECC BBPD_CTR_IDOCREF with message 019-This will result in setting the GOA status to 'Distribution Incorrect'.
so SAP might have tried the same way in CCTR as well, Once message are created and this message number like IDOC number updated in ECC table for the further refrence .so like wise SRM trying to communicate the same to ECC but it would have failed.
do you remeber when GOA idoc fails this table we will have reference number and reprocessing idoc.
like any reference of your input must register in one ECC table but there may have this table or some other reference table.
/SAPSRM/CL_CH_SOA_MAP_CTR_OUT CLASS DO SOME trick and see what is happening here
Muthu

SRM- Pucchase Order and Contract (backend) Tolerance failures

Using SRM 7 Extended classic scenario with ECC 6.0. Tolerances have been set up in ECC and SRM.
The Contract is raised in the backend and replicated into SRM.
In SRM, both PPOMA and Vendor groups have been assigned the correct TOG.
Raising a Shopping Cart that exceeds the Contract Target value, but it within the Tolerance, works fine. However, once the Shopping Cart is approved, the back end PO creation fails, leaving the SC status as Saved. A review of SLG1 says that the PO exceeded the Contract value and displays errors for both Quantity and Target Value.
Any ideas on where to investigate appreciated.
Regards

S0001334469 wrote:>
> Muthu
>
> If I create a PO in the backend then it works within my defined tolerances. When I create a PO via SRM Shop Cart, teh shopping cart is ok but when it gets approved, the SRM PI is created but the backend PO is NOT created - and the SC status is set to Saved in the Follow On Documents for the Purchase Order. Seems that tolerances are being ignored.
>
> 'TOG' is the Tolerance Group - needs to be assigned to Vendor group and HR Org Structure (PPOMA) in SRM
>
> Gerry.
Hi Gerry
give more precise data about TOG you given in org structure
so you will get more suggestions from other people. it is power of SDN
created PO successfully in ECC via ECC request
no PO created successfully in ECC via SRM request
give more data on sc /pr /contract data ( quantity or value contract) for better understanding
Muthu
I'm having similar problems btu with repsect to SRM PO's against Contracts raised in the backend (replicated into SRM)
Our infrastructure -s SRM 7 Extended Classis Scenario and ECC 6.
I have tolerances setup in ECC and SRM and the TOG has been assigned in SRM Vendor Groups and in the HR Org Structure (PPOMA).
Tolerance are 5% up to $100.00
If I raise a Contract in ECC, and a PO (MM) in ECC, then the PO will work if I stay within the allowed tolerances.
When I raise a PO in SRM, the Shopping Cart is processed OK, but when the SC is approved, the backend PO is not created.
In the Shopping cart in Related Documents for document Purchase Order, the Satus is set to Saved. A review of SLG1 indicates error due to exceeding the quantity and the Target value.
Why are tolerances not being taken into consideration? How do I get this to work?
Gerry

Direct contract in the backend - Classic Scenery SRM 7.0

Hi Masters,
I´m using SRM 7.0 Package 08 in the classic scenery.
I´m trying to create a direct contract of a QUOT acepted and that need to go to the backend.
I´m using two badis:
BBP_DETERMINE_LOGSYS
Where the variable CV_LOGSYS is with the system backend destiny
BBP_CTR_BE_CREATE
Where the variable IV_LOGICAL_SYSTEM is with the system backend destiny.
Where the variable CV_USER is with the user RFC.
The result is generating myself a message: " CONTRACT 4400000041 - WAS CREATED " (/SAPSRM/PDO_WKL455 BPP_PD455)
But that contract is not available in SRM and it is not also available in ECC.
I forgetting something?
Thank you,
Pedro Marques

I believe that it exists yes possibility, as well as it comments on the text of the badi:
Use
With Business Add-In BBP_CTR_BE_CREATE, you can replace or supplement existing contract data in SAP Enterprise Buyer with your own backend structures and tables.
Enterprise Buyer calls this BAdI before it makes the RFC to the backend system to create a contract.
Activities
Implement and activate the BAdI if you wish to create contracts in the backend system and replace or supplement contract data.
Anybody have some idea?
Thanks,
Pedro

Distribute contract to SRM-MDM 2.0 catalog in SRM 4.0

Hi,
My client is using SRM 4.0 and need to distribute his contracts to SRM-MDM 2.0 catalog.
Once you set the flag "Distribute contract to catalog" in the contract the XI Sender Interface that the system uses is CatalogUpdateNotification_Out form the Sender Namespace http://sap.com/xi/EBP.
The question is whether there is an XI content for SRM-MDM 2.0 and if so then how can i redirect the distribution to another interface.
Thanks,
Raz
Edited by: Raz Golan on Jan 14, 2009 8:55 AM

Hi,
You can download XI contents for SRM-MDM Catalog 2.0 from SAP Service Marketplace same as other patches. http://service.sap.com/swdc
Regards,
Masa

Incorrect distribution -Error while distributing GOA to R3 Backend system

Hi,
We have installed SRM server 5.5 and implementing contract Management
scenario with backend system R/3 4.6B.
In this scenario we are creating a Global Outline Agreement in SRM
system and distributing it to the back-end ERP system.
In SRM5.0 GOA (Trans.type GCTR) that are distributed at Header level
are failing to distribute to R/3 system v4.6b
We are getting this error message in SRM transaction SLG1: -
The error ocurred by processing event RELEASED_NEWLY with GUID
DCA7101B320134F1949F000347DE470F and object_id= 5600000054 " RECEPIENT
NOT FOUND"
The purchasing org , the plant has been mapped .Also vendor & material is maintained for the company & Plant .
The condition types are mapped in SRM
Pls suggest.
Regards,
Avinash

Hi Avinash,
In reference to your query about GOA, the distribution error might be beacause of the issues in BADI implementation.
By using the BADI you can define which document to be created in the backend.
BBP_CTR_BE_CREATE BADI can be used in SRM and BBP_CTR BADI can be used in back end R/3 for this purpose.
Check for the transaction types (GCTR) and the number ranges for the transaction types.
The GOA will either create a contract or a Scheduling agreement in R/3 back end after distribution.
Also refer the below SDN thread in this regard :
Re: Scheduling Agreement from GOA
Any further clarifications are welcome.
Award points for suitable answers.
Rgds,
Teja

Mass upload contract with "Distribute Contract to Catalog" flag

I need to mass upload contract to update the flag "Distribute Contract to Catalog" (for srm mdm). What are the options. I don't see any option of that flag in the screen "Change Contracts: Mass Processing"

Solved on own
One needs to maintain System type as 'CATALOG' in SPRO >Define Backend Systems.
This makes the Distribute Contract Catalog check box to be visible in the Header tab of contract.
Regards
Sarath

How to create Contract in SAP backend systems( R/3)

Hello All,
We have SRM4.0 with classic scenario. We don't have sourcing cockpit , bidding engine and all activated.
Please suggest me, how can I create contract in backend system?
We don't want to create GOA in SRM system and distribute it to backend system.
Regards
Neelesh

Hi Neeleesh,
Go through the GOA setup in the <a href="https://websmp205.sap-ag.de/~sapidb/011000358700002897362004E/CG_Sourcing5.pdf">Strategic Sourcing Configuration Guide</a>
In the web GUI you can use the transaction BBP_CTR_MAINCC to create the Global Outline Agreement
Note 646903 is also useful.
Hope this helps.
/Kristoffer

Replicating Contract from legacy system

Hi Team,
I have contracts on legacy (non-sap) system. Now I want these contracts replicated to SAP SRM 7.0 system.
Can it be done through PI? or should it be done through flat file and creating the contract using standard FM?
Also, this is not a one time activity, i.e., as and when new contracts are identified in non-sap systems they have to be replicated/updated to SAP SRM7.0.
Please help.
Regards,
Nandu

Thank you Senthil for your reply.
You are right that we can use the FM. Before that the challenge here is how to bring the bulk contract data to the SRM system... is it through flat file or through PI or through ALE Idocs?
Please advise.

Contract creation in Backend with Idoc message type BLAORD

Hello,
We are creating Backend contracts from the Bidding engine functionality. We only want to create backend contracts and did the necesary configuration.
We activated BADI: BBP_DETERMINE_LOGSYS
Method CONTRACT_LOGSYS_DETERMINE.
We did not yet implement BADI:
BBP_CTR_BE_CREATE in SRM 5.0
In SAP R/3 Backend system (Version 46C) we see SAP is trying to create a contract via Idoc message Type: BLAORD.
In the trx BD87 in the backend we get status 51 :
Mesage number: 00 055
"Make an entry in all required fields"
In the segments of the Idoc however we do not see which field is missing!
How can we best analise this problem. Or maybe anyone can give us a a hint what is missing.
Thanks for any reply.
Aart

Hello RRK,
In ref. to your mentioning to change the backend configuration from WKK to MKK might not be as easy to do for organizations. As those configurations effect the overall creation of purchasing document types in R/3.
The Key issue is why the "Target Value" in the Header of the SRM GOA does not get transferred to the R/3 contract. That's why the issue is still there.
Were you guys able to figure out why that was missing? In the BLAORD IDoc the Target Value seems to not get transferred from SRM - its 0.00 if the IDoc is reviewed in WE19. This seems to be the problem.
Just wanted to know if you see the same issue in ur system.
Thanks.
Sunny.

Note 1092194 - Incorrect Purchasing group in distributed Contracts

Hi All,
described problem in note 1092194 applies to situation we face. We implemented that note but problem still exists. Has anyone hints or experience in this?
My Testing results after implementing Note 1092194:
Step
1)      chage PGrp from C01 to C02 in SRM-GOA
2)      distributing GOA from SRM to 2 ERP-Systems a) T01, b) T06
                           a) ECC 6.0 IS-H 600 (T01)
                           b) SAP R/3 Enterprise SAPKB62065
Only PGrp in a) is changed not in b)
Can any one give a hint or help?
Thanks, Isam
note 1092194
You create a GOA and all of the R/3 Contracts created
(ditributed) from the Global Outline Agreement of SRM have the same
purchasing group. This purchasing group is mapped to the first
purchasing group that has been created in the SRM system.
<<<<<
Edited by: Isam Kamel on Jan 15, 2009 9:53 AM
Edited by: Isam Kamel on Jan 15, 2009 9:54 AM

Hi All,
described problem in note 1092194 applies to situation we face. We implemented that note but problem still exists. Has anyone hints or experience in this?
My Testing results after implementing Note 1092194:
Step
1)      chage PGrp from C01 to C02 in SRM-GOA
2)      distributing GOA from SRM to 2 ERP-Systems a) T01, b) T06
                           a) ECC 6.0 IS-H 600 (T01)
                           b) SAP R/3 Enterprise SAPKB62065
Only PGrp in a) is changed not in b)
Can any one give a hint or help?
Thanks, Isam
note 1092194
You create a GOA and all of the R/3 Contracts created
(ditributed) from the Global Outline Agreement of SRM have the same
purchasing group. This purchasing group is mapped to the first
purchasing group that has been created in the SRM system.
<<<<<
Edited by: Isam Kamel on Jan 15, 2009 9:53 AM
Edited by: Isam Kamel on Jan 15, 2009 9:54 AM

Distributed contract release query!

Hi all,
Need help!
As I have created ''distribution contract'' without any plant. Now when trying to release the contract without putting any'' plant'' as I want to leave it open so that as when required ......my other company ''plant'' can create a release order against the contract later.
But during my release order creation... ..system is asking for Plant and now allowing me to save the document. Is it correct for system to ask for PLANT or is there any problem whcih need to be rectified.
Let me know your thoughts and advice.
Thanks in advance.
Cheers!

Thanks to both of you for your time.
But clear me out if I am wrong. I am trying to do my scenerio as per the theory goes for DISTRIBUTED CONTRACT, as follows,,
EXAMPLE -I have company code- ABCD...... & pur org -ABCD............. and plant -A & B with same company code.
now i have created contract with MATERIAL-A (1000 qty) ''without account assignment'' and ''Plant'' in my CENTRAL SYSYTEM.
Therefore now i am trying to do realease order against the contract with proper account assignment , but ''without a plant'' so that my central system makes the contract available to my local system ( so my local company plant A & B can create release order later as per thier need using thier own plant number in my LOCAL SYSTEM)
I guess theory says the same as I describe above. Now could any body let me know if I need to correct somewhere OR how do the actual FLOW happens.
Many thanks in advance.

Difference between centrally agreed contract and distributed contract

Hai
What is the main difference between Centrally agreed Contract and Distributed Contract?
Can any one help me in this?

Please go through the link
http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm

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

SRM 7.01 Central Contract: Email Notification when contract is distributed

Dear all,
I lwould like to know if it exists a standard functionality for distribution notification and how it is customizable.
The scenario:
I create my central contract in SRM and i would like to be able to send email alert to the back end user (Local Contract Manager for example) when the contract has been distributed correctly. Does the user need to be is the SRM Organisational Structure?
Can i use the event schema like expiring contract notifications?
Thank you for your help.
Best Regards,
Jennifer

The first interface that try to get out from SRM was " PurchasingContractERPRequest_Out_V1", thus based on this interface we made the configuration on PI. So, after pressing button " create contract" on srm if we execute tx SXI_MONITOR in SRM we found the interface " PurchasingContractERPRequest_Out_V1" and in the backend system ( ECC) at tv SXI_MONITOR we found interface PurchasingContractERPRequest_In_V1 for this contract with black and white flag ( processed successfully) but no contract created in ECC not even SRM.
Anyway we have checked that inbound proxy is executed but we dont see any contract created
Is this the right Interface? We are missing something?
Best regads and thanks again for your help!

SRM 4.0: distributing contracts to legacy backend

Similar Messages

Maybe you are looking for