CONTRACT DISTRIBUTION CCTR Vs GOA

Hi All
Learnt that SAP has some improvement on DISTRIBUTION for CCTR contract ? Can any one explain how it is Indeed helps compare to GOA.
In GOA --> in the Header it self we go to distribute Porg, plant , Doc Type and Release value.
How new enhanced CCTR Contract Distribution works. I believe seperate folder for DISTRIBUTION in CCTR.
what steps needs to be followed on simple and comlex distribution?.
Muthu

Hi Muthu,
From what i know, CCTR can be referenced and used both in SRM and ECC, wheras, GOA can be used IN ECC only (after it is created and distributed from SRM).
Pricing would be controlled from SRM.
You need to activate Business Function, set the appropriate doc types and condition types in ECC.
CCTR Distribution / qty usage updates works using PI while GOA uses IDOCs.
Additional fields for say CCTR number / item number appear in ECC after Business function activation. You also need to add the workflow user in the Org structure (Local POrg/Pgrp).
Not sure on the Simple and Complex scenarios though.
Cheers - Akash

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 7 Contract Distribution not possible in PPS - is it true ?

Hi SRM Gurus,
I gather that the SRM 7.0 Central Contract are not distributed to ECC 6.04 in PPS environment.
( Ours is SRM 7.0 ECC 6.0 Enhp 4 with PI 7.11 on PPS - ECS.)
Correct me if i am wrong.
If so, is there any other way to distribute Central Contract to ECC . Even it its partial distribution.
Thogh, I hv config for CCTR following the SNote 1268821. To start the problem, the Distribution button on the header of the contract is disabled. CCTR tran type configured both in SRM and ECC.
Kindly share your thoughts.

Hello,
You can try reverting the note 1354971, to get an assign distribution button active at item level.
Interfaces(XML) which are used to transfered the central contract are not extended to all the fields related to PPS functionality. Eg. Guaranteed Minimum.
These fields will not be transfered to backend and other process like release value updation to the backend contract has limitation as PPS funcalities can be used only in extended classic scenario.
So we have a limitation and also this functionality will not be supported in PPS.
Nevertheless, you can enable this funcationality and use with the limitation.
You will have to handle this through custom meta data handle where you need to create dynamic class and method and maitain in the customizing table /SAPSRM/V_MDA_HC. You can enable the Assign distribution button and link in the dynamic class.
You can check the configuration in the standard meta table /SAPSRM/V_MDA_HD for reference.
Courtesy : Lisa Norris!
Re: SRM 7 Contract Distribution not possible in PPS

No Contract Distribution with PPS

Hi guys,
We are implementing SRM7 with ECC6 EHP.
With reference to sap note 1354971 Disable Contract distribution in PPS, does it means we cannot use Central Contract function together with PPS activated?
As I understand the concept of Central Contract is to enable an Operational Contract to be used as valid source of supply in both SRM7 and ECC6 (and for this to be possible it has to be distributed to backend ECC6). However, if the distribution disable how would the contract available as source of supply in ECC6?
Cheers,
Tom

Tom
Thanks for your reply.
I am trying to get the contract distribution working but for some reason I seem to be missing something very fundamental.
I think that I have done all the required config steps and PI has been implemented accordingly.
Would you have any config notes / documentation that you would be will to share so that I can hopefully get to the bottom of it.
Regards
Keith

Why i get this dump monitor contract distribution

Hello All,
Alert ID (AID) invalid (function 'BAPI_SYSTEM_ALERT_GETDETAILS'
when i go monitor contract distribution i get above dump.after SP15 srm 550
why?
any one faced?
any help is greatly appreciated
i have this problem in gui too.bbp_ctr_mon
br
Muhtu

seems to be some basis task let me try in netweaver forum

GOA + Local Contract distribution to R/3 in Extended Classic Scenario

Dear SRM Gurus,
System Information: SRM Server 5.5 EBP5.5
Technical Scenario: Extended Classic Scenario.
Q1) We have created a Global Outline Agreement in EBP. We want this to be distributed to R/3.
But when we click on distribute, it does not get distriduted to R/3 ??? Is there any IDOC to be maintained----wich one ??
Please guide me as to how can we go ahead with this.
Best Regards,
ANIL RAJPAL.

Hi Anil,
The IDOC to be maintained is: BLAREL
For detail information you can visit the links.
http://help.sap.com/saphelp_srm50/helpdata/en/00/f5c93f4d903b1ce10000000a114084/content.htm
https://websmp104.sap-ag.de/~sapidb/011000358700002529571998/blarel02_d.htm
Also you can have look at notes:
643823
953269
671764
641919
Pls let me what all configuration you have done for GOA functionality so that I can suggest you something specific.
Best Regards,
Amit
Do reward the points if ans is helpful!!!

SRM 7 Contract Distribution not possible in PPS

Hi all,
We're on SRM 7 / ECC6 EHP3, and activated PPS. I have been told that for PPS the distribution is not supported completely, and hence the functionality is disabled, NOTE 1354971.
My problem is, since we have activated the PPS functionality in all the landscapes we have at present. I can not switch PPS off or refer to another system without the PPS. By reverting the note 1354971, i have only managed to get an assign distribution button active at item level. I would have assumed, the contract/GOA should be able to be distributed at header level. Consider a contract with 1000 items.
Can please someone tell me what is the process for distributing a contract completely. Not just selective items.
Moreover, this does not work, when i have outline items/sub items in the contract.
Regards
Ali

Dear Ali,
Interfaces(XML) which are used to transfered the central contract are not extended to all the fields related to PPS functionality. Eg. Guaranteed Minimum.
These fields will not be transfered to backend and other process like release value updation to the backend contract has limitation as PPS funcalities can be used only in extended classic scenario.
So we have a limitation and also this functionality will not be supported in PPS.
As it was a bug , we have corrected this through the note 1354971.
Nevertheless, you can enable this funcationality and use with the limitation.
You will have to handle this through custom meta data handle where you need to create dynamic class and method and maitain in the customizing table /SAPSRM/V_MDA_HC. You can enable the Assign distribution button and link in the dynamic class.
You can check the configuration in the standard meta table /SAPSRM/V_MDA_HD for reference.
I hope this helps,
Kind Regards,
Lisa

Central Contract Distribution - line items creates many contract in the BE

Hi SRM Gurus,
We are in SRM 7 ECC 6 Ehp 4 PPS. Ext Classic.
First of all, CCTR - Central Contract can't be distributed as per SAP for PPS impl.
But we have a workaround.
We made snote 1354971 read with 1423994 implemented. Made the process work.
Means Assign distribution on the item level was enabled and Distribution reached BE.
But when we have multiple line items in the Central Contract, and we assign distribution, it creates one contract per line item in the Backend which is really absurd. Which means if you have 100 line items, its creating 100 contracts. When we do the call-off against this central contract, we have multiple contracts.
Gurus, Can you guys throw some light on this entire issue.
with regards,
Freemind

We are having nearly exactly your scenario and CCTR works fine with 1 distributed contract containing multiple items. Check if all the items are distributed to the same purchasing org and location. If all is the same, debug BBP_PD_CTR_TRANSFER with your SRM contract GUID to see when and how multiple contracts get created in ECC.

Distribution Incorrect for GOA

HI:
   I created a GOA in SRM and need it to be distributed to R/3. but there is nothing exist in R/3.I checked the status of this GOA.the status says 'Distribution Incorrect ' and there is a message occurs in the monitor,that is "Could not determine backend system for contract".
      I have checked all configuration both in SRM and R/3 .It seems that everything is OK.I am just wondering do I need to specify backend system for GOA somewhere in SRM? If it is ,please kindly tell me where.tks.
Message was edited by:
        hong pan

Hi
<b>Please go through the following SAP OSS Notes -></b>
Note 550071 FAQ: EBP - Shopping Cart
Note 893493 Improvements in the data mgmt of the ICH purchase order
Note 763980 ECS: Reading values from the R/3 Logistics back end
Note 604420 Composite SAP note SRM 3.0 SP1 group
Note 376348 Contrct documentatn:Changes for EnterpriseBuyer 2.0
Do let me know.
Regards
- Atul

Status distribution incorrect in GOA

Hi,
i've created a shopping cart, then bid invitation followed by Bid submission to bid acceptance. Then i created a contract from this bid response successfully. But the problem is when i distribute this contract to R/3, distribution fail with status "Distribution incorrect" I don't understand the missing link. Am using SRM server 5.5 (SRM 5.0) with ECC 6.0.
Kind Regards,
Maggie

Hi Goithoma,
I faced exactly same problem and coded a BADI to solve this issue.
Actually Condition type in SRM and ERP is different and that is the reason for this.
BADI Name: bbp_ctr_be_create
Sample Code is
METHOD if_ex_bbp_ctr_be_create~contract_interface_fill.
TYPES : BEGIN OF ls_mapping,
cond_type_old TYPE kscha,
cond_type_new TYPE kscha,
END OF ls_mapping.
DATA : lw_ct_be_text TYPE bbps_ctr_text.
DATA: ls_be_items TYPE bbps_ctr_item,
ls_be_cnd_ct TYPE bbpbapicondct,
ls_cnd_hd TYPE bbpbapicondhd,
ls_cnd_it TYPE bbpbapicondit,
ls_cnd_qs TYPE bbpbapicondqs,
ls_cnd_vs TYPE bbpbapicondvs,
ls_mapping TYPE ls_mapping,
lt_mapping TYPE TABLE OF ls_mapping,
lv_tabix_ct TYPE sy-tabix,
lv_tabix_hd TYPE sy-tabix,
lv_tabix_it TYPE sy-tabix.
Condition Type mapping from SRM to ERP system.
ls_mapping-cond_type_old = '01CT'.
ls_mapping-cond_type_new = 'PB00'.
APPEND ls_mapping TO lt_mapping.
ls_mapping-cond_type_old = '01RA'.
ls_mapping-cond_type_new = 'RB00'.
APPEND ls_mapping TO lt_mapping.
ls_mapping-cond_type_old = '01RH'.
ls_mapping-cond_type_new = 'RA01'.
APPEND ls_mapping TO lt_mapping.
ls_mapping-cond_type_old = '01RP'.
ls_mapping-cond_type_new = 'RA00'.
APPEND ls_mapping TO lt_mapping.
go through all service items (product_type 01 = normal material,
product_type 02 = service)
LOOP AT ct_be_items INTO ls_be_items.
additional loop on local condition table if product_type = 02
if 02 --> change SRM condition 01CT to PRS
only valid with services !
    IF ls_be_items-product_type = 02.
      LOOP AT lt_mapping INTO ls_mapping
        WHERE cond_type_old = '01CT'.
        ls_mapping-cond_type_new = 'PRS'.
        MODIFY lt_mapping FROM ls_mapping.
      ENDLOOP.
    ENDIF.
    LOOP AT ct_be_cnd_ct INTO ls_be_cnd_ct.
      lv_tabix_ct = sy-tabix.
      LOOP AT lt_mapping INTO ls_mapping
        WHERE cond_type_old = ls_be_cnd_ct-cond_type.
        CLEAR ls_be_cnd_ct-cond_type.
        MOVE ls_mapping-cond_type_new TO ls_be_cnd_ct-cond_type.
      ENDLOOP.
      MODIFY ct_be_cnd_ct FROM ls_be_cnd_ct.
    ENDLOOP.
    LOOP AT ct_be_cnd_hd INTO ls_cnd_hd.
      LOOP AT lt_mapping INTO ls_mapping
      WHERE cond_type_old = ls_cnd_hd-cond_type.
        CLEAR ls_cnd_hd-cond_type.
        MOVE ls_mapping-cond_type_new TO ls_cnd_hd-cond_type.
        MODIFY ct_be_cnd_hd FROM ls_cnd_hd.
      ENDLOOP.
    ENDLOOP.
    LOOP AT ct_be_cnd_it INTO ls_cnd_it.
      LOOP AT lt_mapping INTO ls_mapping
          WHERE cond_type_old = ls_cnd_it-cond_type.
        CLEAR ls_cnd_it-cond_type.
        MOVE ls_mapping-cond_type_new TO ls_cnd_it-cond_type.
        MODIFY ct_be_cnd_it FROM ls_cnd_it.
      ENDLOOP.
    ENDLOOP.
ENDLOOP.
ENDMETHOD.
Regards,Nishant
Please reward points if this helps.

Problem in contract distribution

Hi All,
We are working on SRM 4.0 classic scenario. We are getting an error message while disributing the GOA in application monitor as "<b>Processing of IDOCs of type BLAORD03 im system BRD302 canceled</b> "
We have checked all the customization and IDOCs. Attributes are also maintained for Pgrp. '
Kindly share your valuable inputs.
Regards
Abhijeet

Hi,
See the foll related threads:
Error in IDOC BLAORD03
Re: Contract not transfered to backend system
Re: IDOC error in R/3 while creating a contract from SRM
Can not distribute GOA to backend due to missing company code
Also see this oss note:
Note 793694 - Global master agreement - long text format specific. missing
BR,
Disha.
Pls reward points for useful answers.

Central contract distribution in two backend ERP system

Hello All,
I am implementing SRM 7.0 Contract management (SAPKIBKV07) with two backend ERP system.
We have a requirement where we will create a Global contract in SRM system. Upon distribution based on purchase organisation this contract should get distributed to two different backend system.
Q-1) Is this a standard featutre available with Contract management or de we need set up some configuration. If yes, then please let me know the details.
Q-2) Again here the master data for both the backend system is not synchronised hence if a Global contract in created in SRM system and distributed to two different countries then each contract in ERP should have the region specific vendor code ?
How this functionality can be achieved.
Thanks,
Yatin

Hello All,
Has anyone implemented contract management with two different backend system and with different master data set up
Thanks,
Yatin

Source determination in backend (R/3) for distributed contract i.e. GOA

Hi,
Source of supply is not getting picked up in R/3 in PR generated for Non- stock item while creating work order (IW31), though GOA exists in R/3 for that material. Maintaining source list also does not help. Please note that it works fine for local contracts. Also it works for PR created using ME51n for GOA as well. Any solution?
Thanks,
Manoj

Hi, did you ever solve this issue? i am suffering the same type o problem, please let me know in case you found a solution.
Best regards.

SRM Contract Distribution Error

Dear All,
Our ERP system 6 EHP 4,And we active the LOG_MM_P2PSE_1,And SRM 7.0,Now we used "Set Up Synchronous Service",Didn't use PI,We according sap notes:1268821 configure the Central Contract Management,Now when we create the Central Contract Management and Distribution it,Then the system have a error "Back-end data could not be read ",Who can help me?

Hi Bill
Note 1268336 - Synchronous peer-to peer Services Configuration
1268821
PI is mandatory . How contract data reach ECC without PI
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

Central contract distribution in PPS

Hi All,
With reference to this forum link, it is possible to distribute central contracts in PPS to ECC.
http://forums.sdn.sap.com/thread.jspa?threadID=1915922
I want to enable the assign distribution button. Pls help me with entries what to maintain in this table.
/SAPSRM/V_MDA_HC
Thanks and Regards,
Abdul Raheem

closing thread

CONTRACT DISTRIBUTION CCTR Vs GOA

Similar Messages

Maybe you are looking for