SAP C_TS470_2412 問題集 練習問題・模擬試験｜日本語版＆英語版対応

Explanation: In SAP S/4HANA Cloud Private Edition, Service, a maintenance plan is used to schedule recurring service or maintenance activities. The call date represents the date when the system generates a call object (e.g., a service order) based on the maintenance plan’s scheduling parameters, such as cycles or intervals. The planned date, on the other hand, is the date when the actual execution of the service or maintenance activity is scheduled to occur. Option B states that "the call date is usually before the planned date, to create a preprocessing phase," which aligns with standard SAP functionality. The call date typically precedes the planned date to allow time for preparation, such as resource allocation, spare parts planning, or technician scheduling. This preprocessing phase ensures that all prerequisites are in place before the service is executed. The difference between these dates is influenced by the call horizon, a parameter in the maintenance plan that defines how far in advance the call object is generated relative to the planned execution date. Option A is incorrect because the call date being equal to the planned date is not a default rule; it depends on specific configurations (e.g., a call horizon of 0%), which is not typical. Option C is a goal of scheduling but does not directly describe the relationship between the dates. Option D is incorrect because the planned date is not always before the call date―this would contradict the purpose of scheduling, as the call initiates the process leading to the planned execution. "The call date is determined by the scheduling parameters of the maintenance plan, including the call horizon, which specifies the lead time before the planned date. This allows for a preprocessing phase to prepare for the service execution."

Explanation: In SAP S/4HANA Cloud Private Edition, Service, a personnel number refers to an identifier for an individual employee or resource, typically managed in the Human Resources (HR) module or linked via organizational management. The question asks which object allows direct assignment of such a personnel number. The correct answer is task list operation (Option C). In a maintenance or service task list, operations define specific activities to be performed, and you can assign a personnel number to an operation to specify the responsible employee or technician. This assignment is part of capacity planning and resource allocation, ensuring that the right individual is scheduled for the task. Organizational unit (A): This is a higher-level structure in organizational management (e.g., a department) and does not directly accept a personnel number assignment. Personnel are linked to it via positions or roles, not directly. Service team (B): While a service team consists of personnel, it is a group entity, and individual personnel numbers are not assigned to it as an object in this context. Work center (D): A work center represents a location or group of resources (e.g., machines or people) and can be linked to capacity, but it does not directly accept a personnel number assignment. Instead, it uses capacity categories or links to HR indirectly. "In task lists, operations can be assigned to specific personnel numbers to define the responsible employee for executing the task, facilitating detailed resource planning."

Explanation: Creating service contracts in SAP S/4HANA Cloud Private Edition, Service can be time-consuming if done from scratch. To streamline this process, SAP provides tools to reuse existing data. The correct answer is service contract templates (Option D). A service contract template is a predefined structure that includes standard data such as items, pricing conditions, billing plans, and service objects. When creating a new service contract, you can select a template and adapt it to the specific customer or scenario, significantly reducing manual entry and ensuring consistency. Service contract quotations (A): These are preliminary documents used to propose a contract to a customer, but they are not designed for reuse as templates for contract creation. Service order templates (B): These are used to standardize service orders, not service contracts, and thus do not apply here. Product bundles (C): These group products or services together but are not templates for creating contracts; they are more relevant to sales or service items. "Service contract templates enable the rapid creation of new contracts by providing reusable structures with predefined data, such as items and conditions, which can be adjusted as needed."