Direct answer

Business partners in SAP Transportation Management identify organisations and people participating in freight processes. General partner information is extended through relevant roles and partner functions. A carrier may execute freight, a shipper or customer requests a service, and supplier and finance extensions may support freight procurement and settlement. These responsibilities are distinct even when one company holds several roles.

A transport planner and purchasing colleague review a carrier assignment before dispatch.
A transport planner and purchasing colleague review a carrier assignment before dispatch.

One organisation, several business responsibilities

The general business partner holds shared identity information such as legal name and address. Role-specific extensions support operational and financial functions. SAP Learning explains that a carrier role makes a partner usable as a carrier in transportation work, while supplier and financial roles can be important for purchasing and payment.

The same logistics provider may appear in transport planning and Accounts Payable. Duplicate records or missing organisational assignments can cause disputes even when a freight route looks correct.

Why role is not the same as the partner on a document

The master-data role describes what a partner may do; a document partner function says which party is responsible in a given shipment. A contractual carrier, executing carrier, communication party and freight invoice recipient may differ.

Transport-specific identifiers such as SCACs or airline codes may be relevant depending on freight mode and product. Do not assume that all modes share identical mandatory attributes.

A responsibility map linking shipper, carrier, supplier and financial settlement roles.
A responsibility map linking shipper, carrier, supplier and financial settlement roles.

Example: a regional carrier contract

A manufacturer books 18 pallets from its plant to a distribution centre. The business owns the delivery need. An approved carrier accepts the planned movement, and a relevant freight agreement supports charge calculation. Operational milestone updates and settlement must reference the correct parties.

A carrier can have the right address but lack a required carrier or supplier extension; such a record may work for one step yet fail downstream. That is a master-data process problem, not necessarily a route-optimisation defect.

Consultant thinking and controls

Check carrier eligibility, relevant business partner roles, purchasing organisation, company-code finance extension, freight agreement and communication contact. Ensure changes to bank or legal identity fields receive the appropriate approval.

In troubleshooting, locate the failed responsibility: selection, tendering, execution message, charge agreement or supplier payment. Avoid treating every transport failure as a system integration issue.

Review checklist

  • Verify the carrier role and party functions required by the freight process.
  • Confirm purchasing and finance extensions for charge settlement.
  • Check contact routing, approved carriers and master-data stewardship.
  • Investigate missing responsibilities rather than duplicate partner identity records.

Related N2i Knowledge

Official SAP References

SAP Learning — Business Partners and Organizations · SAP Learning — Business Partners in TM · SAP Help — Carrier Categorization