Skip to Content

MM-Contract Release Strategy

Hi,

there is a Release Strategy maintained for MM-PO and MM-Contract.

Both have same Release Group.

Issue is whenever PO created with Release Strategy, it triggers Release Group CA and works fine by triggering the BOR BUS2012.

But when a Contract is created with Release Strategy, it also triggers Release Group CA but it doesnt trigger BOR BUS2014, it triggers BUS2012 instead.

Because of this my Contract WF isnt getting triggered.

Observation is that both PO and Contract have same Release Group and the Document type for PO and Contract are defined in the same Release Group.

Could this be a issue, should we create another Release Group for Contract?

Thanks,

Aditya V

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Apr 21, 2017 at 08:47 AM

    Yes have a different Release Group for each

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Lakshmipathi,

      so do you mean that PO should have a different Release Strategy with a different Release Group and

      Contract should have a different Release Strategy with different Release Group?

      Thanks,

      Aditya V

  • Apr 21, 2017 at 01:19 PM

    Can you show your customizing from PFTC Transaction?

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 27, 2017 at 06:27 AM

    Thanks,

    Solution, created a different RS for Contract, atleast now BUS2014 is determined.

    Add comment
    10|10000 characters needed characters exceeded