Interaction Between Organizational Units
You can use this function to model how organizational units interact with each other, for example, how a sales organization interacts with a planning and execution organization. This interaction is especially important if you have to transport certain goods in a specific transportation stage, for example, dangerous goods.
Features
The sales organization is responsible for entering the order, for example, but is not allowed to create freight bookings for specific transportation stages or send them to a carrier. It can therefore propose how to transport the goods (by specifying a route and a schedule, and assigning a freight order or a freight booking) and sets the organization interaction status to transfer the affected stages to the planning and execution organization to be checked. The planning and execution organization checks the proposal and the transportation stage details in the transportation cockpit. It can then confirm the data exactly as proposed in the forwarding order, change data such as the departure and then confirm the proposal, or reject the proposal outright. The status for the stage in the forwarding order then changes to Confirmed
, Confirmed with Deviations
, or Rejected
respectively.
Note
The functions for confirming or rejecting proposals are not displayed as standard, and so the planning and execution organization must first select an appropriate layout set in the transportation cockpit. For more information, see Use of Profile and Layout Sets.
The planning and execution organization can also create a freight booking or a freight order for the transportation stage in the transportation cockpit, or assign the transportation stage to a document that already exists. In this case, the system sets the organization interaction status automatically from To Be Checked
to Confirmed
. The sales organization can then confirm the transportation stages with the ordering party.
Furthermore, the planning and execution organization can select an existing freight booking in addition to the route and schedule and confirm the details for the carrier.
Even if a stage has already been confirmed, the sales organization can still make changes to the order. In this case, the system sets the status of the stage to Changed After Confirmation
.
If the planning and execution organization rejects a stage, the sales organization can submit a new proposal by changing the status of the stage back to To Be Checked
.
Note
If the planning and execution organization rejects unconfirmed stages that are assigned to a freight booking via an auto-confirmation profile these unconfirmed stages are automatically unplanned.
If the sales organization wants to cancel a stage, this must also be approved by the planning and execution organization. The sales organization therefore sets the status of the relevant stage in the forwarding order to Cancellation Requested
. In the transportation cockpit, the planning and execution organization chooses Confirm
for the stage and the status in the forwarding order subsequently changes to Cancellation Approved
.
The sales organization can also remove the default route from a stage in the forwarding order by selecting the stage and choosing 
Schedule
Unassign
.
If the sales organization wants to delete the stages of the default route from the actual route, it can do so by selecting one of the relevant stages and choosing Delete Stage
. The system then replaces the stages containing the default route by the original stages.
Automatically Setting the Organization Interaction Status
The sales organization can set the organization interaction status manually from Confirmed
or Rejected
to To Be Checked
, Not Yet Requested
, or Cancellation Requested
.
You define criteria for automatic confirmation in a profile, which the system determines based on the freight booking type. These criteria can include, for example, the security status, volume, or weight. If a transportation stage meets the criteria defined in the profile, the stage can be confirmed automatically (for example, if the volume and weight defined in the profile are less than the volume and weight defined in the transportation stage).
You can use the Business Add-In BAdI: Change Organization Interaction Status
(/SCMTMS/TOR_ORG_INT_STATUS)
to control the following cases:
A transportation stage can be confirmed automatically (that is, the organization interaction status is set automatically from
To Be Checked
toConfirmed
), such as when the forwarding order does not contain any dangerous goods.A confirmed transportation stage must be rechecked (that is, the organization interaction status is set automatically from
Confirmed
orRejected
toTo Be Checked
), for example, when quantities are changed.
Aggregated Organization Interaction Status
The Statuses
tab page of the forwarding order shows the aggregated organization interaction status of the forwarding order. This is an overall status that is based on the statuses of the individual stages.
If all of the stages have the same status, this status is shown as the aggregated organization interaction status (unless all stages have the status Confirmed with Deviations
, in which case the aggregated organization interaction status is set to Confirmed
). If all of the stages have a status that is either To Be Checked
or Changed After Confirmation
, the aggregated organization interaction status is set to Changed After Confirmation
.
In cases where the status of one stage differs from all of the others, the system sets the aggregated organization interaction status based on the following rules, which it applies in the sequence specified:
Sequence | Status of at Least One Stage | Aggregated Status |
|---|---|---|
1 | Cancellation Approved | Cancellation Partially Approved |
2 | Cancellation Requested | Cancellation Partially Requested |
3 | Rejected | Partially Rejected |
4 | Confirmed | Partially Confirmed |
5 | Confirmed with Deviations | Partially Confirmed |
6 | Changed After Confirmation | Changed After Confirmation |
7 | To Be Checked | To Be Checked |
8 | Not Yet Requested | Not Yet Requested |