|
|
马上注册,结交更多好友,享用更多功能,让你轻松玩转社区。如果您注册时有任何问题请联系客服QQ: 83569622 。
您需要 登录 才可以下载或查看,没有帐号?注册
x
我觉得这段讲的很清楚了
An order has its own life cycle, which begins when you create it and ends after you close it. During this time, different things happen to an order, for example, costs are planned, posted, and settled. Status management informs you that a particular phase in the order life cycle has been reached and determines which business transactions are valid for an order at any given time.
|
| | | The standard R/3 System includes four system status settings: Created, Released, Technically Complete,and Closed. The system status allows only certain business transactions, for example, you cannot post actual costs in the Created phase. Changing the status of an overhead order is itself a business transaction and is done on the order master record. |
| | | If the status settings in the standard system are not detailed enough, you can create user-defined status indicators for further subdivisions. The system and user status settings determine whether a business transaction is valid. A status can: |
| | | | | Allow a business transaction |
| | | | | Allow a business transaction with a warning |
| | | | | Prohibit a business transaction |
| | | For example, you may want to switch to a planning approval procedure for high value orders before they are released. The initial system status of Created allows the release transaction. To restrict this, you could create as your initial user status an Unapproved setting that prohibits releasing the order. A system/user status combination of Created, Approved would be required before the order could be released and have actual costs posted to it. |
| | | You can also define field selections, that are status-dependent, and authorizations for your user status settings. The first allows you to control master data field maintenance during the order life cycle. The second allows you to define which users are allowed to process business transactions at different points in the life cycle.
how to define user-defined status:
| | You define user statuses and associated rules in a status profile, then assign the profile to your order type. |
| | | The status profile allows you to: |
| | | | | | | | | | Assign a sequence to your statuses |
| | | | | | Define an initial status, which is automatically set when an order is created |
| | | | | | Determine that a user status is automatically set during the execution of a business transaction |
| | | | | | Allow or forbid specific transactions |
| | | The status number assigns the sequence for the user statuses in a status profile. You can have only one user status with an active status number at a time. If you assign a status number to a user status, you also specify a lowest and highest status number, which controls the subsequent user statuses. For example, if the current status number is 20, and the highest status number is 40, you can update the order status to either 30 or 40, but not to 50. |
| | | Defining a status number for a user status is not required. A user status that does not have a status number can be activated or deactivated at any time, regardless of whether other user statuses are already active |
|
|
|
该贴已经同步到 xiaoerp的微博 |
|