Failure Cost Handling - FCODOC

Dear Experts,
I have come across the concept of "Failure Cost handling". The concerned Transaction Code is FCODOC. Can anyone help out with any concept document/link on this subject?
Thanks in advance for your kind support.
Regards,
Amit

Dear Experts,
From the knowledge transfer documents received from client, I found following "Failure Cost Handling" being mentioned:
1) Actual Overhead calculation u2013 Failure cost internal order
2) Settlement u2013 Failure cost internal order
3) Settlement u2013 Credit object of Failure cost Internal order
Can any expert throw some light?
Regards,
Amit

Similar Messages

Shiptment Costs handling in SD and itz integration to CO-PA from CO side

Hi ,
Can any one help me to understand the baisc functionaing of Shiptment Costs handling in SD and itz integration to CO-PA,
Any doument link is also most welcome

Please dont cross post the same question in multiple forums
thanks
G. Lakshmipathi

Failure cost solution

I am looking SAP documentation for "failure cost solution".
Please, can you help me and tell me where I can find it.

Hello Adriana,
in case you are working for a customer or partner organization, I would recommend to go to the Service Market Place (http://service.sap.com/) and search in the help portal (http://help.sap.com/) for the documentation. Just enter the search string 'failure cost' and you will find a bunch full of hits for SAP ERP.
I hope this helps.
Regards,
Frauke

Failure cost evaluation

Hello All,
Can anyone please tell me what could be the reason for this. One failure cost document was evaluated 5 times. The evaluation happens through job scheduling. Not able to trace the problem.
Full points will be awarded for atleast answer which provides an idea.
thank you,
Nivas

Can you please explain more of the context, module etc. Are you referring to any reporting?

Configuring selection failure error handler

I have a scope which does an invoke. There is a possibility it causes a selection failure and hence I was trying to configure a catch branch for selection failures.
In the part where I have to give a variable name, I cannot seem to be able to click on the button for creating a new variable. Can someone help me out with configuring a variable for this particular error.
Thanks

1. Add a Catch branch
2. Double click on it
3. In Fault Qname, Select Browser Faults icon
4. Expand System Faults
5. Select selectionFailure
Ok, Done
--Prasanna

Crystal Report error - The Handle is invalid;

I get the error 'The handle is Invalid' when I try to print a crystal report that is opened in the Report viewer.
I was wondering if anyone has encountered this is has a solution.
The report was created using Crystal Report 2008 for SAP B1.
Regards
Albert

Albert,
You may check those old threads first:
Embarrasing issue
Re: 5 : - The handle is invalid
Landscape test connection failure: The handle is invalid.
Thanks,
Gordon

Facing issue while handling faults using fault-policies.xml

Hi All,
Scenario: One Asynchronous Bpel is trying invoke the webservice. When the status of the webservice is "Down", the BPEL will throw "System fault : remoteFault"
This fault will be handled by the fault-policies.xml.
CustomFaultHandler.java : basically it will print data to audit-trail and send data to the JMS Queue.
I am facing some issues , when i am trying to handle faults using fault-policies.xml.
Issue1: Display warning message at time of deployment : Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
Issue2: CustomFaultHandler.java is able to print data to audit-trail but unable to send data to the Queue. and why the policy file getting executed at time of "Start of Invocation" and then it's showing "Invocation faulted" ?
Audit-Trail Message:
*===========*
Started invocation of operation "process" on partner "RemoteService".Started invocation of operation "process" on partner "RemoteService".
[Fault Recovery] Invoked handleBPELFault on custom java action class "com.CustomFaultHandler".
Invoke1
190002190002
default/TestjavaAction!5.0*soa_fcb2a5dd-06a7-47f9-bb88-cab14d343856/TestBPEL
190002
Faulted while invoking operation "process" on provider "RemoteService". Faulted while invoking operation "process" on provider "RemoteService".
fault-policies.xml:
*==========*
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1" id="ErrorHandlingModelr"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-java"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-java">
<javaAction className="com.CustomFaultHandler"
defaultAction="ora-terminate">
<returnValue value="Manual" ref="ora-abort"/>
</javaAction>
</Action>
<Action id="ora-abort">
<abort/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
fault-bindings.xml:
*===========*
<?xml version="1.0" encoding="windows-1252" ?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<component faultPolicy="ErrorHandlingModelr">
<name>TestBPEL</name>
</component>
</faultPolicyBindings>
Warning Message when trying to deploy the composite to the server :
=============================================
Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
Error Message from server:
*==============*
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.
failure to handle a fault thrown from a scope, by any blocks in the scope chain.
This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.
failure to handle a fault thrown from a scope, by any blocks in the scope chain.
This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
at java.lang.Thread.run(Thread.java:662)
Please help..
Thanks in Advance
Edited by: Sharmistha Ghosh on May 16, 2012 12:37 PM

My SOA suite version is 11.1.1.7 and i was getting the same warning while compiling the Composite in JDeveloper. To fix it update your fault-policy.xml
Change it to
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <faultPolicy version="0.0.1"
                 id="BPELProcessV1_Faults"
                 xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                 xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 xmlns="http://schemas.oracle.com/bpel/faultpolicy"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
And it will solve the issue.

Shipment Cost Integration to COPA

Hi ,
Can any one help me to understand the baisc functionaing of Shiptment Costs handling in SD and itz integration to CO-PA,
Any doument link is also most welcome.

Any doument link is also most welcome
Before posting this question, have you searched ??
Check this documentation.
[Shipment Cost Processing |http://help.sap.com/saphelp_oil472/helpdata/en/70/23d94f419311d2ac100000e829fbfe/content.htm]
thanks
G. Lakshmipathi

Is the 256GB flash storage enough for me? Can I install a bigger SD?

Hi there, I am transferring from a Dell (which I love) to the Macbook Air 256. However, I'm very concerned about the storage. I've had my Dell for 10 years and never gotten near the storage capacity. It has 285Gb and I've used 215GB of it. I figured the 256 would be enough, but I've only transferred 1 year of pictures over to my MAC, and the storage space is already HALF FULL!!!! I barely deleted 50 photos, and you can see the storage space free up by a couple GBs. Does flash storage not hold as much as regular hard drives? I'm a novice at mac computers and am getting really frustrated that this computer might not hold anything. Everything is also on an external drive, but I like it all on my computer for easy access. I also heard that I can put SD cards into my Macbook air to give me more storage. Is this true and if so, where do I get that? Thank you so so much for your help!

firebox is only $30 at walmart, if you dont have a safe deposit box.
theft is more about HIDING IT than vaulting it, buy a fireproof SLEEVE on Ebay for $30 and hide it under etc etc something, very easy to do.
you can buy your own private website, which is what I do, I have several   Cost is roughly $120 per year unlimited storage..
(see godaddy.com or otherwise)
However safety has to be put in place to prevent others from accessing your data, also very easy.
Its all about redundancy #1 and #2 longevity (DVD professional archival) for very important information that cant degrade over short term and rated for at least 60+ years.
All these points are explained in detail in the link I posted you as User Tip.
Online archives
Drawbacks:
1. Subject to server failure or due to non-payment of your hosting account, it can be suspended.
2. Subject, due to lack of security on your part, to being attacked and hacked/erased.
Advantages:
1. In case of house fire, etc. your data is safe.
2. In travels, and propagating files to friends and likewise, a mere link by email is all that is needed and no large media needs to be sent across the net.
3. Online archives are the perfect and best-idealized 3rd platform redundancy for data protection.
4. Supremely useful in data isolation from backups and local archives in being online and offsite for long-distance security in isolation.
5. *Level-1.5 security of your vital data.
As for hard drives, dont make the HUGE mistake others make, only having ONE off computer copy on a HD, thats a tragedy in waiting, 2 copies is 1, and 1 is none, ....and the data on the computer doesnt count in the 2-copy scheme.
Hard Drive Warning (all makes and models)
Ironically but logical, new hard drives are far more fragile than one that has been working for several months or a couple years. So beware in your thinking that a new hard drive translates into “extremely reliable”!
Hard drives suffer from high rates of what has been termed "infant mortality". Essentially this means new drives have their highest likelihood of failing in the first few months of usage. This is because of very minor manufacturing defects or HD platter balancing, or head and armature geometry being less than perfect; and this is not immediately obvious and can quickly manifest itself once the drive is put to work.
Hard drives that survive the first few months of use without failing are likely to remain healthy for a number of years.
Generally HD are highly prone to death or corruption for a few months, then work fine for a few years, then spike in mortality starting at 3-4 years and certainly should be considered end-of-life at 5-7+ years even if still working well. Drives written to once and stored away have the highest risk of data corruption due to not being read/written to on a regular basis. Rotate older working HD into low-risk use.
The implication of this is that you should not trust a new hard drive completely (really never completely!) until it has been working perfectly for several months.
Given the second law of thermodynamics, any and all current mfg. HD will, under perfect storage conditions tend themselves to depolarization and a point will be reached, even if the HD mechanism is perfect, that the ferromagnetic read/write surface of the platter inside the HD will entropy to the point of no viable return for data extraction. HD life varies, but barring mechanical failure, 3-8 years typically.
Hard drive failure and handling
The air cushion of air between the platter surface and the head is microscopic, as small as 3 nanometers, meaning bumps, jarring while in operation can cause head crash, scraping off magnetic particles causing internal havoc to the write surface and throwing particles thru the hard drive.
Hard drives are fragile in general, regardless, ... in specific while running hard drives are extremely fragile.
PDF: Bare hard drive handling generic instructions
hard drive moving parts
Some of the common reasons for hard drives to fail:
Infant mortality (due to mfg. defect / build tolerances)
Bad parking   (head impact)
Sudden impact   (hard drive jarred during operation, heads can bounce)
Electrical surge   (fries the controller board, possibly also causing heads to write the wrong data)
Bearing / Motor failure   (spindle bearings or motors wear during any and all use, eventually leading to HD failure)
Board failure   (controller board failure on bottom of HD)
Bad Sectors   (magnetic areas of the platter may become faulty)
General hard drive failure

CREATION OF A TYPICAL PURCHASE ORDER

We have a requirement where in the PO would be created for a set of items under one material code with the unit of measure as Set / Kit / LSM. While receiving the items we will get the items in part and we may have pay them based on the invoices for the partially supplied items. This is going to be the phenomena in the project procurements / EPC Contracts etc. In addition, the same case can happen in the case of service related orders also.
In addition, there is a typical case of one order containing the following conditions:
The order is for some Rs 100 crores, where in about Rs 50 crores worth of materials are supplied by ours at free of cost. Rest Rs 50 crores is given to the vendor for the contribution from the vendor side.
The above Rs 50 crores amount includes Materials procured by vendor, labour Cost (own labour as well the subcontract labour cost), deployment of equipments for construction,
Hiring charges of these equipments, amortization costs for the investments done on the equipments, Engineering and drafting costs, Handling costs, Profit etc
The handling costs are calculated as follows:
An amount equivalent to 15% on the material cost which is supplied by us to the vendor (15% on 50 crores) is paid as handling *** profit to the vendor.
This amount in turn is paid in parts as and when the materials are handed over to the Vendors by us and based on the invoice raised by the vendor to us.
An amount equivalent to 20% on the rest of the value as handling *** profit to him and this is paid based on the invoice raised by the vendor.
In both the cases we have to keep a tab on the total sum paid to the vendors where in the order value cannot be increased.
This order has to be created in SAP immediately.can any body assist me to the same. Points awarded for best solution.
thanks and Regards
Naagsekhar

Hi, please refer to link http://www.sap-img.com/mm021.htm

Issue with FCOST (no FCOST document created)

Hi All,
I have activated FCOST for Production Orders in the settings. A trigger point has been set for the last operation in the routing, which triggers the creation of a rework order when there is a rework qty.
I confirm the rework order with CO11n, but no FCOST document is being created. I am using the rework order just to register the labor hours for rework & no component is added.
May i know why the FCOST document is not being created?
Vivek

Dear,
FCOST stand for Failure Cost. In release 4.70 above, There is a new tcode FCOST for rework confirmation you can update rework quantity to next operation.so it can be confirmed together with yield operation
To Activate Failure Cost Processing for Production Orders
1. Start transaction FCOACTIV_SFC
2. Activate Failure Cost Processing for the required plants and order types.
3. Choose Save.
After activating this Failure cost, then every rework quantity that you confirmed in CO11N will be updated in FCOST. In FCOST, you can confirm all activity and material issues that relevant with rework processing.
Please refer this link also,
[FCOST|https://forums.sdn.sap.com/click.jspa?searchID=16546329&messageID=4230254]
Regards,
R.Brahmankar

Issue with creation FAZ billing doc. No billing document created. No Log.

I am trying to post the invoice with the billing type(FAZ) Down payment request with the sales document type OR. I am using item category TAO and i have attached mile stone billing with this item category. When i try to invoice this down payement item with the billing type FAZ, it gives me the message "No billing docments generated" and when i go to see the log, it says no error log generated, and it shows the processing status on billing screen not processed.
VKOA checked, seems OK.
Thanks for your help.

Dear,
FCOST stand for Failure Cost. In release 4.70 above, There is a new tcode FCOST for rework confirmation you can update rework quantity to next operation.so it can be confirmed together with yield operation
To Activate Failure Cost Processing for Production Orders
1. Start transaction FCOACTIV_SFC
2. Activate Failure Cost Processing for the required plants and order types.
3. Choose Save.
After activating this Failure cost, then every rework quantity that you confirmed in CO11N will be updated in FCOST. In FCOST, you can confirm all activity and material issues that relevant with rework processing.
Please refer this link also,
[FCOST|https://forums.sdn.sap.com/click.jspa?searchID=16546329&messageID=4230254]
Regards,
R.Brahmankar

Porsche Design External Hard Drive for Time Machine back-up

This is what I am looking to buy for my back up: http://www.amazon.com/LaCie-Porsche-Design-External-9000296/dp/B008SA69L8/ref=sr _1_10?s=electronics&ie=UTF8&qid=1393398362&sr=1-10&keywords=porsche+design.
But this is not available on online Apple Store. Only "desktop drives" are available. What is the difference between "desktop drive" and "external drive?"
Also, how do these Porsche Design hard drives rank in terms of reliability and longevity?
Do I need to install LaCie software to use this hard drive for back-up? Or is it possible to directly use Time Machine to use this hard drive for back-up?
Lastly, how does password protection work? Does the LaCie software have to be installed to take advantage of this?

mrq0604 wrote:
How about 3.5" Seagate drives? Are they any better in terms of quality?
Currently the promotional price for 3.0 TB Porsche Design "external drive" is $129 (normally $169). Is this a good deal? And the 3 TB "desktop drive" is $153. Why would they sell thr same product under 2 different names and with different prices? What does "external drive" offer for $16 more? As far I know, they look the same...
How about 3.5" Seagate drives?
Absolutely not, no.
All HD can and do crash and fail, its just statistical sampling in total (see graph above)
If you want the most reliable 3.5" HD, get a 2TB Toshiba, which is actually made by Hitachi (confused yet?)
Hitachi sold their 3.5" division to Toshiba (forced to actually), so a Toshiba 3.5" is really a very well built reliable Hitachi 3.5"
On sale, 2TB Toshiba 3.5" (really Hitachi made) only $88
http://www.amazon.com/Toshiba-Canvio-Desktop-External-HDWC120XK3J1/dp/B008DW96NY /ref=sr_1_10?ie=UTF8&qid=1393443687&sr=8-10&keywords=toshiba+2tb
There is actually a non-commercial HD more reliable than this, which is the WD "black" drives, the server grade drives, but theyre not consumer grade
theyre very expensive, and made for server farms.
here:
http://www.amazon.com/Western-Digital-Cache-Desktop-WD2003FZEX/dp/B00FJRS628/ref =sr_1_2?ie=UTF8&qid=1393443945&sr=8-2&keywords=wd+black
As said no such thing as Porsche, its Seagate . Porsche is just the name on the enclosure.
Why sell under 2 diff. names?   Actually they do it under 5 DIFFERENT NAMES , Hitachi does the same, so does WD
As I said, there are only 4 HD makers on earth.    The many names etc is to fill up shelf space with diff. names such as Porsche , LaCie etc etc.
Id avoid most of the 3TB and certainly the 4TB drives for at least maybe another half year or so.
Large external hard drives are great! Large external hard drives are horrible
It is a common premise that people are overjoyed at the dropping prices per terabyte on external hard drives, and the first thing that enters most peoples minds is "great, I can put all my stuff on one drive,... all of it!" However considerations need to be made in creating a giant single choke point for not mere data loss, but seriously large data loss. If there is at the very least yet another redundant copy, this is fine, otherwise do not consider it whatsoever. Some 3TB and 4TB drives of all mfg. have, at the time of this writing, reliability concerns currently and best recommendation is staying at 2TB drives or less.
Advantages and disadvantages of larger 3TB and 4TB external drives must be weighed
Hard Drive Warning (all makes and models)
Ironically but logical, new hard drives are far more fragile than one that has been working for several months or a couple years. So beware in your thinking that a new hard drive translates into “extremely reliable”!
Hard drives suffer from high rates of what has been termed "infant mortality". Essentially this means new drives have their highest likelihood of failing in the first few months of usage. This is because of very minor manufacturing defects or HD platter balancing, or head and armature geometry being less than perfect; and this is not immediately obvious and can quickly manifest itself once the drive is put to work.
Hard drives that survive the first few months of use without failing are likely to remain healthy for a number of years.
Generally HD are highly prone to death or corruption for a few months, then work fine for a few years, then spike in mortality starting at 3-4 years and certainly should be considered end-of-life at 5-7+ years even if still working well. Drives written to once and stored away have the highest risk of data corruption due to not being read/written to on a regular basis. Rotate older working HD into low-risk use.
The implication of this is that you should not trust a new hard drive completely (really never completely!) until it has been working perfectly for several months.
Given the second law of thermodynamics, any and all current mfg. HD will, under perfect storage conditions tend themselves to depolarization and a point will be reached, even if the HD mechanism is perfect, that the ferromagnetic read/write surface of the platter inside the HD will entropy to the point of no viable return for data extraction. HD life varies, but barring mechanical failure, 3-8 years typically.
Hard drive failure and handling
The air cushion of air between the platter surface and the head is microscopic, as small as 3 nanometers, meaning bumps, jarring while in operation can cause head crash, scraping off magnetic particles causing internal havoc to the write surface and throwing particles thru the hard drive.
Hard drives are fragile in general, regardless, ... in specific while running hard drives are extremely fragile.
PDF: Bare hard drive handling generic instructions
hard drive moving parts
Some of the common reasons for hard drives to fail:
Infant mortality (due to mfg. defect / build tolerances)
Bad parking   (head impact)
Sudden impact   (hard drive jarred during operation, heads can bounce)
Electrical surge   (fries the controller board, possibly also causing heads to write the wrong data)
Bearing / Motor failure   (spindle bearings or motors wear during any and all use, eventually leading to HD failure)
Board failure   (controller board failure on bottom of HD)
Bad Sectors   (magnetic areas of the platter may become faulty)
General hard drive failure

WD external 1TB not working anymore @ Macbook Air

hi there.
After hours trying to figure it out, I just realized that I have too an OLD WD 1TB that has the sata brdge together with the drive itself... problem is, my Macbook is not recognizing the WD passport anymore. It is my time machine backup drive, so I am kind of upset...
There is a way, any way to put this drive again working, in another drive case or whatever?
I already updated the drives, I have 2 others external drvies, one from iomega and another one from WD, olders, and both are working.
i bought this one january/2013 in LA. How old are they?!?! gosh...
I have a MacBook Air 13", MACOSX 10.8.
here is a photo from the drive, after I had opened the case.
Thanks for any help or hint.
Cheers form Brazil,
AM

Yup, that is WHY you never buy WD external HD, they cheap out and save 50 cents by making the controller board and SATA bridge card the same unit
Toshiba is now doing the same thing, avoid them as well
Purchase Seagate and Hitachi to avoid that (Hitachi are the best ext. USB drives without doubt)
see here all about it:
Your dead external hard drive is likely fine! Great hope for your 'faulty' external HD
There is a way, any way to put this drive again working, in another drive case or whatever?
ONLY if you had another identical HD you could swap the controller boards.
. It is my time machine backup drive, so I am kind of upset...
You never should have let yourself be in the position of having a single external DATA copy, ever
hard drives are way way too cheap to let that happen.
i bought this one january/2013 in LA. How old are they?!?! gosh...
That doesnt mean anything
Hard Drive Warning (all makes and models)
Ironically but logical, new hard drives are far more fragile than one that has been working for several months or a couple years. So beware in your thinking that a new hard drive translates into “extremely reliable”!
Hard drives suffer from high rates of what has been termed "infant mortality". Essentially this means new drives have their highest likelihood of failing in the first few months of usage. This is because of very minor manufacturing defects or HD platter balancing, or head and armature geometry being less than perfect; and this is not immediately obvious and can quickly manifest itself once the drive is put to work.
Hard drives that survive the first few months of use without failing are likely to remain healthy for a number of years.
Generally HD are highly prone to death or corruption for a few months, then work fine for a few years, then spike in mortality starting at 3-4 years and certainly should be considered end-of-life at 5-7+ years even if still working well. Drives written to once and stored away have the highest risk of data corruption due to not being read/written to on a regular basis. Rotate older working HD into low-risk use.
The implication of this is that you should not trust a new hard drive completely (really never completely!) until it has been working perfectly for several months.
Given the second law of thermodynamics, any and all current mfg. HD will, under perfect storage conditions tend themselves to depolarization and a point will be reached, even if the HD mechanism is perfect, that the ferromagnetic read/write surface of the platter inside the HD will entropy to the point of no viable return for data extraction. HD life varies, but barring mechanical failure, 3-8 years typically.
Hard drive failure and handling
The air cushion of air between the platter surface and the head is microscopic, as small as 3 nanometers, meaning bumps, jarring while in operation can cause head crash, scraping off magnetic particles causing internal havoc to the write surface and throwing particles thru the hard drive.
Hard drives are fragile in general, regardless, ... in specific while running hard drives are extremely fragile.
PDF: Bare hard drive handling generic instructions
hard drive moving parts
Some of the common reasons for hard drives to fail:
Infant mortality (due to mfg. defect / build tolerances)
Bad parking   (head impact)
Sudden impact   (hard drive jarred during operation, heads can bounce)
Electrical surge   (fries the controller board, possibly also causing heads to write the wrong data)
Bearing / Motor failure   (spindle bearings or motors wear during any and all use, eventually leading to HD failure)
Board failure   (controller board failure on bottom of HD)
Bad Sectors   (magnetic areas of the platter may become faulty)
General hard drive failure

Can we maintain Letter of credit in sap

Hi Friends,
Can we maintain LC in sap ? If so Please tell how to maintain.
Regards

HI,
Link below may be of use to you.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/letterofCredit
http://help.sap.com/erp2005_ehp_01/helpdata/en/95/3ca410110511d4b5ae006094b9ec21/frameset.htm
You can map the Import cycle in SAP. The standard business practices in SAP are
1. Create the Import pricing procedure with all necessary import conditions like customs duty, CVD, Landing cost, handling charges, Freight charges etc. Assign it to the schema group & inturn to Pur. organisation.
2.Create the import vendor master record.Assign the import schema group to this vendor. So that while creating import PO for this venor, the system will determine the import conditions.
3.Create the Import Po with Zero tax code & also with req Payment terms.
4.Enter the Customs vendor against the Customs & CVD conditions. Also maintain Freight vendor against freight conditions in the PO itself.
5.Do the MIRO for Customs vendor. Enter manually all the details in MIRO take the ref as a Bill of entry,
5.Do the MIGO for PO, Capture the excise & post the doc. As per Indian Govt Excise rule, you can take the credit of CVD as Excise.
6.Post the Excise doc.
7.Do the MIRO for material vendor.
8.Clear the Payment.
Thanks & Regards,
Kiran

Failure Cost Handling - FCODOC

Similar Messages

Maybe you are looking for