SAP Design Studio transitions your big data to meaningful data, in attractive visualizations, enabling

you to easily convey knowledge, discover hidden patterns, & transform the way you do business

I started my career with SAP Basis and now after completing more than 5 years i really enjoy working as a Basis Consultant .The most important aspect for SAP Basis is troubleshooting when an issue occur .Here are some of the points and observation I want to document which can be helpful for a new resource in this practice.Any thing that occur has a logical reasoning nothing happens on own.So when an issue occurs we need to find what has changed whether there i a transport or any activity that has messed up.We have to not to be stubborn in our thinking for fixing an issue .We have to see over all perspective of an issue and to start troubleshooting from Scratch .

Also i think we should not trust on any one and double check every logs ,connection ,user ids and basic things.At some time in my career i have observed issue at a very ground level and wasting my time for more than 3-4 days.So initially we have to check and start from Basic level.We need to confirm from our level every thing rather than relying on others.Our motive should be positive and seeing from every perspective.

Issue can be at any level :-

Database

Os Level

Appliation Level

Network level

If we see any recent activity on these level then we can check logs at these first.

Also the important point is we have to be positive, energetic and never give up attitude while fixing an issue .At times in SAP Market i see people like only installing a SAP System like a binary software .But our profile is to Maintain SAP and keep it up and running 24*7.

HANA Rules Framework (HRF) vs. Business Rules Framework Plus (BRF plus) for Public Sector

SAP provides many tools to help customers get the most from their technology investment. In this educational blog post you will learn which public sector business scenarios are best for HRF and which for BRF plus.

18 December 2015

Internet of Things (IoT) – The Next Big Thing in Public Sector?

Is the Internet of Things (IoT) relevant for public sector? A wise man once said, "follow the money." Governments in the US and UK are funding IoT-related projects in broad competitions to bring about real benefits for citizens. Where government spends, industry goes.

9 December 2015

Australia, Germany and a lot of diverse digital insights

Australia hosted a diverse group of public and private sector leaders from Germany and Australia. The German-Australian working group met to discuss Australian-German trade, cultural and political ties, technology transfer, and collaboration on the world stage. SAP and Siemens were invited to the group as technology leaders to look at how technology can play a role in the relationship for the benefit of both countries.

2 December 2015

Transforming Government for the Digital Era with “Post Modern ERP"

Gartner defined post-modern ERP and public sector organizations want to know SAP's position on the subject. How do SAP public sector industry solutions and future roadmap stack up against this definition? Pretty well, in fact.

4 November 2015

SAP TechEd is coming soon - We know, these large events can be overwhelming. Wouldn't it be cool to meet in advance with experts and to “extend” the SAP TechEd event regionally?

At our informal after-work events you will hear from SAP TechEd veterans (our SAP Mentors) on how you get the most out of the event, how to survive, how to plan your agenda, what sessions to attend, where to go….

It is a great chance to meet some of the people that are also going to SAP TechEd, to network, to share what's new and what's important within our local SAP community - while having a beer and snack.

Please find below a list of upcoming community meet-ups - Please use registration links to sign up.

We are looking forward to see you there (and to see you finally at SAP TechEd).

**These meet-ups are driven and initiated by SAP Mentors!**

PAST:

Country	City	Mentor Names	Planned Date (or range)	Location	Blog Link	virtual/in person	comment (e.g. ready to publish/status)
Brazil	Porto Alegre	Eduardo Chagas, Karen Rodrigues	Sep 24th	Porto Alegre - Fontoura Education	link	In Person	DONE
Turkey	Istanbul	Abdulbasit Gulsen	Oct 21th	Buyaka	SCN Meetup Istanbul #3 - Are You Ready for SAP Teched ?	In Person	DONE
Germany	Würzburg	Florian Henninger	Oct 6	Maulaffenbäck	no blog, sorry	In Person	SAP Stammtisch Würzburg DONE

An Activity list is a group of activities, these are used for mass creation of activities, for either one person or for multiple people.

Here, you could select accounts or contacts and it will automatically create activities based on the selection and additional information maintained. Additional information could include details like, the subject, the start and end time. Once this is activated this schedules tasks to be performed by the owner. You can define this for any number of customers.

How to add Activity List Feature:

1. Go to the "Business Configuration" work center.
2. Select the "Project".
3. Click on "Edit Project Scope".
4. In Scoping tab, make sure that the "Activity Management" is Scoped.
5. In Questions tab -> Scope the question "Do you want to record information from activity lists in your system?"
6. Finish your scoping changes.

How to Use Activity Lists:

1. Go to the "Activities" work center.
2. Go to the "Activity Lists" facet.
3. Click on "New" button to create the "Activity List".
4. Select the "Activity Type" for which you want to create the list.
5. Add the Name, Start Date/Time, Owner.
6. Click on "Save and Open".
7. Edit the activity list created.
8. Enter Other Details like End Date/Time, Notes (if any), Priority, Category.
9. Select the check box "Owner Determination" if you want the determination of owners of the added appointments/activties to be redtermined based on the Determination Rules Maintained in the system.
10. Select "New" button to add the "Appointments" from Account/Contact/Individual Customer.
11. Select the "Action" button and set the "Activities List" as "Active".

Points to be Noted for Activity Lists:

• The Owner of the Activity list will not be assigned as the owner of the individual activities/appointments added in the list.
• The person who creates the activity list is the owner. If you want to change/reassign this owner, do it manually.
• To do the changes in the activated activity list, change the status to "In Preparation" by using the "Actions" button.
• Any number of activities can be added to the activity list using "New" button (From Accounts, Contacts, Individual Customers).
• Once you activated the "Activity list", the scheduling takes the start and end date of the activity list.
• To schedule the uploaded activities/appointments in the activity list, Edit the activity list, add Start Date/time and End Date/Time, Save & Activate the activity List.
• If you want the activities to be created in sequence, then you can maintain duration and gap, but leave end time blank.
• The information at Header becomes the template:
  • Start/End time of list get determined based on the Duration & Gap maintained at header.
  • Details like Notes, Subject, Category, Priority get transferred from the header to the activities added.
• The owner can be maintained or derived based on standard owner determination fine tuning. Please see case document "2116706 - Activity Owner Determination in Activity Lists" for Activity Owner Determination.

This document is applicable for Solution Manager 7.0 EHP 1

1. Login to solution manager system and navigate to solman workcenter via transaction ‘solman_workcenter’.

2. Navigate to tab ‘Root Cause Analysis’. Under section ‘Administration’, click on ‘Agent Administration’.

3. Navigate to ‘Application Configuration’ tab.

4. In ‘Agent Applications’ column, select application ‘com.sap.smd.agent.application.wilyhost’.

5. Navigate using dropdown menu in ‘scope’ to required hostname.

Note: Solution Manager Diagnostic Agent should be running on managed host to appear in scope.

6. Using ‘Edit’ button, switch to change mode.

7. Using ‘Add Property’, add properties –

Property Name: jco.client.passwd.<SID>|<hostname>_<SID>_<Instance No.>

Property Value: <password>

Property Attribute: Check secure property.

Note: Remember to check ‘secure property’ as it encrypts fields.

Similarly, for user -

Property Name: jco.client.user.<SID>|<hostname>_<SID>_<Instance No.>

Property Value: <user name> i.e SMDAGENT_XYZ

8. Click on ‘save’ once done and a pop up message appears indicating successful store.

Getting any errors while saving? 'Failed to save the configuration com.sap.smd.agent.application.wilyhost'

Solution: Remove any space from ‘Property Name’ column

9. Navigate to application ‘com.sap.smd.agent.application.wilyhost’ --> ‘Application Resources’ --> ‘SapAgentConfig.xml’

10. Select ‘Scope :’ <hostname> and upload file with new property –

Below are the contents that needs to be updated in property file -

<destination name="<SID>|<hostname>_<SID>_<Instance No.>" class="com.sap.smd.wily.hostagent.destination.JCODestination">

<property name="jco.client.client" value="<Client No.>"/>

<property name="jco.client.passwd" ageletConfigConfigstorePropertyKey="jco.client.passwd.<SID>|<hostname>_<SID>_<Instance No.>"/>

<property name="jco.client.user" ageletConfigConfigstorePropertyKey="jco.client.user.<SID>|< hostname>_<SID>_<Instance No.>"/>

<property name="jco.client.sysnr" value="<Instance No.>"/>

<property name="jco.client.ashost" value="<Hostname>"/>

</destination>

These changes won’t require restart of SMD agents.

The EIM Bulletin

The EIM Bulletin is a timely and regularly-updated information source providing links to hot issues, new documentation, and upcoming events of interest to users and administrators of SAP Data Quality Management (DQM), SAP Data Services (DS), and SAP Information Steward (IS).

Customer Virtual Coffee Corner for SAP Data Services

Please join the EIM Support Team during our next Customer Virtual Coffee Corner session for SAP Data Services!

EIM Meet the Experts Sessions

The EIM Meet the Expert Sessions have been created to provide opportunities for SAP Enterprise Support and Max Attention customer to obtain in-depth knowledge regarding multiple EIM products. Come register for our next session!

What Is Dirty Data Costing You?

Intrinsically, you know that you need good data. But how far do you need to go? What are the real costs incurred if you DON’T have clean data? Check out this new SAP Data Quality infographic, which highlights the probably extent of your data quality problems, and the costs associated with those problems. This blog by Ina Felsheim also links to the popular Information Governance infographic.

EIM Integration Use Cases

Read Ina Felsheim's blog to find out about integration use cases related to SAP Data Services, Information Steward and Master Data Governance.

Innovations in SAP Master Data Governance 8.0

To find out about the innovations that have come with SAP MDG, release 8.0, read the SCN blog by Markus Kuppe and the complementary blog by Steffen Ulmer. 9 November 2015

SAP Master Data Governance in 3 Minutes

Learn what SAP Master Data Governance is all about by watching these new videos

Key Things to Know When Updating BI and Installing Information Steward

SAP analytics customers have benefitted from the fact that our SAP BI applications and our Information Management solutions – SAP Data Services (DS) and SAP Information Steward (IS) – share a common platform, called the Business Intelligence Platform or BIP. Thanks to these shared platform services, administrators have a single environment for creating and maintaining users, but there are some constraints. In this blog, Paul Medaille points out some key dependencies that customers need to know.

Here SAP Contact Center support team is posting an update when a new hotfix is released for SAP Contact Center 7 SP8 / SP8 Patch1 release. Please note that the official information will always be on SAP Market Place. The purpose of this document is to help you follow up what have been released.

You can easily follow this post and receive email notification every time there is a new post by pressing follow button on right hand side. (requires registration to SCN).

To keep this clean and tidy we ask you to avoid posting questions to this discussion. If you have any questions or concerns related to hotfix content please create a new customer incident under CRM-CCI or raise a new discussion to SAP Contact Center SCN pages.

// Direct links to the released hotfix notes available via the SP8 Patch 1 note 2166780 //

KBA documents related to SP8 & SP8P1 releases:

2182407 - CDT Freezing/locking wihtout any reason
2239061 - Problem with voicemail notification email attachments

Short FAQ:

Q: Where I can find document how to install a hotfix?
A: In a hotfix note, you can find instructions in solution chapter. In the Operation Guide instructions can be found from chapter 6.1 Installing Support Packages and Hotfixes

Q: What hotfixes should I install? Should I install all or can I select the one customer is needing?
A: Because of depencies between hotfixies you should install all available hotfixies. We are not able to support incompletely updated systems.

Q: Is there a sample how to install a hotfix?
A: Yes, you can find an example in SAP CCtr Advanced Training Configuration Part 2, chapter Adding Hotfix. The document can be found from SAP Market Place.

Q: From where to find SAP Contact Center trainings?
A: Trainings can found from http://training.sap.com , search for WFIBC*

Q: When I try to open compressed hotfix files the compression software gives an unexpected error. What to do?
A: From hotfix 7.0.8.109 and upwards the compression method has changed to RAR5. The files can be opened with WinRar 5.0 or later.
If you still have problems to open the package, please create an incident.

It seems that everybody understand hierarchies but it is sometimes difficult to handle them, be it

• Defining them,
• Building them or
• Rearranging them,
• Not to speak about the whole stuff in the UI.

This document want to shed some light on these tasks.

Let’s first spent some words on “What is a Hierarchy”

Hierarchy as a Tree in Graph Theory

We will focus here on those special hierarchies in which the vertices have one or zero parents and one or many children which in turn are called Tree.

Second no cycles are permitted. Therefore following the Parent relationship we will reach some vertex without a parent which we will call Root. If we follow the Children relationship to the vertices without children these are the Leaves.

All vertices which can be reached starting from the Root vertex via the Children relationship are belonging to the same Tree (= Hierarchy).

Defining a Tree Hierarchy in BODL

Of course the vertexes are the nodes and the relationships are the associations.

As the Children association has the multiplicity “to-many” we cannot use the normal Alternative Key based associations as these have the multiplicity “to-one”. Instead we had to use the addition “valuation”. As result we can only target nodes from the own Business Object.

There are two different ways to implement such a Tree Hierarchy:

1. You can define the associations on the root node of the Business Object.
   This means that the target is also the root node, but of another Business Object instance.
   So the vertexes are different Business Object instances like the hierarchy defined by the Business Object InstallationPoint.
2. You can define the associations on a sub-node of the Business Object.
   Here the Business Object itself represents the hierarchy as a whole and all the sub-nodes define the hierarchy like in the Business Object ProductCategoryHierarchy.

For the sake of convenience we will work with the second approach here.

So here's the BODL for the Tree hierarchy:

At the Root node of the Business Object we define some information about the root of Tree hierarchy like the association which can be used later as the entry point for traversing the hierarchy.

The node Vertex defines the hierarchy itself:

• The own identifier of the Vertex node.
  Please note that we did not use this identifier as Alternative Key because in that case we cannot use this value in any other hierarchy. We would need to combine it with the identifier of the whole Tree hierarchy.
• The identifier of the own parent node.
  This value will be empty for the Root vertex of the hierarchy
• The element HasKidsIndicator is needed later in the UI to determine if the expand / collapse icon shall be displayed for this entry.
• Of course the associations Parent and Children based on the relationship between the own parent identifier and the identifier of the target node realizes in the valuation clause.

Adding some ABSL Code to Ensure Consistency

We will add an AfterModify script to the Root node of the Business Object to ensure that the root vertex of the Tree hierarchy is existing

And we add also an AfterModify script to the Vertex node to ensure the correct setting of the own HasKidsIndicator which is needed after removing children and also of the parent indicator which in turn is needed after re-arranging of a sub part of the hierarchy.

Define the List as Hierarchy in the UI

First you define the list of the Vertex node instances via an AdvancedListPane, but you add the "HierarchicalExtension" to this list

Second you need to define the bindings for this special structure

This is the result if there are already some vertices maintained. You notice the triangles which tells you that this vertex has children and if the children are visible. Technically spoken: The vertex is collapsed or expanded.
The vertex has no children if there is only a square shown.

You should not show the technical fields like "HasKidsIndicator" or "ParentId", because this information is already shown via the graphics.

It may be useful not only to expand or collapse the current vertex by clicking on the triangle but to show or hide the complete hierarchy. This can be achieved by some EventHandlers with List operations, for example "ExpandAll".

Add a Vertex

Adding an vertex is best done via a modification structure in own pop-up and not inside the hierarchical list.

Please use a data operation before starting the modifications structure which sets the current node as the new parent.

Inside the modification structure let the user only chose the ID and the description of the new vertex

This will prevent such issues like more than one Root vertex.

Delete a Vertex

If you would simple delete the current row, then exact only this would happen. As consequence all children of the current row would lose their parent.

So you need to ensure that on the deletion of a vertex all children (and the children of the children and so on) are deleted too.

This can easily achieved with a small action:

So add the line

action DeleteChildren;

to your BO definition and add this ABSL coding:

Which will delete in a recursive call (depth-first approach) the children and finally the current vertex.

Reorganizing Hierarchical Structure

If you want to re-arrange the hierarchy some precautionary measures should be taken:

• Never allow a new parent for the Root vertex
• Ensure that no circles are created
• Verify if the new parent really exists.
  Otherwise you would decouple the sub-hierarchy from the rest.

The best way to ensure the later topic is to allow the user to select the new parent from a dropdown listbox. Just define a second list in the data model VertexList which is also bound to the Vertex node

Create a "NewParentId" element which is typed as a Code and bind the code list to this new VertexList using the ID and the Name.

I've added an EventHandler to "OnValueChanged" which updates the ParentId of the current selected line and does a Refresh on the VertexHierarchy.

After entering the new parent ID the hierarchy refreshes itself and shows the vertex under the new parent.

Sadly, this worked for me only in HTML5.

Now you should be able to create and modify hierarchies.

That's all, folks.

Horst

Here you will find a collection of different learning materials for SAP Cloud Identity.

Please note that these materials are not SAP official product documentation.

Video Tutorials on Youtube via HANA Accademy(April 2015)

Learn how to enable your users to authenticate against an on-premise Corporate User Store:

1. How-to Guide for authentication with SAP Cloud Identity against Microsoft Active Directory

2. How-to Guide for authentication with SAP Cloud Identity against SAP NetWeaver JAVA AS with possibility to connect to other user repositories

Learn more about Two-factor Authentication

Learn more how to customize SAP Cloud Identity UIs with your corporate branding

Integrations with other Cloud Products:

1. How to configure SAP C4C to authenticate against SAP Cloud Identity

2. How to configure SAP Mobile Secure to authenticate against SAP Cloud Identity

Normally, when we search about Dunning procedures we do get our solution in bits and pieces.

This document would provide a full solution if you want to code as well as configure your dunning procedure with smartforms.

What is Dunning?

Dunning is the process of methodically communicating with customers to ensure the collection of accounts receivable. Communications progress from gentle reminders to threatening letters and phone calls and more or less intimidating location visits as accounts become more overdue.

To automate the procedure for dunning we would need to find our BTE.

What is BTE?

For this the documents are readily available on SCN. Below is the link for the same: http://wiki.scn.sap.com/wiki/display/ABAP/BTE+-+Business+Transaction+Event

The most important step for us is to check if all the configurations are in place or not.

Step 1: Configuration of the process and the BTE.

T-code: BF44

Here we would provide our process which is indeed needed for our coding.

The product assignment should also be done here.

Step 2: Activating the customer product

Next is T-code: BF24where our product would have a text assigned and it should be activated (Activate Customer Product indicator).

Step 3: Configure the FM

T-code: FIBF

The FM here would be the one from which the standard code for smartform would be triggered.

In case of smartform you should put FM as : FI_PRINT_DUNNING_NOTICE_SMARTF

And in case you would want that to be a script the FM would be: FI_PRINT_DUNNING_NOTICE.

Under the SAP application you would be able to give the name of your BTE.

Step 4: Configure the Smartform created

This can be done using the below path in SPRO:

Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Dunning -> Assign Dunning Forms.

Select your respective procedure. This would prompt you to provide for the company code, enter as required.

Below section is the one in which you would provide your smartform name:

Now your configuration is complete.

Technical side for the Dunning procedure.

Scenario: The case would be that at each Dunning level a mail format has to be send to the customer with an attachment. This should be automated for each dunning level.

Coding in BTE.

The first step for this would be to make a copy of the sample BTE already present.

1040 is the BTE in which the coding for mailing the customer should be done.

The event for sending mail and attachment is done from the event 1720, for which Sap has already provided the coding under FM ‘PRINT_DUNNING_NOTICE_SF’.

The below structures are readily available in the FM “SAMPLE_PROCESS_00001040”. And so they would be in your FM copied from the sample BTE.

Explanations for each structure in order to code.

I_MHNK: This would have all the data for dunning. The most important ones would be the dunning date(LAUFD), ID(LAUFI), Account type(KOART), Company code and customer.

I_T047E: This would be the structure from which the form name would be passed to the standard FM for customizing the Dunning.

Structures for sending mail and attachment parameter are below:

C_FINNA: Data for Transmission Medium for Correspondence.

All the parameter required to send a mail are passed in here.

Important fields of this structure:

1.Intad: This is the field in which you would be able to pass the email address.

In most of the cases we would require multiple email ids to be sent. This can be done using the below code:

IF lw_email IS NOT INITIAL. "customer
c_finaa-intad   = lw_email.
ENDIF.

* sales representative
IF lsw_proceed2 = abap_true.
IF lw_email1 IS NOT INITIAL.
IF c_finaa-intad IS NOT INITIAL.
CONCATENATE c_finaa-intad lw_email1 INTO c_finaa-intad SEPARATED BY space.
ELSEIF c_finaa-intad IS INITIAL.
c_finaa-intad = lw_email1.
ENDIF.
ENDIF.
ENDIF.

* send to admin also
IF lsw_proceed1 = abap_true.
IF  ls1_dunn_1040-email IS NOT INITIAL.
CONCATENATE c_finaa-intad  ls1_dunn_1040-email INTO c_finaa-intad
SEPARATED BY space.
ENDIF.
ENDIF.

2.      Namep: This field would be used to pass a text name( SO10 Text), which would be used to pass the mail body of the email.

In our BTE we should pass the name and the “READ_TEXT” would be automatically done by the code in SAP.

IF NOT lw_namep  IS INITIAL.
c_finaa-namep = lw_namep .        

    c_finaa-mail_body_text = ls_dunn_text-namep.
ENDIF.

Also the field mail_body_text can be used for same purpose.

SAP standard would take this value in the changing parameter and do the below:

Always remember to create a SO10 text with “FIKO” as ID.

3.      Mail_send_addr: This field is used to specify the sender of the mail.

4.      Nacha: This field would be passed for Transmission Medium for Correspondence.

Values:

1 - Printout

2 – Fax

I - mail

C_ITCPO: SAPscript output interface

Fields:

1.      TDTITLE: This field would be used for the subject of the email and the attached document name.

If we try to change the Document name and subject we would not be able to do that for below code.

2.      All the spool/archive  parameters can be set with this structure – TDCOPIES, TDDEST, TDPREVIEW, TDARMOD.

Coding in smartforms.

Although we can create a new smartform according to our requirement but in this case we must always remember to pass a parameter in the Import Tab: IS_SFPARAM. Else there would also be an error for “ Parameter missing”.

So even assigning a new smartform created by us in possible.

In case of dunning scenario we would want many dynamic data to be placed in our smartform.

For this we would have to fetch the data in our smartform itself.

This would be possible with the parameter IS_SFPARAM. The dunning date and id could be captured with help of the SFPARAM-CONTENT field, where we would need to get the data by using offsets.

  This smartform would now be sent as the PDF attachment in the mail.

3Compared to many of the BI downloads found in the SAP Community Network, University Alliances offers the latest downloads for an extended period of 6 months from the date of installation. Check back for updated downloads and key codes!

Access SAP Crystal Reports 2013 through this link:

https://global.sap.com/campaign/ne/free_trial/crystal_reports_2013/index.epx?kNtBzmUK9zU

• Once you click on the link, fill out the registration form and click Continue
  The next page will provide 2 options to electronically download SAP Crystal Reports
  Choose option download SAP Crystal Reports 2013 Evaluation and save to a folder
  Open the file when download is complete
• Click on Data Units > Crystal Reports > setup.exe
• Choose your language and click install
• Follow instructions and read the License Agreement - please note the agreement can be found in other languages
• If you accept the agreement, click next and enter key code D720X-4UBV30S-BYN34C9-BA30040-WE
  NOTE: Use this key code (instead of what is provided online and via confirmation email)
  • It has a 6-month validity from date of installation - Please check back for updated keycodes
• Continue with the process and click install
• Once installation is complete, search for the software by going to Start
• Choose All Programs then Crystal Reports

The older 2008 curriculum and software are no longer available.

Note: This is the offline (standalone) version with no connection to any data in SAP BusinessObject Enterprise Server.

• Match specific parts of your dataset with precise locations around the world via a geographical database embedded in Web Intelligence.
• Via the graphic engine integrated into Web Intelligence, you can look for specific locations that you can link to the values of selected dimension objects
• Visualize your data on a map.

SP8 for SAP BW 7.4 has introduced BW’s newest modelling object: the Advanced DSO. The Advanced DSO is BW’s new major modelling object that  plays a central role in any SAP BW on HANA data model. It is used as a classical DSO, info cube, PSA or write optimized DSO. The Advanced DSO manages to replace all of these objects by basically being all of themWhen creating the Object you have to decide about the properties the Info Provider shall have.

Sometime we choose Classical DSO option for  data provision to next layer and so change log table comes into picture. One thing missing at the moment is the possibility to delete the Change log via process type. But according to SAP this functionality is to come in future ( may be BW 7.5 ).

At this moment, it is possible to do the deletion manually to delete the requests manually in the manage UI but no workaround to delete in batch. However, SAP has recently come with a workaround.

After implementation of this note #2253065, program“RSDSO_REMOVE_REQS_PC “ will be available in your BW on HANA system . This program internally calls Function Module M “RSDSO_REMOVE_REQUESTS_API” to delete change log requests in batch.

Take an example, DSO "Z_TEST" ADSO contains 13 change log requests.

We run program "RSDSO_REMOVE_REQS_PC" for ADSO "Z_TEST" with age 15 days

All change log data older than 15 days are deleted now.

We can create an ABAP variant having ADSO name and age of requests to be removed.

We can use this ABAP program and variant in process chain using ABAP process type to automate change log deletion via process chain.

Introduction:-

The cyclomatic complexity measures the complexity of a program and is based on the control flow graph. It is a count for the number of linearly independent paths through the source code. It was developed by Thomas J. McCabe, Sr. in 1976.

The CC goes through a coding block and counts every time,  the control flow has a new path at a specific decision point. A new path will be created due to a "IF", "ELSE", "CASE" and so on.

Ideally, the CC should be between 7 and 15 at each coding block.

1. How to configure CCN

  1.1 Open any program using Tcode “SE38”. Go to program->check->Code Inspector

  1.2. Click on Utility->Default Check Variant->Maintain

1.3 Select procedural metrics in selection screen. Click on green arrow button in front “procedural metrics”

  1.4 Select Show Metrics option. Change in “Scope and rule for metrics section as per your need”. Click on Ok     button.

2. How to check CCN

  2.1 Open  program using Tcode “SE38”. Go to program->check->Code Inspector

  2.2  Go to “Procedural Metrics “ section. Double click on the detail line as per below screen shot

  2 .3  Cyclomatic complexity number should be displayed as output.

SAP HANA memory is very expensive; it’s wise to clean out unnecessary memory when running your SAP BW system on SAP HANA. Of course PSA’s are regularly cleaned (this was usually already initiated when running you SAP BW system on a non-SAP HANA database) as no reporting is done on PSA data. Other ‘tables’ which consume a huge amount of data and which are not used for reporting are your so called change logs (delta tables).

These should be deleted on a regular basis to free up your much required SAP HANA memory.
To easily clean up change log data, the “Deletion of requests from the change log” process chain functionality can be used:

Based on which ‘level’ of your LSA++ architecture your DSO is residing, you can, for example, add several change log deletion steps. (Eg. Data Aquisition layer DSO’s can have a data retention of 30 days while Architected Data Marts have a data retention of 15 days)
The “Deletion of requests from the change log” process comes with 3 different flavours, as to be seen in the picture below:

1. Only successfully booked requests; Set this indicator if you only want to delete requests that have the quality status OK and were updated successfully.

2. Only requests with errors, not updated in any data target; Set this indicator if you only want to delete requests that contain errors and that were not yet updated or no longer exist in any data target.

3. Delete Activation Requests Only; No Load Requests; Only activation requests (requests that begin with ODSR_… ) are deleted. No load requests are deleted.

When running SAP BW 7.4 on SAP HANA, option 3 is required to actually have the process chain deleting change log data

SAP Integrated Business planning is SAP's new, state-of-the art platform for real-time, integrated supply chain planning – built on SAP HANA, for Cloud deployment. SAP IBP is being developed to deliver integrated, unified planning across sales and operations, demand, inventory, supply and response planning, as well as the supply chain control tower for dashboard analytics and monitoring.

   
SAP IBP delivers a new paradigm of user experience and efficiency, leveraging real-time dashboards, advanced predictive analytics, interactive simulation,

embedded social collaboration and Microsoft Excel-enabled planning tables.

Our IBP strategy:

SAP IBP Highlights:

SAP IBP Availability

Several of the new IBP applications are available today, with the next in the portfolio coming soon.

Find out more:

• SAP IBP Overview Video
• More IBP application details:
  • SAP Integrated Business Planning for sales and operations
  • SAP Integrated Business Planning for supply
  • SAP Integrated Business Planning for inventory
  • SAP Integrated Business Planning for demand
  • Supply Chain Control Tower
• Industry Specific Blogs:
  • Integrated Business Planning for the High Tech Industry
  • Integrated Business Planning for the Consumer Products Industry
  • Integrated Business Planning for the Chemical, Oil & Gas Industry
• Pre-Sale - SAP Integrated Business Planning FAQs
• Read the SAPInsider article: Integrated Business Planning for Demand Transparency
• Register for and listen to the SAP SCM On-Demand Webcast Series –Seven Steps to Supply Chain Transformation
• Watch the Weir Minerals SAP Integrated Business Planning Customer Story Webcast
• Get more details on SAP IBP coverage with the IBP Release 5.0 Online Documentation