MM Process Flow, Relevant T-Codes and Tables

最新推荐文章于 2025-08-05 15:39:27 发布
最新推荐文章于 2025-08-05 15:39:27 发布 · 221 阅读 · 1
文章标签：

#thread #PHP #UP #Access

本文详细介绍了SAP系统中物料管理模块(MM)的典型采购流程，包括需求确定、供应商选择、采购订单处理等关键步骤，并列举了常用事务代码及重要数据表。
MM Process Flow
PR (Purchase Requisition) > Release the PR > RFQ (Request for Qotation) > Quotation > Quotation Comparison > PO > Release the PO > GR (Goods Receiving) > Invoice Verification
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

Relevant T-Codes
Purchase Order Requisition- ME51N
RFQ to Vendor ------------------- ME41
Raising Quotation -------------- ME47
Comparison of Price ----------  ME49
Vendor Evaluation -------------- ME61
Creation of PO ------------------- ME21N
Goods Receipt with PO ------- MIGO
Goods Receipt without PO --- MBIC
Invoice Verification -------------- MIRO
Goods Issue --------------------- MB1A
Physical Inventory -------------- MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)

Common Tables used by MM
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types

Reference
https://www.sdn.sap.com/irj/sdn/thread?messageID=2587232#2587232
https://www.sdn.sap.com/irj/sdn/thread?messageID=2757752#2757752
https://www.sdn.sap.com/irj/sdn/thread?messageID=2790858#2790858

http://www.sapgenie.com/abap/tables_mm.htm
http://www.sap-img.com/sap-download/sap-tables.zip
http://www.allsaplinks.com/material_management.html
http://www.training-classes.com/course_hierarchy/courses/2614_SAP_R_3_MM_Invoice_Verification_-_Rel_4_x.php
http://www.sapfriends.com/sapstuff.html

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSMAT/PSMAT.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCMM/CAARCMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOMDMM/LOMDMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMMM/BCBMTWFMMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMIVMVAL/MMIVMVAL.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMWMLVS/MMWMLVS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MMISVE/MMISVE.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSMAT/PSMAT.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCMM/CAARCMM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
5、Mastering SAS SQL: Using Dictionary Tables and Joins
view3的博客
08-01 81
本文深入探讨了SAS SQL中的Dictionary表和连接操作（Joins）。首先介绍了Dictionary表的基本概念及其用途，包括如何查询表定义和显示特定库的信息。接着详细讲解了PROC SQL中连接的类型，包括内连接和外连接的工作原理、语法及使用示例。文中还通过多个实际案例展示了如何使用连接进行数据分析，如员工信息整合和销售数据统计。最后总结了Dictionary表和连接操作在SAS SQL中的重要性，并提供了优化内连接性能的最佳实践。这些内容为SAS开发者和数据分析师提供了实用的参考指南。
MM Process flow Note
01-31 176
Cycle counting的一般做法: 频率每周1次或根据企业自行决定1。MI04打印盘点清单2。库房实盘，把结果输入MI043。GOTO MI07检查差异显示4。如果有差异的材料重盘5。重新CONFIRM 后把结果输入MI0...
物料管理
cudaidie2044的博客
07-11 614
物料管理的一些概念[@more@]1、SAP物流相关模块中，工厂是最重要的组织结构，隶属于公司代码，并且包括了和物流管理相关的最多的控制参数。这里首先创建一个工厂。 2、创建工厂下面的3个库存地点：仓库、生产、运输。 3、创建采...
SD Process Flow, Relevant T-Codes and Tables
Matt的技术专栏
10-12 3056
   SD Process Flow1. Inquiry (VA11)2. Quotation / Contracts / Scheduling Agreements (VA21)3. Sales Order (VA01)4. Delivery          a) Create Delivery (VL01N)         b) Picking (LT03)         c)
ERP Operations /ERP Logistics Operations----Frequently Used Tables
weixin_30716725的博客
09-18 215
Frequently Used Tables Group Table Name Description Classification Tablesand Others AUSP Characteristic Values Classification Tablesand O...
SAP LE学习笔记01 - 豆知识 - LE（物流管理）中WM模块的T-code列表
shi_ly的专栏
08-17 1182
本章主要是LS-WM / DWM / GF 那边的T-code 大集合。LS里面东西还真多啊。
WM 仓库管理T-CODE
banglvfei0870的博客
06-11 357
1.1 LE-WM 仓库管理 Warehouse Management 仓库管理 事务码 描述 LB01 Create Transfer Requirement 创建转储需求 LB02 Change transfer requirement 修改转储需求 LB03 Display Transf...
SAP-MM-代码大全
热门推荐
少年休闲海
07-23 1万+
1.1.1      MM-CBP 基于消费的计划 Consumption-Based Planning 基于消费的计划 事务码              描述 OWD1    Maintain rounding profiles 维护取整参数文件 WR30     Replenishment: Generate wghtng prof. 补充:生成加权参数文件
J2EE 应用设计模式推荐（摘抄自Expert One-on-One J2EE Design and Development）
xingshen100的专栏
08-13 1545
OO Design Recommendations for J2EE Applications It's possible to design a J2EE application so badly that, even if it contains beautifully written Java code at an individual object level, it will stil...
Control Traffic Trapping/Mirroring to the CPU Protocols implemented in software require specific control traffic to be trapped or mirrored to the CPU. The device provides trapping/mirroring mechanisms for many well-known control traffic protocols. Other control traffic that does not have specific support can be trapped/mirrored to the CPU by the Policy engine. A global configuration disables the following controls for packets that were dropped by the Spanning Tree:  IGMP  MLD and Other IPv6 ICMP  UDP Broadcast Mirror/Trap (UDP Relay)  IP Interface Control Traffic Configuration To disable L3 Controls for packets that were dropped by the Spanning Tree, set the <DisableIPControltoCPUforSTP> field in the Bridge Global Configuration1 Register (Table 320 p. 2218). 10.8.1 Layer 2 Interface Unicast Management Traffic Layer 2 interface Unicast management traffic arrives with a MAC DA set to the management MAC address on a given eVLAN interface. Typical examples of Unicast management traffic are:  IP management protocols like SNMP, HTTP, and ICMP  ARP Reply packets To direct Unicast Management Traffic to the CPU, the FDB is configured with an entry as follows:  <MAC Address> = management Unicast MAC Address  <FID> = The Forwarding ID of the management VLAN interface  <DA Command> = FORWARD  <ePort number> = CPU port 63 (refer to Section 23.1, CPU Port)  <Application Specific CPU Code Enable> =1  <static> = 1 Packets with MAC DA matching the management Unicast MAC Address are sent to the CPU with the CPU code BRIDGED_PACKET_FORWARD. However, if the FDB entry <Application Specific CPU Code Enable> is set, the CPU code may be overridden by a finer-grain CPU code. For example, if the packet is an ARP reply, its CPU code assignment can be overridden with the specific CPU code ARP_REPLY_TO_ME. This is performed in the Pre-Egress stage of the Ingress pipeline (Section 23.2.4, Application-Specific CPU Codes). Refer to Section 10.4.7.2, FDB Table Read/Write Access for details on how the FDB is updated. Note When the FDB entry <port number> is set to the CPU port 63, the FDB entry <device number> is not relevant, as the packet is forwarded to the target device according to the CPU code table configuration, as described in Section 23.2.5, CPU Code Table. IPv4/6 and FCoE Interface for Routed Traffic Bridged traffic with a MAC DA of the router interface is subject to processing by the Router engine, per the Router Engine Trigger (refer to Section 11.2, Router Engine Trigger). This traffic may be inbound management traffic with the Unicast destination IP address of the router, or other IP traffic that requires routing to its next-hop interface. It may also be FCoE traffic that is subjected to FCoE Forwarding (FCF) by the Router engine. The FDB is configured with a static Unicast Router MAC address for each eVLAN interface enabled for routing. The FDB Router MAC entry is configured as follows:  <MAC Address> = Unicast Router MAC address  <FID> = The Forwarding ID of the management VLAN interface  <static> = 1  <DA Route>=1, indicating that the entry Unicast MAC Address is the Router MAC  <DA Command>=FORWARD  <Device Number> = local device  <ePort Number>= CPU port (63)  <Application Specific CPU Code Enable> =1 The Router MAC FDB entry serves two purposes:  The <DA Route> bit serves as input to the Router engine trigger check to determine whether the packet is eligible for routing. If the packet is subsequently routed by the Router engine, the bridge forwarding decision (CPU port 63) is overridden by the router next-hop information.  If the packet does not trigger the Router engine for any other reason (for example, packet is not non-IP), the packet is sent to CPU port 63, with the CPU code BRIDGED_PACKET_FORWARD. However, if the FDB entry <Application Specific CPU Code Enable> is set, the CPU code may be overridden by a finer-grain CPU code, for example, if the packet is an ARP reply, its CPU code assignment can be overridden with the specific CPU code ARP_REPLY_TO_ME. This is performed in the Pre-Egress stage of the Ingress pipeline (Section 23.2.4, Application-Specific CPU Codes). 10.8.3 IEEE Reserved Multicast IEEE 802.1D/Q defines the following reserved Multicast MAC ranges:  Bridge Standard Protocols: 01-80-C2-00-00-00 - 01-80-C2-00-00-0F  Bridge GARP Applications: 01-80-C2-00-00-20 - 01-80-C2-00-00-2F Common addresses that fall into these ranges are listed in Table 28. Table 28: IEEE Reserved Multicast Addresses Protocol Identified by IEEE 802.1Q BPDU DA=01-80-C2-00-00-00 IEEE 802.3 Slow Protocols (for example, LACP) DA=01-80-C2-00-00-02 IEEE 802.1X PAE address DA=01-80-C2-00-00-03 IEEE 802.1Q Provider BPDU DA=01-80-C2-00-00-08 IEEE 802.1Q Provider Bridge GVRP DA=01-80-C2-00-00-0D IEEE 802.1AB LLDP DA=01-80-C2-00-00-0E As a generic mechanism to trap or mirror the above reserved IEEE ranges and possible future IEEE protocols, the device supports 8 IEEE Reserved Multicast Command tables. A packet is considered an IEEE Reserved Multicast packet if its MAC destination address is in the range 01-80-C2-00-00-XX. Each ePort is configured to utilize one of these 8 tables to process IEEE Reserved Multicast packets. If a packet is identified as an IEEE Reserved Multicast packet (its MAC destination address is in the range 01-80-C2-00-00-XX) then:  The respective IEEE Reserved Multicast command table is indexed by the last byte of the Multicast address. The command for each entry can be set to: • SOFT DROP • FORWARD • MIRROR • TRAP  A configuration (indexed by the last byte of the Multicast address) defines if the packet is treated as Registered MC (refer to Section 10.14.1.3, Bridge Phase 1 Modification of the Unregistered/Unknown Status). To enable differentiation between different types of IEEE Reserved Multicast packets that are either trapped or mirrored to the CPU, there is a configurable 2-bit <CPU code index>, described in Table 29, assigned to the packet based on table entry index, meaning that the value of the last byte of the MAC destination address. The same <CPU Code Index> assignment is applied independently of the binding to one of the 8 IEEE Reserved Multicast tables. Configuration  To configure the IEEE Reserved Multicast command, set the respective IEEE Reserved Multicast table entry via one of the 8 available tables: • IEEE Reserved Multicast Configuration0 <n> Register (n=0–15) (Table 335 p. 2232) • IEEE Reserved Multicast Configuration1 <n> Register (n=0–15) (Table 336 p. 2234) • IEEE Reserved Multicast Configuration2 <n> Register (n=0–15) (Table 337 p. 2236) IEEE 802.1D GMRP DA=01-80-C2-00-00-20 IEEE 802.1Q GVRP DA=01-80-C2-00-00-21 Table 29: IEEE Reserved Multicast CPU Code Assignment <CPU Code Index> CPU Code Assignment 0 IEEE_RES_MC_ ADDR_TRAP/MIRROR_0 1 IEEE_RES_MC_ ADDR_TRAP/MIRROR_1 2 IEEE_RES_MC_ ADDR_TRAP/MIRROR_2 3 IEEE_RES_MC_ ADDR_TRAP/MIRROR_3 IEEE Reserved Multicast Configuration3 <n> Register (n=0–15) (Table 338 p. 2238) • IEEE Reserved Multicast Configuration4 <n> Register (n=0–15) (Table 339 p. 2241) • IEEE Reserved Multicast Configuration5 <n> Register (n=0–15) (Table 340 p. 2243) • IEEE Reserved Multicast Configuration6 <n> Register (n=0–15) (Table 341 p. 2245) • IEEE Reserved Multicast Configuration7 <n> Register (n=0–15) (Table 342 p. 2247)  To configure for IEEE Reserved Multicast address, if packets to that address are considered registered, set the respective bit in the IEEE Reserved Multicast Registered <n> (n=0–7) (Table 344 p. 2250)  Select one of the 8 tables to be utilized by each ePort by configuring the <IEEE Reserved MC table select> field in the Ingress Bridge ePort Table (Table 392 p. 2333).  To set the CPU code index for each IEEE Reserved Multicast address, configure the relevant fields in IEEE Reserved Multicast CPU Index <n> Register (n=0–15) (Table 343 p. 2249). 10.8.3.1 FDB Learning of Trapped or Dropped IEEE Reserved Multicast Packets When two bridges are connected to each other by more than a single port, IEEE-reserved MC packets are received by the bridge on all ports connecting between the two bridges. The IEEE 802.1Q standard requires the bridges to send the IEEE-reserved MC packets with unique MAC SA per port. There are bridges that use the same MAC SA for all the ports. This triggers continuous moved address indications and related processing in the receiving bridge. To protect those bridges from constantly processing the moved address for IEEE-reserved MC packets, the user can configure the device not to perform MAC SA learning for reserved IEEE MC packets that are dropped or trapped to the CPU. Configuration To enable/disable this feature, use the<EnLearnOnTrapIEEEReservedMC> field in the Ingress Bridge ePort Table (Table 392 p. 2333).翻译一下
11-18
flowchart TD A[桥接流量] -->|MAC DA=路由器MAC| B{触发路由引擎?} B -->|是| C[按路由规则转发] B -->|否| D[发送至CPU端口63] D --> E[精细CPU编码覆盖] ``` #### **IEEE保留组播处理** **多级控制架构** ...
14、Android Web Services: Optimization, Security, and Creation
vim8coder的博客
08-05 65
本文探讨了为Android应用优化、安全化和创建Web服务的最佳实践。内容涵盖了网络带宽优化（如GZIP压缩和HTTP缓存）、安全性（包括防止OWASP十大威胁和使用OAuth认证）、创建RESTful Web服务（使用JAX-RS和Google App Engine）以及性能调优、测试、监控和维护等方面。通过遵循这些指南，开发者可以构建高效、安全且可靠的Android网络应用。
【Introduction to Artificial Intelligence and Data Analytics】（TBC）
m0_66706847的博客
09-13 902
Introduction to Artificial Intelligence and Data Analytics 笔记。
基于Single-Pass增量聚类算法的实时文本流自动聚类工具_实现文本去重与主题聚合_用于高效处理大规模实时数据流如新闻标题或社交媒体内容以发现热点话题和事件演化脉络_支持TF.zip
11-30
基于Single-Pass增量聚类算法的实时文本流自动聚类工具_实现文本去重与主题聚合_用于高效处理大规模实时数据流如新闻标题或社交媒体内容以发现热点话题和事件演化脉络_支持TF.zip
【相控阵雷达跟踪】多目标跟踪的联合阵列资源分配和发射波束设计方法（Matlab代码实现）
最新发布
11-30
【相控阵雷达跟踪】多目标跟踪的联合阵列资源分配和发射波束设计方法（Matlab代码实现）内容概要：本文介绍了基于Matlab代码实现的多目标跟踪中联合阵列资源分配与发射波束设计方法，聚焦于相控阵雷达跟踪技术。该方法通过优化雷达系统的资源分配与波束形成策略，提升对多个高速机动目标的跟踪精度与效率，涵盖信号模型构建、优化问题建模及数值仿真验证等核心环节，旨在解决复杂电磁环境下多目标跟踪面临的资源受限与干扰抑制难题。; 适合人群：具备雷达信号处理、阵列信号处理或优化理论基础，从事电子工程、通信工程、自动化或相关领域研究的研究生、科研人员及工程技术人员。; 使用场景及目标：①用于深入理解相控阵雷达在多目标跟踪中的资源调度与波束设计协同优化机制；②支撑科研项目中雷达系统性能提升的技术方案设计与仿真验证；③作为撰写学术论文或开展算法复现实验的技术参考。; 阅读建议：建议结合Matlab代码进行仿真练习，重点关注优化模型的数学推导与算法实现细节，同时可扩展学习文中提及的相关信号处理与优化方法以增强综合应用能力。
JAVA毕业设计含文档和代码springboot教务管理系统
11-30
JAVA毕业设计含文档和代码springboot教务管理系统
基于遗传算法粒子群优化算法和蚁群优化算法对旅行商问题进行高效求解与性能对比分析的项目_项目极简说明为采用三种主流智能优化算法即遗传算法GA粒子群优化算法PSO和蚁群优化算法ACO针.zip
11-30
基于遗传算法粒子群优化算法和蚁群优化算法对旅行商问题进行高效求解与性能对比分析的项目_项目极简说明为采用三种主流智能优化算法即遗传算法GA粒子群优化算法PSO和蚁群优化算法ACO针.zip
基于C开发的通用面积计算器项目_该项目由涅槃工作室NirvanaStudio团队开发使用C编程语言和NET框架构建在VisualStudio2022IDE中实现.zip
11-30
基于C开发的通用面积计算器项目_该项目由涅槃工作室NirvanaStudio团队开发使用C编程语言和NET框架构建在VisualStudio2022IDE中实现.zip
计算几何与数值优化算法在自动驾驶领域的C实现项目_该项目专注于计算几何学的基础概念如点线面和多段线的定义与操作以及基本问题实现包括几何运算投影距离计算相对位置判断相交检测曲率分.zip
11-30
计算几何与数值优化算法在自动驾驶领域的C实现项目_该项目专注于计算几何学的基础概念如点线面和多段线的定义与操作以及基本问题实现包括几何运算投影距离计算相对位置判断相交检测曲率分.zip
interaction-change vue-flow
05-13
### Vue Flow `interaction-change` Event Usage and Issues In the context of Vue Flow, the `interaction-change` event plays a critical role in handling user interactions with nodes and edges within the flow diagram. This event is triggered whenever there is a change in how users interact with elements such as dragging, resizing, or connecting nodes. When working with this event, developers must consider that user interactions often involve asynchronous processing between different threads similar to what happens in React Native environments[^1]. In Vue Flow specifically, managing these events effectively requires understanding both synchronous updates during rendering phases and potential delays caused by underlying mechanisms like reactivity systems[^2]. For instance, when binding properties together through frameworks utilizing declarative approaches—such as those mentioned earlier—it's important to note that automatic updates may propagate throughout various components due to interconnected dependencies[^3]. Therefore, ensuring proper management of state transitions becomes crucial while leveraging tools provided by libraries designed around efficient animation pipelines might also prove beneficial depending upon specific requirements related to complex scenarios involving gestures or animations beyond basic functionality offered directly out-of-the-box from core packages alone. Additionally, adhering strictly to principles concerning method accessibility ensures cleaner codebases free from unnecessary coupling among unrelated parts thus promoting maintainability long term especially under larger scale applications development efforts where modularity matters significantly more than smaller projects would typically require otherwise [^4]. Below demonstrates an example implementation showcasing listener setup alongside relevant handler logic written inside your component script section: ```javascript <script> export default { mounted() { const vueFlowInstance = this.$refs.vueFlow; if (vueFlowInstance) { vueFlowInstance.on('interaction-change', ({ type, node }) => { console.log(`Interaction changed: ${type} on Node ID:`, node.id); switch(type){ case 'dragstart': // Handle drag start actions here. break; case 'dragend': // Perform post-drag operations e.g., saving position etc.. saveNodePosition(node); break; default: // Catch-all block for unhandled types... logUnhandledType(type,node); } }); } else { throw new Error("Vue Flow reference missing!"); } function saveNodePosition(node){ /* Simulate API call */ fetch('/api/save-position',{ method:"POST", body:JSON.stringify({id:node.id,x:node.position.x,y:node.position.y}) }) .then(response=>response.json()) .catch(err=>console.error("Failed updating:",err)); } function logUnhandledType(type,node){ console.warn(`Unrecognized interaction "${type}" occurred at Node(${node.id}).`); } }, }; </script> <template> <div ref="vueFlow"> <!-- Your existing flow content --> </div> </template> ```
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值