To achieve and maintain clean core data quality in an SAP S/4HANA Cloud Greenfield project, the focus should be on the following aspects:

Accuracy (B): Ensures that the data in the system is correct and precise, minimizing errors and reducing inconsistencies in master and transactional data. Accurate data is critical for reliable analytics, reporting, and operational efficiency.

Timeliness (D): Ensures that data is current and available when needed. This is vital in a cloud environment where real-time decision-making is essential.

The other options—Stability (A)andEfficiency (C)—while important in broader project considerations, do not directly contribute to clean core data quality management.

Alerts provided within the Supply Chain Monitor include:

B. Planned shipment alerts: Notifications related to planned shipments.

D. Order confirmation alerts: Highlights issues or confirmations with purchase orders.

E. Forecast alerts: Relays updates about forecasted requirements.

Incorrect Options:

A. Advance ship notice alerts: Not provided as a standard alert.

C. Inventory alerts: Managed in inventory-specific dashboards, not Supply Chain Monitor.

Refer to:Supply Chain Monitor Alerts

In a consignment scenario, the ownership of goods changes in the following events:

Consignment stock is consumed by the customer (C): Ownership transfers when the customer consumes or uses the consignment stock.

Posting from consignment stock to the buyer's own stock (D): Ownership transfers when the consignment stock is moved to the buyer’s own stock.

The other options are not events that directly affect ownership transfer:

Invoice from the customer is received by supplier (A): Invoicing does not change ownership but acknowledges the financial transaction.

Goods receipt for consignment stock is posted (B): Posting the receipt confirms the stock availability but does not affect ownership.

Certain Supply Chain Collaboration modules in SAP Business Network are considered Add-Ons, requiring separate implementation or subscription:

Quality Collaboration- Facilitates communication between buyers and suppliers regarding quality inspections and issue resolutions.

Supplier Managed Inventory- Allows suppliers to monitor and manage inventory levels at buyer locations.

These modules extend the functionality of the core platform.

References: SAP Business Network -> Add-On Modules Documentation.

The Individual Data Planning screen in the Supplier Managed Inventory (SMI) module of SAP Business Network allows sellers to enter the following quantities:

Net requirements quantity- Reflecting the quantity required by the buyer after considering available inventory.

Planned shipment quantity- Detailing quantities the seller plans to ship to meet the buyer’s requirements.

These inputs enable streamlined collaboration and efficient inventory management.

References: SAP Business Network -> SMI Individual Data Planning User Guide.

The following PO tolerances can trigger an order confirmation approval:

B. Quantity: Differences in ordered vs. confirmed quantities.

C. Price: Variations in pricing between the PO and confirmation.

D. Date: Mismatches in delivery dates.

Incorrect Options:

A. Supplier part ID: Not typically associated with approval triggers.

E. Batch: Not relevant for standard PO tolerance checks.

Refer to:PO Tolerance Triggers

When a Buyer receives a Confirmation alert from the Supply Chain Monitor, they can take the following actions:

A. Approve Only: Approve the confirmation without changes.

C. Reject: Decline the confirmation entirely.

E. Reject and Update: Reject the confirmation while providing updates to the supplier.

Incorrect Options:

B. Confirm: Not an available option for this process.

D. Approve and Update: This is not a standard choice in confirmation alerts.

Refer to:Supply Chain Monitor Alert Actions

SAP Business Network Business Transaction Rules can be maintained at the following levels:

Default level (B): Applies rules that are universally applicable across all transactions unless overridden by more specific settings.

Supplier level (C): Allows configuration of rules specific to individual suppliers, catering to unique requirements or contractual agreements.

Supplier group level (E): Enables the grouping of suppliers and the application of common transaction rules to all members of the group.

The optionsCountry-based invoicing level (A)andBuyer group level (D)are not recognized levels for maintaining business transaction rules in SAP Business Network.

The following items are recorded on an Inspection Lot in SAP Business Network:

C. Usage Decision: This captures the final decision made regarding the inspected goods, such as acceptance or rejection.

D. Inspection Results: Detailed results of the inspection process, including recorded measurements or qualitative evaluations.

Incorrect Options:

A. Customer Complaint: This is managed through Quality Notifications, not Inspection Lots.

B. Quality Task: Tasks are associated with quality notifications and corrective actions.

For further details, refer to SAP's documentation:Inspection Lot Overview

The key features of Consignment Collaboration in SAP Business Network include:

Buyers can create self-billing invoices for consignment movements (B)- Automates the billing process based on goods consumption.

Suppliers can view consignment material stock (C)- Provides visibility into consignment stock levels at buyer locations.

Suppliers can create a debit memo (D)- Allows suppliers to document adjustments and claim compensation for goods consumed.

References: SAP Business Network -> Consignment Collaboration Features Guide.

In SAP Business Network Supply Chain Collaboration, forecast data from the ERP system can originate from various sources. Among the options provided, the correct sources are:

A. Planned order: Planned orders represent anticipated production or procurement activities and serve as a basis for forecasting demand.

D. Planned independent requirement: These are forecasts of demand for finished products or components, independent of actual sales orders, and are crucial for planning purposes.

The other options are not considered sources of forecast data:

B. Production Order: This is an actual order to produce a specific quantity of a product and reflects confirmed production activities rather than forecasted data.

C. Purchase requisition: This is a request for the procurement of materials or services and indicates immediate procurement needs, not forecasted demand.

Therefore, the correct answers areA. Planned orderandD. Planned independent requirement.

For more information, refer to SAP's documentation on differentiating between planning sources in ERP systems: