It's much better to use the standard file upload feature for BW. There is an option to run the file upload planning function in batch but it's not integrated with the web UI. You would specify the file name on the application server has to be accessible from AS ABAP in the planning function parameters. Then schedule the corresponding planning sequence as a process chain.
For a single user case, these are easy hard code the variables in the process chain, tell the user not to change data at the same time but for multiple concurrent planning users this won't be easy especially if they need to plan on the data at the same time. I tried a simple scenario. In DSO I have an object for comments which is set to characteristic as key figure. But when I use File upload tool I have no errors, but any text placed in "comments" column is being converted to 0.
Is there any possibilities to work with characteristic as key figure. Or may be you can give a cue how in which method it can be solved? Is this fixed with Version 4. I am have an agg level on a DSO with comments in a column.
When I load the data it says 1 records read and 0 generated. Although the file has 12 records in it with comments. Never Mind. The comments upload only seems to work only for Comment Characeteristics with Master data, if not it does not do anything. It works well initially, but despite having set the planning fucntion to X -Overwrite - once I have loaded the data one time and activated it ADSO is set like planning cube - all char are key if I try loading the file again, it gives me.
Sorry, Manuela. I don't know why this is happening. Please open an incident so SAP Support can take a look. I have implemented the note you have suggested Version 3. Unfortunately it was not working. Will you please help us the latest note no for flat file upload via planning? Please use version 4 of the solution which you can find attached to SAP Note The display of the format will just be concatenated on the parameter screen which you show.
The file format can be as wide as you like. If you send me an email, I can provide a program to upload the file format from a txt file. Hi Marc, we use your solution with great success in our excisting planning solution on BW 7. Will there be a future solution for your upload Tool? Or is it an standard function for BPC 11 in the future? I think you will need to look into our system to believe it. The solution is in the customer namespace but still build using standard SAP components.
I will take a look at the issue and get back to you via your customer message. We are currently using your enhanced version of File Upload in our project. Unfotrunatelly we noticed one problem. We would expect that also the Data Preview will show the columns with the correct order. But here the order is different and seems random.
I tried to create a new view with the changed layout of the Data Preview. The problem is that this view is then available only for the specific user. Is it possible to create a view that will be available and initial for all users? Is it possible to transport this setting to other systems? No one has complained about the field order yet I get the point and understand that it's not optimal.
The order is given by the internal data structures used by BW-IP. The initial view is configurable. Here is the documentation:. I have not had much time to play with it but there is one limitation: The fields are defined dynamically based on the aggregation level. If you are using the upload for several different levels, then I believe you won't be able to have different initial views. I enhanced the solution to allow you to maintain the initial order of columns separately per planning function.
If you are able to update to a new version, send me an email and I will provide it to you for testing Currently it seems that it runs without packages but I have the need to write the planning buffer in-between. Is it possible to integrate this as a flag maybe in the URL as a parameter?
The complete upload function works on the premise of a single file that is processed in one package. So, unfortunately, this is not feasible to allow for automated packaging. However, you should be able to create your own set of filters and either add them as separate steps to the sequence or use several sequences within a process chain.
If we use the comment function we need use characteristics as a key in the direct-update DSO. It's best to check this case in your system. Please create an incident report and ask support to forward it to my name. Not sure if it is already forwarded to you. You can fill them using a BAdI.
Change the file name in the parameters of your upload planning function to "Prompt". Note: This is usually only for testing.
Your planning users will use the WebDynpro and select the file that way. We extensively and successfully implemented your application for our client, this is really powerful thanks! We are only struggling with one open point: in the data selection header we need to restrict the F4 value help to the list of authorized value.
However, if we open the Webdynpro application, the variable is present in the data selection, but in any case the value help is restricting the values as defined in the BADI. The BADI is not even triggered actually, when putting an external break-point this is not going inside.
Any insight? Do you think we can open OSS message for that? The start of the code should look as follows:. Check that the enhancement spot implementation has the correct filter i. Thanks, actually i am concerned because yes the enhancement implementation is properly configured, and actually this works smoothly when i try to execute the planning sequence in RSPLAN.
But when opening the WebDynpro then there is no restriction anymore and if i put an external break-point inside the enhancement spot it does not go inside. Do you think we can open OSS message to get support on this? Meanwhile i have asked for system opening. It may take a few days, there is no emergency on this topic for the time being.
There's no way to improve performance or reduce memory consumption of the upload for such high data volume. Sorry, but planning functions - not just the file upload - are not designed for this. Several million records probably still lead to memory issues. You will need some trial and error to find the maximum for your system also with other concurrent users.
But please, no complains about performance. If you want a fast load that also requires less memory , use ETL. No one ever asked for it Please send me an email, so I can send you a version for testing. Asking this as it currently generates an error without description - "File Upload: Table conversion error. If it is how it is supposed to work, would you be so kind and propose some workaround so both formats are supported?
With field conversion turned on, this logic will validate data types, which includes the user's date format settings. So the user must supply dates in the format they see everywhere else in SAP. If field conversion is off, there's no such check.
Since this is not coding of the file upload, I won't be able to change or adjust it. The only way around it, is to upload in XML which is unlikely to be accepted. The remaining alternative is to keep field conversion off meaning all values must be in internal format.
However, what you can do is program your own conversion logic in the provided BADI and method transform file from user entries to internal values. You will have to do it for all fields and obviously cover the cases that any user might come up with or you define. A bit of programming but doable. Or the only way to achieve this is to use your Z-development? How do I troubleshoot this? I tested it and the download of date works correctly and as designed. This will lead to the behaviour you see since as you know, the date field has only 8 characters.
The fixed format makes sense only if you leave convert fields off. I was unable to reproduce the second issue. Please check that you have the latest version 4. If you can't figure it out, send me the complete dump from transaction ST Our system is still on BW7. We have installed v4. When infoobject is of type D, instead of assign it D 8 type to the field in the structure, I have assigned it C 10 so that it will capture the full string of converted date ' This has solved the issue for now. For the second issue, I'm still trying to troubleshoot where the problem is.
It seems to throw an error even before it hits the planning function program. That's a misunderstanding. Of course, the latest is always the best. So v4. I will deploy it and try again. Just one suggestion, can you change your document to clarify this misunderstanding? It is not very user-friendly for business users as most of the time it is hard to interpret what key represents.
You can enhance the solution to include the texts: In the download file format, add some fields for the texts like 0TXTLG. Thank you for you suggestions. I'm just back from holiday and testing this. For this to work, I need to define both key and text of the field as output fields in the 'File format' of the planning function. What if I only want to output text field in the file?
Is it achievable using BADI as well? We're on BW 7. Error occur when we press on the save button. Problem was caused by derivation that we're using to record changes in planning data logging - user, time, document id.
I am using Version 4. I enhanced the solution so it should now be possible. Please download the v4. Even though we have to keep in mind that locks are displayed as warnings will not be shown when surpressed. Always a pleasure to make it more useful. Changing a few lines of code here or there is no problem. The lock messages are coming from the IP framework and not the planning function itself. Could you please tell if it is possible to round floating point key figure upload with nine decimal places max to the way BEx does it?
Even though the same Key Figure is used for the flat file upload, the values uploaded via the flat file differ from the ones in the file and in the Input-Ready Query. On the input-ready query zero post attempt, posted to the database is: -8,E -0, Unfortunately, we can't guarantee precise numbers which is due to the nature of how floats are stored i.
And this becomes more difficult in cases you have to add several floats together as is often the case in planning. Any plans to support Hierarchy node variables in Upload flat file. Or still to be planned for an enhancement. System is replacing blank values with and saving that to the ADSO, which is highly impacting data quality.
We are planning to open an incident. We are using this functionality with great results. However, we have lately came across an unexpected scenario, and wanted to ask to what extent that would be supported? We are trying to setup multiple filters in the as part of the planning function e. We have been using the file upload planning function for many years v3 and it is working out well for us.
We are in the middle of an upgrade from 7. When testing the planning function from the HEC server we notice that the updates are occuring to the cube on the on prem server. I know you must be busy, but if you could point me in the right direction without taking too much time, it would be appreciated. Skip to Content Welcome Learners! Technical Articles Marc Bernard. August 13, 3 minute read. Enhancements The following list shows the changes and enhancements in version 3 compared to the previously published version 2.
Alert Moderator. By changing the existing entry osgi. A set of German texts is also shipped with the product however. By default, Eclipse takes the locale settings from the operating system.
If you are using a German locale on the operation system, the BW Modeling Tools will therefore automatically switch to German texts. This default handling can be changed by setting a parameter in the Eclipse INI file. The steps for updating the BW Modeling Tools are straightforward.
The configuration details for this step can be found in the installation guide. Please note however that performing an update will not remove older versions from the file system. If you perform multiple updates, this results in multiple versions of the corresponding feature on the file system and an increase in the disk space required. At runtime however, only the latest version is used. Before the BW Modeling Tools are installed, now create a copy of the current installation folder and keep this one as a backup.
As soon as a new version of the BW Modeling Tools is available, just install this new version on top of the backup version. This way, the installation directory will not grow over the time. With this in mind, please note that the update will not install any new features. In other words, can you use the BW modeling tools to connect to the BW back-end application server only and not give the developers access to the HANA Database directly so no access in the Administrator perspective, Modeling perspective and so on..
Skip to Content Welcome Learners! Steffen Zimmermann. September 20, 4 minute read. To make sure you get the latest version, please pay special attention to how the version numbers are handled, where Release 1. Important: In general we recommend using the latest available version. All required dependencies will be resolved automatically. Step 2. Remove any existing "track" or "browser" lines from your wig file so that it contains only data. Step 3. Download the wigToBigWig program from the binary utilities directory.
Step 4. Use the fetchChromSizes script from the same directory to create the chrom. Step 5. Use the wigToBigWig utility to create the bigWig file from your wig file:.
Step 6. Move the newly created bigWig file myBigWig. Step 7. If the file name ends with a. By default, the file name will be used to name the track. To configure the track label or other visualization options, you must create a track line , as shown in Step 8. Step 8. Construct a custom track using a single track line. The most basic version of the track line will look something like this:. Paste the custom track line into the text box on the custom track management page.
For more information on how bigWig settings are used in native Genome Browser tracks, see the Configuring graph-based tracks page. The file contains data that spans chromosome 21 on the hg19 assembly. Click the "submit" button. On the next page that displays, click the "chr21" link in the custom track listing to view the bigWig track at position chr,,,, in the Genome Browser.
Alternatively, you can customize the track display by including track and browser lines that define certain parameters:.
0コメント