SAP Those Things - Theory -11-SAP Core design logic

SAP Those Things - Theory -11-SAP Core design logic

This article I think is the most important one in the theory, we have to learn anything, if we grasp the essence, then we may get twice the result with half the effort, nvidia partner if we only study the details, or even put the cart before the horse, then we will get half the result with twice the effort. Through this article, I hope we can grasp the core design logic of SAP together, and strive to let us understand SAP and learn SAP can get twice the result with half the effort! So what are some aspects of SAP's core design logic? Let's take a look.

1. Object-oriented design

This is a design concept that has been commonly used in computer programming since the 1970s. Object can be understood as all the objective things that can be perceived. SAP Outsourcing As an object, object first has attributes (attributes are the characteristics of this object), and its most important attributes can be called essential characteristics. At the same time, the object can also be classified, for example, the most typical is the classification of organisms, is the realm, phylum, class, order, family, genus, species, such as humans belong to the animal kingdom, chordate, mammalia, primates, Hominidae, Homo genus, Homo sapiens. The essential feature of an object is the attribute used to distinguish it from other objects, that is to say, we can know the object referred to through this essential feature and will not be confused with other objects. The attribute of an object is used for us to understand the object. The state of an object changes with the change of its attribute, or its attribute is different in a certain state. That is, objects and properties and states interact. Take a chair as an example, it belongs to a class of furniture, its properties have material, weight, price and so on. We can modify the properties or state of the object through the operation of the object, for example, we can change the chair into another style through processing, after processing the state of the chair has changed, and the properties have also changed. Let's take a look at these concepts of objects from the objective world and apply them to SAP systems.

Firstly, in the SAP system, various business objects are classified. The highest level of Object classification is Object Category. smart waste management Take the category of orders as an example, for example, the category of internal orders is 1, and the category of production orders is 10. Under the Object category is the Object Type, for example, production orders can be divided into normal production orders, rework production orders and other different types. In SAP, object classes can not be configured, object types can be configured, which ensures the unity of rigor and flexibility. SAP also uses the state (state parameter file) to control the operation that can be performed on an object. You can use the transaction code BS02 to view the corresponding state and allowed operations of the state parameter file (which can be assigned to the object). Use the Transaction code BS12 to view the Business transactions allowed by the object class (i.e. Business Transaction, business transaction corresponds to operation, foreground operation will be specified by SAP in the background a business transaction, used to distinguish different operations performed on the same object, this concept is used in each module. For example, there are CO business things in the CO module, OKC1 can view; Use the transaction code BS22 to view the business transactions allowed in a certain state; Use the transaction code BS32 to see the allowed state of a business transaction. Is it a little convoluted? It's okay. Let's clean it up again. Corresponding to objects in the real world, we will change the state of the chair through certain operations (such as reprocessing the chair, painting it, or shape changes), right? In turn, the state of the chair will also limit our further processing of it, for example, it has been painted, then obviously under normal circumstances can not be cut, right? Because cutting will destroy the paint already applied. From the perspective of SAP, we process an object, take the production order as an example, release the production order (state change), then the production order will allow subsequent operations, such as reporting, feeding, etc., right? In turn, the change of the status of the order after reporting the work (it can be automatically changed in a certain situation, or it can be manually marked, for example, the DLV status of the production order will be automatically marked according to whether the delivery is sufficient, while TECO can be manually marked), and it will also restrict the subsequent operations, for example, the production order has been marked with TECO, then it is not allowed to feed, report and receive the goods. It is understood that the interaction and diversion between state and permitted business things keeps the business moving forward. That is to say, an object will allow all operations related to this object (this is limited by the underlying code of SAP, although it can be changed, for example, BS12 can forcibly modify the production order as the receiver of the cost center, but we do not recommend), for example, the production order can perform the business of product warehousing, but the internal order is not allowed. This is determined by the object class and, more precisely, by the business things allowed by the business objects in BS12. As the state of this object changes (the state is affected or changed by business things, i.e. foreground operations), the business things it can manipulate also change. In summary, at the beginning, the category of the object determines that all possible operations can be carried out, and the operations change the state of the object, and the state of the object further affects the operations that can be carried out (allowed business things). As the object gets closer and closer to the end state, the operations can be less and less, and finally the object completes. All operations are finished (for example, the production order flag deletes the state DELE, at which point no operations are allowed and it is time to prepare for archiving).

2. Modular development.

People who have engaged in software design and development know that the more complex the software, the more need to be developed by modules, each module to achieve specific functions, and then through the interface between the modules to interact with each other, this time the interface between the modules is very important, the interface should first consider a variety of possible situations, including forward and reverse, The second is to consider what data needs to be transferred between modules and whether it needs to be integrated (merged, split, etc.). In addition, it is also necessary to consider how to determine the data of another module based on the data of one module, such as what the business determines the accounting subject is the most familiar case.

3. Integrated design.

Although sub-module development and design, but the overall architecture is to be designed as a whole, that is to say, we must first think about the overall function and the data interaction between modules and content, and then sub-module development, rather than reverse.

As we all know, there are two kinds of logical thinking methods of human beings. One is based on induction (classification is an important manifestation). Various things or phenomena in the world can be classified and rules can be found through classification. One is based on inference or deduction, which is to deduce from one conclusion to another. SAP also fully embodies such thinking methods and design ideas. Its overall architecture is based on induction and classification (classifying objects, object types and object categories, and giving different functions and definitions to represent or execute different businesses), while its system processes and operations are based on logic and reasoning. For example, the sum of parts is not allowed to be greater than the whole. All kinds of operations and logical symbols and all kinds of business logic check applications are the embodiment of logical reasoning. Mathematics is the embodiment of these two ways of thinking. Interested students can go to see what objects are in SAP, those object types, which object categories, and when you have summarized clearly, the core design logic of SAP is clear!