Transfer of MSP Data from SAP SCM to SAP ERP
You can transfer the maintenance and service planning data from SAP SCM to SAP ERP for use with the Maintenance Event Builder
(MEB) component of the SAP for Aerospace & Defense (SAP for A&D) solution. You perform long-term or mid-term planning in SAP SCM
and transfer the planning results to SAP ERP for short-term planning purposes. For more information about the MEB, see Work Packaging and Sequencing
in the SAP Library for SAP for A&D.
Note
Transfer of MSP data is similar to transfer of other SAP SCM data. However, some differences do exist. Therefore, you should use this documentation together with the standard SAP SCM documentation to ensure that you have a complete overview of data transfer between SAP SCM and SAP ERP.
You cannot transfer planning data that contains maintenance objects without external reference or maintenance objects that have been created in Easy Simulation
. Furthermore,
you cannot transfer planning data that contains service areas that have been created in SAP SCM, but have not been created as proxy service areas.
Prerequisites
The technical integration between SAP SCM and SAP ERP (a Discrete Industries system from release 4.71) has been configured. For more information, see Integration of SAP SCM and SAP R/3 (especially Technical Integration and System Infrastructure).
Activities in SAP SCM
SAP SCM transfers the planning results periodically.
You start the processing of change pointers manually, or schedule this to take place as background processing.
SAP SCM deletes the change pointers once they have been processed.
For more information, see Transferring MSP Data to SAP R/3.
SAP SCM issues a log indicating whether the transfer has been successful or whether any items were deleted from the transfer.
CautionSome work packages are dependent on others, therefore SAP SCM may actually transfer more planning data than you have selected, that is it may also transfer the predecessors of the selected work package slots.
SAP SCM may also stop the transfer of a particular work package, if it contains a slot with a dependency on an unplanned predecessor.
End of the caution.
Activities in SAP ERP
On successful transfer of the data from SAP SCM, the newly generated slot arrives in SAP ERP.
The slot generates a revision with an identical number and the revision type as defined in Customizing for
Maintenance and Service Planning
in SAP ERP. For more information, see Preparatory Activities.For every maintenance demand in the slot:
If the maintenance demand belongs to a schedule call with a notification, SAP ERP assigns the notification to the revision in the
Maintenance Event Builder
(MEB) component. For more information about the MEB, seeWork Packaging and Sequencing
in the SAP Library for SAP for A&D.If the maintenance demand belongs to a schedule call without a notification, SAP ERP does not automatically assign the notification to the revision when it is created. This has to be done manually by the MEB User. Therefore, we recommend that the planning horizons are defined in such a way that the corresponding notification is generated before the revision is generated by the transfer of the slot from MSP.
CautionYou cannot transfer planning data back to SAP SCM, even if it changes in SAP ERP.
If you attempt to transfer changed planning data that has previously been transferred to SAP ERP and for which the revision is now completed in SAP ERP, SAP SCM terminates the transfer. Therefore, we recommend you do not transfer changed planning data from SAP SCM once a revision has been completed in SAP ERP.
End of the caution.