Show TOC

Integration of SCM and ERP 2 Locate this document in the navigation structure

 

Technical Data

Technical name of the business function

SCM_GEN_02

Type of Business Function

Enterprise Business Function

Available as of

SAP ERP 6.0 Enhancement Package 3

ECC software component

SAP_APPL

ECC application component

CA

Business Intelligence content

Not relevant

SAP Enterprise Services

Not relevant

JAVA software component

Not relevant

Portal content

N/A

Additional content available in other SAP applications

As of SAP SCM 2007

Business function requiring activation in addition

SCM_GEN_01

As of SAP ECC 6.0 Enhancement Package 3, the business function Integration of SCM and ERP 2 (SCM_GEN_02) is available. You can use this business function for enhancements in the following areas:

  • Shelf Life

  • Subcontracting

  • Interchangeability

Prerequisites

To be able to use the business function, you must be using SAP SCM 2007.

Features

Shelf Live

Consideration of Shelf Life Data

The following data is transferred between SAP ERP and SAP SCM:

  • Remaining shelf life data of purchase requisitions and purchase orders is transferred from SAP ERP to SAP SCM.

  • Remaining shelf life data of SNP stock transfers (with or without source location) is transferred from Supply Network Planning (SNP) to SAP ERP.

Minimum Remaining Shelf Life in Batch Determination from Stock Transport Order

The required minimum remaining shelf life from the stock transport order is taken into account in batch determination in the goods issue posting.

When recording a goods issue against a stock transport order, you can carry out a batch determination process. In this process, the system searches for batches with certain characteristic values, such as minimum shelf life or status, according to a search schema. You can predefine the search schema and the characteristic values according to which you want to search for the batches. As of this release, the required minimum remaining shelf life and the planned delivery time from the stock transport order are taken into account in the batch determination process.

Minimum Remaining Shelf Life in Purchase Requisition and Purchase Order

You can display and change the minimum remaining shelf life in the requisition and purchase order. The minimum remaining shelf life is adopted in the PO item when a purchase order is created from a requisition.

The minimum remaining shelf life in the purchase requisition can be populated from a source of supply (i.e. contract or info record), the material master, or with data from SAP SCM. Previously, the minimum remaining shelf life in the purchase order was adopted from the following documents and master data in the following order: reference document, RFQ, contract, info record, material master record.

Now the system adopts the minimum remaining shelf life from the purchase requisition. If no minimum remaining shelf life has been defined in the requisition, it is determined from the aforementioned documents and master data.

Effects on Customizing

Furthermore, you can specify in Customizing for Purchasing via the field selection for the purchase requisition (Define Screen Layout at Document Level) whether the field is to be shown or hidden and whether its contents can be changed in the Enjoy transactions. If the minimum remaining shelf life differs from that in the assigned purchase requisition, you can have a message issued in the purchase order (Define Attributes of System Messages).

Subcontracting

Assignment of Multiple Production Versions in SAP ERP

The subcontracting process has been enhanced. You can now assign multiple production versions to a subcontracting purchase info record in SAP ERP. To do the assignment, in SAP ERP, choose Logistics -> Central Functions -> Supply Chain Planning Interface -> Core Interface Advanced Planner and Optimizer -> Environment -> Data Transfer -> Assign Multiple Production Versions.

You can also define whether purchase info records, to which multiple production versions are assigned, are transferred from SAP ERP to SAP APO.

For more information, see the Implementation Guide (IMG) for SAP ERP under Integration with Other SAP Components -> Advanced Planning and Optimization -> Basic Settings for Data Transfer -> Change Transfer -> Change Transfer for Master Data -> Configure Change Transfer for Master Data.

You can also mark individual production versions as invalid in cases where a purchase info record has multiple production versions assigned to it. As part of the initial data transfer to SAP APO, SAP ERP transfers only those production versions that are valid. To mark production versions as invalid, you have two options:

  • You can manually define this by setting the Production Version Invalid indicator for the relevant production version. To do so, in SAP ERP, choose Logistics -> Central Functions -> Supply Chain Planning Interface -> Core Interface Advanced Planner and Optimizer -> Environment -> Data Transfer -> Assign Multiple Production Versions.

  • You can use the report SET_PRODVER_VALIDITY to have the system automatically check whether production versions are valid in the background.

    You have two options when you use the check report:

    - Set not valid entries

    If you choose this option, the invalid production versions are simply marked by the system and are not transferred to SAP APO as part of the initial data transfer. This is the default setting.

    - Delete invalid entries

    If you choose this option, the invalid production versions are automatically deleted by the system.

Multiple Sources of Supply for Subcontracting

Previously in a subcontracting scenario, Supply Network Planning (SNP) and Capable-to-Match (CTM) could only consider one source of supply for each subcontracting location. The reason for this was that in SAP ERP, you could only assign one production version to a purchasing info record. You could then only convert this production version to one production process model (PPM via a PP/DS PPM) or one production data structure (PDS) when transferring data to SAP SCM.

As of SAP SCM 5.1, you can assign multiple production versions to a purchasing info record in SAP ERP. You make this assignment in the SAP ERP system using a new transaction: Logistics -> Central Functions -> Supply Chain Planning Interface -> Core Interface Advanced Planner and Optimizer -> Environment -> Data Transfer -> Assign Multiple Production Versions. After converting the production versions to PPMs or PDS, multiple sources of supply are available for each subcontracting location in the SCM system.

In interactive SNP planning, you can determine the sources of supply as follows:

  • For an SNP stock transfer of type Subcontracting, you can choose an alternative source of supply from a proposal list in the planning table.

  • You can change the source of supply for a planned order in the detail view. SNP and CTM planning runs choose the sources of supply according to the rules for determining source of supply that are in place (for example, on the basis of procurement priority or cost).

Interchangeability

Integration of Interchangeability Master Data from SAP ERP

Interchangeability master data can now be transferred from SAP ERP to SAP SCM.