This Document Contains a list of All Transaction Codes Required for SAP Fiori Development[Front-End,Back-End and Gateway]. For utilization of Workflows in Custom SAP Fiori Apps,Workflow related transactions would be used.Some of these will be available in Frontend[SAP Gateway] and Some will be for SAP Back-End, in case of Central HUB deployment of SAP Gateway. In case you have an Embedded Gateway Deployment,both Back-End and Front-End Transactions would be available in a single system.

The list of T-codes is based on the following system:

EHP7 for SAP ERP 6.0(Release = EHP7 FOR SAP ERP 6.0)

SAP ERP(Release = 2005(SAP ERP 6.0))

SAP Netweaver(Release = 7.4)

and the following Software Components:

SAP_BASIS    Release = 740   SPLevel =  0010    Support Package = SAPKB74010    SAP Basis Component

SAP_ABA    Release = 740    SPLevel = 0010    Support Package = SAPKA74010    Cross-Application Component

SAP_GWFND    Release = 740    SPLevel = 0013    Support Package = SAPK-74013INSAPGWFND    SAP Gateway Foundation 7.40

[Note:]

This list is divided into 3 columns.

(01)T-code

(02)Description of T-code

(03)Alternate T-code called,for example in case of Front-End and Back-End Transaction Codes.

[Note:]

Standard T-codes Required:

Odata Service Development T-codes:

SEGW    Gateway Service Builder

Administrative T-codes:

SU01    User Maintenance

PFCG    Profile Generator

SICF    Maintain Services

LPD_CUST    Launchpad

SMLG    CCMS: Maitain Logon Groups

SM59    RFC Destinations (Display/Maintain)

_____

SPRO    Customizing - Edit Project

Would require access to the following nodes in IMG(Implementation Guide):

SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway

SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway Service Enablement

SAP Customizing Implementation Guide > SAP Netweaver > UI Technologies

Figure 01 : SPRO Nodes Specific to SAP Fiori

_____

RZ10    Maintain Profile Parameters

RZ20    CCMS Monitoring

RSRT    Start of the report monitor

PTARQ    Test Environment for Leaves

EXTID_DN    External Identification Type DN

SPAM    Support Package Manager

SMICM    ICM Monitor

ABAP Related Backend Development T-Codes:

SE93    Maintain Transaction Codes

SE01    Transport Organizer (Extended)

SE80    Object Navigator

SE11    ABAP Dictionary Maintenance

SE18    Business Add-Ins: Definitions

SE24    ABAP Class Builder

ST22    ABAP Dump Analysis

SE63    Translation Editor

SE43    Maintain Area Menu

SE38    Abap Editor

SBWP    SAP Business Workplace

SM30     Call View Maintenance

____

Note:

Authorization for SM30 is required when accessing or configuring Configuration tables for example

creation of Semantic Objects using T-code '/UI2/SEMOBJ' which makes use of Maintenance Tables.

____

Workflow related T-codes:

SWDD    Workflow Builder

SWIA    WI Administration Report

SWDC    Workflow Definition: Administration

PFTC    General Task Maintenance

/IWWRK/WF_FILTER    Handle Activation of WF item filter

For Front End SAP UI5 Development:

All Transaction code starting with '/UI2/' and '/UI5/'.

Transaction Codes starting with '/UI2/':

/UI2/73000001    Register POWL APPLID    SICF_INST

/UI2/73000003    Maintenance view for SAP GUI Tags(user defined tags)    SICF_INST

/UI2/73000004    NWBC Configuration - Define Parameter Names(Customer)    /UI2/NWBC_CFG_P_CUST

/UI2/73000005    NWBC Configuration - Define Parameter Names(Customer)    /UI2/SAPLNWBC_CFG

/UI2/73000007    NWBC Configuration - Define Parameter Names(Customer)

/UI2/73000008    Maintain Services    SICF

/UI2/73000009    Trust Manager    STRUST

/UI2/73000010

/UI2/73000011    Trust Manager    STRUST

/UI2/73000012

/UI2/73000013

/UI2/73000014    Server Communications    CLB2_PLATF

/UI2/73000015    Application Server Assignment    CLB2_APPLI_PLATF

/UI2/73000016    badi Creation    SE18

/UI2/73000017    Semantic Objects

/UI2/73000019    SAPLS_CUS_IMG_ACTIVITY(Catalog)

/UI2/73000020     Catalogs

/UI2/73000021     Catalogs

/UI2/73000022

/UI2/73000023    Configuration of RFC Connections

/UI2/73000024

/UI2/73000025    Manage SAP System Aliases    /UI2/GW_SYS_ALIAS

/UI2/73000026    Activate and Maintain Services    /IWFND/MAINT_SERVICE

/UI2/73000027

/UI2/73000028    Maintain Services    SICF

/UI2/73000029    Role Maintenance    PFCG

/UI2/73000030    Data Browser    SE16

/UI2/73000031    Semantic Objects

/UI2/73000032    Launchpads    LPD_CUST

/UI2/73000033    Fiori Launchpad Checks    /UI2/FLC

/UI2/73000034    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG

/UI2/73000035    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG

/UI2/73000036    Odata Services

/UI2/73000037    Fiori Launchpad Intent Resolution Analysis

/UI2/73000038    Not runnin

/UI2/73000039    badi Creation    SE18

/UI2/73000040    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000041    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000042    SAPLS_CUS_IMG_ACTIVITY    PFCG

/UI2/73000043    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000044    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000045    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000046    Collaboration Tunnel Service    CLB2_TUNNEL

/UI2/73000047    Define Background Job    SM36

/UI2/73000048    Simple Job Selection    SM37

/UI2/73000050

/UI2/73000051    bgRFC Configuration    SBGRFCCONF

/UI2/73000053    Odata Service Settings for Notifications

/UI2/73000054    UI2 Global Cache Invalidation

/UI2/73000055    /UI2/USER_FEEDBACK_Setup    /UI2/FEEDBACK_SETUP

/UI2/73000056    CCMS(maintain Logon Groups)

/UI2/73000057    Badi Creation    SE18

/UI2/73000058    Badi Creation    SE18

/UI2/73000059    Events for Change Document    SWEC

/UI2/73000060    Collaboration Service    CLB2_SERVICE_C

/UI2/CACHE    Register service for UI2 cache us

/UI2/CACHE_DEL    Delete cache entries

/UI2/CHIP    Chip Registration

/UI2/CUST    Customizing of UI Technologies

/UI2/FEEDBACK_SETUP    UI2 Setup User Feedback Service    /UI2/FEEDBACK_SETUP

/UI2/FLC    Fiori Launchpad Checks

/UI2/FLIA    Fiori Launchpad Intent Analyis

/UI2/FLP    SAP Fiori Launchpad

/UI2/FLP_CONTCHECK    Fiori Launchpad - Content Checks

/UI2/FLP_INTENTCHEC    Fiori Launchpad - Intent Checks

/UI2/FLPD_CONF    Fiori Lpd. Designer (cross-client

/UI2/FLPD_CUST    Fiori Lpd. Designer (client-spec.

/UI2/GW_ACTIVATE    Gateway - Activation    /IWFND/IWF_ACTIVATE

/UI2/GW_APPS_LOG    Gateway - Application Log

/UI2/GW_ERR_LOG    Gateway - Error Log

/UI2/GW_MAINT_SRV    Gateway - Service Maintenance

/UI2/GW_SYS_ALIAS    Gateway - Manage SAP System Alias    /UI2/GW_SYS_ALIAS

/UI2/INVAL_CACHES    Global Invalidation of UI2 chache

/UI2/NAV    Register navigation objects

/UI2/NAVPROV    Define navigation provider

/UI2/NWBC    Start UI2 NWBC

/UI2/NWBC_CFG_CUST    NWBC Configuration (Customer)

/UI2/NWBC_CFG_P_CUST    NWBC Config: Define Parameter (Cust)

/UI2/NWBC_CFG_P_SAP    NWBC Config: Define Parameter (SAP)

/UI2/NWBC_CFG_SAP    NWBC Configuration (SAP)

/UI2/PERS_DEL    Cleanup Personalisatation Service

/UI2/POWL    Register POWL for OData consumption

/UI2/SEMOBJ    Define Semantic Object - Customer

/UI2/SEMOBJ_SAP    Define Semantic Object - SAP

Transaction Codes starting with '/UI5/':

/UI5/78000001    ICF: Report for Activating Special Service During Installation    SICF_INST

/UI5/78000002    ICF: Report for Activating Special Service During Installation    SICF_INST

/UI5/THEME_DESIGNER    UI Theme Designer

/UI5/THEME_TOOL    UI Theme Tool

SAP Fiori Front End  Specific T-codes:

/IWFND/32000004    Role Maintenance    PFCG

/IWFND/32000011    Activate/Deactivate Metadata cache    /IWFND/MED_ACTIVATE

/IWFND/32000012    Cleanup of Model Cache    /IWFND/CACHE_CLEANUP

/IWFND/32000013    Activate and Maintain Services    /IWFND/MAINT_SERVICE

/IWFND/32000017    Assign Data Provider to data model

/IWFND/32000018    Change View Assign SAP System Aliases to Odata Service

/IWFND/32000020    IMG Activity not found for transaction /IWFND/32000020

/IWFND/32000021    IMG Activity not found for transaction /IWFND/32000021

/IWFND/32000022    IMG Activity not found for transaction /IWFND/32000022

/IWFND/32000023    IMG Activity not found for transaction /IWFND/32000023

/IWFND/32000024    IMG Activity not found for transaction /IWFND/32000024

/IWFND/50000001    Choose Activity

/IWFND/50000003    SAP Netweaver Activation code    /IWFND/IWF_ACTIVATE

/IWFND/50000004    Manage SAP System Aliases

/IWFND/50000005    Configuration of RFC connections    SM59

/IWFND/50000006    SAP gateway client

/IWFND/50000007    SRT_WS_IDP_CUSTOMIZE[Shedule Switch]

/IWFND/50000008    There are no executable transactions assigned to the IMG activity

/IWFND/50000009    Define Background job    SM36

/IWFND/50000010    cleanup for SAP Netweaver gateway Cache and Persistency Frameworks    /IWFND/CLEANUP

/IWFND/50000011    Simple Job Selection    SM37

/IWFND/50000013    There are no executable transactions assigned to the IMG activity

/IWFND/50000014    Role Maintenance    PFCG

/IWFND/50000015    Role Maintenance    PFCG

/IWFND/50000018    Logon Ticket Administration for Single Sign-On    SS02

/IWFND/50000019    There are no executable transactions assigned to the IMG activity

/IWFND/50000022    Deactivate Logging of Variables T100 Messages

/IWFND/50000027    maintaince dialog is incomplete or not defined

/IWFND/50000031    Registration in System Landscape Directory    R70

/IWFND/50000038    IMG Activity not found for transaction /IWFND/50000038

/IWFND/50000039    IMG Activity not found for transaction /IWFND/50000039

/IWFND/50000040    IMG Activity not found for transaction /IWFND/50000040

/IWFND/50000043    the maintenance dialog for /iwfnd/v_coobgr

/IWFND/50000044    There are no executables assigned to this

/IWFND/50000045    There are no executables assigned to this

/IWFND/50000046    Class Builder    SE24

/IWFND/50000051    Configuration of RFC Connections    SM59

/IWFND/50000052    bgRFC Configuration    SBGRFCCONF

/IWFND/50000053    Consumer Activation

/IWFND/50000054    Maintenance view for the GW CCMS Structure

/IWFND/50000055

/IWFND/50000056    Enter Correct SNC Names in Table View VUSREXTID(from SAP R/3 4.5)    /IWFND/BULK_USER_MAP

/IWFND/50000057    Change View Logical File Path Definition    FILE

/IWFND/50000058

/IWFND/50000059

/IWFND/50000060

/IWFND/50000061    No transaction found

/IWFND/50000062    Role Maintenance    PFCG

/IWFND/50000063    SAP gateway client

/IWFND/50000065    WSS_SETUP    /IWFND/WSS_SETUP

/IWFND/50000066    User Maintenance    SU01

/IWFND/50000068    Badi /IWFND/BD_DCS_PROCESS_PLUGIN

/IWFND/50000071    IMG Activity not found for transaction /IWFND/50000071

/IWFND/50000072    SAP Netweaver Gateway Log Level

/IWFND/50000073    Configuration of RFC Connections    SM59

/IWFND/50000074    Trust Manager:Display    STRUST

/IWFND/50000075    bgRFC Configuation    SBGRFCCONF

/IWFND/50000076    bgRFC Monitor    SBGRFCMON

/IWFND/50000077    Business Communication Services - Administration    SCOT

/IWFND/50000078    Directory Service Connection    LDAP

/IWFND/59000010    Cleanup Notifications    /IWFND/NOTIF_CLEANUP

/IWFND/59000011    SAP Netweaver Gateway Virus Scan Profile Configuration    /IWFND/VIRUS_SCAN

/IWFND/59000012    Creating Badi    SE18

/IWFND/59000013    Creating Badi    SE18

/IWFND/59000018    SAP Netweaver gateway : Error Log    /IWFND/ERROR_LOG

/IWFND/59000019    SAP Netweaver gateway:Tracing Tools    /IWFND/TRACES

/IWFND/59000020    SAP Netweaver Gateway Application Log Viewer    /IWFND/APPS_LOG

/IWFND/59000021    Simple Job Selection    SM37

/IWFND/59000022    Creating Badi    SE18

/IWFND/59000023    Context based SAP System Alias Configuration

/IWFND/59000024    (BADI Implementation)(Implementations for Badi Definition

/IWFND/59000025    Parallelization for Multiple Origin Composition    /IWFND/MOC_PARALLEL

/IWFND/59000026

/IWFND/59000027

/IWFND/99000004

/IWFND/99000005

/IWFND/99000006     Enable or Disable Soft State

/IWFND/APPS_LOG    SAP Gateway Application Log Viewer

/IWFND/BULK_USER_MAP    Transaction to Perform Bulk User M

/IWFND/CACHE_CLEANUP    Cleanup of Model Cache

/IWFND/CLEANUP    Execute Cleanup

/IWFND/CLEANUP_JOBS    Manage cleanup jobs

/IWFND/CRE_DEF_JOBS    Create Default Cleanup Jobs

/IWFND/ERROR_LOG    SAP Gateway Error Log

/IWFND/ERROR_LOG_E2E    SAP Gateway Error Log - E2E

/IWFND/EXPLORER    Service Explorer

/IWFND/GW_CLIENT    SAP Gateway Client

/IWFND/INIT_CCMS    Initialize SAP Gateway CCMS Contex

/IWFND/IWF_ACTIVATE    Activate / Deactivate SAP Gateway

/IWFND/MAINT_SERVICE    Activate and Maintain Services

/IWFND/MED_ACTIVATE    Activate/Deactivate Metadata Cache

/IWFND/MED_SA_ACTIV    Activate system alias based cachin

/IWFND/MOC_PARALLEL    Parallelize Multi-Origin Compositi

/IWFND/NOTIF_CLEANUP    Cleanup Notifications

/IWFND/NOTIF_MONITOR    Notification Monitor

/IWFND/SERVICE_TEST    Service Explorer

/IWFND/SOFTSTATE    Enable or Disable Soft State

/IWFND/STATS    SAP Gateway Statistics

/IWFND/TRACES    SAP Gateway Traces

/IWFND/V4_PUBLISH    SAP Gateway Service Publication

/IWFND/VIEW_LOG    SAP Gateway Application Log Viewer

/IWFND/VIRUS_SCAN    Configuration of SAP GW Virus Scan

/IWFND/WF_WEBGUI    WebGUI For Executing Workflow Item

/IWFND/WSS_SETUP    Configure WS Message-Based

SAP BackEnd  Specific T-codes:

/IWBEP/57000001    Configuration of RFC Connections    SM59

/IWBEP/57000002    Gateway Settings

/IWBEP/57000004    Event Definition

/IWBEP/57000005    Choose Activity

/IWBEP/57000006    Event Type Linkages

/IWBEP/57000007    bgRFC Configuration    SBGRFCCONF

/IWBEP/57000008    bgRFC Monitor    SBGRFCMON

/IWBEP/57000009    Check Configuration Report    /IWBEP/CONFIG_CHECK

/IWBEP/92000002    Maintain Model    /IWBEP/REG_MODEL

/IWBEP/92000003    Maintain Service    /IWBEP/REG_SERVICE

/IWBEP/92000004    Simple Job Selection    SM37

/IWBEP/92000005    SAP Netweaver Application Log Viewer    /IWBEP/VIEW_LOG

/IWBEP/92000006    Clean Up of Model Cache    /IWBEP/CACHE_CLEANUP

/IWBEP/92000007    BADI Creation    SE18

/IWBEP/92000009    Program SRT_WS_IDP_CUSTOMIZE    WSIDPADMIN

/IWBEP/92000012    BADI Creation    SE18

/IWBEP/92000013    Implementation for BADI Definition    SE18

/IWBEP/92000014    BADI Creation    SE18

/IWBEP/92000015    BADI Creation    SE18

/IWBEP/92000016    User Request Management - Application Configuration

/IWBEP/92000018    User Request Management - Cleanup Report    /IWBEP/UR_CLEANUP

/IWBEP/92000019    User Request Management - User Category

/IWBEP/92000020    Role Maintenance    PFCG

/IWBEP/92000021    Role Maintenance    PFCG

/IWBEP/92000022    Role Maintenance    PFCG

/IWBEP/92000023    Maintain Annotation Models    /IWBEP/REG_VOCAN

/IWBEP/92000024    User Self Service Remote Destination Configuration

/IWBEP/92000025    Range Maintenance : GW User Self Service    /IWBEP/UM_NR_INT

/IWBEP/92000026    Parallelization of Batch Queries    /IWBEP/BATCH_CONFIG

/IWBEP/97000002    Display Models

/IWBEP/97000003    Gateway Log Level for the Application Log

/IWBEP/97000004    User Maintenance    SU01

/IWBEP/97000005    Structure of the GW CCMS Context

/IWBEP/97000007    Generate ODATA Channel Implementation    /IWBEP/IMPORT_MODEL

/IWBEP/99000004    Program /IWBEP/R_COS_CLNUP_JOB_CREATE    /IWBEP/CRE_DEF_JOBS

/IWBEP/99000005    Simple Job Selection    SM37

/IWBEP/ANA_SRV_GEN    Analytics Service Generator

/IWBEP/BATCH_CONFIG    Batch Parallelization

/IWBEP/CACHE_CLEANUP    Cleanup of Model Cache

/IWBEP/CLEANUP_JOBS    Manage Cleanup Jobs    SM37

/IWBEP/CONF_SERVICE    Configuration for IWBEP services

/IWBEP/CONFIG_CHECK    Check Configuration of BEP

/IWBEP/CRE_DEF_JOBS    Create Default SAP GW Cleanup Jobs

/IWBEP/ERROR_LOG    SAP GW Backend Error Log

/IWBEP/ERROR_LOG_E2E    SAP GW Backend Error Log - E2E

/IWBEP/IMPORT_MODEL    Service Description File Importer

/IWBEP/NOTIF_MONITOR    SAP GW Backend Notification Monitor

/IWBEP/OCI_SRV_GEN    OData Srvc.(SAPGW)Generator for OSCI

/IWBEP/REG_MODEL    Maintain Model

/IWBEP/REG_SERVICE    Maintain Service

/IWBEP/REG_VOCAN    Maintain Vocabulary Annotations

/IWBEP/RFC_BOP_DEL    OData Channel : Delete RFC BOP

/IWBEP/RFC_BOP_GEN    OData Channel : Generate RFC BOP

/IWBEP/SB    SAP Gateway Service Builder

/IWBEP/SBS    SAP Gateway Service Builder Setup

/IWBEP/TRACES    SAP GW Backend Traces

/IWBEP/UM_NR_INT    MGW Number Range Interval

/IWBEP/UR_CLEANUP    User Request Clean Up

/IWBEP/V4_REGISTER    SAP Gateway Service Registration

/IWBEP/VIEW_LOG    SAP Gateway Log Viewer

/IWBEP/WS_BOP_DEL    OData Channel : Delete WS BOP

/IWBEP/WS_BOP_GEN    OData Channel : Generate WS BOP

Extras:

(01)How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?:

click the link below to access the document:

How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?

(02)How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page?:

click the link below to access the document:

How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page[Doc]?

(03)How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad:

click the link below to access the document:

How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad[Doc]?

[Note: This list will be further categorized and updated in the future]

SAP Web IDE (previously SAP River RDE) is a browser based development tool for SAP UI5

SAP's Browser-Based Development Tool for SAP Fiori / SAPUI5

SAP Web IDE is an extensible cloud-based development environment with a growing set of embedded tools covering the end-to-end development process. With it, you can rapidly design, build, and deploy SAP Fiori applications based on SAPUI5. The new Hybrid Application Toolkit plugin enables development and deployment of hybrid apps.

The full functionality is available on SAP HANA Cloud Platform, where you can benefit from the latest features of the SAP Web IDE trial and productive versions without the need of a local installation. This is the focus of the SAP Web IDE delivery.

We additionally offer this local trial installation of SAP Web IDE 1.12 for test and evaluation purposes. You can experience the SAP Web IDE capabilities and see how simple it is to create and extend SAP Fiori/SAPUI5 applications with SAP Web IDE.

Please note: This is a trial version for non-productive usage only. This version is not updated with the latest features in the way the SAP HANA Cloud version is. It contains a subset of SAP Web IDE functionality, leaving out cloud-specific features such as plugin/template development, consumption of optional plugins and collaboration support.

Please note: This page was updated on 29. July 2015 with the new version SAP Web IDE 1.12 / Hybrid Application Toolkit 1.5. Previous comments might be outdated.

Install the Local Trial Version

• Download the software zip file and unzip it.

The zip contains the SAP Web IDE 1.12 (updatesite.zip - do not unzip this file) and the installation file for the SAP Web IDE Hybrid App Toolkit 1.5 add-on.

• Download the developer guide (PDF).

The Setting Up SAP Web IDE chapter will provide instructions on how to install SAP Web IDE.

You want the full cloud experience?

• Trial usage: https://hanatrial.ondemand.com -> Log On -> Subscriptions -> webide -> Application URL
• Productive usage: SAP HANA Cloud Platform or SAP Store

An alternative path to access these documents is starting the SAP Help Portal for EWM:

http://help.sap.com/extendedwarehousemanagement

Click on SAPEWM 9.0.

Click on Additional Information.

Navigate to How-To Guides.

Open folder 03_Technical Information.

Executive Summary

Event represents occurrence of an occasion in the real world that can have significant effect on the demand history. Identifying these events and removing their effect from demand history is essential to achieve good quality forecast. In enhancement package 2 of SAP SCM 7.0 demand influencing systematic and unsystematic events can be modeled. These events are based on event types that describe their meaning, rule of recurrence and length in a specified bucket size.

Promotions and Event Planning has the following business benefits:

• In many industries especially consumer goods, promotions and events have a huge impact on sales volumes. This functionality helps in adjusting the sales history to obtain non-promoted historical data for the baseline forecast.
• It provides the business ability to determine forecast with or without promotions/events effect.

Functional Overview

There is an existing functionality of promotion planning in APO DP to plan promotions. The event generation functionality differs with the promotion planning functionality in the following way:

In the existing promotion planning functionality with in APO DP, you create promotions in absolute quantity or in percentage (e.g. % of forecast) manually in the planning book. You choose the characteristics for the planned promotion and assign them to the promotions. The promotions for future periods can be recreated using promotion patterns that occurred in the past. However, in this functionality the input that is stored in the promotion key figure is all manual whether defined in absolute or percentages.

The historical data can also be corrected considering past promotions and outlier correction based on settings in the forecast profile. However, this correction is based on the manual quantities stored in the promotions.

On the other hand, the automatic event generation functionality explained in this whitepaper, enables the system to automatically detect the outliers and variations from the historical data based on the event type concept. In the event type you describe its meaning, rule of occurrence, length and periodicity. System then automatically identifies the impact of events on historical data based on its definition and the configuration settings for outlier detection and threshold percentages explained in this paper. The system can also estimate future events based on the identified historical events.

Unlike existing promotion planning, the price change events generation can also be modeled using this functionality wherein the short-term effect of price change on demand can be estimated by the system.

Process Description and Flow Diagram

Event types define the concept of an event. For example, if the Thanksgiving 2015 is an event, the event type is Thanksgiving. The event types have the periodicity (day, week or month) and duration defined. You can also specify the periods before and after occurrence of the actual event where the demand is impacted.

The event types can also be reoccurring; you can define the event type reoccurrence based on the following:

• A simple recurrence definition (for example, the 15th of every second month)
• A holiday from a holiday calendar (for example, Christmas) - This is relevant for moving events e.g. Easter, which can shift depending on the year.

Event types can be assigned to event catalogs. Event catalogs are basically the hierarchical groupings of event types.

For example:

• US Public Holidays (Event Catalog)

• Thanksgiving (Event Type)
• Christmas (Event Type)

The planning processes that can be configured to consider event types and event catalogs are univariate forecasting, outlier detection, and interactive demand planning. The short term effect of price changes on the demand can also be modeled and can be used to estimate effect of planned price changes in the future.

The below process flow diagram shows the demand planning process. The event generation functionality influences the processes highlighted in red boxes.

1. Clean Historical Data: In this process step, the events are identified from the historical data using event generation functionality.

2. Generate Baseline Forecast: Baseline forecast is generated based on the cleansed history from point 1.

3. Forecast Adjustments based on Promotions: Future events can be estimated which can be used for forecast adjustments.

Design Consideration& Configuration

The planning processes that can be configured to consider event types and event catalogs are univariate forecasting, outlier detection, and interactive demand planning. To use the automatic event functionality, business function SCM_APO_FORECASTING_1 (SCM-APO-FCS, Events and Outliers, Causals, ABC/XYZ Classification) must be activated.

After activating the above business function, additional t-codes related to events functionality are available in the SAP easy access menu:

The below diagrams show the configuration steps needed for setting up Automatic Outlier Detection and Event Generation and Price Event Generation functionalities:

The below diagrams show the event history key figure in demand planning book where the automatically identified events are written to cleanse the raw sales history.

To define, edit and delete events, event types and event catalogs:

Advanced Planning and Optimization > Demand Planning > Environment > Demand Planning Worklist

Event types are assigned to event catalogs for hierarchical groupings:

To configure how you want the system to detect events and estimate future events, follow the below menu path in customizing-

Advanced Planning and Optimization > Supply Chain Planning > Demand Planning (DP) > Basic Settings > Events and Outliers > Configure Outlier Detection and Event Catalog Assignments

Here you can configure the settings as shown in the figures below:

Within outlier detection profiles, you define the lower and upper thresholds in percentages for assigning a specific event type to an outlier during outlier detection.

In the next node, you define your planning area and planning levels on which you want the system to detect events.

Note: You can define only one planning level for a planning area.

Planning levels are defined in a separate t-code- Advanced Planning and Optimization > Demand Planning > Environment > Current Settings > Specify Planning Levels

The below figure shows that the planning level is defined at the channel-item characteristics level.

Note: When you create a planning level, make sure that the sequence of the characteristics reflects a hierarchical relationship, from general to specific. Additionally, the promotion planning level must be the last level in the planning level definition.

Outlier Detection Periods: Here you specify the number of periods you want the system to consider before the actual period when it calculates the actual period's moving average during outlier detection.

Event catalogs are assigned to planning area in the next node:

For configuring the future event generation, you specify the event type, number of historical events and calculation method for estimating the effect of historical events on future events.

Automatic Outlier Detection and Event Generation Report

You use this report to identify the impact of different events on the historical demand. The system searches for outliers in the historical demand based on the settings defined in the customizing. After you have run the report, you can use these system identified events during forecasting to estimate the impact of future events. Additionally, you can clean the history from the impacts of events during forecasting.

Advanced Planning and Optimization > Demand Planning > Planning > Promotion > Automatic Outlier Detection and Event Generation Report

In forecasting also, you can specify that you want the system to consider the events created by the Automatic Outlier Detection and Event Generation report. This means that the system removes the effects of the events from the history that serves as the basis of forecasting.

You can also configure forecasting so that the system estimates the future occurrences of event types based on the average value of past events of the same type. On the Univariate Profile tab page, in the Event Types screen area, select the Estimate Automatically checkbox.

Pre-requisites for running the report:

Before running the automatic outlier detection report, ensure the following:

• You have assigned a key figure to save the impact of events and maintained the promotion level for your planning area. Since the effects of events can be either negative or positive relative to the actual sales history, you should allow the system to store negative values in this key figure.

• You have defined a planning level in customizing.

• You defined settings in “Configure Outlier Detection and Event Catalog Assignments” e.g. outlier detection profiles, event catalog assignment to planning area as mentioned in section 2 above

Outliers Detection Logic

The system takes the demand history in the specified time horizon as the basis for outlier detection. If a certain combination does not have a history at the beginning or at the end of the horizon, the system adjusts the outlier detection horizon by removing the periods that do not have historical data from the beginning and from the end of the horizon.

The system calculates a moving average for the number of periods configured in Customizing, and checks if the period currently processed reaches the threshold you defined in the outlier detection profile.

The system processes the outliers by order of magnitude, which means that it first corrects the history for the period that has the largest deviation. This iteration makes sure that the outliers that would otherwise distort the moving average are handled first.

Mass Creation of Events

You use this report to create events for a specified period that is either in the future or in the past. You can create an event with the same parameters for multiple planning objects. After you have run the report, you can use the events the system has found, during forecasting to estimate the impact of future events. Additionally, you can clean the history from the impacts of events during forecasting.

• If the event date you specified lies in the future, the system calculates the event's impacts based on the historic events of the same type.
• If the event date you specified lies in the past, the system calculates the event's impacts from the historical data.

Example:

The event date is Nov 27, 2014 and you have defined event type in monthly buckets. In the occurrence definition of the event you define effect of the event 1 period before and 1 period after the actual event date and the actual event duration is 1 period long.

In this case, the system generates the event starting from Oct 1, 2014 which lasts for three periods.

Future Events Estimation

The system determines the impact of events in the past to estimate the events in the future. The system performs future event estimation every time you run forecasting, or manually create or delete a historical event.

The system estimates future events if the following prerequisites:

• You have maintained the settings for future event estimation in Customizing
• There are historical events in the system based on which the system can calculate future events
• You have created events in the future horizon that the system re-estimates during future event estimation, or selected the Estimate Automatically (Estimate Future Recurring Events Automatically) checkbox in the univariate forecast profile settings.
• You have specified all other settings as mentioned above in figure 1.

Price Change Events

Price change events model the short term impact of price changes on the demand. The system can estimate the price change events based on the changes in the price key figure. For example, demand might rise directly before a price increase, and drop directly after it.

In the Automatic Outlier Detection and Event Generation report, you can have the system create price change events in the past, based on historical price and demand data. The system uses the effect of the price change events in the past to estimate the short-term effect of planned price changes in the future, and uses the results in forecasting.

The following are the pre-requisites for using the price change detection functionality:

Settings in Planning Area:

• Configure price settings. Define here the price key figure, price change event type and price change threshold %. For price change event type field, you should select a non-recurring event type that you have created in demand planning worklist.
• The bucket you use to define the event type duration (for example, week) must match the bucket you use to detect price change events in the Automatic Outlier Detection and Event Generation report.
• In the Price Change Threshold field, you specify a threshold value in percentage. The system detects price change events in periods where there is a (positive or negative) change in the price key figure compared to the previous period that is greater than the threshold value in percentage you specify.

Settings in Forecast Profile:

• The bucket you specified in the Period Indicator field of the master forecast profile must match the bucket you use to detect price change events in the Automatic Outlier Detection and Event Generation report.
• You must specify an MLR profile in the MLR for Univ. Fcst (MLR Profile for Univariate Forecasting) field of the univariate forecast profile. The MLR profile you specify must contain the price key figure in the MLR independent variable list.
• You can specify a price change threshold in the field Price Change Threshold in the univariate forecast profile. If a value is entered here, it overrides the value set in the planning area forecast settings described above, for CVCs that have this univariate forecast profile assigned.
• During the calculation of price change events, the system only applies seasonal correction in case the Periods field of the univariate forecast profile is filled, and the detection time interval you specified for the Automatic Outlier Detection and Event Generation report contains at least twice as many periods as you specified in the Periods field in the univariate forecast profile.

Deletion of Events and Event Types

You can delete events, event types, and event catalogs using any of the following ways:

• From demand planning worklist
• From Interactive demand planning
• Using report: Delete Event Types with Dependencies
• Using report: Mass Deletion of Events

Demonstration

Scenario 1: Mass Creation of Events

The figure below shows the historical data for a product in the planning book. You see that there is an increased demand during the Thanksgiving and Christmas periods in year 2014. We have created an event key figure in the planning book to store the generated events.

Program creates the 3 period long event as defined in the event type and based on the configuration settings explained above.

In the planning book, events are created for the period W51/2015, W52/2015 and W01/2016.

Events displayed with promotion ID in the planning book:

Scenario 2: Future Events Estimation

The system calculates the future events based on the historical events of the same type. You specify the event date in the future in the report for mass creation of events.

The future event calculation is based on the configuration settings done in “Configure Outlier Detection and Event Catalog Assignments” as explained above.

Scenario 3: Automatic Outlier Detection and Event Generation

In the below screenshot, the automatic event detection is executed for event type “Thanksgiving”. The event is detected and calculated by the program based on the customizing settings in “Configure Outlier Detection and Event Catalog Assignments” as explained above.

Program logs:

Event created in planning book with promotion ID:

Scenario 4: Price Change Event Generation

Automatic event generation report can also be used for detecting and generating price change events as explained above.

Settings needed for price change event detection:

You define a non-recurring price change event type and maintain price settings under forecast settings for planning area.

Create an MLR forecasting profile with price key figure as independent variable and assign this MLR profile to the univariate profile under “Combination with MLR” section.

Assign the MLR profile in the univariate profile:

Price change events are detected and generated based on the changes in the price key figure and threshold% defined in the planning area or forecast profile.

Limitations

• You can use only 1 planning level per planning area. E.g. If you specify your planning level as Product-Channel-Market characteristics, you cannot use another planning level with different characteristics in the same planning area.
• During forecasting, only events with the relevant bucket size are considered. E.g. When forecasting in weekly buckets, the events with weekly periodicity are only considered.
• Mixed buckets are not allowed in the data view in which events are to be used.
• Price change events cannot be created manually. However, these can be deleted.
• In Interactive Planning or with the mass event creation report it is not possible to create historical events outside the historical horizon of the assigned forecast profile.
• The characteristic for promotion level has to correspond to the lowest level of the characteristics that you use in your planning level. That is, the characteristic for promotion level has to be the last characteristic in the planning level characteristic sequence.
• When the system creates multiple events that are overlapping, only one event gets the full uplift value and all the other events that overlap this event will get 0 or a very small number for the uplift value. The event identified as being the most significant will get the full uplift.

Conclusion

Ability to identify variations and outliers from historical data is essential to achieve good quality forecast. The event functionality as of SAP SCM 7.0 EHP2 can help identifying these variations based on the event type definitions. Estimation of future events can also be modeled based on the past events. The short term effect of price changes on the demand can also be modeled and can be used to estimate effect of planned price changes in the future.

Abbreviations / Acronyms

References

http://help.sap.com/SAPHELP_SCM700_EHP02/helpdata/EN/4d/33d7f2db9e00d3e10000000a42189b/frameset.htm

SAP Note: 1405656 - Implementation recommendations for SCM 7.0 APO DP

SAP Note: 1618890 - Implementation recommendations for EhP 2 of SAP SCM 7.0 DP

SCM220- Demand Planning: mySAP Supply Chain Management

SAP Predictive Analytics incorporates two different approaches for carrying out predictive modelling

• Automated Analytics: A highly automated framework that enables non-Data-Scientists to quickly create powerful models without deep statistical expertise. This functionality was formerly known as SAP InfiniteInsight.
• Expert Analytics: A graphical workbench for expert users to design specific analytical workflows. This functionality was formerly known as SAP Predictive Analysis.

This website gives an overview on how to extend the "Expert Analytics" functionality. Power Users can extend and customise the functionality of the *Expert Analytics"-mode by adding their own R-Scripts. The logic is encapsulated in so called “Custom R Components”, which casual users can easily work with without having to have any R skills.

This page is pointing to a number of documents that help create such components. It is also linking to various components that have been published on the web and that can be quickly implemented.

Please note however, that the code on these pages is not supported by SAP and that it is provided without any warranty.

We all came across the scenario where material master has to be sent to external system whenever there is a change in particular fields. So we generally achieve this by configuring the change pointers for message type and all the necessary configuration. Now we execute BD21 for our message type, which will generate the material master idoc only with mandatory segment and then only the segments which have changed fields.

That was simple and everything was a standard process but if there is a requirement to send the material master details in full even one field is changed then we cannot use this standard approach so we may end up in developing a custom function module to create a idoc with all the segments.

This document will explain a way to create material master using BD10 transaction, SAP has provided a several Explicit Enhancements in the program RBDSEMAT

we can make use of those enhancements to modify the selection screen and to call the function module CHANGE_POINTERS_READ before creating the idoc and CHANGE_POINTERS_STATUS_WRITE after creation of idoc.

Step 1 - We need to modify the selection screen so that a option is provided to create the idoc using change pointers

If you don not want the title of the frame, then no need to create a second enhancement which populate the frame title

Step 2 - Enhancement AT SELECTION-SCREEN OUTPUT, to populate field label GC_CHG and to retrieve the materials using CHANGE_POINTERS_READ

Step 3 - The above step will populate the materials which are not yet processed in the ECC system, Once the Idoc is generated for the relevant materials you have to change the status of change pointers

Result - Modified Selection Screen

Once you execute the program, Idoc gets created for all the Materials and then status of the change pointers are updated as 'Processed'

Currently, I did this enhancement to trigger the MATMAS idoc. Code can be modified accordingly to process ARTMAS, MATCOR etc idocs

On this page you will find free, open sourced visualization extensions developed by SAP employees and SAP community members: All ready for you to download and deploy!

For other extensions developed by SAP Analytics Partners, check out the Extension Marketplace.

How-to use

These extensions from GitHub are readily available for download and install to work with the latest version of SAP Lumira.

1. Simply download the extension (.zip) and the dataset (.csv), and check out the ReadMe notes for specific instructions on how to use each extension.
2. Install the extensions in Lumira using the Extension Manager (File-> Extension Manager OR Ctrl+J), restart Lumira and play around with the data and the extension!
3. Also, don't forget to check out the blogs written by the developers about the extensions!

Please read the disclaimer at the bottom of this page.

COUNTRY VISAS (Chart with Tooltip and Image)		IoT DATA INTEGRATOR AND VISUALIZATION
Blog |GitHub | Team Limitless SAP Lumira BizViz Hackathon Entry		GitHub| Team Siesta SAP Lumira BizViz Hackathon Entry

POPULATION PYRAMID CHART		HORIZONTAL MEAN POINT BAR CHART
Blog| GitHub | Dong Pan		Blog | GitHub | Xin Wen

EXTENDED BAR CHART		BULLET CHART
Blog| GitHub | Jay Thoden van Velzen		Blog | GitHub| Matt Lloyd

AFFINITY		LOSS INCIDENT OPTIMIZATION
GitHub | Shailesh Borkar		GitHub | Vidur Bhatnagar

INTERACTIVE BULLET CHART		DYNABARS
GitHub | Ankush Mehta		Blog| GitHub| Shiney Sooraj

FORECAST WITH 80% AND 95% CONFIDENCE INTERVALS		FORECAST WITH SINGLE CONFIDENCE INTERVAL
Blog | GitHub|Jay Thoden van Velzen		Blog | GitHub | Jay Thoden van Velzen

HOLT-WINTERS EXPONENTIAL SMOOTHING		LINE CHART WITH ZOOM
Blog | GitHub|Jay Thoden van Velzen		GitHub |Vidur Bhatnagar

3D WORLD		CRIME WATCH
Blog| GitHub | Vincent Dechandon		GitHub | The A-Team SAP Lumira BizViz Hackathon Entry

GOOGLE MAPS HEATMAP		INTEGRATING GOOGLE MAPS
Blog | GitHub | Mustafa Aydogdu		Blog | GitHub | Julien Delvat

GEOEXTENSION		CUSTOM CHOROPLETH MAP OF JAPAN
Blog |  Manfred Schwarz		Blog | GitHub | Robert Russell

POWER FLOW MAPS		GEOMAPS LEAFLET
Blog | GitHub | Jay Thoden van Velzen		Blog| GitHub | Mustafa Aydogdu

BUSINESS BUBBLES		STACKED COLUMN WITH LINE CHART
GitHub | Team Business Bubbles SAP Lumira BizViz Hackathon Entry		Blog | GitHub| Dong Pan

CAPACITY PLANNING CHART

Blog | GitHub| Jay Thoden van Velzen

Disclaimer:

Try, modify, re-submit to the community

We encourage you to submit your own Lumira extensions to help our community grow  - and to get recognized for your efforts. You already have open sourced a viz extension and want it to be added here? Simply let us know by posting a comment right here.

The deal with Open Source

• There is no official support for any of these extensions; the only support comes from the developer or the community (you)
• All extensions listed below come with a use-at-your-own-risk policy
• Many extensions are built for very specific use cases. You get the source code and can modify to fit your needs: please re-submit to everyone's benefit!

The deal with extensions from SAP employees
Some of the extensions are developed by individuals in their spare time that happen to be employed by SAP; we publish these extensions on github.com/sap.  None of these are official SAP software and there is not standard SAP support or documentation that comes with them

SpecialMovementIndicator:

It is always possible to influence the movement of material within WM via the special movement indicators. You can assign another movement type in the Warehouse Management System (WMS) to a movement type from Inventory Management using this indicator.

Since you can specify interim storage areas and interim storage bins within the WM movement types, you can determine which interim storage areas and bins will be selected in WM for a goods movement depending upon the special movement indicator used. You can thereby actively influence the interface between Inventory Management (IM) and Warehouse Management (WM).

CONFIGURATION

First Step:

As a part of Configuration, First Step is to Create the Special Movement Indicators in the below Path:

Logistics Execution --> Warehouse Management --> Master Data --> Material --> Define Special Movement Indicators

Created Special Movement Indicator ‘Z’ – Test.

Second Step:   Assign the WM Movement type to the newly selected Special Movement Indicator.

First assign the reference Movement type to Inventory Management Movement type

Logistics Execution --> Warehouse Management --> Interfaces --> Inventory Management --> Define Movement types --> Assign WM Movement Type References to IM Movement Types

IM Movement type 101 is assigned to Reference Movement type 101.

Then Assign the Warehouse Management reference to the Warehouse Management Movement type.

Logistics Execution --> Warehouse Management --> Interfaces --> Inventory Management --> Define Movement types --> LE-WM Interface to Inventory Management

WM Movement type 105 is assigned to the reference movement type 101 for Movement Indicator B Warehouse 008.

For the 101 Movement type at Inventory level, the Warehouse Movement would be 105 for all Materials with Special Movement indicator ‘Z’ . For others it would be 101.

Step 3:  Define Warehouse Movement type

Now Define the Warehouse Movement # 105 as per your requirements.

Logistics Execution --> Warehouse Management --> Activities --> Transfers --> Define Movement types

Step 4: Define the Storage type Strategies to determine the receiving Storage type based on the Reference storage type search as defined the Warehouse Movement type.

In the below Config, I have assigned Storage type EXW for Warehouse 008, Storage type Indicator 200 and Reference Storage type search 105

Logistics Execution --> Warehouse Management --> Strategies --> Activate Storage type Search

  Master Data

Maintain the below settings in the Material Master [WM View 1] for the warehouse# 008 as per above Configuration.

Special Movement Indicator – Z and the Storage type Indicator for Stock Placement – 200

With the above Configuration and the Master data, All the Materials received with Special Movement Indicator ‘Z’ would move in to Storage type EXW.

Dear Friends,

This document contains process to cover closing of delivery documents as well as reversal process of documents in the SYSTEM.

While users are creating delivery documents in the system, but sometimes USER don’t deliver the documents and even USERs don’t process further.

To close all the open deliveries below are the process to close the same.

STEP: 1 MONITORING OF OPEN DELIVERIES

First user has to see all the open deliveries through VL06O

Where USER has to check in both Activity “FOR PICKING” as well as “FOR PGI/PGR” report as per PROCESS DOCUMENT for “Monitoring of Delivery document.

Once USER will identify the deliveries he needs to check below things to close the deliveries:

If document is OPEN which need to delete in the system he has to go to VL02N

Scenario: 1 OPEN DELIVERIES:  PICKING is not done as well as PGI/PGR is not done in the system.

USER has to DELETE the deliveries

Scenario 2: OPEN Deliveries: PICKING is done but PGI/PGR is not done in the system.

Here user has to first make it Picking QTY as 0 AND delete the deliveries as per SCENARIO: 1

Scenario: 3 BEING PROCESSED: PICKING & PGI/PGR both done but Invoice has not been done.

In this scenario USER has to first “REVERSE the PGI/PGR as once the “GOODS MOVEMENT done stock & stock value will be affected in the system.

1.     REVERSE PROCESS OF PGI & PGR

To reverse the same USER has to GO TO Tcode VL09 and user has to enter the delivery document as shown below:

Here user has to enter the Shipping Point as well as Delivery/Return delivery number & select on the first radio button

After entering above data USER has to execute the transaction below SCREEN will appear.

USER will select the screen and will CLICK on the “REVERSE” button to process further.

Again the system will ask for confirmation and CLICK on the button and confirm the same.

Once USER will confirm the same

Now once the goods movement reversed status of the same will be changed from C to A

Now go to document flow USER will be able to see the REVERSEL DOCUMENT in flow through VL02N

Now once the delivery is reversed user has to make its Picking Qty 0 and then do the process as per scenario 1

Scenario: 4 Completed: PICKING & PGI/PGR both done & Invoice is also done

Tcode: VF11

If you have sales invoice under that delivery - you need to cancel billing doc. using VF11.

Enter the Billing Document number in VF11 transaction

Once you PRESS ENTER below screen will appear

Once USER will CLICK on the “SAVE” button cancellation document will be generated.

Now go to document Flow cancelled document will be reflect in the flow and status of the delivery will be changed

Now reverse the goods movement document and follow the steps as per SCENARIO 1& SCENARIO 2

2.     REVERSEL PROCESS IN RECEIVING PLANT :

Scenario: 1 When Goods receipt in the receiving plant (Bakery), but invoice is not posted as shown in below mentioned PO.

If we realize that any mistake is done during Goods Receipt or any earlier process then we can cancel this goods receipt through MIGO Transaction as shown below because we have not posted invoice yet.

Step 1: Cancel Document in MIGO as shown below.

Now you can see the cancelled document is updated in the PO History as shown below.

Scenario: 2when after goods receipt invoicing is also posted then you have to cancel the invoice 1^st which was equivalent to your Credit Memo Follow the steps as shown below.

Step 2: Here we will first cancel (Credit Memo) invoice as shown below through MR8M Transaction. Enter the invoice document no, fiscal year, reason of cancellation and posting date for cancellation. And click on Save/ Reverse icon.

Step 3:Now we can cancel the goods receipt of the material as shown below through MIGO as shown below. Enter the Material document no., Item ok indicator and save the document.

Reporting of intercompany P.O : To check the PO STATUS use ME2N as shown below, you will come to know about the Material to be delivered and to be invoiced. If you want to know about intercompany PO only you can run the report by restricting from the vendor code.

Execute (F8)

Dear Friends,

This document is for Daily Monitoring of deliveries which USERS are processing on day to day basis.

Whenever store person wants to create any delivery with reference to order created by Sales team, USER has to check the DAILY LOG as per below STEPS

STEP: 1 MONITORING OF SALES ORDER/PURCHASE ORDER WORK LIST

Transaction code: VL04

First user has to go to VL04 T Code where Store person will get all the Pending orders which are due for delivery:

User can select the Input Parameter as per their requirement to create delivery, Once user enters the screen he can select the orders one by one and can create the delivery as per below process.

If user doesn’t want to create deliveries one by one he can click on the “DESELECT ALL” to create the deliveries individually.

Again User can Select the Delivery and CLICK on the INDIVIDUAL DELIVERY to Process the same.

Once the user will do above process he will directly go to Delivery creation screen (VL01N) and Process the same.

STEP: 2 OUTBOUND DELIVERY MONITOR (MONITORING OF ACTIVITIES)

Transaction code: VL06O

Now While USER is processing the Deliveries they have to do two activities in the delivery:

1. PICKING for every Material in PICKING TAB
2. PGI/PGR for the delivery to transfer the ownership of the GOODS

Now once the Delivery is created in the system, User has to check it’s all ACTIVITY LOG for their created delivery in the system.

STEP: 2.1 PICKING ACTIVITY (MONITORING OF ACTIVITIES)

Transaction code: VL06O (FOR PICKING TAB)

First Go to Transaction VL06O

Now first USER has to see its Picking Activity pending for the day CLICK on the PICKING below screen will appear.

Below are the four parameters which user has to take care as per below screenshot:

1. Shipping Point is mandatory
2. Picking Date should be till date (Enter To date as current date)
3. Picking Data (Check on Only Picking Without WM)
4. Output proposal data keep Picking List as “BLANK”

USER can insert additional parameter as per their requirement

Once user will enter all the Data below List will appear whose PICKING ACTIVITY is pending in the system (Day’s Workload for Picking)  as shown below:

Now user has to CLICK on the delivery number and CLICK on the ICON for (change outbound delivery)

Once USER will do above process below screen will appear and USER has to CLICK on the Picking TAB and he has to finish the PICKING activity (VL02N)

Here once USER will finish the ACTIVITY and he can also do the PGI/PGR from the SAME SCREEN as “UNLESS & UNTILL user will not do PICKING in the Delivery, SYSTEM will not allow USER to do PGI/PGR.

After completing the above activities user can once again CROSS CHECK for the same by entering above PARAMETERS USER will get below message means there is no LOG for PICKING in the SYSTEM

Now USER has to check its second ACTIVITY for created deliveries.

STEP: 2.2 PGI/PGR ACTIVITY (MONITORING OF ACTIVITIES)

Transaction code: VL06O (FOR GOODS ISSUE TAB)

Now again GO TO the main SCREEN of VL06O and CLICK on the “FOR GOODS ISSUE” below screen will appear which is appearing for Outbound deliveries pending for PGI/PGR

USER has to enter below Input Parameters to run the LOG Report:

1. Shipping Point
2. Planned Goods Movement Date( For which USER has to Enter To Date as CURRENT DATE)

After Entering all the Parameters mentioned above below SCREEN will appear where LOG will be generated for PGI/PGR pending deliveries.

Below LIST contains DELIVERY LIST (PGI) as well as RETURN DELIVERY LIST (PGR)

Now USER has to CLICK on the Delivery number and CLICK on the “POST GOODS ISSUE” system will ask for Actual Goods Movement Date.

If LOG is for Current date USER can do PGI/PGR on the same date (Which is Current Date)

If LOG is of previous days (for the same Period) than USER can change he DATES for the selected delivery List.

Once USER will do above PROCESS below message will appear on the SCREEN

By processing all the deliveries one by one USER can clear LOG for PGI/PGR for the same.

Now USER can also see the REPORT of Deliveries with “GENERAL DELIVERY LIST-OUTBOND DELIVERIES”

NOTE:

USER can not EDIT the Delivery Document once PGI/PGR is done in the system.

USER can change the Actual PGI/PGR date while creating the delivery or Editing the Delivery before PGI/PGR in Delivery document.

Once all the Activities completed USER (WHO CREATES BILLING) has to check its LOG through VF04 as shown below:

STEP: 3 MONITORING OF BILLING DUE LIST

TRANSACTION CODE: VF04

USER has to enter the Billing date as CURRENT DATE (To Date)

USER can further select the data as per their requirement like Sales Org. etc

Here user has to check its Billing due List where in Kenblest there are different scenarios:

1. Delivery Related Billing: Here User can create the Invoices based on delivery, wherever Store person has created deliveries for the day all the deliveries will be displayed on the LOG and USER can create the delivery related Billing  as shown below.

Now USER can select the document and can CLICK on the” Individual document” user will go to VF01 screen and same can be processed as per Billing Process

Once USER will do above process user can process the Invoice as shown below and can CLEAR the LOG from the Due List:

1. Intercompany Billing: Here user can process the Billing once the delivery is created from McNeel and user has to select the document as “Intercompany Billing”

USER can process the Billing as shown above and clear the LOG.

Chart of account master in S/4 Hana Finance

In S/4 Hana Finance chart of account master has been changed.

Summary:

In S4 Hana Finance we handle chart of accounts and cost elements using one transaction – FS00.

Transaction KA01 (create cost elements) is no longer in use.

For default account assignments transaction OKB9 has to be used.

We use T Code FS00 and take a look on COA master:

We take a look in detail what values can be entered.

We have one master for chart of accounts including secondary cost elements.

Taking a look in  table SKA1 we can see we have new field –  GLACCOUNT_TYPE

Following data can be entered:

X: Balance Sheet Account

N: Nonoperating Expense or Income

P: Primary Costs or Revenue

S: Secondary Costs

When doing migration to S4 Hana Finance – secondary cost elements have to be handled.

You can see the relevant entry in the migration steps.

@Rishab Bucha

Thank you for your feedback, you are right:

Also statistical cost elements (katyp = 90) are moved to chart of account master.

I am looking for your feedback and discussion.

Thank you

all the best erwin

This page is a continuation from the original Open Source Visualization Extensions page, to showcase the increasing number of visualization extensions contributed by the ever-growing open-source developer community.

PIPELINE BUBBLE CHART		TUBBLE CHART
Blog| GitHub | Xin Wen		GitHub | Mustafa Aydogdu

EXTENDED BUBBLE MATRIX		COMPETITION CHART
Blog| GitHub| Annie Niangneihoi		Blog | GitHub | Florian Stumpe

SALES MAGIC		EXOPLANETS
GitHub | Team Vizards SAP Lumira BizViz Hackathon Entry		Blog| GitHub| Matt Lloyd

SCATTER MATRIX		HEXAGONAL BINNING
Blog | GitHub | Mike Howles		Blog | GitHub | Mike Howles

VANILLA SCATTER		COLOR SLIDE SCATTER
Blog | GitHub | Kristina Pereyra		Blog | GitHub | Kristina Pereyra

QUADRANT

GitHub | Vidur Bhatnagar

FOOTBALL HEATMAP

Blog| GitHub | Mustafa Aydogdu

MINI CHARTS

Blog| GitHub | Mustafa Aydogdu

SCROLLABLE TIMELINE CHART		SUNBURST CLOCK CHART
Blog | GitHub | Xin Wen		Blog | GitHub | Xin Wen

SUNBURST SEQUENCE		SUNBURST ZOOMABLE WHEEL
Blog | GitHub | Annie Niangneihoi		Blog| GitHub | Annie Niangneihoi

DRILLABLE KPI TREE		SWOT ANALYSIS
Blog | GitHub | Jay Thoden van Velzen		Blog | GitHub | Xin Wen

SANKEY DIAGRAM		GAUGES
Blog | GitHub| Dong Pan		Blog | GitHub | Andrew Jabbitt

CHORD CHART		FORCE DIAGRAM
Blog | GitHub | Dong Pan		Blog | GitHub | Dong Pan

LOSS OF SALES		BITCOINS
GitHub| Ankush Mehta		GitHub| Shailesh Borkar

HELLO WORLD EXTENSION

Blog | GitHub | Matt Lloyd

SAP Design Studio - Webinars

The SAP Design Studio webinars offer interactive presentations on a variety of topics.

Content is presented by experts from SAP and our broad partner & customer ecosystem.

• Webinar Dates & Times: Dates are subject to change; webinars will start at 7am PST to cover as many global regions as possible.
• Registration links: will be enabled a few days before the scheduled webinar date.
• Recordings: will be posted no later than a week after the event.

Please subscribe to email notifications for this page: you will receive notifications of any updates, including new webinar content, dates and availability of recordings.

Upcoming Webinars - Registrations			Date	Presenter
		Expert Webinar Design Studio - Enterprise Ready Analytics - Performance, Scale, Troubleshooting	tbd	tbd
		Expert Webinar Beautifying your Application - the latest Design Studio capabilities	tbd	tbd
		ASUG Webinar SDK Experiences: SAP Lumira VizPacker and SAP BusinessObjects Design Studio	Jan 26
		Expert Webinar Developing Extensions using the SAP Design Studio SDK	Feb 11
		ASUG Webinar Using SAP BusinessObjects Design Studio for Self Service BI	Mar 1	Ingo Hilgefort
		ASUG Webinar Design Studio Ready-to-Run Application & Template - registration not open yet	Mar 8
		ASUG Webinar What's new with Design Studio 1.6 Feature Pack	May 10
h
Webinar Recordings			Date	Presenter
		Expert Webinar What's New in Design Studio 1.6? - (recording)	Dec 10
		Expert Webinar Design Studio Advanced Geo Dashboards - (recording)	Dec 3
		Expert Webinar SAP Analytics - Integration of SAP BI Platform and SAP Design Studio - (recording)	Nov 24
		Expert Webinar Feature Deep Dives: Report to Report Interface, Bookmarking and Data Binding (recording | pdf)	Oct 15
		Expert Webinar Advanced Visualizations & Dashboards at Palo Alto Networks, with Archius (recording | pdf)	Oct 01
		Expert Webinar Creating Dashboards with the Ad-hoc Analysis, Generic Analysis, and Data Discovery Templates (recording)	Aug 13
		Expert Webinar An Introduction to Creating Components with the Design Studio SDK(recording)	Jul 30
		Expert Webinar What's new in SAP Design Studio 1.5 (recording | presentation)	Jun 25
		Expert Webinar Creating Effective and Engaging Dashboards and Visualizations (recording)	Jun 17
		Expert Webinar SAP Lumira & SAP Design Studio - When to use which	May 20

SAP Design Studio and Lumira In-Person Workshops:

Upcoming Workshops*:

* If a workshop above does not have a live registration link, please contact your local SAP representative for information about workshop participation

Before diving into the official documentation, read this blog to have an idea of what customers say about their ramp up to 7.3 experiences.

Take a look at the following SAP Notes:

• SAP central note for 7.30
• SAP central note for 7.31
• Deprecated Features in SAP Enterprise Portal

Explore the Performance guidelines:

• Performance Best Practices Guide for SAP NetWeaver Portal 7.3
• SAP NetWeaver Portal 7.3 - Tuning Caches
• Note 1551721 - Performance Tuning of Enterprise Portal 7.30/7.31

Have any custom Portal applications developed? Take a look at the following blogs:

• How To Migrate Custom Portal Applications to SAP NetWeaver 7.3
• Locating Relevant JAR Files When Migrating Custom Applications to SAP NetWeaver Portal 7.3
• Customizing Logon Page on Portal 7.3

If you have Business Packages installed, take a look at the following SAP Notes that describes the overall SAP NetWeaver compatibility including overview of enabled Suite product versions:

• 2156543 - Add-on compatibility of SAP NetWeaver 7.5
• 1850345 - Add-on compatibility of SAP NetWeaver 7.4
• 1532805 - Add-On Compatibility of SAP NetWeaver 7.3

Check the detailed information in the attachments of:

• 1874939 - SAP Business Suite for SAP NetWeaver 7.4 hub systems
• 1698276 - SAP Business Suite for SAP NetWeaver 7.31 hub systems
• 1615463 - SAP Business Suite 7i 2010 for SAP NetWeaver 7.3 hub systems
• 1468349 - SAP Business Suite 7 for SAP NetWeaver 7.3 hub systems

Read this blog for additional explanations.

Details about version interoperability and the supported software update strategies are described here.

If you are using SAP BI take a look at this useful note - Note 1636057 - Upgrade to SAP NetWeaver 7.30: BI Java: Useful note.

If you have ESS/MSS installed check out this blog.

If you've developed custom WebDynpro Java applications the process of migrating WebDynpro Java applications is described here and here.

Introduction:

We want to valuate a wage type named "Holiday Payment - Plant" using the following formula:

(Basic Pay + Dearness Allowance )/30 per day.

Basic pay and Dearness allowances will be maintained in Infotype 0008 (Basic Pay).

Valuation Method:

We can use indirect valuation of wage type using module "UNITS" (Module Variant "B").

This can be created in the configuration view V_T539J (as given below):

In the above configuration, 100/30 = 3.33 (which is entered as Weight column), since we

want to add Basic & Dearness allowance and this total is to be divided by 30 as per our

required formula.

Wage Type Properties of Wage type "9000" defined in Table: V_T511 as given below

(specify the indirect valuation module "UNITS" with variant "B") :

Input Wage types in IT0008 (Basic Pay):

8000 - Basic Pay Value:                 16,800 (INR)

8001 - Dearness Allowance Value: 16,884 (INR).

Output:

Output Wage type 9000 (Holiday Payment - Plant) is maintained in IT0015. When we enter the

"Number/Unit" as 15 Days, the output will be as follows:

Calculation:

(Basic Pay + Dearness Allowance)/30 = (16,800 + 16,884)/30

                                                              = 33,684/ 30

                         Per Day Rate                = 1122.8

                         For 15 Days                  = 1122.8 x 15 = 16,842.00

Disclaimer:

This document is not any kind of reproduction and the example mentioned

here is not a real data. The images used are purely to demonstrate the concept

in a better way to the forum users.

Today (instead of watching pre-Super Bowl festivities) I checked out the SAP Learning Hub at training.sap.com

There are some updated materials for Design Studio if you are a Learning Hub subscriber.

Today was all about Global Script variables.

Source: SAP

From above, global script variables can be used in any script of your application.  See the "Note" that states script variable names used as URL parameters must start with a capital X

The above shows the settings for the global script variable, named "Xmode" and the URL parameter is set to true.

This application has two tabs with a crosstab on each.  I don't have the sorting on the columns enabled.

On the second tab I have a print button

The script on the application start up is shown above.  If the URL parameter mode is display, the user will not be able to see the print button or sort the columns; if the mode is set to navigate the user can interact with the application, see the print button and will be able to sort the columns

The above shows the first tab of the application when the display parameter of the URL is passed - no sort icons appear on the crosstab columns.

The above shows how the second tab appears with the display parameter; no print button appears

When the navigate parameter is passed, the user can sort on the crosstab columns

The user sees the print button on the second tab

See the video below:

Upcoming ASUG Design Studio Webcasts:

• March 1 Using SAP BusinessObjects Design Studio for Self Service BI
• May 10 What's New with Design Studio 1.6 Feature Pack
• June 8: Are you ready to migrate from SBOP Dashboards to SBOP Design Studio? (registration not yet open)