Master Data PM Module – SAP

Master data merupakan suatu data yang selalu ada dan digunakan dalam seluruh modul yang ada di sistem SAP. Master data merupakan informasi kunci yang selalu digunakan dalam transaksi, dan sebagai dasar untuk mengidentifikasi dan/atau mencari setiap transaksi yang dicatat dalam sistem.

2017-01-12_15-31-53

Terdapat beberapa perbedaan antara Master Data dan Transactional Data. Master data adalah informasi yang tetap dan jarang berubah selama jangka waktu yang panjang. Sedangkan data transaksi merupakan data yang progressive, yang dapat bertambah atau berubah setiap harinya, serta selalu direlasikan dengan Master Data sebagai dasar transaksinya.

Berikut ini adalah Master Data yang ada dalam modul Plant Maintenance

  1. Functional Location
  2. Equipment
  3. Bill of Material
  4. Work Center
  5. Classification & Characteristic
  6. Measuring Point
  7. Catalog
  8. Task List
  9. Maintenance Plan & Strategy

SAP Factory Calendar dalam PM Module

Ada beberapa cara untuk melihat SAP Factory Calendar yang di setting pada PM Module.

PERTAMA

Plant calendar

Customizing → Enterprise Structure → Definition → Logistics – General → Define, copy, delete, check plant → Define Plant

Double klik pada plant, lalu lihat ‘Factory calendar’ dari Plant


KEDUA

Work center calendar

Transaction IR03 → ‘Capacities’ tab → ‘Capacity’ button

Lihat ‘Factory calendar ID’ dari work center


KETIGA

Maintenance plan SAP Calendar

Transaction IP03 → ‘Maintenance plan scheduling parameter’ tab

Lihat ‘Factory calendar’ dari maintenance plan

Jenis Pesan yang akan Muncul dalam Transaksi SAP

Dalam SAP, ada beberapa jenis pesan yang akan muncul dalam transaksi SAP (biasanya berada di status bar), dimulai dengan :

I           Information – sekadar pemberitahuan tentang status anda.

            Contoh : “Your document has been saved”

W         Warning – anda dapat mengabaikannya dengan menekan tombol enter

            Contoh : “Please check your input”

E          Error – anda tidak dapat melanjutkan sampai masalah tersebut terselesaikan.

            Contoh : “Please enter company code”

A          Abort – adanya kesalahan pada program yang tidak dapat anda selesaikan,

             hubungi team SAP.

Notes :   Jika menemui field bertanda field wajib.jpg  , artinya field tersebut harus diisi (Required field), agar dapat masuk ke langkah / proses berikutnya. Dan untuk field-field yang tidak bertanda field wajib  , artinya field tersebut boleh tidak diisi (Optional field), dan pengguna dapat langsung melanjutkan ke langkah / proses berikutnya.

Cara Menampilkan History Components (Material) / Operations yang Sudah di Hapus dari Order

Jika kita ingin menampilkan history dari components (material) / operations yang sudah di hapus dari sebuah order, maka berikut adalah langkah yang dapat dilakukan :

PERTAMA

Sebagai contoh untuk menampilkan history Components, misalkan pada saat awal membuat Order saya input 2 material, yaitu Kabel NYY = 40 X 70 MM , dan PIN 8747425 lalu kita Release kemudian Save.

21-05-2017 19-52-32.jpg

KEDUA

Dalam keadaan system status REL / Release, namun ternyata saya ingin mengganti Kabel NYY = 40 X 70 MM dengan Bearing SKF 6304 C3, sehingga saya menghapus Kabel NYY = 40 X 70 MM lalu menambahkan Bearing SKF 6304 C3

21-05-2017 20-57-25

KETIGA

Maka jika kita ingin memunculkan history material apa saja yang pernah di input lalu di hapus, maka Klik Edit → Display Deletions → On

21-05-2017 19-58-39.jpg

Sehingga tampilan pada Tab Components akan menampilkan seluruh material yang sudah di hapus maupun yang existing / yang sedang di pakai. Jika berwarna abu-abu dan tidak bisa di edit, maka material tsb adalah material yang sudah di hapus dari Order dan tidak digunakan lagi.

21-05-2017 19-52-47.jpg

CATATAN :

History ini berlaku untuk menampilkan operations maupun components.

History material ini hanya bisa ditampilkan jika Order sudah di RELEASE atau dengan system status REL.

Jika masih dalam keadaan system status CREATED, maka history dari material tidak bisa di tampilkan.

Jadi misalkan, pada saat order dengan system status CRTD, kita input material A,B,C. lalu kita hapus material C, sehingga tinggal tersisa material A dan B lalu baru kita Release dan Save. Jika kita buka kembali ordernya, maka tidak ada history nya bahwa kita pernah input material C pada order tersebut.

Lain halnya jika kita input material D dan E, lalu kita menghapus material A dan B pada order yang sudah di release tadi, maka jika kita check pada display deletions, maka akan tampil material A, B, D dan E pada order, namun tampilan material A dan B akan berwarna abu-abu dan tidak bisa di edit, karena material A dan B dihapus ketika order berstatus REL / Release.

Type of Transaction

The following list shows the individual transactions with examples of how they are used. The transaction/event key is specified in brackets.

  • Agency business: income (AG1)
    This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
  • Agency business: turnover (AG2)
    This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
  • Agency business: expense (AG3)
    This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
  • Expense/revenue from consumption of consignment material (AKO)
    This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
  • Expenditure/income from transfer posting (AUM)
    This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
  • Provisions for subsequent (end-of-period rebate) settlement (BO1)
    If you use the “subsequent settlement” function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
  • Income from subsequent settlement (BO2)
    The rebate income generated in the course of “subsequent settlement” (end-of-period rebate settlement) is posted via this transaction.
  • Income from subsequent settlement after actual settlement (BO3)
    If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the “subsequent settlement” facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
  • Supplementary entry for stock (BSD)
    This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
  • Change in stock (BSV)
    Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
  • Stock posting (BSX)
    This transaction is used for all postings to stock accounts. Such postings are effected, for example:
    • In inventory management in the case of goods receipts to own stock and goods issues from own stock
    • In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
    • In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
    Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
  • Revaluation of other consumption (COC)

This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.

Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.

The header account is determined using the transaction/event key COC.

  • Del credere (DEL)
    Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
  • Small differences, Materials Management (DIF)
    This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
  • Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)

These transactions are used only if Purchase Account Management is active in the company code.

  • Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
    These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
    You can also enter your own transactions for delivery costs in condition types.
  • External service (FRL)
    The transaction is used for goods and invoice receipts in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
  • External service, delivery costs (FRN)
    This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
  • Offsetting entry for stock posting (GBB)
    Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
      • AUA: for order settlement
      • AUF: for goods receipts for orders (without account assignment) and for order settlement if AUA is not maintained
      • AUI: Subsequent adjustment of actual price from cost center directly to material (with account assignment)
      • BSA: for initial entry of stock balances
      • INV: for expenditure/income from inventory differences
      • VAX: for goods issues for sales orders without account assignment object (the account is not a cost element)
      • VAY: for goods issues for sales orders with account assignment object (account is a cost element)
      • VBO: for consumption from stock of material provided to vendor
      • VBR: for internal goods issues (for example, for cost center)
      • VKA: for sales order account assignment (for example, for individual purchase order)
      • VKP: for project account assignment (for example, for individual PO)
      • VNG: for scrapping/destruction
      • VQP: for sample withdrawals without account assignment
      • VQY: for sample withdrawals with account assignment
      • ZOB: for goods receipts without purchase orders (mvt type 501)
      • ZOF: for goods receipts without production orders (mvt types 521 and 531)
  • Purchase order with account assignment (KBS)
    You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
  • Exchange Rate Differences Materials Management(AVR) (KDG)
    When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
  • Exchange rate differences in the case of open items (KDM)
    Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
  • Differences due to exchange rate rounding, Materials Management (KDR)
    An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
  • Exchange Rate Differences from Lower Levels (KDV)
    In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
  • Consignment liabilities (KON)
    Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
  • Offsetting entry for price differences in cost object hierarchies (KTR)
    The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
  • Accruals and deferrals account (material ledger) (LKW)
    If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
    If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
  • Price Difference from Exploded WIP (Lar.) (PRA)
    If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
  • Differences (AVR Price) (PRC)
    In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
  • Price differences (PRD)
    Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
    Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
  • Price Differences (Material Ledger, AVR) (PRG)
    When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
  • Price differences in cost object hierarchies (PRK)
    In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
  • Price Difference from Exploded WIP (Mat.) (PRM)
    If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
  • Price differences, product cost collector (PRP)
    During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
    This transaction is currently used in the following instances only:
    – Production cost collector in Release 4.0
    – Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
  • Offsetting entry: price differences, product cost collector (PRQ)
    The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
    This transaction is currently used in the following instances only:
    – Production cost collector in Release 4.0
    – Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
  • Price Differences from Lower Levels (PRV)
    In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
  • Price differences for material ledger (PRY)
    In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
  • Expense and revenue from revaluation (retroactive pricing, RAP)
    This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
    At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the “Expense from Revaluation” or “Revenue from Revaluation” account. The offsetting (contra) entry is made to the relevant vendor account.
  • Invoice reductions in Logistics Invoice Verification (RKA)
    This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
    If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
  • Provision for delivery costs (RUE)
    Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
  • Taxes in case of transfer posting GI/GR (TXO)
    This transaction/event key is only relevant to Brazil (nota fiscal).
  • Revenue/expense from revaluation (UMB)
    This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
  • Expenditure/income from revaluation (UMD)
    This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
  • Unplanned delivery costs (UPF)
    Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
  • Input tax, Purchasing (VST)
    Transaction/event key for tax account determination within the “subsequent settlement” facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
  • Inflation posting (WGB)
    Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
  • Goods issue, revaluation (inflation) (WGI)
    This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
  • Goods receipt, revaluation (inflation) (WGR)
    This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
  • WIP from Price Differences (Internal Activity) (WPA)
    When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
  • WIP from Price Differences (Material) (WPM)
    When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
  • GR/IR clearing (WRX)
    Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders.
  • GR/IR clearing for material ledger (WRY)
    This transaction/event key is not used from Release 4.0 onwards.
    Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
    Customers who used the transaction WRY prior to Release 4.0 must make a transfer posting from the WRY account to the WRX account in order to ensure that the final balance on the WRY account is zero.

Sources : SAP Library

PM Module – Exit Name

Exit Name Description
QQMA0001 QM/PM/SM: User Subscreen for Notification Header
QQMA0002 QM: Authorization Check for Entry into Notif. Transaction
QQMA0003 QM: “User data” Function in “Goto” Menu
QQMA0004 QM: “User data” Function in “Goto   > Item” Menu
QQMA0005 QM: Check Validity of Status Change
QQMA0006 QM: Automatic Task Determination for Quality Notifications
QQMA0007 QM: Default Values when Creating a Notification
QQMA0008 QM/PM/SM: User Subscreen for Additional Data on Notif. Item
QQMA0009 QM: Predefine QM Order Parameters
QQMA0010 QM/PM/SM: User Subscreen for Additional Data on Cause
QQMA0011 QM/PM/SM: User Subscreen for Additional Data on Task
QQMA0012 QM/PM/SM: User Subscreen for Additional Data on Activity
QQMA0013 QM: Default Values when Creating a Task
QQMA0014 QM/PM/SM: Checks before saving a notification
QQMA0015 QM/PM/SM: User-Exit before Call-Up of F4 Help on Catalogs
QQMA0016 QM/PM/SM: “User data” Function “Goto”   > “Task” Menu
QQMA0017 QM/PM/SM: “User data” Function “Goto”   > “Activity” Menu
QQMA0018 QM/PM/SM: Deadline setting based on entered priority
QQMA0019 QM/PM/SM: Default Partner when Creating a Notification
QQMA0020 QM: Determining BOM Usage at BOM explosion
QQMA0021 QM/PM/SM: Function “User data” in “Goto” menu
QQMA0022 QM/PM/SM: “User data” function in “Goto -> Causes” menu
QQMA0023 QM/PM/SM: “User data” function in “Goto -> Item” menu
QQMA0024 QM/PM/SM Deactivate function codes in CUA menu
QQMA0025 PM/SM: Default values when adding a notification
QQMA0026 PM/SM: Auth. check when accessing notification transaction
QQMA0027 PM/SM: Default values when adding a task
QQMA0028 QM: Create notif. from confirmation of production order
QQMA0029 QM/PM/SM: Change Notification Type
QQMA0030 Check validity of status change
Exit Name Description
COZF0001 Change purchase req. for externally processed operation
COZF0002 Change purchase req. for externally procured component
Exit Name Description
IAIH0001 Customer-Enhancements for Tasklists
IAOM0001 Change Characteristics of a Controlling Object
IB020001 Filter components
IBIP IBIP: Trans. IBIP Data Transfer
IBPP0001 Filter IBase Components When Generating From PP Data
ICRP0201 Search Help CS_ORG_02: Authorization Check
ICRP0202 Search Help CS_ORG_02: Internally-Programmed Selection
ICRP0203 Search Help CS_ORG_02: Propose Task
ICSV0001 Display of geographic location data
ICSV0002 Automatic task determination for service notifications
ICSV0003 Partner selection
ICSV0004 Check PM object and display object information
ICSV0005 Determining reason for rejection – resource-related billing
ICSV0007 Serial Number Partner Transfer on Goods Issue and Returns
ICSV0008 Validation of additional partner types
IDCP0001 Customer Data for Printing Prenumbered Invoices
IDCP0002 Customer Data for Printing Prenumbered Delivery Notes
IEQM0001 Add. checks for equip. installation at functional locations
IEQM0002 Additional checks for definition of equipment hierarchies
IEQM0003 Additional checks before equipment update
IEQM0004 Object is allowed for contract partner (Order->MaintCont.)
IEQM0005 Object allowed for SD contract (MaintContract->MaintCont.)
IEQM0006 Object allowed for SD contract (Maintain maintenance cont.)
IEQM0007 Check/change manufacturer field in equipment master
IHCL0001 Create equipment using material template: Classes/chars
ILOM0001 Additional checks before saving a functional location
ILOM0002 User exit when checking structure of location numbers
IMRC0001 MeasPoint/MeasDoc: Exit before update (after COMMIT WORK)
IMRC0002 MeasPoint: Menu exit for customer-specific function
IMRC0003 MeasDoc: Menu exit for customer-specific function
IMRC0004 Measure.doc.:Exit according to stndrd checks for new mes. Doc
IMRC0005 Measure point: Exit in AUTHORITY_CHECK_IMPT
IMSMCOMM MSM communication enhancement
INTERFAC Interface for data transfer
IPRM0002 Determine planned date info for maintenance plan
IPRM0003 User field: Maintenance plan
IPRM0004 Maintenance plan / item: Customer check for time “SAVE”
IPRM0005 Determine Offset for Performance-Based Strategy Plans
IQSM0001 Automatic serial number assignment
IQSM0002 Check when copying object list
IQSM0003 Serial numbers, user exit for additional data
IQSM0004 Serial numbers, user exit after exiting the serial screen
IQSM0005 Serial numbers, user exit in the update
IQSM0007 Serial numbers, user exit for goods movements
IQSM0008 Serial number character string check
IREV0001 Revision: Additional Fields
ISRE0001 Determine bank procedure account no.
ISRE0002 IPD reporting data retrieval
ISTDUNN1 IS-T-CA: Fill cust. rec. layout fields: phone no. disconnect
ISTDUNNI IS-T/CA: Send phone number (dis)connect file
ISTEBS01 IS-T: Transfer of Billing Docs from Ext. Sys. (using IDocs)
ISTEBS04 Providing Enhancement to IDoc IST_EBS_POI_OUT
ISTPAYME IS-T/CA: Fill reconnect file
ITOB0001 PM: Customer include subscreen for techn. obj. master data
ITOB0002 ITOB: Field changes to copy model
ITOB0003 PM: Customer Include subscreen for fleet object data
ITOB0004 PM: Customer Exit fleet identification data: Checks
IWMI0001 User exits for SM/PM IDOCs
IWO10001 Create a PM sub-order
IWO10002 PM maintenance order: Customer check for order release
IWO10004 Maintenance order: Customer check for order completion
IWO10005 Maintenance order: Cust.-specif. determination of profit ctr
IWO10006 Maint. order: Fcode exclusion through cust. enhancement
IWO10007 Maint.order: Customer enhancement – permits in the order
IWO10008 Cust. enhancement: Determination of tax jurisdiction code
IWO10009 PM Order: Customer Check for ‘Save’ Event
IWO10010 Maint. order: Cust. enhancement for determining WBS element
IWO10011 Maint. order: Customer enhancement for component selection
IWO10012 Maintenance order: Priority handling on central header
IWO10015 Maintenance order: F4 Help for user fields on operation
IWO10016 PM Order: Cust. enhancement to check operation user fields
IWO10017 Determine external order number by customer logic
IWO10018 Maintenance order: User fields on order header
IWO10020 Maintenance order: Automatically include task list
IWO10021 Automatic task list transfer when creating order from notif.
IWO10022 Determine calendar from user exit
IWO10023 Service order: Change header data for advance shipment doc.
IWO10024 Service order: Changes to items for advance shipment
IWO10025 PM/SM order: Finding responsible cost center
IWO10026 User check on setting status ‘Do not perform’
IWO10027 User exit: Generate user-defined settlement rule
IWO10029 Inclusion of bill of material in PM/SM order
IWO10030 Preset Fields for Event Object
IWO10031 Hide personnel number in PM/SM order
IWO20001 PM order: User exit to pass routing to order
IWOC0001 Create PM/SM notification: Determine reference object
IWOC0002 PM/SM notification: Check whether status change is allowed
IWOC0003 PM/SM authorization check of ref. object and planner group
IWOC0004 Change single-level list editing PM/QM/SM ALV settings

 

PM Functional Module

Function Module Description Object
BADI_EQMT_MODIFY You can update selected fields at database level. Very useful for mass resetting of fields Technical objects
BG00_WARRANTY_LINK_UPDATE Updates warranty info for object e.g. equipment master (direct database update) Technical objects
CO_BO_AFVGBT_GET Orders
CO_IH* CO reports Orders
CP_EX_PLAN_READ Get task list data Task lists
CRS_EQUI_COL_KEYS_AND_DATA Technical objects
CRS_EQUIPMENT_COLLECT_DATA Technical objects
CRS_EQUIPMENT_COLLECT_KEYS Technical objects
CRS_EQUIPMENT_EXTRACT Technical objects
CRS_EQUIPMENT_SEND_TO_SERVER Technical objects
CRS_EQUIPMENT_UPLOAD_PROXY Technical objects
CRS_MAP_SM_NOTIF_TO_BAPIMTCS Notifications
CRS_NOTIF_COL_KEYS_AND_DATA Notifications
CRS_NOTIF_COLLECT_DATA Notifications
CRS_NOTIF_COLLECT_KEYS Notifications
CRS_NOTIF_EXPORT_SEND_TOGETHER Notifications
CRS_NOTIF_EXTRACT Notifications
CRS_NOTIF_GET_R3KEY Notifications
CRS_NOTIF_KEY_CONVERT Notifications
CRS_NOTIF_MAP_EXT_STRUCTURE Notifications
CRS_NOTIF_MAP_ILOA Notifications
CRS_NOTIF_SEND_TO_SERVER Notifications
CRS_NOTIF_UPLOAD_CHANGE_PROXY Notifications
CRS_NOTIF_UPLOAD_PROXY Notifications
EQUIPMENT_COLLECT_DATA Technical objects
EQUIPMENT_MODIFY Used to update equipment. Its called from BADI_EQMT_MODIFY but has all of V_EQUI available Technical objects
IBAPI_ALM_* Great FModules for order data Orders
K_ACTIVITY_PRICE_READ Get labour rate by CC/AT (populate GJAHR,KOKRS,KOSTL,LSTAR,PERIO,PERKZ=X,VERSN) Orders
K_KKB_KKBCS_ORDER_REPORT CO reports Orders
K_KKB_OR_REPORT_CALL CO reports Orders
MAP_EQUIPMENT_TO_BAPIMTCS Technical objects
MAP2E_EQKT_TO_BAPI_EQKT1 Technical objects
MAP2E_EQST_TO_BAPI_EQST1 Technical objects
MAP2E_EQUI_INTO_BAPI_STRUCTUR Technical objects
MAP2E_EQUI_TO_BAPI_EQUI1 Technical objects
MAP2E_EQUZ_TO_BAPI_EQUZ1 Technical objects
MAP2E_IHPAVB_TO_BAPI_IHPA Technical objects
MAP2E_ILOA_TO_BAPI_ILOA1 Technical objects
MAP2E_ITXTL_TO_BAPISTXTXL
MAP2E_JEST_TO_BAPISMJEST
MAP2E_JSTO_TO_BAPISMJSTO
MAP2E_STXH_TO_BAPISTXTXH
MAP2E_VIQMEL_TO_BAPIVIQMEL
MAP2E_WQMFE_TO_BAPIQMFE1
MAP2E_WQMMA_TO_BAPIQMMA1
MAP2E_WQMSM_TO_BAPIQMSM1
MAP2E_WQMUR_TO_BAPIQMUR1
NOTIF_COLLECT_DATA
PM_OBJECT_INFO Object information for Equipment, FLocs, Notifications and Service Orders Technical objects
READ_TEXT Reads document text from database General
STATUS_CHANGE_EXTERN Sets user-status after commit. Can be used with user-exits such as QQMA0014 or IWO10009 (at save) Status
STATUS_CHECK_NEW_OLD Status
STATUS_READ Status
STATUS_TEXT_EDIT Search for object status Status
TH_POPUP Send a message to a logged-on user General
VC_I_GET_CONFIGURATION Get VC data. Also try TCode CUTABLEINFO Classification
STATUS_MAINTAIN Displays the standard status screen Status
STATUS_CHECK_NEW_OLD Status
STATUS_READ Status
CO_BO_AFVGBT_GET Orders


sources : https://wiki.scn.sap.com/wiki/display/ERPLO/Some+Useful+PM+Functional+Modules

 

PM Tables

Configuration

Tables Description
CSKS Cost Center Master Data
CSSL Cost Center / Activity Type Assignment
T001W Plant
T006 Unit of Measure
T024I Maintenance Planner Groups
T352B Catalog Profile
T357 Plant Section
T370C ABC Indicator
T370F Functional Location Category
T370S Functional Location Structure Indicator
T399I Planning Plant
T430 Operation/Activity Control Key
T499S Location Codes
TC21 Standard Value Key
TC23 Work Center Usage
TC24 Work Center Person Responsible
TC25 Work Center Capacity Other Formula
TC26 Work Center Capacity Category
TC27 Work Center Capacity Planner Gorup
TC30 Work Center Category
TC38A Work Center Shift Sequence
TGSB Business Area

Classification

Tables Description
INOB Link between internal number and object
KSSK Allocation Table: Object to Class
AUSP Actual Characteristic Values
KLAH Class Header Data
KSML Characteristics of a Class
CAWN Possible Characteristic Values
SWOR Class Description (keywords)
CABN Characteristic
CAWNT Characteristic Description

KLAH : Class Header

Key Fields Description
CLINT Int Class #
CLASS Class Name
KLART Class Type

SWOR : Class Description:  Keyworks

Key Fields Description
CLINT Int Class #
CLASS Class Name


CABN : Characteristics

Key Fields Description
ATINN Int Char #
ADZHL Int Count for Archive
ATNAM Char Description
ATFOR Data Type of Characteristic
ANZST Number of Characters
ANZDZ Number of Decimal Places
ATKLA Characteristic Group


KSML:  Characteristics of a Class

Key Fields Description
CLINT Int Class #
POSNR Item number
ADZHL Int Count for Archive
IMERK Int Char #


KSSK:  Object Allocation to a Class

Key Fields Description
OBJEK Object
MAFID Indicator: object/class
KLART Class type
CLINT Int Class #
ADZHL Int Count for Archive


CAWNT:  Characteristic Value

Key Fields Description
ATINN Int Char #
ATZHL Int Counter
SPRAS Language key
ADZHL Int Count for Archive
ATWTB Char Value Description

CAWN:  Possible Characteristic Values

Key Fields Description
ATINN Int Char #
ATZHL Int Counter
ADZHL Int Count for Archive
ATWRT Char Value


AUSP:  Actual Object Characteristic Values

Key Fields Description
OBJEK Object
ATINN Int Char #
ATZHL Char Val Counter
MAFID Indicator: object/class
KLART Class type
ADZHL Int Count for Archive
ATWRT Char Value


INOB:  Link Between internal number and object

Key Fields Description
CUOBJ Object
KLART Class type
OBTAB Dbase table name
OBJEK Key of classified object
ROBTAB Dbase table name
ROBJEK Key of config object
CLINT Int Class #


Work Center

Tables Description
CRHD Work Center Header
CRCO Assignment of Work Center to Cost Center
CRTX Work Center Descriptions


CRHD:  Work Center Header

Key Fields Description
OBJTY Object type
OBJID Object ID (Key)
ARBPL Work Center
WERKS Plant
VERWE Work Center Category


CRCO:  Assignment of Work Center to Cost Center

Key Fields Description
OBJID Object ID (Key)
KTEXT Short Description

CRTX:  Work Center Descriptions

Key Fields Description
OBJID Object ID (Key)
KOSTL Cost Center
KOKRS Controlling Area
LSTAR Activity Type


Functional Location

Tables Description
IFLOT Functional Location Table
IFLOTX Functional Location Short Texts
ILOA PM Object Location and Account Assignment


IFLOT:  Functional Location Table

Key Fields Description
TPLNR Functional Location
FLTYP Functional Location Category
TPLMA Superior Functional Location
INGRP Planner Group
RBNR Catalog Profile
ILOAN Location and Account Assignment Key


IFLOT:  Functional Location Short Texts

Key Fields Description
TPLNR Functional Location
PLTXT Description of Functional Location


ILOA:  PM Object Location and Account Assignment

Key Fields Description
TPLNR Functional Location
EQFNR Sort Field
SWERK Maintenance Plant
STORT Location
BEBER Plant Section
GSBER Business Area
KOKRS Controlling Area
KOSTL Cost Center
BUKRS Company Code


Equipment

Tables Description
EQUI Equipment Master Data
EQUZ Equipment Time Segment
EQKT Equipment Short Texts

EQUI:  Equipment Master Data

Key Fields Description
EQUNR Equipment Number
EQTYP Equipment Category
LVORM Deletion Flag
INVRN Inventory Number
HERST Manufacture
GERNR Serial
OBJNR Object Number
WERK Plant


EQUZ:  Equipment Time Segment

Key Fields Description
EQUNR Equipment Number
DATBI Vaid to date (99991231 for latest)
IWERK Planning Plant
HEQUI Superior Equipment
HEQNR Equipment Position at Install Location
INGRP Planner Group
TIDNR Technical ID
RBNR Catalog Profile


EQKT:  Equipment Short Texts

Key Fields Description
EQUNR Equipment Number
EQKTX Short Description


Equipment BOM

Tables Description
EQST Equipment to BOM Link
STKO BOM Header
STPO BOM Details


EQST:  Equipment to BOM Link

Key Fields Description
EQUNR Equipment Number
WERKS Plant
STLNR Equip to Detail Link


STPO:  BOM Details

Key Fields Description
STLNR Equip to Detail Link
STLTY Detail Type “E” for Equip BOMs
INDRK Component
POSTP  Item Category
POSNR Item Number
POSTX1 ItemText
MENGE Component Quantity

Equipment Task List

Tables Description
EAPL (Equipment Only) Allocation of Task List to Equipment
PLKO Task List – Header
PLAS Task List – Selection of Operations / Activities
PLPO Task List – Operation / Activity


EAPL:  Allocation of Task List to Equipment

Key Fields Description
EQUNR Equipment number
PLNTY Task list type
PLNNR Group key
PLNAL Group Counter
LOEKZ Deletion Indicator
SWERK Maintenance Plant
IWERK Planning Plant


PLKO:  Task List – Header

Key Fields Description
PLNTY Task list type
PLNNR Group key
PLNAL Group Counter
VERWE Task List Usage
WERKS Plant
STATU Status
IWERK Planning Plant
ARBID Work Center ID
KTEXT Short Description


PLPO:  Task List – Operation / Activity

Key Fields Description
PLNTY Task List Type
PLNNR Key for Task List Group
VORNR Operation Number
STEUS Control Key
WERKS Plant
LTXA1 Short Text
LAR01 Activity Type


Functional Location BOM

Tables Description
TPST Functional Location – BOM Link
STPO BOM Details


TPST:  Functional Location to BOM Link

Key Fields Description
TPLNR Functional Location
WERKS Plant
STLNR Functional Location to Detail Link

STPO:  BOM Details

Key Fields Description
STLNR Equip to Detail Link
STLTY Detail Type “E” for Equip BOMs
INDRK Component
POSTP  Item Category
POSNR Item Number
POSTX1 ItemText
MENGE Component Quantity
Key Fields Description
TPST.TPLNR Equipment Number
TPST.WERKS Plant
TPST.STLAN BOM Usage
STPO.INDRK Component
STPO.POSTP  Item Category
STPO.POSNR Item Number
STPO.MENGE Component Quantity

Material BOM

Tables Description
MAST Material to BOM Link
STPO BOM Details

MAST:  BOM Header

Key Fields Description
MATNR Material Number
WERKS Plant
STLAN BOM Usage (“4” for PM)
STLNR Bill of material

STPO:  BOM Details

Key Fields Description
STLNR BOM Header – BOM Detail Link
STLTY Detail Type “?” for Material BOMs
INDRK Component
POSTP  Item Category
POSNR Item Number
POSTX1 ItemText
MENGE Component Quantity


Functional Location Task List

Tables Description
TAPL Allocation of Task List to Functional Location
PLAS Task List – Selection of Operations / Activities
PLPO Task List – Operation / Activity


TAPL:  Allocation of Task List to Functional Location

Key Fields Description
TPLNR Functional Location
PLNTY Task List Type
PLNNR Key for Task List Group
PLNAL Group Counter
IWERK Maintenance Planning Plant
ARBID Work Center ID


PLAS:  Task List – Selection of Operation / Activities

Key Fields Description
PLNTY Task List Type
PLNNR Key for Task List Group
PLNAL Group Counter
LOEKZ Marked for Deletion (“X”)


PLPO:  Task List – Operation / Activity

Key Fields Description
PLNTY Task List Type
PLNNR Key for Task List Group
VORNR Operation Number
STEUS Control Key
WERKS Plant
LTXA1 Short Text
LAR01 Activity Type


General Task List

Tables Description
PLKO Task List Header
PLAS Task List – Selection of Operations / Activities
PLPO Task List – Operation / Activity

PLKO:  Task List Header

Key Fields Description
PLNTY Task List Type
PLNNR Key for Task List Group
PLNAL Group Counter
VERWE Task List Usage
WERKS Plant
KTEXT Task List Short Text
VAGRP Responsible Planner Group


PLAS:  Task List – Selection of Operation / Activities

Key Fields Description
PLNTY Task List Type
PLNNR Key for Task List Group
PLNAL Group Counter
LOEKZ Marked for Deletion (“X”)


Maintenance Plans

Tables Description
MPLA Maintenance Plan
MPOS Maintenance Item
PLWP Alloc of Maint. Packages to TaskList Operatoins
T351P Maintenance Packages
MHIS Maintenance Plan History


MPLA:  Maintenance Plan

Key Fields Description
WARPL Maintenance Plan
WPTXT Maintenance Plan Text
STRAT Maintenance Plan Strategy
EQUNR Equipment Number
TPLNR Functional Location
HORIZ Call Horizon
ABRHO Scheduling Period


MPOS:  Maintenance Item

Key Fields Description
WAPOS Maintenance Item
WARPL Maintenance Plan
STRAT Maintenance Strategy
PSTXT Item Short Text
EQUNR Equipment Number
PLNTY Task List Type
PLNNR Task List Group
PLNAL Group Counter
WPGRP Planner Group
GEWRK Object ID for Work Center
IWERK Maintenance Planning Plant
ILOAN Location
AUART Order Type
PRIOK Priority
WARPL Maintenance Plan
ABNUM Maintenance Plan Call Number
NPLDA Next Planned Date
STADT Start Date
LRMDT Date of last Comp. Confirmation
HORDA Call Date


PLWP:  Allocation of Maintenance Packages to Task List Operations

Key Fields Description
PLNTY Task List Type
PLNNR Group Key
PLNAL Group Counter
STRAT Maintenance Strategy
LOEKZ Deletion Indicator
PAKET Maintenance package number

Work Orders

Tables Description
AUFK Order master data
AFIH Maintenance Order Header
AFKO Order Header data
AFVC Operation within an order
AFVV Operation Duration Quantity/Dates/Values
AFVU User fields for Operation
JEST Object Status
TJ02T System Status Texts
CRHD Work Center Header
ILOA PM Object Location and Account Assignment
COBRA Settlement Rule for Order Settlement
COBRB  Distribution Rules for Settlement Rule (order)


AUFK:  Order master data

Key Fields Description
AUFNR Order Number
AUART Order Type (“30” for PM)
AUTYP Order Category
KTEXT Short Text
LTEXT Indicator:  “Long Text Exists”
WERKS Maintenance Plant
LOEKZ Deletion Flag
KOSTL Settlement Cost Center
KOSTV Responsible Cost Center


AFIH:  Maintenance Order Header

Key Fields Description
AUFNR Order Number
PRIOK Priority
EQUNR Equipment Number
ILOAN Functional Location ID
ANLZU System Condition
IWERK Planning Plant
INGPR Responsible Planner Group
GEWRK Work Center ID
ILART Maintenance Activity Type
QMNUM Notification


AFKO:  Order Header Data

Key Fields Description
AUFNR Order Number
GLTRP Basic finish date
GSTRP Basic start date
AUFPL Link to Order Operation


AFVC:  Order Operations

Key Fields Description
AUFPL Link to Order Header
VORNR Operation Number
STEUS Control Key
ARBID Work Center ID
WERKS Plant
LTXA1 Short Text
LTXA2 2nd Line of Description
LARNT Activity Type
INDET Calculation Key
ANZZL Number of Resources


AFVV:  Operation Duration Quantity/Dates/Values

Key Fields Description
ARBEI Work
DAUNO Duration


sources : https://wiki.scn.sap.com/wiki/display/ERPLO/Useful+Tables+-+PM+Module