I would like to share code snippet for identifying the Top 100 Changelog/PSA table list along with size it's consuming. This would be very helpful for house keeping activities.

SELECT

1. M."TABLE_NAME",D."DDTEXT"as TABLE_DESC,

SUM(M."MEMORY_SIZE_IN_TOTAL") as DBSIZE,

CAST(sum(M."MEMORY_SIZE_IN_TOTAL" / 1073741824.0) ASDECIMAL(10, 2)) AS DBSIZE_DB

FROM M_CS_TABLES M

INNERJOIN SAPDP1."DD02T" D

ON M."TABLE_NAME" = D."TABNAME"

WHERE TABLE_NAME like'/BIC/B%00'

GROUPBY M."TABLE_NAME", D."DDTEXT"

ORDERBY  DBSIZE DESC

LIMIT 100

We can alter list by changing the LIMIT value

Modified the SQL which would show the descriptions of the PSA or Changelog table name...I intentionally didn't give the output of mine.

Thanks,

Shanthi Bhaskar

Google has announced that the OpenID 2.0 API for Google accounts will be retired on April 20 2015

https://support.google.com/accounts/answer/6135882

As a result, OpenID is being replaced by Google Connect API / Google + API for authentication.

What does this mean to me and are there any settings that will need to be changed to ensure I can login in the future?

1. Go to the login page
2. Select at the bottom "Click HERE if you are having trouble signing in"
3. This will e-mail you a temporary Signing option.

Once you click the link you will be placed at the page to add a new provider. Choose this option and choose the new Google login button as indicated above.

Source of this article

This document describes the SAP Landscape Virtualization Management scenarios with Linux on Power. For other IBM platforms refer to the parent document IBM On-Premise Cloud Configuration for SAP.

IBM PowerVC is the infrastructure management offering, built on OpenStack, that delivers advanced virtualization and storage management on IBM Power Systems. OpenStack technology has evolved as industry standard for infrastructure-as-a-service management. This technology has been made available for SAP on IBM Power environments by supporting PowerVC with SAP Landscape Virtualization Management.

SAP HANA on IBM Power Systems is supported for all scenarios and configurations described here.

Virtualization scenarios:

The following virtualization scenarios are supported with any type of storage and storage attachment:

Storage scenarios:

The following storage-related scenarios are supported:

IBM Spectrum Virtualize (SAN Volume Controller / SVC or Storwize V7000) provides storage virtualization and allows to combine storage systems from multiple vendors. Likewise, IBM FlashSystem models with integrated storage virtualization (V9000, V840) are supported.

SAP scenarios:

• Automatic Capacity Management including provisioning of additional dialog instances is supported.
• Post-Copy Automation is supported.

SAP notes and documentation:

• Note 2075173 - Integration of IBM Components into SAP LVM 2.1 for IBM Power

What is coming next?

Online cloning with PowerVC is under investigation.

Introduction:

Automatic Payment Program (F110) is used to do the clear the invoices and post the payments.F110 is the standard t-code for doing the same.

In addition to the above there also forms sent to customers and vendors about the Payments done which are called Remittance Advices and Payment Advices based on the payment method configured

Forms:

• There are three kinds of forms that can be used in SAP :
• SAP scripts
• SMARTFORMS
• Adobe Forms

  For payment advices we can use all the three kinds of forms .In this document configuration and the calling logics for all the 3 kinds of forms.SAP SCRIPTS:

• This is the default configuration provided by SAP.
• Standard script for the payment advices  : 'F110_IN_AVIS’
• The same can be configured in the FBZP screen as shown below :

1. Payment method in company code .This will be the default script name in case in case the configuration on the payment methods if the script name is not given.

• Enter the script name in the below mentioned place.

• Print program for each will be defined at the payment method level.

• Two types of print programs can be defined

               Use payment medium work bench :

• In the below print program will always be a standard print program in case of PMW as it is hardcoded in the standard F110 Program .
• In the standard SAPF110V program based on the xformi indicator.

• In the T042Z table FORMI is the name of the Payment medium workbench.

• Based on the above the print program will be called.

Use classic print programs :                        SMARTFORMS:

• There is no standard way of customizing smart forms in SAP for Payment advices.
• So maintain the form names in one table based on the company code and the payment method. In the program call the form name and in the part of the code in the standard include call the form name and smart form name.
• In case of the classic payment medium programs we can custom a Z Program.
• In case of the Payment medium work bench always the program RFFOAVIS_FPAYM is called :

• So create a Z program program and then use the same calling the smart forms.
• Logic to call should be written at this place in the include :

• Fill the variable hlp_pdfformular in the program by the same form name and then instead of the above FM call the smart form FM and then fill the OTF data to either send mail or to create spool.

Adobe Forms:

• Adobe forms configuration can be done only in the Company code level not on the payment method level.
• SAP has already provided standard Adobe forms for the Payment advice.
• The same can be configured and can be used.
• Below are the steps to be followed for the configuration.

Standard adobe forms for the  F110 would be F110_AVIS_INT

• Below is the place where the Adobe form will be called and sent in either email or spool.

Any Inputs are highly appreciated.

Introduction:

‘BAPI_COPAACTUALS_POSTCOSTDATA’is a Standard SAP BAPI provided to post COPA documents in the system. This BAPI is ideal to post CO-PA documents through ABAP programs by providing all requisite information as input.

As-Is situation:

• Currently SAP is using the below mentioned function module to execute the KE21 transaction for posting CO-PA documents.

call function 'RKE_CREATE_BATCH_INPUT'
exporting
erkrs       = p_erkrs
group       = p_sesion
user        = sy-uname
tables
ep_tab      = it_batchinput
fieldtab    = it_dbtable
exceptions
no_ep_found = 1
others      = 2.

• Once the above sessions are created then run the below program

submit rsbdcsub exporting list to memory
with bis      = sy-datum
with mappe    = p_sesion
with von      = sy-datum
with z_verarb = true
and return.

• The above FM creates a BDC and creates the session for which it will be run from SM35 Transactions.

Cons of using the FM 'RKE_CREATE_BATCH_INPUT'

• In case of any errors the entire session has to be reprocessed.
• Also time taken to create the session and the run the session in SM35 is tedious job.
• No track of the Document number in the output display is possible if the posting is done through the standard reporting.
• Many performance impacts are possible as we are using the BDC recording.

Usage of the BAPI ‘BAPI_COPAACTUALS_POSTCOSTDATA’:

• The mentioned FM can be replaced with the BAPI

  call function 'BAPI_COPAACTUALS_POSTCOSTDATA'
      exporting
      operatingconcern = i_erkrs
      testrun          = i_testrun
      tables
      inputdata        = t_dat
      fieldlist        = t_field
      return           = t_return.

The above BAPI provides the below advantages for postings :

• Test Mode functionality for which it will identify if there are any errors which are present.
• In the return parameters if there are errors in the postings then the erros can be shown in the report .
• Individual document postings are also possible which was happening as a session in the case of the above BDC Fm.
• Below is the sample code with which shows program logic to post CO-PA documents using BAPI ‘BAPI_COPAACTUALS_POSTCOSTDATA’.

f_dat-record_id  = w_recno.
f_dat-fieldname = 'WWTP'.
f_dat-value     = w_bukrs.
append f_dat to t_dat.

clear f_dat.
f_dat-record_id  = w_recno.
f_dat-fieldname = 'WWACT'.
f_dat-value     = <fs_final>-wwact.
append f_dat to t_dat.


clear f_dat.
f_dat-record_id  = w_recno.
f_dat-fieldname = 'WWAT'.
f_dat-value     = <fs_final>-wwat.
append f_dat to t_dat.

clear f_dat.
f_dat-record_id  = w_recno.
f_dat-fieldname = 'VRGAR'.
f_dat-value     = 'J'.
append f_dat to t_dat.

clear: f_field.

f_field-fieldname = 'WWTP'.

append f_field to i_field.

clear: f_field.

f_field-fieldname = 'WWACT'.

append f_field to i_field.

clear: f_field.

f_field-fieldname = 'WWAT'.

append f_field to i_field.

clear: f_field.

f_field-fieldname = 'VRGAR'.

append f_field to i_field.

Call function 'BAPI_COPAACTUALS_POSTCOSTDATA'
exporting
operatingconcern = i_erkrs
testrun          = i_testrun
tables
inputdata        = t_dat
fieldlist        = t_field
return           = t_return.

If the posting is successful

if sy-subrc is  initial  .

call function 'BAPI_TRANSACTION_COMMIT'

exporting
wait = 'X'.

                             Endif.

• Use the below enhancement to fetch the document number from each posting :
• Before calling the BAPI 'BAPI_COPAACTUALS_POSTCOSTDATA' write the below code.

• Inside the FM RKE_SERVE_ACT_DOC_NUMBER write the below code and fetch the document number as mentioned below :

• So after the posting of the each document number we can fetch the document numbers if the posting is successful which makes life easier for the reporting as shown in the below screen shot.

• For more details on the BAPI read the below documentation :

SAP standard Report for testing the above BAPI:

• SAP has provided a standard program for the COPA_BAPI_TEST through which the postings can be tested as done in the KE21 report.
• Below are the steps for which this BAPI has to be tested.When you enter the BAPI it will have an option to enter the operating concern and do the postings based on either Costing-based or account-based.
• 
  

• Then it will provide various option through which posting can be done as done in case of KE21.

• The same can be first tested which the above BAPI and can be copied and customized for further custom requirements.

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

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		Blog | GitHub | Mustafa Aydogdu

EXTENDED BUBBLE MATRIX		COMPETITION CHART
Blog| GitHub| Annie Suantak 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

FOOTBALL HEATMAP

Blog| GitHub | Mustafa Aydogdu

MINI CHARTS

Blog| GitHub | Mustafa Aydogdu

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

GitHub | Vidur Shailendra Bhatnagar

HELLO WORLD EXTENSION

Blog | GitHub | Matt Lloyd

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]

The SAP Help says the following:

Source: SAP

This document covers the second part of the paragraph.

Figure 1

Figure 1 shows by going to Tools >  Preferences > Application Design > Application Templates,  you store the path to

the folder where these templates are stored

In this example, I also create a template category called "Custom Category"

Figure 2

Now to export the application, go to the menu as shown in Figure 2, select Application > Export as Template

Figure 3

Click Next to continue

Figure 4

Figure 4 shows you can add a custom icon for your template, along with a description.  You also assign the template a category

Figure 5

To access new custom template select File > New and you can see the Custom Category created at the bottom of Figure 5, along with the icon

Because I am a big coffee drinker, I thought, why not see where coffee is produced and where it is consumed?  What are the top coffee consumers and producers?

First I ran a query at USDA site http://apps.fas.usda.gov/psdonline/psdQuery.aspx

Unfortunately you can only select one measure at a time.  First I selected consumption and saved it to an Excel file.  Then I selected production.  Now I have two Excel files and I want to compare production versus consumption.  I could use a VLOOKUP in Excel to join the two, but I have always struggled remember the syntax.  Also Excel is not always an "analysis-friendly" tool.

So now I will try it with Lumira:

First, acquire the consumption data.  Then add the production data

Go to the Visualization Tab to “Link Datasets”

Define the link - in this case, based on country:

Create a simple visualization from coffee production dataset

Switch to consumption dataset

Now rank the top 5 coffee producers

Brazil, Vietnam, Colombia, Indonesia and Ethiopia are the top producers

Maybe everyone knew about these countries - I didn't realize that Vietnam was a top coffee producer

Top consumers include Europe, United States, Brazil (which makes both lists), Japan and Canada

Reference

Introducing Data Blending in SAP Lumira 1.27

Joining vs Blending in SAP Lumira 1.27

Long term planning is being used to simulate the future demand in all BOM levels. Main intension is to check the capacity situation, material requirement and vendor /supplier ability to provide the material in proper time. This is not an actual run but a simulative run where actual plan is not being affected. It is possible to transfer the plan from simulative area to operative area if through simulation it is found that all capacity and requirement can be fulfilled.

The main objective of LTP are:

• Reconciliation of capacities.
• Forecast of purchasing element
• Simulation of demand program at all BOM level

The main intension of LTP is to simulate different versions of the demand program. But it is not necessary that simulative planning has to be there always with long term. It can be short term also as there is no time restriction.

Generally planned independent requirement version can be active or inactive. For LTP planned independent version should be inactive as it is a simulative version. Only active PIR version is being taken for operative planning.

Existing master data can be used for LTP. But to have a different master data (BOM and Routing) for LTP is also possible. Below are the setting.

BOM: A special LTP BOM can be created. In customizing “ Define BOM usage” (OS20) and “Define order of priority of BOM usage”(OS31) has to be defined.  Then selection ID and selection priority has to be maintained.

Below are the screens where the data has to be maintained (as already explained this is not mandatory, its the requirement of individual)

The customized selection ID has to be given in LTP scenario to have a different master data.

Routing: To have a different routing data in customizing “define scheduling parameters for planned orders” (OPU5) has to be maintained.

Double click on and select new entries.

To run LTP first we have to create planning scenario (MS31).

Initially the status will be not released

Planning period will be the time between which the PIR will be considered.

Opening stock can be considered as per the selection.

As well whether to consider SO or to switch off PTF , whether to consider receipt etc can be decided in planning scenario.

Here we can also select BOM selection ID if at all we want to use a different master data (BOM).

Now we have to select 

We have to assign the version in the scenario.

As well we have to assign plant to the scenario and confirm so that the scenario will be applicable for that particular plant

Then the scenario has to be released

After releasing the screen will look like below. The scenario will be released.

If some parameter has to be changed in the scenario in future then in MS02 first we have to do “cancel release” and then change. Again we have to release after change.

Now create the independent requirement (MD61).

Now check MS04. There will be no change in MD04 as the requirement is with inactive version.

Now run LTP with MS02

Again check MS04. Planned order got created.

By this all the requirement element can be checked for the future availability. As well capacity can be checked also from CM38.

Detail overview

The detail can be seen as per the proposals.

Standard overview

In this view the load can be seen. This is the deciding factor for considering the requirement in LTP and whether to enhance capacity. Decisions are being taken for future course of action regarding capacity.

Once the simulation is fine then the version can be copied through MS64.

Generally if the simulation is fine and workable in future dates, the same requirement can be sent in operative planning. The data can be seen in MD04 once the requirement came in operative planning.

Best regards,

Krishnendu.

Currency Hedging is the act of entering into a financial contract in order to protect against unexpected, expected or anticipated changes in currency exchange rates. Currency hedging is used by financial investors and business to eliminate risks they encounter when conducting business internationally. Hedging can be likened to an insurance policy that limits the impact of foreign exchange risk.

Hedging can be accomplished by purchasing or booking different types of contracts that are designed to achieve specific goals.These goals are based on the level of risk the customer is exposed to and seeking protection from and allow the individual to lock in future rates without affecting, to a great extent, their liquidity.

Hedging can be a very complicated enterprise. The various hedging mechanism range from basic to extremely intrincate.

Scenario

Here is an example of hedging currency in a scenario which combines 2 Treasury Product Types

t0:      Contract is created

t1:      Guarantee is payed

t2, t3: Monthly Financial Closing

t4:      End of the Contract

Between t1 and t4 the Contract suffers form market volatility. The variations above or below the agreed spot rate are credited/debited from the bank account every day, so at the end (t4) you don't have to pay/receive in full the difference, you have done it during the contract.

Start Date:   01.12.2015

End Date:    31.03.2016

Ex Rate:      11,0000

t0 Ex Rate:  10,0000

Requirements:    SAP ERP EhP 4 or above

                            Extension:                  EA-FS

                            Business Function:     FIN_TRM_LR_FI_AN

                                                               FIN_TRM_LR_FI_AN_2

t0: Contract is created

tx: FTR_CREATE

Product Type:        76A

Transaction Type:  100

Business Partner:    3730010 (in this example)

Select your option

Flow Type 1300 is for Profit / Loss Accounts in the Premium. Flow Type 1302 is for Balance Sheet Account.

Exercise Period  ->  End of Contract

Exercise Type    ->  European (same date as Exercise Period),

                                American (Any date between start date and Exercise Period)

Settlement          ->  Physical (Create a new transacion ; 60A - 101),

                                Cash Settlement ( Settle in this Transaction )

Points Quot        ->  The Premium is a fixed amount

Percentage        ->   The Premium is a percentage of the Contract

Payment Date    ->  The day the Premium is payed

Curr                   ->   Premium Currency

Amnt                  ->   Premium Payed (Guarantee)

Go to Underlying tab and complete the contract

Complete the information of the contract

FTR_CREATE calls TI71.

tx: FTR_EDIT

If you want to change the transaction, use FTR_EDIT or TI72

Settle the transaction.

FTR_EDIT calls TI75.

Until now we have created the Forex hedging, but we need a Product Type to register market fluctuations.

We are goingo to create a Security Product to administer this fluctuations.

tx: FWZZ

Product Type:    70C

There are some considerations in this Value:

- Min Price flow:        Minimum value the price modifies this value

- Index points:          The value in points of the index

- Value:                    The price for the index point defined in "index point".

                               in this case, as we are not interested in Index, we can use a 1:1 relationship

- Start of Term:        The day the Value starts

- Last traded day:    The last day you can trade a Value

- Expiration Date.    The day the value ends

Entered but not used

- Securit. Index.:      An index to use as a reference (SP&500, Nasdaq, etc). in this scenario there is no index

- Index Point val:      The value of Security Index point in Value Currency

- Crcy IndexPoint :  The Currency of the Sec. Index Point

In Exchanges tab, complete the market

Save the Value

tx: TPM4

Create a Security Account for Hedge instrument

t1. Premium is payed

tx: TBB1

Post the Premium (Guarantee)

Now the premium is posted, we use Security Product (Prod type 70C) to reflect the fluctuations.

tx: FTR_CREATE

Product Type:          70C

Transaction type:     400

ID Number:              HEDGE_CURR

Sec. Account:          HEDGE_ACC

Payment Date:        03.12.2015

Number of units:     1.000,00

Price.                      11,00000

FTR_CREATE calls TI5AN

tx: TBB1

Product Type 70C doesn't need to be Settled.

When you run TBB1 it changes the Position Status from P (Planned) to F (Fixed).

From t1 to t2

During this period you register market fluctuations. The Bank account is credited/debited if the market price is above or below spot rate.

You enter market price with tx FW17. The daily variation is calculated with tx PMVM.

tx: FW17

tx: PMVM

The variation between 03.12.2015 and 04.12.2015 is 0,0154 and this is reflected on the FI document.

Next day 07.12.2015 the next value is 11,0150 so the variation is -0,0004

All variations are reflected on the Bank Account.

t2, t3: Period Closing

At the end of month (or year), you prepare the Financial Closing process and FSCM-TRM is part of it.

One of the processes involved is valuation. You will valuate your asset with the value at the end of period.

tx: TPM1

Nominal Value:    11,05

Key Date:            31.12.2015

In TPM1 you set your G/L Asset Account from PMVM to 0 and send the accumulated variations to Profit/Loss Account.

If you do Valuation without reset, the journal entry on 01.01.2016 is not created.

t4: End of Contract

At the end of the contract you have 2 transactions to close, 76A & 70C.

As the sum of daly variations of Market Valuations represents the difference between spot rate and close rate of the contract, Product Type 76A should have no Proft/Loss but it will be posted by Product Type 70C.

tx: PMVM

Post the variation of the last operations day (31.03.2016)

At 30.03.2016 the price is 11,4975. At 31.03.2016 the price is 11,5000. If we have 1.000,00 units the variation is

1.000,00 * ( 11,5000 - 11,4975 ) = 2,50

tx: FTR_CREATE

Sell the position in HEDGE_CURR with Prod type 70C - 500 on 01.04.2016

The Price is the same as the last day of the Contract. Price:  11,5000

In case the Security Class ends the last day of the month, the reclassification from Asset to P/L Account will be done by TPM1 and the next month it will be definitively posted with TPM18.

Example:

31.03.2016             tx: PMVM                                                                            (Last Operations Day)

                                                   40     Bank Incoming                     2,50    

                                                   50     Other Asset                          2,50-

                               tx: TPM1                                                                             (Accumulated P/L)

                                                   40      Other Asset                     500,00     

                                                   50      Incoming Ex.Rate            500,00 -

01.04.2016             tx: TPM1                                                                             (Reverse  Valuation)

                                                   40      Incoming Ex. Rate           500,00   

                                                   50      Other Asset                      500,00 -

                               tx: TPM18                                                                           (Derived Business Flow)

                                                   40      Other Asset                     500,00

                                                   50      Incoming Ex. Rate           500,00 -

tx: FTR_EDIT

Change the settlement for transaction 76A from "Physical Exercise" to "". FTR_EDIT calls TI72

Exercise the transaction. FTR_EDIT calls TI86

Settle the transaction. FTR_EDIT or TI75.

In case the transaction doesn't post because of "0" PaymtAmt, you will have to use Settlement "Physical Exercise"

tx: TBB1

Post the transaction.

Here is an example of Prod type 76A & 70C

tx: TPM18

Post Derived Business Transaction and create the operation Profit / Loss.

Additional Information:

In case you recover the Guarantee, you need to create a new transaction with Prod Type 76A - 200 and sell your Foreign Exchange Position with the same values as the created in t0. In this case Settlement is "Physical Exercise". Post the transaction (tx TBB1) and Exercise it (tx TI86)  creating a subsequent transaction (Prod Type. 60A -101 ), but after you created it you have to reverse.

Journal Entries

Hy,

today i would like to write about test case management with the net weaver gateway client. I really like the NetWeaver Gateway - it's so simple to provide SAP backend data to a consumer & provided functionality is good. There are some restrictions, but i'm sure it will greatly improve with future releases.

So let's talk about testing:

I would like to give you an idea, how we set up testing your oData services with the NetWeaver Gateway client.

Why is it important to create testcases in the NW GW client?

For me, there are several reasons why creating test cases is important. There is plenty of documentation around for this topic so therefore i just want to point out some of the major reasons.

- Test Cases help to understand requirements & fasten up checks to proof, that a requirement was implemented properly.

- Changes can be checked against proper testcases

- The next developer who has to maintain the service doesn't have to check docu or even the programm to verifiy if his don't affect the current logic in a negative manner.

- After an upgrade, the service can be checked faster if it works still correct

- The customer can be involved to define test cases & therefore has to maintain proper test data

First of all, for every service we created there is a corresponding test group - containing all test cases related to the service.

1) How to create a Testgroup?

In /IWFND/GW_CLIENT transaction, run a request for e.g. GET and one of your EnittySets. After execution (works also if you didn't execute the request) hit the save button. There will be a popup asking you to enter testgroup and a description of your testcase.

2) How to add a testcase to the testgroup?

Execute Request in NW GW client and hit the save button aftewards. Select the testgroup you've created, provide a description & the new testcase is saved.

3) How to run a testcase?

Hit the select Button (with blue Database icon) and choose your testgroup or service name. You will get a list of your saved testcases. Select an entry in the list and hit run test button.

4) How to run multiple tests at once?

If you selected the testgroup you can select multiple testcases in the list displayed and hit the button run tests.

5) How to chain tests?

I usually make a create testcase first. Afterwards, i take the id & continue with read, update,delete testcases. If there is no id or other unique identifier present, i just execute all testcases at once.

6) How to set a expected result.

For every testcase you test, there is the possibility to set the expected result. The expected result represents a expecetd http status code (eg. 200, 204 and so on). This can be done e.g on the overview list of the executed testcases or on the list displaying the testcases of a testgroup.

7) How to arrange test cases?

For myself i've created the following naming convention, which worked nice up till now.

0000 - Metadata : This testcases has the metadata request of the service

0101 - Entity1 - Operation 1

0102 - Entity1 - Operation 2

0201 - Entity2 - Operation 1

Z-Description - Testcases, that i created to test specific things not coverad in the numbered testcases.

I hope this document helped you to get started with test case management with the NetWeaver Gateway client. Let me know, if you require printscreens oder oder documentation to manage the testcases.

I wish you all a nice day & enjoy the last days of 2015.

Kind regards,

Michael

Olá Caros Colegas,

Por gentileza, alguém poderia me ajudar com este caso de desconto no pedido de compras para ser contemplado na entrada da NF-e.

Estou configurando 2 tipos de condição para serem contemplados no campo redução da NF-e de entrada, já os adicionei

na configuração da J1BTAX.

O esquema é o "ZLOCBR" mesmo, é porque a matriz fica no México e eles criaram este esquema específico para Localização Brasil (Com Cópia do RM0000).

No pedido inseri o tipo de condição RB00, Mas na MIRO entrada da NF-e não está sendo contemplado este valor.

Nosso Release é o SAP ECC 6.00 e o Support Package Level é o 0025

Alguém tem idéia do que pode ser, ou será que tenho que aplicar alguma Nota SAP?

Agradeço desde já atenção de todos!

This document was generated from the following discussion: Condição RB00 Não Concebida na NF-e

• WARN: windows platform for mobile is only supported on windows desktop! You cannot use a mac for this!

• Install and set up environment
• Make sure node and npm is installed
• there is a bug: you can/should use the latest version but then you cannot use proxy, so use direct internet access !
• Make sure cordova 5.0 installed (check with cordova -v)
• Take a kapsel drop: this should contain the Kapsel plugins for iOS, Android, Windows.
• Create and set up a new cordova app with logon plugin
• cordova create PATH ID NAME



• Go into the folder created by the previous command
• Add the platform
• cordova platform add windows
• Add the Logon plugin
• cordova plugin add kapsel-plugin-logon -sourcepath <path of 'plugins' in kapsel drop>
This will add every dependency of the Logon plugin as well
• Make sure all the necessary html/js is prepared for the platforms
• cordova prepare
• Open the solution (CordovaApp.sln)
• The solution will automatically be  migrated to Win8.1
• Remove the unnecessary 8.0 project
• Add the SampleFileCertificateProvider
• Download the SDKKapselSamples from github.wdf.sap.corp latest version as a zip. Unzip it somewhere.
• Take the SampleFileCertificateProvider project folder with all of its content (beside the .sln) and copy to the windows platform directory
• download from github
• copy to the generated app's platform\windows directory
• Add the SampleFileCertificateProvider sample project to the solution.
• right click, add existing project... select the SampleFileCertificateProvider.csproj
• Since the sample provider implements and interface which shipped in the kapsel drop you should set up the references: add the interface definition reference in the SampleFileCertificateProvider:
• references right click, add reference...
• browse the kapsel drop\plugins\logon\windows81\bin
• select all files
• select the SAP.CertificateProvider.winmd
• In order to use it in the app you should set up the references to it (for the CordovaApp.Windows and Phone as well)
• Add to the References: rigth click, add reference, solution/project and select the SampleFileCertificateProvider
• make sure the rpoject dependencies are correct, so the SampleFileCertificateProvider will be built before the app: check build dependencies/project dependency to the SampleFileCertificateProvider
• Add the necessary resources to the app
• If you haven't done in the previous step, download the SDKKapselSamples from github.wdf.sap.corp latest version as a zip. Unzip it somewhere.
• Go to the CertificateProviderCordovaSample folder
• Copy the index.html to the app's platform\windows\www folder and overwrite the existing file there
• Copy and add an AppMetadata.json file to the app project (CordovaApp.Windows and Phone), this is used to load the proper provider class. Its content should be similar:
• { "com.sap.certProviderClass" : "SAP.Sample.CertificateProvider.FileCertificateProvider,SampleFileCertificateProvider,ContentType=WindowsRuntime" }
• properties: Package Action=Resource; Copy to Output Directory=Do not copy
• Copy and add the MAFTEST.p12 file to the project
• properties: Package Action= content; Copy to Output Directory=Copy Always
• Build and run
• First click on the the logon button: a massge should appear as registration successful.
• click on sendrequest: a html screen should present with a fiori app

A new User Experience with SAP Business Client*

*SAP Business Client 6.0 is the new name for the latest version of SAP NetWeaver Business Client

iOS

1) Create Kapsel project or a Fiori Client application from the latest SMP SDK.

2) Set the following parameter in the LogonInit function.

setAutoSelectCertifcateConfig( autoSelectSingleCert)

parameters:

autoSelectSingleCert: boolean type

Fiori Client can specify this property as a new fiori url parameter "autoSelectSingleCert". It can also be specify in appconfig.js

2) Fiori Client specification:-

For fiori client, the above settings will be persisted in the similar way as other application settings by apppreference plugin, such as DemoMode.

The logon plugin will not need to have any change for this feature.

For regular kapsel project, the index.js should call the authproxy js setAutoSelectCertifcateConfig method in onDeviceReady method.

4. How to test :-

4.1 Set fiori configuration to enable autoSelectSingleCert.

For fiori client, update appconfig.js to set autoSelectSingleCert to true as below,

      "autoSelectSingleCert": true,

or set the fiori url with the parameter of  "autoSelectSingleCert=false"

4.2 disable logon to provide cert automatically

    A new authproxy preference CredentialSearchSource in config.xml can be used to test this feature with logon plugin afaria certificate provide, it your testing gets the client certificate from a different way other than from logon plugin, then you do not need to use the CredentialSearchSource setting for the testing.

First set CredentialSearchSource to 5 in config.xml as

    <preference name="CredentialSearchSource"value="5" />

and then do anafaria NO-SMP certificate registration, setting CredentialSearchSource to 5 will skip logon plugin as credential source when authproxy tries to get the client certificate for mutual auth.

  Some of the things that happen when an update occurs are the following:

1. If unique indexes exist (e.g., primary key), verify that that the new key (if changed) is unique.
2. If RI is involved, make sure no foreign key relationships are violated.
3. If there are BEFORE (or INSTEAD OF) triggers, fire those triggers.
4. Update each modified index key.
5. Write the record to the table.
6. If RI is involved (e.g., cascade operations) modify all "child" tables (and recurse downward as necessary).
7. If AFTER triggers exist, fire those.
8. If replication involved, write the record to the replication queue.
9. Unlock the record if necessary

Of those things, the potentially expensive ones are triggers and RI. A trigger could obviously run a long time (it is user defined), but it would not typically block other operations. RI is relatively expensive, but one update should not typically take longer than another. 

Here is what might be happening:

1. Some user A causes an large index scan on this table. An obvious way this could happen is by setting a filter that covers most/all of the index (e.g., a query/filter with EMPID > 1" which would cover the entire table. Setting such an AOF could end up reading the entire index (while holding a read lock). Another possibility would be reading the table in index order while a restrictive filter is set. Scanning from one record to the next record that passes the filter could read a large number of index pages.
2. While user A scans the index, user B updates the table. It would block on that index scan while waiting for the write lock.

If the index is highly fragmented, an index scan (the first time through) could be very expensive. Once the index is cached, subsequent operations would be much faster (probably).

If this is the problem, it would make sense to re-index the table. And you might consider using a larger index page size (if you are using ADT tables). A larger page size can help mitigate the cost of large index scans on fragmented indexes.

We can use number sets to classify a product for multiple customs codes for more than one country and for multiple application area .

Here we can check how to implement this feature in SAP GTS.

1. Defining Number Set Schema

Execute transaction SPRO.

Global Trade services -> General Settings -> Numbering Schemes -> Define Numbering scheme and structure of Numbering set

2. Define Number Set Structure

Now We have to define a reference structure to which the user and system can refer during the classification process in product master.

Reference structure you can copy from the existing numbering scheme .

For creating the entries,I have used EUSTA as reference structure .

3. Assign Numbering Schemes to Set Schema for Classification

Global Trade services -> General Settings -> Numbering Schemes -> Assign Numbering scheme to Set Schema

Save the entries.

4. Create Number Set

SAP Global Trade Services -> SAP Customs Management -> Classification -> Number Sets -> Assign Numbers to Sets

Select Create Number set

Use the input help to enter the generic part of the customs code number. This input help functions in exactly the same way as the standard classification help function.

Use Generate Set Number ,The system generates the number set and displays the generic customs code number in the field next to the name of the number set at the top of the screen.

Save the entries .

5. Classify Product using number set

Select assign numbering set

Select the schema's and use Assign Set button

There is an optimization to number set functionality available for the  below releases from the mentioned SP on wards.

Please refer the note  2170205 - Optimization of number set functionality in product classification