别看流氓凶，其实流氓比你更害怕

  转:这是在调戏鲁迅先生和他的家人吗?

  在2010年鲁迅论坛的讲台上，陈丹青又来了个冷不防，让台上坐着的和台下坐着的

都不知所措。但这个冷不防真让人提气。下面我就转载陈丹青发言开头的一部分。

主持人：陈丹青发言，他发言的题目是"从鲁迅看文学家、思想家、艺术家的关系

"，大家欢迎。

   陈丹青：大家好！我尽快念，因为我要说一些题外话，可能跟今天的讨论完全没有

关系。所以我临时请（周）令飞原谅，如果我让你为难，请原谅我。

我第一次来贵院参加论坛，非常荣幸，尤其荣幸的是回来十年，这是我第一次被要

求发言稿事先呈交当局审查，审查两个词不好听，他们说是看一看，等于现在警察

局约你训话叫做"喝茶"，非常斯文，非常礼貌。可是文化部官员为什么要事先看一

看，说是将来要出书，好像文化官员成了书刊编辑要出书，自然先要看看。我不知

道这套把戏是刚刚时行，还是很早就时行，是因为讨论鲁迅才要看一看，还是今后

所有论坛发言都要事先看一看，但我愿意相信，今天大家坐在这里开会，诸位学

者、教授都已经事先呈交了，过去五年我曾经应孙宇兄和令飞兄的邀请六次讨论鲁

迅，事先从未被要求要看，后来六篇讲稿都收到书里去，当然要给出版社，出版社

又要给出版署的老爷看一看，看过之后就要删，删没有问题，我们都 很幸福，都

跟鲁迅的命一样，说话、写字随时准备删，可是事后看、事后删和事先就要看一

看，完全两回事，大家知道为了安全起见，我们现在上飞机或者进人民大会堂，先

要所有人全身摸一遍，搜一搜，现在等于脑袋瓜都预先掰开来，把我们党的手电筒

伸进去照一照，看看里面有没有炸药或者打火机，这是新世纪的创举，这个文化部

非常有文化。

大约一周前我先接到主办部门一位女士的电话，要求预审发言稿，当时我在出差中

还没有写，前天令飞兄来短信再次要求提交发言稿，想必主办方急于向上交待，只

好求他，可我仍然一个词还没写，令飞兄说先把提纲发过来以便交差，每次只要鲁

迅先生的长孙有所要求，我都会顺从，当夜写了几行字，发到他邮箱，我的意思是

说倘若不是令飞兄亲自要求，我不会听从任何部门、任何官员，除非我犯法，现在

我很希望知道在座哪位是文化部官员？有没有哪位在这儿？很抱歉，哪位在，没

有，那我就空说了，我非常乐意当面告诉这位官员，你们的上司不觉得这样的做法

多么丢脸吗？你们不觉得这是在调戏鲁迅先生和他的家人吗？你们不觉得这种公然

的卑怯是在直接调戏文化部自己吗？真是能干，你们的上司怎么会想出 这种猥琐

的把戏调戏你们自己，所以这场戏太闹了，我提前相信这种调戏行为远远比今天的

鲁迅论坛更有价值。今年鲁迅先生死去七十四年，在他去世前几年曾在一篇杂文里

提到国民党反动派的审查制度，想将来的子孙不会明白，所以感慨"我们活在这样

的时代"，鲁迅真是老实人，心肠太好，想象力太有限，八十多年后，今天我希望

令飞兄打电话通知鲁迅说："是的，我们活在这样的时代"，这样的时代其实远远胜

过鲁迅的时代，大家同意吗？我们坐在这里，包括鲁迅的亲孙子一起纪念鲁迅、谈

论鲁迅，而所有的讨论事先全部交给文化部哪几个官员看过了，看过了又怎么

样？你们到底怕什么？是怕鲁迅吗？还是害怕坐在这里的书生？我们都很乖的，都

已经裤子脱下来，脑子掰开来，给你摸过、搜过，而且从来就被你们看 管着、豢

养着，怕什么呢？除非是怕鲁迅和刘晓波有什么来往吗？八十多年前，咱们鲁迅早

就一口回绝了诺贝尔奖，八十多年过去你们怎么还在怕？请诸位原谅我不懂事，原

谅我的大惊小怪，我知道此刻我很可能正在冒犯大家，可是我不能容忍这些小动

作，不能容忍自己一声不响、置身事外，目前的当局的种种不得以，我知道、我体

谅，当局的官员都要混口党饭吃，不容易，提前审稿都要算很斯文的，算是一种软

之又软的软势力，但我愿意向鲁迅老人家保证，以后再也不出席这类预先必须看一

看的所谓论坛，再也不冒犯可怜的文化部官员，总之再也不给大家添麻烦。

好了，接下去谈鲁迅，您别客气，时间一到就停，不会占用的。这次是谈鲁迅和艺

术的关系，我想大约说几点：......

路由器设置防QQ登录

    部分同学知道，QQ这款流氓软件会上传你计算机内私有文件清单及监控聊天，你的朋友或家人对此并不知情或在意，在局域网计算机上使用而危胁到你的安全，屏蔽它是有必要的。
    方法其实很简单，以我手头的TP LINK家用路由为例。
    1、建立主机列表。
          如果是局域网内所有机器，视你IP段填写，不可使用*作通配符。常用的是192.168.0.1-192.168.0.254 或是192.168.1.1-192.168.1.254

    2、访问目标
          基本原理是禁止某些主机访问QQ的服务器，一是可以通过域名，二是可以通过IP指名QQ服务器。我选用的是域名。

         域名清单如下：

UDP服务器： sz.tencent.com 端口:8000 IP地址：219.133.49.171
UDP服务器：sz2.tencent.com 端口:8000 IP地址：58.60.14.44
UDP服务器：sz3.tencent.com 端口:8000 IP地址：219.133.60.32
UDP服务器：sz4.tencent.com 端口:8000 IP地址：58.60.14.32
UDP服务器：sz5.tencent.com 端口:8000 IP地址：58.60.14.33
UDP服务器：sz6.tencent.com 端口:8000 IP地址：219.133.60.37
UDP服务器：sz7.tencent.com 端口:8000 IP地址：219.133.48.89
UDP服务器：sz8.tencent.com 端口:8000 IP地址：219.133.40.37
UDP服务器：sz9.tencent.com 端口:8000 IP地址：219.133.60.39

TCP服务器： tcpconn.tencent.com 端口:80 IP地址：219.133.48.103
TCP服务器：tcpconn2.tencent.com 端口:80 IP地址：219.133.38.230
TCP服务器：tcpconn3.tencent.com 端口:80 IP地址：219.133.38.5
TCP服务器：tcpconn4.tencent.com 端口:80 IP地址：58.60.14.45
TCP服务器：tcpconn5.tencent.com 端口:80 IP地址：219.133.49.211
TCP服务器：tcpconn6.tencent.com 端口:80 IP地址：219.133.60.173

VIP服务器：端口:443 IP地址：58.60.9.58
WEB QQ ： 端口:80 web2.qq.com




   3、日程计划
         这步主要是建立一个时间段，因为你也许只是想在特定时间应用你的规则，比如 10-14点之间可以访问某电影服务器。如果你是想在全部时间应用规则，则可以跳过这步。
   4、建立规则
        规则是指定主机列表中的主机，在访问目标时，指定的日程内，可以访问还是禁止访问。这步会用到前三步建立的数据。

好了，通过以上手段，我让老婆只能上WEB QQ，而用客户端没法上QQ了。大伙，千万别和她说噢。

Dependent requirement still remained even I deleted the subcontract PO

Symptom:

Requirement remian unchange after subcontract PO was deleted ( 195650 / 2010 )

Refer to SAP note: Note 115899 - Correction report for subcontractor requirements

Symptom

In the customer system, inconsistencies occur for dependent requirements for subcontracting purchase order proposals (planned orders, purchase requisitions, purchase orders, schedule lines).
This can result from different program errors.
Required is a central report with which these inconsistencies can be discovered and corrected. (AFTER the cause of the error has been found and eliminated!)

You need an OSS account to access this note.If you have create a RFC connection to SAP OSS ,you may use transaction code SNOTE to download and implement it.

Another situation ,when the parent planned order was delete ,the dependent requirements still exist ,please refer to this note :

Note 633119 - Dependent requirements without parent planned order

Summary

Symptom
Dependent requirements (DepReqs) exist in the Stock/Requirements list (MD04) for which no parent planned order exists.
Simulative dependent requirements (DepReqs) exist in the Stock/Requirements list of long-term planning (MS04) for which no parent planned order exists.
Dependent requirements for subcontracting (SubReqs) still appear in the Stock/Requirements list (MD04) after the completion or deletion of the pegged requirements.

These erroneous requirements cause the creation of unnecessary receipt
elements during the planning run.

Other terms
orphaned dependent requirement, missing planned order, deleted planned
order, zombie report, 61003, 61 527, 61527, MD05, MS05, RESB

Reason and Prerequisites
Depending on the particular situation, the problem may be caused by
a handling error in the R/3 system, or possibly by an SAP program error.

Solution
Occurences of this problem generally fall into one of 3 categories:

1. Deleted planned order (for Standard or Simulative DepReqs)
              In this case, the parent planned order has been deleted but the dependent requirement still exists.  The planned order number is displayed in the MRP element data of the dependent requirement, but the planned order itself cannot be displayed or changed.  Attempting to do this generates the error message 61 003, 'Planned order ... does not exist'.

              Solution

              Try to determine the cause of the inconsistency.  How was the parent planned order created/changed/deleted?  Can the problem be reproduced? Then create an OSS message in the component PP-MRP containing all the relevant information.  On analysis of the issue, SAP Support can provide you with an ABAP report to safely remove the erroneous dependent requirements.

2. Reprocessing record from REM (Repetitive Manufacturing) backflush (for Standard DepReqs)
              In this case, no planned order number is displayed in the MRP element data of the dependent requirement.  Instead, the string 'NProc' is displayed.  This means that the dependent requirement is a reprocessing record for a goods movement that failed during an REM backflush.

              Solution

              These reprocessing records can be processed (removed) using transaction MF47 or COGI (see note 61144.)  If these transactions cannot locate the reprocessing records, they can be removed by following the instructions in note 95307.

3. Completed/deleted pegged requirements (for SubReqs)
              There is a possibility that a program error exists which has caused the inconsistency in this case.

              Solution

              If such requirements appear in your system for which no pegged requirements exist, you should consult note 128061. This is a collective note which lists any corrective notes currently existing in this regard.  You should apply any corrective notes that could be related to the problem and are valid for your current release and patch level.  Then create an OSS message in the component PP-MRP, outlining the problem in detail and listing any notes that have been applied.  At that point, SAP Support can provide you with an ABAP report to remove any outstanding erroneous requirements.



Good luck .

SAP特殊获取类型 Special procurement

IMG: OPPQ Maintain master data - > Special procurement .
设置栏位解释：
Direct Procurement 直接获取

message raised:Document is not valid on explosion date when create production order.

When you create a production order you got a  warring message：

****************************************
Document: T-22720,
Document part: 000,
Version: 00
is not valid on explosion date.
No further valid versions are available. Should
the document link be transferred anyway?

Choose yes or no.
****************************************



We can found some useful information ,it  seems relate to DMS (document manage system) .

First ,find out the material number which  you want to create production order .then go to MM02 - additional data - document data
you will found a document link to this material ,e.g ,document number T-22720 ,document type DES so on .
According to previous information ,we knew the warring message is cause by the document valid date ,so we have 2 choice:
1、release this document .(use CV02N)
2、remove the link between material and document .(MM02 - additional data - document data)

SAP Mvt 309 transfer posting material to material

Test purpose : test if the issuing material and receipting material must have the same stock keeping unit (SKU) or you can't make a posting.
material : 000100062R  Basic Unit :KG   10M = 1 KG

material : 000110003R  Basic Unit :M    100G =  1 M

Transfer material 000110003R 1M to 000100062R

When posting,system respond :

Stockkeeping units M and KG differ

Message no. M7105

Diagnosis

The "receiving" material is not managed in the same stockkeeping unit as the "issuing" material. A transfer posting "material to material" is only possible if both materials are managed in the same stockkeeping unit.

Procedure

Enter a different material or terminate processing.

Date comes after end of valid factory calendar

    When you use transaction code MD04 to check the stock/requirement list ,you got this SAP error message:

e.g : 2015/1/4 date comes after end of valid factory calendar .

Correct:

1. Extend the factory calendar . (TC: SCAL)
2. Change the plan horizon ,ensure the horizon days is less than the days between current date and the end of valid factory calendar.(I have no reason,I think SAP use different logic to process the demand out and in of a horizon )
3. Change the Lot-size of thematerial ,almost is cause by a WB or similar lot-size types . I think cause a WEEK lot-size will cross a month or 1 year ,for example the first week of 2015 include 2014's last 3 days and  Jan 1st and Jan 4th of 2015 . So if you change the lot-size to day or month Lot-size this issue will be solved ,cause they never cross a month or a year .(MM02)

SAP发票价格与PO价格不一致时如何更新库存价值及移动平均价

测试步骤：

1、物料：000130016  工厂3000 供应商：D0992  当前无库存

2、对PO收货100PC，移动类型101 PO: 6111000021，订单价格3.74元 ，库存总值为374元。  

3、发料90PC. 发货值：336.30元    库存剩余值：37.4 数量10PC

3、发票，给出不同于收货的价格,总价值1000元，无税，发票过账后的会计分录为：

  借： 应付账款-供应商XX  1000

              贷：原材料  62.6

                  GR/IR   374

                  差异科目  563.4

目的：测试价格差异是否只记录10PC的库存价值变化，其余差异全部进入差异科目。

此时,物料主数据中MAP为：10，库存总值更新为100元。

在此过程中，每PC原材料价格相当于增加了10-3.74=6.26，由于库存只有10PC,故原材料增加库存价格为6.26*10=62.6,其他90PC的总差异为：90*（10-3.74）=563.4

测试表明，当发票价格与PO价格不一致时，如果库存数量小于原始发票数量时，价格差异只更新相应数量的库存，其余部分全部进入差异科目。