Main language for documentation module /SDF/WS_MON not found

[Former Member]

Hello Gugus,

we install SP-A/PI 01P_700 in our ERP System (NW 701).

In Phase DDIC_ACTIVATION we get the following error:

TP_STEP_FAILURE RC 12 Main language for documentation module /SDF/WS_MON not found.

Protocoll:

2.921 switch copied for activation, 12 for deletion

Business function set /SDF/WS_MON has been deleted

Start of deletion process for business function set /SDF/WS_MON

Main language for documentation module /SDF/WS_MON not found

Error while copying DDIC objects from switches

We only have language EN and DE in our SAP.

Has someone a suggestion how we can fix this?

kind regards

Chris

[Former Member]

Dear all,

The easiest way to solve the problem is to implement the SAP note #1476315 in a different system ( in our case the SolMan production system) and to transport it back to the development. SNOTE is not locked there.

It worked fine for us. Of course it is not the proper way of transports, but it avoids manual corrections with high risk of errors. We imported the transport using the command line.

Afterwards the implementation of ST-PI 2008_1_700 patch 6, DDIC_ACTIVATION phase finished successfully! This is more the kind of solution for a basis administrator!

Hope this helps!

Best regards

[Former Member]

Dear Thomas,

The Note #1476315 helps indeed.

To reset the OCS queue, you can do the following:

• log on to the transport domain
• open a command prompt
• use this command: tp r3i all <SID> pf=/usr/sap/trans/bin/TP_DOMAIN.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8
• ofc the part after "pf=" should point exactly to the tp_domain.pfl, <SID> is clear to you aswell, I guess
• after you run the command, you can log off from the tp. domain
• log into the affected system (which OCS queue you want to reset)
• use TR. SE37 with the function module OCS_RESET_QUEUE
• parameters: IV_TOOL=SPAM or SAINT, whatever you are stuck into; IV_FORCE=X
• run the function module --> your OCS queue is empty now.

After this, you can redefine the OCS queue.

Best regards,

Greg

[former_member189797]

Hello All,

Please do not use any manual command if you face this issue. It is not supported by SAP.

Please open a message in the BC-UPG-OCS-SPA

component.

You can safely follow the recommendation in the Note :

1730081 - Main language for documentation module /SDF/WS_MON not found during DDIC_ACTIVATION phase

Regards,

Gaurav

[former_member196000]

The solution reported by Thomas Schmidt does actually work.

The only thing you should do is import the transport request you created in the other system via tp on operating system and not via Transaction STMS.

I had the SP error in System Development which is also Domain Controller. Then I created Transport Request on Test System (if it makes a local request out of it, use transport of copies and add the objects of the local request) with destination Development System. Then on the Development System STMS gives error about locked OCS by transaction SPAM. So, import the request via tp import on OS level.

[Former Member]

Faced the exact same issue, and had no ABAPpers at hand to help perform manual implementation of the corrections described in note 1476315.

So I followed Gerko's instructions, worked like a charm. Thumbs up.