FI--Integration of FICO with Other Modules

本文详细介绍了SAP系统中FI-MM模块集成的过程,包括采购订单、收货凭证、发票过账及供应商付款等环节的财务会计处理;同时探讨了FI-SD模块集成,涉及销售订单创建、交货凭证、开票文件发布及收款等流程的财务管理。文章还列举了理解这些集成过程所需的关键知识点。

FI-MM: The integration between FI-MM happens in T-code OBYC. 

  1. When PO is created :

       ---- No Entry -----

  2. When GR is posted 

      Inventory Account dr (Transaction Key BSX in OBYC)
            To GRIR account (T.Key WRX in T-code OBYC)

  3. When Invoice is posted

      GRIR account Dr.
      Vendor account  Cr.

  4. Payment made to Vendor

      Vendor A/c Dr
            To Bank Clearing A/c Cr.

Points to know : Movement Types, Assignment of Movement types to T-keys (T-code OMJJ), Value string (I also need some information on this) , OMWN and OMWB transactions. 

---

There is a close integration b/w FI & MM, actually document flows from MM to FI in the following areas such as,
   
 1. Movement Types:
 
Used to enable the system to find the predefined posting rules determining how the accounts of financial accounting system are to be posted & to update the stock fields in the matrl master data.(Goods Receipt, Goods Issue, etc)
   
 2. Valuation Class:
   
Assignment of material to grp of gl account, used to determine the gl accounts that are updated as a result of goods movement.
   
 3. Transaction/Event key:
   
Used to control the storage or filing of documents & assignment of documents.Used to differeniate b/w various transactions such as goods movement tht occur in inventory.
   
 4. Material Type:
   
Each material should assign mtrl type in mtrl master record used to update whether changes made in qty are updated in material master record & change in value also updated in stock account.
   
 FI-SD Integration: The integration is done in T-code VKOA

  1. Sales Order Created 

        ---No Entry---

  2. PGI done (Goods issue)

      Cost of Goods Sold     Dr (Configured in OBYC GBB T-Key)
           To Inventory Account

  3. Billing document released to Accounting

        Customer Account Dr.
              To Sales Revenue Account (ERL T-key in Pricing procedure)

  Note : The GL account is assigned to this ERL in VKOA

  4. Payment Received

        Bank Clearing A/c Dr
                       Customer A/c Cr. 

Points to Know : Good to understand the pricing procedure and how the different transaction keys are used like ERL, ERS etc.

 Source URL:http://www.sap-img.com/financial/integration-of-fico-with-other-modules.htm
内容概要:本文详细介绍了“秒杀商城”微服务架构的设计与实战全过程,涵盖系统从需求分析、服务拆分、技术选型到核心功能开发、分布式事务处理、容器化部署及监控链路追踪的完整流程。重点解决了高并发场景下的超卖问题,采用Redis预减库存、消息队列削峰、数据库乐观锁等手段保障数据一致性,并通过Nacos实现服务注册发现与配置管理,利用Seata处理跨服务分布式事务,结合RabbitMQ实现异步下单,提升系统吞吐能力。同时,项目支持Docker Compose快速部署和Kubernetes生产级编排,集成Sleuth+Zipkin链路追踪与Prometheus+Grafana监控体系,构建可观测性强的微服务系统。; 适合人群:具备Java基础和Spring Boot开发经验,熟悉微服务基本概念的中高级研发人员,尤其是希望深入理解高并发系统设计、分布式事务、服务治理等核心技术的开发者;适合工作2-5年、有志于转型微服务或提升架构能力的工程师; 使用场景及目标:①学习如何基于Spring Cloud Alibaba构建完整的微服务项目;②掌握秒杀场景下高并发、超卖控制、异步化、削峰填谷等关键技术方案;③实践分布式事务(Seata)、服务熔断降级、链路追踪、统一配置中心等企业级中间件的应用;④完成从本地开发到容器化部署的全流程落地; 阅读建议:建议按照文档提供的七个阶段循序渐进地动手实践,重点关注秒杀流程设计、服务间通信机制、分布式事务实现和系统性能优化部分,结合代码调试与监控工具深入理解各组件协作原理,真正掌握高并发微服务系统的构建能力。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值