Export to flat file package- Select members issue

[Former Member]

Hello,

In Export to Flat File package, there is an option " Please select Members". We are calling dimension members that have a specific property. First time when we make this selection, the members are exported correctly. However, when there are additional members (owing to subsequent master data loads) with the same property, the new members are not getting exported. But if we make the selection again, it is exporting the new members also.

Can we avoid having to select the property everytime the package is executed?

[former_member186338 · Accepted solution]

I have found some issues with filter in the latest EPM versions...

But there is a solution - you can hardcode the filter name in the DM advanced script text:

Instead of the line:

PROMPT(DIMENSIONMEMBER, %DIMENSIONMEMBERS%, "Please select dimension", "Please select members", %DIMS%,0)

Use 3 lines:

INFO(%DIMENSIONMEMBERS%,@@@SAVE@@@@@@EXPAND@@@|DIMENSION:ACCOUNT|[FILTER:FILTERNAME]|)
INFO(%DIMENSIONMEMBERS_KEYDATE%,)
INFO(%DIMENSIONMEMBERS_DATEFROM%,)

Where FILTERNAME is the name of your filter!

Tested, working!

[former_member186338 · Accepted solution]

P.S. But based on my experience, simple custom logic badi to export data is the best solution:

Custom logic badi is launched from script file where you can define set of members not only by single property, but using multiple properties and BAS, DEP etc... Very flexible!

[Former Member]

Hello Vadim,

Here are the logs:

Log file 1: Before update of property ie., number of members in dimension fulfilling the criteria = 5000

Log file 2: Before update of property ie., number of members in dimension fulfilling the criteria = 5050.

Sorry I made certain characters as X to avoid Confidentiality issues. Please share your email if you feel you require the original file.

[former_member186338]

Sorry, but personal support by e-mail is not free.

And I don't see any logs...

[former_member186338]

P.S. If you have issues with confidential information - reproduce this case in the copy of ENVIRONMENSHELL 🙂

[Former Member]

Hello Vadim,

When the dimension had 5000 members with property X, it exported correctly when I saved & selected the filter. But when I ear marked 50 more members as property X & selected the same filter, it is still exporting 5000 members. Meaning the filter is working only for the first time.

[former_member186338]

Post dm logs

[former_member186338]

Sorry, but I am unable to understand what you are doing (without screenshots)

Once again, saved filter is working correctly!

[former_member186338]

"the final screen shows the members that fulfil the criteria." - don't look on it!

If you use saved filter by property then it will be applied each time you run the package.

"So, ideally there should be an increase in the members exported which is not happening. It is exporting the same members on both executions." - incorrect! if you have new members for property condition then new members will be exported. Perform correct tests and you will see.

[Former Member]

Hello Vadim,

I set the filter in Organize Package List & saved the settings.

1. When I open the Organize Package List, the filter selection isn't there anymore

2. When I go to Run Package Link & execute the tasks, I don't see the filter that I set in Organize Package List.

3. After the first execution, when I execute the package link again, I don't see the filter anymore. So I have to select the filter again

Is there a way that the filter appears by default after either Organize Package List or after the first execution?

[Former Member]

Hello Vadim,

I saved the filter during the first execution. In the subsequent execution, I selected the filter. In both the cases, the final screen shows the members that fulfil the criteria. This is what we want to avoid. Between 1st export & 2nd export we did an import. So, ideally there should be an increase in the members exported which is not happening. It is exporting the same members on both executions.

[former_member186338]

Sorry, but I am talking about saving filter, not simply applying it! Please read help!

[former_member186338]

1 Option - create and save filter by property. Disadvantage - filters are user dependent (filter created for some user is not visible for other users). But you can use some dedicated user with UJD_TEST_PACKAGE https://blogs.sap.com/2009/08/28/automate-execution-of-any-data-manager-package/

2 Option - use routine badi and filter members by property inside badi.

3 Option - use Custom logic badi (filter inside badi based on badi parameters passed from script logic) with script logic

[Former Member]

Hello Vadim,

Thanks for the reply.

The issue observed is, once we create (& save) the filter & then click on the subsequent prompts, in the ultimate screen with Finish button, it still shows the members with the selected property. I guess it is hard-coding the members though I selected the filter based on dimension property. So in the eventual log file in UJFS, the log is displaying all the members & not the filter.