摘要： 简介:Acceptance at Origin功能常使用于美国国防部(US Department of Defense).该功能指在对货物有物理上的拥有之前,政府部门需获得拥有权.一旦有了拥有权,政府部门才可对发票进行付款. 货物移动类型107,109被引进以满足该需求.Acceptance at Origin Indicator in ERP Material Master Acceptance at Origin Indicator in SRM Product Data [COMMPR01] Acceptance at Origin Indicator in SRM Document L 阅读全文

摘要： 症状:You post a confirmation (backend Goods receipt) for SRM Purchase Orders, the releated document tab statistic view is not updated. You post an invoice (backend invoice) for SRM Purchase Orders, the releated document tab statistic view is not updated. The final confirmation flag or final invoice fl 阅读全文

摘要： 收货:使用IDoc Type WMMBID (4.0以前) MBGMCR(4.5以后)发票校验:使用IDoc Type BBPIV以BBPIV为例,收货也同样适用:1. 发票校验在SRM创建, IDoc BBPIV发出1.1 在发票中,状态设为I1022 "Release granted"和I1017 "In transfer".1.2 表BBP_DOCUMENT_TAB会插入值. 1.3 后台作业CLEAN_REQREQ_UP读表BBP_DOCUMENT_TAB.1.4 后台作业CLEAN_REQREQ_UP进行RFC Call per META_GOODSMVT_UPDATECHECK以检 阅读全文

摘要： Team purchasing is not buy on behalf of.后台配置: Define transaction typeYou can define No Team Purchasing/Admin Only/Admin+Users. Note: If Cross-organizational assignment is selected , user can select substitute from cross organization else from same organization.前台配置:可以在用户的个人设定配置 也可以在管理员用户下配置 Demo:1. 阅读全文

摘要： 演示ECC PR是如何进入SRM的 1: SOA direct When the PR is saved in transaction ME51n, the PR is transferred to SRM. SOA service will be called automatically. 2: SOA via CPPR When the PR is saved in transaction ME51n, the PR is transferred to SRM via CPPR application. Harmonized/ERP purchaser user must process 阅读全文

该文被密码保护。 阅读全文

摘要： 1140770 FAQ: F4-Help Cost Assignment 阅读全文

摘要： 前提:以下功能已经打开 SAP SRM Procurement for Public Sector Basis (/SAPSSRM/SRM_CROSS_INDUSTRIES)SAP SRM Procurement for Public Sector Functions (/SAPSSRM/SRM_PPS) 功能:1. 在订单的抬头部分,仅需一步即可取消整张订单中开放的部分(open item),即那些还未做收货或发票校验的行项目. 2. 一旦做了取消,在ECC端,系统自动取消预留资金(De-obligate Funds). 2.1 可通过表FMIOI查看. 2.2.如果做了取消预留资金,用 阅读全文

摘要： 想当年在为San Jose的Hitachi做服务时,那个台湾女老板很凶地责问SRM POWL为什么没有自动更新功能.当时是这么对付过去的:As POWL is static, the refresh doesn't happen automatically. The mentioned behavior is the standard, not a bug. According to our development this future is currently not available for SRM 7.0 . This is under development in Enhancem 阅读全文

摘要： 今天发现个NOTE..2010年8月底出的.从SRM7.0 SP10开始,SRM Classic Transfer的逻辑有重大变化. 首先,确保1342152已经打上[700 SP04, 500 SP16自动附带],该NOTE确保了BBP_GET_STATUS_2使用了正确的上锁机制.逻辑变化总结:1. Creation of backend documents in the backend system and updating of the SRM related data to these documents is now done in one synchronous step. (说 阅读全文