ChaRM Maintenance Cycle Transaction Type ZMMN

[Former Member]

Hi,

When I create the Task List in Maintenance project -> System Landscape -> Change Management

System automatically created the  SMMN Maintenance Cycle, insted of ZMMN.

Where can do this setting for replacing SMMN with ZMMN, so that when I create the Task List, system should automatically create ZMMN Maintenance cycle.

Regards

P Kumar

[former_member211260]

Hi All,

We have similar type of situation and we want to use both SMMN and ZMMN for Maintenance Line and Project Line cycles respectively.

Request to help me if you have some solution.

Thanks in advance.

Regards,

Piyush Jain

[hannes_langner]

Hi,

did anyone find out how to use ZMMN / ZMDV / ZMMM instead of SMMN / SMDV / SMMM ?

Best regards

Hannes

[Former Member]

Hi Hannes:

We decided to change the answer previously provided as we had the opportunity to start replicating the proposed changes, and it seems there is more fabric to cut, than what we initially foresaw.   It is complex, but for now, we will place the main tables that contain the data with the idea that in principle the entry CRMW needs to point out to ZMMM and ZMMN, instead of SMMM and SMMN, respectively, in the tables listed below.

Most of the tables are accessible via SE16 or SM34.  Probably the full process will be found in the future, but we would recommend that if you can live with the scenario as-is, do not bother on making the changes to the tables below.  A support package will overwrite any deletions you make.

/TMWFLOW/TPCPVAR

/TMWFLOW/VC_PHMD

/TMWFLOW/TPPHMCV

/TMWFLOW/TPCPVAA  I would say this is the tricky table.  There may be a way in SPRO to replicate the entries SMMM and SMMN with ZMMM and ZMMN

As a complement, let us pass you some other details in case you have a developer close to you, if you happen to have that need.

Method /TMWFLOW/IF_EX_PHCTRL_COOP~CYCLE_CREATED contains the piece of code that calls SMMN and SMMM.

* Create cycle transaction (SMMN, SMMM)

call function 'SOCM_CREATE_CHANGE_TRANSACTION'
destination rfc_dest
exporting
im_process_type = ls_variants-coop_variant
im_description = text
importing
ex_transaction_guid = lv_guid_raw
exceptions
communication_failure = 1 message lv_msg_text
system_failure = 1 message lv_msg_text.
if sy-subrc <> 0.
raise exception type /tmwflow/cx_commit_cancled.
endif

As you see,ls_variantsis the key.  That variant represents table /TMWFLOW/TPPHMCV, which before any changes looks like this:

PHASE_MODEL COOPERATOR COOP_VARIANT

DEVRL       CRMS       SDDV
DEVRL       CRMW      SMDV
DEVRL       C_PR       000000000000001
DEVRL       C_PR       000000000000004
DEVRL       C_PR       000000000000005
DEVRL       C_PR       DEFAULT
DEVRL       QGM        QGMV
DEVRL       SCMA       SAP0I
DEVRL       SCMA       SAP0T
DEVRL       SCMA       SAP0U
DEVRL       SOLM       SOLAR
DEVRL       SOLM       SOLUTI
DEVRL       SOLM       UPGRA
MNTCL       CRMS       SDMN
MNTCL       CRMW       SMMN
MNTCL       C_PR       000000000000006
MNTCL       QGM        QGMN
MNTCL       SCMA       SAP0M
MNTCL       SOLM       MAINT
MNTMM       CRMS     SDMM
MNTMM       CRMW    SMMM
MNTMM       QGM        QGMM
MNTMM       SCMA       SAP1M
MNTMM       SOLM       MAINT

That method also uses what they call cooperators, which are stored in table /TMWFLOW/TPCPVAA, already mentioned.

Regards,

Juan

[Former Member]

Hi:

Did you find that out?

Thanks,

Juan

[Former Member]

anyone got lucky with the solution? Please kindly share