SAP Training, Tutorials, How-tos, News, Weblogs, Screencasts, SAP Jobs, Forums and much more, all on SAP » TCodes

Top 25 SCN Blogs of all Time

webmaster — Tue, 10 Jan 2012 10:07:36 +0000

At a time where the SCN website is due to have a clean face, SAP employee and SAP mentor Mark Finnern delights us, yet again, with a highly useful post titled “Top 25 SCN Blogs of all Time“. In case you have missed it, here is your opportunity to know which are the most popular SAP SCN weblogs, of all time. This ranking has been produced taking in consideration the number of user views, counted on the last 8 years. So these are the most viewed weblogs, which obviously reflect which SAP subjects users are more interested in.

Mark Finnern also adds a few observations that sustain this thorough list:

Wow there are some well known names and some surprises in the list, not the least the number one blog post by Steffen Weber. With 178K almost twice as many hits as the famous often updated originaly named XI FAQ post by Michal Krawczyk. Looks like the Excel Macro File referenced in Steffen’s blog post does come really handy. Congratulations Steffen for having written the most viewed post of the last 8 years.

I have to smile seeing that Michal’s XI/PI FAQ post is #2. I had long discussion with him why this kind of content should be moved to a wiki page so that everyone can improve it. His argument is that you need a curator, otherwise the quality isn’t there. Number of views he got is proofing his point, comments of certain links not working anymore can be counted for the wiki camp, but this is not the blog post to bring up that argument again, but to celebrate the top blog posts of SCN.

Thomas Jung can ad the title Master of SCN blogging to the long list of his career achievements, as 6 of his posts are in the top 25. I am always at awe seeing the beauty and quality of his posts. I remember the early beginnings when Brain McKellar nudged him after seeing his excellent BSP forum answers to post blogs. I am so glad he did oh and we miss Brian on SCN.

Love it that a Crystal Report post by Blair Wheadon is #5. It is a beautiful proof, that the BOBJ community has found a home on SCN. Being posted only 2 years ago in December 2009 it is also the youngest blog post on the list. Really amazing that it is on rank #5 already. Well done Blair.

Just wow that there are still 3 Roberto Negro posts in this top 25 list. He used to dominate the BW space, as it was called back in the mid 2000s. He moved on and is unfortunately not working in the SAP space anymore. Really bummed that he nver made it to a TechEd, or at least I don’t remember. I hope the hammock he once offered me is still standing somewhere in Italy waiting for me to relax in. Roberto we really miss you here, please come back.

Manfred Lutz and Ingo Hilgefort are the other two bloggers that have more than one post in the list. We have over 3000 SCNers who have written at least one post, To be in the top 25 is quite the achievement. Thank you all for putting the effort in.

Top 25 SCN Blogs of all Time

1. SAP NetWeaver Portal Reporting for Collaboration Rooms
This Blog describes how to create consolidated and ordered reports out of standard SAP NetWeaver Portal collaboration room raw data files.
Steffen Weber in Knowledge Management (KM), Standards, SAP NetWeaver Platform

2. XI/PI FAQ (Frequently Asked Questions)
Exchange Infrastructure – Frequently Asked Questions
Michal_Krawczyk_PIXI in SAP Process Integration (PI)

3. Sending E-Mail from ABAP – Version 610 and Higher – BCS Interface
Yesterday I posted a weblog on how to send E-Mails from ABAP in releases <= 46D using the API functions. Today we are going to look at releases >= 610 and the BCS Interface.
Thomas Jung in ABAP, Application Server

4. Web Dynpro ABAP Demonstration Videos
Web Dynpro, with its strong graphical modeling environment, provides an interesting challenge for authors of all types of written materials on the subject. Often videos can fill that gap. This weblog describes several hours of newly released Web Dynpro ABAP videos.
Thomas Jung in ABAP, Beginner, Enterprise Portal (EP), Web Dynpro

5. Crystal Reports in Visual Studio 2010
An overview of how Microsoft Visual Studio 2010 customers will receive Crystal Reports.
Blair Wheadon in SAP Crystal Reports, Interoperability .NET

6. New Blog Series: ABAP Trial Version for Newbies
New Blog Series: ABAP Trial Version for Newbies With the new build of the SAP NetWeaver 2004s ABAP Trial Version (SP11), we in SAP NetWeaver Product Management are eager to introduce, through a series of blogs, SAP ABAP technology to those with limited ABAP experience.
Manfred Lutz in ABAP, Application Server, Beginner, Web Dynpro

7. BusinessObjects and SAP Part I
This is Part I of a series on BusinessObjects and SAP products.
Ingo Hilgefort in Enterprise Data Warehousing/Business Warehouse, Business Intelligence (BusinessObjects), Business Process Expert

8. How do you activate ABAP Proxies?
Have you got the error message “Unable to connect to the Integration Builder, when you are trying to create a ABAP PROXY from a R/3 system? This blog show the steps to be executed to make sure you are able to build ABAP Proxies.
vijaya kumari in SAP Process Integration (PI)

9. SAP NetWeaver 7.0 – Java and ABAP Trial Version on Linux – VMware Edition – Tips & Tricks
Here you find the required steps missed out in the official Documentation. How to get the Application Server running, install the License and connect from Windows.
Gregor Wolf in ABAP, SAP NetWeaver Platform

10. BSP a Developer’s Journal Part XIV – Consuming WebServices with ABAP
In this BSP Developer’s Journal we once again look at a technology that just does ride on the edge of the BSP environment. We look at how we can call WebServices with ABAP.
Thomas Jung in Business Server Pages, ABAP, Application Server

11. LOGISTIC COCKPIT DELTA MECHANISM – Episode one: V3 Update, the ‘serializer’
This is the first episode of a series (of three) concernig delta mechanism in the Logistic Cockpit for BW. Here you can find a short overview examining the conception and technical background of delta extraction related to logistic flows towards BW system by using the Serialized V3 Update.
Roberto Negro in Enterprise Data Warehousing/Business Warehouse

12. Basic ABAP OO eLearnings
I frequently receive requests for learning materials on basic ABAP Object Oriented concepts. In response I have created a 5 part eLearning series that is intended to be accessible to anyone just starting out with ABAP OO.
Thomas Jung in ABAP, Beginner, Business Server Pages, Web Dynpro

13. Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
This aim of this blog is to discuss how to configure your browser parameters as well as discuss how to install the latest SAP NetWeaver 2004s BI Frontend Components. Keep in mind that it is always best to keep your frontend patches up to do date. This article covers most of the issues I’ve seen when working with different browsers and frontend components specifically related to installation of frontend components.
Prakash Darji in Enterprise Data Warehousing/Business Warehouse, Enterprise Portal (EP)

14. LOGISTIC COCKPIT – WHEN YOU NEED MORE – First option: enhance it !
Through this weblog we will go on in our tour around the logistic data extraction world: after having familiarized with the data flows that the system can run for every available update methods in LBWE and before approaching all the other extraction mechanisms managed by SAP Business Warehouse, now it’s necessary facing this question: what’s happen if a standard logistic datasource (and its related information set) is not enough for our needs ?
Roberto Negro in Enterprise Data Warehousing/Business Warehouse

15. Web Dynpro ABAP exercises from TechEd 2007
For those who are looking to improve their Web Dynpro ABAP skills, here is the content of the hands-on session for Web Dynpro ABAP at TechEd 2007. Based on the ESM (Enterprise Sales Model), the exercises are structured so that the result of one task forms the foundation for the next exercise. The download contains all required objects, the ESM data generator, the example solutions, the templates, and the document ‘CD255 Developing User Interfaces with Web Dynpro ABAP’. All you need is a local installation of the latest ABAP Trial Version.
Manfred Lutz in ABAP, Application Server, Web Dynpro

16. Gravity – Collaborative Business Process Modelling within Google Wave
Gravity is a prototype developed by SAP Research in Brisbane, Australia and SAP NetWeaver Development providing real-time, cloud-based collaborative business process modelling within Google Wave. Google Wave is Google’s new real-time collaboration platform that combines features of e-mail, social networking, wikis and instant messaging in one integrated browser-based client.
Alexander Dreiling in Service-Oriented Architecture, Business Process Expert, Business Process Management, Business Process Modeling, Business Rules Management, Composition Environment (CE), Consumer Products, Insurance, Interoperability, SAP NetWeaver Platform, SAP Research, Enterprise Social Systems

17. Update Your ABAP Development Skills to SAP NetWeaver 7.0
If the title of this blog sounds familiar, then chances are good that you have attended session CD251 at one of the TechEds this year. Now find out how some of the core content of this TechEd Session has been made available as an Online SDN E-Learning.
Thomas Jung in ABAP, Service-Oriented Architecture, SAP Process Integration (PI), SAP TechEd, Web Dynpro

18. BusinessObjects and SAP – Installation and Configuration Part 1 of 4
In this blog series I am describing the steps that are required to install and configure the BusinessObjects solution on top of a SAP BI system (Part #1).
Ingo Hilgefort in Analytics, Enterprise Data Warehousing/Business Warehouse, Business Intelligence (BusinessObjects), Community Day, ERP, SAP NetWeaver Platform, SAP TechEd

19. ABAP Proxies in XI(Client Proxy)
The other way of interfacing XI is through proxies. From WAS 6.20, proxy generation feature enables application systems to communicate with XI using proxies. Proxy generation enables you to create proxies in application systems. Proxies encapsulate the creation or parsing of XML messages and the communication with the relevant runtime components required to send or receive the messages.
Ravikumar Allampallam in SAP Process Integration (PI)

20. Generic Extraction via Function Module
Short overview about the extraction api, using custom defined function modules.
Siegfried Szameitat in Enterprise Data Warehousing/Business Warehouse

21. Aspirant to learn SAP XI…You won the Jackpot if you read this!-Part I
My inbox is flooding with many mails soliciting the direction to start their career into SAP XI. I am too lethargic to reply for everyone as it is a bit lengthy process to explicate it in a mail. You can ask me, Why am blogging so late? I told you already am lazy to pen lengthy stuff:)…But…One day I got a mail from an graduate student asking me to guide him…!!….Alas! Iam amazed and impressed with that mail….I guess SDN Community has accomplished its goal in global marketing and inspiring all sorts of people across the globe……Kuddos to SDN!…
Sravya Talanki in SAP Process Integration (PI)

22. LOGISTIC COCKPIT DELTA MECHANISM – Episode three: the new update methods
This third episode describes in detail all the elements required to help make an aware selection of the right new update method (after the serialized V3 update mechanism replacement) for the applications related to the Logistic Cockpit.
Roberto Negro in Enterprise Data Warehousing/Business Warehouse

23. Http* Errors in XI
There are many forum discussions about Http Errors. This blog is collective information about most common HTTP errors occurring during XI implementations and possible tips to solve the problems.
Krishna Moorthy P in SAP Process Integration (PI)

24. SAP’s definitive strategy for planning technologies moving forward: What’s the word on BPC, BI-IP and SRC?
This blog discuss SAP’s direction for planning products. It describes SAP’s official stance, and provides a bit more insight into Business Planning and Consolidation 7.0, version for SAP NetWeaver.
Ryan Leask in Analytics, Enterprise Data Warehousing/Business Warehouse, Business Intelligence (BusinessObjects), Business Process Expert, Business Process Management, Business Process Modeling, Business Solutions, Enterprise Performance Management, SAP NetWeaver Platform

25. First steps to work with Change Request Management scenario
This blog describes how to create a test landscape to practice with the Charm scenario in Solution Manager 7.0 without creating interferences with real TMS landscapes. Also you will find tips and tricks for the common mistakes in the configuration of this scenario.
Dolores Correa in SAP Solution Manager

Many thanks again to Mark Finnern for this great contribution. Here is Mark’s career summary.

Mark Finnern is the Chief Community Evangelist of the SAP Community Network focusing on the SAP Mentor initiative. He is an SAP veteran, has implemented SAP FI/CO at many customers in Germany and the US. Was the co-inventor of the Pre-Configured Client (PCC), which at times was used by 90% of all US SAP customers to save implementation time. It evolved into SAP’s Best Practices and All-In-One offerings. He is the proud owner of a Traffic Monitoring System patent. Mark was the driving force behind community features of the SAP Community Network: Blogs, points recognition system, wiki, Community Day now Inside Track. Mark Finnern has a bachelor’s degree in Business oriented Computer Science from the Fachhochschule in Furtwangen Germany. He is also the founder and host of the Future Salon with its new tag line: Creating a world that works for all.

Source: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/27705

10 SAP Blogs you must follow

webmaster — Thu, 02 Jun 2011 10:47:11 +0000

It sometimes seems difficult to find your ways in the SAP neverending web of information. Anyone who works with SAP knows that a big part of their job is to constantly search and digest the best piece of information (ideally) they can find. These mostly originate from various sources and most of the times, in what refers to blogs, at least half of them are low quality.

Being that said, I’ve decided to write this post and reveal which are my top SAP fellow blogs, whom I follow and recommend that you visit.

1. SAP Community Network Blogs

SAP blogs are by far the most complete and extensive source of information. It also has the advantage of being supported by SAP and its contents managed and updated by SAP employees, SAP mentors and other credible SAP professionals. The downside to it is that you’ll need an SAP user in order to view it fully or be able to post comments.

Link: http://www.sdn.sap.com/irj/scn/weblogs

2. SearchSAP

Owned by TechTarget, SearchSAP is a very complete website and blog with more than tutorials or how-to’s on SAP. It contains news, expert advice, technical tips and career guidance, latest applications as well as future ERP system plans with breaking news coverage from independent editors. I recommend this website and its rich content.

Link: http://searchsap.techtarget.com/

3. JonERP.com

Jon Reed’s blog is widely known and is a complete source that I recommend for any SAP professional. Jon actively blogs about several SAP emerging areas, SAP market trends, with a special focus on SAP career – Jon Reed’s blog has a special SAP Career Center page, designed for people wanting to know more about careers on SAP and how to enhance it. Jon also is consistently posting new podcasts and webcasts.

Link: http://www.jonerp.com

4. Pixelbase

Michael Koch is the driver of Pixelbase, which I recommend that you follow and visit on a regular basis. Michael is an experienced independent consultant and he’s also a well known SAP Mentor. Pixelbase is the commercial face of Michael’s activity, however, you’ll find that there is much to learn from the blog, covering topics such as SAP Web Development (ITS, BSP, WebDynpro for ABAP), custom SAP Development (ABAP and ABAP OO), RIA (Adobe Flex), Interfaces (ALE, IDOCS, XML), SAP CRM development and Data Migration, as well as conference coverage, among others.

Link: http://www.pixelbase.co.uk/

5. Feeding the SAP EcoSystem

Peter Russo is the main blogger and webmaster of Feeding the SAP EcoSystem blog. Unlike others, this blog focuses more on SAP products and Peter includes his personal experiences in each post he writes. Benefiting from the fact that he appears to attend lots of SAP events, he also transmits these experiences to the blog, which are obviously enriching for any of us. It is ideal if you want to understand what’s going on in the SAP world and also where SAP is going in the future.

Link: http://www.feedingthesapecosystem.com

6. Blag’s Bag of Rants

Blag is Alvaro Tejada Galindo’s nickname on twitter (@blag),. Alvaro is a senior ABAP Consultant, SAP Mentor, Programming Geek, Blagbert/Programming books author. Alvaro is Peruvian and lives in Montreal, Canada. If you want technical, Blag’s blog is the place to go.

Link: http://blagrants.blogspot.com/

7. Friday Morning Report

The Friday Morning Report is owned and managed by Craig Cmehil, a well known SAP community evangelist that works for SAP AG as a Director for Social Media Relations. Hence, Craig is very active in his blogging, tweeting and moderating discussions over at the SCN website and blogs.

Link: http://fridaymorningreport.tv/

8. SAP WEB 2.0

This is an interesting blog that I also follow. It focuses in cloud computing solutions and 3 main areas: Web 2.0 by SAP, Web 2.0 in SAP and Web 2.0 with SAP. It is worth taking a look!

Link: http://www.sapweb20.com/blog/

9. SAP Bloggers Corner

SAP Bloggers corner is intended to promote conversation about what SAP is doing in the market. The main attraction of this blog is the livestream feature, podcasts and broadcasts, published on a regular basis.

Link: http://sapbloggerscorner.com/

10. ERP Genie

I think this was the first SAP blog I visited, ever since I started in the SAP world. It is very rich in content covering SAP podcasts (from Jon Reed), Job Board, Foruns, FAQs, whitepapers and tutorials, etc. You can also browse the blog based on your user/consultant profile, i.e., Functional or Technical. The blog also contains a very complete section on SAP General. It’s a really good starting point for anybody and definitely a blog that you want to come back.

Link: http://www.erpgenie.com/

Hope you liked this blog list; these are just a few of the ones I follow on a regular basis. What are your favourite blogs?

How to create a Sales Order in SAP (Part 1)

webmaster — Wed, 23 Feb 2011 11:21:50 +0000

In this session, we are going to understand how to create a sales order in SAP SD. For more tutorials like these or for SAP Training, please visit Magna Training.

Business Scenario: A customer has placed an order with company ABC Computers Inc., for 10 computers to be delivered on 10th of March. The customer typically pays with Net30, but this time for this order, he wants a Net 60 payment terms.

Step No. 1: Use the Transaction Code [ VA01 ] to create the Sales Order in SAP. Alternatively, you can use the menu path as shown in the picture below [ Logistics -> Sales and Distribution -> Sales -> Order -> Create ]

Step No. 2: Use the document type ‘OR’ in the field Order Type.

Select a Customer ( say 1400 ) and enter some text in the Customer PO Number field and either hit the return key or the Green check mark button. This will ensure that SAP will validate the data you have entered.

Step No. 3: Enter a material number and quantity. We have chosen a material of M-01 (representing Computer product) and a quantity of 10 based on the scenario. As you can see, the corresponding material descriptions and other information is automatically pulled up by SAP.

Step No. 4: As you can see, SAP automatically proposed a Requested Delivery date (28/02/2011) from the picture above. This data is retrieved from the lead time configuration in the Sales Order. However, since the customer has requested that the goods be delivered on March 10th, let’s change the requested delivery date.

Hint: Always change the Requested Delivery Date before you enter the line items.

Step No. 5: Since the customer has requested a change in the Payment terms, let’s select the right payment terms from the SAP Search Help.

Since the customer has requested a payment terms of NET 60, we are choosing a payment terms of ‘0004’ – Within 60 days due net.

Step No. 6: If you are done with creating the Sales Order in SAP, click the save button to finish the order. SAP will display the order number at the bottom.

In the next parts of this series, we will discuss more about how to manipulate more fields in the SAP sales order and the business significance of those fields.

How Many Lines of ABAP Code In Your System?

webmaster — Mon, 31 Jan 2011 12:19:58 +0000

I ran into a curious post by Sergio Ferrari which allows us to calculate how many lines of ABAP code we have in our systems. More than a curiosity, this simple tool can help us determine if our system is too overloaded with custom code or not.

The author excluded ABAP generated by special frameworks, like Report writer, SAP Query, Web Dynpro, LSMW, and so on. He opted to do the filtering by Source System, Owner and Package. The release covered by this tool is ECC 6.0 an the following are also out of scope of this tool:

BSP’s
Adobe Forms, Smartforms and SAPScript
XSLT/Web Services

This utility was named ZSDN_simple_ABAP_SLOC_COUNT, and aims to be an an indicator. The author didn’t want to give it too much relevance, the idea is solely to be an useful tool and help us estimate the upgrade effort or to evaluate the amount of work allocated for each of our packages.

As a curiosity, the post also includes the following information, related to lines of code in known software systems:

Windows XP: 45 million lines of code
Windows Vista: 50 million lines of code
Mac OS: 86 million lines of code
SAP (ABAP): 238 million lines of ABAP

Copy the code from the textearea below and paste it in a new report in transaction code SE38.

*&---------------------------------------------------------------------*
*& Report  ZSDN_SIMPLE_ABAP_SLOC_COUNT
*& Author: Andrea Olivieri, Sergio Ferrari
*&         Techedge SpA
*& Version: 1.0  - 2009/01/20
*& Title   How many lines of custom ABAP code are inside your system?
*&---------------------------------------------------------------------*
REPORT  zsdn_simple_abap_sloc_count_n LINE-SIZE 255.

* Global Data Type [ GDT   ]
TYPES: BEGIN OF ty_repository,
         devclass  TYPE tadir-devclass,
         name      TYPE trdir-name,
         object    TYPE tadir-object,
         srcsystem TYPE tadir-srcsystem,
         author    TYPE tadir-author,
         subc      TYPE trdir-subc,
         sloc      TYPE i,
       END OF ty_repository.
DATA: l_repository TYPE ty_repository.
DATA: t_repository TYPE STANDARD TABLE OF ty_repository.

* defining the selection-screen
TABLES: tadir.
SELECT-OPTIONS: xpack   FOR tadir-devclass,
                xobject FOR tadir-object,
                xauthor FOR tadir-obj_name.

INITIALIZATION.
  PERFORM init_select_options.

START-OF-SELECTION.
  PERFORM get_obj_set.
  PERFORM upd_obj_set_count_class_sloc.
  PERFORM count_prog_sloc.

END-OF-SELECTION.
  PERFORM alv.

*&---------------------------------------------------------------------*
*&      Form  init_select_options
*&---------------------------------------------------------------------*
*       INCLUDE OBJECTS:  PROG, FUGR and CLAS
*       EXCLUDE PACKAGES: $TMP and from A to W
*       EXCLUDE USERS:    SAP, SAP*, DDIC
*----------------------------------------------------------------------*
FORM init_select_options.

* Include objects: PROG, FUGR and CLAS
  IF xobject[] IS INITIAL.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'PROG'.
APPEND xobject.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'FUGR'.
APPEND xobject.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'CLAS'.
APPEND xobject.
  ENDIF.

* Exclude packages: $TMP and from A to W
  IF xpack[] IS INITIAL.
    xpack-sign   = 'E'. xpack-option = 'BT'. xpack-low = 'A'. xpack-high
= 'WZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'. APPEND xpack.
    xpack-sign   = 'E'. xpack-option = 'EQ'. xpack-low = '$TMP'. APPEND
xpack.
  ENDIF.

* Exclude objects belonging to users: SAP* and DDIC
  IF xauthor[] IS INITIAL.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'SAP'.  APPEND xauthor.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'SAP*'. APPEND xauthor.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'DDIC'. APPEND xauthor.
  ENDIF.
ENDFORM.                    "init_select_options

*&---------------------------------------------------------------------*
*&      Form  get_obj_set
*&---------------------------------------------------------------------*
*       Get from TADIR
*----------------------------------------------------------------------*
FORM get_obj_set.
  DATA: l_tadir TYPE tadir.

  SELECT * FROM tadir INTO l_tadir
           WHERE pgmid      EQ 'R3TR'
           AND   obj_name   IN xauthor
           AND   object     IN xobject
           AND   devclass   IN xpack
            AND srcsystem   NE 'SAP'
           AND   author     IN xauthor.               "#EC CI_SGLSELECT
    IF NOT l_tadir-obj_name CP '_______________________________*'.
      MOVE-CORRESPONDING l_tadir TO l_repository.
      l_repository-name     = l_tadir-obj_name.
      l_repository-devclass = l_tadir-devclass.
      APPEND l_repository TO t_repository.
    ENDIF.
  ENDSELECT.
*
  SORT t_repository BY devclass name.

ENDFORM.                    "get_obj_set

*&---------------------------------------------------------------------*
*&      Form  upd_obj_set_count_class_sloc
*&---------------------------------------------------------------------*
*       ...and Compute SLOC for CLAS
*----------------------------------------------------------------------*
FORM upd_obj_set_count_class_sloc.
  TYPE-POOLS: sedi.
  TYPES: BEGIN OF ty_irdir,
          name LIKE trdir-name,
          devc    LIKE tadir-devclass,
        END OF ty_irdir,
        BEGIN OF ty_itab,
          repname LIKE sy-repid,
          devc    LIKE tadir-devclass,
        END OF ty_itab,
        BEGIN OF ty_crdir,
          name LIKE trdir-name,
          subc LIKE trdir-subc,
          devc    LIKE tadir-devclass,
        END OF ty_crdir.

  DATA: save_tabix      TYPE sy-tabix,
        l_class         TYPE sobj_name,
        l_pgmid         TYPE pgmid,
        l_object        TYPE trobjtype,
        class_name      TYPE programm,
        class_pool_name TYPE programm,
        lclskey         TYPE seoclskey.
  DATA: sourceline      TYPE string.
  DATA: l_1st_char      TYPE c.

  DATA: l_irdir         TYPE ty_irdir,
        l_itab          TYPE ty_itab,
        l_itab1         TYPE ty_itab,
        l_crdir         TYPE ty_crdir.
  DATA: t_irdir TYPE STANDARD TABLE OF ty_irdir,
        t_itab  TYPE STANDARD TABLE OF ty_itab,
        t_itab1 TYPE STANDARD TABLE OF ty_itab,
        t_crdir TYPE STANDARD TABLE OF ty_crdir.

  DATA: l_sloc          TYPE i.

  LOOP AT t_repository INTO l_repository.
    save_tabix = sy-tabix.
    CASE l_repository-object.
      WHEN 'PROG'.
        SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE  name
= l_repository-name.
        IF sy-subrc = 0.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING subc .
        ENDIF.
      WHEN 'FUGR'.
        CONCATENATE 'SAPL' l_repository-name INTO l_irdir-name.
        l_irdir-devc = l_repository-devclass.
        APPEND l_irdir TO t_irdir.
        l_repository-name   = l_irdir-name.
        l_repository-object = 'PROG'.
        SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE  name
= l_repository-name.
        IF sy-subrc = 0.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING name object subc.
        ENDIF.
        CLEAR l_irdir.
      WHEN 'CLAS'.
        DATA source_new TYPE sedi_source.
        DATA l_inctype(5).

        class_name = l_repository-name.
        l_pgmid = 'R3TR'.
        l_object = l_repository-object.
        l_class = class_name.
        CALL FUNCTION 'SEO_CLASS_GET_CP_NAME'
          EXPORTING
            pgmid                 = l_pgmid
            object                = l_object
            obj_name              = l_class
          IMPORTING
            progname              = class_pool_name
          EXCEPTIONS
            no_class_or_interface = 1.

        IF sy-subrc = 0.
          SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE name
= class_pool_name.
        ENDIF.

        lclskey-clsname = cl_oo_classname_service=>get_clsname_by_include(
class_name ).

        CLEAR l_class.
        CONCATENATE l_repository-name '%' INTO l_class.

        SELECT name FROM  trdir INTO TABLE t_crdir WHERE  name  LIKE
l_class.
        IF NOT t_crdir[] IS INITIAL.
          LOOP AT t_crdir INTO l_crdir.
            l_inctype = l_crdir-name+30(5) .
            REFRESH source_new.
            CALL FUNCTION 'SEO_CLASS_GET_INCLUDE_SOURCE'
              EXPORTING
                clskey                       = lclskey
                inctype                      = l_inctype
              IMPORTING
                source_expanded              = source_new
              EXCEPTIONS
                _internal_class_not_existing = 1
                not_existing                 = 2
                OTHERS                       = 3.
            CHECK sy-subrc = 0.

*           Compute SLOC !
            LOOP AT source_new INTO sourceline.
              l_1st_char = sourceline.
              IF    sourceline IS INITIAL
                 OR l_1st_char = '*'.
                DELETE source_new INDEX sy-tabix.
              ENDIF.
            ENDLOOP.
            l_sloc = LINES( source_new ).
            ADD l_sloc TO l_repository-sloc.
          ENDLOOP.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING sloc subc.
        ENDIF.
      WHEN OTHERS. CONTINUE.
    ENDCASE.

  ENDLOOP.

  IF t_irdir[] IS NOT INITIAL.
    LOOP AT t_irdir INTO l_irdir.
      REFRESH t_itab1.
      CALL FUNCTION 'GET_INCLUDES'
        EXPORTING
          progname = l_irdir-name
        TABLES
          incltab  = t_itab1.

*     append lines of t_itab1 to itab.
      LOOP AT t_itab1 INTO l_itab1.
        l_itab-repname = l_itab1-repname.
        l_itab-devc    = l_irdir-devc.    "Sometimes it's false
        APPEND l_itab TO t_itab.
        CLEAR l_itab.
      ENDLOOP.
    ENDLOOP.
  ENDIF.

  DATA: l_trdir TYPE trdir.

  LOOP AT t_itab INTO l_itab.
    SELECT SINGLE * FROM  trdir INTO l_trdir
           WHERE  name  = l_itab-repname
            AND    cnam  NOT LIKE 'SAP%'
            AND    cnam  <> 'DDIC'.
    CHECK sy-subrc = 0.

    MOVE-CORRESPONDING l_trdir TO l_repository.
    l_repository-devclass = l_itab-devc.
    l_repository-object   = 'PROG'.
    APPEND l_repository TO t_repository.

  ENDLOOP.

  SORT t_repository BY name object devclass.
  DELETE ADJACENT DUPLICATES FROM t_repository COMPARING name object
devclass.

ENDFORM.                    "upd_obj_set_count_class_sloc
*&---------------------------------------------------------------------*
*&      Form  count_prog_sloc
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM count_prog_sloc.
  DATA: l_prog     TYPE c LENGTH 30.
  DATA: isource    TYPE TABLE OF string.
  DATA: l_1st_char TYPE c.

  LOOP AT t_repository INTO l_repository WHERE object = 'PROG'.
*   Compute SLOC !
    l_prog = l_repository-name.
    READ REPORT l_prog INTO isource.
    DATA: l_source_line TYPE string.
    LOOP AT isource INTO l_source_line.
      l_1st_char = l_source_line.
      IF    l_source_line IS INITIAL     "Empty
         OR l_1st_char = '*'.            "Comment
        DELETE isource INDEX sy-tabix.
      ENDIF.
    ENDLOOP.
    l_repository-sloc = LINES( isource ).

*   Update SLOC into t_repository
    READ TABLE t_repository WITH TABLE KEY name     = l_repository-name
                                       devclass = l_repository-devclass
                                       object   = l_repository-object
                                       srcsystem = l_repository-srcsystem
                                       author    = l_repository-author
                                       subc      = l_repository-subc
                        TRANSPORTING NO FIELDS.
    IF sy-subrc = 0.
      MODIFY t_repository FROM l_repository INDEX sy-tabix TRANSPORTING
sloc.
    ENDIF.
  ENDLOOP.
ENDFORM.                    "count_prog_sloc

*&---------------------------------------------------------------------*
*&      Form  alv
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM alv.
  DATA: gr_table     TYPE REF TO cl_salv_table,
        gr_display   TYPE REF TO cl_salv_display_settings,
        gr_functions TYPE REF TO cl_salv_functions,
        gr_sorts     TYPE REF TO cl_salv_sorts,
        gr_agg       TYPE REF TO cl_salv_aggregations.
  TRY.
*     Create ALV table
      cl_salv_table=>factory( IMPORTING r_salv_table = gr_table CHANGING
t_table = t_repository ).
*     Set zebra layout
      gr_display = gr_table->get_display_settings( ).
      gr_display->set_striped_pattern( cl_salv_display_settings=>true ).
*     Display all standard function
      gr_functions = gr_table->get_functions( ).
      gr_functions->set_all( abap_true ).
*     Sort
      gr_sorts = gr_table->get_sorts( ).
      gr_sorts->add_sort( columnname = 'DEVCLASS' subtotal = abap_true ).
      gr_sorts->add_sort( columnname = 'NAME'     subtotal = abap_false ).
*     Totals
      gr_agg = gr_table->get_aggregations( ).
      gr_agg->add_aggregation( 'SLOC' ).
*     Display table
      gr_table->display( ).
    CATCH cx_salv_msg.
      WRITE: / 'Exception CX_SALV_MSG'.
    CATCH cx_salv_not_found.
      WRITE: / 'Exception CX_SALV_NOT_FOUND'.
    CATCH cx_salv_data_error.
      WRITE: / 'Exception CX_SALV_DATA_ERROR'.
    CATCH cx_salv_existing.
      WRITE: / 'Exception CX_SALV_EXISTING'.
  ENDTRY.
ENDFORM.                    "alv

Additional links and resources:

Source lines of code (wikipedia)

Position and Personnel Area have different Controlling Area

webmaster — Mon, 18 Oct 2010 11:39:21 +0000

Following my previous post “Submit an Article, Win a Free Ad“, it is with great pleasure that I announce the winner for this free campaign. Winner is website “Perfect Resources” which is a website and Blog specialized in SAP HR eLearning solutions.

This article focuses on a particular situation in SAP HR, typically when the user is performing a Hiring Action. You have created a position and attached it to an Organization Unit. You have the position ID and everything is all set. Now you want to hire an employee into this position. You go to transaction PA40 and select a date and then select the hire action. You enter the required information, enter the position number and the position attributes are defaulted, now you hit enter again and you get at error message “Position and Personnel Area have different controlling area“… hmm what is this?

You can do a couple of things to resolve this issue. First go to transaction code SPRO, click on Enterprise structure then assignments. Click on Controlling and then assign Company Code to Controlling Area. Click on the Controlling Area which has your country’s name and then click on Assignment of Company Code.

Next, check to see if your Company Code exists.

Now go to transaction code PO13 and enter the position ID which you created. Check Account Assignment infotype 1008 and click on display. Verify the Company Code and Controlling Area. If it’s not the same, let your finance guy know this.

You can also resolve this issue by going through transaction code PO13, enter the Position ID you created and click on Relationship infotype. Select the radio button All and then click on Overview. Select the relationship A003 Belongs To and click on display.

Copy the Organization Unit ID and open a new screen. Type in transaction code PO10 and enter the Organization ID you just copied. Now click on Relationship type infotype and select overview. Check if there is a A011 Relationship; it should be there. Select this relationship and if you know the right cost center click on change, enter the correct cost center over here and click on save.

Now go back to the hire action screen and continue with your hiring.

Author: PerfectResource.net

How to Send a System Message to another SAP User

webmaster — Thu, 22 Jul 2010 14:06:58 +0000

Imagine that you’re working configuring a certain SAP module, touching several tables and configuration spots. Sometimes it might happen that someone else is maintaining the same table that you need access. This standard Function Module could be useful in these cases, since you might not know an alternative way to contact the user locking the table or other SAP object. Since the system will display who is locking the table, you will know for whom to send the message.

Here’s how it goes.

Trying to access the table

When trying to maintain a certain table, the user will receive the following warning:

Sending a system message using a standard SAP function module

Once you’ve identified the user, access SE37 – assuming you have permission! In SE37 call SAP standard function module TH_POPUP.

Fill in the following input parameters:

- CLIENT: the system client on which you’re working on. If you don’t know this, take a look at the lower right status bar;
- USER: the user for which you want the message to be delivered;
- MESSAGE: the text message you want to deliver to the user;
- MESSAGE_LEN: allows you to define a message length. Leave it empty;
- CUT_BLANKS: allows you to specify if you want to trim existing spaces. Leave it empty.

To submit the message just hit “Execute (F8)”

What the user receives

When you click on “Execute (F8)”, the destination user receives the following message as a pop-up:

This is just a simple system tool that can help you in a day to day basis, working with SAP.

SAPLAB Version 2.0 is on-line!

webmaster — Wed, 07 Jul 2010 16:43:26 +0000

It gives me great pleasure to announce that today I’m releasing version 2.0 of the SAPLAB.org blog. Since the beginning of this project, roughly and more seriously about 2 years ago, I tried as much as possible to update the blog with useful and practical information around several SAP subjects. While doing this, I always tried to add my own personal flavor and experience to it, without, obviously, compromising any client sensible information.

The result and feedback has been good and now I’ve decided to raise this project to a new level. Besides the new look and feel, which is now more web 2.0 friendly, new functionalities will come and also more posts in the following weeks. Please be aware and keep visiting the blog! Please click here to subscribe the newsletter, which will bring updates to your e-mail.

I’d also like to take this opportunity to thank all returning visitors, as well as new visitors landing in SAPLAB. Please take your time to browse through the blog and don’t forget to leave your comments. It’s what gives life to this project!

Sincerely, kind regards.

Antonio Caldas

TIP: Overide Lack of Authorization on a Transaction Code

webmaster — Tue, 16 Mar 2010 15:55:43 +0000

When you just need to look on a specific transaction and you don’t have permission?
Wait no more, this is a good and quick work-arround:

- Go to transaction SE37, display the function module RS_TRANSACTION_TEST and place a break-point after instruction ( CALL ‘AUTH_CHECK_TCODE’ ID ‘TCODE’ FIELD objectname. ).

- Go to transaction SE93, fill the transaction code that you need to execute and press the test Button (F8).

The debug window will pop-up and you will find yourself on the breakpoint that you placed on the function module RS_TRANSACTION_TEST. Change the system variable SY-SUBRC to ’0′ and press F8. And then you will find yourself in the transaction that you needed.

Simple and Easy!

SAP Sales and Distribution (SD) Transaction Codes

webmaster — Sat, 27 Jun 2009 11:14:13 +0000

Customer:

XD01 – Create Customer (Centrally)
XD02 – Change Customer (Centrally)
XD03 – Display Customer (Centrally)
XD04 – Customer Changes (Centrally)
XD05 – Block customer (centrally)
XD06 – Mark customer for deletion (centr.)
XD07 – Change Customer Account Group
XD99 – Customer master mass maintenance
XDN1 – Maintain Number Ranges (Customer)

Vendor:

XEIP – Number range maintenance: EXPIMP
XK01 – Create vendor (centrally)
XK02 – Change vendor (centrally)
XK03 – Display vendor (centrally)
XK04 – Vendor Changes (Centrally)
XK05 – Block Vendor (Centrally)
XK06 – Mark vendor for deletion (centrally)
XK07 – Change vendor account group

Sales Order:

VA00 – Initial Sales Menu
VA01 – Create Sales Order
VA02 – Change Sales Order
VA03 – Display Sales Order
VA05 – List of Sales Orders
VA07 – Compare Sales – Purchasing (Order)
VA08 – Compare Sales – Purchasing (Org.Dt.)

Inquiry:

VA11 – Create Inquiry
VA12 – Change Inquiry
VA13 – Display Inquiry
VA14L – Sales Documents Blocked for Delivery
VA15 – Inquiries List

Quotation:

VA21 – Create Quotation
VA22 – Change Quotation
VA23 – Display Quotation
VA25 – Quotations List
VA26 – Collective Processing for Quotations

Contract:

VA41 – Create Contract
VA42 – Change Contract
VA42W – Workflow for master contract
VA43 – Display Contract
VA44 – Actual Overhead: Sales Order
VA45 – List of Contracts
VA46 – Coll.Subseq.Processing f.Contracts

Item Proposal:

VA51 – Create Item Proposal
VA52 – Change Item Proposal
VA53 – Display Item Proposal
VA55 – List of Item Proposals
VA88 – Actual Settlement: Sales Orders

Delivery (Outbound):

VL00 – Shipping
VL01 – Create Delivery
VL01N – Create Outbound Dlv. with Order Ref.
VL01NO – Create Outbound Dlv. w/o Order Ref.
VL02 – Change Outbound Delivery
VL02N – Change Outbound Delivery
VL03 – Display Outbound Delivery
VL03N – Display Outbound Delivery
VL04 – Process Delivery Due List
VL06 – Delivery Monitor
VL06C – List Outbound Dlvs for Confirmation
VL06D – Outbound Deliveries for Distribution
VL06F – General delivery list – Outb.deliv.
VL06G – List of Oubound Dlvs for Goods Issue
VL06I – Inbound Delivery Monitor
VL06IC – Confirmation of putaway inb. deliv.
VL06ID – Inbound Deliveries for Distribution
VL06IF – Selection inbound deliveries
VL06IG – Inbound deliveries for goods receipt
VL06IP – Inbound deliveries for putaway
VL06L – Outbound Deliveries to be Loaded
VL06O – Outbound Delivery Monitor
VL06P – List of Outbound Dlvs for Picking
VL06T – List Outbound Dlvs (Trans. Planning)
VL06U – List of Uncheckd Outbound Deliveries
VL08 – Confirmation of Picking Request
VL09 – Cancel Goods Issue for Delivery Note
VL10 – Edit User-specific Delivery List
VL10A – Sales Orders Due for Delivery
VL10B – Purchase Orders Due for Delivery

Customer management:

FD01 – Create Customer (Accounting)
FD02 – Change Customer (Accounting)
FD02CORE – Maintain customer
FD03 – Display Customer (Accounting)
FD04 – Customer Changes (Accounting)
FD05 – Block Customer (Accounting)
FD06 – Mark Customer for Deletion (Acctng)
FD08 – Confirm Customer Individually(Actng)
FD09 – Confirm Customer List (Accounting)
FD10 – Customer Account Balance
FD10N – Customer Balance Display
FD10NA – Customer Bal. Display with Worklist
FD10NET – Customer Balance Display
FD11 – Customer Account Analysis
FD15 – Transfer customer changes: send
FD16 – Transfer customer changes: receive
FD24 – Credit Limit Changes
FD32 – Change Customer Credit Management
FD33 – Display Customer Credit Management
FD37 – Credit Management Mass Change

Pricing:

V/03 – Create Condition Table (SD Price)
V/04 – Change Condition Table (Sales pr.)
V/05 – Display Condition Table: (Sales Pr.)
V/06 – Condition Categories: SD Pricing
V/07 – Maintain Access (Sales Price)
V/08 – Conditions: Procedure for A V
V/09 – Condition Types: Account Determin.
V/10 – Account Determination: Access Seqnc
V/11 – Conditions: Account Determin.Proced.
V/12 – Account Determination: Create Table
V/13 – Account Determination: Change Table
V/14 – Account Determination: Display Table

BOM:

CS00 – BOM Menu
CS01 – Create Material BOM
CS02 – Change Material BOM
CS03 – Display Material BOM
CS05 – Change Material BOM Group
CS06 – Display Material BOM Group
CS07 – Allocate Material BOM to Plant
CS08 – Change Material BOM – Plant Alloc.
CS09 – Display Allocations to Plant
CS11 – Display BOM Level by Level
CS12 – Multilevel BOM
CS13 – Summarized BOM
CS14 – BOM Comparison
CS15 – Single-Level Where-Used List
CS20 – Mass Change: Initial Screen
CS21 – Mass Material Change: Initial Screen
CS22 – Mass Document Change: Initial Screen
CS23 – Mass Class Change: Initial Screen
CS25 – Archiving for BOMs
CS26 – BOM deletion
CS27 – Retrieval of BOMs
CS28 – Archiving for BOMs
CS31 – Create class BOM
CS32 – Change class BOM
CS33 – Display class BOM
CS40 – Create Link to Configurable Material
CS41 – Change Material Config. Allocation
CS42 – Display Material Config. Assignment
CS51 – Create standard BOM
CS52 – Change standard BOM
CS53 – Display standard BOM
CS61 – Create Order BOM
CS62 – Change Order BOM
CS63 – Display Order BOM
CS71 – Create WBS BOM
CS72 – Change WBS BOM
CS73 – Display WBS BOM
CS74 – Create multi-level WBS BOM
CS75 – Change multi-level WBS BOM
CS76 – Display multi-level WBS BOM
CS80 – Change Documents for Material BOM
CS81 – Change Documents for Standard BOM
CS82 – Change documents for sales order BOM
CS83 – Change documents for WBS BOM
CS84 – Change documents for class BOM
CS90 – Material BOM Number Ranges
CS91 – Number Ranges for Standard BOMs
CS92 – Number Ranges for Sales Order BOMs

SAP Production Planning (PP) Transaction Codes

webmaster — Wed, 10 Jun 2009 11:05:31 +0000

Master Data:

MD25 – Create planning calendar
MD26 – Change planning calendar
MD27 – Display planning calendar
MDSA – Display BOM explosion number
MDSP – Edit BOM explosion number
MEQ1 – Maintain quota file
OPPP – Explode BOM by date
MDUS – Display project assignment
MDUP – Process project assignment
MDL1 – Create production lot
MDL2 – Change production lot
MDL3 – Display production lot

Planning:

MD20 – Create planning file entry
MD21 – Display planning file entry
MDAB – Set up planning file entry in background
MDRE – Check planning file entry
MD01 – Total planning online
MDBT – Total planning in background
MD03 – Single-item, single-level planning
MD02 – Single-item, multi-level planning
MD43 – Interactive single-item planning
MD50 – Multi-level, make-to-order planning
MD51 – Multi-level project planning
MF52 – Display planning table
MF50 – Change planning table
MF57 – Planning table by MRP lists
MF51 – Planning table by production list

Evaluations:

MD04 – Stock/requirements list
MD07 – Collective access of stock/requirements lists
MD05 – MRP list
MD06 – Collective access of MRP lists
MDLD – Print MRP list
MD45 – Planning result
MD46 – Collective access of planning result
MD44 – Planning situation for a material
MD47 – Planning situation for a product group
MD48 – Cross-plant planning situation
MD4C – Order report
MD09 – Pegged requirements
CO46 – Order progress

Planned Order:

MD11 – Create planned order
MD12 – Change planned order
MD13 – Individual access of planned order
MD16 – Collective access of planned orders
MD14 – Individual conversion of planned order into purchase requisition
MD15 – Collective conversion of planned orders into purchase requisitions
MDUM – Convert planned order into purchase requisition in background
CO40 – Convert individual planned order into production order
CO41 – Collective conversion of planned orders into production orders
CO48 – Partial conversion of planned order into production order
COR7 – Individual conversion of planned order into process order
COR7_PC – Collective conversion of planned orders into process orders
COR8 – Partial conversion of planned order into process order
MDVP – Collective availability check
MDAC – Execute action for planned order

SAP Plant Maintenance (PM) Transaction Codes

webmaster — Sun, 07 Jun 2009 10:53:07 +0000

General:

IW31 – Create Plant Maintenance Order
IW32 – Change Plant Maintenance Order
IW33 – Display Plant Maintenance Order
IW34 – Create Notification Order
IW51 – Create Service Notification
IW52 – Change Service Notification
IW53 – Display Service Notification
IW54 – Create Service Notification roblem notification
IW55 – Create Service Notification :Activity Request
IW56 – Create Service Notification :Service Request
IW57 – Assign deletion Flag to Completed Service Notifications
IW58 – Change Service Notifications: Selection of Notification
IW59 – Display Service Notifications: Selection of Notification
IA07 – Display General Task List
IA03 – Display Equipment Task List
IA13 – Display Functional Location Task List
IR03 – Display Work Centre
KO88 – Settle Order (Single)
IW32 – Change Work Order
IW31 – Create Work Order
IW33 – Display Work Order
IW38 – Work Order List Editing – Change
IW39 – Work Order List Editing – Display
IW40 – Work Order List Editing – Display Multi Level
ME21 – Create Purchase Order (pre R4.6)
ME21N – Create Purchase Order (R4.6 onwards)
IP41 – Create Single Cycle Plan (R4 onwards)
IE02 – Change Equipment
IE01 – Create Equipment
IE03 – Display Equipment
IE05 – Equipment List Editing – Change
IE08 – Equipment List Editing – Display
IW42 – Overall Completion Confirmation
IW26 – Create Notification
QS42 – Display Catalog
ML81 – Create Service Entry Sheet
MM03 – Display Material
CS03 – Display Material BOM
IW13 – Material Where Used List
IW66 – Change Notification List of Tasks
IW67 – Display Notification List of Tasks
IW22 – Change Notification
IW23 – Display Notification
IH01 – Display Functional Location Structure
MB11 – Goods Movement
MB31 – Goods Receipt
IW8W – Goods Receipt for Refurbishment (R4 onwards)
IP02 – Change Maintenance Plan
IP03 – Display Maintenance Plan
IP10 – Schedule Maintenance Plan
IP30 – Deadline Monitoring
IP11 – Change Maintenance Strategy
IP12 – Display Maintenance Strategy
IP19 – Maintenance Scheduling Overview Graphic
IP24 – Maintenance Scheduling Overview List
IW28 – Notification List Editing – Change
IW29 – Notification List Editing – Display
IW30 – Notification List Editing – Display Multi Level
IW64 – Change Notification List of Activities
IW65 – Display Notification List of Activities
IW68 – Change Notification List of Items
IW69 – Display Notification List of Items
IQ03 – Display Serial Numbers
IW24 – Create Notification
IP42 – Create Strategy Maintenance Plan (from R4 onwards)
IW25 – Create Notification
IL02 – Change Functional Location
IL01 – Create Functional Location
IL03 – Display Functional Location
IL05 – Functional Location List Editing – Change
IL06 – Functional Location List Editing – Display
IW41 – Time Confirmation – Indvidual Entry
IW48 – Time Confirmation – Collective Entry with Selection
IW44 – Time Confirmation – Collective Entry no Selection
IA11 – Create Functional LocationTask Lists
IA12 – Change Functional Location Task List
IL02 – Change Functional Location
IA05 – Create General Task List
IA06 – Change General Task List
IA01 – Create Equpment Task List
IA02 – Change Equipment Task List
IE03 – Display Equipment
IR01 – Create Work Centre
IR02 – Change Work Centre
CA85 – Replace Work Centre
IP13 – Strategy Package Sequence
IP14 – Strategy Package Sequence
IP04 – Create Maintenance Item
IP05 – Change Maintenance Item
IP06 – Display Maintenance Item
IP17 – Maintenance Item List Editing – Change
IP18 – Maintenance Item List Editing – Display
IP02 – Change Maintenance Plan
IP03 – Display Maintenance Plan
IP15 – Maintenance Plan List Editing – Change
IP16 – Maintenance Plan List Editing – Display
IK11 – Create Measurement Documents
IK12 – Change Measurement Documents
IK13 – Display Measurement Documents
IK22 – Measurement Documents List Editing – Create
IK21 – Measurement Documents List Editing – Create
IK22 – Measurement Documents List Editing – Create
IK18 – Measurement Documents List Editing – Change
IK17 – Measurement Documents List Editing – Display
IK41 – Measurement Documents List Editing – Display Archive
IQ01 – Create Serial Numbers
IQ02 – Change Serial numbers
IQ04 – Serial Numbers List Editing – Create
IQ08 – Serial Numbers List Editing – Change
IQ09 – Serial Numbers List Editing – Display
IK01 – Create Measurment Point
IK02 – Change Measurement Point
Ik03 – Display Measurement Point
IK08 – Measurement Point List Editing – Change
Ik07 – Measurement Point List Editing – Display

SAP Material Management (MM) Transaction Codes

webmaster — Sun, 07 Jun 2009 10:46:27 +0000

Most used:

IH09 – Display Material
MM01 – Create Material
MM02 – Change Material
MM03 – Display Material
MM50 – List Extendable Materials
MMBE – Stock Overview
MMI1 – Create Operating Supplies
MMN1 – Create Non-Stock Material
MMS1 – Create Service
MMU1 – Create Non-Valuated Material
ME51N – Create Purchase Requisition
ME52N – Change Purchase Requisition
ME53N – Display Purchase Requisition
ME5A – Purchase Requisitions: List Display
ME5J – Purchase Requisitions for Project
ME5K – Requisitions by Account Assignment
MELB – Purch. Transactions by Tracking No.
ME56 – Assign Source to Purch. Requisition
ME57 – Assign and Process Requisitions
ME58 – Ordering: Assigned Requisitions
ME59 – Automatic Generation of POs
ME54 – Release Purchase Requisition
ME55 – Collective Release of Purchase Reqs.
ME5F – Release Reminder: Purch. Requisition
MB21 – Create Reservation
MB22 – Change Reservation
MB23 – Display Reservation
MB24 – Reservations by Material
MB25 – Reservations by Account Assignment
MB1C – Other Goods Receipts
MB90 – Output Processing for Mat. Documents
MB21 – Create Reservation
MB22 – Change Reservation
MB23 – Display Reservation
MB24 – Reservations by Material
MB25 – Reservations by Account Assignment
MBRL – Return Delivery per Mat. Document
MB1C – Other Goods Receipts
MB90 – Output Processing for Mat. Documents
MB1B – Transfer Posting
MIBC – ABC Analysis for Cycle Counting
MI01 – Create Physical Inventory Document
MI02 – Change Physical Inventory Document
MI03 – Display Physical Inventory Document
MI31 – Batch Input: Create Phys. Inv. Doc.
MI32 – Batch Input: Block Material
MI33 – Batch Input: Freeze Book Inv.Balance
MICN – Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 – Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 – Batch Input: PhInvDoc. Project Stock
MI01 – Create Physical Inventory Document
MI02 – Change Physical Inventory Document
MI03 – Display Physical Inventory Document
MI31 – Batch Input: Create Phys. Inv. Doc.
MI32 – Batch Input: Block Material
MI33 – Batch Input: Freeze Book Inv.Balance
MICN – Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 – Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 – Batch Input: PhInvDoc. Project Stock
MI01 – Create Physical Inventory Document
MI02 – Change Physical Inventory Document
MI03 – Display Physical Inventory Document
MI31 – Batch Input: Create Phys. Inv. Doc.
MI32 – Batch Input: Block Material
MI33 – Batch Input: Freeze Book Inv.Balance
MICN – Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 – Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 – Batch Input: PhInvDoc. Project Stock
MI21 – Print physical inventory document
MI04 – Enter Inventory Count with Document
MI05 – Change Inventory Count
MI06 – Display Inventory Count
MI09 – Enter Inventory Count w/o Document
MI34 – Batch Input: Enter Count
MI35 – Batch Input: Post Zero Stock Balance
MI38 – Batch Input: Count and Differences
MI39 – Batch Input: Document and Count
MI40 – Batch Input: Doc., Count and Diff.
MI08 – Create List of Differences with Doc.
MI10 – Create List of Differences w/o Doc.
MI20 – Print List of Differences
MI11 – Physical Inventory Document Recount
MI07 – Process List of Differences
MI37 – Batch Input: Post Differences
CT01 – Create Characteristic
CT02 – Change Characteristic
CT03 – Display Characteristic
CL01 – Create Class
CL02 – Classes
CL03 – Display Class
CL04 – Delete Class
CL2B – Class Types