Test Data for Volume Testing – SAP SCM Demand Planning

Best Practice for Solution Management
Version Date: November 2006 The newest version of this Best Practice can always be obtained through the SAP Solution Manager or the SAP Service Marketplace.

Applicability, Goals, and Requirements................................................................................................1 Best Practice Procedure and Verification.............................................................................................3 Introduction to Demand Planning ..................................................................................................3 Preliminary Tasks..........................................................................................................................5 Procedure .....................................................................................................................................5 Preparation of Data for Characteristic Value Combinations ......................................................5 Creation of Data Structures in APO DP....................................................................................7 Create a Back-up InfoCube in SAP BW ................................................................................. 11 Repetitive Tests.....................................................................................................................14 Further Information ...........................................................................................................................16 Feedback and Questions ............................................................................................................16

Applicability, Goals, and Requirements
To ensure that this Best Practice is the one you need, consider the following goals and requirements:

Goal of Using this Service
The goal of volume testing is to run a realistic simulation of expected workload during the implementation period of an IT solution. This simulation tests the solution's performance, sizing and scalability. Specifically, it focuses on runtimes and data throughput for critical business process paths and interacting components. One of the key requirements for a successful volume test is the availability of suitable test data. This Best Practice describes how you may generate test data for SCM Demand Planning scenarios. The methodology is a straight-forward procedure and is explained step by step, providing you with the necessary technical background to set up a set of test data for demand planning on SCM 4.1 / SCM 5.0.

To apply this Best Practice. Then. If you are unable to use the system configuration that will be used in your production landscape. .sap. which handle the various data upload and generation tasks described below. Procedure for test data preparation: This section describes in detail how to prepare a set of test data required for Demand Planning load tests. As an order of magnitude for executing this procedure we estimate about one week. This Best Practice document is divided into three parts: Preliminary activities: This section describes key requirements. Therein. A designated project team with appropriate knowledge regarding technology and applications in this field is required for the volume test project. If you are experienced with SCM Demand Planning and APO BW. The computational time required for this procedure is mainly determined by the number of background work processes. the setup of data objects and structures should be manageable in one or two days (depending on the complexity of your test scenario and the variety of planning scenarios you want to test. refer to the Best Practice Volume Testing for SAP Solutions – Generic Procedure. 2 Staff and Skills Requirements This Best Practice describes a subset of tasks to be performed for the setup of a Demand Planning volume test scenario. we refer you to SAP Service Marketplace http://service. which have to be fulfilled before the volume tests can be started. you have to setup a designated project (as a subproject of your Demand Planning implementation / update project). refer to the Best Practice Volume Testing for SAP Solutions – Generic Procedure. System Requirements The test environment must have comparable hardware to the productive hardware solution.com/VTO. Nevertheless. this Best Practice can also be used to gain familiarity with the functionalities described herein and can provide you with links to more detailed information. The data load (at least for the data that are directly used for the test scenario) should be brought close enough to the estimate data load on productive environment to replicate realistic conditions. use it to guide you through the different steps of the project. ensure that the application parameters are set similarly and that the hardware size has at least been confirmed by a sizing estimation. For the volume test itself. you should be familiar with the key functionalities of SCM Demand Planning and APO BW. the number of characteristic value combinations (CVCs) and key figures). For further details. This measure is also applied for the data volume. Ideally the test should either be performed directly with the planned productive system configuration or with a suitable copy. Duration and Timing The preparation of test data for Demand Planning is a straight forward procedure and depends mainly on the available computational capacities and the complexity of your planning scenario (basically speaking.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning For further information on volume testing and related Best Practices. How to Use this Best Practice Read the whole document prior to the project start.

New characteristic value combinations need to be generated. (In contrast to DP. SAP R/3. tactical. in SNP no pre-allocation of memory is performed. SAP R/3. or OS file access. for your demand planning business process. to the different products in the product family) . planning areas are initialized.. it may be a time-consuming issue since the realignment process blocks the DP planning processes. In APO. the tools for extracting data from other systems and transferring them to APO for demand planning purposes are the same as SAP BW uses. Background Information The various strategies for using SAP APO. The planning area controls also how a Demand Plan created on high-level (such as product family) is disaggregated to a lower level (for example. SAP BW. Important question for volume tests: How stable is the initially defined POS? In case of many changes. and operational decisions. These systems can be SAP R/3. the Supply Chain Management solution provided by SAP. Planning Area: The central data structure (“data container” which is analog to R/3 table or LSI info structure) of DP / SNP. The system types that can be used here are SAP APO itself (in particular. SAP APO is used to make strategic. if no other procedure applies In DP. IDocs.e. is executed in liveCache memory. SAP Business Information Warehouse (BW). which is held in liveCache DP. primarily to define the key expressions used throughout the description of the best practice procedure. Characteristic Value Combinations (CVC): A characteristics combination that can be used for planning in Demand Planning. i. or again third-party (legacy) systems.in three ways: o by using the proportional factor for each branch in the tree o distributing it according to another key figure o equal distribution. Planning Object Structure (POS): An APO Structure that contains characteristic combinations. The SAP Advanced Planner and Optimizer (APO) is the planning component of mySAP SCM. which are linked to time-series objects (time streams of key figure values within liveCache). and possibly other data processing systems in combination are called integration scenarios. and / or third party and legacy systems or a combination of these.) . its modules SNP and / or PP/DS). 12 months into future). Usually. memory is allocated although no values may have been defined yet. The planning results that come out of the demand planning process are fed into other data processing systems for further planning or execution purposes. Since SAP APO comprises a complete SAP BW. for example if new products are planned or if new materials appear in customer’s purchase orders. Demand Planning is used for long and midterm planning (typical time horizon: 2 years into past. we give a brief introduction into Demand Planning. Created as part of the Demand Planning/Supply Network Planning setup and determines key figures to be accessed from database (InfoCube) or from liveCache (via POS).Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 3 Best Practice Procedure and Verification Introduction to Demand Planning In this section. such as sales figures. an APO system is connected to one or more systems that provide historical and actual data. The APO BW reads the data using remote function call (RFC) techniques.

typically for 4 to 20 characteristics are used for a POS. There is no limit on the number of planning books you can have for a planning area. planned sales.). and saved The assignment of key figures to aggregates Supply Network Planning (SNP) offers already predefined planning areas. and accessibility of the view for other users (there is no limit on the number of views you can have within one planning book) You can configure these and further elements of the interactive planning screen (such as the position of columns and rows. not in the planning area. not the planning book. Planning Book for back-up or reporting The planning book defines the content and layout of the interactive planning screen. we maintain following information for example: Pieces sold per month .g. a planning book is generated. They allow you to design the screen to suit individual planning tasks. 4 Backup of planning areas: Usually. Example for data view: Key figure = sold pieces Characteristics = car model.. most data in the liveCache is DP data purposes. March 03. e. The Data Mart contains historical data loaded up from flat file (EXCEL). sales office Time bucket = monthly For the set of data chosen. o [Key figures actually sold.. R/3. April 03…] The planning areas are linked to the APO Data Mart.. the appearance of the graphic. number of grids. like products. aggregated. location (city). A planning book is based on a planning area. You use planning books in Demand Planning and Supply Network Planning. pcs] Currency in which data is planned (optional) Currency conversion type for viewing planning data in other currencies (optional) Storage buckets profile that determines the buckets in which data is stored in this planning area Aggregate levels on which data can be stored in addition to the lowest level of detail to enhance performance Key figures that are used in this planning area Settings that determine how each key figure is disaggregated. BW… The planning area specifies the following: One unit of measure in which data is planned [for example. the use of colors and icons in rows. up to 100 and more are possible). these data can be downloaded to a BW InfoCube. areas.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning Typical number of planning areas in APO systems is about 10 (but. In the planning book you define the following elements: Key figures and other rows Characteristics Functions and applications that can be accessed directly from this planning book User-specific planning horizons User-specific views on the planning book including initial column. The data container “planning area” has entries of following structure: o [POS = planning hierarchy (user-defined combination of characteristics. countries. In the planning book. simulated sales…] o [Time dimensions a number used in forecast creation to describe a period of time. You can also define your own ones. The liveCache objects on which data is actually saved are based on the planning area. The end users work in the planning book. and macros) by using the context menus in interactive design mode. the visibility or non-visibility of rows.

0): Error! Objects cannot be created from editing field codes. For demand planning. you need a definite knowledge about the planning scenarios you want to simulate. In particular. you have to restrict yourself to a maximum size of ~ 60. such as historical sales volume. no master data is required. the preparation of test data for Demand Planning can be realized quite easily. In the following.000 CVCs (per line one CVC). which correspond to the expected future data volume in your realistic demand planning scenario. o Create a macro for population of historical values for key figures o Populate key figure values via the macro In BW or APO BW: Store the demand planning data in a BW InfoCube. price. and so on) Key figures. Create a file with characteristic value combinations (CVC) or define source for data input into APO In APO: o Create a planning object structure (POS) o Upload the file with CVCs to create CVCs in the POS o Create Storage Bucket Profile required for planning area o Create a planning area o Create time series objects for key figures from planning area o Create a planning boo.536 rows by 256 columns.1 and SCM 5. model. corrected history. Preparation of Data for Characteristic Value Combinations Create a Microsoft EXCEL file containing characteristic value combinations (CVCs) Since the limitation of an EXCEL worksheet is 65. before you start the setup of test data as described in this document. we describe these steps in detail. In accordance with the actual number of CVCs expected for your demand planning process (typical order of magnitude is some hundred thousand CVCs) you will have to make an according number of copies of this EXCEL sheet to end up with a total number of CVCs. the only input required is characteristic value combination and key figures. which are based on transactional or master data. you need to ensure the availability of a SAP SCM system where you can follow the procedure described in this document. and future demand. the following information regarding your business and requirements for demand planning has to be available: characteristic value combinations key figures required for the demand planning knowledge of time period ( = planning periodicity) for which you need historical data and planning horizon for demand planning Procedure In comparison with other planning scenarios. quality. Example: Characteristics of product (color. . To generate a set of test data.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 5 Preliminary Tasks For the setup of test data for Demand Planning. Generally. location) the company (sales organization. country. size. The procedure to set up test data for Demand Planning consists of the following basic steps (for releases SCM 4.

at each location each product is available. Save the EXCEL Files as ASCII (*. Most probably. In practice. the natural way to upload the CVCs to APO Demand Planning would be to do it via these data sources. In this case. sales organization): SS SS SS SS SS LOC1 LOC1 LOC1 LOC1 LOC1 PR1 PR1 PR1 PR1 PR1 SUPP1 SUPP2 SUPP3 SUPP4 SUPP5 SO10 SO10 SO10 SO10 SO10 Note: To ensure that the appropriate data volume is generated in DP. the number of CVCs may become very large if you have a large number of planning hierarchies and if you assume that for example. Further below. in APO identical CVCs are deleted. . When you perform in APO the upload of the CVCs to the planning object structure. the CVCs defined in this way have to be unique. you will have your CVCs available via legacy systems or in a BW InfoCube. we describe how to do the upload from BW to APO. NOTE: As it becomes obvious from the above example. product. supplier.txt) File These text files are required for the upload to a planning object structure. The procedure described here is more of a pedagogical nature. location.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 6 Your business may imply following characteristics: No of locations: No of products in each location: No of suppliers for each product: No of CVCs: Sales Organizations/Brands: 10 10 100 10000 SO10 SO20 SO30 SO40 SO50 SO60 60000 SS MS LS SM MM LM SL ML LL XL 10 brands Total No of CVCs (typical order of magnitude): 600000 corresponds to 10 EXCEL sheets (each with 60000 lines) One EXCEL sheet corresponding to one brand small small medium small large small small medium medium medium large medium small large medium large large large x-large For one sales organization No of CVCs: Brand Name: The first entries in the EXCEL sheet then look like (columns: brand name. you will have deviations and will have to adapt the EXCEL sheets accordingly.

sales organization. for our example: o Start date: e.01. select the radio-button Generate in background).Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 7 Creation of Data Structures in APO DP NOTE: The steps described in this section are valid for both SCM 4. products. change view from Planning areas to Planning Object Structures go to Edit Create Planning Object Structure In the pop-up. brand name) we can either use the delivered standard characteristics with prefix “9A*” (9ALOCNO.2001 mostly chosen: at least ~5 years in past 1 2 For the sake of simplicity. 2 With the buttons Check and Activate (upper menu bar) check and activate your POS. Step 1: Create a Planning Object Structure (POS) Call transaction /N/SAPAPO/MSDP_ADMIN (S&DP Administration) in the upper menu bar. mark the radio-button Generate immediately (for execution in background. Value Execute via the Execute button.g. Go to section Data Source Load Data From choose File Go to Local PC browse to the text file containing the CVC. . enter a Flag the appropriate bucket granularity (for DP. suppliers. you may call transaction /N/SAPAPO/MSDP_ADMIN (S & DP Administration) change view to Planning Object Structures mark the text entry for your POS and click the right-hand mouse button Details Expand Performance check the number of created CVCs. Set the flag for Results Log and Check Char.1 In field Text.1 and SCM 5. it is necessary to define the characteristics product and location in the POS. 9AVKORG.. Step 2: Create Characteristic Combinations in your POS based on data from the Excel file Call transaction /N/SAPAPO/MC62 (Maintain planning-relevant characteristic combinations) in field Master Planning Object Structure enter the POS name (POS_VT) go to Create Characteristic Combinations: For immediate creation. In case that there is a difference between the procedures for the two different releases. we set the flags for “Week” and “Month”) Define the Start and End Date for storage of the Time Series Objects (not relevant for memory allocation). Step 4: Create Storage Bucket Profile for your Planning Area Call transaction /N/SAPAPO/TR32 (Maintain Periodicity) name for the storage bucket profile (example: SBP_VT) In the entry field Stor. it is explicitly mentioned hereafter. 9ASPSUPL. 9AMATNR. Step 3: Display created characteristic combinations Call transaction /N/SAPAPO/MC62 click Display Characteristic Combinations enter the name of your POS (POS_VT): Click No. In case that you transfer the demand planning results to APO SNP. For our example (locations.Bckts Prfl. add the appropriate characteristics to your POS. we extend the naming for our example objects / structures with _VT (volume test). you can also specify selection criteria) Alternatively. 9ABRAND) or create new ones which are more suitable for your business needs. enter a description for the POS Do not mark any of the other fields In accordance with your CVCs (as defined via the ASCII file). of combinations to check the number of just created CVCs Click Execute to display the single values (to limit the amount of displayed data. for our example. Do this via marking the appropriate entries in the bottom-right table and copying by clicking the left-hand directed arrow-button.0. 01. we recommended to use weeks as the smallest bucket for the data storage. define a name for the Master Planning Object (example: POS_VT).

for example: o 9AHISTB History (Basis) o 9AHISTP History (Promo) o 9AHISTT History (Total) o 9AMANFCST Manual Forecast o 9AMANUP Manual Correction o 9ADMDTOT Total Demand Plan o 9ADMDP1 Sales Order o 9ADMDSE Dependent Demand o 9AFPROD Production (Conf.01.2030 mostly chosen: at least ~30 years in future 3 Save by clicking the diskette (SAVE) icon.01.01. pieces pc) Click Confirm Go to the tab Key Figs: From the right-hand screen.) Check the Planning Area (by clicking the Check button) and save by clicking the diskette (SAVE) icon. In the Planning Book Wizard. set the corresponding flag in the dialog box) After successful initialization (status: green). via drag and drop from the list Planning Area. about 2 years in the past) o End Date <01.2004> (typically. Step 7: Create Planning Book Call transaction /N/SAPAPO/SDP8B (SDP Interactive Planning – Initial Screen) in Planning Book Selection. In tab Data View o Enter a name for the data view (example: DATAVIEW_VT) 3 Because your planning horizon is continuously rolling into future it should be ensured to have enough of a time buffer in the storage bucket profile. assign the characteristics via drag and drop continue. . Otherwise it can happen that you will have to re-initialize used DP objects in order to extend the validity of the bucket profile.2008> (typically. 01. assign your planning area on the bottom. field Planning Book enter a name for the planning book (example: PB_VT) and click the Create button. choose key figures you wish to plan for in your Planning Area. you can display the created time series objects via right mouse click the planning Area Created Time Series Objects.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning o End Date: e.. click Continue In tab Key Figures. Check the allocated memory in liveCache (for details. assign your key figures to the planning book continue In tab Characteristics. see step 10). about 3 years in the future) Click the Execute button (to execute in background. Step 6: Create Time Series Objects for Your Planning Area Call transaction /N/SAPAPO/MSDP_ADMIN view: Planning Areas choose your planning area with click right-hand mouse button choose Create Time Series Objects a dialog box is displayed: Enter Planning Version 000 specify start and end date for which time series objects should be created: o Start date <01.g. Step 5: Create Planning Area Call transaction /N/SAPAPO/MSDP_ADMIN Planning Area: choose view Planning Area click Edit Create 8 Enter a name (example: PLA_VT) Specify the POS (POS_VT) Specify the storage bucket profile (SBP_VT) Specify the unit of measure (for example.

01. it may become quite large.11. you have to restrict the number of CVCs for which you populate the full set of required key figures.2004). The appearance of your macro could be as follows: Note: Since a detailed description of advanced macro maintenance is beyond the scope of this Best Practice. Call transaction /N/SAPAPO/ADVM (Macro Workbench): In column Macro Book Description. Note: Since the runtime of the macro scales with the number of CVCs. Step 8: Create Macro for background job to populate values of some of the key figures in the Planning Book. that is. we refer you to SAP Help Portal Demand Planning Process Planning Book Design Advanced Macros Step 9: Define background job to execute the Macro Call transaction /N/SAPAPO/MC8T (Define Activity for Mass Processing) to define an activity: 4 Usually.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning o 9 Specify time buckets profile ID for future and past periods (for example. Therefore. create a new macro (example: Macro for Volume Testing). In tab Key Figures assign the key figures to the Data View and complete the planning book by clicking the Complete icon in the bottom of the planning book wizard. demand planning for future values of key figures depends on the key figures itself. in many cases for a given CVC the value assigned to a key figure depends on the values of one or several other key figures for this CVC. . the first to define the historical values and the second to define the future values. to limit the runtime of the macro it does not make sense to reduce the number of key figures which are populated by the macro. 12MONTHS and 24MONTHS) o Define the date from when they should be visible and open for manual input (for example. Maintain the macro according to your business requirements that is with reference to the key figures you need for your demand planning. double-click the name of your planning book (PB_VT) Inside the macro book for your planning book. two steps. To limit the macro runtime.4This macro could consist of for example.

o o Save by clicking the SAVE (diskette) icon. and the name of the Data View (DATAVIEW_VT) In tab Macro. assign the selection ID (SELECTION_VT) via drag and drop to your user. and Version. which will be processed lateron in case that this selection has been assigned to the corresponding job. o In addition to this. as automatically proposed. A dialog box Maintain selection profiles for users is displayed. o To assign an appropriate aggregation level. Show = Sales Organization and under that meet following conditions the values APO Planning Version = 000. specify the names for your Planning Book. for example. Select all the characteristic combinations in the dialog box. o In the screen Create Planning Job. under Control Parameters for background planning. Click SAVE.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning o o o o In field Activity. you may restrict the execution of the macro to available selection IDs. and APO Product = <APO product>. enter an appropriate name for the selection (example: SELECTION_VT) On the left-hand menu bar. In our example: . click Selection Profile. Click Execute. Step 10: Check liveCache Size and Used Area Call transaction /NLC10 (liveCache – Initial Screen) In field Name of Database Connection specify the name of the liveCache Click the button liveCache Monitoring go to Memory Areas select Data Area (all values in KB). click button Aggregation Level. enter a name (example: MACRO_VT) and add a description (example: Run macro for volume test) and click Create Enter a description. assign the activity you have created before (JOBNO_1). set the radio button One and select the selection ID you have created before (SELECTION_VT). the name of your Planning Book (PB_VT). enter the name of the recently created macro (Macro for Volume Testing) Save by clicking the SAVE (diskette) icon on the top. o Click button Selection Window (left-hand side of the screen. o Call transaction /N/SAPAPO/MC8D (Create Planning Job) to define a planning job o Enter a job number (example: JOBNO_1) and a job Name (example: EXECUTE_MACRO) and click Execute o In the displayed dialog box. o In Planning Job Information. you may check the number of planning objects (it depends on the number of CVCs specified by the selection you have assigned to the planning job). o Click SAVE. select. To specify a particular selection. In the dialog box. o In Chars (characteristics). Data View. Call transaction /N/SAPAPO/SDP94 (Interactive Demand Planning) o Navigate to your Planning Book/Data View (PB_VT/DATAVIEW_VT) and open it. In the dialog box. 10 The next step is to create a selection ID for a subset of CVCs. selector menu bar at the top) o To restrict the selection to a subset of CVCs. set the flag for Generate Log.

Step 12: Check Usage of LiveCache (Used Area): To check the usage of liveCache after successful creation of data via the background job. In the following section. For each entry. Recommendation: In case that processing a macro. we recommend you to schedule in parallel several planning jobs for disjoint sets of CVCs. we describe how to create an InfoCube in BW.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning Step 11: Execute the Background Job 11 Call transaction /N/SAPAPO/MC8G (Schedule Mass Processing): select the job number and job name number (JOBNO_1. For optimum job scheduling. you may create an InfoCube in BW to store your historical data to upload them to APO later-on. To have a look on the job results. which populates the key figures for all CVCs at once leads to performance issues (for instance. EXECUTE_MACRO) schedule the job You can check status of your job via transaction /NSM37. the following steps are necessary: Create an Info Area (~Folder for InfoCube): Create a backup InfoCube for Planning Area Generate DataSource Replicate DataSource Create Application Component Create Info Source Assign Source System Maintain Transfer Rules Create Update Rules for Info Cube Create Info Package Schedule Info Package Control data uploaded to InfoCube . call transaction /N/SAPAPO/PERFMON Demand Planning Statistics: Mass Processing. you can control the number of processed and saved CVCs in the respective columns. The purpose of this InfoCube is to have this test data available for the repeated initial setup of test runs. Create a Back-up InfoCube in SAP BW Once we have finished the necessary activities in SCM APO to obtain a set of test data for demand planning. In the same way. To create a back-up InfoCube and upload the data. we recommend you to employ Redwood Chronacle. we have to back-up these data in an InfoCube in SAP BW. proceed as described before. ALTERNATIVE: Upload of Historical Data from BW An alternative to populating historical values for key figures via a macro would be to upload this data from a BW InfoCube. to make automatic use of temporary available hardware resources. long runtime and / or too much memory required).

go Step 4: Replicate DataSource To replicate the data source from APO to BW: Call transaction /N/SAPAPO/SDP_EXTR enter the names of your planning area (PA_VT) and your DataSource (9ADS_VT) click Replicate DataSource. On the top of this list. specify how you want to create the objects: as DataSource or as 3. Enter a name (example: INFOAREA_VT) and a description for the Info Area to be created. For SCM 5. we use the transactions in the APO BW.0.> Step 5: Create Application Component Call transaction /nrsa1 go to Modeling click InfoSources on the right-hand side. maintenance screen for transfer rules and communication structure appears.1) Choose Flexible Update in any Data Target (Except Hierarchies) insert a name (example: INFS_VT) and a description for the InfoSource to be created Confirm and save Step 7: Assign Source System In the list of InfoSources. call transaction /NRSA1 to InfoProvider expand the entry for InfoArea INFOAREA_VT. we recommend using 3. click with the right mouse button on the newly created InfoSource INFS_VT and for SCM 5. .0: select Additional Functions Assign Source System select the appropriate source system (system on which SCM DP is operated) in the displayed dialog box. In the following. you have to create a workbench request by yourself. Step 2: Create a backup InfoCube for Planning Area Call transaction /N/SAPAPO/SDP_EXTR (DP/SNP Data Extraction) in field Planning Area. Press Continue (Enter). you have the possibility to hide / select some fields (by setting the corresponding flag) Click SAVE.x) <In SCM 4.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 12 You may create this InfoCube either in your separate BW (if available) or in the APO BW. Step 3: Generate DataSource Call transaction /N/SAPAPO/SDP_EXTR enter name of your Planning Area (PLA_VT) and define a name for the DataSource (example: DS_VT) Generate DataSource in the dialog box. click with the right mouse button on entry for the newly created application component (APPLICATION_COMPONENT_VT) and select Additional Functions Create Info Source3. select the name of your planning area click Data backup execute Generate InfoCube from planning area and enter name of the InfoCube (example: IC_VT) description name of InfoArea (INFOAREA_VT) Execute (confirm the dialog box asking if you want to add the key figure for proportional factors to the InfoCube). insert a name (example: APPLICATION_COMPONENT_VT) and a description Click Continue (Enter) (Possibly.x (for SCM 5. in the displayed popup. click with the right mouse button on InfoSources and click Create Application Component for the application component to be created. A dialog box appears. Step 1: Create an Info Area (corresponds to a “folder” for InfoCube) Call transaction /NRSA1 (Data Warehousing workbench: Modeling) InfoProvider click with the right mouse button on the node Info Provider and choose Create InfoArea. the list InfoSources is displayed. To check that the InfoCube was automatically assigned to the InfoArea.x DataSource.1.) Step 6: Create Info Source Call transaction /NRSA1 In the list for InfoSources. in field with prefix “9A” enter the DataSource name confirm in the next screen. select the appropriate DataSource (9ADS_VT) click SAVE to save changes On the right-hand sight of the screen.0) / Create Info Source (for SCM 4. this dialog box is not displayed.

0. In the Update rule: Detail screen you specify one of the following update options: 1. continue as follows: o Enter a value (<000>) in field /BI0/9AVERSION(APO Planning Version) since it is a mandatory input field o In the Schedule tab: select Start Data Load Immediately and click Start o Press Monitor to check the upload results via SM37. 2.1: Double-click the icon of the corresponding InfoCube (IC_VT) In the InfoCube maintenance screen. Select the name of the InfoCube and check its content (you see the 5 If the status of a key figure is red. even if no master data exists for the data To upload the data into the InfoCube. If you are uploading data for this key figure and you do want the data to be modified in this process. If necessary. double-click on it.1 your source system click with the right-hand mouse button and select Create Info Package enter a description click SAVE.0: click the icon of the corresponding InfoCube (IC_VT) to start the InfoCube browser transaction. If you are uploading data for this key figure and the update is straightforward (that is.0 mark your DataSource / for SCM 4. Formulas are a “simplified” version of routines if you are not able to write an ABAP–routine. In the Processing tab. You are also led to the maintenance screen for transfer rules from here. select the radio-button PSA and then into data targets. Call transaction LISTCUBE same screen as above). Then choose Transfer. choose Transfer.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 13 For SCM 4. set the flag if you want to display the contents with SID on the next screen. fill manually missing entries in the column InfoObject by copying them from the left part of the screen) Save and activate the InfoSource (by clicking the icons on top of the screen). The InfoObjects for which you can specify a range depending on which ones you selected. select Assign Data Source and continue in analogy to the description for SCM 5. Step 8: Maintain Transfer Rules Ensure that Transfer method = PSA ( Persistent Staging Area) is selected In tab Transfer Rules. select the update method Routine and create a routine by clicking on the Create icon. specify the InfoSource (INFS_VT) click Continue (Enter) 5 When all status are green (respectively. you can also choose Formula und press Create. activate the update rules. Step 9: Create Update Rules for Info Cube Call transaction /NRSA1 go to menu bar Modeling click InfoProvider click with the right-hand mouse button on your InfoCube for SCM 5. restrict the ranges for which data is uploaded on the Data Selection tab. set the radio-button Select Data Targets and select the recently created InfoCube. for SCM 5. click Display Data SCM 4. Then choose Transfer. choose Transfer. no red status lights are displayed). . Once you have created the formula. Otherwise choose Addition. click the icon Propose Transfer Rules (if necessary. If you are uploading data for this key figure and you do want the data to be modified in this process. go to Edit InfoCube data display in the displayed dialog box. Once you have created the routine. In the Update tab select Full Update and Always update data. click Execute.0 only: select Additional Functions Create Update Rules in the displayed dialog box. 4. select the update type No update. If you are not uploading data for this key figure. In the Data Targets tab. you do not wish the data to be modified in this process). 3. choose the update method Source key figure.1. Step 11: Check Results of Data Load into Info Cube Call transaction /NRSA1: Modeling click Info Provider click right-hand mouse button SCM 5. Step 10: Create and schedule Info Package Still in the “InfoSource” area.

This copy has to be completed by the remaining key figures which have been populated during the planning run. This can be easily done making a copy of the macro you have used to populate some of the key figures. the data) in the planning area. There are two possibilities: (1) Overwrite the key figure entries by “0”. Once you are finished with your optimization measures. Once the time series objects have been deleted. you have to reinitialize the key figures in the planning area.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 14 Repetitive Tests In case that you experience performance bottlenecks during the volume test runs. (2) Alternatively. Choose “0” as an operator value assigned to the rows of the macro. For that purpose. you have to retest the planning scenarios. you possibly will prefer to execute the macros instead of loading up the data from the InfoCube. following steps are necessary: Delete any logs written during the planning runs Delete the key figures containing the planning result from macro calculation Upload back-up data from BW InfoCube to the planning area Note: The runtime for the upload of the InfoCube may significantly exceed the runtime of the macros for populating the key figures. To overwrite the values for one single key figure (here. historical values for demand) the macro would look as follows: Once you have executed this macro. . you may reinitialize the planning area. one again has to initialize the planning area as described above in step Create Time Series Objects for your Planning Area. you have to optimize your scenario. Therefore. which are affected by the changes. This is equivalent to a deletion of all time series objects (that is. Either you have to optimize the technical performance or to reconsider and adapt your planning activities to the technically feasible time windows. the key figures in the corresponding planning book are reinitialized. Reset planning area To reset the planning area. Call transaction /SAPAPO/MSDP_ADMIN select the planning area click the right-hand mouse button select Delete Time Series Objects (this activity can also be run in background).

Click EXECUTE. you have to upload the initial Demand Planning data from the BW InfoCube to liveCache as follows: Call transaction /N/SAPAPO/TSCUBE (Load planning area version): For the source. . Define the horizon (period from . Assign the characteristics between the Info Cube and the Planning Area. define the planning area (PLA_VT) and the planning version (000). Include restrictions for data selection. For the target. define the InfoCube (IC_VT) and the planning version (000). if necessary.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 15 Upload Back-up Data from BW InfoCube to the Planning Area Before starting the next test run.to). Assign the key figures between the Info Cube and the Planning Area. Mark the flag Log to receive a log afterwards.

SAP shall have no liability for damages of any kind including without limitation direct. z/OS. VideoFrame. xSeries. WebSphere. either express or implied. indirect. developments. S/390. Please note that this document is subject to change and may be changed by SAP at any time without notice. The information in this document is proprietary to SAP. This document is provided without a warranty of any kind. MaxDB is a trademark of MySQL AB. XML. IBM. OS/390. MVS/ESA. SAP. Inc. National product specifications may vary. and Informix are trademarks or registered trademarks of IBM Corporation. R/3.Best Practice: Test Data for Volume Testing – SAP SCM Demand Planning 16 Further Information Feedback and Questions Send any feedback by formulating in the SAP Service Marketplace http://service. Outlook. XHTML and W3C are trademarks or registered trademarks of W3C®. . and Motif are registered trademarks of the Open Group. © Copyright 2006 SAP AG. special. copied. World Wide Web Consortium. Citrix. including but not limited to the implied warranties of merchantability. Program Neighborhood. Data contained in this document serves informational purposes only. No part of this document may be reproduced. Massachusetts Institute of Technology. All other product and service names mentioned are the trademarks of their respective companies. DB2 Universal Database. mySAP. WinFrame. Microsoft. fitness for a particular purpose. xApp. HTML. AIX. This limitation shall not apply in cases of intent or gross negligence.com/message a customer message on component SV-SMG-SER with title “Best Practice for Volume Testing”. Windows. zSeries. mySAP. DB2. OS/400. Inc. or non-infringement. or consequential damages that may result from the use of these materials. MetaFrame. pSeries. SAP does not warrant the accuracy or completeness of the information. or other items contained within this material. Tivoli. Oracle is a registered trademark of Oracle Corporation. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of thirdparty Web pages nor provide any warranty whatsoever relating to third-party Web pages. SAP assumes no responsibility for errors or omissions in this document. X/Open.. 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 in several other countries all over the world. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. SAP NetWeaver. ICA. Netfinity. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. product strategy. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. and/or development. and PowerPoint are registered trademarks of Microsoft Corporation. This document contains only intended strategies. Parallel Sysplex. OSF/1. and MultiWin are trademarks or registered trademarks of Citrix Systems. used under license for technology invented and implemented by Netscape. iSeries. graphics. The information contained herein may be changed without prior notice. 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. AFP. AS/400. UNIX.sap. text. links. The statutory liability for personal injury and defective products is not affected. OS/2. Sweden. Java is a registered trademark of Sun Microsystems. JavaScript is a registered trademark of Sun Microsystems. Intelligent Miner. Inc. xApps.com.