Comparison of Sales Scheduling Agreements The comparison of sales scheduling agreement data is carried out on the basis of schedule lines.
In other words, sales scheduling agreement items for which schedule lines do not exist in SAP APO or SAP R/3 are not taken into account in the compare/reconcile function.
The report specifies the total number of schedule lines checked on the
Results
tab page.
Note
You should note that schedule lines on tab pages subordinate to the
Sales Scheduling Agreement
tab page (for example on the
Receipts/Requirements
or
Differences in Content
tab pages) may be displayed more than once.
This is the case if you have set in the control profile that you want to work with operative delivery schedules and forecast/planning delivery schedules in SAP APO. For this reason, both a JIT delivery schedule and a forecast delivery schedule are created when scheduling agreement schedule lines are sent from SAP APO to SAP R/3.
Because the sales scheduling agreement data is formatted in the same way as it is sent to SAP R/3 it may seem as if some scheduling agreement schedule lines are displayed twice.
Recommendation
To compare requirements with sales scheduling agreements that have been created in SAP R/3 and transferred in the integration model with the object type
Sales Orders,
you must select
Sales Orders
on the initial screen of the Compare/Reconcile function.
The comparison of sales scheduling agreements is only possible as of SAP R/3 Enterprise Core 4.70with Plug-In PI 2003.1or DIMP 4.71 with Plug-In PI 2003.1 and higher.
For more information, see Release Management for Sales Scheduling Agreements .
The compare/reconcile function checks Sales-or SD scheduling agreementsin SAP APO and SAP R/3 for the following inconsistencies:
| Inconsistency | The order only exists in one system |
| Possible Manifestation of Inconsistency | Possible Cause and Solution |
The sales scheduling agreement item is missing in SAP APO. |
Incorrect transfer of the sales scheduling agreement item even though it is contained in an active integration model.
|
The sales scheduling agreement item is missing in SAP R/3. |
The item may have been created in SAP R/3 and transferred to SAP APO The item was deleted in SAP R/3 at a later time (and before follow-on documents existed).
|
| Inconsistency | The order exists in SAP APO, but it is not contained in an active integration model . |
| Possible Manifestation of Inconsistency | Possible Cause and Solution |
The sales scheduling agreement is not contained in an active integration model. |
The sales scheduling agreement item may have been transferred from SAP R/3 to SAP APO and the integration model may then have been deactivated.
|
| Inconsistency | The order has differences in content . |
| Possible Manifestation of Inconsistency | Possible Cause and Solution |
The following data is checked:
|
Changes to the data were not transferred correctly to the other system.
|
|
|
Cumulative quantities:
|
|
Correction quantities:
|
|
Prerequisites: It only makes sense to use the comparison if you use cross-system update logic. See Cross-system Update Logic and Cross-system Update Logic for Sales Scheduling Agreements You can use the Business Add-In (BAdI) /SAPAPO/CIF_DELTA3 to define that the update counter is checked when the comparison takes place. |
The sales scheduling agreement item has a different Update Counterin SAP APO than in SAP R/3.
You have the following options:
|
| Inconsistency | The order contains requirements (or receipts) with errors . |
| Possible Manifestation of Inconsistency | Possible Cause and Solution |
Schedule lines for the sales scheduling agreement item are missing in SAP APO or in SAP R/3. |
Changes to the schedule lines were not transferred to SAP R/3 correctly.
|
Schedule lines for the sales scheduling agreement item are missing in SAP APO. |
This can occur for any of the following reasons:
If the measures described above do not remove the inconsistency then you have the following options:
|