Learn, Practice, and Improve with SAP C_TS412_2021 Practice Test Questions

Explanation:

In SAP PS, activity scheduling is driven by relationships (dependencies) between activities. To define a successor activity starting two days after its predecessor finishes, apply a positive offset on a Finish-to-Start (FS) relationship. This offset (e.g., +2d) is the standard and dynamic method, ensuring automatic schedule recalculation if predecessor dates change.

Why other options are incorrect:

B. Milestone date offset:
Milestones are fixed schedule markers; offsetting them does not recalculate activity dates based on predecessors.

C. Material requirement date offset:
This controls material availability timing (e.g., lead-time scheduling) relative to an activity’s dates, but does not define the activity-to-activity scheduling logic.

D. Hard constraint ('Must start on'):
Manually fixes the start date, breaking dynamic scheduling. Any change to the predecessor requires manual recalculation.

Reference:
SAP standard network scheduling logic, as defined in the SAP Help documentation "Relationships Between Activities" and "Time Scheduling in Networks". This core PS principle is also covered in SAP certification training for C_TS412_2021 under network scheduling.

Explanation:

This sequence follows the standard procurement and service acceptance process integrated with an internal activity (cost activity) in SAP PS. After vendor selection based on quotations, a purchase order (PO) is issued. The PO is then monitored until the service is performed. The Acceptance of Performed Service (done via a system confirmation or service entry sheet) is the equivalent of a Goods Receipt for services. Only after confirming service completion (GR) can the vendor's Invoice Receipt be matched and posted, enabling payment.

Why other options are incorrect:

A: Incorrectly places "Benefic check" first and mixes the sequence. A benefic check (often budget check) occurs before or during PO release, not before vendor selection. Also, "Acceptance of performed service" is the GR step and must occur before invoice receipt.
B: Omits Goods Receipt (Acceptance) and Invoice Receipt, which are mandatory final steps for service completion and payment.
C: Incorrectly places invoice receipt before goods receipt (service acceptance). In SAP, you cannot post an invoice for a service or material before recording its receipt.

Reference:
This follows the standard Procurement Cycle integrated with Project Systems. Key documentation includes SAP Help: "External Procurement Processes in Networks" and "Service Entry Sheets for Internal Activities". The process is also detailed in training materials for C_TS412_2021 under the integration of Networks with Materials Management (MM) and Invoice Verification.

Explanation:

In SAP Project Systems, material and service requirements generated in a network (like reservations for stock materials or purchase requisitions for external procurement) are only activated and passed to the downstream logistics modules when the relevant network or activity is released. The release status is a key control point that authorizes execution and triggers the creation of procurement documents in the system.

Why other options are incorrect:

A: Saving the project or network only stores the data; it does not trigger the activation of requirements or change the document status to "Released".

B: The replenishment lead time and requirement date are used for scheduling the requirement date within the network, but the actual activation (document generation) still depends on the release.

C: A standard milestone activity can influence dates and scheduling but does not itself act as a release trigger for requirements.

Reference:
This is a core concept in Network Status Management. The behavior is defined in the "Release" system status for networks/activities. SAP Help documentation "Releasing Networks and Activities" confirms that releasing is the trigger for generating reservations, purchase requisitions, and generating capacity requirements.

Explanation:

To enable automatic scheduling of events in Progress Tracking (PS-PRT), you must first define Event Scenarios in Customizing (transaction OPS9). An event scenario contains the scheduling-relevant parameters, such as the duration of the event and its relationship to other events or to the network activity's basic dates. This allows the system to calculate event dates automatically based on the network schedule, replacing manual maintenance.

Why other options are incorrect:

A: Priority of events is used for sorting and evaluation in reporting, not for scheduling calculations.

B: Material scheduling parameters (like in MRP) are for procurement and do not control the date calculation of Progress Tracking events.

C: Manual release of events is a status management step; it does not enable or define the automatic date scheduling logic.

Reference:
SAP Help: "Progress Tracking: Event Scenarios" (Customizing path: Project System → Progress Tracking → Define Event Scenario). The configuration of event scenarios with durations and relationships is the prerequisite for moving from manual date entry to automatic event scheduling.

Explanations:

A & E: Structural Hierarchy SAP PS allows for significant flexibility in project design. While most projects utilize a single Level 1 "Header" WBS, the system technically supports multiple Level 1 elements within a single Project Definition. Similarly, at any subordinate level, you can create multiple peer elements to represent different work packages or departments.

D: Operative Indicators This is the most functional aspect of a WBS. Operative Indicators define what a WBS element can "do." Since a single work package often requires budget planning, actual cost collection, and revenue generation, SAP allows a single element to hold all three statuses (Planning, Account Assignment, and Billing) simultaneously.

Why the Other Options are Incorrect:

B: The 10-level Limit:
This is a common "distractor" in SAP exams. While the Project Coding Mask (set in T-code OPSK) defines the length and depth of the ID, there is no hard-coded requirement or limit of exactly 10 levels.

C: Project Definition Assignment:
A WBS element is intrinsically tied to its parent Project Definition. The Project Definition serves as the master record; you cannot "cross-assign" a WBS element to a different project header without physically moving or recreating it.

References:
SAP Learning (PLM200): Project Management - Structures. This course details the hierarchy and the use of operative indicators.

Explanation:

B. Correct. For activity-account-assigned networks, costs are collected at the network header (or activity) level and must be settled. The settlement rule is specified directly on the network header (or activity) to allocate these costs.

C. Correct. WBS elements are the primary settlement receivers in Project Systems. Settlement rules are defined on WBS elements to distribute costs to one or more receivers (e.g., cost centers, fixed assets, other WBS elements).

Why A is incorrect:

A. Standard WBS elements are templates for creating operative WBS elements and do not carry actual costs. Settlement rules are only maintained on operative objects that incur costs (actual WBS elements, networks, or orders).

Reference:
SAP Help: "Settlement Rule Maintenance" and "Settlement in Networks" confirm that settlement rules are assigned to cost objects (operative WBS elements, network headers, or activities in activity-account-assigned networks). Standard WBS elements are for structure templates only.

Explanation:

When creating projects that contain networks, the Project Profile must specify a Network Profile. The network profile determines key control parameters for all networks within that project, such as numbering, status management, and default settings. This assignment is mandatory in the project's definition phase.

Why other options are incorrect:

A: You cannot reassign an activity from one network to another. Activities are permanently tied to their network. You would need to delete and recreate the activity in the target network.

B: A network header is assigned to exactly one WBS element (the highest-level WBS element for costing). Multiple assignments are not possible.

D: The Account Assignment Element indicator is activated for WBS elements that receive actual costs, but this is not a requirement specifically for WBS elements with activities. Activities themselves or their network header may handle account assignment, depending on the network type.

Reference:

SAP Help: "Project Profile" configuration specifies the assigned network profile. This is a foundational setting in the IMG path: Project System → Structures → Operative Structures → Work Breakdown Structure → Create Project Profile. Network-WBS assignment rules are defined under network account assignment settings.