Archives

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

Cara Menghapus Order dengan User Status PLAN / PCOM

Untuk menghapus order dengan user status PLAN ataupun PCOM, maka berikut adalah cara yang bisa dilakukan

PERTAMA

Buat Plan Cost menjadi 0 (nol), dengan cara menghapus semua jasa dan juga material

Menghapus Jasa

Check pada tab Operations. Pastikan hanya ada 1 operation dengan control key INT, dan juga field work dan number harus kosong

menghapus3

Jika masih ada operations yang lain, baik internal maupun external, maka harus di hapus dengan cara berikut :

menghapus2

Menghapus Material

Check pada tab Components. Pastikan semua material sudah di hapus

menghapus5

Jika masih ada material, maka harus di hapus dengan cara berikut :
menghapus4



KEDUA

Kembali check pada tab Cost. Pastikan PLAN COSTS sudah menjadi 0 (nol), dengan cara klik Determine Cost lalu jika sudah nol (0) lalu klik SAVE

menghapus6



KETIGA

Klik Order → Functions → Complete → Do not execute

Cara menghapus WO dg user status PLAN atau PCOM.png

maka System status menjadi CLSD (Closed)

hapus.jpg


KEMPAT

Klik Order → Functions → Deletion Flag → Set

HAPUS 1.jpg

Maka Order akan berhasil di Tutup tanpa ada biaya / cost (nol). Status order akan berubah menjadi CLSD (Closed), DLFL (Deletion Flag)

HAPUS 2.jpg

Permits

Kita bisa menggunakan Permits dalam maintenance and service order processing. Permit digunakan untuk menentukan rules / condition tertentu yang digunakan dalam eksekusi sebuah maintenance tasks.

Untuk menentukan waktu dari sebuah proses order, Permit dapat diberikan :

  • Sebelum order itu di released
  • Sebelum order di TECO (technically completed)

Untuk lebih memahami bagaimana cara kerja dari permit, dapat diakses di SAP Library di bawah modul Plant Maintenance (PM) -> Technical Objects (PM-EQM) -> Permits (CS-SE/PM-EQM-SF).

 

SAP PM Standard Reporting

reporting.png

TECHNICAL OBJECT

Technical Objects
MCI1 Object Class
MCI2 Manufacturer
MCI3 Location
MCI6 Object Statistics

MASTER DATA

Functional Location
IH06 List Display Functional Location (List Editing)
IH01 Functional Location Structural Display
IL03 Display Functional Location
MCJC Mean Time to Repair (MTTR)/ Mean Time Between Repair (MTBR) for FunctLoc.
Equipment
IH08 Display Equipment (List Editing)
IE03 Display Equipment
IH03 Structural Display
MCJB Mean Time to Repair (MTTR)/ Mean Time Between Repair (MTBR) for Equipment
Bill of Material (BOM)
IB03 Display Equipment BOM
CS03 Display Material BOM
CS15 Material Where-Used List BOM
Work Center
CR05 Work Center List
IR03 Display Work Center
Measuring Point
IK07 Display Measuring Points (List Editing)
IK03 Display Measuring Point
Class
CL6A Class List
CL6AN Class List (alv)
CL03 Display Classes
CL30N Find Objects in Classes
CL31 Find Objects in Class Type
Characteristics
CT10 Characteristics List
CT11 Characteristics Value List
Catalog
QS42 Display Catalog
Task List
IA09 Display Task List (List Editing)
IA03 Display Equipment Task List
IA07 Display General Maintenance Task List
IP62 Material Usage in Task List
IA16 Task List Costing
Maintenance Strategy
IP12 Display Maintenance Strategy
IP13 Package Sequence
IP14 Where-Used List Strategy
Maintenance Plan
IP16 Display Maintenance Plan (List Editing)
IP03 Display Maintenance Plan
Maintenance Item
IP06 Display
IP18 List

PROCESSING

Maintenance Schedule
IP30 Deadline Monitoring
IP24 Scheduling Overview List Form
IP19 Graphical Scheduling Overview
IP31 Maintenance Plan Costing
Measurement Document
IK17 Display Measurement Document (List Editing)
IK13 Display Measurement document
Maintenance Tasks
MCI4 Planner Group
Notification
IW29 Display Notifications (List Editing)
IW23 Display PM Notification
IW69 Display Notification Items
MCI5 Damage Analysis
MCI7 Breakdown Analysis
Maintenance Order
IW39 Display Maint. Orders (List Editing)
IW33 Display Maintenance Order
IW49N Display Order & Operations
MCI8 Cost Analysis
IWBK Material Availability
IW3M Display Good Movement for Order
IW3D Print Order
IW13 Material Where-Used List
IW12 Display Document Flow List
MB23 Display Reservation
MB25 Reservation List
MM03 Display Material
IH09 / MM60 List of Material – Display
MMBE Stock Overview
MB52 List of Warehouse Stocks
IW3M Display Goods Movements for Order
ME53N Display Purchase Requisition
ME5K List of Purchase Requisitions by Account Assignment
ML84 List of Service Entry Sheets
Confirmation Maintenance Order
IW47 Confirmation List
IW43 Display Maint. Order Confirmation

PM INFORMATION SYSTEM

Plant Maintenance Information System
MCI1 Object Class Analysis
(Report yang menunjukkan jumlah order, notif dan total biaya secara actual maupun plan secara keseluruhan total biaya)
MCI2 Manufacturer Analysis
(Report yang menunjukkan analisis biaya equipment berdasarkan Merk Mesinnya)
MCI3 Location Analysis
(Report yang menunjukkan analisis biaya equipment berdasarkan Lokasinya)
MCI4 Planner Group Analysis
(Report yang menunjukkan analisis biaya equipment berdasarkan plannernya dan bisa di drill down hingga ke biaya per equipment nya)
MCI5 Single Object – Damage Analysis
(Report yang menunjukkan analisis notifikasi berdasarkan jenis laporan kerusakannya)
MCI6 Object Statistics
(Report yang menunjukkan analisis biaya equipment berdasarkan object class nya; funcloc maupun equipment nya)
MCI7 Breakdown Analysis
(Report yang menunjukkan analisis notifikasi berdasarkan jenis laporan breakdown)
MCI8 Cost Analysis
(Report yang menunjukkan analisis biaya berdasarkan jenis order type nya, dan bisa drill down hingga ke funcloc nya)
MCJB Mean Time to Repair (MTTR)/ Mean Time Between Repair (MTBR) for Equipment
(Report yang menunjukkan analisis waktu perbaikan yang di butuhkan pada sebuah equipment
-MTTR : untuk report berapa banyak waktu yang di butuhkan dalam perbaikan 1 equipment
-MTBR : untuk report berapa rata-rata waktu sebuah equipment ini akan rusak kembali)
MCJC Mean Time to Repair (MTTR)/ Mean Time Between Repair (MTBR) for FunctLoc.
(Report yang menunjukkan analisis waktu perbaikan yang di butuhkan pada sebuah funcloc
-MTTR : untuk report berapa banyak waktu yang di butuhkan dalam perbaikan 1 funcloc
-MTBR : untuk report berapa rata-rata waktu sebuah equipment ini akan rusak kembali)

Maintenance Plant

Maintenance Plant adalah sebuah area fisik dimana pekerjaan maintenance dibutuhkan. Pengertian ini juga mengacu pada pengertian sebagai sebuah Plant dalam area logistik. Plant didefinisikan sebagai organisasi tertinggi dalam Company Code yang berhubungan dengan logistik dan pembelian dan merupakan tempat dimana material atau jasa tersedia. Beberapa Plant dapat di-assign ke satu Company Code dimana penilaian persediaan dapat dilakukan untuk masing-masing Plant, dengan kata lain bahwa nilai material  masing-masing Plant dapat berbeda.