"MDM 3.0 Add-on" - oss note 748777? missing

In the MDM3.0 Master Guide, there are references in section 2.5.1 to oss note 748777. I can't find this note on oss. Since it's in the guide I'm assuming it's something important. If you've got any helpful info here please let me know - thanks

Hello Ben,
The note 748777 is currently in process. Therefore it is not visible, but it will be there again soon.
Bye,
Horst

Similar Messages

ECM : OSS notes for missing structures

Hi Experts,
Below Standard SAP structures are missing in one of my system and existing in other server.
Can you please suggest if I can implment any OSS notes ?
If yes, how can I search OSS notes for below particular structures ?
DMSCLS_SIMPLE_SELECTION
DMSCLS_SEARCH_OBJECTS
Thank you in advance.

Hi,
Check this SAP note. 1239471
Regards,
Srini.

Error Message: Data from Business Add-In ME_PROCESS_PO_CUST not transferred

Hi All,
I have done a BADI implementation for ME_PROCESS_PO_CUST and when I try to convert a PR to PO using ME59N in ECC u2013 AFS System I am getting below error message.
Data from Business Add-In ME_PROCESS_PO_CUST not transferred.
I am trying to populate certain PO fields ( ekko and ekpo ) from PR fields. But the above error occurs when I update the Ex Factory Date manual that is EKPO-J_3AEXFCM.
I am updating this in the method PROCESS_ITEM and what I found while debugging is in the class CL_PO_HEADER_HANDLE_MM, in the implementation of IF_FLUSH_TRANSPORT_MM~START, the contents of field u2018my_iteration_countu2019 keeps increasing and becomes 10 and raises this error.
I read few of the related questions raised by others in this forum and understood that this can happen if I try to change the field that is disabled ( greyed) in ME22N. But this field that I am talking about is enabled.
I also tried to move my code of populating the field EKPO-J_3AEXFCM from the PROCESS_ITEM to the enhancement point just above the user exit EXIT_SAPMMO6E_018 but still it doesnu2019t resolve the error.
(We donu2019t want to use User Exit and hence we are trying with BADIs or enhancement point.)
Can anyone please help me with this. I also found an OSS note 1334046 but not sure if that can resolve my issue.
Thanks in advance.
Ameesha.

Hi Ameesha,
i think u need to implement the BADI ME_PROCESS_PO_CUST in SPRO settings.
SPRO>Purchasing>Business Add-in Purchasing-->BAdI: Enhance Processing of Enjoy Purchase Order
try this once.
All check this link.
[Error Message: Data from Business Add-In ME_PROCESS_PO_CUST not transferred;
Hope it helps.
Regards,
Raj

Oss note problem

Hi ,
i applid oss note 1046758. to 2 include and 1 program
includes:
    J_1IEWT_CERT_TOP
    J_1IEWT_CERT_F01
program :
       J_1IEWT_CERT
But i getting error like report/program statement missing.
plz give me solution
Edited by: vasanth kandula on Jan 4, 2008 1:25 PM

Hi,
open the documentation of that note in Tcode "SNOTE", go through the documentation, there they will propse the piece of code to delete and piece of code to add, check wheather it has been done corectly in your includes and program.
while applying notes first it will checks for the context block where it has to delete the code and where it has to include the new code, some times due to manual changes there may be a chance of code misplace.
go through the documentation clearly, it will guide you.
Reward if useful.
Thanks,
Sreeram.

How to create a Attribute "Type standard table OF" to a OSS NOTE

Dear experts,
I need to add new attributes in a standard class as per one OSS note. I took access key to add new attributes. I have a question.
class name: CL_J_1BEFD
Attribute: MT_GROUP_C350
Level: Instance
Visibility: Private
Type STANDARD TABLE OF mty_result
How do i add the instance attribute because i do not want to give the typing and associated type, instead i have to declare data: MT_GROUP_C350 type standard table of mty_result in class builder private section code.
if you look at the pushbutton between Associated type and Description, for all instance attributes there's a green color lining below the arrow. I want my attribute also to be exactly same.
Though i have access key, in private section the display<->Change button is disabled.
Please suggest me how do i add code in private section of a standard class. i have required access key to change the class.
Thanks,
Alysson

Hi Friend...
Thanks, but the question is...
When I went to transaction se24 or se80, I chose the class CL_J_1BEFD and second I swap to "CHANGE MODE".. after that the pushbutton is blocked... I can create the Attribute mt_group_c800 in the Class (using TYPE or LIKE option), but i can't change the code in the private session even using the assistant to modify it.
When I acess the Button "Detail View" the option "Direct Type Entry" is just unavaliable too, no matter what i do!
I coudn't find a way to create the Attibute like the note Describes (SAPNOTE NUMBER 1575772 - in the attachment of the note)
The changes are contained in the attachment
Follows the instructions retrieved from the file:
Add the following Attributes on the Class CL_J_1BEFD Private section
data:
mt_group_c800 TYPE STANDARD TABLE OF mty_result .
data:
mt_group_c850 TYPE STANDARD TABLE OF mty_result .
data:
mt_group_c860 TYPE STANDARD TABLE OF mty_result .
data:
mt_group_c890 TYPE STANDARD TABLE OF mty_result .
How can i make a way to creat this attributes using "TYPE STANDARD TABLE OF " Option?

TUB 166 and OSS Note 1422655 -- Michigan FUTA

We have applied TUB 166 and would like to get the Michigan taxes straightened out since the changes are retroactive to 1/1/2009. I found OSS note 1422655 and it says 'Before apply the instructions of this note, it is necessary to configure unemploymnet tax type 11 for Michigan state in your tax model'. Does that mean that I need to add a record to table V_T5UTD (Config step 'Maintain Tax Types per Tax Authority') and that is the only thing I need to do? Thanks.

Hi ,
You have to mantain the following config. :
1) Tax Model Tables T5UTE, T5UTM and T5UTY.
2) Also mandatory to maintain V_T5UTD (Maintain Tax Type 11 per Tax Auth - - Michigan in this case) and V_T5UTI (Mantain Tax Type per Tax Company Code per Tax Auth ).
3) Also ensure that tax type 11 is maintained at BSI Tax Factory's end for Michigan
FYI: Tax Type 11 is Employer Debt Repayment Tax
Thanks And Regards,
Somdeb.
Edited by: Sombed on Jan 27, 2010 4:08 PM

From where do we see OSS notes and message errors...

hi,
From where do we see OSS notes and message errors details if the error number is provided??
Thanks & Regards

*OSS* are online sap support notes. These notes are available online for solving critical problems in sap system.We may use the already existing notes or may add our own quaries.
In order to apply any OSS note, you have to be authorized by your company and be assigned an OSS ID and password.
For any SAP standard program modification, you are required to login to OSS and request for a repair program Access key.
Access the SAP Support Portal:
*http://service.sap.com/*
- Keys and Requests
-- Request license key
--- Follow the Steps 1 to 5 of the License keys for SAP Business Suite
Follow this step to obtain the Program Access key:
Menu Path: System -> Services -> SAP Service (Transaction code OSS1)
Login in with your OSS ID and Password
Click the Registration button
Click Register Object
Double click R/3 Value Contract
Fill in the Object Registration for Installation:
For e.g.
PGMID/Object/Name: R3TR FUGR MIGO
SAP release: 46C
Finished, click the Register button
Select the Key number and use the Copy and Paste short key to copy the Access key
You are now able to modify the SAP standard program.
Finished the modification, do remember to transport it to the production system after all the necessary testing.
http://www.sap-img.com/basis/what-are-sap-notes.htm
http://www.sap-img.com/basis/oss-notes.htm
http://www.sap-img.com/basis/manually-applying-the-oss-note.htm
Regards,
Ashok

Objects locked in different tasks while implementing the oss note

Hi frnds,
I am facing a problem while implementing the oss note and it shows the message that the objects are locked at different tasks.
Can anybody give the solution.
Sur

Hi Suresh,
Locked in different tasks means there were some repairs carried out for the objects and the transport request is not yet released. Some possible solutions are
1. Ask the owner of the original transport to release the transport. The the object will be unlockedand you can make modifications to it.
2. Ask the user of the above said task to add another task for you in the transport request.
3. See if you can delete the object from that transport and include all the changes in a separate transport of your own and transport. (Please check if any dependencies are there with the other objects in the transport).
Regards
Barada

OSS Note for Clearing to Specific Ledger Group Field

Does anybody know if there is an individual OSS Note that allows you to add this field in the GL Account master without having to install a support / enhancement pack?

Hari,
There is no specific note that allows this functionality, however, after installing EHP 3, you can decide which functionality to activate depending on your requirement.
Regards
Amit Gupta

OSS note for FM ADDRESS_INTO_PRINTFORM

Hi All,
Can anyone please provide me OSS note numbers available for FM ADDRESS_INTO_PRINTFORM.
I want to see OSS notes applicable for printing Countries in address.
Regards,
Imran Kundan.

Better perform (yourself or basis) the search yourself at http://service.sap.com/notes, as the list depends on your exact version/sp level and list of application/add-ons, use keyword BAS_PRINT. And there are MANY notes, already 2 exist for July 2014. You could also start with collective note 35931 - Collective note: Formatting/printing addresses .
Regards,
Raymond

Implementing OSS Note with /SAP/ and /DEVPROG/ - Note 1117955

I am trying to post OSS Note 1117955 which contains a Z* module from SAP as well as multiple changes to SAP modules. This is asking me for a transport for the Z module using /DEVPROG/, but then the SAP module changes are asking for a /SAP/ transport. The Note seems locked on the 1st transport and will not allow me to create a 2nd transport for the SAP program pieces. Anyone run into this before?

Usually when you do a modification to standard code (which a note application basically is) it puts it under a task of type 'Repair'.
Whereas when you change Z-objects they will be put under a task of type 'Development/Correction'
Try the following:
Create a transport that you will use for the note application which contains two tasks: one for repair and one for development/corrections and try to apply the note again by linking it to your new transport.
- SE10
- Create
- Select Workbench
- Confirm
- put in a description
- confirm
- put the cursor on the request
- click on the add user button
- choose your own user name
- confirm (this will add a second task to your transport request)
- click on the first task
- menu request/task - change type
- Choose Repair
- Do the same for the second task and choose development
Hope that helps,
Michael

FI Invoices correction to send via IDoc vs OSS Note 114814

Hi All,
I would like to send Financial Invoice Corrections via IDoc and I am looking for some guidelines and technical explanation on how I should proceed.
I found some explanations in OSS Note 114814 and on other forum threads but I am kind of confused on what I need to do exactly.
I understood that FM EXIT_SAPLF050_008 is involved in the process and also IDoc type FIDCCP01 and FIDCCP02 but I do not know what need to be enhanced in the FM? Does someone have any coding example?
Where exactly is FM EXIT_SAPLF050_008 being called (TCode)? Is it in FB60? I cannot find the enhancement point in this case.
Do I only have to create a project in CMOD and activate it and that's it? I do not know what I need to do in the function module.
Thank you in advance for your guidance. I am a bit lost here to be honest.
Best regards,
Sylvain

first of all u have to find out the user exit.and then if u need to add fields ,then u can write the code here. and then determine the outbound partner profle using tcode WE20. AND then u can u can assign those things in bd64 bussiness model.and if need filters u can set there.
Regards,
Jampani.

OSS Note 1048856 does not fix system error VL 059

Hi all,
we have exactly the issue described in OSS Note: 1048856.
"When you use IDocs to create inbound deliveries, the system issues error VL 059 by mistake 'You cannot add this item to the delivery'."
Our process is:
1. Post over the IDOC DESADV to create the inbound dlry.
2. Within the IDOC we have the Handling Unit (e.g. MATNR 400877).
3. Delivery type (EL) has the item-req. 201
=> IDOC message output: 'You cannot add this item to the delivery'.
When I change the item-req for the delivery type EL to 202 we do not get the message but in that case we cannot complete our goods receipt.
The inbound delivery cannot be completed, although all TO items have been confirmed.
Does somebody has a idea who we can solve the issue without changing the item-req of delivery type from 201 to something else.
Every input is very welcome.
Best regads,
Burhan

Hi All,
Note: The OSS-Note 1048856 is already implemented in our system.
Best regards,
Burhan

OSS note 1044741 contains no correction instructions for 46C.

I am trying to apply OSS note 1044741 to fix BC Set creation for deleted table entries. However OSS note 1044741 contains no correction instructions for 46C. Please provide assistance.
Bruce Reeves

Dear Bruce,
How to raise an OSS note:
In service.sap.com, choose Keys and Requests -> Development Requests -> Create Development Request
The Create development request form appears. It is divided into the sections described below:
Classification
In the 'Classification' section of the form, you can classify your request by selecting various criteria from the listboxes. This information is used for reporting purposes and to assign your request to a processor at SAP.
Reporting unit is only displayed for information. It defines if you enter the request for yourself, on behalf of a Customer Competence Center (CCC), of a customer, or of a user group. Which entries are available depends on the organization you are working for.
Priority defines the priority this request has for you.
Industry is only displayed for information. This is the industry of your company.
Other Industry allows you to select further industries if the request refers not only to your industry. To select more than one industry, hold down the <Ctrl> key and select the desired items by clicking on them.
Component defines the application component to which your request applies.
Core release defines the R/3 release you are currently working with.
Add-on defines, in case the request applies to an industry solution, the specific add-on release you are currently working with.
General provides generic features for a better classification of your request. If you wish to define more than one category, hold down the <Ctrl> key and select the desired items by clicking on them.
Cross-component provides cross-component features for a better classification of your request. If you wish to define more than one application, hold down the <Ctrl> key and select the desired items by clicking on them.
Only relevant for country allows you to specify that your request is only relevant for the selected country.
Personal classification by requestor
In the 'Personal classification by requestor' section, you can add your own classification criteria to the request:
Classification 1 - 3: allows you to specify your own features, e.g., "Project xyz". You can enter any text up to 30 characters in these fields.
Description
In the Description section of the form, you can describe in detail the feature you request for the SAP software.
In the Language field, select the language in which you are describing your request. For processing at SAP, all non-English requests will be translated into English.
In the Short text field, enter a meaningful title for your request.
The Long text field is mandatory. Use it to describe your request in detail. Even if you attach external description files, please enter a detailed description here.
The Business need field is mandatory. Please use it to explain why the requested feature is needed for your business.
The Example field is collapsed by default. Click on the plus symbol to the left of the field to expand the entry field, and enter an example for the requested feature.
The Current workaround field is collapsed by default. Click on the plus symbol to the left of the field to expand the entry field, and describe which procedure you currently use instead of the requested feature.
The Proposed solution field is collapsed by default. Click on the plus symbol to the left of the field to expand the entry field, and describe how you propose to solve the issue related to your request.
Attaching documents
You can also attach files that further describe your request, for example, documents or presentations. All file types supported by this site can be attached, this includes all popular Office formats.
To be able to attach files to your request, you must have the Check In Wizard program installed on your computer. Otherwise, an error message will be displayed. If you do not have the Check In Wizard installed, click here to start the installation
NOTE:
This will automatically save your request with the status New. The request will, however, not yet be sent to SAP. If you have not yet filled in all required fields, the system will prompt you to do so before you can add an attachment. The attachments will be listed only after you have saved or sent the request.
To attach a file, choose Add attachment.
The Check in Files dialog box appears.
Select the file you want to attach, and choose Open.
A status dialog box appears. When the status The check in process has completed successfully is displayed, confirm with OK.
The file is now attached to the development request.
Repeat the above steps for any additional files, if required.
Saving the development request
When you have entered all required data you can save your request. To do this, choose Save. You can then edit the request and send it to SAP later. This allows a company or user group to internally manage, discuss and consolidate its development requests before it decides which development requests will be sent to SAP in the next step. (Development requests that are no longer relevant can be set to status Closed by author).
Sending the development request to SAP
When you have entered all required data, you can alternatively send the request to SAP immediately. To do this, choose Sent to SAP. You need a special authorization to use this function. If you had saved a request before but not yet sent it to SAP, you can send it to SAP later using this function.
Resetting the request form
If you make a mistake during data entry and want to reset all entries to the values they had when you opened the form, choose the Reset button.
Closing the request
If you find that you no longer need the request, you can close it. In this way, you specify that no further processing of the request is necessary.
To close the request, choose Closed by author.
(After closing, confirm the request to remove it from your inbox.)
Confirming the request
Confirm the request if you have received SAP's final decision. The development request will no longer be shown in your Inbox.
To confirm the request, choose Confirm.
You will find the answers in your SAP inbox.
Visit the following link for information regarding SAP Notes:
http://help.sap.com/saphelp_nw04/helpdata/en/b8/3cf839fd35384de10000000a11402f/frameset.htm
Hope this will help.
Regards,
Naveen.

OSS NOTE Number required

Hi Gurus,
could you plese provide me the Related OSS NOTE number for the folowing exception .
TSV_TNEW_PAGE_ALLOC_FAILED
No storage space available for extending the internal table.
You attempted to extend an internal table, but the required space was not available .

Hi u can see the copd here
REPORT /rb17/ym_forc_model_ext_new             .
*& T Y P E S                                                           *
TYPES: BEGIN OF typ_itab_rec.
          INCLUDE STRUCTURE /rb17/ym_mod_new.
TYPES: END OF typ_itab_rec.
table types
TYPES: typ_itab_table TYPE STANDARD TABLE OF typ_itab_rec
          WITH KEY matnr werks .
*& D A T A                                                             *
Internal table to store records from database
DATA : g_t_itab   TYPE typ_itab_table WITH HEADER LINE .
Internal table to fill datbase
DATA : g_t_jtab   TYPE typ_itab_table WITH HEADER LINE .
Work area
DATA : g_r_itab   TYPE typ_itab_rec.
DATA : counter    TYPE i .
DATA cnt type i value 0.
SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS : p_vers TYPE vrsio.
SELECTION-SCREEN END OF BLOCK b1.
*&   Event START-OF-SELECTION
PERFORM get_data.
PERFORM populate_data.
PERFORM assign_version.
PERFORM update_table.
*&      Form get_data
      text
--> p1        text
<-- p2        text
FORM get_data .
REFRESH : g_t_itab[].
SELECT * FROM /rb17/ym_model INTO CORRESPONDING FIELDS OF
           TABLE g_t_itab.
ENDFORM.                    " get_data
*&      Form populate_data
      text
--> p1        text
<-- p2        text
FORM populate_data .
DATA : l_f_bstrf TYPE bstrf,
         l_f_prctr TYPE prctr,
         l_f_maabc TYPE maabc,
         l_f_mfrnr TYPE mfrnr,
         l_f_kondm TYPE kondm,
         l_f_ktgrm TYPE ktgrm,
         l_f_bezek TYPE bezap,
         l_f_lifnr TYPE lifnr.
CLEAR : l_f_bstrf , l_f_prctr , l_f_maabc, l_f_mfrnr,
          l_f_kondm , l_f_ktgrm , l_f_bezek, l_f_lifnr.
CLEAR g_r_itab.
LOOP AT g_t_itab.
    SELECT SINGLE bstrf prctr maabc INTO
       (l_f_bstrf , l_f_prctr , l_f_maabc) FROM marc
       WHERE matnr = g_t_itab-matnr AND
             werks = g_t_itab-werks.
    SELECT SINGLE mfrnr INTO l_f_mfrnr FROM mara
       WHERE matnr = g_t_itab-matnr.
    SELECT SINGLE kondm ktgrm INTO (l_f_kondm , l_f_ktgrm) FROM mvke
       WHERE matnr = g_t_itab-matnr.
    SELECT SINGLE bezek INTO l_f_bezek FROM t25b1
       WHERE wwz02 = g_t_itab-prmgr.
    SELECT SINGLE lifnr INTO l_f_lifnr FROM eord
       WHERE matnr = g_t_itab-matnr AND
             werks = g_t_itab-werks AND
             flifn = 'X'.
    IF sy-subrc NE 0.
      SELECT SINGLE lifnr INTO l_f_lifnr FROM eord
         WHERE matnr = g_t_itab-matnr AND
              werks = g_t_itab-werks .
    ENDIF.
*get backorder value
    PERFORM get_backorders USING g_t_itab-matnr
                           CHANGING g_t_itab-backord.
    g_r_itab-bstrf = l_f_bstrf.
    g_r_itab-prctr = l_f_prctr.
    g_r_itab-maabc = l_f_maabc.
    g_r_itab-mfrnr = l_f_mfrnr.
    g_r_itab-kondm = l_f_kondm.
    g_r_itab-ktgrm = l_f_ktgrm.
    g_r_itab-bezek = l_f_bezek.
    g_r_itab-lifnr = l_f_lifnr.
*set version = 1 for new rows.
    g_r_itab-version = 1.
    MODIFY g_t_itab FROM g_r_itab TRANSPORTING bstrf mfrnr prctr kondm
                                               ktgrm lifnr bezek maabc
                                               backord version.
ENDLOOP.
SORT g_t_itab BY spmon vrsio bukrs matnr version.
ENDFORM.                    " populate_data
*&      Form get_backorders
      text
     -->P_G_T_ITAB_MATNR text
     <--P_G_T_ITAB_BACKORD text
FORM get_backorders USING    p_g_t_itab_matnr TYPE matnr
                     CHANGING p_g_t_itab_backord TYPE netwr_ap.
TYPES: BEGIN OF typ_outord.
          INCLUDE STRUCTURE /rb17/yv_outord.
TYPES: END OF typ_outord.
DATA: t_outord TYPE TABLE OF typ_outord WITH HEADER LINE.
REFRESH: t_outord.
first load outstanding orders for out materials from
nightly extract of data (run from /rb17/yv_outstanding_orders)
SELECT * FROM /rb17/yv_outord INTO TABLE t_outord
      WHERE matnr = p_g_t_itab_matnr.
accumulate all past due orders
LOOP AT t_outord .
    IF t_outord-edatu < t_outord-wadat   "backorder
    OR t_outord-edatu < sy-datum.
      IF t_outord-bmeng > 0.
        ADD t_outord-bmeng TO p_g_t_itab_backord.    "+ confirmed
      ELSE.
        ADD t_outord-kwmeng TO p_g_t_itab_backord.    "+ ordered
      ENDIF.
      SUBTRACT t_outord-lfimg FROM p_g_t_itab_backord.    "- delivered
    ENDIF.
ENDLOOP.
ENDFORM.                    " get_backorders
*&      Form update_table
      text
--> p1        text
<-- p2        text
FORM update_table .
DELETE FROM /rb17/ym_mod_new.
MODIFY /rb17/ym_mod_new FROM TABLE g_t_jtab .
COMMIT WORK.
ENDFORM.                    " update_table
*&      Form assign_version
      text
--> p1        text
<-- p2        text
FORM assign_version .
delete records with version = no of versions given by user.
LOOP AT g_t_itab .
    IF g_t_itab-version EQ p_vers.
      DELETE g_t_itab.
      CONTINUE.
    ENDIF.
ENDLOOP.
Changing versions and populating final internal table
LOOP AT g_t_itab .
    counter = p_vers - 1 .
    DO counter TIMES .
      MOVE-CORRESPONDING g_t_itab TO g_r_itab.
      g_r_itab-version = counter + 1 .
      APPEND g_r_itab TO g_t_jtab .
      counter = counter - 1.
      CLEAR g_r_itab.
    ENDDO .
ENDLOOP.
SORT g_t_itab BY spmon vrsio bukrs matnr version.
ENDFORM.                    " assign_version

"MDM 3.0 Add-on" - oss note 748777? missing

Similar Messages

Maybe you are looking for