Vendor tolerance level for price.
hi,
Is there any vendor specific seting or field,
So that system will gives message at the time of invoice posting.
Ie. if price increased above the vendor specific tolerance, system will give the message at the time of
invoice posting..
regards,
MPL.
Hi Mahendra,
There is a Setting Present in the SPRO.
GO to the Path
SPRO..> MM> LIV> incomming invoice--> Set up tolerance linits for Vendor
The settings can be made at Company code level .know define a tolerance group for the same.
so after defining your Tolerance group.
KNow it is the time to activate it on the vendor master.
SO to the Vendor master record to which it ahs to be done and update the tolerance Group in the Payment transactions accounting ..
the updation for a bulk of vendors can be done by using the below
it can also be done in MASS using the t code MASS or XK99
object --> LFA1 and the TAble is LFB1.
Hope so it helps
Regards
Anjanna
Similar Messages
-
Tolerance Limit for Price Variance (Purchase Order)
Hello,
Business Case :
Final users require a specific tolerance limit rate for Price variance in Freight services POs.
We have a current rate set up at Company level
--> standard customizing (MM / Purchasing / Purchase order / Set tolerance limit for Price variance)
Do you know any way to set up diffferent tolerance limit depending on the purchasing flow ? Vendor level for example ?
thanks for your time.
regards,Thanks for your reply.
What do you mean by "syestem look for noramal quantity variance from info record" ?
P.I.R only conatins under and over delivery tolerance, but nothing related to price variance between GR and Invoice.
I'm looking for a customizing in order to have a Tolerance limit for Price variance at another level than Company.
At vendor level for example ?
Do you confirm there is no standard customizing ?
Any user exit available ?
thanks
regards -
Set Tolerance Limits for Price Variance for PR missing from SPRO
I'm looking into setting up tolerance limits for price variance at the PR level. But when i navigate here:
SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance
I'm not seeing that available in SPRO. It's available for PO's but not PR's. We want to be able to set tolerances on the PR to be applied to the PO for non stock items (material master). Please adviseHi,
There is no standard configuration option to set the tolerance limit at PR level. You may set the tolerance limit for PO and control the price change. If you want the same functionality at PR level, then you have to go for development. Please check whether the BAdI: ME_PROCESS_REQ_CUST can fulfill your requirement. You may set the tolerance limit in OLME - PO - Set Tolerance Limits for Price Variance itself and write the logic in the BAdI to check the price variance in PR based on the same configuration (table T169G and similar).
You may check the similar thread: PR VS PO Price Tolerance
Regards,
AKPT -
Tolerance limits for Price Variation
Dear All,
I have set the Following in Customizing.
In the following node : IMG-------> Materials Management ----------> Purchasing -----------> Purchase Order ---------> Set tolerance limits for price Variance.
In this, For Company code & Tolerance Key "PE" combination, it has been set " Check Limit 20%" in the Percentage field ( Upper limit ).
Now, I have a material having a Moving Average price of 100 INR in the material master Accounting view. When I create a PO for 130 INR, there is no warning/error message that is popping up? Isn't the system supposed to throw a message here, since 130 inr exceeds 120 INR, or am I missing something out here ?
Note : 120 INR = 100 + (20%)(100) = 120 INR.
Regards
SathyaHi Sathyanarayana Rao V N
You can benefit from M8 messages for incoming invoices with tolerances to solve your problem. You have to configure your system messages with error.
Regards.
M.Ozgur Unal -
Set Tolerance Limits for Price Variance when PO-based Purch.Requisition
We must garanty that Price from Purch.Requisition will be the same at PO.
IF some variance occur a error messag must be sent to user and PO could not be saved.
I found at customzing under SPRO > Materials Management > Purchasing > Purch.requisition > Set Tolerance Limits for Price Variance .
Reading the help of customizing it mean the system consists what we need..
I have created tolerance limit NB, and set limits for all checks as 0,01.
When I will activate messages as recommended on help no messages 601 and 602 have the text that guide us to correctly setting.
The help mention that after create tolerance limit we must set this tolerance by document type..but I didnt find this field at customzing
Does anyone can help me ?
See the help on customizing below
Set Tolerance Limits for Price Variance
In this step, you can define percentage-based and value-based (absolute) tolerance limits for price variances between purchase orders and purchase requisitions. Variance types are mapped out in the SAP system by tolerance keys.
You define the tolerance limits for each tolerance key and assign your tolerance key to the document types for purchase requisitions. The tolerance limit then applies for all documents of this document type.
When processing a purchase order, the system checks whether the unit price of a purchase order item differs from the unit price of a purchase requisition item. If you have configured, activated and defined tolerance limits in document types, variances are permitted in the tolerance limits. If the variance exceeds the tolerance limit, the system issues a warning. If you have defined a percentage-based and a value-based absolute tolerance limit, the strictest of the two variances will apply for this check.
Note
You can determine whether the system messages (601 and 602) appear as warnings or error messages in step "Define Attributes of System Messages".
To do this, go to the Materials Management IMG and choose Purchasing -> Environment Data -> Define Attributes of System Messages.
Requirements
The tolerance key must be defined in step Define Tolerance Key.
Activities
1. Define tolerance limits for each tolerance key.
2. Define the tolerance key in step Define Document Types.
Thx and best regards,
AleHI
SET TOLERANCE LIMITS FOR PURCHASE REQUISITION UNDER THE DEFINE DOCUMENTS FOR PR
AFTER SETTING TOLERANCE LIMITS WHILE CREATING PURCHASE U WILL GET BASED ON TOLERANCE LIMITS THERE FOUR WAYS TO SET TOLERANCE LITS
1
ABSOLUTE VALUE
2
PERCANTAGE
3
TOTAL PO VALUE
4
QUANITY BASED PRICE PER UNIT
OK BYE -
Tolerance Check for Price Variance is not working
Hello,
In SRM 5.0 IMS we have configured a tolerance group with tolerance Key PP to allow Price Variance while Invoice entry.
We have assigned this tolerance group to the user via attribute TOG in the organizational structure (Transaction Code: PPOMA_BBP)
The user to whom this tolerance group is assigned is logged on into the system and created an invoice in the system with the higher amount as compare to the PO. This difference of price is very well within the tolerance limit configured in the system, but still it gives the following errors:
Average price too high: Tolerance limit of 0.00 and USD exceeded (Item 1)
Value too high (tolerance limit of 0.00 and USD exceeded) (Item 1)
Its not checking the tolerance limit assigned to the user through tolerance group.
But the same works when we assign this to vendor group, but this we don't want.
We want the system to check the tolerance group assigned to the user.
Please suggest the solution to reslove the above errors.
Thanks
SarabjeetHi,
Priority of tolerances is PO tolerance limit, TOG tolerance grp. for User, TOG tolerance grp. for Vendor (if user not logged on). Even absolute tolerance limit always has priority over percentage limit.
In your case, you need to check PO tolerance first then TOG for user.
regards,
rahul -
PO Tolerance Limit for Price Variance
All,
For the key PE I have set Upper Limit for Percentage Check Limit to 0.01%. At what point is the tolerance limit check? Is it at PO creation or some other point?
Thanks,
SeanThe related error message appears at the time of PO creation. It will prevent you from creating the PO with a price that is ourside the allowed tolerance value
PE tolerance limits defines the allowed variation in price between the PO price and that of material price stored in the material master as standard price. The standard price is the output of the standard costing process -
Hi,
Can we set tolerance for price change for particular material or groups of materials.
say i dont want my material price to hit by more than 10% when using average price.Hi Ravi,
SPRO - MM - Purchasing - Purchase Order - Set Tolerance Limit for Price Change
Using the Above path, you can change the Tolerance limits for price at Company code level.
Regards,
Ashok -
LIV tolerance for price variance from PO to LIV
Hi Friends,
I am finding difficulty in setting up the tolerance key for price variance from PO value to invoice value. Suppose if PO price is $100 then system should allow upto $105 with out blocking means with percentage of 5%. If it exceeds 5% system should block the invoice.
Please suggest the tolerance key to use and if any other settings required.
Thanks...
Best RegardsHi,
Following is the SAP help on the Tolerance settings for Invoice. Check the config and decide what is best for you (from your brief explanation it looks like AP and PP may be relevant fro your case)
===================
Set Tolerance Limits
In this step, you specify the tolerance limits for each tolerance key
for each company code.
When processing an invoice, the R/3 System checks each item for
variances between the invoice and the purchase order or goods receipt.
The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
o AN: Amount for item without order reference
If you activate the item amount check, the system checks every line
item in an invoice with no order reference against the absolute
upper limit defined.
o AP: Amount for item with order reference
If you activate the item amount check, the system checks specific
line items in an invoice with order reference against the absolute
upper limit defined. Which invoice items are checked depends on how
you configure the item amount check.
o BD: Form small differences automatically
The system checks the balance of the invoice against the absolute
upper limit defined. If the upper limit is not exceeded, the system
automatically creates a posting line called Expense/Income from
Small Differences, making the balance zero and allowing the system
to post the document.
o BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following
ratios: quantity invoiced in order price quantity units : quantity
invoiced in order units and quantity ordered in order price quantity
units : quantity ordered in order units. The system compares the
variance with the upper and lower percentage tolerance limits.
o BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following
ratios: quantity invoiced in order price quantity units: quantity
invoiced in order units and goods receipt quantity in order price
quantity units : goods receipt quantity in order units. The system
compares the variance with the upper and lower percentage limits
defined.
o DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods
receipt has already been posted, the system multiplies the net order
price by (quantity invoiced - (total quantity delivered - total
quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net
order price by (quantity invoiced - (quantity ordered - total
quantity invoiced)).
The system compares the outcome with the absolute upper and lower
limits defined.
This allows relatively high quantity variances for invoice items for
small amounts, but only small quantity variances for invoice items
for larger amounts.
You can also configure percentage limits for the quantity variance
check. In this case, the system calculates the percentage variance
from the expected quantity, irrespective of the order price, and
compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned
delivery costs.
o DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet
been posted, the system multiplies the net order price by (quantity
invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper
tolerance limit defined.
If you have not maintained tolerance key DW for your company code,
the system blocks an invoice for which no goods receipt has been
posted yet. If you want to prevent this block, then set the
tolerance limits for your company code for tolerance key DW to Do
not check.
o KW: Variance from condition value
The system calculates the amount by which each delivery costs item
varies from the product of quantity invoiced * planned delivery
costs/ planned quantity. It compares the variance with the upper and
lower limits defined (absolute limits and percentage limits).
o LA: Amount of blanket purchase order
The system determines the number of days by which the invoice is
outside the planned time interval. If the posting date of the
invoice is before the validity period, the system calculates the
number of days between the posting date and the start of the
validity period. If the posting date of the invoice is after the
validity period, the system calculates the number of days between
the posting date and the end of the validity period. The system
compares the number of days with the with the absolute upper limit
defined.
o PP: Price variance
The system determines by how much each invoice item varies from the
product of quantity invoiced * order price. It then compares the
variance with the upper and lower limits defined (absolute limits
and percentage limits).
When posting a subsequent debit/credit, the system first checks if a
price check has been defined for subsequent debits/credits. If so,
the system calculates the difference between (value of subsequent
debit/credit + value invoiced so far) / quantity invoiced so far *
quantity to be debited/credited and the product of the quantity to
be debited/credited * order price and compares this with the upper
and lower tolerance limits (absolute limits and percentage limits).
o PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for
this item, the system calculates the difference between the invoice
value and the product of quantity invoiced * order price and
compares the variance with the upper and lower tolerance limits
defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks
whether a price check has been defined for subsequent
debits/credits, If so, the system calculates the difference between
(value of subsequent debit/credit + value invoiced so far) /
quantity invoiced so far * quantity to be debited/credited and the
product quantity to be debited/credited * order price. It then
compares the variance with the upper and lower tolerance limits
defined (absolute limits and percentage limits).
o ST: Date variance (value x days)
The system calculates for each item the product of amount *
(scheduled delivery date - date invoice entered) and compares this
product with the absolute upper limit defined. This allows
relatively high schedule variances for invoice items for small
amounts, but only small schedule variances for invoice items for
large amounts.
o VP: Moving average price variance
When a stock posting line is created as a result of an invoice item,
the system calculates the new moving average price that results from
the posting. It compares the percentage variance of the new moving
average price to the old price using the percentage tolerance limits
defined.
Variances are allowed within predefined tolerance limits. If a variance
exceeds a tolerance limit, however, the system issues a message
informing the user. If an upper limit (except with BD and VP) is
exceeded, the invoice is blocked for payment when you post it. You must
then release the invoice in a separate step. If the tolerance limit for
BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the
system does not check that tolerance limit. Therefore any variance would
be accepted. This does not make sense particularly in the case of the
tolerance key Form small differences automatically.
Activities
Configure the tolerance limits for the individual tolerance keys.
Lower limit Upper limit
Absolute Percentage Absolute Percentage
AN - - X -
AP - - X -
BD X - X -
BR - X - X
BW - X - X
DQ - - X -
DW - - X -
KW X X X X
LA - - X X
LD X - X -
PP X X X X
PS X X X X
ST - - X -
VP - X - X
===============================================
Best Regards,
Siva -
Tolerance for price confirmation
1.The tolerance for price confirmation is not restrictive enough for confirmation control key one particulatr KEY.Where to upadte it to allow only 10% tolerance
Hi
Maintain the config in
SPRO-> IMG-> MM -> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
Here you can miantain the tolernace limits for key PE: Price variance: purchasing
Thanks & Regards
Kishore -
Tolerance limits for PO,MIGO..etc..?
Dear all
Can anybody explain me about the tolerance limits in SAP-MM,
1.what is tolerance limits..?
2.Why tolerance limits need in SAP-MM..?
3.How to configure in SPRO
Which are all the area has to maintain Tolerance limits according to MM point of view
Advance thanks
goods answers will be highly rewardable.
Thanks
sap-mmHi
tolerance limits for price variancesin Purchase order
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
For Invoices specify the tolerance limits for each tolerance key for each company code.
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Thanks & Regards
Kishore -
Maintain tolerance limits for tolerance key PE (CoCode S001)
Dear all
im getting error when i creating PO
Maintain tolerance limits for tolerance key PE (CoCode S001)
Please help me
Regards
venu gopalHi
You need to maintain the Tolerance key
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
Maintain the tolearnce key in
SPRO-> IMG-> Materials Management-> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
If you want the sytem to propmt for a warning or Error message you can configure the same in
SPRO-> IMG-> Materials Management-> Purchasing-> Environment Data-> Define Attributes of System Messages -
Maintain tolerance limits for tolerance key PE
Hi,
How can I correct the error below?
"Maintain tolerance limits for tolerance key PE"
ThanksREFER BELOW SDN POST
Re: TOLERANCE KEY ERROR DURING MIGO
MAINTAIN TOLERANCE LIMITS FOR TOLERANCE KEY PE ACCOUNT ASSIGNMENT -
> Please follow this link --> SPRO -> MM-> Purchasing --> Purchase Order --> Set Tolerance limits for price variance --> Here you have to set for Tolerance keys PE and SE. Just copy them from std co. code.
Message was edited by:
SHESAGIRI.G -
Underdelivery tolerance level automatic closing of PO
Hi Gurus,
We define 5% tolerance level for under and overdelivery, for example: for stock items, we have PO qty 100 pcs,
during goods receipt, over delivery tolerance of 5% we can GR 105 pcs and marked as delivery completed, and in under delivery we can GR 95 pcs but it's marked item partially delivered how we can set this item to be delivery completed to automatically closed the PO?
thanks
Edited by: Marina_25 on Jan 21, 2011 6:57 AMHi Marina,
Your requirement is a genuine one, but in between 2 optins system is not able to decide which one to take
1.) As per tolerance prospective it is under delivery
2.) But you may receive that 5% also in later date
You can go for mass updation of delivery completed tab thro MEMASSPO and can be closed
Thanks.....
Srini Rao -
Ignore Tolerance limits for Subsequent docs.
Dear All,
Is there any possibility exists to avoid PP tolerance key check ignore for only in case of SUBSEQUENT DEBIT/CREDIT.
The tolerance limits sets in PP working fine for INVOICE, but this check i dont want to be considered in case of SUBSEQUENT documents. SUBSEQUENT DEBIT can be done any amount without restricting the limits for PO or tolerances.
Thank you in advance.
Regards,
Syed Hussain.Hi,
I would try this:
1. Configure alternative vendor tolerance limit for my company code.
2. Impelment badi: MRM_TOLERANCE_GROUP. Here, according to SAP documentation, you can change vendor tolerance key during invoice entry based on your on logic.
For the documentation of this badi go to IMG help for: 'IMG -> Materials Management -> Logistics Invoice Verification -> Maintain Customer Exits and Business Add-Ins -> Maintain Business Add-Ins for Invoice Verification' and then for badi MRM_TOLERANCE_GROUP.
Hope, it helps.
Regards,
w.
Maybe you are looking for
-
Macbook Air Haswell-doesn't wake up
As mentioned in the title, literally, my Macbook Air doesn't wake up occasionally. Sometimes (3 or 4 times out of 3-50) when i close the lid of my notebook and open, nothing appears but the black screen appears and only the light of the keyboard glo
-
What is the point of the multitasking bar?
So, I get that for Pandora, Skype, etc. that multitasking is great. I just opened up my multitasking bar though, and found the following "open" items: Messages, Mail, Calendar, Camera, Settings, Map, Weather, Calculator, YouTube, Compass, IMDb, Faceb
-
32 Bit Oracle Client Libraries on a 64 Bit Machine
Hello, I own a 32 bit application that is running on a 64 bit linux machine currently only installed with 64 bit oracle client libraries. I requested the administrator install the 32 bit client libraries so that my application can function and they t
-
Screen turns to black, red green ect.
Ok so I have been having this problem with my G4 ibook. It will be fine and working ok. Then it will suddenly turn to a black screen, then red, then green, then gray, white and back to black. There are no lines on the screen just a solid color. When
-
SSIS - How to run command line to copy files with User Variables within a Execute Process Task
Hello, I'm am having syntax issues within the Arguments when trying to copy a file with cmd.exe using User Variables. It works when I hard code the arguments : /c copy /b "\\folder1\file.txt" "\\folder2\file.txt" However, it's failing when I try usi