Scenario Control SNC Extension Guide

Transcription

1 Scenario Control SNC Extension Guide 1 ABOUT SCENARIO CONTROL DEFINE SCENARIO CONTROL KEYS (SCKS) ASSIGN SCKS TO LOCATION PRODUCTS PREPARE BADI TO UTILIZE SCKS IN SELECTION FURTHER INFO... 8 Version: 1.2 Date

2 The SNC Extension Guide is a collection of tips and tricks on how to extend SAP Supply Network Collaboration to meet your specific business requirements. It is based on SNC 7.0. Consultants, Developers and Solution Managers have worked together to build this content based on customer experiences. We invite you to actively participate in the content - share your experiences, comments and questions. Disclaimer: SAP is not liable for any discrepancies in the content or code in the documents. 1 About Scenario Control You can use Scenario Control to filter out those applications for which a location product is displayed on the SAP Supply Network Collaboration (SAP SNC) Web UI. Scenario Control is supported by all applications in SAP SNC that use the user-partner based visibility concept. That includes screens with selection modes PDNF, PDNF_NEW, ODM_xxx and MD. You cannot use Scenario Control for example with SNI screens, since it uses the profile-based visibility concept. For more details, see Visible Master and Transaction data on help.sap.com. SAP SNC 7.0 supports two applications (SMI and DCM) with 4 keys by default: Scenario Control Explanation Key (SCK) 0 The location product is displayed in the DCM and in the SMI Monitor. The system creates alerts for the location product for both stock on hand and projected stock. 1 The location product is only displayed in the SMI Monitor. The system creates alerts for the location product only for projected stock. 2 The location product is only displayed in the DCM. The system creates alerts for the location product only for stock on hand. 3 The location product is not displayed in any of the monitors. The system creates no inventory alerts for the location product. For more help on this topic, see Scenario Control on help.sap.com, and see the documentation in Customizing for Supply Network Collaboration under Basic Settings Visibility Define Scenario Control Keys. The generation of alerts for SMI and DCM is also controlled by the default keys 0-3, since the reports used to create alerts use the same selection mechanisms as the screens. However, it may not be the case for other SNC applications utilizing the Scenario Control. It depends how the alerts are created in that particular application. If a location product is only to be displayed in specific applications, you can introduce you own filtering logic as described below. Example: You want to filter out some products from the Order Forecast Monitor (formerly known as Demand Monitor), but you want those products to be displayed on all other screens. You also do not want the system to generate Order Forecast Alerts for these products. Limiting the alert generation comes for free, since in this case SAP SNC uses the same selection mechanism for alert creation as the WebUI screen does. 2 Define Scenario Control Keys (SCKs) If you want to introduce an own filtering logic, you have to set up your own Scenario Control Key(s) in Customizing for Supply Network Collaboration under Basic Settings Visibility Define Scenario Control Keys: 2

3 In our example, we will use the new SCK 42 to assign it to some location products, and therefore limit their visibility on the Order Forecast Monitor. 3 Assign SCKs to Location Products Assign a Scenario Control Key for each relevant location product in the location product settings on the SAP SNC Web UI. You call the location product settings in the Web application menu of SAP SNC under MasterData -> Product -> SMI Location Product Settings - Customer. Make sure that you specify the supplier before saving the entry; otherwise it will not be saved and used later on by SAP SNC. 3

4 In our example, we have specified one supplier location product to filter the visibility. 4 Prepare BadI to utilize SCKs in selection The BAdI /SCF/BADI_SELECTION filters for SCKs. Use TA: se18 to display its definition: For this BAdI, there are two inactive implementations in the system: /SCF/IM_DCM_SELECT, with two filters: DCM and SMI. (See the domain values of /SCA/SUPP_COLL_PROCESS_CODE_DM for supported filters). If you want to know the selection mode and context of your application, refer to Customizing for Supply Network Collaboration under Basic Settings Visibility Display SAP Default Selection Modes of Application: 4

5 In our example, we want to create and activate a new BAdI implementation ZIM_DMO_SELECT with the filter DMO (Selection Context): Feel free to copy the example implementation /SCF/IM_DCM_SELECT. 5

6 If you want to filter out products from applications, it is enough to use method /SCF/IF_EX_BADI_SELECTION~AFTER_SELRANGE_EVALUATE only, as seen in /SCF/IM_DCM_SELECT. If you want to perform a more sophisticated selection twist, you can also use the method /SCF/IF_EX_BADI_SELECTION~BEFORE_SELRANGE_EVALUATE which runs before the selection range is evaluated. To achieve our example goal, the BAdI implementation would look like the following. method /SCF/IF_EX_BADI_SELECTION~AFTER_SELRANGE_EVALUATE. DATA: l_app_component TYPE /scmb/mdl_appl_component. * scenario control for Demand Monitor (Order Forecast Monitor) l_app_component = flt_val. CHECK l_app_component = 'DMO'. * do the filtering CALL FUNCTION 'ZDMO_SELECT_SCN_CONTROL' EXPORTING ip_app_component = l_app_component CHANGING ct_locfrloctomat_data = ct_locfrloctomat_data[] ct_lane = ct_lane. endmethod. 6

7 FUNCTION ZDMO_SELECT_SCN_CONTROL. *" *"*"Local Interface: *" IMPORTING *" REFERENCE(IP_APP_COMPONENT) TYPE /SCMB/MDL_APPL_COMPONENT *" CHANGING *" REFERENCE(CT_LOCFRLOCTOMAT_DATA) TYPE *" /SCF/LOCFRLOCTOMAT_DATA_TAB *" REFERENCE(CT_LANE_LOCFRLOCTOMAT) TYPE *" /SCMB/MDL_LOCFRLOCTOMATID_TAB OPTIONAL *" REFERENCE(CT_LANE) TYPE /SCMB/MDE_LANE_TAB OPTIONAL *" CONSTANTS: c_dmo_val TYPE numc4 VALUE '42', c_dmo(4) TYPE c VALUE 'DMO'. DATA: lt_id TYPE /scmb/mdl_prtlpid_tab, ls_id TYPE /scmb/mdl_prtlpid_str, lt_prtmatloc_multi TYPE /sca/dm_prtlp_tab, lt_locfrloctomat_data TYPE STANDARD TABLE OF /scf/locfrloctomat_data_ str, l_index TYPE sy-tabix, l_pml_reached TYPE xfeld. FIELD-SYMBOLS: <ls_locfrloctomatid> TYPE /scf/locfrloctomat_data_str, <ls_multi> LIKE LINE OF lt_prtmatloc_multi. INSERT lines of ct_locfrloctomat_data[] INTO TABLE lt_locfrloctomat_data[]. SORT lt_locfrloctomat_data BY prtidfr matid locidto. LOOP AT lt_locfrloctomat_data ASSIGNING <ls_locfrloctomatid>. ls_id-locid = <ls_locfrloctomatid>-locidto. ls_id-matid = <ls_locfrloctomatid>-matid. ls_id-partner_guid = <ls_locfrloctomatid>-prtidfr. INSERT ls_id INTO TABLE lt_id. ENDLOOP. TRY. CALL FUNCTION '/SCMB/MDL_PRTLP_READ_MULTI' EXPORTING iv_appl_component = ip_app_component it_id = lt_id[] IMPORTING et_data = lt_prtmatloc_multi[]. CATCH /scmb/cx_mdl_interface /scmb/cx_mdl_result /scmb/cx_mdl. "#EC NO_HANDLER ENDTRY. CHECK NOT lt_prtmatloc_multi[] IS INITIAL. SORT lt_prtmatloc_multi BY partner_guid matid locid. l_index = 0. LOOP AT lt_prtmatloc_multi ASSIGNING <ls_multi>. "sorted p-m-l * Filter products/locations/partners out IF ip_app_component = c_dmo. * Demand Monitor (Order Forecast Monitor) Filtering CHECK <ls_multi>-cscc = c_dmo_val. 7

8 CLEAR l_pml_reached. * Delete filtered-out lines in return tables LOOP AT lt_locfrloctomat_data ASSIGNING <ls_locfrloctomatid> FROM l_index. "sorted p-m-l l_index = sy-tabix. * get all locations-from for the p-m-l! IF <ls_locfrloctomatid>-prtidfr NE <ls_multi>-partner_guid OR <ls_locfrloctomatid>-matid NE <ls_multi>-matid OR <ls_locfrloctomatid>-locidto NE <ls_multi>-locid. IF l_pml_reached IS INITIAL. CONTINUE. "partfr-mat-locto not yet reached ELSE. EXIT. "no more locs-from for this partfr-mat-locto ELSE. l_pml_reached = 'X'. * remove lanes IF ct_lane IS REQUESTED. DELETE ct_lane WHERE locto = <ls_multi>-locid AND matid = <ls_multi>-matid AND locfr = <ls_locfrloctomatid>-locidfr. IF ct_lane_locfrloctomat IS REQUESTED. DELETE ct_lane_locfrloctomat WHERE locto = <ls_multi>-locid AND matid = <ls_multi>-matid AND locfr = <ls_locfrloctomatid>-locidfr. * remove lofrloctomat DELETE TABLE ct_locfrloctomat_data FROM <ls_locfrloctomatid>. ENDLOOP. ENDLOOP. ENDFUNCTION. Do not forget to activate you BAdI implementation once its done. 5 Further Info Master Data in SNC 7.0 (help.sap.com): link Visible Master and Transaction Data in SNC 7.0 (help.saps.com): link Scenario Control (help.sap.com): link 8

9 6 Copyright Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 9