SAP R/3 Transaction Codes
Unofficial Certification and Review Guide
Equity Press
SAP R/3 Transaction Codes: Unofficial Certification and Review Guide
ISBN: 978-1-60332-306-2
Smashwords Edition
Edited By: Jamie Fisher
Copyright© 2007 Equity Press and SAP COOKBOOK all rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording or otherwise) without either the prior written permission of the publisher or a license permitting restricted copying in the United States or abroad.
The scanning, uploading and distribution of this book via the internet or via any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions, and do not participate in or encourage piracy of copyrighted materials.
The programs in this book have been included for instructional value only. They have been tested with care but are not guaranteed for any particular purpose.
The publisher does not offer any warranties or representations and does not accept any liabilities with respect to the programs.
Trademarks: All trademarks are the property of their respective owners. Equity Press is not associated with any product or vendor mentioned in this book.
Please visit our website at www.sapcookbook.com
Introduction: Finding the list of SAP Transaction codes
Question 01: Create a movement type
Question 02: Adopt standard settings for message determination
Question 03: Set price control for receipts
Question 04: Accessing Materials Management Configuration Menu
Question 05: Access to MM configuration transactions
Question 06: Important Materials Management Tables
Question 07: Add custom fields to POs and RFQs
Question 08: Dictate Planned Orders conversions
Question 09: Update or create Material Master Records
Question 11: Production Resource/Tool defined as a material
Question 12: Creating a new Material
Question 13: Materials Views perspective
Question 14: Set user defaults for views and organizational levels
Question 15: Requisites for automatic copy
Question 16: Create a document/e-mail notifier
Question 17: Authority settings
Question 18: Define a Release Procedure for PRs and POs
Question 19: Change Characteristic
Question 21: Configure the Release Procedure
Question 22: Sales and Purchasing view
Question 23: Create Vendor Account Groups
Question 24: Material Master Key Fields
Question 25: Main Purchasing Tables
Question 26: Create a material
Question 27: Data points provided by Purchasing for a material
Question 28: Lot Size attributes of a material
Question 30: materials assigned to vendors
Question 31: Information Record Data contents
Question 32: Create the Information Record
Question 33: Initial configuration steps for Purchase Requisitions
Question 34: Setup Stock Transport Order
Question 35: Initial configuration steps for Inventory Management
Complete MM Transaction Codes List
SAP R/3 Transaction codes for HR
Question 01: Configuring a custom feature for a default contract type
Question 02: Info type 0019, Monitoring of Tasks
Question 03: Tracking viewed info types
Question 04: Storing federal tax id with the SSN
Question 10: Display only option
Question 11: Configuring Dynamic Actions
Question 12: Changed data report
Question 13: Validity for infotype records
Question 14: Notes on infotypes
Question 15: Enhancing infotype
Question 16: Create infotype 0041
Question 17: SAP HR Payroll India Module
Question 19: Payroll configuration
Question 20: SAP HR Terminologies
Question 21: Run payroll without BSI interface
Question 22: Annual values in Payroll
Question 24: Manual data entry
Question 26: Retention of employee numbers and payroll history
Question 30: Leave without pay
Question 31: Inter-company postings
Question 32: Down system while in the middle of payroll activities
Question 35: Automatic salary increase
Question 36: Appearance of wage type
Question 38: Overtime calculation
Question 39: Copying standard wage type
Question 40: Additional allowance
Question 41: Wage type and benefits
Question 42: Balance sheet account
Question 43: Pre-noted direct deposit accounts
Question 44: Retroactive accounting
Question 45: Remuneration Statement
Question 50: Shifting of schedules
Question 56: Backdate an initial hire date
Question 58: Service joining date
Question 59: Overlapping schedule
Question 60: Configuring benefit eligibility
Question 61: Configuring a medical opt out
Question 62: Configure by rules of schema
Question 65: Vacation entitlement
Question 67: Configuration steps in MSS
Question 68: Defaulting problem
Question 69: Configuring the MSS
Question 70: Final Confirm field
Question 71: Approving CATS timesheets
SAP R/3 Transaction Codes for FICO
Quick Reference Guide to Basic FICO Transaction Codes
Question 01: CO Enterprise Structure
Question 02: Posting key and Field status group
Question 03: Identify target cost version
Question 04: Parking of document
Question 06: Creating Vendor Invoice
Question 07: Bank Reconciliation Statement
Question 08: Document flow confusion
Question 09: Change reconciliation account of customer master
Question 10: Various postings to GL account
Question 11: Creating new company code
Question 14: Middle of the year Asset data transfer
Question 17: Interest calculation
Question 18: Electronic Bank Statement
Question 19: Convert in update rules
Question 21: Currency conversion
Question 22: Foreign currency valuation
Question 23: Currency conversion dependent on date
Question 24: Currency Conversions
Question 25: Currency exchange rate
Question 26: Foreign Exchange (forex) transactions
Question 28: Currency conversion issues
Question 29: Foreign currency test scripts
Question 30: Automatic outgoing program error
Question 31: GR/IR tolerance for automatic clearing
Question 32: Valuation methods
Question 34: Transport GL Accounts
Question 35: Mass blocking of GL accounts
Question 36: Reconciliation & Alternate Reconciliation Account
Question 38: Alternative Reconciliation account
Question 39: Automated payments
Question 40: Vendor down payment made
Question 41: Advance Payment to Vendors
Question 42: Assigning material and GL to cost center
Question 43: Configure FICO reconciliation
Question 44: Configuration for Special Purpose Ledger
Question 45: Cost elements not created for GL
Question 46: Calculate bank interest
Question 47: Special G/L transaction
Question 48: GL Accounts not be displayed
Question 49: Entries in particular Field in GL
Question 50: Amount transfer from bank to bank
Question 51: Chart of Accounts
Question 52: Transport of chart of accounts
Question 53: Copy GL account from COA
Question 54: Transporting COA, Cost Center & Profit Center Hierarchies
Question 55: Create and assign multiple FS to CC
Question 57: Adding Fields to COPA Data Source
Question 60: COPA does not reconcile between BW and R/3
Question 65: Delete init request in COPA
Question 66: COPA extraction delta failure
Question 67: Data extraction for COPA pulling 0 records
Question 68: Increase/Decrease credit limit
Question 69: A/R - Credit Management for customers
Question 70: Update Customer Credit Management
Question 71: Mass update customer credit limit
Question 72: Customer report with dr. balance only
Question 73: Customer credit management change BO Required
SAP R/3 SD Transaction Codes: SD Fundamentals
Question 01: SAP Sales and Distribution Processing Document Flow
Question 02: Sales Document Type
Question 03: New Division/Sales Area/Sales Office
Question 04: Difference between sales organization and sales area
Question 05: Block Sales Document Type / Delivery / Billing by Customer
Question 06: Wrong/duplicate RE Created
Question 07: Movement type determination and Availability
Question 08: Sales reservation
Question 09: Sales Order Stock
Question 10: Forecasted and Confirmed Sales Orders
Question 11: Backorder Processing
Question 12: Third Party Order Processing
Question 13: Product Group and Sales BOM
Question 14: Defining Company and Assigning Sales Organization
Question 15: Partner Procedures
Question 16: Goods Return from Customer
Question 17: Diagram of SD Customer Master Tables
Question 18: Rebate Agreement and Partner Determination
Question 19: Document Flow in Sales
Question 20: Data flow diagram for shipping and billing
SAP R/3 Netweaver Transaction Codes: Installation, Authorization, and Connection Issues
Question 01: Business Transaction Codes
Question 02: Problems while deploying Java Proxy
Question 03: ‘functiontemplate’ from repository was <null>
Question 04: ExchangeProfile Problem
Question 05: XI Installation Problems
Question 07: FTP Connection Error
Question 08: XI Lost Connection to J2EE
Question 09: JCo Connection Parameters and Migration through Dev/QA/Prod
Question 10: sm58 - Name or Password is Incorrect
Question 12: RWB Error during Message Monitoring
Question 13: Websphere MQ Problem
Question 14: Reassigning Change List to a Different User
Question 16: Unable to Find any Adapter Engines
Question 17: Setting the Username & Password for the Plain HTTP Adapter
Question 18: Outbound File Adapter
Question 19: J2SE Adapter Registration
Question 20: Problem with SOAP adapter
Question 21: RFC Adapter as Sender
Question 22: “No steps” Mapping & Determination in Pipeline (SXMB_MONI)
Question 23: Mapping Flat Structure in Complex Structure
Question 24: RFC Sender Problem (Asynchronous)
Acknowledgements and references for FICO /SD T-codes
Introduction: Finding the list of SAP Transaction codes
Question: Where can I find the list of transaction codes and their usage? I heard that there is some table which contains all the transaction codes with their descriptions. Does anyone know about the Table that consist all the T-Code?
A: Listed here are the various ways you can find the list of transaction codes and their usage:
Use transaction SE11 - ABAP Dictionary:
Fill in the Database table name and click the Display button.
- TSTC table will contain all the T-codes and
- TSTCT table will contain all the T-codes with Texts.
Once you entered the screen, click in Top Menu - Utilities - Table contents - Display
If you want to display all the transaction code (total - 57,048) you have to change the Fields: Maximum number of hits to 99999 (default 500).
Or:
Simply go to transaction SM01, although this T-code is to Lock/Unlock any transaction code, you can also view all the T-code available in the R/3 system from here.
Or:
Go to transaction SE93
There are two ways where you can find the list of transaction codes in SE93:
Method 1:
You must be familiar with the starting characters strings for each of the R/3 application modules.
Assuming you know that most Materials Management transaction codes start with MM.
In the Fields: Transaction code, type in MM* and press the function key F4
The list of transaction code starting with MM will be displayed.
Method 2:
On the Top Menu, click Utilities - Find - Execute and the first 500 transaction will be display.
If want to display all the T-codes, make sure you remembered to change the Fields: Maximum no. of hits right at the bottom of the screen.
Question: I know a particular T Code and can enter and work on it. How do I know what is the menu path for that T Code?
A: Enter Search_SAP_Menu in the command box and when the pop box appears enter, the T-code and it will give the nodes and menu path. This is helpful only in case of SAP Menu not in case of SPRO - i.e. IMG.
Question 01: Create a movement type
How do you create a movement type? When will movement type numbers be odd?
A: When prompted by a dialog box after an activity, you copy a movement type. Select the field “Movement Type” and “Continue”. In the Define Work area, enter the movement type to be copied in “From:” and the name your new movement type in the “To:” field. Now choose “Continue”. Choose the desired movement type you want then choose “Edit > Copy as” and re-type the selected movement type with the new type copy all dependent entries and make sure to begin with a proper prefix (9,X,Z). All control indicators are copied to the new movement type. Review the new movement type changing any necessary controls. Reversal movement types are numbered as the number type plus one. The reversal for movement type 451 (Returns From Customer) is 452. As a last step before saving your settings, add a copy the reversal movement type and enter it in Reversal/follow-on movement types.
Question 02: Adopt standard settings for message determination
How do you adopt standard settings for the Message Determination Facility in MM-PUR?
A: The Message Determination Facility is by default active and message determination schema is supplied for all purchasing documents including POs, PRs, RFQs etc.
All of the desired message types must be maintained. Choose Master data > Messages > Purchasing document > Create or Change from the Purchasing menu. Add the message type and pick the key combination. The key combination decides the condition table where the condition record is stored. Enter all needed items. Next screen, create the individual condition records. Using the menu options Goto > Means of Communication, enter the proper peripheral, or output for each message record. Save.
Question 03: Set price control for receipts
How do you set price control for receipts (goods/invoice) telling the system how to value stocks?
A: Transaction Code OMW1 allows you to set price control to S (Standard Price) or V (Moving Average Price).
Under Standard Price (S), the materials and accounting documents are both valid. The one with the lower value will be posted with a price variance entry.
Question 04: Accessing Materials Management Configuration Menu
How do you access the Materials Management Configuration Menu?
A: Transaction Code OLMS has a host of options that are not accessible through the IMG.
Question 05: Access to MM configuration transactions
How are the various MM configuration Transactions accessed?
A: Transaction Codes OLMD accesses MM-CBP, OLMB accesses MM-IM, OLME accesses MM-PUR, OLML accesses MM-Warehouse Management, OLMS accesses Material Master Data, and OLMW is the proper transaction for valuation and account assignment.
Question 06: Important Materials Management Tables
What are some of the more important Materials Management Tables?
A: EINA contains general data of the (Purchasing) Information Record; EINE includes Purchasing Organization of the same. MAKT is the Materials Description table, MARA-General Materials data, MARC-Plant Data for Materials, MARD-Storage Location Data for Material, MAST-Material to BOM Link, MBEW-Material Valuation, and MKPF-Header Material Document.
Some of the tables that directly pertain to the document types are T156 Movement Type and T023/T024 Groups Material and Purchasing.
Question 07: Add custom fields to POs and RFQs
Can you add custom fields to POs and RFQs?
A: Yes, you can. You can add custom fields to the customer including structures I_EKKODB and I_EKPODB.
Create a project via CMOD for enhancement MM06E005. Follow the documentation for MM06E005, and create the sub-screens for function group XM06 using transaction SE80. Add fields to the appropriate screen. It is recommended that you call the screen fields EKPO_CI-name or EKKO_CI-name. This simplifies transferring data to/from the screen. Put code in EXIT_SAPMM06E_018 to transfer data from sub-screen to structure E_CI_EKPO. Put code in EXIT_SAPMM06E_016 to transfer data from database to sub-screen using structure I_CI_EKPO. In the PBO of the sub-screen, do any processing to make fields display only, or hide them. If you need values from the main screen to make decisions in the sub-screen, define variables in the global data part of the function module, and fill the variables in EXIT_SAPMM06E_016 (PBO of main screen) Make sure everything has been activated like user exists, screens, etc.
Question 08: Dictate Planned Orders conversions
Where can you dictate how Planned Orders are converted into Requisitions in MRP?
A: Look at the Transaction Code OPPR indicator. Assign the proper indicator.
Question 09: Update or create Material Master Records
What SAP program is used to update or create Material Master Records?
A: RMDATIND is used to update Material Master Records and can be used for such assignments as extending all materials to a new plant.
What Views are possible for a material?
A: The material type selected controls the views possible for material.
For a material to be used in the system it needs to be created for each plant. Multiple views of a material are possible but at a minimum, the material needs to have a description and a base unit of measure assigned on the basic data view. Additional department views (i.e. Accounting, Sales, Purchasing, MRP, Warehouse) can be added at a later time by extending the material. As additional plants are added, a material will need to be extended to the plants before it can be used there.
Question 11: Production Resource/Tool defined as a material
When can a Production Resource/Tool be defined as a material?
A: A Production Resource / Tool can be defined as a material if purchasing and inventory functions are to be carried out for that PRT.
The information required to be input is dependent upon which department views are being created. Thus, material master information is typically entered at different times by numerous system users. Note that to add a view, the “Create Material” transaction is used rather than the “Change Material” transaction.
Question 12: Creating a new Material
When creating a new Material, what may prompt some of the possible Material Types?
A: Pressing F4 gives a list of choices. Select the material type for the material you are creating. Examples of these are FHMI for Production, Resources/tools, ROH for Raw Materials, and FERT for Finished Products, etc.
Question 13: Materials Views perspective
How do you determine which views of a material need to be added or to see which plants a material has been extended to?
A: You can use transaction MM50.
To extend a material to a different plant requires selecting the new plant on the organizational level screen. Note that all views of a material are not extended unless they were selected on the initial screen. In addition, each plant may have a different system configuration requiring additional inputs on each of the departmental screens. Material changes made in one plant do not change that material in other plants.
Question 14: Set user defaults for views and organizational levels
How can you set user defaults for views and organizational levels?
A: The user defaults for views can be set under Menus: Defaults > Views. Select those views to be checked on by default when generating a new material. Select ‘View selection only on request’ option when the select view pop-up is to be by-passed.
For organizational levels, Menus: Defaults > organizational levels. Enter those organizational levels to be defaulted when generating a new material. Select ‘Org. levels/profiles only on request’ when the select view pop-up is to be by-passed unless selected.
Question 15: Requisites for automatic copy
What needs to be present in order for Material Type to be automatically copied from one view to another?
A: When creating any view, the Industry Sector and Material type will be automatically copied from an existing view, so long as at least one view exists.
Question 16: Create a document/e-mail notifier
How do you create a document/e-mail notifying your supplier or internal personnel when an invoice plan is settled?
A: The IMG setting is Material Management > Logistics Invoice Verification > Message Determination.
If these settings are not made, the message “Invoicing Plan: No Message Was Found for Partner XXX, Company Code XXX”. If the notifying documents are not required, simply turn off the message by changing the message from “error” to “information” using Material Management > Logistic Invoice Verification > Define Attributes of System Messages.
Question 17: Authority settings
How can one keep users from using standard MM Movement Types?
A: Standard Movement Types should not be deleted from the system. The account assignments, however, may be deleted for a particular Movement Type in table T030 using transaction OBYC.
Another way to achieve the same result is to enter Movement Type in transaction OMJJ. Remove MBXX from allowed transactions.
Question 18: Define a Release Procedure for PRs and POs
How do you define a Release Procedure for PRs and POs?
A: Use Transaction ME54 and ME28 respectively.
Question 19: Change Characteristic
How do you accomplish and do the “Change Characteristic”?
A: Use Transaction Code CT04. Follow these steps: Format (numeric, character, etc.), Unit of Measure, Templates, Required Entry, Intervals as Values , descriptions for texts for characteristics and characteristic values, display options for characteristics on the value assignment screen, Allowed Values, Default Values that are set automatically on the Value Assignment Screen.
How do you create a Class?
A: Class is defined as the group of characteristics, which can be attributed to a product. Use Transaction CL01. Enter the value for the Class name and a small description. Select the group from it. The values on the different tabs are not mandatory, so you can skip the values if you wish or you can go to any extent needed. Save, and the Class is created.
Question 21: Configure the Release Procedure
How do you configure the Release Procedure?
A: Use Transaction OMGQ.
Question 22: Sales and Purchasing view
Will ROH have a sales view? Will FERT have a purchasing view?
A: They shouldn’t because ROH type materials are procured from the outside not sold and FERT type materials are created inside and aren’t procured. In some special cases, we have to sell raw materials (ROH) and buy finished goods (FERT) from outside sources. The views must be extended in these cases using transactions OMS2 and MM50.
Question 23: Create Vendor Account Groups
Where do we create Vendor Account Groups, or screen layout in Vendor Master?
A: Using SPRO, go to Financial Accounting > Accounts Payable/Receivable > Vendor Accounts > Master Records > Preparations for Creating Vendor Master Records > define Account Groups With Screen Layout (Vendors) or define Screen Layout Per Activity.
Question 24: Material Master Key Fields
What are the key fields for the Material Master?
A: The key fields are: Material Groups, External Material Groups, Divisions, Material Status, Labs & Offices, Basic Materials, Storage Conditions, Temperature Conditions, Container Requirements, and Units or Measure Groups.
Question 25: Main Purchasing Tables
What are the main Purchasing Tables?
A: These are the main purchasing tables:
-EKBNPurchase Requisition
-EBKNPurchase Requisition Account Assignment
-EKABRelease Documentation
-EKBEHistory of Purchase Document
Question 26: Create a material
How do you create a material?
A: Use Transaction Code MM01. Name the material, choose an industry sector, choose a material type, create or copy the views, add a basic description, give it’s attributes/values, MRP information, reorder point, accounting valuation, warehouse management information and then save the data.
Question 27: Data points provided by Purchasing for a material
What are some of the data points provided by Purchasing for a material?
A: Some of the key inputs when creating a material are Base Unit of Measure, Purchasing Group, Reminder days, tolerance levels, shipping instructions, GR processing time, JIT schedule indicator, Critical part, etc.
Question 28: Lot Size attributes of a material
What is the Lot Size attributes a material can posse?
A: Lot Sizing dictates the reorder quantity for a material. A material can have a static, periodic, optimum, or fixed lot size.
How do you create a Vendor?
A: Use Transaction Code XK01. Add the Vendor name, Company Code, Purchasing Organization, Account Group, and the Vendor address. Next add the country, Bank Key, Bank Account, Account Holder (an actual name), and then save the data.
Question 30: materials assigned to vendors
How are materials assigned to vendors?
A: Information Record links materials to the vendor, thus facilitating the process of selecting quotations. Use Transaction Code ME11 or Logistics > Material Management > Purchasing and then Master Data > Info Record > Create.
Question 31: Information Record Data contents
What data does the Information Record contain?
A: The Information Record has data on Units of Measure, Vendor price changes after a certain level, what materials have been procured by a specific vendor, price and conditions for relevant Purchase Organization, Tolerance limits for over/under delivery, Vendor evaluation data, planned delivery time, and availability time the vendor can supply the material.
Question 32: Create the Information Record
How do you create the Information Record based on the Material Master record?
A: In the IMG, Master Data > Info Record > Create. Enter Vendor Number, Material Number, Purchasing Organization or Plant Number. Enter the number of the Information Record if external number assignments are used (left blank, the system will assign a number). Enter the General Data for the Vendor, order unit, origin data, and supply option, Customs Tariff Number. Next, enter the Vendor’s planned delivery time (used for scheduling), responsible Purchasing Group, and Standard PO quantity (used in conjunction with price scales for price determination). Check the Control Data. The tolerance data and the responsible purchasing group are taken as default values from the Material Master record. Enter the net price. Now, from the top of the screen, go to > Texts to display the text overview. You can enter the info memo or the PO text. If the PO text is already defined in the Material Master record, it appears as a default value. Save the record.
Question 33: Initial configuration steps for Purchase Requisitions
What are some of the initial configuration steps for Purchase Requisitions?
A: Define Document Types, Processing Time, Release Procedure (with and without classification), Setup Authorization Check for G/L Accounts, Define Number Range.
Question 34: Setup Stock Transport Order
When, in initial configuration, why would you have to Setup Stock Transport Order?
A: If it is required to carry out an inter-plant Stock Transfer through SD, then this configuration is required and must be carried out.
Question 35: Initial configuration steps for Inventory Management
What are some of the initial configuration steps for Inventory Management?
A: Go to Plant Parameters, Define System Message Attributes, Number Assignment (Allocate document type FI to transactions), Goods Issues, Transfer Postings, Define Screen Layout, maintain Copy Rules for Reference Documents, Setup Dynamic Availability Check, Allow Negative Stocks.
Define Default Values for Physical Inventory Document, Batch Input Reports, Tolerances for Physical Inventory Differences, and Inventory Sampling. Cycle Counting should be configured as well.
Complete MM Transaction Codes List
ME01 Maintain Source List
ME03 Display Source List
ME04 Changes to Source List
ME05 Generate Source List
ME06 Analyze Source List
ME07 Reorganize Source List
ME08 Send Source List
ME0M Source List for Material
ME11 Create Purchasing Info Record
ME12 Change Purchasing Info Record
ME13 Display Purchasing Info Record
ME14 Changes to Purchasing Info Record
ME15 Flag Purchase Info Rec. for Deletion
ME16 Purchasing Info Recs. for Deletion
ME17 Archive Info Records
ME18 Send Purchasing Info Record
ME1A Archived Purchasing Info Records
ME1B Re-determine Info Record Price
ME1E Quotation Price History
ME1L Info Records Per Vendor
ME1M Info Records per Material
ME1P Purchase Order Price History
ME1W Info Records Per Material Group
ME1X Buyer's Negotiation Sheet for Vendor
ME1Y Buyer's Negotiation Sheet for Material
ME21 Create Purchase Order
ME21N Create Purchase Order
ME22 Change Purchase Order
ME22N Change Purchase Order
ME23 Display Purchase Order
ME23N Display Purchase Order
ME24 Maintain Purchase Order Supplement
ME25 Create PO with Source Determination
ME26 Display PO Supplement (IR)
ME27 Create Stock Transport Order
ME28 Release Purchase Order
ME29N Release purchase order
ME2A Monitor Confirmations
ME2B POs by Requirement Tracking Number
ME2C Purchase Orders by Material Group
ME2J Purchase Orders for Project
ME2K Purchase Orders by Account Assignment
ME2L Purchase Orders by Vendor
ME2M Purchase Orders by Material
ME2N Purchase Orders by PO Number
ME2O SC Stock Monitoring (Vendor)
ME2S Services per Purchase Order
ME2V Goods Receipt Forecast
ME2W Purchase Orders for Supplying Plant
ME308 Send Contracts with Conditions
ME31 Create Outline Agreement
ME31K Create Contract
ME31L Create Scheduling Agreement
ME32 Change Outline Agreement
ME32K Change Contract
ME32L Change Scheduling Agreement
ME33 Display Outline Agreement
ME33K Display Contract
ME33L Display Scheduling Agreement
ME34 Maintain Outline Agreement Supplement
ME34K Maintain Contract Supplement
ME34L Maintain Scheduled Agreement Supplement
ME35 Release Outline Agreement
ME35K Release Contract
ME35L Release Scheduling Agreement
ME36 Display Agreement Supplement (IR)
ME37 Create Transport Scheduling Agreement
ME38 Maintain Scheduled Agreement Schedule
ME39 Display Scheduled Agreement. Schedule (TEST)
ME3A Transmit Release Documentation Record
ME3B Outline Agreements per Requirement Number
ME3C Outline Agreements by Material Group
ME3J Outline Agreements per Project
ME3K Outline Agreements by Acct. Assignment
ME3L Outline Agreements per Vendor
ME3M Outline Agreements by Material
ME3N Outline Agreements by Agreement Number
ME3P Recalculate Contract Price
ME3R Recalculate Scheduled Agreement Price
ME3S Service List for Contract
ME41 Create Request For Quotation
ME42 Change Request For Quotation
ME43 Display Request For Quotation
ME44 Maintain RFQ Supplement
ME45 Release RFQ
ME47 Create Quotation
ME48 Display Quotation
ME49 Price Comparison List
ME4B RFQs by Requirement Tracking Number
ME4C RFQs by Material Group
ME4L RFQs by Vendor
ME4M RFQs by Material
ME4N RFQs by RFQ Number
ME4S RFQs by Collective Number
ME51 Create Purchase Requisition
ME51N Create Purchase Requisition
ME52 Change Purchase Requisition
ME52N Change Purchase Requisition
ME52NB Buyer Approval: Purchase Requisition
ME53 Display Purchase Requisition
ME53N Display Purchase Requisition
ME54 Release Purchase Requisition
ME54N Release Purchase Requisition
ME55 Collective Release of Purchase Requirements
ME56 Assign Source to Purchase Requisition
ME57 Assign and Process Requisitions
ME58 Ordering: Assigned Requisitions
ME59 Automatic Generation of POs
ME59N Automatic generation of POs
ME5A Purchase Requisitions: List Display
ME5F Release Reminder: Purchase Requisition
ME5J Purchase Requisitions for Project
ME5K Requisitions by Account Assignment
ME5R Archived Purchase Requisitions
ME5W Resubmission of Purchase Requisitions
ME61 Maintain Vendor Evaluation
ME62 Display Vendor Evaluation
ME63 Evaluation of Automatic Sub criteria
ME64 Evaluation Comparison
ME65 Evaluation Lists
ME6A Changes to Vendor Evaluation
ME6B Display Vendor Evaluation for Material
ME6C Vendors without Evaluation
ME6D Vendors Not Evaluated Since...
ME6E Evaluation Records without Weighting
ME6F Print
ME6G Vendor Evaluation in the Background
ME6H Standard Analysis: Vendor Evaluation
ME6Z Transport Vendor Evaluation Tables
ME80 Purchasing Reporting
ME80A Purchasing Reporting: RFQs
ME80AN General Analyses (A)
ME80F Purchasing Reporting: POs
ME80FN General Analyses (F)
ME80R Purchasing Reporting: Outline Agreements
ME80RN General Analyses (L,K)
ME81 Analysis of Order Values
ME81N Analysis of Order Values
ME82 Archived Purchasing Documents
ME84 Generation of Scheduled Agreement Releases
ME84A Individual Display of SA Release
ME85 Renumber Schedule Lines
ME86 Aggregate Schedule Lines
ME87 Aggregate PO History
ME88 Set Agreement Cum. Qty./Reconciliation Date
ME91 Purchasing Documents: Urging/Reminding
ME91A Urge Submission of Quotations
ME91E Scheduled Agreement. Schedules: Urging/Remind
ME91F Purchase Orders: Urging/Reminders
ME92 Monitor Order Acknowledgment
ME92F Monitor Order Acknowledgment
ME92K Monitor Order Acknowledgment
ME92L Monitor Order Acknowledgment
ME97 Archive Purchase Requisitions
ME98 Archive Purchasing Documents
ME99 Messages from Purchase Orders
ME9A Message Output: RFQs
ME9E Message Output: Scheduled Agreement Schedules
ME9F Message Output: Purchase Orders
ME9K Message Output: Contracts
ME9L Message Output: Scheduled Agreements
MEAN Delivery Addresses
MEB0 Reversal of Settlement Runs
MEB1 Create Reb. Arrangs. (Subseq. Sett.)
MEB2 Change Reb. Arrangs. (Subseq. Sett.)
MEB3 Displ. Reb. Arrangs. (Subseq. Sett.)
MEB4 Settlement re Vendor Rebate Arrs.
MEB5 List of Vendor Rebate Arrangements
MEB6 Busn. Vol. Data, Vendor Rebate Arrs.
MEB7 Extend Vendor Rebate Arrangements
MEB8 Det. Statement, Vendor Rebate Arrs.
MEB9 Stat. Statement, Vendor Rebate Arrs.
MEBA Comp. Suppl. BV, Vendor Rebate Arr.
MEBB Check Open Docs., Vendor Reb. Arrs.
MEBC Check Customizing: Subsequent Sett.
MEBE Workflow Sett. re Vendor Reb. Arrs.
MEBF Updating of External Busn. Volumes
MEBG Chg. Curr. (Euro), Vend. Reb. Arrs.
MEBH Generate Work Items (Man. Extension)
MEBI Message, Subs.Settlem. - Settlem.Run
MEBJ Recompile Income, Vendor Reb. Arrs.
MEBK Message., Subs. Settlem.- Arrangment
MEBM List of settlement runs for arrngmts
MEBR Archive Rebate Arrangements
MEBS Stmnt. Sett. Docs., Vend. Reb. Arrs.
MEBT Test Data: External Business Volumes
MEBV Extend Rebate Arrangements (Dialog)
MECCP_ME2K For Requisition Account Assignment
MEDL Price Change: Contract
MEI1 Automatic Purchasing Document Change
MEI2 Automatic Document Change
MEI3 Recompilation of Document Index
MEI4 Compile Worklist for Document Index
MEI5 Delete Worklist for Document Index
MEI6 Delete purchasing document index
MEI7 Change sales prices in purch. orders
MEI8 Recomp. doc. index settlement req.
MEI9 Recomp. doc. index vendor bill. doc.
MEIA New Structure Doc.Ind. Cust. Sett.
MEIS Data Selection: Arrivals
MEK1 Create Conditions (Purchasing)
MEK2 Change Conditions (Purchasing)
MEK3 Display Conditions (Purchasing)
MEK31 Condition Maintenance: Change
MEK32 Condition Maintenance: Change
MEK33 Condition Maintenance: Change
MEK4 Create Conditions (Purchasing)
MEKA Conditions: General Overview
MEKB Conditions by Contract
MEKC Conditions by Info Record
MEKD Conditions for Material Group
MEKE Conditions for Vendor
MEKF Conditions for Material Type
MEKG Conditions for Condition Group
MEKH Market Price
MEKI Conditions for Incoterms
MEKJ Conditions for Invoicing Party
MEKK Conditions for Vendor Sub-Range
MEKL Price Change: Scheduling Agreements
MEKLE Currency Change: Sched. Agreements
MEKP Price Change: Info Records
MEKPE Currency Change: Info Records
MEKR Price Change: Contracts
MEKRE Currency Change: Contracts
MEKX Transport Condition Types Purchasing
MEKY Trnsp. Calc. Schema: Mkt. Pr. (Pur.)
MEKZ Trnsp. Calculation Schemas (Purch.)
MELB Purch. Transactions by Tracking No.
MEMASSIN Mass-Changing of Purch. Info Records
MEMASSPO Mass Change of Purchase Orders
MEMASSRQ Mass-Changing of Purch. Requisitions
MENU_MIGRATION Menu Migration into New Hierarchy
MEPA Order Price Simulation/Price Info
MEPB Price Info/Vendor Negotiations
MEPO Purchase Order
MEQ1 Maintain Quota Arrangement
MEQ3 Display Quota Arrangement
MEQ4 Changes to Quota Arrangement
MEQ6 Analyze Quota Arrangement
MEQ7 Reorganize Quota Arrangement
MEQ8 Monitor Quota Arrangements
MEQB Revise Quota Arrangement
MEQM Quota Arrangement for Material
MER4 Settlement re Customer Rebate Arrs.
MER5 List of Customer Rebate Arrangements
MER6 Busn. Vols., Cust. Reb. Arrangements
MER7 Extension of Cust. Reb. Arrangements
MER8 Det. Statement: Cust. Rebate Arrs.
MER9 Statement: Customer Reb. Arr. Stats.
MERA Comp. Suppl. BV, Cust. Rebate Arrs.
MERB Check re Open Docs. Cust. Reb. Arr.
MERE Workflow: Sett. Cust. Rebate Arrs.
MEREP_EX_REPLIC SAP Mobile: Execute Replicator
MEREP_GROUP SAP Mobile: Mobile Group
MEREP_LOG SAP Mobile: Activity Log
MEREP_MIG SAP Mobile: Migration
MEREP_MON SAP Mobile: Mobile Monitor
MEREP_PD SAP Mobile: Profile Dialog
MEREP_PURGE SAP Mobile: Purge Tool
MEREP_SBUILDER SAP Mobile: SyncBO Builder
MEREP_SCENGEN SAP Mobile: SyncBO Generator
MERF Updating of External Busn. Volumes
MERG Change Curr. (Euro) Cust. Reb. Arrs.
MERH Generate Work Items (Man. Extension)
MERJ Recomp. of Income, Cust. Reb. Arrs.
MERS Stmnt. Sett. Docs. Cust. Reb. Arrs.
MEU0 Assign User to User Group
MEU2 Perform Busn. Volume Comp.: Rebate
MEU3 Display Busn. Volume Comp.: Rebate
MEU4 Display Busn. Volume Comp.: Rebate
MEU5 Display Busn. Volume Comp.: Rebate
MEW0 Procurement Transaction
MEW1 Create Requirement Request
MEW10 Service Entry in Web
MEW2 Status Display: Requirement Requests
MEW3 Collective Release of Purchase Reqs.
MEW5 Collective Release of Purchase Order
MEW6 Assign Purchase Orders WEB
MEW7 Release of Service Entry Sheets
MEW8 Release of Service Entry Sheet
MEW9 mew9
MEWP Web based PO
MEWS Service Entry (Component)
ME_SWP_ALERT Display MRP Alerts (Web)
ME_SWP_CO Display Purchasing Pricing (Web)
ME_SWP_IV Display Settlement Status (Web)
ME_SWP_PDI Display Purchase Document Info (Web)
ME_SWP_PH Display Purchasing History (Web)
ME_SWP_SRI Display Schedule Releases (Web)
ME_WIZARD ME: Registration and Generation
SAP R/3 Transaction codes for HR
Question 01: Configuring a custom feature for a default contract type
I have made a custom feature to default the contract type in info type 0001. Since it is a custom feature, it needs to be linked somewhere to that field to default the value.
If there is some USER EXIT which one should I use?
What is the command to call a feature?
A: There is user exit within enhancement PBAS0001 that may be used to assign default values in all info types. You can also use the zxpadu01 or 02 user exits.
Question 02: Info type 0019, Monitoring of Tasks
We are tracking employees on Sabbatical Leave using IT-0019. When an employee goes on a ‘Sabbatical leave’, we create an action that calls IT-0000, IT-0001, and IT-0019. IT-0019 is used to record the expected return date and set up a reminder. If the employee does not return but is extended, we create another IT-0019 using PA30 with the new expected return date and a new reminder.
When the employee finally returns, we create an action that calls IT-000, IT-0001, and IT-0019 in the background via a dynamic action. The dynamic action should set the monitoring date to 2-task completed.
This is working fine except for those records that have multiple IT-0019 (extensions).
Is there a way to make the dynamic action mark all IT-0019, Subtype 13's as 2-task completed and not just the last one?
My dynamic action looks like the following:
0000 04 66 P P0000-MASSG='SR'
0000 04 67 I MOD,19,13,,/D
0000 04 68 W P0019-BVMRK='2'
A: You can set it to two (2) via a function module. With dynamic actions, you do not loop over all the records you want to modify. You should find one and modify it.
Question 03: Tracking viewed info types
Transaction S_AHR_61016380 can be used to track changes to infotypes as set in the V_T585A table. This is a good tool for tracking updates, deletes and changes.
Is there a means to track viewed infotypes?
A: I don't think there's a standard solution. There is, however, an object history that if switched on, it can tell you the last few personnel numbers looked at. But there’s no certainty that this is configurable by basis to show more details.
Another method is to use a user exit to trigger an update to a customer table storing the user name, time, etc.
You can also try to consult your basis consultant regarding "System Trace". At OS level, system records which the user has executed shows which transaction and when.
Question 04: Storing federal tax id with the SSN
In our business, we treat some contract employees as independent business entities. So, we need to store their federal tax id along with the SSN on an employee record.
Is there any way in SAP that this can be achieved?
A: You have to give the Infotype permissibility to the country code you are using. E.g. If you are using MOLGA IS 40, Indian country code, then you have to go to the node:
SPRO --> Personnel Management --> Personnel Administration --> Customizing Procedures --> Infotypes--> Assign Infotypes to countries
Now, select one line (any line) --> copy --> and accordingly you change it for your requirement.
E.g. Give the IT (0185) and the Sub type (if you have any specific, or just leave it blank), and then give the country code, and select the ‘Push’ button, Permitted --> SAVE
By doing this, you are assigning or giving the permissibility to your country code to use this Info type.
Then, come out of the screen and go to PA30, you will be able to use IT 0185.
One of our customers would like to be able to group an applicant by more than one applicant group. They want to group their applicants by the types of jobs in their company. Many applicants are interested in more than one job type, and would therefore be grouped in two or even more groups. I was wondering whether we might have to create a customer infotype to store this information or maybe use the qualifications catalogue.
Is there a way to group an applicant in more than one applicant group?
Or are there some other groupings we can use to store this information?
A: It seems like you are using the old ‘SAP Recruitment’. But in E-Recruiting, there is a new PD object "Job Family coming out in an upcoming support pack that looks like what you need. Check out the SAP website for updates.
I am trying to create a bespoke infotype using transaction PM01 by keying in the new infotype number, and checking the "Module Pool" radio button. I go on putting in the infotype name and a couple of fields (e.g. endda begdda), save the details, and save it as object directory entry "Z001" (customer specified). When I activated it, I got the following error message:
"Table P9017 not active in ABAP Dictionary".
How can I fix it?
A: You can try the following procedures:
Procedure no: 1
Check if you have you used the transaction PM01. In here, you need to create the structure “PS9nnn”, and then the modules and the screens. You can go for the ‘create all’ button.
After this, you need to maintain the infotype characteristics and the technical characteristics.
Under ‘Infotype Characteristics’, maintain the time constraints, single screen, (2000) and list screen (3000).
Doing all this will activate and prepare the basic framework for your infotype.
The further logic can be done in the ‘Screen flow logic’ of screen 2000.
Procedure No: 2
Here are the steps to create a new Infotype:
1. Go to transaction code PM01;
2. Type the new Infotype (starting with 9);
3. Create the PS structure;
a. Type in the desired fields;
b. Check -> Save -> Generate;
4. Create all;
5. Click IT Characteristics (or F5);
a. Select the new infotype;
b. Click details (or F2) in change mode;
c. Type in the required fields;
d. Save;
6. Click Technical Characteristics (or Shift+F);
a. Select the new infotype;
b. Click details (or F2) in change mode;
c. Type in the required fields;
d. Save;
Is there any easy way to block the SSN (personnel ID number) on IT0002?
We do not want all the users to have access to this information, and we want to grant it on a need-to-know basis.
The security person at my company asked me what is the best approach would be, but I wasn’t really sure.
I know I can use the feature P0002 via T588m to control this, but we want to create this authorization based on the user groups. The structure for P0002 does not carry UGR. We do not want to completely suppress the field for all the users.
Should I create a screen variant and use a user exit?
What is the best way to control this?
A: I don't think there's any such thing as field level authorization in SAP HR. The concept of info types is that they are groupings of related fields, so if you can see one you should be able to see all.
T588M and UGR are useful if it's only the view you're interested in, but this isn't security based.
The only solution I can think of is to copy I0002 to a customer info type, where you have complete control over the contents and can hide SSN. Remove I0002 from the relevant role, and then add the customer 0002 instead.
Where can I find the ''code of conduct'', or related field to input the code of conduct in SAP HR?
A: You can try using Infotype 41 (Date specifications), create date type z1 as a code of business conduct, and input the date when the employee signed.
I used PA30 to create a new personnel number while I use actions infotype to create an organizational assignment. But I can't input position 9999, and 9999 does not appeared in the drop box even if I already defined 9999 as position in IMG OG30 transaction (I maintained entry like object:S, position:9999). When I create time sheet default infotype, the controlling area is empty. By law it should be a default value. Thus, I can't save.
How can I resolve this?
A: You can use PA40 instead. It is intended for hiring. PA30 is for maintenance of infotype. Regarding time sheet, you can use PA61, list entry option.
Question 10: Display only option
In ESS, there is a standard scenario to enable employees to view and change their own employee data. I need to make this a ‘Display only’ option. To change any personal information entry, the employee needs to submit a document proof to HR Department e.g. Marriage Certificate, or passport.
It used to be possible in the ITS version, but I can’t see any other way of doing it in the ESS Business Package Webdynpro stuff on EP. I’m working on mySAP ERP 2004 with EP 6.0 and ESS Business Package.
How can I execute this?
A: We had a similar issue where we found that users had access to change data for certain infotypes which we didn't want them to. We had to get an ABAPer to change the transaction for that infotype access to PA20 rather than PA30.
Question 11: Configuring Dynamic Actions
I am trying to configure Dynamic Actions for Infotype 8 (PY-INDIA). We are calling IT 8 after a User Defined IT via Dynamic Action, and it has been called successfully.
Can we pass Dynamic Variables to Dynamic action to default the values?
For example: WGTYP 3ADP needs to be assigned to any one in between BET01....BET19; How can this be done successfully?
A: You can do a set of plausibility checks (they show as "P") in your dynamic action, so you can tailor the dynamic action based on business rules.
Also check and look at feature LGMST and related configurations for defaulting in wage types into IT8. You can go with the feature over dynamic actions if it's a good fit.
Question 12: Changed data report
I got a request from our HR department to have a report that shows a changed data, and "changed by" for all employees belonging to a specific PA. That should be an ‘output list’ and would enable control if the proper procedures are followed. The report should show only changed data in a specific timeframe.
How can this be done?
A: You could use the Audit Report RPUAUD00.
Alternatively, you could write Ad Hoc or SAP Queries to give you the correct data on the various info types by outputting the "changed on" and "changed by" fields.
Question 13: Validity for infotype records
I hired someone on 08/01/2006. When hiring, I created a new 378 with the start date of 08/01/2006. When I get to the enrollment transaction, it is showing the "validity period" as 10/30/2006.
Where does the system calculate this date from?
In the 2 steps in the IMG, 1 "define admin parameters". I didn’t do any changes, so the validity for infotype records is from the key date. In the step where I define the adjustment reason, the validity of infotype records is set to "adj. reason date". I thought this was correct. We are on ECC 5.0 with HR pack number 19 SAPKE50019.
Is there any other place to look for setting the validity for infotype records?
A: For the benefits, the ‘adjustment reason date’ is the selection period defaulted for the benefit program, not the ‘date of entry’. If you want the ‘date of entry’, you need to flag ‘date of offer’ and tick anytime in the time frame.
Question 14: Notes on infotypes
SAP enables you to make notes on infotypes. You will get a “Word-like” text editor where you can make your notes. My question is, can I report on these notes?
This would be very useful if I can do that.
Is it possible to delete an already entered note?
A: Reading is possible with “Fm hr_read_infty_note”.
The input parameter is the same key as in cluster table PCL1. This is where notes are stored.
Maybe manipulation of this data can be done with “FM hr_infotype_operations”, or else check that function group HRMM for something useful.
Question 15: Enhancing infotype
I created an infotype, and I want it to behave in a way that if the data in a particular field already exists, it will show a warning message. Just like in IT Communication, if the number already exists in an existing employee, it shows a warning message to which the number already exists.
Where can I enhance infotype?
A: It sounds to me that this requirement needs a user exit. There are different types of user exits. You can do a quick search and you will get the information you need.
Another suggestion is if you are working on an infotype you created, you can insert code anywhere you want. Have a look at your code in your module pool.
Take note: MPXXXX00 where XXXX = your infotype.
Question 16: Create infotype 0041
I have created a dynamic action to create infotype 0041 in the background, but whenever PA41 is used to change a start date a duplicate record is created in infotype 0041.
Is there any place where can I look?
A: Try deleting IT0041 from the info group that is set up for your intended action. If you haven't done this yet, it might be worth giving a try.
SAP R/3 HR T-codes
Question 17: SAP HR Payroll India Module
I am using SAP HR Payroll India Module. I am trying to create a new action for an existing employee. This employee belongs to an employee subgroup TM, and has action type ‘Hiring’. When I tried to create a new action type ‘Leaving’, I received an error message 'Assignment to feature IGMOD did not take place'. When I double clicked on this error message, it stated:
Assignment to feature IGMOD did not take place
Message no. P0603
Diagnosis:
You can assign a specific operation (assignment) to each decision option within a feature. You can also define decision option ** whose assignment is effected for all unlisted decision options (this is known as a default value).
Example:
D PERSK
K1 &ABRKS=D1, <- D1 for employee subgroup K1
K2 &ABRKS=D1, <- D1 for employee subgroup K2
K3 &ABRKS=D2, <- D2 for employee subgroup K3
** &ABRKS=D0, <- D0 for all other employee subgroups
If you now create employee subgroup K4 and the default entry ** is missing, the system is unable to find a decision option for payroll area ABKRS.
Procedure:
Define a decision option for K4 or for default value **.
I don’t know how to define a decision option. I am getting the same error message for all employees belonging to the employee subgroup TM.
Is there a way to correct this?
A: It seems that your feature IGMOD is missing some entries. You can use transaction PE03 to view the feature IGMOD, and read the tree to see what's wrong.
Is it possible in QA / Pre-Prod client to delete all the payroll results from the last payroll for a certain payroll area?
A: If by "last payroll" you mean the last payroll period run in the history, then the answer is yes. However, it’s 'onerous'.
You can select for each employee the period you wish to delete. There’s no easy way to select just the last period for an employee. Depending on your payroll size, it could take a while although it wouldn’t take long to write an ABAP to do it.
Question 19: Payroll configuration
How can I configure the payroll system?
What does it need to configure and run a payroll for an employee?
Are there any configuration documents?
A: The basic things which go into payroll processing are the following:
1. Payroll areas, period parameters and payroll calendar.
2. LGMST - feature returns allowance model and links all the allowable wage types to each allowance model. The automatic defaulting of wage types based on pay scale area, pay scale type, pay scale group and pay scale level in Infotype 8.
3. RAP - all allowance models to be linked with custom defined wage types created in the company.
4. Enterprise structure - personal areas, personal sub areas, employee groups, and employee sub group creation.
5. Wage type creations - Personal administration module.
6. Time Management - work schedule creation and linking of work schedule with employee in infotype 7.
The data in Infotype 0, 1, and 7 is mandatory. Allowances can be stored in Infotype 8, 14, 15, 57, etc.
Investments, Tax, Arrears, Benefits, Off-cycle payroll, cumulation, processing, and evaluation classes of wage types, priority of deductions, loans, posting configurations, etc. form part of payroll configurations as well.
You can also refer to SAP.help.com. It is excellent resource for learning the basics.
SAP provides pre-configured data for most of the nodes in Payroll. You can run the payroll without any configurations in the start. All the things above are pre-configured with standard values in SAP, but you need to customize your own payroll based on your requirements.
Question 20: SAP HR Terminologies