Dump while exporting the ALV data into local file

Recently I confronted to one issue in ALV. ALV was being implemented through Oops and data was being displayed. Everything was perfect but when user tried to export the ALV data to local file, it was going into below dump.

This dump was coming into a standard report and the export function is also the standard one. So actually there was no point of its not working. I started debugging and the issue came out to be in our code only.

Actually we have created field catalog based on one data dictionary structure. And final internal table to be displayed was based on one locally defined structure. Now this locally defined structure was having every field of dictionary structure except one. And this was causing error.

When control was going into program SAPLKKBL it was doing a case-end case on field catalog and in each case, it will look for that field in final internal table and will try to assign a field symbol. Now because one particular field was there in field catalog but not in final internal table, it was going into the case but when it tries searching for that field in internal table it was not finding anything and field symbol remain unassigned. And this dump was coming.

Now this is beautiful. One small issue in Z code was causing dump from standard code. Strange.

Happy learning :)

Basics of ABAP Webdynpro: Getting familiar with Webdynpro jargons part 3

Internal/Context mapping: We can define context node at any of the available controller. However as WD component controller works as a global one, context node defined there is accessible in any other controller. We just have to drag and drop those WD component controller context node to the controller we want them to be used. In that case, if we define any value to this node at WD component level, this value will flow to the other controller where it has been used. And also if we make any changes in that context node in controller where it is mapped, that value will flow to WD component level also.

External/Cross component context mapping: In one of the earlier posts we have seen what component usage is all about. Suppose we are using WDC1 into WDC2 through component usage. Now context mapping between a context node, which is in interface controller of WDC1, and a context node of WDC2 will be known as external mapping. In that case context node data from WDC2 will flow to WDC1.

Hook methods: As soon as you create a WD component, many hook methods will be automatically will be available at WD component level, view level, Window Level. In one of my post, I have very elaborately described about the Hook methods and their order of triggering in normal as well as in special scenarios. To know more ClickHere and Here

Singleton Node: We will understand this with one example. Suppose there is one node which will have sales order header related information. Now this node has another sub/child node which is meant for the item level information. In normal scenario if both of these nodes are normal node, if the parent node has 10 header records, child node will have the item level information of all the 10 sales order.

Now in case the child node is defined as singleton node, this child node will only contain item level information for the sales order which is currently selected. This is huge success in improving the overall application performance.

Supply function: While defining the context node we can give the supply function also. This supply function is meant for providing a value to the context node. Supply function will gets triggered if the data of the context node is being used and its value is either initial or invalid. Context node’s value will be invalid if it’s a singleton node and the lead selection of the parent node has changed. In that case supply function will get triggered and will calculate the new value based on the parent node’s data.

Apart from the ABAP Webdynpro terms I covered in last 3 posts, I have already shared many ABAP Webdynpro related posts in my blogs. While you can go through the blog to find more, here are few links of the important posts.

Using checkbox in ALV Webdynpro with Messaging functionality 

Deploy ABAPWebdynpro application in SAP Enterprise portal 

Default leadselection in ALV in ABAP webdynpro

Disable empty rowscoming in Webdynpro ALV

Dump (System_name :is not a valid attribute type) in starting the Webdynpro Application 

Radio button as a cell editor for a column in Table UI element - Part 1 

Radio button as acell editor for a column in Table UI element - Part 2 

Different types ofwindow creation in Webdynpro

Cell Variant: A wayto use multiple editor in a single table column in webdynpro ALV 

Floor Plan Manager:FPM application using OIF

Use ofIF_FPM_UI_BUILDING_BLOCK interface in FPM and triggering sequence of itsmethods 

I’ll continue posting more basic concepts and exercises in my further post. Till then Happy Learning :)

Modify statement going into dump

Weired thinigs happen to you and you are left clueless on the root cause. This happens to me when I was doing routine coding and all ofa sudden Modify statement starts giving dump.

Lots of head scratching finally got to know the reason.

Below is my coding.

The reason is that I was doing loop on one internal table and was trying to upadte the other internal table inside that loop.

The Purpose of MODIFY statement is to modify the internal table content with in the particular loop of the internal table.

The reason for dump is I was trying to modify the unknown internal table directly.

So when I change the coding like in below screen shot, it works.