Consignment issue - stock related problem

hello,
This is an issue related with consignment issue.
material document is created and and seen in document flow. also posted in FI
It can be seen in MB51 with special stock indicator 'w' But it cant be seen in MB58.
There is a mismatch.
movement type used is 633.
Please help on how we can analyse this further.
Thanks

Hi,
I dont think Consignment issues are shown in MB58 report since this report is only for consignment stocks at customer place and also for returnable packaging stocks.
Consignment issue is as good as sale. so it wont reflect in the MB58 report only Movement types goods with 631 and 634 will show in MB58.
Please check.
Regards,
Sharan

Similar Messages

Consignment issue stock problem

Hi Guys,
One consignment issue sales order of 500 qty has been created but only 139 qty got confirmed.
When I check in MMBE for the particular customer, consignment stock is there. 503 qty.
Still, cant able to confirm full qty in order.
What could be the probable reason?
And what needs to be done to up the stock?
Please advice.
Cheers....!!
Chetan.

In my earlier project, same problem was coming repeatedly from the end users and in almost all the cases, the issue order quantity was more than the proforma quantity. Other than that, whatever I suggested is only my assumption. In fact, what I would suggest is that for that material, you list all open KE sale orders created and compare with quantity despatched from parent plant. I feel definitely, the root cause of your problem should be here only.
Will suggest in case I got any other clue
thanks
G. Lakshmipathi

Consignment issue Accounting entries problem

Dear Guru's
I have configured the consignment sales for my client but i am facing one problem pl advice
1. Consignment fill up process (delivery of goods)
Create Billing document         Accounting Entry
                   Consignee A/c                       Dr
                   Consignment Sales Contra Cr
but issue in
2. Consignment issue process
Create Billing document         Accounting Entry             as
                      Consignee A/c                       Dr
                     Sales revenue                        Cr
WHERE AS IN THIS CASE I NEED IT SHOULD DEBIT THE Consignment Sales Contra
I need this entries in accounting document
Consignment Sales Contra Dr
Sales revenue                        Cr
Regards
Arun
Edited by: ArunSingh2010 on Jun 20, 2010 11:20 AM

Consignee A/c Dr
Consignment Sales Contra Cr
I feel you have not configured properly for consignment process. As you would be aware in fill up stage, there would be no accounting implications either while posting the goods issue or creating a proforma on customer due to the fact that you would just be moving the goods from delivering plant to another location.
This being the case, I dont know why you want the consignee account to be debited ??
thanks
G. Lakshmipathi

Consignment issue stock

hello experts,
There is a situation where in one user has to process a consignment fill up order. let us go by an example, if the consignment fill up is for 100 units. the user has processed the first consignment issue for 25 units. at the time of the second consignment issue the consignment stock available should show only 75, not the entire 100(100-25), Any popup and userexit to be maintained her for the purpose? what is the solution here?
Regards,
Raj

Dear Raj
The process would be as follows:-
1) Consignment Fillup
- Create (KB) Fillup order
- Create (LF) Delivery
- Create (F8) Proforma
- Create Excise Invoice in J1IIN
2) Consignment Issue
- Create (KE) Issue Order referencing F8 proforma
- Create Issue Delivery for the quantity what is moved from warehouse
- Create commercial (F2) invoice
: you need to maintain the excise invoice number range for exports in SNRO for Object : J_1IEXCEXP
thanks
G. Lakshmipathi

Dead stock related problem.

hi,
how do we configure dead stock period ?
n:b--- I'm using the t.code mc50 for display purpose
thankx
Aniruddha

It is by default a 3 months period, backdated from today which is autoamtically pulled into the selection screen of MC50.
If you want analyze a different period, then you have to overwrite this in the selection screen. No configuration available.

Consignment Issue - No stock available

Hi,
While creating a Consignment Issue order, the quantities are not getting confirmed eventhough the stock is available in MMBE (Customer Consignment) for that particular customer.
i have checked that there are no other open orders for the same, the Sch Line Category = C1 & the Movement type = 633.
Please let me know what could be the issue here.
Thanks & regards
Narain

Hi Lakshmipathi,
thanks for your reference link.
Here also, there seems to be an issue with the ATP logic. But, i am not changing any partner details.
The Problem statement as below: (There were no open orders / deliveries before we start the below process)
First Run:
I create a Consignment Fill up order (say, CF00001) with Quantity 1, Delivery & GI. In MMBE, there is a cust consignment stock of qty 1. The ATP quantities (in CO09 transaction) are: Receipts 1, Issues 0 & Confirmed Isses 0.
Then, i create a Consignment Issue Order (say, CI00001) with Qty 1. I am able to create a delivery & then do the GI.
In MMBE, the cust consignment stock vanishes & in CO09, the ATP quantities are: Receipts 0: Issues 1 & Confirmed Issues: 1
The above looks fine to me.
Second Run:
I create another Consignment Fill up order (say, CF00002) with Quantity 2, Delivery & GI. In MMBE, there is a cust consignment stock of qty 2. The ATP quantities (in CO09 transaction) are: Receipts 2, Issues 1 & Confirmed Isses 1.
Then, i create a Consignment Issue Order (say, CI00002) with Qty 2. The system confirms only 1 qty & not 2 as required.
I am not sure what could be the possible reason.
Is it because, since in the ATP,
Receipts is 2, Issue is 1 - the system calculates the difference (Receipt - Issue) & confirms only 1 qty.
Please let me know if my understanding is correct & what could be the possible solution to this.
Edited by: Narain on Jan 21, 2011 1:39 PM

Process of issuing stock to consignment customers

Hi,
Please tell me or guide me on proper procedure in issuing stock to consignment. now we are using transfer posting from fix bin to storage location of consignment.
1. first we create reservation thru PO of customers using tcode MB21 with mvt type Z11
2. printing of picklist for pick and pack
3. good issue of stock tcode MB1B mvt. type Z11
4, Run the MMBE it show stock of consignment at unrestricted use.
LIke sample of Storage location
ZS01 = Supervalue but have different outlet like Megamall, Mall of Asia, North Edsa.
ZP01 = Puregold but have different outlet like Puregold Pasig, Puregold Mandaluyong.
what we are doing now are correct or not please guide me on proper process in consignment.
Thanks a lot
Ermin D. Concepcion

Hi ,
The complete process will be having four steps ;
Consignment fill up : the stock will go to the customer place ,but the ownership will be with company only.
Sales Document type ; KB
Item category             :KBN
Movement type           :631
Consignment issue : we will create an invoice equal to the addressed by the customer .(the end customer sale )
Sales Document type ; KE
Item category             :KEN
Movement type           :633
Consignment returns :if the end customer returns to our customer , here the stock will be at customers place ,but
we will make return invoice.
Sales Document type ; KR
Item category             :KRN
Movement type           :634Hi
Consignment pick up :If the stock returned from customer location to our location .
Sales Document type ; KB
Item category             :KBN
Movement type           :632 .
Here customer means our customer .
final customer means ; our customer's customer .
Regards
Raghavendra

Consignment issue Problem

The problem we encounter is that in the consignment issue order which is created by reference to fill-up order, every time issue order will set the quantity of the material to be the quantity in referred fill-up order. For example, if fill-up order has 100 unit of material X, and then system will set the quantity of material X in issue order to be 100 either.
But there is a situation that in the first issue order, we have consumed 10 unit of material X. In this case, in the second issue order, we want to have the quantity of material X to be default as 90 units (100 - 10 = 90 units).
Is there any User exit or BADI or whatever way to help me to calculate the remained quantity automatically in issue order?
give me some solutions for this issue.
Thanks&Regards,
Mahi

In complition rule what shoud i maintain to process my senario.My issue is with ref to consignment fillup order we create the issue order ,. For example, if fill-up order has 100 unit of material X, and then system will set the quantity of material X in issue order to be 100 either.
But there is a situation that in the first issue order, we have consumed 10 unit of material X. In this case, in the second issue order, we want to have the quantity of material X to be default as 90 units (100 - 10 = 90 units).
A     Item is completed with the first reference
B     Item is completed after full quantity has been referenced
C     Item is completed after the target qty is fully referenced
D     Item is referenced via contract release
E     Item is completed after full target value is referenced.
Pls help me on this issue.
Thanks& Regards
Mahi

Problem in receipt stock & Issue stock

Dear All,
I have some problem in inventory cube 0IC_C03. when we execute query for total stock ,total Receipt stock &Total issue stock, we found that total stock is matching with MB5B but issue stock & receipt stock is not matching. Then I added material doc no. & movement type in cube 0IC_C03 and checked query material doc no. wise & movement type wise. I found that some material docs no are not coming in MB5B which are for stock transfer. & some movement type such as 310,202,602,552 (which are reverse of 309,201,601,551 Issue stock) is coming in BW for issue stock with negative values in Bex query.But in MB5B these movement types are coming in receipt stock.Therefore total receipt qty and issue qty is not matching with MB5B. Please suggest what restrictions i shuold make in BW so that my query will match with MB5B.
Thanks in advance,
regards,
Yogesh

Dear Guys,
Regards.Even we are stuck up with the same above issue for quite sometime..Would be great if someone could throw light on this...........if possible...
Manythanks
arun

Regarding Consignment Issue

Hi Friends,
I have a question regarding consignment issue. During the consignment fill up I have entered a material (machine) that is configurable and also assigned a serial number to it. Now when I try to create an order (consignment issue) and enter the corresponding serial number tied up to the machine in Consignment fillup, the system is taking just the higher level item of the BOM. The BOM is not getting exploded in the order. Can anyone please suggest where I can control. Any help is greatly appreciated. Thanks in advance.
Sunny.

Hi
I don't think it will b exploded in Consignment Issue as it has already exploded in Consignment fill up. Consignment issue means what selling the stock which is at consignee's place so it dose not have to b exploded. u carr on like that and see what is the flow if it is ok then go on otherwise u let me know the problem.
Thanks
Mastan

Consignment issues,delivery,return.plese guide customise

hi,
consignment problem and customise.

Hi,
The consignment process in SAP standard consist of four small processes:
Consignment fill-up (send materials to customer consignment).
Here you have a consignment fill-up order and a consignment fill-up delivery.
Consignment issue (issue materials from customer consignment to the customer).
Here you have a consignment issue order, consignment issue delivery and a consignment issue invoice. (the flow is very similar to a normal OR flow, but the materials are issued from the consignment stock instead of plant stock unrestricted).
Consignment return (return materials from customer ownership to customer consignment).
Here you have a consignment return order, consignment return delivery and a consignment return invoice. (the flow is very similar to a normal RE flow, but the materials are returned to the consignment stock instead of plant stock returns).
Consignment pickup (pickup consignment stock and move it to plant stock).
Here you have a consignment pickup order and a consignment pickup delivery.
Note that in consignment fillup and consignment pickup there are no invoices since there is no change of ownership for the materials.
How to perform a consignment order?
In consignment orders you are allowing the stock to sit in your customer location. Once he informs that he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.
It is defined in 4 steps.
1. Consignment fill up:
Sales document type is KB
Item category KBN
shedule line category E1
In this step, you are not invoicing the customer. document flow is sales order -
delivery item category. It will not be relevent for billing and pricing because you are not charging money for these goods in this step.
In schedule line category, you will set movement type 631 & set for availability check and TOR.
2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods.
Sales document: KE
Item category: KEN
shedule line category: C0 or C1
Here you are invoicing the customer(because he used the goods). you are assigning the delivery documnt and billing document to the sales document.
In item category, you are setting relevent for billing, pricing, special stock.
In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.
3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document.
Sales document type: KR
Item category: KRN
Shedule line category: D0
You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
4. Consignment Pick up:
Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing.
Assign retrun delivery to sales document type.
Sales document: KA
Item category: KAN
schedule line category: F0 & F1
Your setting item category relevent for returns. any shedule line category relevent for 632 movement type, MRP, availability check, delivery.
Now you check your plant stock. Stock will increase.
Regards,
Abhee.

Consignment Issue - Resheduling.

Dear All,
We create COnsignment issue order with material X, whee stcoks were 0, item level its not confimred.
Next we place the consignment stocks Via MB1C, and trying to run V_V2 resheduling job, but system is not confirming the quanity ar item level.. can you please put some light.

Hi Ramki,
As per standard we have to do the consignment fillup.Becuase system recognises that the plant stock has been posted to particuklar consignee with the Special stock indicator"W" which is harcoded in the movement type "631" You can see this in the transaction "OMJJ" and select the movement type "631" and Select Filed selection/Batch search procedure and click on general data and at the top you can see the "Spec.Ind.f.St.TrnsferW". Then system will place this stock under consigment. When you do the issue ,system seraches for the consignment stock rather than the Unrestricted stock at the palnt level. To achieve , what you are looking for , you can proceed by posting the intial sotkc with the special stock category "W"(System will ask for the customer, enter the same) and check the stock in MMBE. It will show the customer consignment stock. Now proceed creating the issue, you will not find any problem. Kindly please let me know If you need any more information on this.
Regards,
Ram Pedarla

Consignment issue (KE)

hi gurus,
In the customer consignment process when we issue (KE) to the customer we still have to do the delivery, posts goods issue and then we can bill. I want to skip the delivery because the items have already been delivered by consignment fill up (KB). Is there a way I can do the billing for customer issue without delivery and still update the inventory and get appropiate accounting/controlling docs.
thx

Consignment Stock Processing
Purpose
Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.
Consignment Fill-Up: Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.
Create a sales order using order type KB.
Enter the required data on the customer, the consignment goods and the delivering plant.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The underlying goods movement type is a stock transfer. This ensures that when goods issue is posted, consignment special stock is created for the customer concerned. If special stock of this kind already exists in the delivering plant for this customer, the goods are posted to this special stock.
Order type: KB (document category C: sales order)
Std. Delivery type: LF
Item category: KBN (not relevant for pricing and billing)
Schedule line category: E1 (relevant for deliveries, uses availability check, 631 (GI consignment: lending) to post the stock into a special consignment category in the delivering plants stock for that particular customer and material)
Copy control rules for the sales doc, item category, and schedule line category.
Use trans MB58 or MMBE to check the stock.
In this case, Accounting document is required to be generated only for taxes, as the stock is still the ownership of the company. In the pricing procedure all condition type except for Taxes should be statistical.
Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.
Create a sales order using order type KE.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The goods are then reduced by the relevant quantity in the special stock assigned to the customer. This goods issue also reduces your total stock.
Invoice the delivery which issues the consignment goods.
Order type: KE (document category C: sales order)
Std. Delivery type: LF
Invoice: F2
Item category: KEN (relevant for pricing and deliver related billing, special stock indicator W, should determine cost too)
Schedule line category: C1 (relevant for deliveries, uses availability check, 633 (GI issue: customer consignment)
In this case, Accounting document is required to be generated only for most of the condition type, as it is being invoiced to end customer.
Consignment returns: proceed as follows: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.
Create a sales order using sales order type CR.
Enter the required data on the customer and the consignment goods.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The goods issue posting cancels the goods issue posting which was carried out when the consignment goods were issued. This posting records the return of the goods to the plant where goods receipt was carried out.
Create a credit memo for the consignment return you created in Step 1.
Order type: KR (document category H: returns)
Delivery type: LR
Credit for Returns Order type: RE (delivery or order related billing)
Item category: KRN (relevant for pricing and deliver related billing, special stock indicator W
Schedule line category: D0 (relevant for deliveries, no availability check, 634
In this case, Accounting document is required to be generated only for most of the condition type, as it is being returned by the customer & invoicing already done to customer..
Consignment Pick-Up: The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.
It may be beneficial to have a mandatory reference such as the consignment fill-up. In addition to it copy control rules can be used to further control it. In the copy control rules indicate the document flow. As the stock is coming back into the warehouse or plant, you can specify a returns shipping point to be automatically determined. No invoice is necessary, as the goods are not changing ownership.
Create a sales order using order type KA.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The transaction is completed by the goods issue posting which initiates a transfer posting from the customer's special stock to your plant stock.
Order type: KA (document category C: sales order)
Delivery type: LR
No invoice
Item category: KAN
Schedule line category: F1 (relevant for deliveries, availability check against the stock on the customers consignment, 632 (Consignment pickup)
In this case, Accounting document is required to be generated only for taxes, as the stock is still the ownership of the company. In the pricing procedure all condition type except for Taxes should be statistical, as the stock is being returned from consignment site to plant.
Regards,
Rajesh Banka
Reward points if helpful.

Error of Excise Invoice in Consignment Issue billing document

The usual process of billing from excisable unit (with CIN) is as follows:
1. VA01 >2. VL01N(PGI)> 3. VF01 (Proforma Inv) --> 4. J1IIN (Excise Inv) --> 5. VF01 (Comm Inv)
While in non-Excisable unit the 3 & 4 steps are not required.
In Consignment Fill-up- The process is only upto Generation of Excise Invoice and order processing is complete. Excise Invoice in this case works as Excise Gate pass- just to let the material out of factory gates and no sales is booked.
Further, In consignment issue- the process should be like non-exciseable unit i.e. 1, 2 & 5 step only. While we are getting the error is coming at step no 5 (Excise Invoice no is missing !)
One more thing I want to ask:
During Consignment fill-up, movement type 631 is used - which removes the stock from storage location and put it in 'Consignment stock in the same plant. Now since the plant is declared as excisabel, probably it is asking for 'Excise invoice'. It means, there is one more step of material movement, before 'Issue' order- what could be it ??
Please help.
Praveen Singh

The correct process in consignment fillup process is
a) Create fillup Order (order type KB)
b) Create fillup Delivery (movement type 631)
c) Create F8 proforma
d) Create Excise Invoice referencing Proforma
a) Create Consignment Issue Order (Order type KE)
b) Create Issue Delivery (movement type 633)
c) Create Commercial Invoice (billing type F2)
In the second stage only, you need to create commercial invoice and not in the first stage as indicated by you.
thanks
G. Lakshmipathi

Problem description: I have ordered a new iMac but my current one seems to be running very slowly. I believe it to be a memory related problem but can't seem to identify what is causing it. Help is greatly appreciated.

Problem description:
I have ordered a new iMac but my current one seems to be running really slowly. I believe it to be a memory related problem but can’t seem to identify what is causing it. Your help is greatly appreciated.
EtreCheck version: 2.1.8 (121)
Report generated March 7, 2015 at 4:01:26 PM PST
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
    iMac (24-inch, Early 2008) (Verified)
    iMac - model: iMac8,1
    1 2.8 GHz Intel Core 2 Duo CPU: 2-core
    2 GB RAM Upgradeable
        BANK 0/DIMM0
            1 GB DDR2 SDRAM 800 MHz ok
        BANK 1/DIMM1
            1 GB DDR2 SDRAM 800 MHz ok
    Bluetooth: Old - Handoff/Airdrop2 not supported
    Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
    ATI Radeon HD 2600 Pro - VRAM: 256 MB
        iMac 1920 x 1200
System Software: ℹ️
    OS X 10.10 (14A389) - Time since boot: 23 days 18:5:35
Disk Information: ℹ️
    ST3320820AS_Q disk0 : (320.07 GB)
        EFI (disk0s1) <not mounted> : 210 MB
        Macintosh HD (disk0s2) / : 319.21 GB (195.05 GB free)
        Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
USB Information: ℹ️
    HP Officejet 6000 E609n
    Apple, Inc. Keyboard Hub
        Primax Electronics Apple Optical USB Mouse
        Apple, Inc Apple Keyboard
    Apple Inc. Built-in iSight
    Western Digital External HDD 500.11 GB
        My Passport (disk1s1) /Volumes/My Passport : 500.11 GB (200.60 GB free)
    Apple Inc. BRCM2046 Hub
        Apple Inc. Bluetooth USB Host Controller
    Apple Computer, Inc. IR Receiver
Gatekeeper: ℹ️
    Mac App Store and identified developers
Kernel Extensions: ℹ️
        /Applications/Popcorn 4/Popcorn.app
    [not loaded]    com.roxio.TDIXController (2.0) [Click for support]
        /System/Library/Extensions
    [not loaded]    com.aliph.driver.jstub (1.1.2 - SDK 10.7) [Click for support]
Problem System Launch Agents: ℹ️
    [killed]    com.apple.accountsd.plist
    [killed]    com.apple.AirPlayUIAgent.plist
    [killed]    com.apple.bird.plist
    [killed]    com.apple.CalendarAgent.plist
    [killed]    com.apple.CallHistoryPluginHelper.plist
    [killed]    com.apple.CallHistorySyncHelper.plist
    [killed]    com.apple.cloudd.plist
    [killed]    com.apple.cmfsyncagent.plist
    [killed]    com.apple.coreservices.appleid.authentication.plist
    [killed]    com.apple.coreservices.uiagent.plist
    [killed]    com.apple.EscrowSecurityAlert.plist
    [killed]    com.apple.nsurlsessiond.plist
    [killed]    com.apple.pluginkit.pkd.plist
    [killed]    com.apple.printtool.agent.plist
    [killed]    com.apple.rcd.plist
    [killed]    com.apple.recentsd.plist
    [killed]    com.apple.sbd.plist
    [killed]    com.apple.scopedbookmarkagent.xpc.plist
    [killed]    com.apple.secd.plist
    [killed]    com.apple.security.cloudkeychainproxy.plist
    [killed]    com.apple.spindump_agent.plist
    [killed]    com.apple.telephonyutilities.callservicesd.plist
    22 processes killed due to memory pressure
Problem System Launch Daemons: ℹ️
    [killed]    com.apple.AssetCacheLocatorService.plist
    [killed]    com.apple.awdd.plist
    [killed]    com.apple.ctkd.plist
    [killed]    com.apple.diagnosticd.plist
    [killed]    com.apple.emond.aslmanager.plist
    [killed]    com.apple.GSSCred.plist
    [killed]    com.apple.icloud.findmydeviced.plist
    [killed]    com.apple.ifdreader.plist
    [killed]    com.apple.nehelper.plist
    [killed]    com.apple.nsurlsessiond.plist
    [killed]    com.apple.periodic-daily.plist
    [killed]    com.apple.periodic-monthly.plist
    [killed]    com.apple.periodic-weekly.plist
    [killed]    com.apple.softwareupdate_download_service.plist
    [killed]    com.apple.softwareupdated.plist
    [killed]    com.apple.spindump.plist
    [killed]    com.apple.tccd.system.plist
    [killed]    com.apple.wdhelper.plist
    [killed]    com.apple.xpc.smd.plist
    [killed]    org.cups.cupsd.plist
    20 processes killed due to memory pressure
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist [Click for support]
    [loaded]    com.sonos.smbbump.plist [Click for support]
User Login Items: ℹ️
    iTunesHelper    UNKNOWN Hidden (missing value)
    Jawbone Updater    Application (/Applications/Jawbone Updater.app)
    Dropbox    Application (/Applications/Dropbox.app)
Internet Plug-ins: ℹ️
    Photo Center Plugin: Version: Photo Center Plugin 1.1.2.2 [Click for support]
    FlashPlayer-10.6: Version: 16.0.0.305 - SDK 10.6 [Click for support]
    Default Browser: Version: 600 - SDK 10.10
    Flash Player: Version: 16.0.0.305 - SDK 10.6 [Click for support]
    QuickTime Plugin: Version: 7.7.3
    OfficeLiveBrowserPlugin: Version: 12.3.6 [Click for support]
    CitrixICAClientPlugIn: Version: 11.2.0 [Click for support]
    iPhotoPhotocast: Version: 7.0
3rd Party Preference Panes: ℹ️
    Citrix Online Plug-in [Click for support]
    Flash Player [Click for support]
    UE Smart Radio [Click for support]
Time Machine: ℹ️
    Auto backup: YES
    Volumes being backed up:
        Macintosh HD: Disk size: 319.21 GB Disk used: 124.16 GB
    Destinations:
        Time Machine Backups [Local]
        Total size: 3.00 TB
        Total number of backups: 98
        Oldest backup: 2013-08-28 05:45:36 +0000
        Last backup: 2014-12-30 19:39:32 +0000
        Size of backup disk: Excellent
            Backup size 3.00 TB > (Disk size 319.21 GB X 3)
Top Processes by CPU: ℹ️
         5%    com.apple.WebKit.Plugin.64
         3%    WindowServer
         2%    sysmond
         0%    AppleSpell
         0%    com.apple.WebKit.Networking
Top Processes by Memory: ℹ️
    41 MB    Finder
    41 MB    iTunes
    37 MB    Safari
    32 MB    com.apple.WebKit.Plugin.64
    32 MB    mds
Virtual Memory Information: ℹ️
    53 MB    Free RAM
    501 MB    Active RAM
    463 MB    Inactive RAM
    398 MB    Wired RAM
    78.46 GB    Page-ins
    3.04 GB    Page-outs
Diagnostics Information: ℹ️
    Mar 7, 2015, 12:41:34 PM    /Library/Logs/DiagnosticReports/Inkjet4_2015-03-07-124134_[redacted].crash
    Mar 5, 2015, 07:42:29 PM    /Library/Logs/DiagnosticReports/com.apple.WebKit.WebContent_2015-03-05-194229_[ redacted].crash

That certainly looks like a low memory issue, 2 GB ram is barely enough to run Mac OS X versions from Lion through Yosemite. The high number of Page Outs and killed processes show very high memory pressure.
Try adding memory, but be sure it is high quality, Mac certified memory such as that from OWC, http://www.macsales.com or Crucial, http://www.crucial.com

Consignment issue - stock related problem

Similar Messages

Maybe you are looking for