1-logistics-general下载

weixin_39820535 2019-09-10 09:30:21

customers and within your company You can create sales activity output for example customer telephone calls mailing campaigns and group output for
example freight lists Your company employees can send and receive output Output is directly linked to the corresponding sales transaction for
相关下载链接：//download.csdn.net/download/zrpssh/8104933?utm_source=bbsseo

...全文

18 回复打赏收藏转发到动态举报

写回复

回复

切换为时间正序

请发表友善的回复…

发表回复

customers and within your company You can create sales activity output for example customer telephone calls mailing campaigns and group output for example freight lists Your company employees can send and receive output Output is directly linked to the corresponding sales transaction for example the system automatically sends an order confirmation via Electronic Data Interchange EDI as soon as the employee creates an order ">customers and within your company You can create sales activity output for example customer telephone calls mailing campaigns and group output for example freight lists Your company employees can send and receive output Output is directly linked to the corresponding sales transaction for [更多]

Abstract—Based on demands in proxy pattern, this article proposes informatization solution of proxy pattern which includes enterprise management, proxy management, franchisee management and supply chain management, then discusses basic functions, system architecture of the platform as well as metadata services, security strategies, and finally gives a multi-user data model -shared database, shared architecture. Keywords-Proxy Pattern; Informatization; Multi-User Data Model I. INTRODUCTION SaaS is the abbreviation of software as a service. It is a brand innovative software application pattern which starts in the 21st century along with the development and application of Internet technology. Through providing the software services over the Internet, manufactures deploy the application software on his own server, while the user customizes the services over the Internet according to the actual demand, at the same time defrays the expense according to the kind and hours of service used. What is a proxy pattern? It refers to that someone obtains the sale proxy of production enterprise or purchase proxy of users through a form of contract, and gets the commission after finishing the transaction [1]. Generally speaking, it is suitable for a new market or marketing of specialized product, such as jewelry industry, they always need special supply chain management, technology and local market, some requirements should be possessed by distributor. But it is not easy to find such one, so using a proxy pattern and establishing a proxy service center is very useful to open the target market rapidly, meanwhile fully control the logistics of both supply and demand, as shown in Figure 1: Figure 1. Proxy pattern service schema As a public service platform of the supply chain, the proxy service center is an extremely important intermediate link. On one hand, it enables every enterprise in each link of the proxy pattern to be a node in the supply chain network; on the other hand it realizes the exchange and sharing of data, information and knowledge among supply, product, and sales enterprises. The proxy service center which carries on the product logistics between supplier and franchisee has a function of managing retailers and franchisees. So this pattern can grasps the supply condition quickly, control the logistics flexibly. At present, there are already relatively mature networks in many industries. Therefore, it has a very vital practical significance to promote the informatization platform based on the proxy pattern. II. FUNCTION STUDIES OF INFORMATIZATION PLATFORM The proxy pattern informatization mainly provides a stable, completely functional service platform which integrates application systems configuring on the unified service architecture. The service vendor who is responsible for maintenance and management of the software provides the software service over the Internet for users. Users need not purchase, construct and maintain infrastructure and the application procedure. According to informatization demands in proxy industry, functions of this platform includes enterprise informatization, franchisee informatization, proxy service center informatization, supply chain informatization and SaaS website service, which is shown in Figure 2: Figure 2. Proxy pattern informatization platform A. Enterprise informatization Enterprise informatization will be realized in this module which is mainly composed of general information management systems and management information systems for specific industry. The former includes OA system, personnel management system, attendance system, human resources management system and financial system .etc; the latter are suitable for the different industries, such as production management, workshop management, inventory management etc. Each system can realize seamless integration through web services; users in different industries can customize a combination of modules, share the synthesis statistical report, and establish basic data set .etc. This has fully manifested the superiorities of the SaaS application, which not only meets individual demands of various enterprises, but also makes these enterprises to be a link in the industry chain as well as realize its own informatization. Thus, every enterprise can share the information in upstream and downstream which is a great advantage for enterprise development. B. Proxy service center informatization As one important part of the informatization platform, the proxy service center carries on the product logistics between suppliers and franchisees. The realization of proxy pattern informatization may break the phenomenon of information island, which makes the proxy service center to be an important information channel on the entire industrial chain, thus it is more advantageous for information communication and sharing among enterprises. Informatization management for the proxy service center includes functions like statistics, inquiry, finance, user management. The center requires comprehensive statistic and inquire abilities, so as to fully grasp upstream and downstream information of the industrial chain. C. Franchisee service informatization Under the proxy pattern, franchisee manages one or several brands through the proxy service center, technically accepts the instruction of the brands, and engages in the operating activities according to the business pattern in the contract. As a different from branch business, franchisee has independent operation system and informatization platform. Informatization management for franchisee will be realized in this module, which includes functions like inventory, statistics, sales, finance .etc. So it not only realizes franchisee informatization service, but integrates franchisees into the industry informatization process. D. SaaS website service SaaS website service is a show window of service vendor and a communication channel of users, through which users submit their informatization demands. After satisfying the demand of users, the supplier gives feedback to users, so as to interact with user on line. Functions like company introduction, product synopsis, informatization diagnosis, product experience, service support will be included in this module. III. SYSTEM ARCHITECTURE Above we discuss the basic functions of informatization platform in proxy industry, the remainder of this article will detail the system architecture that can help us plan and build SaaS application. A well-designed SaaS application is distinguished by three qualities: scalability, configurability, and multi-user efficiency [2]. • Scalability, which is maximum enhancing concurrency, so as to high-efficiently use the application resources. • Configurability, refers to that each user can configure appearance and behaviors of the application with metadata, simultaneously guarantees easy use of the configuration and no expense. • Multi-user efficiency, this requires an architecture that maximizes the sharing of resources across users, but that is still able to differentiate data belonging to different users [3]. In a SaaS application, keys to determine these characteristics are metadata service and data security service, which are also the focus of users [4]. Neither can a common B/S architecture guarantee the data security of users, nor can satisfy flexible business requirement. Therefore, this article proposes the following SaaS platform system architecture based on proxy pattern, as Figure 3 shows: Figure 3. SaaS system architecture under proxy pattern In this architecture, the service vendor hosts multiple users on a load-balanced farm of identical instances (SCM instance, ERP instance, franchisee instance, agent instance etc.) with the same code library. Each instance serves for a certain amount of users with different demands, and with configurable metadata providing a unique user experience and feature set for each user [5]. Identical instances can maximize resource sharing. From users’ perspectives, the application is used as usual. As a unified interface of users, the load-balanced server will be responsible to manage these application instances. SaaS can meet various kinds of service requirement changes as well as behavior differences of business logic, which is realized mainly through metadata services. Configurable and customizable of the metadata make the platform highly scalable. According to his own business process, the user can define his fields, menu, form of report, formulas, jurisdiction, views, workflow and business rules, customize kinds of service for him, thus fully meet enterprises' individual demands and realize fast response to demand changes. The security service is most important in SaaS architecture, which is specially concerned by users. From user access to security data itself, we give a solution through authentication, authorization and means of hybrid encryption. In order to realize logon security, we want to consider a hybrid approach that combines centralized and decentralized authentication system—using the centralized approach to authenticate and manage smaller users, and the federated approach for large enterprises that demand, and will pay for, the single sign-on experience [6]. After the user logs on, access to resources and business functions in a SaaS application is managed by using roles that map to specific job functions within an organization. Each role is given one or more permission that enable users assigned to the role to perform actions in accordance with any relevant business rules, roles are managed within the SaaS application itself; they can contain individual user accounts, as well as user groups. Individual user accounts and groups can be assigned several different roles as required [7]. When the user access data resources, we have another protection—data encryption. A key wrapping system that combines the advantages of symmetric and asymmetric methods is used in this platform. Three keys are created for each user as part of the provisioning process: a symmetric key and an asymmetric key pair consisting of a public key and a private key. The symmetric key is used to encrypt the user's critical data for storage [8].A asymmetric key pair is used to encrypt and decrypt the symmetric key, so as to add another layer of security. IV. MULTI-USER DATA MODEL The multi-user data model is a very important link in SaaS platform design. A good data model has a good scalability, can share the data and information well, and satisfy the users’ individual needs. The simplest data model is storing users’ data in separate databases. Computing resources and application code are generally shared between all the users on a server, but each user has its own set of data that remains logically isolated from data that belongs to all other users[7].This model makes it easy to extend the application’s data model to meet all users’ individual needs, and restoring a user’s data from backups in a failure is a relatively simple thing[9].But usually this model expands software and hardware investment and equipment maintenance cost, which is similar to traditional single user model. The second data model is shared database, separate schema in which houses multiple users in the same database, with each user having his own set of tables that are grouped into a schema created specifically for the user. Each user can use SQL statement to operate his own data table [10]. This model can guarantee logic independence and security of users’ data, while it will increase complexity to backup and restoring of the data. In order to solve the problem of two kinds mentioned above, shared database, shared schema will be used in our platform based on standardization, unification in proxy industry, in which the same database and the same set of tables are used to host multiple users’ data. Different users’ data are stored in the same table, and distinguished by different UserID. This approach has the lowest hardware and backup costs, but it has the highest sharing, because it allows you to serve the largest number of users per database server. Some proxy industry like jewelry, there are so many nodes (they are almost small and medium-sized enterprises) that we can obtain considerable clients if we can effectively guarantee data security which is the key issue of SaaS application. What is more important, the shared schema ensures logic independence of users’ data, fully share and use all users’ data resources, is advantageous to integrate entire operation process in proxy pattern; on the other hand, different enterprises with the same service may have a different business requirement, they can flexibly extend the data model according to their own demands. Now we will discuss how to realize the extension of the data model. Generally speaking, there are two schemes: reallocated fields and Name-Value pairs [11]. Reallocated fields was used to reserve some fields in advance for user extension, when new requirement was put forward, we use one field or several fields to storage extension data [12].This scheme well realizes scalability of the data to some extent, but how many fields are reallocated at last is a problem hard to control for a large number of clients in SaaS application, while this problem is decided in scheme design. So we give up this scheme, and use Name-Value pairs to realize data extension, as shown in Figure 4: Figure 4. Name-Value pairs for Multi-User data model The scheme Name-Value pairs separate the data for extension with original data table, the extension data is stored in a unified extension table which changes transverse column of the extension table for longitudinal data sets, each extension field of original data record is stored by one extension data line, then we associate the record in original data table with the record in configuration table. Thus, extension data records are formed [13]. We will store users’ data in original data table, which contains only RecordID in the form record of the default data model, the only RecordID corresponds with one line or several lines in configuration table. A user can create records in configuration table as many as possible according to the business needs, which associate the extension table through ConfigID; then customized field values will be stored in extension table, and the table is consistent with the main data table through UserID. The scheme above allows each user to create as many custom fields as necessary so as to fully meet its diversified business needs, and it won’t waste too much storage space. V. CONCLUSIONS At present, SaaS application is vigorously promoted in many industries which can save the cost for the users, reduce the risk, and speed up the informatization process of the entire industry. Based on the informatization demands in proxy industry, this article expands SaaS application from the common management software to informatization of the entire industry, proposes basic function and the multi-user system architecture of the SaaS platform under the proxy pattern, then designs multi-user data model as well as data security services which makes the data achieve a good sharing and scalability, and effectively guarantees the data security. REFERENCES [1] Liyun Feng, Distribution Channel Management, Economy & Management Publishing House, Beijing, 2002. [2] Frederick Chong, and Gianpaolo Carraro Roger Wolter, Multi-Tenant Data Architecture, Microsoft Corporation, Washington, June 2006. [3] Wenbin Yu, Xiaohui Huang, and Min Yu,”A Solution of Shared Database and Architecture’s SaaS Based on XML”, Computer and Modernization, 8-10, April 2008. [4] Zongzuo Chang, Yue Xu, and Gang Dai,” The multi-tenant data architecture study based on the SaaS model for the public service platform”, Computer Systems and Application, 7-11, Feb. 2008. [5] Zongzuo Chang, Yue Xu, and Gang Dai,” The multi-tenant data architecture study based on the SaaS model for the public service platform”, Computer Systems and Application, 7-11, Feb. 2008. [6] Frederick Chong, and Gianpaolo Carraro Roger Wolter, Architecture Strategies for Catching the Long Tail, Microsoft Corporation, Washington, April 2006. [7] Frederick Chong, and Gianpaolo Carraro Roger Wolter, Architecture Strategies for Catching the Long Tail, Microsoft Corporation, Washington, April 2006. [8] Frederick Chong, and Gianpaolo Carraro Roger Wolter, Multi-Tenant Data Architecture, Microsoft Corporation, Washington, June 2006. [9] Frederick Chong, and Gianpaolo Carraro Roger Wolter, Multi-Tenant Data Architecture, Microsoft Corporation, Washington, June 2006. [10] Wenbin Yu, Xiaohui Huang, and Min Yu,”A Solution of Shared Database and Architecture’s SaaS Based on XML”, Computer and Modernization, 8-10, April 2008. [11] Frederick Chong, and Gianpaolo Carraro Roger Wolter, Multi-Tenant Data Architecture, Microsoft Corporation, Washington, June 2006. [12] Wei Ye .etc,Software Revolution in Internet Age:SaaS Architecture Design,Publishing House of Electronics Industry,Beijing,2009, 102. [13] Wei Ye .etc,Software Revolution in Internet Age:SaaS Architecture Design,Publishing House of Electronics Industry,Beijing,2009,104-105.

Articles of Association for Zhongbao Energy Resources Service Company Catalogue Chapter 1 General Provisions Chapter 2 Objectives， Scope and Scale of Production and Business Chapter 3 Total Investment Amount and the Registered Capital Chapter 4 Investors Chapter 5 Board of Directors Chapter 6 Supervisors Chapter 7 Business Management Office Chapter 8 Labor Management Chapter 9 Trade Union Chapter 10 Taxation and Finance Chapter 11 Exchange Management Chapter 12 Distribution of Profits Chapter 13 Duration and Termination Chapter 14 Insurance Chapter 15 Supplementary Provisions Chapter 1 General Provisions Article 1 In accordance with Law of the People's Republic of China on Foreign-Capital Enterprises ,Company Law of the PRC and other relevant Chinese laws and regulations, __Treasure China Investment Limited intends to set up Zhongbao Energy Resources Service Co. Ltd. (hereinafter referred to as the Company), an exclusively foreign-owned enterprise. For this purpose, these Articles of Association hereunder are worked out. Article 2 The investing party is a legal person registered with Hong Kong in accordance with the laws of Hong Kong. Basic information as follows: The legal name of the investing party is Treasure China Investment Limited. Its legal representative: Name Nationality The legal address of the Company is at Rooms 1001-4A, Champion Building, 287-291 Des Voeux Road Central, Hong Kong. Tel: Fax: Article 3 The name of the Company in Chinese is 中宝能源设备服务有限公司 The name of the Company in English is Zhongbao Energy Resources Service Company. The legal address of the Company is at 6,Gangwu Avenue, Xi’an International Trade &Logistics Park, Xi’an, China. Article 4 Chairman of the Board is the legal representative, perform his or her duties comply with the stipulations of the Chinese laws, decrees and relevant regulations. Article 5 The Company is Chinese legal person, i

Table of Contents 2 General Settings 16 检查度量单位(Check Units of Measurement) 16 Financial Accounting 19 Financial Accounting Global Settings 19 例1功能范围的应用. 19 例2业务范围(Business Area) 19 年度变式(Fiscal Year) 19 会计凭证(Document) 如何限制不同财务用户使用不同的财务凭证类型 22 Field status和Coding block subscreen 30 Validation凭证的确认 35 Substitution凭证的退代 40 3 几个相关函数FI_VALIDATION_DOC|FI_VALIDATION_HEADER 45 货币类型和外币评估 50 ERP货币类型和外币业务 56 （一）ERP货币设置 57 （二）汇率类型和汇率换算表（Tcode：OB07|OB08） 59 （三）平行货币 62 汇率与外币评估 63 财务分类帐 92 Tax on Purchase & Sales 100 大话MM定价增值税处理 100 SAP 税务配置. 108 SD篇 tax 112 SD一周通系列 114 SD定价实例 118 收入科目确定. 119 税务设置 119 特别总帐 (Special Purpose Ledger) 128 1基本设置(Basic Settings) 129 (1)Perform Preparation 129 (2) Maintain Coding Block 130 (3) Tables 133 (4) Maintain Table Directory 139 (5) Maintain Fixed Field Movements 139 (6) Master Data 140 (7) Production Start-Up Preparation 148 (8) Validation 148 (9) Substitution 148 (10) User Exits 148 2计划(Planning) 148 3实际过帐(Actual Posting) 148 4期间处理(Periodic Processing) 148 5信息系统(Information System) 148 6工具(Tools) 149 例1 使用SPL出中方会计报表 149 例2 维护coding block screen 151 EC-CS Consolidation 151 合并会计处理方法 151 第14夜:合并数据建模 152 一.建立合并源数据基础信息立方体(Tcode:RSA1). 152 二.建立合并数据基础信息立方体(Tcode:RSA1) 153 三.BCS建模(Tcode:UCWB,UCWB01,UCMP0) 154 (1).建立合并数据基础 154 (2).设置合并范围 158 (3).设置合并参数(Tcode:UCMP0) 160 (4).设置合并源数据基础 160 (5).合并会计科目表和合并频率设置 161 (6).BCS60数据增强的功能 161 例1 使用混合合并单元 162 例2 BCS和ECCS等合并系统简单对比 163 第五节子分配和细分类别 164 SAP会计科目自动分配配置大全 170 1 Maintain Accounting Configuration(概览) 170 2 Automatic Posting Configuration (MM Module) 171 例1:如何使用Valuation group code 180 例2 PO condition和OBYC 182 例3使用PO处理委外加工 182 例4 Account assignment的逻辑分析 182 例5采购运费处理 182 例6:P&L科目和成本要素的建立 183 例7采购科目分配设置 183 例8汇率变更影响发票校验. 183 例9月结GR/IR处理 183 戏说一下SAP的清帐 183 Vendor的AP和Customer的AR能被对清,需要在Vendor和customer主数据设置一下, 189 如图7-[2],在vendor的control页的Account control的Customer填上Customer name 80005803. 189 如图8-[2],在payment transaction accountings页选上Clng with Cust.标志 189 Asset Accounting 197 折旧方法和折旧码 197 使用Substitution退还固定资产折旧某资产折旧的费用科目和折旧金额 204 FB08如何reverse多余的折旧凭证. 218 应收应付(Accounts Receivable and Accounts Payable)配置 226 Report painter外资公司如何出中方式报表. 234 FICO统驭和中间清算 245 Field status and Coding block subscreen 字段状态组实例 250 特别总帐标识 255 预付款处理 258 目的 258 流程 258 预付款结帐 258 发票冻结(Invoice Block) 259 Dunning AR催款配置 262 浅谈表结法和帐结法 269 1.结转收入 270 2. 结转费用. 270 营业管理财务各期间费用 270 所得税费用等等 270 Company和Company Code的区别 272 Investment Management 273 投资管理 273 投资计量 276 投资订单预算 278 Treasury 281 现金管理和预算控制 281 第一节现金管理配置 282 第二节现金管理业务操作 290 现金管理一日通 295 CO - Controlling 306 Internal Order 内部订单 306 第一节订单主数据 308 第二节订单审批 311 第三节订单计划 317 第四节内部订单预算 317 第五节结算规则自动生成 320 内部订单(Internal Orders) 审批流程配置 322 1 订单主数据 323 [1]激活订单管理(Tcode:OKKP) 323 [2]定义订单类型(Tcode: KOT2|KOT2-OPA|KOT2_FUNCAREA) 324 [3]维护订单编号范围(Tcode:KONK) 326 [4]定义状态主文件(Tcode:OK02|BS02) 326 [5]定义受权码(Tcode:BS52/BS53) 328 [6](Tcode:KOV2) 328 [7]分配状态管理给订单类型(Tcode: 328 例1.设置订单审批流程 328 例2.使用投资订单管理固定资产项目 332 CO-CCA Cost Center Accounting 332 分配分摊 332 最牛B最灵活的分配分摊依据--统计指标 340 作业类型 352 一建立type 43次级成本要素(Tcode:KA06) 353 Act Ind. deter&Alloc 353 二建立作业类型(Tcode:KL01) 353 三建立生产成本中心(Tcode:KS02) 356 四成本中心作业量计划(Tcode:KP26|KP27) 357 Cost center CCTR3 has none of the activity types used here 357 五建立成本中心费用计划(Tcode:KP06|KP16/KP17/KP36/KP37) 359 六计算计划价格(Tcode:KSPI) 361 七维护分割结构(Tcode:OKES/OKEW) 362 八建立工作中心. 371 Activity type ACTMN is not allowed for business transaction RKL 371 九建立统计指标 372 十重过帐和直接作业分摊 372 十一分配分摊 372 CO-PC 381 Costing Sheet 成本核算单 381 [1].Define Origin Groups(Tcode:OKZ1) 382 [2].Maintain Overhead Cost Elements（Tcode：KA06） 383 [3].Define Costing sheets 383 [4].Define Calculation Bases 385 [5].Define Percentage Overhead Rates（Tcode:S_ALR_87008275） 386 [6].Define Quantity_Based Overhead Rates 387 [7].Define Credits 388 [8].Develop Enhancement 388 [9].Define Overhead Key 389 [10].Define Overhead Group 389 [11].Define Cost Component Structure（Tcode：OKTZ） 390 [12].Error Management 390 使用成本核算单的标准成本估算实例。 390 标准成本Cost variant的Valuation Variant 001(Tcode:OKK4) . 390 作业计划价格和Routing检查(CA03). 390 作业计划价格检查(KP26) 391 成本核算单和成本组件结构 393 例1 Origin group的使用 402 例2 Costing sheet结构和成本估算实例 404 例3 407 例4 ZROY Calculation Base增强 407 例5 细说Cost component Structure和Cost Variant关系 411 生产成本控制(Product Cost Controlling)后台配置 411 6.1 Product Cost Planning 412 6.1.1 Basic Settings for Material Costing 412 Plan, Target, Actual and Control Cost 421 [1]Basic Settings 423 [2]Cost Variants for Manufacturing Orders 423 [3]Valuation Varaint 427 [7] Define Cost-Accounting-Relevant Default Values 430 [9] Error message 管理 431 [10] 431 (一) Work in Process 433 (2) Variance Calculation 439 Variances = actual debit – actual credit. 用中国的话来说就是FUl settlement的工单差异一定等于实际的生产成本投入和产出之差. 那么我还要target cost 干什么? 444 (3) Settlement 452 Future costing 方案(技术篇). 460 业务背景: 460 业务未定部分 461 解决方案 462 CO-PC部分 462 (1)Creating costing type (Tcode:OKKI) 462 (2)Create Valuation variant Z03 (Tcode:OKK4). 463 (3)建立成本估算变式(Tcode:OKKN) 463 (4)按业务背景编写取价逻辑(Tcode:SMOD/SE38) 464 CO-PA部分 465 (1) 建立销售计划版本(Tcode:OKEQN/OKEVN) 465 (2) 定义评估策略(Tcode:KE4U) 467 (3) 自定义评估策略(Tcode:SMOD/SE38) 467 需要确定因素: 467 CK11N取info record 分析报告(注:相当于某地方级政府GDP报告) 468 Purchase Info record tables : 468 取什么info record 470 Cost Estimation 成本估算 471 1成本估算变式 472 [1]Define Costing Types 472 [2]Define Valuation Variants 473 (1)Material valuation 473 (2)Actity Type/Process 475 (3)Subcontracting 475 (4)External Processing 475 (5)Overhead 476 (6)Price Factors 476 [3]Define Date Control 477 [4]Define Quantity Structure Control 477 [5]Define Transfer Strategy 478 [6]Define Reference Variants 478 [7]Define Costing Variants 478 2.标准成本估算 479 例1. Last PO Price Cost Estimate 479 例2. Future Costing for COPA 479 例3. 479 数量结果控制设置 479 重复制造生产配置. 482 按库存生产配置(Make-to-Stock). 482 按订单生产配置(Make-to-order). 483 CO-PA 483 7.利润分析(Profitability Analysis)后台配置 483 7.1 Structures 484 7.1.1 Maintain Characteristics 485 7.1.2 Maintain Value Fields 488 7.1.3 Maintain Operating Concern 490 7.1.4 Sample Operating Concerns 492 7.1.5 Define profitability Segment Char. 493 7.1.6 Set Operating Concern 493 7.2 Master Data 493 7.2.1 Maintain Characteristic Values 493 7.2.2 Define Characteristics Hierarchy 494 7.2.3 Define Characteristic Derivation 494 7.2.4 Valuation Strategies 498 7.2.5 Set Up Valuation Using Material Cost Estimate 498 7.2.6 Set Up Conditions and Costing Sheets 498 7.3 Planning 499 7.3.1 Initial Steps 499 7.3.1.1 Define Number Ranges for Planning Data 499 7.3.1.2 Maintain Versions 499 7..3.1.3 Assign Quantity Fields 499 7.3.2 Planning Framework 499 7.3.2.1 Set Up Planning Framework 499 7.3.2.2 Create Planning Level fro Planning Layout 500 7.3.2.3 Display Planner Profiles 500 7.3.3 Manual Entry of Planning Data 500 7.3.3.1 Define Planning layout 500 7.3.3.2 Define Value Field Assignments 500 7.3.3.3 Define Distribution Profiles 500 7.3.3.4 Calculated Values as Reference 500 7.3.4 Integrated Planning 500 7.3.5 Planning Aids 500 7.3.6 Reorganization 500 7.4 Flows of Actual Values 500 7.4.1 Initial Steps 501 7.4.1.1 Define Number Ranges for Actual Postings 501 7.4.1.2 Maintain Characteristic Groups 502 7.4.1.3 Assign Cha. Grp. for Assignment Screen 502 7.4.1.4 Assing Char. Grp. For Line Item Screen 503 7.4.1.5 Maintain Value Field Groups 503 7.4.1.7 Summarize Data During Update 505 7.4.1.8 Store Quantities In CO-PA Std. Unit of Measure 505 7.4.2 Transfer of Incoming Sales Orders 506 7.4.3 Transfer of Billing Documents 507 7.4.4 Order and Project Settlement 508 7.4.5 Direct Posting from FI/MM 508 7.4.6 Settlement of Production Variances 508 7.4.7 Transfer of Overhead 508 7.4.8 Transfer Customer Rebate Agreements 508 7.4.9 Multiple Valuation Approaches/Transfer Price 508 7.4.10 Periodic Adjustments 508 7.4.11 Activate Profitability Analysis 508 1.定义经营范围 511 2.获利分析段PSG 518 3.特征值派生和值字段评估 519 1 基本设置(Basic Settings) 530 2 企业组织(Enterprise Organization) 535 3 主数据(Master Data) 536 4 利润中心分配(Assignments to Profit Centers) 539 SAP屠宰行业CO解决方案 540 业务背景： 540 SAP实现 542 1建立物料 543 2建立BOM 543 3.外包给屠夫宰 545 4.使用外包工序 549 关于联产品工单成本怎么结算?你整一个Allocation structure, SAPhelp. Create Allocation Structure 551 5工单 552 Material Ledger 物料分类账详解 552 一.ML功能简介 552 二.标准价Pk加权平均价 559 三.差异来源和差异处理 564 四.SAP差异科目设置 565 利润中心(Profit Center Accounting) 565 1 基本设置(Basic Settings) 566 2 企业组织(Enterprise Organization) 571 3 主数据(Master Data) 572 4 利润中心分配(Assignments to Profit Centers) 575 5 转移价格(Transfer Prices) 576 Logistics - General 576 销售运作计划(SOP)和利润计划 576 LIS配置 578 (2)应用Sales Flexible Planning 584 (3)使用PA Planning Framework(KEPM ) 589 (4)PA Valuation Stratege 595 MM Material Management 595 PO Account Assignment 增强 Coding Block 596 Background: 599 1.Related IMG 599 Step 1.Define valuation class for those non-material 599 Step 2.Define PO Account Assignment Categories 602 Step 3. Assign account to VBR 604 Step 4.Where we define valuation class 604 2.Q&A 605 1.How to Activate Direct Posting to G/L Accounts and Material Account 605 2.What will Happen? 607 3.Mark delv. Completed 607 物料移动类型和后勤自动科目设置 608 分割评估和混合成本 620 业务背景: 620 配置分割评估 620 建立物料主数据 624 建立cosing mix ratio (Tcode:CK91/CK91N|CK94) 627 Valuation variant分析 632 后勤一般设置(Logsticis-General) 638 物料主数据(Material Master) 638 MM Condition配置 647 PO审批流程 661 一定义Release group 661 二定义Release code 661 三定义Release indictor 662 四定义Release Strategy 663 五建立分类Z_PUR_DOC_RELEASE 667 Stock Transfer Order 669 MM PO配置 670 跨公司transfer order 681 两种外包方式比较 686 业务背景: 686 1.直接使用外包PO 687 (1)成本核单(Costing sheet)设置 687 (2)成本部件(Cost component structure) 688 (3)维护物料info record 690 (4)标准成本估算 690 (5)外包PO无Condition流程 692 (6)应用PO condition 694 (7)外包科目设置 695 (8)外包PO带4个condition流程. 696 (9)存在的问题 698 2.使用工单混合作业外包 699 (1)建立作业外包info record 699 (2)建立外包工序 700 (3)标准成本估算 701 (4)建立工单和作业PR转PO 702 (5)作业外包PO收货 704 (6)配置PO Account assignment 704 (7)工单收货外包料的价格处理 706 (8)自定义逻辑 708 (9)存在的问题 709 委外加工的种类和处理方法(使用prod. Order和purchase order) -2 709 1.Related IMG 710 Step 1.Define valuation class for those non-material 710 Step 2.Define PO Account Assignment Categories 712 Step 3. Assign account to VBR 714 Step 4.Where we define valuation class 714 2.Q&A 715 1.How to Activate Direct Posting to G/L Accounts and Material Account 715 2.What will Happen? 717 3.Mark delv. Completed 717 MM Condition MM采购定价 720 透视条件（Condition）技术 725 （1）定义采购定价控制级别（SE16：V_001W_K） 727 （2）熟悉采购定价过程 728 物料主数据 739 (1).物料主数据配置 739 (2).为用户设置可维护主数据屏幕 739 (3).限制维护物料字段 743 (4).设置物料交易状态（Tcode：OMS4） 746 (5).特殊物料处理 747 SAP相关打印编程- PO打印 751 物料管理(Material Management) 后台配置 761 物料管理一般设置 761 采购环境数据(Environment Data) 762 物料采购数据(Material Data) 762 分隔评估(Split Valuation) 765 供应商和合作伙伴确定(Vendor Master| Parter Determination) 765 后勤发票校验(Logistics Invoice Verification) 765 收进发票处理(Incoming Invoice) 767 Valuation and Account Assignment 772 例1:如何使用Valuation group code 781 例2 PO condition和OBYC 783 例3 移动类型如何取得自动配置科目 ? 783 运杂费处理 788 (一)方法1:直接列入期间费用 789 (二)方法2:使用事后借记和计划外运输费用 789 (三)方法3:应计条件类型处理运杂费. 791 (四)方法4:建立厂外临时工厂. 799 (五)其他方法 800 GR/IR科目拆分 801 Background 801 OMSF define additional material group ZSTONE 802 Define additional valuation class ZSTV (OMSK) 802 OMQW define additional material group 804 Define another GR/IR account with OBYC->WRX 804 ME21N/MIGO test 805 正解方案: 808 物料类型 810 管道物料(Pipeline Material) 810 供应商寄存物料(Consignment Stock) 811 委外加工物资 811 寄售给客户物料 811 客户维修物料 812 更改物料Valuation class 812 GR/IR 的绝妙应用 814 PP - Production 817 使用外包工序 817 (1)建立作业外包信息记录 817 (2).建立外包工序 818 (3)外包标准成本估算 819 (4).建立外包工单 820 (5).外包采购单收货 822 (6).外包工单收货外包件价格设置 823 Super BOM(Configurable material BOM)的应用 824 一 Classification System(分类系统)简介 824 二 Super BOM和配置BOM应用举例 825 建立物料(Tcode:MM01) 827 建立Super BOM(CS01) 829 建立configurable profile (Tcode:CU41) 830 例1- Phantom Part的使用. 834 例2 配置BOM的成本估算 834 SD - Sales & Distribution 834 SD Condition SD销售定价 834 BC - Basis 840 How to Archive material master data or inventory data? 840 Relatd T-codes: 840 2. How to change valuation category with existed transaction data . 840 3. How to archive the batch data . 842 4.Unit test OK ! 845 How to delete a change request 846 How to set required fields for material master 847 1. Self define a Sel. Group and Re-assign Fields to Field Selection Groups 847 2. Maintain Field Selection for Data Screens 849 3. Unit test result . 850 Little SAP tips 851 How to add a search Help? 853 How to add field MARA-ZEIAR(Document type ) as a search help 853 1.What is so-called a search help 853 2.How to add a search help for material master data 854 How to add code for SAP Query 857 Case 1. change fields sign . 858 Case 2. Add additional Tables and fields . 859 Case 3.Coding using work area or internal table for additional fields. 860 Case 4: Use alias table to add a same table for query twice or multiple times. 863 Case5. User cluster table BSEG with logical database 864 1. use logical database, such as BRF 866 2. direct read of table BSEG 866 Case6. Use left outer join to avoid query data missing 867 Case7.Change Query Program with SE38 868 大话ERP权限控制 870 IMG剖析和SE16 878 如何收集常用事务码? 880 ABAP 882 ABAP开发三月通 882 前言 882 一.基础篇 883 1.什么是ABAP ? 884 2.ABAP开发环境的建立 887 3.获得Access Key . 887 4.ABAP workbench和ABAP dictionary 887 5.第一个程序-Hello World. 888 6.ABAP语法简介 889 7.Open SQL和Native SQL 889 8.内表和工作区 889 9.使用字段符号 889 10.模块化程序 889 11.文件处理 889 12.簇数据库和逻辑消息和错误处理数据库 889 13. 889 14.使用用户授权 897 15.调用外部程序和程序动态生产 897 16.选择屏幕 897 17.使用程序运行变式 897 18.制作Tcode 897 二.加强篇. 898 1.CATT 898 2.BDC 898 3.制作程序的background job 898 4.SapScript 898 5.Smartform 898 6.SAP Query 898 7.ALV编程 898 8.ALE/iDoc 898 9.Report painter和Drilldown Report 898 10.RFC/BAPI 898 11.编写用户增强 898 12.深入ABAP工作台 898 13.传输请求 899 14.和其它语言的交互 901 三.实战篇 901 1.MM模块开发实例. 901 一.MM常用表格及其关联关系图 901 二.开发实例 901 1.MM相关单据打印 902 2.PO增强编程 902 自动建立PO和SO 903 SE11建立一记录表ZPOSO 904 使用PO User_exit 904 3.物料主数据编程 915 4.供应商列表分析 (No Content) 915 5.收货检测增强 (No Content) 915 6.库存分析报表 (No Content) 916 7.GR/IR报表 (No Content) 916 8.报废流程增强 (No Content) 916 2.SD模块开发实例. 916 3.PP模块开发实例. 916 4.FI模块开发实例. 917 1.编写财务报表 917 2.财务凭证的确定(Validation) 917 3.财务凭证的退代(Substitution) 924 4.BKPF|BSEG浅析 937 5.Dunning催款 937 6.支票打印 937 7. 937 8. 937 5.CO模块开发实例 (No Content). 937 6.Basis相关开发实例 937 1.删除传输请求 937 2.检测用户授权列表 940 3.致命SAP权限控制漏洞 940 4.再谈开发权限漏洞 945 开发项目流程简介 (No Content). 951 附录: 951 ABAPer 常用Tcode 951 编写用户增强 953 操作最简单的欺骗Access Key的文档 957 (1)SE38 :输入LSKEYF00按display 957 (2)/n 或者/O开新窗口,SE38再输入LSKEYF00这次按change按钮. 957 (3)SE16: progdir,准备请空PROGDIR-EDTX 958 4.插入一行SY-SUBRC = 0 .到LSKEYF00就可. 960 快速修改表内容 961 如何快速找到增强 964 Message消息控制 966 BW 969 第一篇 BW篇 969 第1夜数据仓库知识 969 一.什么是数据仓库(Data Warehouse)? 969 二.为什么使用SAP BW 970 三.数据仓库架构理论(附) 973 四.OLTP&OLAP(附) 973 五SAP BW(Business Information Warehouse)实施方法论 975 a. SAP BW的版本历史 976 第2夜ABAP基础 977 第3夜逻辑系统和数据源 977 一.建立逻辑系统 977 思考:如何建立R/3和BW的数据交换通信? 980 二.将配置Tcode整成前台执行 982 三.建立数据源(Data Source) 985 思考: 如何增强0FI_GL_1? 989 四.数据源传输模式 994 五.SAP发展简史(附) 995 第4夜BW管理员工作台 997 第5夜数据抽取准备 1001 一.建立源系统(Source System) 1001 SEM - Strategic Enterprise Management 1004 第22夜 SEM模块简介 1005 Procedure for System Administration 1009 第23夜使用BPS制定销售计划 1010 一.SAP R/3 的LIS->SOP->KEPM实例回顾 1010 1.建立LIS表格 1010 2.SOP 1018 二.使用BPS制定销售计划 1019 1.建立销售计划信息立方体 1019 2.启动BPS工作台(Tcode:BPS0) (1)Create Planning Area 1020 BCS 混合合并疑问 1022 例1 使用混合合并单元 1022 一.合并版本(Verions) 1026 例2 使用混合版本 1026 SAP上线期初初始数据如何导入（尤其是针对以前有老系统的情况） 1029 MM 1029 SD: 1030 PP 1031 FICO 1031

下载资源悬赏专区

12,795

社区成员

12,332,765

社区内容

发帖

与我相关

我的任务

其他技术论坛（原bbs）

社区管理员

加入社区

近7日
近30日
至今

加载中

查看更多榜单

社区公告

暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章