topic Re: Oss Note - Object MTXT in Application Development and Automation Discussions

Oss Note - Object MTXT

tiagocorreia1 — Thu, 14 Feb 2013 16:01:39 GMT

Dear Experts,

I'm trying to implement the Oss Note 1796626. I made all manual steps, I checked all programs and the log shows "completely implemented". But the Oss Note has the status "Incompletely implemented"; and I can't change to "completely implemented".

I was checking in corrections inside the note and I found the object (MTXT) as "Unknown object type".

Corrections

120061532 1548432 -> SAP_HRCBR Releases: From 470 To 604

(MTXT) 4OFq5FAFqao1bT9CYvDpeG -> Unknown object type

Does anyone know how to implement it?

Thanks,

Re: Oss Note - Object MTXT

Former Member — Thu, 14 Feb 2013 16:56:56 GMT

Hi Tiago,

Please check this.

The problem might be caused by following possibilities:

Not all objects were included in the request.

Solution: Check whether all objects changed by the SAP note are included in the request. If there is any object missing in the request,

create a new request to include it in DEV system and transport the request to QAS and PRD system.

The request was not imported into QAS and PRD completely.

Solution: Check the import log. If import failed with error, do import again.

R3trans bug, like SAP note 1525399.

Solution: Download the latest R3trans and create a new request to include the affected objects (if you know) or all the objects in DEV system

and transport the request to QAS and PRD system.

for detail refer : http://wiki.sdn.sap.com/wiki/display/SL/SAP+Note+Implementation+using+Note+Assistant+-+Frequently+Asked+Questions

Regards,

Sudhir Kothavale.

Re: Oss Note - Object MTXT

tiagocorreia1 — Thu, 14 Feb 2013 17:11:52 GMT

Hi Sudhir,

All objects are into the Request but the oss note shows a stranger object that don't exist in my sap system.

Thanks,

Tiago

Re: Oss Note - Object MTXT

Former Member — Thu, 14 Feb 2013 17:22:18 GMT

Tiago,

follow the steps,

To implement OSS SAP Notes automatically from transaction ‘SNOTE’.

1.Download the SAP Note from OSS portal by the ‘Download SAP Note’ option from the ‘Goto’ menu.

2.The SAP Note can also be downloaded from the application toolbar button.

3.On clicking the download option, a popup is displayed to provide the note number for download.

4.All the newly downloaded SAP Notes can be viewed in the node ‘New’ under root node ‘SAP Notes’.

The details of individual SAP Note can be seen by double-clicking the note. The implementation status tells us whether the SAP Note can be implemented or not.

The objects impacted and the correction instructions can be seen from the hierarchy in the left side of the screen. An SAP note can be implemented by clicking the menu

‘SAP Note Display -> Implement SAP Note’

Also refer,

http://scn.sap.com/thread/741448

Regards,

Sudhir Kothavale.

Message was edited by: SUDHIR KOTHAVALE

Re: Oss Note - Object MTXT

Former Member — Fri, 22 Feb 2013 04:11:49 GMT

Hi Tiago,

Have you resolved the issue related to Unknow object type in OSS note yet? I also found an MTXTobject in several instruction corrections when implementing OSS note 1790670 into GTS.

120061532 1541423 SLL-LEG Releases: From 720 To 901

(MTXT) YmfIGeu3iKw{WEcnYyVZCm Unknown object type

120061532 1557633 SLL-LEG Releases: From 720 To 800

(MTXT) u9{hD}D0AqUj5uIbHKvfj0 Unknown object type

Hi experts, does anyone know how to implement these corrections?

Thanks and Regards,

Hoang

Re: Oss Note - Object MTXT

tiagocorreia1 — Fri, 22 Feb 2013 12:25:06 GMT

Hello Bui,

I didn't resolve the issue related to Unknown objects type in Oss note.

I implemented the Oss note manually.

Regards,

Tiago

Re: Oss Note - Object MTXT

Former Member — Thu, 11 Apr 2013 16:57:11 GMT

Hello Tiago,

I have seen quite a few MTXT objects in Notes over the last couple of years.

This is a "placeholder" object, used by the system to identify and prompt for additional activities and the completion of the manual portions of the Note. It does not contain instructions SNOTE can operate against.

The SNOTE display is especially puzzling when only the manual instructions in the Note are valid for the system release.

See Note 1709728 on ECC system as example. This Note contains only manual instructions. The validity range of the MTXT object is, in our case, applicable to our system release. Yet the SNOTE status will always be "cannot be implemented". Of course, as there is nothing in this Note for SNOTE (the tool) to apply.

Regards,

Sue Morton