BODS is an ETL tool that delivers a single enterprise-class solution for data integration, data quality, and data profiling that permits you to integrate, transform, improve, and provide trusted data that supports important business processes and enables sound decisions.
I’m developing some GUI script macros that will run on a schedule, and download daily reports out of SAP, and save to a folder on a network drive.
One of the issues I’m having, is that in a few reports when the file is exported it auto-opens in excel. I’m trying to get this behavior to stop, because I’d like to run quite a few reports this way...
I’ve tried handling this within VBA - using the workbook.close method, application.quit and even through some more extreme methods (like killing the Excel process completely). I’ve had mixed success here - sometimes it closes, other times it seems immune to the file, and doesn’t know it’s open...
Anything I can do from a user setting perspective to disable auto-open on export? Or am I stuck using VBA?
I wonder if every SAP HANA active data table is providing some hidden meta data (per row) which helps identifying the row. We need a column we could sort the table by that is unique. The column should be numerical or a datetime value.
Do you know if there is something like a unique id that is created automatically? Or a creation timestamp?
Our customer did not think about adding this information to the table beforehand.
Hi everyone! The University of Tennessee is looking for an experienced ERP programmer to join our software development team in Knoxville as an IT Software Developer III. Compensation for this position will be competitive and will include an attractive benefits package including health insurance, retirement, tuition discounts and more. Additionally, Tennessee residents do not pay a state income tax.
Please check out our job posting for a full description and application instructions. Feel free to spread the word about this opportunity!
I have a warehouse that is having issues where they're receiving goods using MFBF and the behavior of SAP after backflushing is differing based on the cost center. I'm not a production person so this is confusing me to no end.
Essentially: if the cost center is "CC1" it will create a TR and a subsequent TO which will move the pallet to the correct staging location. If the cost center is "CC2" it will create the TR but not a TO and the pallet will be left in a 902 bin until someone manually moves it to the staging location.
I have looked into WM movements and they're both using the same movement types, no special movement indicators, etc. I have exhausted my knowledge. Anyone have any ideas?