This Blog is mainly on SAP Exam Questions and Selected "How-to" SAP processes

Saturday, October 31, 2026

Question no 4260 : Planned Delivery Costs Automatic Settlement

In SAP S/4, to be able to perform Automatic Settlement of Delivery Cost via MRDC (Automatic Delivery Costs Settlement), select the required Prerequisites ?


(more than one answers)

A)  Baseline date must be set at the Company Code of the Freight Vendor V02.
B)  Baseline date must be set at the Company Code of the Freight Vendor V01.
C)  Vendor Master "V02" must be set with "ERS" indicator.
D)  Automatic Settlement of Planned Delivery Costs configured for the Freight Vendor V02.
E)  Automatic Settlement of Planned Delivery Costs configured for the Freight Vendor V01.
.

Answer: A, D

Prerequisites for MRDC (Automatic Delivery Costs Settlement)
    IMG > MM > LIV > ERS > Specify automatic Settlement of Planned Delivery Costs
        Activate for combination Company Code + Pur.Org + Freight Vendor V02
    SM30 Table T196F
        Transaction Code MRDC with Default Document type "RE" (or other user defined)
    Freight Vendor V02
        Payment Term at the Company Code of the PO concerned

Friday, October 30, 2026

SAP SD - Adjust and Process Output Type for Outbound Delivery

click "here" to view the Presentation

Question no 4259 : ERS without GR-Based IV

In SAP S/4 1909, ERS without GR-Based IV can be used for which ERS transaction below ?


(more than one answers)

A)  MRRL.
B)  MRKO for Consignment Settlement.
C)  MRKO for Pipeline Settlement.
D)  MRIS for Invoicing Plan Settlement
E)  All of the above.
.

Answer: B, C, D

Both MRRL and MRDC
    expects ERS with GR-Based IV to Settle Material Supplier Invoice and Freight Supplier Invoice as 
    the basis on Auto Invoice is based on Goods Receipt Material Document.
MRER (for Automotive ERS) 
    is available in S/4 carried over from Automotive Industry Solution; technically in S/4
    MRER can be used for a ERS+GR-BasedIV PO.
MRKO (Consignment and Pipeline Settlement)
    There is no Price for Consignment PO and Goods Receipt for Consignment PO is not valuated.
    The GI of Consignment stock and Transfer of Consignment Stock to own stock do not required
    GR-Based-IV for the Auto Invoice.
    The GI of Pipeline stocks Material Document tis used for Auto Invoice but without GR-Based-IV 
    setting.
MRIS (Invoicing Plan Settlement)
    Invoicing Plan settlement is for Invoicing Plan PO without GR and GR-Based-IV setting is therefore
    not relevant.

Thursday, October 29, 2026

SAP Business One (Production) - Processes and Account Determination for Non-Stock Item in the Production Order

CLICK here to view the Presentation 

Question no 4258: Materials created with the Material Type UNBW

In SAP Material Management, what can be said to be TRUE about Materials created with the Material Type UNBW ?


(more than one answers) 

A)  The Material Type "UNBW" is to delivered with Accounting view selection for the Material Master.
B)  Good Receipt without Purchase Order for this type of Material will not result in any Accounting Document. 
C)  Info Record is not possible for Material created with Material Type "UNBW". 
D)  Account Assignment is mandatory in the Purchase Order for this kind of Material.
E)  GR Non-Valuated scenario is not allowed for Purchase Order of Material with "UNBW".
.

Answer: A, B, D





Wednesday, October 28, 2026

SAP MM - Text Types for PO Message Output

SAP Business One (Production) - Template BOM vs Sales BOM used in Sales and Purchasing

CLICK here to view the Presentation 

SAP SD - Pricing Area Menu in VK31, VK32, VK33

 

click "here" to view the Presentation

Question no 4257 : Pre-requisites for Invoicing Plan

In SAP S/4, what are the pre-requisites for Invoicing Plan ?


(more than one answers)

A)  GR-Based IV is mandatory.
B)  The Purchase Order item must be set with a Tax Code.
C)  ERS indicator must be set in the Vendor Master.
D)  Material Master is not required in the Purchase Order. 
E)  ERS indicator need not be in the Vendor Master but can be set in the PO item.
.
(more than one answers)

Answer: A, B, C, D

Characteristics for Invoicing Plan
Vendor Purchasing data setting for ERS is Mandatory (if ERS not set in Vendor, the ERS indicator is not visible in the PO item "Invoice" tab)
In the PO Header, the Doc type "FO" (Framework Order) is expected for allowing Validity Periods
In the PO Header, Payment Term is necessary so that Base line date is derived for the Auto Invoice
In the PO item overview, the Account Assignment is Mandatory (not "U" or Unknown)
In the PO item overview, Item Category is not logical
In the PO item overview, Material Master is possible to default description, UOM, or PO Text and Material Group 
In the PO Delivery Tab, the GR indicator  if select must be set also with GR-Non-Valuated indicator (and GR is still possible, however this may not make sense for Invoicing Plan)
In the PO Invoice Tab, Tax Code is Mandatory
In the PO Invoice Tab, ERS indicator expected otherwise MRIS not possible
In the PO Invoice Tab, Define the Invoice Plan details

 

Tuesday, October 27, 2026

Question no 4256 : Source list Blocked

In SAP S/4, when the Source List is Blocked with Info Record for Material + Vendor set for "Auto Sourcing", which of the following statements are TRUE ?


(more than one answers)

A)  Source Determination in manual Purchase Requisitions is not possible.
B)  MRP Live will not create Purchase Requisitions but only Planned Orders for any shortages.
C)  RFQ is not possible.
D)  Create Purchase Order is not possible.
E)  Goods Receipt for Purchase Orders previously created is no longer possible.
.

Answer: A, D

Monday, October 26, 2026

SAP Business One (Production) - BOM with Items for Backflush, Goods Issue, and Labor


 CLICK here to view the Presentation

S/4 PS - Project Budgets (Fiori App and S/4 Gui)

 

click "here" to view the Presentation

SAP Business One (Tools) - Query Wizard: OITM (Item Master Table)


 CLICK here to view the Presentation

S/4 PS - Project Execution (Fiori App and S/4 Gui)

 

click "here" to view the Presentation

Question no 4255 : ME58 Generate Service Entry Sheet

In SAP S/4, what are the characteristics of the Service Entry Sheet generation via ME58 (Follow-on function for Purchase Requisition - via Assignment List)


(more than one answer)

A) A Framework Purchase Order with Document type "FO".
B) The Vendor for the Framework Purchase Order must be in the Source List.
C) The Framework PO is assigned to the Maintenance Order Operation.
D) Service Master or Description without Service Master is possible as Service item.
E) There is no Goods Receipt for the Framework PO.
.

Answer: A, C, D, E

(B) There is no Material in the Framework PO (just description) and therefore it is not relevant to the Source List.

Setup for Framework Order SES for Plant Maintenance
Service Master (AC03)
Framework PO (ME21)
Doc type "FO"
Header Validity Period
Account Assignment "U"
Item Category "D"
Service Master in the PO detail
Maintenance Order
Operation with Control Key PM03
Assign the Framework Purchase Order
Purchase Requisition generated assigned to the Framework PO as the Source
ME58 to Generate the SES 



Sunday, October 25, 2026

SAP Production Planning & Detail Scheduling - Alternative Materials in Production Orders

SAP Business One (Inventory) - Stock Count (Warehouse w/o Bin Location)


 CLICK here to view the Presentation

Question no 4254 : Functions of ME58

In SAP S/4, what are the functions of ME58 (via Assignment List) ?
 

(more than one answers)

A)  PO Release Order for Contract.
B)  Delivery Schedule for Scheduling Agreement.
C)  SES for Framework Purchase Order.
D)  RFQ
E)  Stock Transport Purchase Order.
.

Answer: A, B, C, E

ME58 can generate the following:
PO Release Order for Contract.
Delivery Schedule for Scheduling Agreement.
SES for Framework Purchase Order.
Stock Transport Purchase Order.
Purchase Order for external Vendor 

Saturday, October 24, 2026

SAP Plant Maintenance - Replace EQ (Meter) in Object List in Maintenance Plan

 

CLICK here to view the Presentation

SAP Plant Maintenance - Classic Revision Management (Order-Level)


Question no 4253 : ME56 (Assign) and ME57 (Assign and Process)

In SAP S/4, in Materials Management, the differences between ME56 and ME57 in Follow-up Processing for Purchase Requisitions are which of the following ? (ME57 can perform what additional functions)


(more than one answers)

A)  Change contents in the Purchase Requisition item.
B)  Assign and Un-Assign Source of Supply.
C)  Convert Purchase Requisitions to Purchase Orders.
D)  Convert Purchase Requisitions into Contracts.
E)  Process Purchase Requisitions flagged for RFQ
.

Answer: C, E   

ME56 (Assign) can do the following:
Source Determination (Automatic)
Source Assignment (Manual)
Unset Source Assigned
Attach DMS Documents
Undo Changes (previous step) (there is a button for this)
Make changes to PR item fields

ME57 (Assign and Process) can do the following:
Source Determination (Automatic)
Source Assignment (Manual)
Unset Source Assigned
Attach DMS Documents
Undo Changes (previous step) (there is a button for this)
Make changes to PR item fields
Flag PR for RFQ with Vendor
Flag PR for RFQ without Vendor
Processing Flagged PR for RFQ into RFQ document
Convert PRs to PO
Convert PRs to Contract Released Order
Convert PRs with Scheduling Agreement to Delivery Schedules

Friday, October 23, 2026

SAP Plant Maintenance - CMMS Compliance

SAP and Computerized Maintenance Management System (CMMS) often referred to as the Plant Maintenance module (PM) or "Enterprise Asset Management (EAM)" ensures regulatory compliance, safety standards adherence, and provides extensive audit-ready maintenance tracking by pairing enterprise financial controls with plant maintenance planning and execution processes. 
How SAP and CMMS Drive Compliance:
  • System of Record vs. Execution: SAP (such as SAP PM, EHS, and QM modules) remains the core system of record for asset master data, maintenance plans, and financial/audit logs, while a connected CMMS handles mobile work execution, checklists, and technician task updates.
  • Preventive Maintenance (PM) Compliance: Tracks whether preventive maintenance work orders are completed on or before their due dates, often benchmarked using standard grace rules (e.g., closing monthly PMs within 3 days, quarterly PMs within 9 days, and annual PMs within 36 days.
  • Regulatory Alignment (GMP, OSHA, ISO): Integrates calibration records (e.g., 21 CFR §211.68), equipment qualification (IQ/OQ/PQ under GAMP 5), and process safety management (PSM/MOC workflows) directly into asset audit trails.
Core Integrated Modules:
  • SAP PM (Plant Maintenance): Stores equipment and equipment structure, functional locations, maintenance plans, and maintenance notifications, and maintenance orders planning and execution. 
  • SAP QM (Quality Management): Manages inspection lots, compliance documentation, and root-cause analysis.
  • SAP EHS / Compliance Obligation Registers: Tracks permits, safety inspections, air/water emissions regulations, and action assignments to prevent compliance gap. 
  • SAP MM: Links spare parts consumption, calibration tool traceability, serial-equipment tracting, contract purchasing, warranty management and end-to-end procurement process from purchase requisition to accounts payable and payment.
  • SAP FI/CO: Links spare parts consumption, calibration tool traceability, and labor cost settlements directly to compliance work orders. 
Core Compliance Checklist Categories:

1. Asset Register & Criticality Data:
  • Hierarchical Asset Tree: Map functional location hierarchy with equipment installation and their relevant construction types (BOM explosion) plus permits.
    • SAP T-code: IH01, IH03, IN16.
    • SAP Fiori: Asset Viewer.
  • Criticality Classifications: Tag assets by safety, environmental, and production impact to set required preventive maintenance (PM) frequencies.
    • SAP T-code: IL01/IL02 (Structural Indicator with Edit Mask).
    • SAP T-code: CL02, CT04 Functional Location (Class type "03").
    • SAP T-code: CL02, CT04 Equipment Classification (Class type "02"). 
  • Failure Code Tracking: Standardize root-cause codes via Catalog Profile and Catalog Types (e.g., electrical, mechanical, safety interlock failure) logged by technicians on every maintenance notification. 
    • SAP T-code: QS41. 
    • SAP T-code; IL02, IE02 assignment of Catalog Profile.
2. Preventive & Compliance Maintenance Targets:
  • Detective Tasks (Min. 85% compliance): Inspection Rounding and Inspection Checklist.
    • SAP T-code: IA05/IA06 (Create Task List for Inspection Checklist). 
    • SAP T-code: IP41 (Create Single Cycle Plans for Technical Object). 
    • SAP T-code: IW91 (Checklists: Result Overview (used to view and record inspection results).
    • SAP T-code IW92  (Checklists: Generation (used to generate checklists for maintenance orders).
    • SAP T-code IW93 (Checklists: Collective Usage Decisions (used to process collective usage decisions and execute follow-up actions).
    • SAP T-code IW97 (Checklists: Simulate Inspection Lots (used for testing and simulation).
    • SAP T-code IW98 (Checklists: Classification Characteristics (used to define characteristic matching).
    • SAP T-code IW99 Checklists: Types (used to define and configure checklist types).
  • Time-Based Preventive Tasks (Min. 90% compliance): Component replacements, filter changes, and lubrication, calibration, shutdown etc. 
    • SAP T-code: IP11 (Strategy Type for Time and Other Unit of Measure eg; Engine hours, Distance etc). 
    • SAP T-code: IP42 (Strategy Plan). 
    • SAP T-code: IP19, IP24.
  • Condition-Based / Predictive Tasks (Min. 95% data availability): Continuous vibration, temperature, or sensor data streams integrated directly into maintenance order. To implement Condition-Based Maintenance (CBM) in SAP (Plant Maintenance / EAM or SAP S/4HANA), you link asset condition readings to automated alerts, notifications, and maintenance order. 
    • Automated / External Integration:
      • Connect external SCADA, PLC, or IoT monitoring systems using the PM-PCS Interface or SAP Asset Performance Management (SAP APM) with embedded IoT/OPC UA connections.
      • Incoming telemetry streams pass values directly into SAP to generate measurement documents.
    • Manual Entry: 
      • Operators or technicians enter regular inspection or sensor readings via transaction IK11 (Create Measurement Document). You can also use valuation codes (e.g., Normal, Medium, Immediate Stop).
3. Facility Systems & Safety Infrastructure:
  • Production Machinery: Motors, drives, gearboxes, and conveyors.
  • Facility Infrastructure: HVAC, high-voltage electrical panels, and compressed air systems.
  • Safety Systems: Emergency stop buttons, light curtains, physical guards, and safety interlock validation.
  • Material Handling & Storage: Forklifts, cranes, hoists, and storage rack load certifications. 
    • SAP T-code: IL01, IE01, IH01, IH03 (mapping Floc and Equipments).
    • SAP T-code: CL02, CT04 (Floc and Equipment Classification).
    • STP T-code: IA05 (Calibration Plan).
4. Documentation & Audit Trails:
  • Digital Work Order Logs: Timestamped records of who performed the task, parts used, downtime duration, and sign-offs.
    • SAP T-code: MCJB, MCI7, MCI4 (analyzing Mean Time to Repair (MTTR) and Mean Time Between Repari (MTBR)). 
    • SAP T-code: IW29 / IW28 (used to list and filter breakdown notifications, allowing you to export or sum total breakdown durations to manually calculate MTTR (Total Downtime / Number of Breakdowns). 
  • Standard Operating Procedures (SOPs): Attached safety manuals, Lockout-Tagout (LOTO) guides, and schematics linked directly to PM templates.
    • SAP T-code: WCTK (Work Clearance Application)
    • SAP T-code: WCTA (Work Clearance Approval)
    • SAP T-code: WCT6 (Operational WCD)
  • Regulatory Compliance Logs: SAP Plant Maintenance (PM) supports inspection certificates, checklists, and measurement recordings, though formal quality certification workflows are often integrated with the SAP Quality Management (QM) module or handled via SAP S/4 HANA  "Inspection Checklists". 
    • SAP T-code: IW91 (Checklists: Result Overview (used to view and record inspection results).
    • SAP T-code IW92  (Checklists: Generation (used to generate checklists for maintenance orders).
    • SAP T-code QC21 (Print or generate a quality certificate for an inspection lot for the inspection checklist). 
  • Spare Parts & BOM Integration: Bill of Materials linked to specific assets (Equipment and/or Functional Location) to verify proper replacement components are used during compliance-mandated repairs.
    • T-code: IE02, IL02, CS01/CS02 (BOM) as Construction Type
5. CMMS Compliance Best Practices:
  • Automate Schedule Tracking: Monitor schedule compliance (percentage of PMs completed on or before their due date; target 90%–95%, noting that >20% late completion signals process breakdown).
    • SAP Fiori App using "Resource Scheduling for Maintenance Order" (App ID F2227)
  • Enforce Mandatory Fields: Restrict Maintenance Notification closure "NOCO status" in the CMMS until failure codes, safety checklists, and photo verifications are attached. This is done via Task Catalog Code assignment which must be completed before the Maintenance Notification can be set with "NOCO status".
    • SAP T-code: IW66, IW67
    • SAP T-code: Field Selection Configuration for Maintenance Notification
  • Schedule Periodic Audits: Review CMMS compliance logs monthly or quarterly to catch inspection gaps before regulatory walk-throughs.
    • SAP T-code: PLMD_AUDIT (Main transaction for creating and managing audit plans, audits, question lists, and audit components). 
    • SAP T-code: PLMC_AUDIT (Customizing transaction for configuring SAP Audit Management settings). 
    • SAP T-code: PLM_AUDITMONITOR (Used for monitoring, reviewing, and evaluating existing audit objects and question list results). 
    • SAP T-code: PLM_AUDIT_DISPLAY (Used specifically for displaying audit components in read-only mode). 

Question no 4252 : ME56 (Assign) functions

In SAP S/4, the following screen is form transaction code ME56 (Assign) in Material Management, the possible processes that can be performed in this this transaction code are?

(Do not be confused by the screen title "Assign and process Purchase Requisitions, it is transaction code ME56)



(only one answer)

A) Perform Source Determination.
B) Unset Assigned Source to the Purchase Requisitions.
C) Flag Purchase Requisitions for RFQ and convert to an RFQ.
D) Change Assigned Source Manually.
E) Change the Purchase Requisitions contents for example Delivery Address.
.

Answer: A, B, D, E