Hi!

If you wish to Join the #BlogItForward (BIF) challenge and you haven't been tagged yet, please edit the document to add your name below in the table. Then someone will Blog It Forward to you.

Please remember to remove your name once you join BIF and update the Blog It Forward chain

Overview -

The variant management control allows users to load, save, and change variants. You can use variant management with filter bar. The filter settings consist of selection fields, their filter parameters, and layout, But this blog refers to a variant management that allows users to load, save, and change variants without interacting filter bar.

Biggest challenge in such implementation of variant management is to enable save button, for which i have used  "currentVariantSetModified(true);"

Here is the step by step guide to implement such variants -

I have created following view to implement Variant Management.

This view has two controls

• Filter bar with two input fields and one checkbox.
• Variant management.

Variant items are bound with OData service So the data is coming from database table.

View

Below is the code to create view as shown in screenshot.

<core:Viewxmlns:core="sap.ui.core"xmlns:mvc="sap.ui.core.mvc"

xmlns:fb="sap.ui.comp.filterbar"xmlns="sap.m"xmlns:l="sap.ui.layout"

            xmlns:v="sap.ui.comp.variants"controllerName="scn.Punter"

      xmlns:html="http://www.w3.org/1999/xhtml">

<Appid="app">

<Pagetitle="Variant Management"navButtonPress="onNavBack"showNavButton="true">

<content>

      <v:VariantManagementid="vm"select="onSelect"save="onSave"enabled="true"manage="onManage"

                         showExecuteOnSelection="true"showShare="false"variantItems="{/VariantSet}">

<v:variantItems>

<v:VariantItemtext="{VAR_NAME}"key="{VAR_KEY}"></v:VariantItem>

            </v:variantItems>                             

      </v:VariantManagement>

<fb:FilterBarid="fb"search="onGo"initialise="initialise">

<fb:filterItems>

      <fb:FilterItemname="A"label="FirstProfile">

      <fb:control>

<Inputid="firstProfile"value="{selection>/FIRST_PROFILE}"type="Text"placeholder="First Profile ..."

showSuggestion="true"showValueHelp="true" valueHelpRequest="firstProfileValueHelp"/>

      </fb:control>

      </fb:FilterItem>

<fb:FilterItemname="B"label="Second Profile">

      <fb:control>

      <Inputid="secondProfile"value="{selection>/SECOND_PROFILE}"type="Text"placeholder="Second Profile ..."

showSuggestion="true"showValueHelp="true"valueHelpRequest="secondProfileValueHelp"></Input>

      </fb:control>

      </fb:FilterItem>

      <fb:FilterItemname="C">

      <fb:control>

      <CheckBoxid="critical"selected="{selection>/CRITICAL}" text="Critical"/>  

      </fb:control>

      </fb:FilterItem>

</fb:filterItems>

</fb:FilterBar>

      </content>

</Page>

      </App>

</core:View>

Controller

sap.ui.controller("scn.Punter", {

onInit : function() {

               var oModel = new sap.ui.model.json.JSONModel();

            oDataModel = new sap.ui.model.odata.ODataModel("https://xxxxxx.xxx.sap.corp:xxxxx/sap/opu/odata/xxxxxx/xxxxx_xxxxxxxx_SRV/");

        oDataModel.read("VariantSet",null,null,true,function(oData, response){

                       oModel.setData({VariantSet : oData.results});

                       }, function(err) {

                                            alert("Service Failed");

                       });

        sap.ui.getCore().setModel(oModel);

                var oModelSelection = new sap.ui.model.json.JSONModel();

        oModelSelection.setDefaultBindingMode(sap.ui.model.BindingMode.OneWay);

        sap.ui.getCore().setModel(oModelSelection,"selection");

                      },

    onSave : function(oEvent) {

             jQuery.sap.require("sap.m.MessageToast");

                          var params = oEvent.getParameters();          

                                          if (params.overwrite){

//Get Values from selection screen

                           var parametersValue = this.getParametersValue();

//Get selected Variants Data

                            var selectedKey = oEvent.getSource().getSelectionKey();

                            var bindingPath = oEvent.getSource().getItemByKey(selectedKey).getBindingContext().getPath();

                            var modelData   = sap.ui.getCore().byId("idPunter1").byId("app").getModel().getProperty(bindingPath);

                            var save = Object.create(null);

                  save.FIRST_PROFILE    = parametersValue.firstProfile; 

                  save.SECOND_PROFILE       = parametersValue.secondProfile;

                  save.CRITICAL         = parametersValue.critical;

                  save.VAR_KEY            = modelData.VAR_KEY;  

                  save.VAR_NAME           = modelData.VAR_NAME;

               $.extend( modelData, save );

          sap.ui.getCore().byId("idPunter1").byId("app").getModel().refresh();                      

          oDataModel.update("VariantSet('"+save.VAR_KEY+"')", save, null,function(oData, response){

                   }, function(err) {

                                    alert("Service Failed");

                 });

               }

                                  else{

                                            var parametersValue = this.getParametersValue();

                                            var newEntry = Object.create(null);

                          newEntry.VAR_NAME             = params.name;

                          newEntry.VAR_KEY              = params.key;

                          newEntry.FIRST_PROFILE      = parametersValue.firstProfile;       

                          newEntry.SECOND_PROFILE         = parametersValue.secondProfile;    

                          newEntry.CRITICAL           = parametersValue.critical;

//Updating database via Odata           

         oDataModel.create("VariantSet",newEntry, null,function(oData, response){

//Updating Json Model Local Data

                    var Data = sap.ui.getCore().byId("idPunter1").byId("app").getModel().getData().VariantSet;

              Data.push(newEntry);

          sap.ui.getCore().byId("idPunter1").byId("app").getModel().refresh();

                              }, function(err) {

                                    alert("Service Failed");

        });

     }

                    var sMessage = "New Name: " + params.name + "\nDefault: " + params.def + "\nOverwrite:" + params.overwrite + "\nSelected Item Key: " + params.key;

          sap.m.MessageToast.show(sMessage);                        

                            },

      onManage : function(oEvent) {

                 "use strict";

                     jQuery.sap.require("sap.m.MessageToast");

                                          var params = oEvent.getParameters();

                                          var renamed = params.renamed;

                                          var deleted = params.deleted;

//rename backend data       

     if (renamed){

      renamed.forEach(function(rename){

     oDataModel.update("/VariantSet('"+rename.key+"')",

                                                       {VAR_KEY: rename.key,

                                                        VAR_NAME:rename.name}, null, function(){

                              alert("Update successful");

                        },function(){

                              alert("Update failed");});

                  });

            }

            var sMessage = "renamed: \n";

            for (var h = 0; h < renamed.length; h++) {

                sMessage += renamed[h].key + "=" + renamed[h].name + "\n";

            }

//delete backend data             

     if (deleted){

     deleted.forEach(function(remove){ oDataModel.remove("/VariantSet('"+remove+"')", null, function(){

                              alert("Delete successful");

                        },function(){

                              alert("Delete failed");});

                  });

            }

            sMessage += "\n\ndeleted: ";

            for (var f = 0; f < deleted.length; f++) {

                sMessage += deleted[f] + ",";

            }

            sap.m.MessageToast.show(sMessage);

          },

      onSelect : function(oEvent) {

            var selectedKey = oEvent.getSource().getSelectionKey();

            if(selectedKey === "*standard*"){

                  var modelData={};

                  var model=sap.ui.getCore().byId("idPunter1").byId("app").getModel("selection");

                  model.setData(modelData);

                  model.refresh();

                  }

            else{

                         var bindingPath = oEvent.getSource().getItemByKey(selectedKey).getBindingContext().getPath();

                         var modelData=sap.ui.getCore().byId("idPunter1").byId("app").getModel().getProperty(bindingPath);

                         var model=sap.ui.getCore().byId("idPunter1").byId("app").getModel("selection");

            model.setData(modelData);

                         if(model.oData.CRITICAL == "false" || model.oData.CRITICAL == false ){

                     model.oData.CRITICAL = false;

                  }

                         else

                  model.oData.CRITICAL = true;

                  model.refresh();

              }

               var sMessage = "New Variant Selected:"+selectedKey;

          sap.m.MessageToast.show(sMessage);

          },        

      onAfterRendering: function() {

     var controlIdArray="firstProfile secondProfile critical".split(" ");

       controlIdArray.forEach(function(controlId){

                                                                 var control=sap.ui.getCore().byId("idPunter1").byId(controlId);

          control.addEventDelegate({

     onfocusout : function() {

          var selectedKey = sap.ui.getCore().byId("idPunter1").byId("vm").getSelectionKey();

          var bindingPath = sap.ui.getCore().byId("idPunter1").byId("vm").getItemByKey(selectedKey)&&sap.ui.getCore().byId("idPunter1").byId("vm").getItemByKey(selectedKey).getBindingContext().getPath();

                                                      var modelData=sap.ui.getCore().byId("idPunter1").byId("app").getModel().getProperty(bindingPath);

                                                      var map = {

                                       critical : "CRITICAL",

                                       firstProfile : "FIRST_PROFILE",

                                       secondProfile : "SECOND_PROFILE",

                                      };

     if(controlId==="critical"){

                if(modelData["CRITICAL"] !== control.getSelected()){                                  sap.ui.getCore().byId("idPunter1").byId("vm").currentVariantSetModified(true);

         }

}elseif (!modelData){
          sap.ui.getCore().byId("idPunter1").byId("vm").currentVariantSetModified(true);

         }

           elseif (modelData[map[controlId]] !== control.getValue()){           sap.ui.getCore().byId("idPunter1").byId("vm").currentVariantSetModified(true);

          }

         }

        });

      });

},

getParametersValue: function (){

            var parametersValue = Object.create(null);          

          parametersValue.firstProfile = sap.ui.getCore().byId("idPunter1").byId("firstProfile").getValue();

          parametersValue.secondProfile = sap.ui.getCore().byId("idPunter1").byId("secondProfile").getValue();

          parametersValue.critical = sap.ui.getCore().byId("idPunter1").byId("critical").getSelected();

return parametersValue; 

},

});

Thanks
- Tapesh Syawariya

Introduction

Document How to deal with legal/regulatory changes (using SAP EHS MANAGEMENT)?

tries to give an overview regarding some IT challenges in using EHS classic. E.g. thread How many types of SDS we have with standard SAP? shows that there might be still some uncertainty "how to use SAP standard" in some circumstances. What kind of software is delivered by SAP? What should I buy on the top to use the software?

Many new challenges are coming to be handled by chemical industries (or other industries which can use SAP EHS classic for many purposes). From time to time you should ask your self some questions regarding e.g. "how to avoid costs" in your company.

Future

If you check the many publications, documents etc. from SAP you will may be realize: SAP assumes that you (as a potential customer of SAP) will look for cost reduction options. One important cost reduction option is e.g. "Cloud services" of many kind. Many other services (SERC/SERD) exists as well. But what are the key questions to decide how to go on with your SAP landscape? Here only some examples:

• if you use the many services from SAP you need not to look for "experts" in your company; a big part of data management, data handling, and document handling, is "outsourced"

• Because of the many legislation trends and because of the fact that you would use "SAP best practise standard" you can ask therefore your self: what kind of costs need I to invest to check my SAP ERP landscape to be able to move to a "service" delivered by SAP?

  Roughly once a year some legislation changes are coming up; if you use your own SAP EHS "road" you will never be able to move to SAP standard; but using the SAP services: this can simplify your "IT" part (and you will hopefully be able to reduce costs).

   

  Therefore: one big driver for IT projects in the next years might be: simplify your SAP landscape; make it "less" complex; more user friendly (so that the people using the software need may be less training and can focus on "legal" etc. part and not on IT part) etc. More and more demands will come from outside and you should be able to provide/exchange data, documents with your suppliers and customers. Many other IT initiative need to be checked as well (to make sure that you still deliver your products and services using "state of the art" processes).

   

   

  SAP HANA and any solution around will support you in the future. The potential key word is still "sustainable". Not only you would like to know key numbers from financial point of view but from e.g. product saftey point of view as well (how long does a process need? Are there any bottlenecks? And what are the reasons of them? People? Software? Organisation?).

   

  Any body ouside clearly expects from you, that you deliver a SDS/MSDS/Label (or other documents); so this kind of "service" is a core one. The same is true for any kind of "dangerous goods handling" etc.  So if you provide consulting services: you need to be able to help your customers to get these standard documents "out of the box" in a "short" time. Now other data/documents are of "higher" interest. At least: data management and data analysis is still an important factor; especially for chemical industry.

  Topics as described e.g. here: Sustainability Performance Management Software | Sustainability | SAP

  are the future (and check e.g. http://news.sap.com/germany/2014/08/22/industrie-4-0-zwei-beispiele-fur-die-fabrik-der-zukunft/

  as well)

   

  E.g. these documents focuses on these trends as well:

  Climate change: The role and responsibility of IT

  Risk Management - Is your approach Holistic?

  Time to think of Digital EHS Management

  How well is that process being performed?

  Managing Product Data with SAP#

  It's just a temporary change. I'll remember to reverse it - Management of Change Gone Bad

1. Access sequence created: ZDUA and Condition table used SAPIBD01 and Fields in condition table SAPIBD01 and Field Ship From is selected as optional so that we can use this same access sequence from other Source.

Configuration : SPRO-> SCM Basis-> Pack -> Packaging Specification-> Determination of Packaging Specifications-> Define Access Sequences

2. Condition type used is ZDUA

3. Determination procedure used is ZSPP_D.

4. ZSPP_DRP_ROUNDING is the rounding profile defined and Rounding profile Configuration in DRP.

SPRO-> Advanced Planning and Optimization -> Supply Chain Planning -> Service Parts Planning (SPP) -> Basic Settings -> Define Rounding Profile

5. Setting of Z_DRP service profile which is used for DRP. ZSPP_DRP_ROUNDING is rounding profile assigned.

SPRO-> Advanced Planning and Optimization -> Supply Chain Planning -> Service Parts Planning (SPP)->Distribution Requirements Planning (DRP) ->Define Service Profile for DRP

6. Pack spec ZSPP_0048 maintained for supplier XXX and Target qty 75 at level SPP rounding

Transaction /SCWM/PACKSPEC

7. Testing pack spec  in simulation mode using transaction /SAPAPO/AC12

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

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

/UI2/73000020

/UI2/73000021

/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

/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

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

Steps-

Create Adobe Form

First, Develop Adobe Form using Tcode SFP ZF_AdobeForm, which will have input as docparams and will export formoutput.

You can follow step to create Adobe Form as per requirement

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40553f25-08d1-2c10-3e8f-fe7af794566e?QuickLink=index&overridelayout=true&46158013817331

Create Project and Entity Type

Now develop GW service which will help us to expose Form. Create simple GW service ZFORM as displayed below.

We have EntityForm (Media Type) and Entity Set Forms.

Generate run-time artifacts.

Redefine Define method marking Mime Type

Now we need to redefine DEFINE Method in MPC_EXT class as below.

METHODdefine.

 

  DATA:

lo_entity   TYPEREFTO/iwbep/if_mgw_odata_entity_typ,

lo_property TYPEREFTO/iwbep/if_mgw_odata_property.

 

super->define().

 

lo_entity= model->get_entity_type(iv_entity_name= 'pdf').

 

  IFlo_entity ISBOUND.

lo_property= lo_entity->get_property(iv_property_name= 'mime_type').

lo_property->set_as_content_type().

  ENDIF.

ENDMETHOD.

Redefine GET_STREAM

Redefine method /iwbep/if_mgw_appl_srv_runtime~get_stream in DPC_EXT as below.

METHOD /iwbep/if_mgw_appl_srv_runtime~get_stream.

 

     DATA: lv_funcname     TYPE funcname,

           ls_outputparams TYPE sfpoutputparams,

           ls_docparams    TYPE sfpdocparams,

           ls_formoutput   TYPE fpformoutput.

     DATA: ls_stream   TYPE ty_s_media_resource.

 

     " Getting the Function Module Name for the Adobe Form

     TRY.

         CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'

           EXPORTING

             i_name     = 'ZF_AdobeForm'     "Adobeform name

           IMPORTING

             e_funcname = lv_funcname.

         "Handle Exceptions with Try - catch

     ENDTRY.

 

     " Opening the Job

     ls_outputparams-nodialog = abap_true.

     ls_outputparams-getpdf   = abap_true.

 

     CALL FUNCTION 'FP_JOB_OPEN'

       CHANGING

         ie_outputparams = ls_outputparams

       EXCEPTIONS

         cancel          = 1

         usage_error     = 2

         system_error    = 3

         internal_error  = 4

         OTHERS          = 5.

     IF sy-subrc <> 0.

* Implement suitable error handling here

     ENDIF.

 

     ls_docparams-langu = sy-langu.

     ls_docparams-country = 'US'.

 

     CALL FUNCTION lv_funcname

       EXPORTING

         /1bcdwb/docparams  = ls_docparams

       IMPORTING

         /1bcdwb/formoutput = ls_formoutput

       EXCEPTIONS

         usage_error        = 1

         system_error       = 2

         internal_error     = 3

         OTHERS             = 4.

     IF sy-subrc <> 0.

* Implement suitable error handling here

     ENDIF.

 

     " Closing the Job

     CALL FUNCTION 'FP_JOB_CLOSE'

       EXCEPTIONS

         usage_error    = 1

         system_error   = 2

         internal_error = 3

         OTHERS         = 4.

     IF sy-subrc <> 0. " Subrc Check is not required, so we are not handling any exception here

     ENDIF.

     " Converting the PDF to XString

     ls_stream-value = ls_formoutput-pdf.

     ls_stream-mime_type = 'PDF'.

 

     copy_data_to_ref( EXPORTING is_data = ls_stream CHANGING  cr_data = er_stream ).

 

ENDMETHOD.

Testing the Service

Register GW service, and we are ready for testing.

To read document a GET containing the keys with $value to read stream can be requested:

/sap/opu/odata/sap/ZFORM_SRV/Form('key value value')/$value

We are happy to announce that the BIF chain got too long:) and got archived:

Click here for 2012 Blog It Forward archive

Click here for 2013 Blog It Forward archive

Click here for 2014 Blog It Forward archive

If you are new BIFer, please continue to update the list below.

Click here for more information about how to join Blog It Forward challenge. Follow us on Twitter  (#BlogItForward or @Moshenaveh) or on G+.

Blog It Forward (BIF) Chain:

1. To the right, click Edit

2. Enter your name, country, topic, BIF from, BIF to

3. Save and Publish

@Sygyzmundovych

http://http://scn.sap.com/community/about/blog/2015/11/01/blog-it-forward-saurabh-raheja

2015 Top 10 SAP Predictive Analytics Community Articles

by Julie HORVILLE - The 2015 retrospective of the most popular blogs and articles!

SAP Predictive Analytics News #2

The second edition is out! Read now!

20 Ways to Follow SAP #Predictive #Analytics

by Pierre Leroux - Engage with us on social media!

Announcing SAP Predictive Analytics 2.4!

by Ashish Morzaria - 2.4 has been delivered! Read more! Related resources: Useful Links, FAQ& New Tutorials!

Hands-On Tutorial SAP Predictive Analytics, Automated Mode: Time Series Analysis

by Andreas Forster - New tutorial using daily rental London’s bicycle to forecast future demand!

Forecast Planning service takes long time due to huge entries in change history table entries in the time series.

Forecast Planning services: SPP: Forecast Service -  SPP_FCS_SERVICE, SPP: Forecast Disaggregation Service -  SPP_FCST_DISAGGREGATION, SPP: Forecast Service (StdDev.) - SPP_FCS_SERVICE_MSE, SPP: Forecast Approval -  SPP_FCST_RELEASE.

Below Changed history tables in time series data area have Millions of records.

It leads to poor performance in the forecast planning service.

/SCA/TK1SPM  -  Key Figures of Time Series Data Area 1SPM

/SCA/TS1SPM - Status Values of Time Series Data Area 1SPM

/SCA/TN1SPM - Notes for Time Series Data Area 1SPM

/SCA/KT1SPM  - Key Figure History for Time Series Data Area 1SPM

/SCA/ST1SPM  - Status History for Time Series Data Area 1SPM

/SCA/IS1SPM  - Internal Status of Time Series Data Area 1SPM

Delete all change History for times series data area which will improve performance.

You can use below reports to delete time series change history entries.

Report /SCA/TSDM_TS_HIST_DELETE - Delete time series change history

Report /SCA/TSDM_TS_HIST_DELETE_ALL - Delete All Time Series Change History Entries

Author                : Ramani Nagarajan

Organization      : IBM India Pvt Ltd

Title                     : Dynamic tray selection while printing forms through ABAP Code

Mail-id                 : ramani600091@gmail.com

Requirement

We all know that, any forms can be printed on the required Tray by setting the appropriate value to the "Resource Name" field in the design screen of the form and be activated.

But the current requirement is to set the "Resource-Name" attribute of both Smartforms (or) SAPScript dynamically just before the form is printed.

This article explains how to set it dynamically !!

Printing the forms on the required tray

Incase of Smart forms, currently there are 2 ways to print the forms on the required tray as below:

1. By assigning the "Resource Name" attribute field on the Smartforms designer with the below values:

             TRY01  for Tray-1

     TRY02  for Tray-2

     and so on  up to 9

   2. Or, by changing the default tray on the SPAD transaction

     Incase of SAPScript, the above said point-1 is the only way

Challenges

There is no dynamic value assignment capability available for the field "Resource Name" on both the forms.   Owing to the best practice, an alternative way to be discovered for assigning the tray values at run time before the printing, instead of Hardcoding or changing the SPAD settings (incase of Smartforms).

Proposed solution

Upon exploring the SAP approach on the "Form printing", it is found that, the Print-Attribute entered in the design time of both Smartforms & SAPScript are Exported to Memory database table as below:

Incase of SAPScript    :      STXL(xx)

Incase of Smartforms  :      STXFCONTR(sf)

Below given is the screen shot of the Import Procedure being done by the Standard coding of SAP:

And the print routine, imports the Print Attributes from the above memory database table and assign it to printing.

Logic for proposed solution

1. Import the relevant print attribute of the concerned form
2. Keep a local copy of it
3. Lock the Memory Database Table record
4. Change the Resource Name with the required TRAY on the imported internal table
5. Export the above modified internal table back to the Memory Database Table
6. Call the Form Printing routine
7. Export the Local Copy of internal tables from Step(2) back to the Memory Database Table
8. Unlock the Memory Database Table

Code Snippet:

The complete code written on a Class named as "ZCL_PRNTR_ATTRIBUTE" is attached for reference.

There are 5 methods implemented as below:

1. OPEN_FORM
2. CLOSE_SMARTFORM
3. CLOSE_SAPSCRIPT
4. WRITE_SMARFORM
5. WRITE_SAPSCRIPT
6. REFRESH_MEMORY

Following steps are to be written in the Driver-Program in the same sequence:

(1) OPEN_FORM is the main form which is to be called through the Driver Program.

(2) <Existing print routine>  --> No change in these

(3) CLOSE_SMARTFORM or CLOSE_SAPSCRIPT is to be called

Note: Methods (4),(5),(6) are executed internally through other methods.  Hence, we do not need to call them.

How to invoke the coding?

Here is the screen shot for calling procedure through Driver-program:

Note: Highlighted rows are our new methods.

How to utilize the attached code?
The code is a generic code, which can be used anywhere.  Hence, anyone can copy the code and use it.

**Caution:

During testing, please, let the driver program run the sequence as cited above fully.

Once the OPEN_FORM method is run, CLOSE_SMARTFORM/ CLOSE_SAPSCRIPT method also should be executed  sequentially.  Hence, do not abort the execution half the way.   This would leave the current print attribute values with the Memory Database Table.  To reset the values, we have to re-activate the Smartforms / SapScript by changing the Resourse-Name to blank.

Thanks for reading it!!

Ramani Nagarajan

IBM India Private Limited

While performing the steps to install SAP Host Agent on Unix Platforms using the steps outlined in:

How to install the SAP Host Agent on Unix Platforms - Business Intelligence (BusinessObjects) - SCN Wiki
below errors were seen:

Symptoms:

1) Command: SAPCAR* -xvf SAPHOST*.SAR

OR

Command: SAPCAR* -xvf SAPHOSTAGENT207_207-20005731.SAR

Response: -bash: SAPCAR_721-20010450.EXE: command not found

2) Command: ./SAPCAR.sh -xvf SAPHOSTAGENT207_207-20005731.SAR

Response: -bash: ./SAPCAR.sh: Permission denied

3) Command: ./saphostexec -install

Response:

-----

Install service

sh: /usr/sbin/useradd: Permission denied

[Thr 140318646814496] Tue Dec 29 18:02:04 2015

[Thr 140318646814496] *** WARNING => useradd exit with status 126 [OsUtilux.cpp 404]

[ERROR]

Create user sapadm failed

-----

Environment:

• SAP BI Platform Support Tool 2.x
• SAPHOSTAGENT
• Linux

Solution:

1) With reference to the below error message mentioned above:

------

-bash: SAPCAR_721-20010450.EXE: command not found

------

please perform the below step:

1.a) mv SAPCAR_721-20010450.EXE SAPCAR.sh

Thereafter, attempt to execute the below commmand:

1.b) /SAPCAR.sh -xvf SAPHOSTAGENT207_207-20005731.SAR

2) With reference to the below error message mentioned above:

------

-bash: ./SAPCAR.sh: Permission denied

------

please ensure that the folder in which SAPCAR.sh and SAPHOSTAGENT207_207-20005731.SAR exists has the read, write and execute permissions for the user who is executing the above mentioned relevant command.

3) With reference to the below error message mentioned above:

------

sh: /usr/sbin/useradd: Permission denied

[Thr 140318646814496] Tue Dec 29 18:02:04 2015

[Thr 140318646814496] *** WARNING => useradd exit with status 126 [OsUtilux.cpp 404]

[ERROR]

Create user sapadm failed

------

please ensure that the user who is executing the above mentioned relevant command has read, write and execute permissions for the 'useradd' file under '/usr/sbin' folder.

I have already done NW 731 SP08 install. But when I was trying to run the setup.exe from DVD 51050311_7 (Support Package 6 of E-Sourcing Server 10.0) it does nothing. There is no error message also.

Resolution

Add JAVA executable to PATH variable of your current user.After that I was able to launch it.

Download and view developer guides, API reference material, sample code, and object model diagrams for Java, .NET, COM, and Flex APIs available in SAP BusinessObjects BI 4.x. Visit the samples page to access the sample applications, reports, and dashboards. For version 3.x and earlier of the SDK library, visit the SAP BusinessObjects BI 3.x Developer SDK Library page.

Note:

1. To view the developer guides, save and uncompress the entire .zip file to your local drive and then open it.

    Otherwise, if you open the zip files directly from the browser, you may see "The Address is not Valid" error.

2. If you are opening a .chm file, clear the Always ask before opening this file check box in the Open File dialog box.

Java SDK Developer Guides and API References

View developer guides below that contain key concepts and tasks with supporting sample code snippets. In each guide, go to the Start Here > What's New sections to learn about new features in the SDK. Also view and download API references that contain syntax, information, and examples for the classes, interfaces, and members of each SDK.

To view online Javadocs for our Java SDKs, visit: http://help.sap.com/javadocs.

.NET SDK Developer Guides and API References

View developer guides below that contain key concepts and tasks with supporting sample code snippets. In each guide, go to the Start Here > What's New sections to learn about new features in the SDK.

Also view and download API references that contain syntax, information, and examples for the classes, interfaces, and members of each SDK.

COM SDK Developer Guides and API References

RESTful Web Services SDK Developer Guides and API References

Additional Guides and Resources

Title:

This document is plotted based on the latest standard procedure of TREX upgrade . It's an updated version of my previous document http://scn.sap.com/docs/DOC-43264

Version Details:

Source Version of TREX: TREX 7.10 PL 58

Target Version of TREX : TREX 7.10 PL 65

Download Location:

http://support.sap.com/swdc

>  Support Packages and patches

>  Browse our Download Catalog

>  SAP Netweaver and complementary products

>  SAP NETWEAVER

>  SAP NETWEAVER 7.0

>  Entry By Component

>  Search & Classif. (TREX)

>  TREX 7.10

>  Platform

Upgrade Process:

As mentioned in previous document , TREX version can be updated till 7.10 PL 57 via sapinst available under TREX UPDATE SAR file [format: TREX71_<version>-<*>.SAR >]. However from TREX 7.10 PL 58 onwards, SWPM (SWPM)needs to be used for TREX version update. Exceptionally , in some scenarios, shell scripts also requires to be used for TREX update, which will be shown in lateral part of this document.

Process 1 : Along with SWPM -

1. Download SWPM from below location :

https://service.sap.com/sltoolset (Need authorized S user ID)

>  SL ToolSet > Software Logistics Toolset 1.0

>  System Provisioning

>  Download Tool

>  Support Packages Patches

>  Select OS

>  SWPM10SP<*> 7<*>.SAR

2. Extract both the SWPM & TREX UPDATE SAR files and keep it in a separate location.

3. Execute SWPM with ROOT user and select "UPDATE - TREX System" as shown in below screen shot :

4.  Provide the TREX binary file location: ( Path : Under extracted TREX SAR file , navigate to tx_trex_content/TX_<OS>/LABEL.ASC  )

5.  Then provide residual inputs in following screens till EXECUTION phase. Once completed, check the TREX updated version in TREXADMIN (either via TREXADMIN transaction or else via TREXAdmin.sh script. If it gets updated then well and good or else follow Process - 2 .

Process 2 : Along with shell script -

1.  Navigate to TREX SAR file  extracted directory and then from tx_trex_content/TX<OS>/ execute following command via ROOT user :

./install.sh --action=update --sid=<TREX SID> --password=<password of TREX_SID_ADM user> --restart

At the end it should SUCCESSFUL as follows for successfull completion of TREX update :

2. After this , it should show latest version in TREXADMIN

NB: In case you are running in multinode TREX system, then execute the above command from MASTER1 , which will update the TREX version in other backup master nodes as well .

Reference Link :

1. Note : 2242152

    * Standard documents can be found from the provided path details in the abpve mentioned note .

Regards,

Nilutpal.

Dear All,

I am herewith explaining the step by step way out for updating TREX server, which is very much required now in days in order to incorporate with dependent peripheral SAP SW Components . I am trying to architect the procedure based on one of my recent activity which includes following scenario :-

1. Old TREX Server : 7.10 SP40

2. Update Level : 7.10 SP55 (latest one)

3. OS: Windows 2008 (64 bit)

4. Number of connected SAP system RFCs : 3

Step 1: Check  the current version of TREX in connected SAP system though TREXADMIN T-Code.

Step 2: Download the latest patch level from SMP . Follow https://service.sap.com/swdc  >  Support Packages and Patches> Browse our Download Catalog> SAP NetWeaver and complementary products> SAP Netweaver > SAP NETWEAVER 7.0> Entry By Components > Search & Classification (TREX) > TREX 7.10 > Windows on X64 64 bit > TREX71_55-10004511.SAR

Step 3: Then extract it with SAPCAR with following command:-

sapcar -xvf <file name.SAR>

Step 4: Stop TREX service and also the Trex Admin console (if running somewhere).

Step 5: Execute SAPinst from the extracted directory :-

Step 6 :Choose "Update a TREX system" option :-

You can take restart of TREX server manually later on though MMC.

Step 7: Restart the TREX server through MMC and then you can check the latest version again in TREXADMIN.

NB: TREX Upgrade process from 7.1- PL 58 onwards, you can follow updated document - http://scn.sap.com/docs/DOC-69966

Regards,

Nilutpal.

Hola:

Por medio de este documento voy a explicar como se puede manejar para un traslado Inter-compañía la condición manual PBXX desde el pedido.

Introducción:

Cuando se genera un pedido de Traslado Inter-compañía es usual que se maneje el precio con un registro info y por ende la condición del pedido se determina como PB00. Pero por requerimientos del negocio en algunas ocasiones no se tiene dado de alta un registro info para el precio y los usuarios indican el precio con la condición manual PBXX, situación que puede derivar en un error en la factura Inter-compañía si no se tiene la configuración necesaria.

Procedimiento:

1. Alta condición PBXX en configuración comercial

Comercial --> Funciones básicas --> Determinación de precio --> Control de la determinación de precios --> Definir clases de condición:

Este puede ser creada con referencia a la condición PB00.

2. Alta condición PBXX en esquema de calculo

Comercial --> Funciones básicas --> Determinación de precio --> Control de la determinación de precios --> Definir y asignar esquemas de calculo --> Actualizar esquema de calculo:

En este link pueden revisar todos los temas que he publicado con referencia al traslado Inter-compañiaTraslado Intercompañia (Intercompany STO)

Espero les sea de utilidad así como recibir sus comentarios y/o sugerencias.

Saludos

Jose Antonio Martinez

The purpose of this document is to cover common questions that come up prior to purchasing Integrated Business Planning applications.

If you have technical questions related to an implementation, please see:SAP Integrated Business Planning FAQs for implementations.

General Questions

Subscription and Services

Implementation

Cloud and Security

Learn More

General Questions:

What is IBP (Integrated Business Planning)?

The term “IBP” is an industry standard term referring to the process of integrating sales forecasts, inventory targets, supply plans, and financial plans into a single operational plan for the business or business unit, agreed by all parties (sales, operations, logistics, finance) and “blessed” by business leadership.

What is IBP at SAP?

In SAP terms, “IBP” is the next generation SAP supply chain planning applications that sit on HANA and support the above Integrated Business Planning process.

There are 5 applications in IBP:

1. Integrated Business Planning for sales and operations: “One set of numbers”

        1 Page Product Overview| You Tube Demo

• Balance demand and supply while providing organizational visibility and alignment
• What-if scenarios,  using “real time” information
• JAM embedded communication, and analytics
• SAP Integrated Business Planning for sales and operations

2.Supply Chain Control Tower: “Visibility”

   1 Page Product Overview

• Achieve end-to-end visibility in the extended supply chain
• Integrate Data from various Systems
• Drive visibility and action with configurable Analytics & Alerts and Case Management
• Pre-delivered Supply Chain Performance (SCOR) metrics.
• Supply Chain Control Tower

3.    Integrated Business Planning for inventory“Master Uncertainty, use inventory efficiently”

          1 Page Product Overview

• Efficiently position inventory to best respond  to forecast error, demand variability and supply uncertainty
• Multi-echelon (multi-stage) inventory optimization to solve the science of postponement
• Drive S&OP decisions to inventory target recommendations for Planners (item-location-timeframe specific)
• SAP Integrated Business Planning for inventory

4. Integrated Business Planning for demand:  “Forecast Better”

      1 Page Product Overview

• Demand Sensing (predict and reforecast, pattern recognition)
• Forecasting statistical techniques
• Collaborative Demand Planning
• SAP Integrated Business Planning for demand

5. Integrated Business Planning for response and supply: “Master supply planning and response intelligence”

      1 Page Product Overview

• Plan production, procurement,  and distribution
• Respond to daily disruptions  through what-if analysis to change supply plans and reschedule demand
• Manage allocations where supply is scarce
• SAP Integrated Business Planning for supply

Comparison of each of the IBP solutions and their capabilities: LINK

IBP Overview Blog: Getting started: What is Integrated Business Planning?

IBP Overview Webinar:Supply Chain Transformation with new Integrated Business Planning solutions from SAP

I have APO do I need IBP?

• IBP adds important functionality to APO and other Advanced Planning software, but the true answer depends on YOU!
• Every customer is different. That being said there are different ways of adopting the solution.
• Even if you have APO DP, you can leverage demand sensing (part of IBP for demand), to obtain better short-term forecasting based on pattern recognition and multiple forecast inputs
• APO SNP vis a vis IBP for inventory
  • IBP for inventory is a planning tool, taking in factors around risk and uncertainty (forecast error, supply uncertainty) to most efficiently absorb risk using the lowest amount of inventory to meet customer service levels.  It accomplishes this by setting most-efficient safety stock targets across the supply chain. 
  • SNP then uses these IBPfor inventory “SS” targets to optimize how to most efficiently supply demand (forecast + demand + any change in SS).  This meets both service levels (by supplying safety stock), forecast and existing orders.
  • APO SNP does have a safety stock optimization function, but this is extremely limited in scope:  APO SNP only handles an individual location, essentially considering only demand variability.  IBP for inventory considers the entire supply, using multi-stage optimization, as well as considering additional uncertainties like supply timing variability. IBP for inventory can meet the same service level targets using (typically) 10-30% less inventory.

What are the benefits of IBP?

• End to end comprehensive view of supply chain current and historical supply chain performance
• Alerts quickly identify current and future potential supply chain problems
• Collaboration enables the quick resolution of issues across functions
• Real-time scenarios and simulation on entire model
• Demand, supply chain, and financial model at aggregate and detailed levels

What is the Value Proposition:

• 1%-2% Top Line Revenue Growth
• 5%-15% Better Inventory turns with improved service levels by using inventory more efficiently
• 5-10% better order fulfillment metrics, better service
• Better user engagement, faster planning cycles and consistent planning processes
• Full support for your monthly or weekly planning processes

What synergy is available when applying 2 or more IBP applications?  In other words, why does “one + one” = “more than 2”?

• IBP for sales and operations + Supply Chain Control Tower = Management level strategic control and visibility over the business.
  
• IBP for sales and operations +IBP for inventory =  taking S&OP to SIOP, taking S&OP decisions and applying multistage inventory optimization in near-real-time to drive inventory targets to the Planners the same day the S&OP decision is made.
• IBP for inventory + IBP for demand: = A 1-2 punch against uncertainty!  Use IBP for demand to improve forecasting and, recognizing that even the best forecast is not 100% accurate (and suppliers aren’t 100% reliable either), position inventory most efficiently to buffer the remaining uncertainty in your supply chain.
• IBP for supply and response + Supply Chain Control Tower = Provides instant visibility to global inventory and capacity utilization. It incorporates the ability to understand exceptions and run what-if simulations on a global level to make decisions and effectively orchestrate fast issue resolution.

What does IBP look like?

• IBP Overview Video
• SAP S&OP Product overview demo
• SAP IBP youtube channel

How do I get started with IBP?

Want to try IBP out: http://www.sapstore.com/solutions/60032/SAP-Integrated-Business-Planning-for-sales-and-operations

Please contact l.w.bryan.charnock@sap.coml.w.bryan.charnock@sap.comif you have any questions with the Starter Edition on the SAP Store.

Ready to buy?

Our sales team would be happy to clarify any questions that you may have regarding SAP Integrated Business Planning and the Onboarding Process.

• Contact your SAP Account Executive or our IBP Sales experts below:
  • North America: JR Kavanagh
  • Latin America: Rudi Meyfarth
  • MEE: Martin Hill;  Eva Hartmann
  • EMEA(Europe): Mike Wade; Jesper Waaben; Matthias Alois Vogel
  • APJ: Jeff Majestic

Where can I learn about customer experiences with IBP?

• We have a large number of SAP Integrated Business Planning customers from many industries including: High Tech, Consumer Products, Life Science, Chemicals, and Industrial Machinery and Components.

Here are some ways to hear from our customers:

1. Listen to recorded webinars or presentations:

• Case Study: See how Weir Minerals leverages SAP Integrated Business Planning (IBP) for their Sales & Operational Planning Process
• Sapphire ColgateReplay
• Sapphire Nature's Way Customer PanelCustomer Panel Replay
• IBP Customer Tyson Foods: Demand Planning Best Practices

2. Review a case study:

• Arauco

3. Reference Call:

• SAP hosts multiple reference live calls where you can ask your questions directly to our customers.
• Contact your SAP Sales Team to request a recording of a previous session or to be included in a future session.

4. Attend an upcoming Customer Event:

• Complete SAP IBP Event & Webinar List

Subscription and Services

How long does the system provisioning process take?

• Starter Pack systems are available within 2 business days of completing the order and submitting the completed provisioning checklist.
• Test and Production systems are available within 4 business days of completing the order and submitting the completed provisioning checklist.

What software is included in the IBP subscription?

• IBP – licensed Integrated Business Planning application(s)
• HCI –Hana Cloud Integration; HCI gives you the ability to easily load data into IBP and extract data into other systems.
• SCI – SAP Cloud Identity - Single Sign On capability
• SAP JAM – SAP JAM is SAP’s collaboration platform (Optional additional license required)

What do I get with my subscription?

• System operations support
• Upgrades
• Standard application support
• Data security
• System monitoring
• Access to subscribed IBP application(s) and HCI

Think about all the IT dollars you will save!

What is the Release Cycle and Patch upgrade process?

• SAP wants to make sure you get the latest and greatest bug fixes and enhancements, therefore we provide our customers with system updates every 4 to 6 weeks.
• Updated Releases (with major enhancements) also come out 2 to 3 times a year.
• To find out more about IBP Upgrade Planning and Communications click on this LINK.

Where can I get more information on each Patch / Release?

Release notes: http://service.sap.com/sap/support/notes/2089926

Implementation:

How long does it take to implement IBP applications?

• Implementations can take as little as 3 months. Of course, implementation timelines can range due to scope, implementation approach, data quality, and resource availability.
• Upon request, the SAP Services team and SAP Partners would be happy to provide you with a sample implementation approach and plan.

Which SAP Partners are enabled on IBP applications?

• Please contact sunny.chandan@sap.comfor more information regarding SAP Partners for IBP.

Cloud and Security:

How do I access IBP in the cloud?

• Through a URL provided by SAP. You can access IBP through Internet Explorer or Google Chrome.

How do I load and extract data from the cloud?

• SAP’s proprietary HANA Cloud Integration has prebuilt templates that allow you to load and extract data from many standard SAP systems as well as non-SAP systems.

I understand that IBP is available in the cloud, how do I know that my data and system is secure?

• SAP has very high levels of data center and data security meeting all the key certification and audit requirements.
• SAP takes data security and system reliability very seriously. Take a tour of our data centers and learn about data security: http://www.sapdatacenter.com/
• SAP commits to a 99.5% system availability SLA for IBP on the cloud:

          http://www.sap.com/corporate-en/about/our-company/policies/cloud/service-level-agreement.html

Learn More:

Where can I find Product Documentation?

http://help.sap.com/ibp-ref

What Education Courses are offered for IBP?

Training.sap.com

This step by step document describes how to consume Sharepoint content - like lists, in Web Intelligence.

Currently there is no universe or Web Intelligence connector that enables users to expose Sharepoint content as a data source. It is however possible to leverage MS Access support of Sharepoint through a universe to solve this restriction.

A.     MS Access database

In this example, we are going to expose and consume in WebIntelligence a couple of Sharepoint lists.

1. In Microsoft Access, create a new Access Database  or open an existing database to reuse with Sharepoint

2. Insert a SharePoint object using the menu External Data:

     External Data->Sharepoint List

3. Enter the Sharepoint site with the port number (2845 in this example)

4. Make sure you select option “Link to the data source by creating a linked table” is selected. This insures that the universe and the dependent WebI reports will be dynamic and will be able to retrieve new data from Sharepoint on Refresh.

5. All available Sharepoint lists and items on the selected site are displayed; select the lists and items you need to expose in Web Intelligence:

6. The selected lists are inserted in Access database as tables with appropriate data

7. Save the database

B.     Universe

1. On the client machine where Information Design Tool will be used, open ODBC Data Source Administrator and create a new DSN pointing to the Access database

2. If you plan to use Web Intelligence in server mode from BI Launchpad, you need to create the same DSN described in previous step, on that server.

3. Open Information Design Tool and create a new relational connection:

4. Publish the connection to the CMS, and create a connection shortcut (.cns).

5. Create a Data Foundation on that connection shortcut

6. Insert the tables representing the Sharepoint lists, lists that you want to expose in the universe and Web Intelligence:

In this example we expose two Lists in the same universe without joins. It is however possible to join multiple tables representing various Sharepoint lists if that is necessary.

7. Create a Business layer on that Data Foundation then publish the universe to the CMS.

C.     Web Intelligence document

1. Start Web Intelligence in BI Launchpad or Web Intelligence Rich Client, and then create a new document based on universe. Select the previously published universe.

2. Add the objects representing the fields you want to expose in Web Intelligence document to the Query and Run the query

3. The result report exposes the data retrieved from SharePoint:

4. Changing the date in SharePoint, then refreshing Web Intelligence document reflects the changes instantly

Adding a new line in SharePoint:

Refreshing Web Intelligence document, the new line is added to the report:

Content under discussion