What are some SAP recommended guiding principles to achieve clean core operations? Note: There are 3 correct answers to this question.
SAP's clean core principles (as per S/4HANA Cloud strategy) aim for a standardized, upgrade-friendly system:
Establish an Organizational Structure, Technical Foundation, and Transformation Methodology for Clean Core (A): This foundational principle ensures governance and methodology (e.g., SAP Activate) for clean core adoption.
Integrate Clean Core Practices in the End-to-End Value Process Chain (B): Embedding clean core into business processes ensures minimal customization and maximum standard use.
Establish Regular Housekeeping Tasks and Procedures (C): Ongoing maintenance (e.g., data cleanup) keeps the system lean and standard-compliant.
Establish Release Management (D): While important, it's a broader IT practice, not a core clean core principle.
Define Roles and Responsibilities as Part of a Process Transformation Office (E): Useful but not a primary SAP-defined clean core principle.
Thus, 'A, B, C' are the correct answers.
You have entered a priority during creation of a notification. What action will this trigger in the system?
Entering a priority (e.g., 'High') in a quality notification (transaction QM01):
Calculate the Notification Start and Finish Dates (C): The priority (set in Customizing, SPRO > QM > Quality Notifications > Define Priorities) triggers the system to calculate required start and end dates based on response times linked to the priority (e.g., 24 hours for 'High'). This is standard behavior for time-sensitive notifications.
Create Activities Automatically (A): Activities are logged manually or via action boxes, not priority.
Create Tasks Automatically (B): Tasks require a response profile, not just priority.
Calculate Malfunction Dates (D): Malfunction dates are specific to equipment notifications (e.g., F2), not driven by priority alone.
Thus, 'Calculate the notification start and finish dates' is the correct answer.
In which business object do you set whether the supplier must provide a quality certificate and the type of quality certificate that is required?
The requirement for a supplier to provide a quality certificate and its type is configured in:
Quality Info Record: Procurement (D): In the quality info record (transaction QI01), you set the 'Certificate Required' indicator and specify the 'Certificate Type' (e.g., 'ISO 9001') under the 'Certificate Data' section. This links the requirement to a specific material-supplier combination, enforced during GR (SPRO > QM > Quality Inspection > Quality Info Record).
Purchase Order (A): POs inherit certificate settings from the quality info record, not define them.
Material Master (B): The QM view defines inspection types, not certificate requirements or types.
Business Partner (C): Supplier master data lacks QM-specific certificate settings.
Thus, 'Quality info record: Procurement' is the correct answer.
For which structure elements of a quality notification is the assignment of a catalog type possible? Note: There are 3 correct answers to this question.
In SAP S/4HANA QM, quality notifications (e.g., transaction QM01) use catalog types to classify data in specific structure elements:
Defect Locations (A): Catalog type 'A' (Defect Location) can be assigned to specify where a defect occurred (e.g., 'Surface'), configured in the notification item (SPRO > QM > Quality Notifications > Catalogs).
Defect Types (D): Catalog type '9' (Defect Type) is assigned to classify the nature of the defect (e.g., 'Scratch'), a standard field in the notification item.
Tasks (E): Catalog type '2' (Tasks) is used to define actions (e.g., 'Repair') in the tasks tab of the notification.
Assigned Objects (B): Objects (e.g., material, batch) are referenced but don't use catalog types directly.
Defect Causers (C): Causers (e.g., 'Machine') use catalog type '5' (Causes), but this isn't listed as 'Defect causers' in standard terms; it's typically 'Causes.'
Thus, 'Defect locations,' 'Defect types,' and 'Tasks' are the correct answers based on standard structure elements.
You want to create a quality notification for the Complaint Against Supplier notification origin. Which of the following documents are available as standard in SAP S/4HANA to use as reference documents? Note: There are 2 correct answers to this question.
For a 'Complaint Against Supplier' notification (e.g., type Q2, transaction QM01):
Material Document (B): Material documents (e.g., goods receipt via MIGO) are standard references, linking the complaint to a specific receipt event (SPRO > QM > Quality Notifications > Notification Creation).
Purchasing Document (C): Purchase orders (e.g., from ME21N) are commonly referenced to tie the complaint to the supplier's delivery or order.
WBS Element (A): Work Breakdown Structure elements are PS-related, not standard for supplier complaints.
QM Order (D): QM orders track costs but aren't reference documents for notification creation.
Thus, 'Material document' and 'Purchasing document' are the correct answers.
Harrison
1 month agoOra
2 months agoKerry
2 months agoAudria
2 months agoJohna
2 months agoMarkus
3 months agoRoselle
3 months agoLeah
3 months agoGertude
3 months agoAvery
4 months agoAnnette
4 months agoAnthony
4 months agoFallon
4 months agoRueben
5 months agoErin
5 months agoBrice
5 months agoAlonso
5 months agoMagnolia
6 months agoChara
6 months agoCrista
8 months agoLaura
9 months agoAudry
11 months agoLauran
12 months agoMariann
1 year agoSylvia
1 year agoBarb
1 year agoLenora
1 year agoMaryanne
1 year agoAudry
1 year agoAntonette
1 year agoValda
1 year agoMireya
1 year agoCarlee
1 year agoKimberlie
1 year agoFreida
1 year agoMartina
1 year agoTresa
1 year agoJean
2 years agoDelisa
2 years agoCyril
2 years agoTrevor
2 years agoAlmeta
2 years agoLizette
2 years agoVal
2 years agoTijuana
2 years agoSolange
2 years agoJunita
2 years agoCarin
2 years agoShanice
2 years ago