multilevel available to promise (mlatp) with rules · pdf filemultilevel available to promise...
TRANSCRIPT
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 1
Multilevel Available To Promise
(MLATP) with Rules-Based
Component Substitution
Applies to:
SCM 5.0 / SCM 7.0. For more information, visit the Supply Chain Management homepage.
Summary
Multilevel Available To Promise (MLATP) is used in high tech industries where availability is checked at component level. This white paper explains configuration details of MLATP and Rules based substitution of components. The ATP structure is formed incase of component shortage and receipt element is created once conversion of ATP Tree structure into PPDS Planned order takes place.
Author: Pavan Verma
Company: Netage Systems
Created on: 31 December 2009
Author Bio
Pavan Verma has 10 years of experience in SAP and has worked in field of GATP, SNP and SD. Pavan is presently working with Netage systems Inc. as Senior SCM Solution Architect
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
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 ......................................................................................................................................................... 3
Scenario .......................................................................................................................................................... 3 Master Data ................................................................................................................................................................. 3
Configuration ................................................................................................................................................................ 5
Steps .......................................................................................................................................................................... 14
Related Content ................................................................................................................................................ 21
Disclaimer and Liability Notice .......................................................................................................................... 22
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 3
Introduction
This white paper explains process of Multilevel ATP and component substitution in MLATP.MLATP is generally used in High Tech industries where final assembly is only initiated when sales order is entered. The component availability check is done in the sales order and BOM is exploded within ATP check. The sales order line item is confirmed only when components are available. The ATP check triggers creation of ATP Tree structure and receipt elements are generated when ATP Tree structure is converted into PPDS Planned order. MLATP supports following:
Scope of check in the product availability check
Check against forecast
Rules-based ATP check (product substitution and location determination at component level)
Scenario
We have a End Product (SKU) PL200. PL200 is made up of COMP4 (Component). Primary Component COMP4 can be substituted by COMP3. There is no stock for PL200. Primary Component COMP4 has stock of 500 pcs and alternate component COMP3 has 500 pcs.
Master Data
We need Material Master for SKU, Components, BOM, Routing, Work center, Production Version, Integration Models.
BOM of PL200
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 4
A valid Production Version with Routing in ECC
SCM Data
A valid PPDS –PDS in SCM
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 5
Configuration
Required Configuration in ECC is Strategy of component. This will be assigned to components COMP4 and COMP3
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 6
Strategy of SKU or Header material, this will be assigned to SKU PL200
Requirement Type of SKU
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 7
Requirement Class of Component
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 8
Requirement class of SKU PL200
Configuration in SCM
Check Instructions in SCM for SKU
T code /SAPAPO/ATPC07
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 9
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 10
Check Instructions for Component
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 11
Configuration for Rules for Component substitution
1. Create Table 910 : two fields MATNR and RULE_MATNR
2. Create access sequence ZML1 and assign table 910 to it.
3. Create Condition type ZCM1 and assign access sequence ZML1 to it.
4. Create Rule Strategy ZMLCOM and assign condition type ZCM1 to strategy.
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 12
5. Create Rule 1MLATPNOLM Using T code /SAPAPO/RBA04 with product substitution procedure 4COMP
Product substitution procedure 4COMP has two products COMP4, COMP3 . Component COMP4 is substituted by COMP3
Assign the Rule to SKU and to primary component using T code /SAPCND/AO11
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 13
Rule for Component:
Transaction data in SCM
No Stock for SKU PL200 ( T code /SAPAPO/RRP3)
Primary Component has 500 pcs
Alternate component COMP3 also has 500 pcs
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 14
Steps
ECC: Create sales order for SKU (PL200) of 500 pcs
Primary component COMP4 has stock of 500 pcs. BOM will be exploded in the Availability check and sales order line item will be confirmed for the SKU PL200
Confirmation for the SKU
In SCM
Using /SAPAPO/RRP_ATP2PPDS Conversion ATP Tree Structures -> Production Planning
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 15
This can be done in background also using T code /SAPAPO/ATP2PPDS
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 16
After conversion of ATP Tree structure into PPDS Planned order
Now we can see Planned order for PL200
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 17
And Dependent demand of 500 pcs for Component COMP4
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 18
Scenario 2: Demand for 510 pcs of SKU PL200
Primary component COMP4 has 500 pcs available , alternate component COMP3 has 500 pcs available
Now MLATP will trigger component substitution
After saving the sales order and converting the ATP Tree structure into Planned order, there will be a dependent demand of 500 pcs for COMP4 and dependent demand of 10 pcs for COMP3
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 19
Component COMP3 ( T code /SAPAPO/RRP3)
In ECC : The Planned order is also visible
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 20
This Planned order can be converted into Production order in SCM. The Production order is now visible in ECC.
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 21
Related Content
http://help.sap.com/saphelp_scm50/helpdata/EN/05/7e1f3bc779144ae10000000a114084/content.htm
http://help.sap.com/saphelp_scm50/helpdata/EN/82/b557a4431cd511bcbe0800060d9c68/content.htm
http://help.sap.com/saphelp_scm50/helpdata/en/a4/f7423b1fea840ce10000000a11402f/content.htm
For more information, visit the Supply Chain Management homepage.
Multilevel Available To Promise (MLATP) with Rules-Based Component Substitution
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2010 SAP AG 22
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 or code 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.