Default setting of ini file entry?

What, in v2011, is the default setting of the AllowMultipleInstances value of the ini file? I know that it isn't a normally included field in the ini file generated when an exe is built, I'm just wondering what the value is by default? I've added it to the ini file, set to False, on a machine I'm trying to troubleshoot which has a program launch so slow that the operators frequently go back and try and launch it again, which results in two instances, only one of which is correctly running.
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion
Solved!
Go to Solution.

pincpanter wrote:
...it appears that the default value is false...
I can concur that this appears to be the case for a simple executable.
Maybe when the executable loads a large number of VIs before beginning execution it doesn't register itself with whatever service needs to know until it is actually executing, and if the executable is double-clicked again before this point it may be able to launch a second instance.
This is harder to test without creating a substantial executable.
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Similar Messages

Default setting for deleting files, default setting for deleting files

How can I change default value for deleting files from 'Keep file' to 'In waste basket' (sorry this is a translation from the German 'In den Papierkorb') meaning delete file from harddisk definitely.

Thank you for your quick answer. Yes that's the place I am doing the job. And yes I do get a choice to choose between 'Delete from hard disk' or 'Delete from iTunes only'.
But the 'Delete from iTunes only' is the default setting. I would like to change the default setting to 'Delete permanently (from hard disk too)'. This would enable me to work much quicker by using keys only (Del + Enter) without touching the mouse to change from 'Delete from iTunes only' to 'Delete permanently'.

DC noise values set from ini file

Hello,
I am trying to build a waveform generator with ( sine wave, triangle, saw tooth, square, DC, random noise). I managed to get the waveform working using the NI waveform generator built in VI function. but I want to add the DC case which I manage to do. but I want the values (amplitude and frequency ) to be in an ini file. My idea is to manual set the values in the file, once I run the vi and select the DC noise case, it should read the file get the values and output the data and once I stop it, it saves the dc values before exiting.
I am kind of stuck trying to figure how to do this. I hope I was clear enough. I don't have code to show since I havent started coding on that part yet. Please help.
Solved!
Go to Solution.

Clearly enough explained.
Have a look at the configuration file VIs, found in File I/O > Config File VIs. There are also plenty of examples n the community, as well as in the Example Finder, which show how to use these. A good place to start is the Write Configuration Settings File example in the Example Finder, as well as Read Configuration Settings File.
Your .ini file will look something like this, once created:
[DC Noise Settings]
Amplitude = 1.234567
Frequency = 8.901234
This is equivalent to:
[Section Name]
Key 1 = Value
Key 2 = Value
When asked to read a specific key from a certain section, the read VI scans through the file for the named section, then looks for they key name that you've provided it. Bear in mind you'll need to know what the data type is when you read back.
You can use the write VI to modify specific keys in specific sections once you close the file.
This is one of a multitude of methods you could use to do this, but is probably the simplest.
CLD

DignosticFile= setting in .ini file not working?

When editing Lookout.ini file in Lookout 6.1 and adding setting as follows:
[COM9]
DiagnosticFile=C:\com9.txt
or
[COM3]
DiagnosticFile=C:\Program Files\National Instruments\Lookout 6.1\com3.txt
No logs are created for the named COM port.
I know I used this feature sucessfully back in Lookout 4.5 and earlier, maybe even in Lookout 5.1.
Please confirm and help!

You can configure this in Lookout. Go to Option->Serial ports, select COM9, check "Enable", input the diagnostic file path, "Accept".
Close Lookout, then open lookout.ini. You will see the following codes.
DiagnosticFileEnable=1
DiagnosticFile=c:\test.txt
DiagnosticAllHex=1
DiagnosticTimeStamp=1
DiagnosticTimeStampDateFormat=73
So, you need to add DiagnosticFileEnable=1 to make it active.
I'm not sure how it worked in Lookout 4.
Ryan Shi
National Instruments

How to refresh/apply column value default setting on current files or folders

Hi All
I have set-up default column data per folder in my library (via
Library Settings > Column default settings) and it works great for new documents or folders that are added to the library.
But what do I do if I have an existing Library with folders and files and need to apply default column data to each? Is there a way of "refreshing" the default columns so that the data is populated through a specific folder and/or its sub-folders?
(I really hope this is an easy fix or just a setting that I over-looked somewhere!)
Thank you!

I had to do this as well recently, and remembered your post.
Here is the function I wrote , this worked for text, choice, and metadata columns
It is pretty slow and could be optimized and broken up into more functions, but I had to do several things:
1. I mass-updated the content types in a library
2. On Library settings : set default values and also different defaults per folder
3. For each file I then needed to:
3.a. either copy the value from a column in the old content type to the new, or
3.b. set the column to the default
so this function does step 3, like I said it works for certain types of columns and can be sped up (I used it to update 700 files in a couple minutes), and it makes some assumptions about the environment but this at least is a starting point.
As Alex said you may want to change SystemUpdate($true) to just Update(), depending on your requirements.
<#
.SYNOPSIS
Resets columns in a document library to defaults for blank columns. Use this
after changing the content types or adding columns to a doc lib with existing files
.DESCRIPTION
Resets columns in a doc lib to their defaults. Will only set them if the columns are blank (unless overridden)
Will also copy some values from one column to another while you are there.
Can restrict the update to a subset of columns, or have it look for all columns with defaults.
Will use the list defaults as well as folder defaults.
All names of columns passed in should use InternalName.
This has ONLY been tested on Text, Choice, Metadata, and mult-Choice and Mult-Metadata columns
Pass in a list and it will recursively travel down the list to update all items with the defaults for the items in that folder.
If you call it on a folder, it will travel up the tree of folders to find the proper defaults
Author:
Chris Buchholz
[email protected]
@plutosdad
.PARAMETER list
The document library to update. Using this parameter it will update all files in the doc lib
.PARAMETER folder
The folder containing files to update. Function will update all files in this folder and subfolders.
.PARAMETER ParentFolderDefaults
Hashtable of internal field names as KEY, and value VALUE, summing up all the parent folders or list defaults.
If not supplied, then the function will travel up the tree of folders to the parent doclib to determine
the correct defaults to apply.
If the field is managed metadata, then the value is a string
Currently only tested for string and metadata values, not lookup or date
.PARAMETER termstore
The termstore to use if you are going to update managed metadata columns, this assumes we are only using the one termstore for all columns to update
If you are using the site collection specific termstore for some columns you want to update, and
the central termstore for others, then you should call this method twice, once with each termstore,
and specify the respective columns in fieldsToUpdate
.PARAMETER fieldsToCopy
Hashtable of internal field names, where KEY is the "to" field, and VALUE is the "from" field
Use this to copy values from one field to another for the item.
These override the defaults, and also cause the "from" (Value) fields to NOT be overwritten with defaults even if
they are in the fieldsToUpdate array.
Example: @{"MyNewColumn" = "My_x0020_Old_x0020_Column"}
.PARAMETER fieldsToUpdate
If supplied then the method will update only the fields in this array to their default values, if null then it will update
all fields that have defaults.
If you pass in an empty array, then this method will only copy fields in the fieldtocopy and not
apply any defaults
Example: @() - to only copy and not set any fields to default
Example2: @('UpdateField1','UpdateField2') will
.EXAMPLE
Set-SPListItemValuesToDefaults -list $list -fieldsToCopy @{"MyNewColumn" = "My_x0020_Old_x0020_Column"} -fieldsToUpdate @() -overwrite -termStore $termStore
This will not set any defaults, but instead only set MyNewColumn to non null values of My_x0020_Old_x0020_Column
It will overwrite any values of MyNewColumn
.EXAMPLE
Set-SPListItemValuesToDefaults -list $list -overwrite
This will set all columns to their default values even if they are filled in already
.EXAMPLE
Set-SPListItemValuesToDefaults -folder $list.RootFolder.SubFolder[3].SubFolder[5]
This will set all columns to their defaults in the given subfolder of a library
.EXAMPLE
Set-SPListItemValuesToDefaults -list $list -fieldsToUpdate @('ColumnOneInternalName','ColumnTwoInternalName')
This will set columns ColumnOneInternalName and ColumnTwoInternalName to their defaults for all items where they are currently null
.EXAMPLE
Set-SPListItemValuesToDefaults -list $list -fieldsToCopy @{"MyNewColumn" = "My_x0020_Old_x0020_Column"} -fieldsToUpdate @("MyNewColumn") -termStore $termStore
This will set all MyNewColumn values to their default, and then also copy the values of My_x0020_Old_x0020_Column to MyNewColumn where the old column is not null,
but both of these will only happen for items where MyNewColumn is null
.EXAMPLE
Set-SPListItemValuesToDefaults -list $list -fieldsToCopy @{"MyNewColumn" = "My_x0020_Old_x0020_Column"} -termStore $termStore
This will set ALL columns with defaults to the default value (if the item's value is null),
except for My_x0020_Old_x0020_Column which will not be modified even if it has a default value, and will also set MyNewColumn to the
value of My_x0020_Old_x0020_Column if the old value is not null
#>
function Set-SPListItemValuesToDefaults {
[CmdletBinding(SupportsShouldProcess=$true)]
param(
[Parameter(Mandatory=$true,ValueFromPipeline=$true,ParameterSetName="List")][Microsoft.SharePoint.SPList]$list,
[Parameter(Mandatory=$true,ValueFromPipeline=$true,ParameterSetName="Folder")][Microsoft.SharePoint.SPFolder]$folder,
[Parameter(Mandatory=$false,ParameterSetName="Folder")][HashTable]$ParentFolderDefaults,
[Parameter(Mandatory=$false)][HashTable]$fieldsToCopy,
[Parameter(Mandatory=$false)][Array]$fieldsToUpdate,
[Parameter(Mandatory=$false)][Microsoft.SharePoint.Taxonomy.TermStore]$termStore,
[Switch]$overwrite,
[Switch]$overwriteFromFields
begin {
#one or both can be null, but if both empty, then nothing to do
if ($null -ne $fieldsToUpdate -and $fieldsToUpdate.Count -eq 0 -and
( $null -eq $fieldsToCopy -or $fieldsToCopy.Count -eq 0)) {
Write-Warning "No fields to update OR copy"
return
if ($PSCmdlet.ParameterSetName -eq "Folder") {
$list = $folder.DocumentLibrary
if ($null -eq $termStore ) {
$taxonomySession = Get-SPTaxonomySession -site $list.ParentWeb.Site
$termStores = $taxonomySession.TermStores
$termStore = $termStores[0]
#if we did not pass in the parent folder defaults then we must go backward up tree
if ($PSCmdlet.ParameterSetName -eq "Folder" -and $null -eq $ParentFolderDefaults ) {
$ParentFolderDefaults = @{}
if ($null -eq $fieldsToUpdate -or $fieldsToUpdate.Count -gt 0) {
write-Debug "ParentFolderDefaults is null"
$tempfolder=$folder.ParentFolder
while ($tempfolder.ParentListId -ne [Guid]::Empty) {
Write-Debug "at folder $($tempfolder.Url)"
$pairs = $columnDefaults.GetDefaultMetadata($tempfolder)
foreach ($pair in $pairs) {
if (!$ParentFolderDefaults.ContainsKey($pair.First)) {
Write-Debug "Folder $($tempfolder.Name) default: $($pair.First) = $($pair.Second)"
$ParentFolderDefaults.Add($pair.First,$pair.Second)
$tempfolder = $tempfolder.ParentFolder
#listdefaults
Write-Debug "at list"
foreach ($field in $folder.DocumentLibrary.Fields) {
if ($field.InternalName -eq "_ModerationStatus") { continue }
#$field = $list.Fields[$name]
if (![String]::IsNullOrEmpty($field.DefaultValue)) {
#Write-Verbose "List default found key $($field.InternalName)"
if (!$ParentFolderDefaults.ContainsKey($field.InternalName)) {
Write-Debug "List Default $($field.InternalName) = $($field.DefaultValue)"
$ParentFolderDefaults.Add($field.InternalName,$field.DefaultValue)
process {
Write-Debug "Calling with $($PSCmdlet.ParameterSetName)"
Write-Debug "Parent folder hash has $($ParentFolderDefaults.Count) items"
if ($PSCmdlet.ParameterSetName -eq "List" ) {
$folder = $list.RootFolder
$ParentFolderDefaults=@{}
if ($null -eq $fieldsToUpdate -or $fieldsToUpdate.Count -gt 0) {
foreach ($field in $list.Fields) {
if ($field.InternalName -eq "_ModerationStatus") { continue }
if (![String]::IsNullOrEmpty($field.DefaultValue)) {
Write-Debug "List Default $($field.InternalName) = $($field.DefaultValue)"
$ParentFolderDefaults.Add($field.InternalName,$field.DefaultValue)
Write-Verbose "At folder $($folder.Url)"
$FolderDefaults=@{}
$FolderDefaults += $ParentFolderDefaults
if ($null -eq $fieldsToUpdate -or $fieldsToUpdate.Count -gt 0) {
$pairs = $columnDefaults.GetDefaultMetadata($folder)
foreach ($pair in $pairs) {
if ($FolderDefaults.ContainsKey($pair.First)) {
$FolderDefaults.Remove($pair.First)
Write-Debug "Folder $($folder.Name) default: $($pair.First) = $($pair.Second)"
$FolderDefaults.Add($pair.First,$pair.Second)
#set values
foreach ($file in $folder.Files) {
if ($file.CheckOutType -ne [Microsoft.SharePoint.SPFile+SPCheckOutType]::None) {
Write-Warning "File $($file.Url).CheckOutType = $($file.CheckOutType)) ... skipping"
continue
$item = $file.Item
$ItemDefaults=@{}
$ItemDefaults+= $FolderDefaults
#if we only want certain fields then remove the others
#Move this to every time we add values to the defaults
if ($null -ne $fieldsToUpdate ) {
$ItemDefaults2=@{}
foreach ($fieldInternalName in $fieldsToUpdate) {
try {
$ItemDefaults2.Add($fieldInternalName,$ItemDefaults[$fieldInternalName])
} catch { } #who cares if not in list
$ItemDefaults = $ItemDefaults2
#do not overwrite already filled in values unless specified
if (!$overwrite) {
$keys = $itemDefaults.Keys
for ($i=$keys.Count - 1; $i -ge 0; $i-- ) {
$key=$keys[$i]
try {
$val =$item[$item.Fields.GetFieldByInternalName($key)]
if ($val -ne $null) {
$ItemDefaults.Remove($key)
} catch {} #if fieldname does not exist then ignore, we should check for this earlier
#do not overwrite FROM fields in copy list unless specified
if (!$overwriteFromFields) {
if ($null -ne $fieldToCopy -and $fieldsToCopy.Count -gt 0) {
foreach ($value in $fieldsToCopy.Values) {
try {
$ItemDefaults.Remove($value)
} catch {} #who cares if not in list
#do not overwrite TO fields in copy list if we're going to copy instead
if (!$overwriteFromFields) {
if ($null -ne $fieldToCopy -and $fieldsToCopy.Count -gt 0) {
foreach ($key in $fieldsToCopy.Keys) {
$fromfield = $item.Fields.GetFieldByInternalName($fieldsToCopy[$key])
try {
if ($null -ne $item[$fromfield]) {
$ItemDefaults.Remove($key)
} catch {} #who cares if not in list
Write-Verbose $item.Url
$namestr = [String]::Empty
if ($ItemDefaults.Count -eq 0) {
write-Verbose "No defaults, copy only"
} else {
$str = $ItemDefaults | Out-String
$namestr += $str
Write-Verbose $str
if ($null -ne $fieldsToCopy -and $fieldsToCopy.Count -gt 0) {
$str = $fieldsToCopy | Out-String
$namestr +=$str
if ($PSCmdlet.ShouldProcess($item.Url,"Set Values: $namestr"))
#defaults
if ($null -ne $ItemDefaults -and $ItemDefaults.Count -gt 0) {
foreach ($key in $ItemDefaults.Keys) {
$tofield = $item.Fields.GetFieldByInternalName($key)
if ($tofield.TypeAsString -like "TaxonomyFieldType*") {
$taxfield =[Microsoft.SharePoint.Taxonomy.TaxonomyField]$tofield
$taxfieldValue = New-Object Microsoft.SharePoint.Taxonomy.TaxonomyFieldValue($tofield)
$lookupval=$ItemDefaults[$key]
$termval=$lookupval.Substring( $lookupval.IndexOf('#')+1)
$taxfieldValue.PopulateFromLabelGuidPair($termval)
if ($tofield.TypeAsString -eq "TaxonomyFieldType") {
$taxfield.SetFieldValue($item,$taxfieldValue)
} else {
#multi
$taxfieldValues = New-Object Microsoft.SharePoint.Taxonomy.TaxonomyFieldValueCollection $tofield
$taxfieldValues.Add($taxfieldValue)
$taxfield.SetFieldValue($item,$taxfieldValues)
} else {
$item[$field]=$ItemDefaults[$key]
#copyfields
if ($null -ne $fieldsToCopy -and $fieldsToCopy.Count -gt 0) {
#$fieldsToCopy | Out-String | Write-Verbose
foreach ($key in $fieldsToCopy.Keys) {
$tofield = $item.Fields.GetFieldByInternalName($key)
$fromfield = $item.Fields.GetFieldByInternalName($fieldsToCopy[$key])
if ($null -eq $item[$fromfield] -or ( !$overwrite -and $null -ne $item[$tofield] )) {
continue
if ($tofield.TypeAsString -eq "TaxonomyFieldType" -and
$fromfield.TypeAsString -notlike "TaxonomyFieldType*" ) {
#non taxonomy to taxonomy
$taxfield =[Microsoft.SharePoint.Taxonomy.TaxonomyField]$tofield
$termSet = $termStore.GetTermSet($taxfield.TermSetId)
[String]$fromval = $item[$fromfield]
$vals = $fromval -split ';#' | where {![String]::IsNullOrEmpty($_)}
if ($null -ne $vals -and $vals.Count -ge 0 ) {
$val = $vals[0]
if ($vals.Count -gt 1) {
write-Warning "$($item.Url) Found more than one value in $($fromfield.InternalName)"
continue
$terms =$termSet.GetTerms($val,$true)
if ($null -ne $terms -and $terms.Count -gt 0) {
$term = $terms[0]
$taxfield.SetFieldValue($item,$term)
Write-Verbose "$($tofield.InternalName) = $($term.Name)"
} else {
Write-Warning "Could not determine term for $($fromfield.InternalName) for $($item.Url)"
continue
} elseif ($tofield.TypeAsString -eq "TaxonomyFieldTypeMulti" -and
$fromfield.TypeAsString -notlike "TaxonomyFieldType*" ) {
Write-Debug "we are here: $($item.Name): $($fromfield.TypeAsString) to $($tofield.TypeAsString )"
#non taxonomy to taxonomy
$taxfield =[Microsoft.SharePoint.Taxonomy.TaxonomyField]$tofield
$termSet = $termStore.GetTermSet($taxfield.TermSetId)
$taxfieldValues = New-Object Microsoft.SharePoint.Taxonomy.TaxonomyFieldValueCollection $tofield
[String]$fromval = $item[$fromfield]
$vals = $fromval -split ';#' | where {![String]::IsNullOrEmpty($_)}
foreach ($val in $vals){
$terms =$termSet.GetTerms($val,$true)
if ($null -ne $terms -and $terms.Count -gt 0) {
$term=$terms[0]
$taxfieldValue = New-Object Microsoft.SharePoint.Taxonomy.TaxonomyFieldValue($tofield)
$taxfieldValue.TermGuid = $term.Id.ToString()
$taxfieldValue.Label = $term.Name
$taxfieldValues.Add($taxfieldValue)
} else {
Write-Warning "Could not determine term for $($fromfield.InternalName) for $($item.Url)"
continue
#,[Microsoft.SharePoint.Taxonomy.StringMatchOption]::ExactMatch,
$taxfield.SetFieldValue($item,$taxfieldValues)
$valsAsString = $taxfieldValues | Out-String
Write-Debug "$($tofield.InternalName) = $valsAsString"
} elseif ($tofield.TypeAsString -eq "TaxonomyFieldTypeMulti" -and
$fromfield.TypeAsString -eq "TaxonomyFieldType" ) {
#single taxonomy to multi
$taxfieldValues = New-Object Microsoft.SharePoint.Taxonomy.TaxonomyFieldValueCollection $tofield
$taxfield =[Microsoft.SharePoint.Taxonomy.TaxonomyField]$tofield
$taxfieldValues.Add($item[$fromfield])
$taxfield.SetFieldValue($item,$taxFieldValues)
Write-Verbose "$($tofield.InternalName) = $valsAsString"
} elseif ($tofield.TypeAsString -eq "TaxonomyFieldType" -and
$fromfield.TypeAsString -eq "TaxonomyFieldTypeMulti" ) {
#multi taxonomy to single taxonomy
Write-Warning "multi to non multi - what to do here"
continue
} elseif ($tofield.TypeAsString -eq "Lookup" -and
$fromfield.TypeAsString -ne "Lookup" ) {
#non lookup to lookup
Write-Warning "non lookup to lookup - still todo"
continue
} else {
#straight copy
$item[$tofield] = $item[$fromfield]
$item.SystemUpdate($false)
$folders = $folder.SubFolders | where name -ne "Forms"
$folders | Set-SPListItemValuesToDefaults -ParentFolderDefaults $FolderDefaults -fieldsToCopy $fieldsToCopy -fieldsToUpdate $fieldsToUpdate -overwrite:$overwrite -overwriteFromFields:$overwriteFromFields -termStore $termStore

SAP R/3 4.7 custom Fax Cover Page default setting in Workplace Fax Entries

How can we implement a custom Z form SAP fax cover page as the default fax cover page in SAP workplace, it makes you enter the Z form name in fax cover page entries when we tested it each time you do a fax, Iu2019m sure the users arenu2019t going to want to do that. Research Iu2019ve done on SAP seems to say you change the Default SAP fax cover page form in transaction SO41 the OFFICE-TELEFAX form which had the From: company name and address hardcoded with SAPu2019s German company name and address which we don't want to use.

We decided to use Z fax cover created from OFFICE-TELEFAX and when you enter the Z fax cover name in fax detail entries it keeps the entry in field in SBWP we've found so you don't have to retype it in and we hardly do any user controlled fax of reports right from SAP, mostly email of reports they do thru SBWP SAP Office. And auto fax, auto email of documents with NACE records thru SCOT, SOST transaction to an Esker Deliveryware fax server.

Planning file Entries

Hi Friends
When is a Planning File Entry is Created?? During the creation of Material master?? We have uploaded the material Master and found that there are few materials for which Planning File Entries are not createdu2026.. How can we overcome this?? Do we have to create the planning file entries using MD20??
Is there any views which are required for Planning file entry Creation?? Like MRP 1 u2013 4 Views should be there for Planning File entry Creations??
Please get back to me on the above.
Jade

Dear,
All materials assigned with MRP are automatically entered in planning file entry.
Depends on changes in material planning or in proposal , system will create planning file entry.
When MRP run system will consider only which materials having entry in above contents of planning file entry.
If the materials is created before activating planning file for plant, you must generate planning file entry for all material by tcode MDAB.
T-Code :
MD20 Create planning file entry
MD21 Display planning file entry
MDAB Set up planning file entry in background
MDRE Check planning file entry
For the first time (just before Go-live), it is advisable to create the Planning file entries mnually and execute the MRP.. This is to reduce the inconsistencies..
But, system will automatically Creates the Planning File entry, if the Material is relevnt for planning.
First time MRP Run with NEUPL will not consider the planning file entries..
So, after that every thing will be stream lined.
In rare cases systm may miss the entering the Material details in the Planning file
Regards,
R.Brahmankar

Change Planning file entry

Hi,
How can I change Planning file entry or selection? For a material, earlier I have selected the following in MD20
1. NETCH
2. NETPL
4. Reset order proposal
5. BOM explosion.
Now I want to deselect BOM explosion , how can I do that?
Sincerely,
Ketan

Hi,
Run MRP in MD02 with Planning mode as 3 - Delete.
This will delete the planning file entry of the material
then create the planning file entry manually by
MD20 - Create planning file entry
MD21 - Display planning file entry
MDAB - Set up planning file entry in background
MDRE -Check planning file entry
Regards,
R.Brahmankar

MRP Run - Planning file entry Issue

Dear All,
We are facing one problem in MRP Run. We run MRP in the background for a plant (MDBT) System is not creating planned order for few component. I have checked all relevant setting. I found that planning file entry is missing. I would like to know that how system can miss the material? How system creates & delete planning file entry ? I have some data related to this.
Last MRP run date is 22-04-09
PIR changed date on 30-04-09
MDRE Run on the 30-.4-09 at night.
MRP Run on 02-05-09 at night.
Problem reported that no planned order for the material on 07-05-09.
We have huge number of material so its difficult to check all material individually whether MRP run happend or not ?
Please let me know the possible reason for this.
Thanks & Regards
Kundan Kumar

Dear,
If you carte materaial or uplod materail before activation plant for MRP this may be the cause for this.
Planning File creates all the materials relevant for the planning run.
The planning run and the scope of the planning run (which materials are planned in which planning run) are controlled by the planning file.
For planning file entry use the following transactions,
MD20 : Create planning file entry
MD21 : Display planning file entry
MDAB : Set up planning file entry in background
MDRE : Check planning file entry Please run this in it will solve your problem
All materials assigned with MRP are automatically entered in planning file entry.
Depends on changes in material planning or in proposal , system will create planning file entry.
When MRP run system will consider only which materials having entry in above contents of planning file entry. After MRP run system delete the planning file entry. And again material gone the changes like GI GR on any other demand then system generate planning file enty again.
Hope it will help you to understand basic concept.
Regards,
R.Brahmankar

Planning File Entry Job MDAB

Hi ,
We are in process of implementing MRP for a plant.
Query
Do we need to schedule MDAB for the planning file entry before MRP job( NETCH) or run MDAB just once.
If we do not schedule this job and run just once what are the problems we will face.
Thanks,
Anup

Hello,
MDAB is a batch program to set up planning file entries. So after you run this program, system will make planning file entries for all those materials which might have missed the entry.
This normally does not happen, but as a good practise it is better to run MDAB & MDRE, to ensure that the planning file entries are consistent.
Effects as such: As you might know already, if a planning file entry does not exist for a material it will not be considered in MRP run.
When to Run the Job:
There is no need to run this transaction regularly, unless otherwise you find a lot of inconsistency and some material which are supposed to get planned in MRP run are not getting planned.
SAP automatically creates a planning file entry for the material whenever an MRP related change is happening for the material. Some times due to inconsistencies in the system, this entry is not made, so that materials would not get planned in MRP run, only when you face problem like this you need to run MDAB
Hope the above clarifies.
Regards

Planning file entry MDAB

Hi All,
I have a pecualir situation.
We have some materials in SAP where in the planning file entry is not created for them automatically. These are semifinished goods and MRP type is PD. This are new materials and are created post go live. I have executed MDAB - Set up planning file entries at plant level and the result said " Number of set planning file entries = 0" and the planning file entries are not created.
My query is why has not the planning file entries created (MRP requirement planning is actiavted at plant level - tcode OMDU).
Regards,
Narendra Bora

A number of discussions in the past on this topic.
Check these:
Planning File entry not created automatically
Planning file entries
Planning File Entry not created

Set up planning file

dear gurus,
            in config mrp,Activate MRP and setup planning file entries.i ticked the activate mrp.what is the use of creating variant for set up planning file entries?whether this is mandaotry in mrp config?what is the use of this.
        please through some light
                                                     -guna

hi,
      my project is a roll out implementation.already plants are there.i am copying the plant and creating new plant?whether it set upl planning file entries is mandotry for me?
guna

MS ssis service: registry setting specifying configuration file does not exist. attempting to load default configuration file. SQLIService100 - event id 274

window 2008 R2 server ---- after installing SQL 2008 R2 then applying sp2 / sp3 I noted a warning -
Note this server had SQL 2008 R2 uninstalled previously.
MS ssis service: registry setting specifying configuration file does not exist. attempting to load default configuration file.
SQLIService100 - source
event id- 274
user - N/A
Task category - service control.
Do we need to fix something and how do we fix this warning event?
dsk

You could search online for this warning. I was able to find http://superuser.com/questions/346264/event-log-warning-registry-setting-specifying-configuration-file-does-not-exist
where the fix is "in your registry, go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile
or
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ServiceConfigFile
if value is empty then add in:
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.ini.xml"
Arthur
MyBlog
Twitter

.INI files vs .TXT files for changing default values in a .EXE?

Hi,
I have a two-part question related to updating the default values of controls in an executable:
I am creating a LabVIEW executable for installation on two different production-floor computers.   I need to be able to change the default values of the front panel controls (as I would do with the “make this value default” command during development). From reading prior posts, I understand that I could use the “Write Configuration Settings File.vi” and “Read Configuration Settings File.vi” to generate a .INI file that would be read by the .EXE and would establish the desired values of the controls. However when I took a look at the block diagrams for those configuration .VIs, they don’t appear (to me) to be any easier to use than just reading values from a spreadsheet file. IE: Instead of using these configuration files and a .INI file, could I not instead just read values from a .TXT file that contains the desired values?   I’ve never used a .INI file before, or had to worry about “keys” and “sections,” so from my (perhaps naïve) perspective, the .INI method seems less easy to use. Is there any advantage to the .INI format?
Regardless of whether I use the .INI file or a .TXT file, I have this additional problem: One of the things that changes when I install my .EXE file on a new computer is the COM port numbers used by two serial devices.   (On my development computer, the two serial devices use COM5 and COM6, whereas on the two production-flood computers, the COM ports will almost certainly be different).   I suppose I could use the Device Manager on the production-floor computers to change the COM ports to be the same as those on my development computer, but I’d prefer to be able to (again) change the default value of the COM ports in my .EXE.   However, I’m not sure how to do that.   The configuration VIs, have options for reading / writing Booleans, strings, paths, and numeric, but not, (so far as I can tell) for a VISA class.
Any thoughts / suggestions are welcome. Thanks.
Solved!
Go to Solution.

Dan_the_Clam wrote:
Thanks for your reply, Yamaeda,
Great that I can use a string to open a VISA session - I had no idea. I'll try that.
And - ah - you are right about the .INI files. I just did an experiment in which I re-ordered the sections and randomly changed which letters were capitalized in the key values, and the "read configuration settings.VI" still read the file correctly. Thanks for that.
Unfortunately, in my existing code, the controls on the block-diagram aren't all co-located together; they are scattered throughout the block diagram - some of them in case structures and loops.   I suppose that means I'll have to move them all to the left side of the block diagram, route them to these "Write Key.VIs" and then wire them up into the cases and loops with fairly long wires.   It's just a hassle, and is going to make my block diagram more complicated.  Well, I suppose that's how one learns...
Thanks again.
dan
Assuming you have a state machine and an Init state it's a fair use of Local Variables to update controls from the ini-file. The same goes for saving the values.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Cretaion of UTL.File in Oracle 10G and directory entry in Ora.ini file

Hi,
Kindly advise me if:
(!) we can create a directory and log file in this directory on some other server instead of creating it in the file system of the server where the Oracle 10G database is residing?
Created directory in Oracle using create or replace directory command.
My package will be creating a log file using UTL.File in the above directory.
I want to create this directory on some other server to save my log file/s. Is this possible?
(2) Also, let me know in Oracle 10G, do we need to add the directory entry (mention above in #1) in the Ora.ini file on the Oracle 10G server?

Hi,
1) utl_dir are different from directory object
2) you cannot create directory on remote server and there is no need to write directory entry on oracle init file (not ini..)
Acr

Default setting of ini file entry?

Similar Messages

Maybe you are looking for