All topics
MM_P2Pbeginner

Subcontracting

More overview details for this topic are coming soon.

Interview questions covered

  • How would you architect a subcontracting solution where the subcontractor also performs external services requiring service entry sheets, and components must be provided cross-company from a different legal entity?
  • What controls should be designed to prevent GR/IR imbalances when a PP subcontracting interface repeatedly fails to post goods receipts for components sent to a subcontractor?
  • A subcontracting vendor's special stock (movement type 541 issued components) shows a large unexplained variance versus the vendor's confirmed consumption at period close, and the GL account for subcontracting consumption is out of balance with the physical component stock at the vendor. How would you architect the root-cause investigation and remediation?
  • Walk through how source determination works for a subcontracting process in SAP MM, including how the subcontractor is selected and components are provided.
  • During Fit-to-Standard workshops for a P2P migration, the client's PP team insists on retaining a custom subcontracting reconciliation process built in ECC that has no standard equivalent in S/4HANA Public Cloud. How do you handle this in the fit-to-standard methodology and what integration risk must be flagged?
  • What is source determination in a subcontracting scenario, and how does it differ from source determination for standard stock or service procurement?
  • A global rollout wants to extend inbound delivery processing (currently used only for scheduling agreements with materials) to cover components supplied to a subcontractor performing external services, so goods receipt and FI-AP invoice matching align with a common document type architecture. What architectural considerations would you evaluate before extending inbound delivery to this scenario?
  • A client running S/4HANA Public Cloud with tight clean core governance discovers that a PP-integrated procurement scenario (subcontracting with component provisioning) needs custom logic that standard scope items don't cover. As architect, how do you evaluate whether this justifies an extension versus a process change, and what monitoring implications follow?
  • In a subcontracting scenario, a subcontract PO (item category L) posts goods issue of components automatically at goods receipt, but stock discrepancies are appearing between the subcontractor stock (special stock indicator O) and the component consumption. As the architect, what document type and configuration areas would you investigate?

Related topics