世界上有这么一种人,似乎特别得到老天爷的偏爱——他总是有自己的理想,并且总是努力去做,最重要的是,老天爷每一次都会帮他取得成功。
是不是很令人羡慕?其实,我一直以为,与其说每个人有自己的命盘,人生各不相同,倒不如说我们自己打造了自己别样的人生。
内心的强大,才可能让我们的生活是丰实而非空洞的;生活的丰实,才可能让我们的人生是精彩而非轻佻的。前面有一次文章中,我说过,一个幸福的愿望可以得到全世界的协助。内心的强大正帮助你积聚来自外界的能量的前提。试问,一个内心空虚乏物的人,如何凝聚力量来实现自己的愿望?
内心的强大,是内心的安定与平静。强大,不是霸道,不是要将别人的所有占为己有,恰恰相反,内心的强大带给我们的是宽容和谦让。正是因为内心的安定与平静,我们才明白自己真正需要什么,才明白如何才能得到快乐。
内心的强大,是不纠缠、不羁绊的状态。所谓“心轻上天堂”,就是说无牵无挂、不计较、不被琐事烦扰的心灵才可以接近天堂。
内心的强大,是对未来充满希望。当我们内心强大到可以战胜一切恐惧与悲观的时候,其实已经无所谓希望了,因为我们在哪儿,希望就在哪儿。
内心的强大,是人生目标的清晰。因为清晰,所以我们可以坚定地走下去;因为清晰,我们才不会跌跌撞撞却不知身在何方;因为清晰,我们才可以知道什么是对的,什么是错的。
那么,怎么做,才可以让自己的内心强大起来呢?
我们前面已经讲过,如何接纳自己、激励自己,如何拥有积极的心态。这些都是拥有强大的内心的前提。
我们还谈过自强、聊过成功的意义,这些都是在帮助你澄清自己的人生观,价值观。
我们还介绍过调节情绪、拥有行动力的很多方法,这样的生活比较阳光,比较健康。如果真的照我的建议去做了,就可以感受到更多的来自内心的力量。
过去讲了很多针对问题本身很具体的办法,但是这一次,很抱歉,我没有办法告诉你,如果想让自己的内心强大起来,第一步应该怎么做,第二步应该怎么做,很抱歉,我不能告诉你。
在这个过程里,更多的是我们对自己生活的探索。没有固定的线路和模式。也许需要付出比别人更多的经历和时间,那又有什么关系呢?
重要的是,你必须学会主动地澄清你自己内心的真实想法。不要用世俗的标准去衡量它们。不要给他们标记上“对”或者“错”。你必须看清楚它们究竟是什么。如果你听到自己的心说“我要挣大钱”,也不必觉得难以启齿。在你的道德标准范围内,你的任何想法都完全可以心安理得。
你应该做的,只是让他们变得明朗化。不要让内心积聚太多的冲突。
也许有的时候,你根本不知道自己的目标是什么。没有关系,你需要的,也许正是这样一段期间里的无欲无求。纵使不是无欲无求,也不用觉得懊恼,我们生活的过程正是不断澄清自己的过程。生命的使命之一就在于认识我们自己。即使现在我们还是困惑之中,也是不要紧的。这是我们生命的过程。
生命不仅仅是一个等待的过程。不要让自己在等待自由,等待明天的过程里慢慢地衰竭掉。你可以做的事情其实很多。不要让生活的平淡把你的内心也变得空洞起来。也许我们暂时无法左右我们的生活,但是我们的内心就在我们自己的躯体里面。屋子可以是黑漆漆的,但是我们的内心依旧可以光亮。
我们也许会暂时变得一无所有。空空的手心并不意味着空空的内心。卷土重来的英雄故事我们听得太多了。一切只关乎内心的强大。在文章的开篇,我们提到世界上有这么一种人,似乎特别得到老天爷的偏爱,他们可以得到他们想要的一切。但是你看到没有,他们都有着强大的内心。
你可以苦闷、可以失落,但是你不可以内心空虚。你必须明白,环境是什么并不重要,记得让自己的内心强大起来。
2009年1月15日星期四
Purchase to Pay Process Overview
One essential business process is the purchase of goods that will be presented hereas the complex process Purchase to Pay in order to explain the most inportanttransactions in Accounting.
Purchase order handling: When you create purchase orders, the system providesyou with tools to help you enter the data. The required entry data such as supplier,material, plant and other data relevant to the organization of purchasing must beprovided. The purchaser can supervise the processing status of the order in thesystem. He can define, for example, whether a goods receipt or an invoice hasbeen executed for the respective order position. The system also supports dunning.This procedure runs exclusively in Materials Management. No postings are madein Financial Accounting.
When goods are received, the system checks, among other things, the quantityof goods received against the order quantity. A material document is createdin Materials Management to update the stock. At the same time, a document iscreated in Financial Accounting to post the evaluated goods to the material stockaccount or the consumption account (debit) and to a goods receipt / invoice receiptaccount (credit).
After the invoice has been received in the Invoice Verification, the VendorInvoice is checked as to the correctness of computation and content. All of thesepurchasing processes are handled by the Logistics components of the SAP system.
The vendor invoice is posted in Materials Management and, at the same time, adocument is created in Financial Accounting to post the invoice amount to thegoods receipt / invoice receipt account (debit) and the vendor account (credit). Thegoods receipt / invoice receipt account is used to make sure that a goods receipt isexecuted for every invoice and vice versa.
The Payment Processing usually takes place in Financial Accounting. It is herethat decisions are made about the payment process, such as, for example, thepayment methods and the bank settlement.
Purchase order handling: When you create purchase orders, the system providesyou with tools to help you enter the data. The required entry data such as supplier,material, plant and other data relevant to the organization of purchasing must beprovided. The purchaser can supervise the processing status of the order in thesystem. He can define, for example, whether a goods receipt or an invoice hasbeen executed for the respective order position. The system also supports dunning.This procedure runs exclusively in Materials Management. No postings are madein Financial Accounting.
When goods are received, the system checks, among other things, the quantityof goods received against the order quantity. A material document is createdin Materials Management to update the stock. At the same time, a document iscreated in Financial Accounting to post the evaluated goods to the material stockaccount or the consumption account (debit) and to a goods receipt / invoice receiptaccount (credit).
After the invoice has been received in the Invoice Verification, the VendorInvoice is checked as to the correctness of computation and content. All of thesepurchasing processes are handled by the Logistics components of the SAP system.
The vendor invoice is posted in Materials Management and, at the same time, adocument is created in Financial Accounting to post the invoice amount to thegoods receipt / invoice receipt account (debit) and the vendor account (credit). Thegoods receipt / invoice receipt account is used to make sure that a goods receipt isexecuted for every invoice and vice versa.
The Payment Processing usually takes place in Financial Accounting. It is herethat decisions are made about the payment process, such as, for example, thepayment methods and the bank settlement.
2009年1月10日星期六
BCT激活
BCT激活
向前的数据,手动安装,清单, 选择cube进行安装,带出其他对应当ods、info object、transfer/update rule。
如果出现数据源不能安装,可能是ECC中没有激活,用RSA5激活数据源,用比较数据源查看是否已经安装,如果已经安装能在RSA6中看到~
然后复制数据源,如果遇到不能安装的问题,可能是Infoobject与transfer rule有冲突,需要删除传输规则/更新规则再次安装~
安装后测试数据,首先测试主数据,然后测试业务数据。
主数据测试过程,首先加载属性数据,然后文字数据,最后层次。
如果有错误,检查transfer rule与info object的数据是否匹配,不匹配则修改。
向前的数据,手动安装,清单, 选择cube进行安装,带出其他对应当ods、info object、transfer/update rule。
如果出现数据源不能安装,可能是ECC中没有激活,用RSA5激活数据源,用比较数据源查看是否已经安装,如果已经安装能在RSA6中看到~
然后复制数据源,如果遇到不能安装的问题,可能是Infoobject与transfer rule有冲突,需要删除传输规则/更新规则再次安装~
安装后测试数据,首先测试主数据,然后测试业务数据。
主数据测试过程,首先加载属性数据,然后文字数据,最后层次。
如果有错误,检查transfer rule与info object的数据是否匹配,不匹配则修改。
2009年1月9日星期五
Match(x) and Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
Example of an automatic match
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if
¡ the match indicator is not set and
¡ the install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
...
a. Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
b. Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties which are taken into account when versions are matched are now listed.
....
With the most important object types, the active version and the SAP delivery version can be matched.
From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
Example of an automatic match
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if
¡ the match indicator is not set and
¡ the install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
...
a. Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
b. Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties which are taken into account when versions are matched are now listed.
....
2009年1月8日星期四
创建BAPI
新建BAPI
一.建立Function Module
Step 1: Define a Structure for BAPI
In this step structures for the parameters and tables of the function module used for the BAPI are defined.
USE T CODE : SE11 then Data type -> Structure
Define the structure Name : Ex: ZVEND
Important note:
You will have to define a structure for every parameter in the BAPI. You cannot use the same structures used in existing applications because BAPI structures are frozen when BAPIS are released and then there are restrictions on changing them.
Step 2:Define a Function Group
USE T CODE: SE80 to create a Function Group
note:
一个Function Group只能包含一个BAPI;参数传值;必须有有一个BAPIRETURN类型的EXPORT参数
Step 3:Define a Function Module
USE T CODE: SE37 to create a Function Module
note: Function Module就是具体执行的代码
二.封装
1,在SWO1,建Object Type
2,把Function Module作为一个Method加入,utilities->API Methods->Add Method
3,编辑->更改状态,release Object和Module。使在BAPI Browser 中可以看到。也就是外部能够调用。
一.建立Function Module
Step 1: Define a Structure for BAPI
In this step structures for the parameters and tables of the function module used for the BAPI are defined.
USE T CODE : SE11 then Data type -> Structure
Define the structure Name : Ex: ZVEND
Important note:
You will have to define a structure for every parameter in the BAPI. You cannot use the same structures used in existing applications because BAPI structures are frozen when BAPIS are released and then there are restrictions on changing them.
Step 2:Define a Function Group
USE T CODE: SE80 to create a Function Group
note:
一个Function Group只能包含一个BAPI;参数传值;必须有有一个BAPIRETURN类型的EXPORT参数
Step 3:Define a Function Module
USE T CODE: SE37 to create a Function Module
note: Function Module就是具体执行的代码
二.封装
1,在SWO1,建Object Type
2,把Function Module作为一个Method加入,utilities->API Methods->Add Method
3,编辑->更改状态,release Object和Module。使在BAPI Browser 中可以看到。也就是外部能够调用。
订阅:
博文 (Atom)
