Ryan's profile✿ 潜龙勿用PhotosBlogListsMore Tools Help
    July 28

    [转载] 《木兰词 拟古决绝词柬友》纳兰容若

    人生若只如初见,何事秋风悲画扇?
    等闲变却故人心,却道故人心易变。
    骊山语罢清宵半,夜雨霖铃终不怨。
    何如薄幸锦衣儿,比翼连枝当日愿。
     
    [鉴赏]

    词题:这是一首拟古之作。古诗中的《决绝词》,是以女子的口吻控诉薄情郎,从而表示与之决绝。显然这种“闺怨”是一种假托,是纳兰特有隐情的表现。

    两个典故。

    “秋风悲画扇”:借用汉朝班婕妤的故事。她曾是汉成帝的妃子,却遭到赵飞燕的妒忌、馋害而打入冷宫。“妾身似秋扇”,于是就用秋扇比喻被遗弃的女子。

    “骊山”“泪雨零霖”“比翼连枝”:都是讲的唐明皇与杨贵妃的故事。白居易的《长恨歌》已经把这个故事传颂千古了。

    [作者]纳兰性德(1655-1685):清词人。原名成德,字容若,满洲正黄旗人。大学士明珠之子。康熙进士。善骑射,好读书。词以小令见长,多感伤情调,间有雄浑之作。也能诗。
    July 22

    [原创] Tips for SAP rollout project -_-!!

    累死累活写了这么多,不留个纪念貌似对不起消耗的碳水化合物啊。
     
    As per my experience and understanding, following points which I learnt from GFAU rollout may contribute to  a successful rollout project. These points listed below doesn't work as a SD specific guideline, it pretty much may be regarded as experience sharing.
     
    1. Template knowledge transfer and customer customized solution
    As far as I'm concerned, usually we are likely to build up the questionnaires from standard SAP view, but customer maybe have customized many add-ons based on SAP standard functions. So those customer specific solutions, on which should be put more effort for discussion. The more information we get, the easier we can tackle surprises on following phases. Especially for those highly customized system by customer, like GFAU. Both customers and SAP team were bombarded by heavy email communication during realization due to lack of enough global template knowledge.
     
    2. Fit/Gap analysis
    Elaborate the template to local customers, and try to note down their local requirements in detail whatever it makes sense or not. Afterwards, all those information different from template can be translated in to GAP list. From time to time, the point which is ignored on this phase, may be raised again on system realization, as customer sometimes is not quite sure what's their exact requirements. It may involve group discussion from different departments. Finally, double check with local key user to minimize the GAP, and stick to it.
     
    3. Output forms
    The Form format is also a key point for SD. It may involve some of followings in one project, order confirmation, delivery note,  goods issue slip, normal invoice, proforma invoice, credit and debit memo, etc. During GFAU realization, we spent big chuck of time on discussing the layout and testing . So it's better to have customer prepare the format in advance, latter we can spend less time polish the layout.
     
    4. SD customizing list
    During my last project, before the knowledge transfer, I built up a customizing list which contains almost all SAP standard functions used by customer, for example, sales order types, item categories, pricing procedure, partner determination, billing types and output types, etc. Since not all of them can be implemented in China, it speed up the knowledge transfer by marking China relevant items directly in the list instead of navigating in SAP. And it's easier to discuss based on one Excel book.
     
    5. Issue list and report
    From project management point of view, in order to avoid email overload and miscommunication, the approach for issue raise and status report should be discussed and finalized at the beginning. Also it helps to put both customer and SAP team into the same picture.
     
    One more point, it makes more sense to understand customer's business process from his/her point view instead of sticking  to SAP standard solution, which can prevent us from missing some points. That's all what I learnt from my previous project experience. Hope it helps.

    Harvard Business IdeaCast(免费提供)

    本人免费提供Harvard Business IdeaCast mp3格式的音频。

    以下内容是转载di....

    HBR IdeaCast主要关于和管理相关的理念,也有哈佛商业评论(Harvard Business Review)编辑/作者的评论。在第一期IdeaCast里,你甚至可以听到关于中国消费者心理的分析……

    哈佛不愧是哈佛,对新技术的应用不慢。不过按理,整日教书育人的商学院应该是反应最快的:Podcasting可以是一种成本不高而又效果不错的Marketing方式。

    要想知道一所商学院是否好(或者更准确地说,它的Marketing是否强),这或许可以是一个辅助指标:这所商学院开始Podcast了吗?
    July 16

    Talking about 公司间采购简化版

    公司间采购简化版

    关于公司间原料采购的操作方案

    由于新公司的启用,老公司与新公司之间会存在原料互相调拨的情况,为了尽可能的简化业务操作和满足需求,我们建议采用下列操作方法:

    1、 物料移动采用301移动类型(工厂到工厂一步到位法),事务代码MB1B

    举例说明:将物料1200004从1000工厂(老公司)3011库存地转到2000工厂(老公司)3011库存地。执行MB1B,移动类型301,保存后,该物料120004即从1000工厂的3011转移到了2000工厂下的3011库。

    该物料凭证会同时产生二张会计凭证,分别在1000和2000公司代码下,具体凭证如下:

    1000公司(销售物料方)凭证如下:

    借:过渡科目(可自行定义)

    贷:原材料 (成本价)

    2000公司(采购物料方)凭证如下:

    借:原材料

    贷:过渡科目(可自行定义)

    2、 月末财务开具发票,手工编制销售收入和采购业务凭证,当月需开票数可以通过MB51,查询301的移动类型。

    1000公司(销售物料方)出具发票后,编制凭证如下:

    借:应收帐款-关联方(2000公司)

    贷:其他业务收入

    贷:应交税金-销项税

    同时结转其他业务成本

    借:其他业务成本

    贷:过渡科目

    2000公司(采购物料方)收到发票后,编制凭证如下:

    借:过渡科目

    借:应交税金-进项税

    贷:应付帐款-关联方(1000公司)

    借/贷:材料成本差异(如果实际开票价格不等于结转的成本价,最好是指定物料)

    July 15

    Business writing: An internal bad news message.

    Server Restart Notice

     

    Dear colleagues,

     

    We have discovered that the backup tape equipment for our mail server has some problems. (坏消息的邮件起始有个缓冲,而不是直接告诉对方这个消息) For this reason, we will restart the server beginning at 17:15 today. (紧接着给出这个消息) We expect the server to be available again after 18:00. (同时告诉对方可用的具体时间,让对方心中有数)

     

    These repairs to the server will make your Internet email connections more reliable in the future. (告诉对方重启服务器带来的好处,让对方认为这不是无用的工作)

     

    We apologize for the inconvenience. If you have any questions and concerns, please feel free to call me on extension 588. (客气的收尾,让对方感觉到你在负责这件事)

     

    Thank you for your patience and understanding.

     

    Best regards,

     

    Jenny

    July 03

    这个周末可咋过啊~~?!

    这个周末可咋过啊...常熟这个破地方...进次城都要跋山涉水...公司的网络还不能斗地主...郁闷ing
    呃,....想到一个好去处....上海地铁世纪公园....hoho~~~