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 · Accepted solution]

Hi,

I hope this issue not related with the SDF/WS_MON,

have you checked this http://scn.sap.com/thread/1779265

and as stated validate the sap note 1476315

Thanks,

Jansi

[Former Member · Accepted solution]

Hello,

yes i have found this thrad before. But SAP Note 1476315 cannot be implemented.

thanks.

Chris

[former_member189797 · Accepted solution]

Hello Christian,

Whats your BASIS release & SAP_BASIS SP level ??

Regards,

Gaurav

[Former Member · Accepted solution]

Hi,

You are NW 701 s t? why this note cannt be implemented?

may I know what version of st-a/pi u trying to install,

check in RTCCTOOL suggestons, sap note 69455 giving the details of 01P* of ST-A/PI and erros fixing on QA part of the note

Please check and update.

Thanks

Jansi

[Former Member · Accepted solution]

Hello,

we are at

SAP_BASIS 701 SP07

regards

Chris

[former_member189797 · Accepted solution]

Hello Chris,

then you should be able to implement the Note. If you check the Note, it is valid for the

700 - 702 release.

Also there are 2 correction instruction for the 701 release :

Both are valid for the SAPKB70107.

Could you please let us know what is the reason this note cannot be implemented?

Regards,

Gaurav

[Former Member · Accepted solution]

Hi Chris,

please download the sap note using the tcode SNOTE, check the status there.

if your snote nt working, as stated in he note please apply the corrections manually.

Since SAP released 01P* new by this june, might be oher way we can get sap guidance by OSS.

before that please apply the corrections.

Thanks,

Jansi

[Former Member · Accepted solution]

Hello,

We checked note 69455 before starting this thread, but there are no fixing hints of this error in note 69455.

We checked the objects of note 1476315. But the fixes are not implemented.
Now we implemented the note 1476315 manually. This solve the problem.

regards

Chris

[former_member189797 · Accepted solution]

Hello Chris,

Glad to know that issue has been resolved. So just for the information,

In the DDIC_ACTIVATION phase , you cannot implement a note using SNOTE as OCS will be     

locked by the SPAM/SAINT. I have seen similar issue where the status of the Note was     

cannot be implemented in this phase but once the queue was resetted, the status changed to

can be implemented. So in the next system, apply this note before starting the

installation, I believe at that time the status should be 'can be implemented'.

As an alternative, correction of this Note have been delievered with the SAPKB70108 . So you can apply this SP also. After this you should not face this issue.

Hope the above information helps.

Regards,

Gaurav

[Former Member · Accepted solution]

Hola buen día la aplicacion de la nota 1476315 me ayudo a solucionar mi problema, a que yo estaba aplicando los ST/PI 5 y 6 dentro de basis 700 patch 22

Muchas gracias,

Hello, the aplication of note 1476315 was excellent solution, my proble was with ST/PI 5 y 6 in SAP_BASIS 700 patch 22

Thanks a lot

[former_member214380 · Accepted solution]

Hi Christian,

currently I am in the same situation. SNOTE is blocked, SPAM standstill.

I am working on implementing the 1476315 manually. I do have a question here. By looking in code fragments that have to be changed I can see the following Deltas two times:

As you can see there is the same content that has to be changed - but why then two different deltas? Looking into the SAP systems ABAP code I can find the exact matching context block four times.

So how to proceed here? How did you do it? Cange all(!) occurences in the source code or just one/two...?

Regards and thanks in advance!

Daniel

[Former Member · Accepted solution]

Saludos,

Soy nuevo con las correcciones manuales, podrias indicarme la manera en que implementaste la nota 1476315 de manera manual.

Gracias

[former_member214380]

Hi there,

fixing this issue is actually quite simple - believe me! It is just deleting/copy/pasting ABAP code.

Example, how I did it:

Just mark out the old code with * and put the new code below it. Make sure to check and activate the changes. Then SPAM will proceed.

[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_member238301]

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.

[former_member189797]

Hello,

Just for the information. Note has been released for this issue.

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

Regards,

Gaurav

[Former Member]

Hi Christian

I have the same issue, but I don't know how to implement the note manually, could you tell me the t-code that you used to implement sap note 1476315.

Thanks in advance

[Former Member]

SE80

[former_member189797]

Hello,

Please take help from your ABAPer colleague. It should be done in the ABAP workbench (SE80).

Regards,

Gaurav

[Former Member]

Hello,

Faced with a typical problem that was solved by installing

note "1476315 - Error in activation protocol for switch framework".

regards

Denis