NO.23 What could be the reason for multiple commitments, where several operations have the same scheduled dates on a work center after dispatching? Note: There are 2 correct answers to this question.
Multiple commitments occur when several operations are scheduled to start or finish at the same time on a work center. This can happen for different reasons, depending on the settings of the strategy profile and the work center. Two possible reasons are: The Finite Scheduling indicator is NOT set in the strategy profile. This means that the system does not consider the capacity availability of the work center when scheduling the operations. The system only checks the basic dates and the relationships between the operations. Therefore, the system can schedule multiple operations at the same time on the same work center, resulting in multiple commitments. The work center has several individual capacities. This means that the work center can perform several operations simultaneously, depending on the number and type of individual capacities. The system assigns the operations to the individual capacities based on the capacity category and the priority. However, if the individual capacities have the same capacity category and priority, the system can assign multiple operations to the same individual capacity, resulting in multiple commitments. References: Scheduling | SAP Help Portal, Strategy Profile | SAP Help Portal, Individual Capacities | SAP Help Portal.
NO.27 What does the material type influence? Note: There are 2 correct answers to this question.
The material type is a key attribute that classifies materials according to their characteristics and determines how they are processed in the system. The material type influences the following aspects of material management: Which material master screens appear and in which sequence: The material type controls which fields are required, optional, or hidden in the material master record. It also determines the order in which the screens are displayed when creating or changing a material master record. Different material types may have different views and fields depending on the business requirements. For example, a raw material may have a purchasing view, while a finished product may have a sales view. Whether the material is produced in-house, procured externally, or both: The material type defines the procurement type of the material, which indicates how the material is procured. The procurement type can be in-house production, external procurement, or both. The procurement type affects the planning and execution of the material requirements. For example, a material with in-house production procurement type will generate planned orders, while a material with external procurement type will generate purchase requisitions or schedule lines. The material type does not influence the following aspects of material management: Which document types and class categories are allowed: The document type is a key attribute that classifies documents according to their business purpose and determines how they are processed in the system. The document type controls the number range, field selection, and status profile of the document. The document type is independent of the material type and can be used for any material type. For example, a purchase order document type can be used for any material type that is procured externally. The class category is a key attribute that classifies classes according to their application area and determines how they are processed in the system. The class category controls the characteristics, object types, and inheritance rules of the class. The class category is independent of the material type and can be used for any material type. For example, a material class category can be used for any material type that has characteristics. Which plant-specific and plant-independent statuses are allowed: The status is an attribute that indicates the current condition of an object in the system. The status can be plant-specific or plant-independent, depending on whether it applies to a specific plant or to all plants. The status is independent of the material type and can be used for any material type. For example, a material can have a plant-specific status of blocked for quality reasons, or a plant-independent status of discontinued. References: Material Type | SAP Help Portal, Material Master (LO-MD-MM) | SAP Help Portal, Document Types | SAP Help Portal, [Class Category | SAP Help Portal], [Status Management | SAP Help Portal]
NO.29 Why would you use phantom assemblies? Note: There are 3 correct answers to this question.
Phantom assemblies are assemblies that have their own product structure, but whose assembly does not actually physically exist. The components of the phantom assembly are incorporated directly in the superordinate product. The product structure of the superordinate product contains a reference to the phantom assembly. You can use phantom assemblies for the following purposes: To simplify the structure of bills of material: Phantom assemblies allow you to group components that belong together logically or functionally, without creating an additional level in the product structure. This can make the product structure easier to maintain and understand. To reduce the number of material masters: Phantom assemblies do not require a material master record in SAP S/4HANA, as they are not physically produced or stored. This can save storage space and reduce the effort of creating and updating material masters. To reduce the number of changes required in bills of material: Phantom assemblies can be used to represent common subassemblies that are used in multiple products. This way, you only need to maintain the product structure of the phantom assembly once, and any changes will be reflected in all the products that reference it. Phantom assemblies do not increase the number of planning levels, as they are not considered as separate planning objects. They also do not make the assignment of components easier, as the components are assigned to the superordinate product, not to the phantom assembly. References: Phantom Assembly | SAP Help Portal, Phantom Assembly | SAP Help Portal, Planning Phantom Assemblies | SAP Help Portal.
NO.32 What will happen in the MRP run if you have created a new MRP-relevant material that supports both in-house production and external procurement?
If you have created a new MRP-relevant material that supports both in-house production and external procurement, you need to specify the procurement type for the material in the material master record. The procurement type determines how the material is procured, either in-house, externally, or both. If you do not specify the procurement type, the MRP run does not consider the material, and it has to be planned interactively using the MRP Live app or the MD04 transaction. In interactive planning, you can manually assign a procurement type to the material and create the corresponding order proposals, such as planned orders or purchase requisitions. Alternatively, you can maintain a production version for the material, which defines the procurement type and the BOM and routing to be used for in-house production or external procurement. The production version can be assigned to the material in the material master record or in the MRP Live app or the MD04 transaction. The production version allows the MRP run to plan the material automatically based on the specified procurement type123. References: Procurement Type | SAP Help Portal, Production Version | SAP Help Portal, Material Requirements Planning with SAP S/4HANA, page 79-80.
NO.34 You want to insert an operation at a certain time on a work center in the graphical planning table. The planning direction is forward. The planning direction is forward. The desired dispatching time coincides with an operation that has previously been dispatched, how does the insertion take place?
The graphical planning table is a tool for capacity planning and scheduling that displays the operations and the work centers in a time-oriented view. You can use the graphical planning table to create, change, or dispatch operations manually or automatically. The planning direction determines whether the operations are scheduled from the start date or the finish date of the order. If the planning direction is forward, the operations are scheduled from the start date of the order1. If you want to insert an operation at a certain time on a work center in the graphical planning table, and the planning direction is forward, and the desired dispatching time coincides with an operation that has previously been dispatched, the insertion takes place as follows: The new operation is inserted at the desired time; the previously dispatched operation is moved backward (B): This is the correct answer. The system inserts the new operation at the specified time and shifts the previously dispatched operation to a later time, so that the sequence and the capacity requirements of the operations are maintained. The system also adjusts the start and finish dates of the order and the subsequent operations accordingly2. The other options are not correct for the following reasons: The new operation is inserted at the desired time; the previous dispatched operation is moved forward (A): This is not correct. The system does not move the previously dispatched operation to an earlier time, as this would violate the planning direction and the capacity constraints of the work center. The system only moves the previously dispatched operation to a later time, as explained in option B. The previously dispatched operation stays as is; the new operation is inserted after the dispatched operation : This is not correct. The system does not insert the new operation after the previously dispatched operation, as this would not match the desired dispatching time specified by the user. The system inserts the new operation at the desired time and moves the previously dispatched operation backward, as explained in option B. The previously dispatched operation stays as is; the new operation is inserted before the dispatched operation (D): This is not correct. The system does not insert the new operation before the previously dispatched operation, as this would violate the planning direction and the capacity constraints of the work center. The system inserts the new operation at the desired time and moves the previously dispatched operation backward, as explained in option B. References:
Recent Comments