Skip to Content
avatar image
Former Member

Contracts not transfered from SRM to ECC

Hi People!

It is my first time implementing contracts, and have following issue: Contract BUS2000113 no replicate to ECC. We need to create the contract in SRM and replicate it in ERP when is approved.

We implement BBP_DETERMINE_LOGSYS referring to SRM systems ( if not, in SOCOcréate backend contract directly, and we need to have it in srm), and need to know how to proceed when contract is approved in order to replicate it in backend.

Thanks and regards!

PD: in the following talks abput company code https://scn.sap.com/thread/1432241 , but I am not understanding where we have to add this field.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Jun 23, 2016 at 06:48 PM

    Hi Carla, I don't know if you are aware but if you do not complete distribution, no xml or transfering action occur.

    It means that if you do not assign items to a distribution line at header level of the central contract, even if the contract is released, nothing is triggered.

    If you have completed the distribution you should see something like this at document and BBP_PD

    hope this help !


    pic 1.png (23.8 kB)
    pic 2.PNG (28.9 kB)
    Add comment
    10|10000 characters needed characters exceeded

    • In standard you can't, but you have the possibility to make the Assign Distribution button enabled via custom meta data handling. Unfortunately it is not guaranteed that the distribution will work perfectly in this case and it is considered as a modification of standard system, hence it is not recommended.

      For this you need to create a dynamic class and method and maintain it in the customizing table /SAPSRM/V_MDA_HC. You can enable the Assign distribution button in the dynamic class or simply set it to enabled in the customizing without the dynamic class and method.

      You can also access this customizing table via SPRO:

      SAP Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization) -> Control Actions -> Configure Control of Actions on Header Level

      You can check the configuration in the standard meta table /SAPSRM/V_MDA_HD for reference. Or in SPRO:

      SAP Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization) -> Control Actions -> Display Standard Metadata Tables for Actions on Header Level

  • Jun 23, 2016 at 10:21 AM

    Hi Carla,

    If the relevant eSOA environment and XML services are ready in your system, then the Contracts can be replicated to the backend system by maintaining a distribution entry on item level on Distribution tab. If the distribution is correctly maintained upon releasing the contract, the backend contract will be created too.

    For more information regarding distribution, please refer to Contract Distribution section of Contract Troubleshooting Guide in SRM Wiki: Contract TSG - Supplier Relationship Management - SCN Wiki.

    Best Regards,

    Daniel Marlen

    Add comment
    10|10000 characters needed characters exceeded

    • Thank you for the information. Please provide the followings:

      -the Business Functions that are activated in the system

      You can find it in SPRO: SAP Supplier Relationship Management -> SRM Server -> Activate Business Functions

      - Display View /SAPSRM/V_TS_VIS in transaction SM30 and send a screenshot of it.

      - Check if an "Assign Distribution" button is available in the Item Overview table.

      Best Regards,

      Daniel

  • Jun 23, 2016 at 02:37 PM

    Hi,

    First, you have to maintain distribution in contract for both header and item level.
    If ESOA is used, XML will be triggered from SRM to send the contract to ECC side.
    If old ERP system type is used, idoc will be generated in ECC side directly to transfer this contract.

    You may use FM BBP_PD_CTR_TRANSFER to debug the transfer process to see why XML or idoc is not triggered. Please note this FM is only used for troubleshooting.

    BR,
    Ivy

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I Tried, but debug is not stoping in BBP_PD_CTR_TRANSFER when Contract is approved.

      I do not understand where should be setted this configuration, because do not find any place to do it. I think This is not triggered 😔