Upload
doubledeed1
View
232
Download
1
Embed Size (px)
Citation preview
8/22/2019 SCM deployment
1/12
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 1
SCM7.0 PPDS: Cross PlantDeployment (New Functionality)
Applies to:
Supply Chain Management. For more information, visit theSupply Chain Management homepage.
Summary
This article explains the steps to be followed to achieve the PPDS Cross plant deployment functionality
Author: Mahesh Babu MG
Company: SAP Labs India Pvt., Ltd.
Created on: 14 May 2010
Author Bio
The author is a Principal Consultant in SAP Labs India Pvt., Ltd. with expertise in SCM APO- PPDS & CIF.
https://www.sdn.sap.com/irj/sdn/bpx-scmhttps://www.sdn.sap.com/irj/sdn/bpx-scmhttps://www.sdn.sap.com/irj/sdn/bpx-scmhttps://www.sdn.sap.com/irj/sdn/bpx-scm8/22/2019 SCM deployment
2/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 2
Table of Contents
Introduction ................................................................................................................................................... 3Steps to be followed ........................ ......................... ........................ .......................... ........................... ........ 3
Prerequisites ............................................................................................................................................. 3Scenario Explained .......................... .......................... ........................ ......................... ........................... .... 3Customizing settings.................................................................................................................................. 3
Maintain PPDS Deployment characteristics profile ...................................................................................................... 3Master data settings .................................................................................................................................. 4Process ..................................................................................................................................................... 5
Overview...................................................................................................................................................................... 5Heuristics ..................................................................................................................................................................... 8Results......................................................................................................................................................................... 8Deployment without characteristics.............................................................................................................................. 9
Related content ........................... ......................... ......................... ......................... .......................... ........... 11Copyright ....................................................................................................... Error! Bookmark not defined.
8/22/2019 SCM deployment
3/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 3
Introduction
In SCM7.0 this new functionality (PPDS Deployment) is introduced, this is specifically meant to beused in characteristics based planning, but can also work in environments without the usage ofcharacteristics.
PPDS Deployment works similar to the SNP deployment and has some limitations compared to theSNP deployment.But, as mentioned earlier the main advantage of this functionality is that, the newheuristics can consider the characteristics values of the receipt, requirement elements for allocating
the quantity.
Steps to be followed
Prerequisites
1. The planning area 9ASNP_PPDS needs to be initialized for the corresponding planning version.
2. In PPDS Global settings the ATP category assignments to be done in the following way:
Receipt Stock Transfer Cnf: EF Deployment: Purchase requisition
Requirement Stock Transfer Cnf: EG Deployment: Release for stk transf.
3. Note 1465801 to be implemented for releases till SAPKY70007.
Scenario Explained
There are demands for a product from 2 locations to a source location (production plant) with differentcharacteristic values and the PPDS Deployment heuristics should take care of the characteristic values andallocate the quantities to the demand elements(deployment orders) according to the fair share rule.
Customizing settings
Maintain PPDS Deployment characteristics profile
Here, create a profile and assign the characteristics, based on which the deployment should happen
8/22/2019 SCM deployment
4/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 4
Master data settings
Product created and classified in R/3 and CIFed to APO.
This CLASS MG_PPDSDEPL contains the characteristics MG_LENGTH and MG_WIDTH
In PPDS tab assign the Characteristics profile, Fare share rule (only A and X supported) and the deploymenthorizons.
8/22/2019 SCM deployment
5/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 5
Process
Heuristics SAP_DEPL_SNG, SAP_DEPL_MUL are introduced in SCM7.0 for achieving this functionality
Overview
Product MG_PPDS_DEPL_RAW@E4A000
Location PL0001@E4A000
Element: Planned order
Product MG_PPDS_DEPL_RAW@E4A000
Location PLMGM1@E4A000
Element: Purc. Reqn
Product MG_PPDS_DEPL_RAW@E4A000
Location PLMGM2@E4A000
Element: Purc. Reqn
DemandsDemands
Deploys
8/22/2019 SCM deployment
6/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 6
Product MG_PPDS_DEPL_RAW@E4A000 at location PLMGM1@E4A000 has a purchase requisition with the followingcharacteristic values
Product MG_PPDS_DEPL_RAW@E4A000 at location PLMGM2@E4A000 has a purchase requisition with the followingcharacteristic values
And in the source location PL0001@E4ACLNT000 there are 2 planned orders with the following char values
8/22/2019 SCM deployment
7/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 7
So, the expectation is that,
Planned order 779272 will be deployed for quantity 50 to the PReqRel 779270 as the characteristic value forthe MG_LENGTH is matching (value: 100)
Demand Elements fromthe target locations
8/22/2019 SCM deployment
8/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 8
And, the planned order 779273 will be deployed for quantity 50 to the PReqRel 779271 as the characteristicvalue for the LENGTH is matching (value: 200)
Also, note that the value for the characteristic Width is irrelevant here, because Width is not part of thedeployment characteristics profile.
Heuristics
Heuristics profile SAP_CBCLP is available in SCM7.0 for executing the new heuristics from PPDS planningtools.
In product view of the Source location execute the SAP_DEPL_SNG from the variable heuristics option
Results
After heuristics the following is the status,
8/22/2019 SCM deployment
9/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 9
After the heuristics only 50 quantity of each planned order is deployed against the requirements as per thematching characteristics values.
Deployment without characteristics
If the characteristics profile is removed from the product master the following will be result,
The deployment orders do not have the characteristics assignment and only one planned order (779350) isdeployed against the 2 requirements irrespective of the characteristics value.
8/22/2019 SCM deployment
10/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 10
8/22/2019 SCM deployment
11/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
2010 SAP AG 11
Related content
SDN:www.sdn.sap.com
SAP Help:www.help.sap.com
For more information, visit theSupply Chain Management homepage.
http://www.sdn.sap.com/http://www.sdn.sap.com/http://www.sdn.sap.com/http://www.help.sap.com/http://www.help.sap.com/http://www.help.sap.com/https://www.sdn.sap.com/irj/sdn/bpx-scmhttps://www.sdn.sap.com/irj/sdn/bpx-scmhttps://www.sdn.sap.com/irj/sdn/bpx-scmhttps://www.sdn.sap.com/irj/sdn/bpx-scmhttp://www.help.sap.com/http://www.sdn.sap.com/8/22/2019 SCM deployment
12/12
SCM7.0 PPDS: Cross Plant Deployment (New Functionality)
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.